1. September 200391.3913 Ron McFadyen1 design analysis implementation testing maintenance Waterfall Development Process Linear one phase is completed before the next begins in practice, must revise earlier decisions based on experience in project - I.e. there is feedback

2. September 200391.3913 Ron McFadyen2 design analysis implementation testing maintenance Waterfall Development Process Not iterative errors in earlier phases are really expensive to fix doesn’t allow for prototyping which is a strong aid for confirming requirements

3. September 200391.3913 Ron McFadyen3 A Generic Spiral Process for Development evaluate Analyze risks / plan Engineer (design, implement, test) Analyze requirements for this iteration 4 phases comprise one iteration arbitrary number of iterations user involvement early feedback Studies show more successes with an iterative approach

4. September 200391.3913 Ron McFadyen4 Unified Process (UP) Defined by Rational Corporation Booch, Rumbaugh, Jacobson An iterative development process an iteration yields a working system iterations last anywhere from 2 weeks to 6 months many iterations make a project risk-driven early iterations prove out the major risks or show- stoppers

5. September 200391.3913 Ron McFadyen5 Unified Process (UP) several activities deliverables are referred to as artifacts - works produced (use cases, code, database designs, …) 4 phases inception, elaboration, construction, transition Inception Use case model is started

6. September 200391.3913 Ron McFadyen6 Figure 2.4 Illustrates the activities in UP used to develop a system Iterative development is central to the UP

7. September 200391.3913 Ron McFadyen7 Figure 2.3 illustrates the 4 phases comprising the UP More requirements gatheringMore programming

8. September 200391.3913 Ron McFadyen8 Unified Modeling Language (UML) Booch, Rumbaugh, Jacobson (the 3 Amigos) joined forces (all work for Rational) to create a unified development method/process, from which came the Unified Modeling Language (UML) Not a methodology Methodologies can use UML examples: Rational’s Unified Process; Catalysis value of UML is in the common language IT professionals have for expressing the nature of a system

9. September 200391.3913 Ron McFadyen9 Use Cases Use Cases help with: requirements capture scope definition iteration management test planning

10. September 200391.3913 Ron McFadyen10 Use Cases a Use Case is initiated by an Actor Describes functional requirements from the user’s perspective illustrate actors & tasks forms: pictorial (defined in UML) textual not defined in UML recommended to leave UI details out and focus on the purpose of the use case focus on what the system does, not how it does it (black box)

11. September 200391.3913 Ron McFadyen11 Figure 9.1

12. September 200391.3913 Ron McFadyen12 Figure 9.3

13. September 200391.3913 Ron McFadyen13 Use Cases Widely used. Not just an OO technique. Diagramming defined in UML Each Use Case will meet one or more user goals; collectively, Use Cases represent the functionality required by a system. 2 Forms: diagrams, textual – simplicity is important, both used Scenario: an instance of a Use Case. Scenarios document a single flow (a story) through a Use Case, and are useful for testing purposes later on. Main success scenario, Alternate scenario 1, Alternate scenario 2, …

14. September 200391.3913 Ron McFadyen14 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” www.usecases.org - may be of use to you in the future “blackbox” style is recommended - specify what the system must do, and not how it must do it. A project may begin with the definition of many “brief” or “casual” use case definitions. Later on, these can be become “fully dressed”

15. September 200391.3913 Ron McFadyen15 Use Cases Ch 6. Use Case example is very lengthy and fairly complete must read: pages 45-61, and sections 6.12, 6.13, 6.15 Ch 25. Use Case has been broken down into multiple Use Cases that are related via > and > must read: sections 25.1, 25.2, 25.3, 25.5

16. September 200391.3913 Ron McFadyen16 Use Cases Diagrams System boundary Actors – ‘stick people’ Use cases – ovals Associations Actors and use cases Extend Include …

17. September 200391.3913 Ron McFadyen17 Use Case Example - diagram Cashier Process Sale Handle Cheque Payment > Handle Cash Payment > Handle Credit Payment Process Rental >

18. September 200391.3913 Ron McFadyen18 Cashier Process Sale Handle Cheque Payment > Handle Cash Payment > Handle Credit Payment Process Rental > Handle Gift Certificate Payment > Use Case Example - diagram

19. September 200391.3913 Ron McFadyen19 Use Case Example - textual Ch 6 example. Process Sale Ch 25 example Process Sale Process Rental Handle Credit Payment Handle Cheque Payment Handle Gift Certificate Payment