Planning at CMM level 2 Copyright, 2000 © Jerzy R. Nawrocki [email protected] ...
-
Upload
mikaela-bowditch -
Category
Documents
-
view
213 -
download
0
Transcript of Planning at CMM level 2 Copyright, 2000 © Jerzy R. Nawrocki [email protected] ...
Planning at CMM level 2Planning at CMM level 2
Copyright, 2000 © Jerzy R. Nawrocki
www.cs.put.poznan.pl/jnawrocki/mse/quality/
Requirements Engineering Requirements Engineering
Lecture 12Lecture 12
Requirements Engineering Requirements Engineering
Lecture 12Lecture 12
J. Nawrocki, Requirements Eng.., Lecture 12
Plan of the lecturePlan of the lecturePlan of the lecturePlan of the lecture
IntroductionWork productsWork products measuresAbilitiesWide-band Delphi MethodAbilities (contd.)Activities
J. Nawrocki, Requirements Eng.., Lecture 12
IntroductionIntroductionIntroductionIntroduction
Documented procedures for ..
• developing an SDP• estimating size, effort, cost, critical
computer resources, and schedule• planning SQA activities• planning SCM• . . .
J. Nawrocki, Requirements Eng.., Lecture 12
IntroductionIntroductionIntroductionIntroduction
Product measures
Process measures
Size
Effort
Cost (not applicable?)
(Computer) resources
Delivery date (schedule)
Measures at CMM Level 2
J. Nawrocki, Requirements Eng.., Lecture 12
Work productsWork productsWork productsWork products
• IPD• Concept of the system• SRS• (Intermediate) design• Implementation (a set of
modules)• Acceptance tests• Bachelor thesis
• Specification
• Implementation idea
• Code
• Test bed
• Test cases
J. Nawrocki, Requirements Eng.., Lecture 12
Work productsWork productsWork productsWork products
• IPD• Concept of the system• SRS• (Intermediate) design• Implementation (a set of
modules)• Acceptance tests• Bachelor thesis
1 Introduction (~IPD)
2 Concept of the system
3 Requirements specification
4 Intermediate design
5 Implementation
6 Acceptance tests
7 Development plans
8 Measurements
9 Conclusions
J. Nawrocki, Requirements Eng.., Lecture 12
Work product measuresWork product measuresWork product measuresWork product measures
• IPD (A4, ch)• Concept of the system
(A4, ch, sc, bh)• SRS (A4, ch, rq)• (Intermediate) design
(A4, ch, de)• Implementation (A4, lc,
ch, ht, tb, tc)• Acceptance tests (A4,
ch, tb, tc)• Bachelor thesis (A4, ch)
A4: A4 pages
ch: characters
sc: scenarios
bh: behaviours
rq: requirements
de: diagram elements
lc: Lines of code
ht: HTML tags
tb: test beds
tc: test cases
J. Nawrocki, Requirements Eng.., Lecture 12
AbilitiesAbilitiesAbilitiesAbilities
Ab1. A documented and approved statement of work exists for the software project.
J. Nawrocki, Requirements Eng.., Lecture 12
AbilitiesAbilitiesAbilitiesAbilities
Scope of the work
Technical goals and objectives
Identification of customers & end users
Imposed standards
Assigned responsibilities
Cost and schedule constraints and goals
Statement of Work (I)
J. Nawrocki, Requirements Eng.., Lecture 12
AbilitiesAbilitiesAbilitiesAbilities
Dependencies between the software project and other organisations (customer, subcontractors, j.v. partners)
Resource constraints
Other constraints
Statement of Work (II)
• Statement of work is reviewed.
• It is managed and controlled.
J. Nawrocki, Requirements Eng.., Lecture 12
AbilitiesAbilitiesAbilitiesAbilities
Ab2. Responsibilities for developing the software development plan are assigned.
• The project manager co-ordinates the project’s planning.
• Responsibilities for the software work products and activities are partitioned and assigned to in a traceable, accountable manner.
J. Nawrocki, Requirements Eng.., Lecture 12
Responsibilities at PUT
AbilitiesAbilitiesAbilitiesAbilities
SQA plan: the SQA group
SCM plan: S.C. Manager
Other activities and work products: ‘Project Planner’ (4th year)
The recommended technique: Wide-band Delphi Method
J. Nawrocki, Requirements Eng.., Lecture 12
Wide-band Delphi methodWide-band Delphi methodWide-band Delphi methodWide-band Delphi method
Rand Corporation, Boehm’81
• A few experts individually produce size estimates.
• A Delphi process is used to reach a consensus.
PythiaPythia
J. Nawrocki, Requirements Eng.., Lecture 12
Wide-band Delphi methodWide-band Delphi methodWide-band Delphi methodWide-band Delphi method
1. Experts get the specification and an estimation form
2. They meet for discussion (project goals, assumptions, estimation issues)
3. Each expert anonymously lists the tasks and estimates the size
4. The estimates go to the estimate moderator. He tabulates the results and returns them to the experts.
The Delphi procedureThe Delphi procedure
The estimateThe estimate
moderatormoderator
J. Nawrocki, Requirements Eng.., Lecture 12
Wide-band Delphi methodWide-band Delphi methodWide-band Delphi methodWide-band Delphi method
Estimator: Jerzy Nawrocki Date: 22.06.1999
Project: Sorting routine
The estimates from the 1st round:
e E M e e
0 20 40 60 80 100
e - estimates, E - your estimate, M - median estimate
Your estimate for the next round: ......... LOC
A rationale for your estimate: ...........................................
..............................................................................................
J. Nawrocki, Requirements Eng.., Lecture 12
Wide-band Delphi methodWide-band Delphi methodWide-band Delphi methodWide-band Delphi method
5. The experts meet to discuss the results. They review the tasks they have defined but not their size estimates.
6. The procedure is repeated from step 3 until the estimates are acceptably near
The Delphi procedureThe Delphi procedure
The estimateThe estimate
moderatormoderator
J. Nawrocki, Requirements Eng.., Lecture 12
AbilitiesAbilitiesAbilitiesAbilities
Ab3. Adequate resources and funding are provided for planning the project.
Is it enough?
J. Nawrocki, Requirements Eng.., Lecture 12
AbilitiesAbilitiesAbilitiesAbilities
Ab4.
• The software managers,
• software engineers, and
• other individuals involved in the software project planning
are trained in the software estimating and planning procedures applicable to their areas of responsibility.
J. Nawrocki, Requirements Eng.., Lecture 12
Plan of the lecturePlan of the lecturePlan of the lecturePlan of the lecture
IntroductionWork productsWork products measuresAbilitiesWide-band Delphi MethodAbilities (contd.)
Activities
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
Ac1. The software engineering group participates on the project proposal team.
The software engineering group reviews the proposed commitments.
J. Nawrocki, Requirements Eng.., Lecture 12
Overallplanning
ActivitiesActivitiesActivitiesActivities
Ac2. Software project planning is initiated in the early stages of, and in parallel with, the overall project planning.
Softwareplanning
At PUT:
software project = overall proj.
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
Ac3. The software engineering group participates with other affected groups in the overall project planning throughout the project’s life.
The software engineering group reviews the project-level plans.
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
Ac4. Software project commitments made to individuals and groups external to the organisation are reviewed with senior management (J.N. or B.W.) according to a documented procedure.
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
Ac5. A software life cycle with predefined stages of manageable size is identified or defined.
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
IPDConcept of the system (scenarios)Soft. requirements specificationDetailed planningHigh-level design with UMLRelease 1 (from reqs to acceptance)Release 2Final acceptance (bachelor degree)
Classical software life cycle at PUT
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
Ac6. The project’s software development plan is developed according to a documented procedure.How
towriteSDP
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
The SDP is based on the customer’s and project’s standards, IPD, and SRS.
Plans are negotiated with the affected groups (3rd year!). The agreements are documented.
The SDP is reviewed, and managed and controlled.
Howto
writeSDP
The planning procedure at PUT
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
Howto
writeSDP
The planning procedure at PUT
• The SDP is approved by the Project Area Manager (Bartek).
• The SDP is available through the project’s web page along with all the previous versions of it. That web page is referenced in the Initial Project Description (IPD).
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
Ac7. The plan for the software project is documented.SD P
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
1. Introduction
1.1 Purpose of the Document
1.2 Scope of the Plan
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
2. Project’s purpose, scope, goals, and objectives
3. The selected software life cycle
5. Work products to be developed
SDP (I)
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
5. Selected procedures, methods, and standards 5.1 Change management procedure 5.2 Configuration management 5.3 Review procedure 5.4 Unit testing 5.5 Integration testing 5.6 SRS standard 5.7 Coding standards 5.8 Acceptance procedure 5.9 Bachelor thesis standard
SDP (II)
J. Nawrocki, Requirements Eng.., Lecture 12
ActivitiesActivitiesActivitiesActivities
6. SQA plan7. SCM plan8. Size estimates9. Effort estimates10. Estimated use of critical computer resources11. The project schedule with milestones &
reviews12. Risk factors and mitigation plans13. Project facilities and support tools
SDP (III)
J. Nawrocki, Requirements Eng.., Lecture 12
Generic FTR procedureGeneric FTR procedureGeneric FTR procedureGeneric FTR procedure
Parameters to be specified in SDP
• Name of the product• URL of the standard doc-struct• Due date for approved product• Producer• Review leader (SQA group)• Recorder (SQA group)• Reviewers (including recorder)• Expected preparation time• Expected meeting duration
J. Nawrocki, Requirements Eng.., Lecture 12
SummarySummarySummarySummary
Wide-band Delphi Method
Work products and their measures
Function Points have not been discussed
The planning procedure
Structure of the SDP
J. Nawrocki, Requirements Eng.., Lecture 12
Further readingsFurther readingsFurther readingsFurther readings
[CMM] M.C. Paulk et. al.,The Capability
Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, Reading, 1994.
J. Nawrocki, Requirements Eng.., Lecture 12
HomeworkHomeworkHomeworkHomework
• Does SDS Initial Project Description satisfy the requirements imposed by CMM on a ‘statement of work’. If not, propose a new standard for IPD.
• Exercise the Wide-band Delphi Method
J. Nawrocki, Requirements Eng.., Lecture 12
Quality assessmentQuality assessmentQuality assessmentQuality assessment
1. What is your general impression? (1 - 6)
2. Was it too slow or too fast?
3. What important did you learn during the lecture?
4. What to improve and how?