This document discusses various topics related to software engineering including software measurement, types of software measurement, purpose of software measurement, capability maturity model integration (CMMI), risk management, and software project estimation. It defines direct and indirect software measurements, explains why software measurement is important, and outlines issues that can be measured such as schedule, cost, size, quality, and ability. It also provides a brief history and overview of CMMI and discusses the main activities involved in software project planning including estimation, scheduling, risk analysis, and quality management planning.

2. .Process
Measurement
.CMMI
.Risk
Measurement
.Software
project
Estimation
(Software Engineering - 1)

3. Presented By:
Muhammad Kamran Chishti
18-Arid-386

4. Software Measurement:
– software measurement is an emerging field of a software engineering since it
may provide support for planning controlling and improving the software
development process as needed in any industrial development.

5. Types Of Software
Measurement:
There are two types of software Process measurements.
– Direct Measures:
• Easy to collect.
• (E.G) cost , effort , lines of codes , execution speed , memory size etc.
– Indirect Measures:
• More difficult to assess and can be measured indirectly only.
• (E.G) Quality , Functionality , Complexity , Reliability , Efficiency , etc.

6. Why Do Software Measurement?
– To do process improvement.
– To make a better estimate of the cost schedule , complexity , effort
requirements etc.

8. Purpose of Software
Measurement:
Provide insight to software process and products.
Better decision.
Manage the achievement of goals.

9. Issues that can be measured:
Schedule: Can we expect it to be done on time.
Cost: Can we afford to finish this project, or will it end up costing more
then it is worth.
Size: How big is the project so far.
Quality: is the project being made well with few bugs.
Ability: how much design/coding/debugging etc. can this team do per
month.
Performance: is the program fast enough using reasonable resources.

10. Capability Maturity Model
integration[CMMI]
– Software process:
– it is the way we produce software for customer
– A software process is a road map that helps you create a timely high
quality result.
– Process Maturity:
– A bench-mark for measuring the maturity of an organization software
process.
– The software engineering institute(SEI) has developed a framework to
judge the process maturity level of an organization.
– SEI CMMI is a process improvement approach that provides organization
with the essential elements of effective process.

11. History
– The CMM was developed from 1987
– CMMI is the successor of the capability maturity model (CMM) or software
CMM.
– In 2002 version 1.1 was released
– In 2006 version 1.2 was released
– In 2010 version 1.3 was released

12. Capability Maturity
Model[CMM]
– CMM is a reference model of matured practices in a specified discipline like
– System Engineering CMM
– Software CMM
– But they ware difficult to integrate as and when needed

13. Capability Maturity Model
Integration[CMMI]
– CMMI was developed by the CMMI project which aimed to improve the
usability of maturity models by integrating many different model into one
frame.
– The capability maturity model integration or CMMI is a process model that
provides a clear definition or what an organization should do to promote
behaviors that lead to improved performance.
– CMMI Objectives:
– Produce quality products or services
– Create value for the stockholders
– Enhance customers satisfaction

14. Risk Management
Software surprises can occur any time. let’s reduce their chance of survival.
What is Risk?
Possibility of unpleasant happening.
Risk can threaten the success of project.
Impact of Risk.
#Cost
#Schedule
#Success
#Quality
#Morale of team

15. Types of Risk
– Due to dependency: out sourcing projects.
– Wrong input/data/items by customers.
– Due to requirement issue:
– Lack of clear product vision.
– Rapidly changing requirements.
– Management is poor:
– No decision making.
– Poor communication.
– Due to lack of training: poor documentation.
– No experience.

17. Software Project Estimation
.The main activities which comes order software project planning are….
#Estimation
#Scheduling
#Risk Analysis
#Quality Management Planning
#Changes Management Planning

18. Estimation
– Estimation is an attempt to determine how much money , effort , resources and
time it will take to build a specific software based system or project.
– Who does Estimation.
– Software manager does estimation using information collected from customers
and software engineers.
– Software metrics data collected from past projects.
– Assumption taken from experience.

19. Steps For Estimation:
– Estimate the size of the development product.
– Estimate the effort in person month or person hours.
Time
Cost
Scope
Quality

20. Estimate Risk
– Before a final estimate is made problem complexity and risk are considered.
– Estimate risk.
– Estimate risk is measured by the degree of uncertainty in the quantitative
estimates established by the resources cost and schedule.