1. Process 3a 1 A Spiral Model of Software Development and Enhancement Barry Boehm Computer, May 1988 text pp34-45

2. Process 3a 2 Software Process Model u “The primary functions of a software process model are to determine the order of the stages involved in software development and evolution and to establish the transition criteria for progressing from one stage to the next.”

3. Process 3a 3 Who discovered the waterfall model? u A. Royce in 1970 u B. Boehm in 1988 u C. Fred Waterfall in 1950 u D. It always existed, someone just named it in 1966 u E. Every other discipline knew about it long ago

4. Process 3a 4 Advice u Use a life-cycle development model to manage software development –The stages become milestones to mark progress

5. Process 3a 5 Question u How do you decide whether a stage is complete? –A. The manager says it is complete –B. The team is ready to go on to the next stage –C. The team votes on whether it is complete

6. Process 3a 6 TRW’s Ada Process Model for Incremental Development of Large Software Systems Walker Royce 12th ICSE 1990 text pp46-55

7. Process 3a 7 Interesting Approach u Incremental development u Used Ada as spec language as well as implementation u Using stubs and drivers to execute partially implemented systems

8. Process 3a 8 Software Process “Software Processes are software, too” Leon Osterweil (1987)

9. Process 3a 9 software process

10. Process 3a 10 Definition u A process model is a description of the significant aspects of the tasks that are accomplished during the development of software, including the artifacts produced, the agents involved in the activities, and the relationships between these entities.

11. Process 3a 11 Rules for PM diagrams u Every process must use one or more artifacts and must produce one or more artifacts. u There must be an artifact between two consecutive processes.

12. Process 3a 12 Testing Fragment u The test designer builds test cases using the source code and the documents. The output is a set of tests u The test team does testing using the tests from the test designer and the source code producing a test report

13. Process 3a 13 Example Fragment

14. Process 3a 14 Example - testing u shows who is responsible for what tasks u shows what information is necessary for a task u shows what is produced by a task u shows sequences and dependencies of tasks

15. Process 3a 15 PM Notations u Many possible notations –functional diagrams –state diagrams –petri models –textual descriptions –“programming languages”

16. Process 3a 16 PM - petri net docsourcedesigner tests build t c test team testing test report

17. Process 3a 17 Entities in Process Models u Activities/Tasks u Information –Artifacts (Products) –Knowledge u Agents –People, Positions, Roles u Constraints

18. Process 3a 18 Control Decisions u Some PM show control in terms of decisions

19. Process 3a 19 Example Fragment with Decision

20. Process 3a 20 L3aS20 Group Task u Create a process model for a cooking-dinner task. u Work in groups of 2-4 only. u Turn in at beginning of 2 nd hour.