©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Review 1

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 2 Phase II report -1 l Due on 10/06 l On top of Phase I report l 5-15 pages in total (together phase I report) l Free style in writing (use 11pt font or larger) l Focus on requirements l Description of related activities, e.g., interviews with stakeholders l Describe functional and nonfunctional requirements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 3 Phase II report -2 l Provide scenarios or use-cases l Provide requirements management planning l Feasibility studies l Draw at least 2 models if applicable Context models Data-flow model State machine models Inheritance models Object aggregation models Object behaviour model

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 4 Exam 1 l Thursday, 10/04/05 l 1-hour l closed book l Chapters 1-8 l 20% of your total grade

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 5 Exam topics -1 l Chapter 1 Software engineering vs. system engineering Software process Software cost l Chapter 2 Socio-technical systems Emergent properties of a system Sub-systems Legacy system

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 6 Exam topics -2 l Chapter 3 Critical system Reliability and availability Safety and security l Chapter 4 Waterfall model Evolutionary development Exploratory development and throw-away prototype Component-based development Process iteration Rational unified process CASE tool

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 7 Exam topics -3 l Chapter 5 Project planning Milestones Deliverables Project scheduling Bar charts and activity networks Risk management

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 8 Exam topics -4 l Chapter 6 User requirements System requirements Functional/non-functional requirements Domain requirements Requirement documents

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 9 Exam topics -5 l Chapter 7 Stakeholders Viewpoints Feasibility studies Scenarios User cases Prototyping Requirement validation Requirement management

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 10 Exam topics -6 l Chapter 8 Context model Architectural model Behavioral model Data-flow models State machine models Data models Object inheritance model Object aggregation model UML

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 11 Sample exam questions - 1 l 1. Are the following statements about the software requirements document true or false? (1) Software engineering is only useful for those who become software engineers. (2) The requirements document should not specify responses to undesirable events.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 12 Sample exam questions - 2 l 2.Multiple choices l (1) In system modeling, a ___________ model shows the system’s reaction to events. A.Context B.Architectural C.Stimulus/response D.Data Processing

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 13 Sample exam questions - 2 l (2) System Requirements are A. A detailed list of services and constraints of a proposed system B. A natural language statement of the functionality a system should provide C. A list of basic requirements the system must meet to run the software D. Not on this test (wishful thinking) E. None of the above

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 14 Sample exam questions - 3 l (3) User Requirements are A. A detailed list of services and constraints of a proposed system B. A natural language statement of the functionality a system should provide C. A list of basic requirements the user must meet before using a given system D. Not condoned by my religion E. None of the above

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 15 Sample exam questions - 4 l 3. Short answers l (1) Describe the waterfall model of software development. What are some of its advantages and disadvantages? What alternatives exist? l (2) What type of UML diagram is used to describe a specific scenario of a use case? l (3) What is the difference between evolutionary and throw-away prototyping? l (4) What is one major difference between System Engineering and Software Engineering, as disciplines?

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 16 Sample exam questions - 5 l (5) What is the purpose of upper-CASE tools? l (6) Give one specific example of a possible emergent property of a nuclear power plant. State the property as a requirement. l (7) Give one specific example of an organizational non-functional requirement of each variety below. (a) Delivery: (b) Implementation: (c) Standards:

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 17 Sample exam questions - 6 l (8) Identify four potential stakeholders of a point- of-sale system at a gasoline fuel pump. l (9) Why is traceability an important aspect of requirements management? l (10) Give one reason why context system models are useful for requirements validation. l (11) Which style of prototyping is most appropriate when the requirements are not well- understood?

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 18 Sample exam questions - 7 l 4. Match each system to the most appropriate model and briefly justify your decision. l Software Process Models A. Waterfall Model B. Evolutionary Development C. Reuse-oriented Development l __3D modeling and animation software designed to have a revolutionary user interface and novel algorithms for creating surreal scenes __A shopping cart module for a website that needs to be up and running with basic functionality within a week __Implementation of a Linux driver for a hardware device where full specifications are available from the manufacturer

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 19 Sample exam questions - 8 l 6. Describe functional and non-functional requirements in the following categories. Functional requirementNon-functional requirement Definition List the requirements (three for each type) for a university library system

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 20 Sample exam questions - 9 TaskDuration (days)Dependencies T110 T210T1 T315 T45T1,T3 T515T2 T615T3 T715 T815T3,T4,T5 T935T7 T1020T4,T6 T1110T9 T1220T10 T1315T4,T5 T1410T11,T8 T1520T12,T14 T1615T13,T15 The accompanying table sets out a number of activities, durations, and dependencies. Draw an activity chart and identify the critical path(s). What is the length of the critical path? What is the maximum number of days that T4 can be delayed without impacting the finish date?