180 likes | 355 Views
Process Modeling. CS 4320 Fall 2003. Process Difficulties. SW not a production line Each project is different—even within the same company No universally accepted processes for SE Shelfware No Training Resistance (is not always futile). Levels of Process (Humphrey).
E N D
Process Modeling CS 4320 Fall 2003
Process Difficulties • SW not a production line • Each project is different—even within the same company • No universally accepted processes for SE • Shelfware • No Training • Resistance (is not always futile)
Levels of Process (Humphrey) • U – Universe (Life Cycles) • W – Worldly (sequence of tasks and prereq) • A – Atomic (enormously detailed) • Can also be viewed as: • Policies • Procedures • Standards
Example Levels (Humphrey) • U – Waterfall Model • W – Critical Design Review held before entry into implementation, Issues are submitted to… • A – Actual checklist for critical design review
Levels of Process (Text) • Meta-Object Facility – Model of Model Notation • Process Metamodel – Model Notation (UML) • Process Model – Model itself (RUP) • Performing Process – What we actually do
Process Decomposition (ISO 12207) • Process (High Level Category) • Activity (Major Common Categories) • Task (Actual Work Tasks)
Examples • Process: Software Requirements Analysis • Activity: Complete Requirements Spec • Task: Conduct Requirements Review
ISO Std 12207 • Primary • Acquisition (Let the contract) • Supply (Fulfill the contract) • Development (Make the product) • Operation (Operate the product in a system) • Maintenance (Correct/Modify the product)
ISO Std 12207 • Organizational Processes • Management • Infrastructure • Improvement • Human Resource • Asset Management • Reuse Program Management • Domain Engineering
ISO Std 12207 • Supporting • Documentation • Configuration Management • Quality Assurance • Verification • Validation • Joint Review • Audit • Problem Resolution • Usability • Product Evaluation
ISO Std 12207 • Development Activities • Process Implementation • System Requirements Analysis • System Architectural Design • Software Requirements Analysis • Software Architectural Design • Software Detailed Design • Software Coding and Testing • Software Integration • Software Qualification Testing • System Integration • System Qualification Testing • Software Installation • Software Acceptance Support
U Level Software Life Cycle Models • Examples of Models: • Code-and-Fix • Waterfall • Incremental, Design to Sched • Spiral • Evolutionary Proto, Delivery • Life-cycle: A project-specific, sequenced mapping of activities. May be a “standard” model adapted for your specific project. • Choose Right One for project and Tailor it • Table 7-1 (Rapid Development) Choosing a life cycle model
Issues in Selecting Life Cycle • How well are requirements understood? • How “firm” are requirements? • How long can you go without “something”? • How much risk is there? • How hard is it to use the model? • How much overhead is required? • Do I have an artificial schedule?
Process Architecture (ETVX) Resources Needed N Input Output Process Name Entry Exit Activity List Measures Feedback Out Feedback In Interfaces Interfaces
Filled out cell MS Project 1. Approved SDP 2. Approved WBS 3. Project Init in MS Marketing Inputs Concept Approval 001 Project Planning Resource Schedule Info • Estimate Effort • Prepare WBS • Prepare Schedule Measurement: Person-Months KLOC Requests for Clarification Scope Changes Interface: Approved ECP Interface: email phone formal memo
Class Exercise, Process Models • Pick a Life Cycle Model……. • And let’s model it…
The Infosys Process Description • Overview • Participants • Entry Criteria • Exit Criteria • Inputs • Activities • Exit Criteria • Outputs • Measurements • Special Considerations • References