software measurement and analysis

18
LOGO Software Measurement and Analysis Team Assignment 02 Team 2 - HIT

Upload: lev

Post on 22-Feb-2016

39 views

Category:

Documents


1 download

DESCRIPTION

Software Measurement and Analysis. Team Assignment 02. Team 2 - HIT. Team members:. Team Assignment 02. Describing what the Viking project should measure to ensure business value to ABC Systems. Contents. 1. Project Description . 2. Project Scope . Business Value. 3. Measurement. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Software Measurement  and  Analysis

LOGO

Software Measurement and Analysis

Team Assignment 02

Team 2 - HIT

Page 2: Software Measurement  and  Analysis

Team members:Team members: Members ID

Giang Thị Hà Thanh T097828

Trần Dũng Đạt T095716

Nguyễn Vũ Trọng Giang T096656

Huỳnh Chấn Huy T096498

Tạ Quang Hiệp T090363

Nguyễn Trần Hồng Phúc T095014

Page 3: Software Measurement  and  Analysis

Team Assignment 02

Describing what the Viking project should measure to ensure business value to ABC Systems

Page 4: Software Measurement  and  Analysis

ContentsProject Description

Project Scope

Business Value

Measurement4

1

2

3

Page 5: Software Measurement  and  Analysis

Project Description

The objective of this project is to deliver the Viking product to market within 6 months of the kick-off of this project, and within budget

A multi-function project management tool (PMT) developed and sold to customers in many business sectors, initially including aerospace-defense companies.

Page 6: Software Measurement  and  Analysis

Project Description

Improves project management processes by providing the following functionality: action item management, to-do lists, risk and defect tracking, architecture, design, and test documentation management, and lessons learned reflections. The Viking project deliverables include the software application, user documentation (installation and user guide), and training material. Viking is intended to run on any desktop/laptop

Page 7: Software Measurement  and  Analysis

ContentsProject Description

Project Scope

Business Value

Measurement4

1

2

3

Page 8: Software Measurement  and  Analysis

Project Scope

The scope of the Viking project is to: Create the Viking software product Test the Viking product, including engineering

test, system test and beta test. Develop Viking all user and administrative

documentation and training material Produce Viking product CD(s) containing the

Viking system and soft documentation Prepare the material required to support the

Viking product (hopefully it will be supported by ABC Systems)

Page 9: Software Measurement  and  Analysis

ContentsProject Description

Project Scope

Business Value

Measurement4

1

2

3

Page 10: Software Measurement  and  Analysis

Business Value

Cross-sell products and services to utilize reasonable resources of the ABC system, providing maximum profit

Build an integrated, web enabled issue and action item logging and tracking application for a new ABC Systems customer. This will fill a critical gap in today’s project management tools industry and provide profit for ABC systems

Page 11: Software Measurement  and  Analysis

Business Value

Build and nurture long-term partnerships with ABC’s customers.

Be regarded as a premier provider of PMT solutions, develop a high quality architecture, toolkit and components

Regain the trust of customers after the Matador project, completed Viking project in time and cost with high quality

Page 12: Software Measurement  and  Analysis

ContentsProject Description

Project Scope

Business Value

Measurement4

1

2

3

Page 13: Software Measurement  and  Analysis

MeasurementNo Goal Question Measure Metric Description1 Schedule How do you

know the schedule on time?

- The actual progress (measured by person-month): A

- The estimate progress (measured by person-month): E

- Deviation of the progress estimate (measured by %): D

 

 

Provides information on how well the project is performing with respect to its schedule.

2 Risk How is the risk management process

- Numbers of risk identified (measured by risks): E

- Numbers of problem occurred during all process (measured by risks): A

- Deviation of the risk estimate (measured by %): D

  Know how much efficiency of the risk management process

3 Cost How do you know the cost estimation is accurate?

- The actual cost (measured by person-month): A

- The estimated cost (measured by person-month): E

- Deviation of the cost estimate (measured by %): D

 

 

Provides tracking of actual costs against estimated costs and predicts future costs.

Page 14: Software Measurement  and  Analysis

No Goal Question Measure Metric Description4 Change How is the

change management process?

- Numbers of change request approved (measured by change request): X

- Numbers of change request (measured by change request): D

- Rate of change request approved and change request (measured by %): R

 

 

 

 

Know how many percent change are approved

5 Defect How are unit tests effective?

- Numbers of defects found (measured by defects): Df

- Number of defects per line of code (measured by defects /KLOC): Sf

- Number of functions (measured by function): Fc

- Number of defects per function (measured by defects/function): Sc

- Defect /KLOC

-Defect/Function

Know how efficiency of debug progress

6 Customer satisfaction

Is the product’s quality sufficient to warrant release?

- Number of post-release defects found (measured by defects): X

- Number of pre-release defects fixed from the product (measured by defects): D

- Rate of pre-release defects removed from the product and Sum of that and post-release defects found (measured by %): R

 

 

 

 

Know how efficiency of fixing defect in pre-release

Page 15: Software Measurement  and  Analysis

No Goal Question Measure Metric Description

7 Quality Are the quality problems fixed?

- Number of defects fixed (measured by defects): X

- Number of defect found by a user acceptance test (measured by defects): D

- Rate of defect fixed and defect found by user acceptance test (measured by %): R

  Know how many percent of defect are fixed.

Page 16: Software Measurement  and  Analysis

No Goal Question Measure Metric Description8 Testing How do we

know the testing process good or not?

- Number of test cases executed (measured by test cases): E

- Number of test cases passed (measured by test cases): p

- Rate of test cases passed and test cases executed (measured by %): P

- Rate of test cases failed and test cases executed (measured by %): F

 

 

Know how many percent of test case passed or failed

Page 17: Software Measurement  and  Analysis

MeasurementNo Goal Questio

nMeasure Metric Description

9 Customer satisfaction

How do we know about software quality after release?

- Numbers of customer-found defects 3 month after release of Viking (measured by defects): V

- Numbers of customer-found defects 3 month after release of Matador (measured by defects): M

- Rate of customer-found defects 3 months after release of Viking and customer-found defects 3 months after release of Matador (measured by %): R

 

 

 

 

Know the percent of customer-found defects are fixed or not 3 months after release

Page 18: Software Measurement  and  Analysis

LOGO