First, the software requirements management process
Three Key plan:
Range plan \ schedule \ Program costs (cost baseline, schedule baseline)
Software Requirements
Demand refers to the user's requirements for functionality and performance of software, is the software the user wants to do something, what kind of function is completed, to what performance.
Level software requirements
Reasons for project failure analysis
Software requirements management process
Requirements elicitation
Demand analysis (functional behavioral data model, modeling)
Writing requirements specifications
Needs verification
The basic mission requirements engineering
Requirements elicitation
Baseline: The assessment of demand
The definition of needs analysis
Needs analysis is for the end user sees the establishment of a system conceptual model is an abstract description of requirements.
Demand Analysis Model
Requirements Specification
- A basic requirement analysis is completed sign is the formation of a complete specification of requirements specifications
- Preparation of requirements specification is to enable users and software developers both sides have a common understanding of the provisions of the original software, making it the basis for the entire development effort.
Principles of software requirements specification
- Functional separation from reality, that is, to describe "what" rather than "how to achieve"
- The use of certain specification language
- If you are developing a software element is just a big system, then the whole system is also included among the big described in the specification of
- Specifications should include the system operating environment
- Specifications should be a model for understanding
- Specifications should be allowed incompleteness and allow expansion
Specification Reference Documents
- introduction
- System Definition
- Application Environment
- Functional Specifications
- Performance requirements
- Submit
- Implementation constraints
- Quality description
- other
- Signature certification
Needs verification
- Demand is right for you?
- Demand is the same do?
- Demand is complete it?
- Demand is it practical?
- Demand is necessary?
- Demand is it verifiable?
- Demand is traceable right?
- The final signature
The total change in demand
Requirements change management
- Identify needs change control process
- Establish Change Control Board (SCCB)
- Conduct requirements change impact analysis
- Tracking changes affect demand for all work products
- Establish baseline demand version of the document version and demand control
- Maintenance requirements change history
- Tracking the status of each requirement
- Measure needs stability
Requirements change management
Management and control requirements baseline process
Demand change control system
A formal document that explains how to control the demand for change
Build change approval system
Second, the definition of task decomposition
WBS (Work Breakdown Structure)
Task decomposition process will be broken down into more of a project or subproject work breakdown, make the project smaller, more manageable, easier to operate.
Task decomposition results WBS (Work Breakdown Structure).
WBS-oriented deliverables.
The lowest level Work packages (work packages) WBS deliverables
WBS examples
PMI defines WBS
Is a packet-oriented elements of the project deliverables, which organizes and defines the entire scope of the project. WBS is not included in the work is not the work of the project
It is a hierarchical tree structure, the decomposition process is project from coarse to fine. Work breakdown structure represents a hierarchical description of each project element more detailed
PMI defines Work packages
The lowest level of the WBS deliverables
Work packages should be responsible only subject
The deliverables can be assigned to another, a project manager for planning and implementation, or completed by way of subprojects
Third, the type of task decomposition
Types of
- Inventory
- chart
Chart Type
List Type
1. change counter
1.1 compare two versions of the program
1.1.1 Pretreatment
1.1.2 File Compare
1.1.3 result processing
1.2 added and deleted in the revised program to identify lines of code
1.2.1 identify additional lines of code
1.2.2 identify the deleted lines of code
The number of lines of code after the procedure 1.3 statistical modification adds and deletes.
1.3.1 statistical increase in the number of lines of code
1.3.2 Statistical delete lines of code
1.4 The total number of lines of code statistics
Setting 1.5 times marked to indicate modified
1.6 modify the record increase in the program's head
Fourth, the task decomposition methods
Task decomposition process
Decomposition
- Analogy: WBS reference to similar projects
- Template:, add or delete them through a common template
- Top-down
- bottom up
WBS template example
Decomposition - from top to bottom
Decomposition - bottom-up
Decomposition task structure (WBS) Step
Identify and break down the constituent elements of the project
OK decomposition Standard
Determine whether a detailed break down
Determine the project deliverables
Verify the correctness of the decomposition (build number)
WBS numbering system
WBS and the OBS (Organization Breakdown Structure)
Standard decomposition
- Survival
- Functional components
Decomposition standards should be uniform
Student Management
According to the decomposition of life
-
- Planning and design requirements submitted encoding test
- According to the composition of decomposition products
- 1.1 Enrollment Management
- 1.2 Placement Management
- 1.3 student records management
- 1.4 student achievement management
- You can not use both standards decomposition
- Enrollment Management Placement manage student records management design student achievement management planning needs to submit encoding test
The results of the decomposition test standards
- WBS decomposition of the size and number vary by project, because the project manager varies
- Collect all information relating to the project
- See what similar project WBS, discussions with stakeholders
- Templates can refer to the lowest level are controllable and manageable, but avoid unnecessary too small, preferably not more than 7 layers,
- Recommended software project task decomposition to 40 hours
- Note: 80/8 rule
- Each Work package must have a Submissions
- The standard definition of the task is completed
- Each WBS must be conducive to the allocation of responsibilities
- You can prepare WBS dictionary
- The last review with stakeholders
WBS dictionary content
