After studying this chapter you will be able to: Review (or learn for the first time); introduction to use case modelling; what are the major steps in an object-oriented design process? How? stakeholder identification, requirements elicitation, use case diagrams; major alternatives (not taught in this course): user stories (for agile development), formal specifications (for safety-critical software). | Software Construction Lecture 2 Use Cases 1 Agenda & Reading 2 Topics: Review (or learn for the first time) What are the major steps in an Object-Oriented Design process? Introduction to Use Case modelling What? A process of determining what the stakeholders require – by decomposing their requirements into tasks (or “use cases”) for each class of stakeholders. How? Stakeholder Identification, Requirements Elicitation, Use Case Diagrams Why learn this? Use cases are widely used in the industry, because they seem to work pretty well, aren’t very expensive to develop, and are at a good level of detail for end-users. Major alternatives (not taught in this course): user stories (for agile development), formal specifications (for safety-critical software). Reading: D. G. Firesmith, “Use Cases: the Pros and Cons”, in The Wisdom of the Gurus, SIGS Reference Library,1996. Available: . To learn more (optional reading): A. Ramirez, “Requirements Capture”, in . | Software Construction Lecture 2 Use Cases 1 Agenda & Reading 2 Topics: Review (or learn for the first time) What are the major steps in an Object-Oriented Design process? Introduction to Use Case modelling What? A process of determining what the stakeholders require – by decomposing their requirements into tasks (or “use cases”) for each class of stakeholders. How? Stakeholder Identification, Requirements Elicitation, Use Case Diagrams Why learn this? Use cases are widely used in the industry, because they seem to work pretty well, aren’t very expensive to develop, and are at a good level of detail for end-users. Major alternatives (not taught in this course): user stories (for agile development), formal specifications (for safety-critical software). Reading: D. G. Firesmith, “Use Cases: the Pros and Cons”, in The Wisdom of the Gurus, SIGS Reference Library,1996. Available: . To learn more (optional reading): A. Ramirez, “Requirements Capture”, in ArgoUML User Manual, , 2011. Object Management Group, “Use Cases”, in OMG Unified Modeling Language (OMG UML) Superstructure, v , 6 August 2011. Software Design (review) 3 Communication: identify stakeholders, find out what they want and need. Planning: list tasks, identify risks, obtain resources, define milestones, estimate schedule. Modeling: develop structure diagrams and use cases, maybe some other UML artifacts. Construction: implement the software, with assured quality. Deployment: deliver the software, then get feedback for possible revision. To learn more: R. Pressman, Software Engineering: A Practitioner’s Approach, 7th Ed., 2010, pp. 14-15. 3 Stakeholder Identification 4 Identify a variety of stakeholders, by asking yourself: Who is likely to be affected by, or to have an effect on, this system? Classify the stakeholders you know about. Anyone who will directly use the system is a stakeholder. Anyone who will be indirectly affected (in a major way) is a stakeholder. .
