©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 6/6/2016 1/25 IT076IU Software Engineering Project Review 2

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 2 6/6/2016 2/25  Team setup  Goal  Project plan System requirements System architecture Risk analysis  Q & A Topics

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 3 6/6/2016 3/25  Team – Members – Leader – Topics (30/09/12) 14Trần Nguyễn Ngọc ĐườngEvent 22Nguyễn Minh VươngBus Schedules 35Phan Tien NhutNews 4??? Team setup

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 4 6/6/2016 4/25 Goal

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 5 6/6/2016 5/25  Outline Introduction Project organization Resource requirements Work breakdown Project schedule System requirements System architecture Risk analysis Project Plan

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 6 6/6/2016 6/25  A document to show user requirements  Content Functional requirements Stories, scenario, use case Non-functional requirements Performance, user interface, data integrity, etc.  Reference Chapter 4 – Requirements engineering The software requirements document (Page 91-94) System requirements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 7 6/6/2016 7/25  Story (scenario, use cases)  Format A description of what the system and users expect when the story starts. A description of the normal flow of events (tasks) in the story. A description of what can go wrong and how this is handled. Information about other activities that might be going on at the same time. A description of the system state when the story finishes.  Reference Chapter 4 – Requirements engineering Elicitation and analysis (Page ) Functional Requirement

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 8 6/6/2016 8/25  Example Story / Scenario

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 9 6/6/2016 9/25  Example Use cases

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 10 6/6/ /25  Product Performance, memory, reliability, etc.  Organization Development process (programming language, etc.) Operation process (user group, etc.)  External Government regulation  Reference Chapter 4 – Requirements engineering Non-functional requirements (Page ) Non-functional requirements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 11 6/6/ /25  Example Non-functional requirements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 12 6/6/ /25  A document to show the structure and behavior of the system  Content System architecture High-level overview, function distribution across the system System models Component static/dynamic relationship, data flow  Reference Chapter 5 – System modeling Models (Page ) Chapter 6 – Architectural design Application architecture (Page 164) System architecture

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 13 6/6/ /25  Architecture diagram System architecture

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 14 6/6/ /25  Context System models

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 15 6/6/ /25  Interaction System models

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 16 6/6/ /25  Structural System models

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 17 6/6/ /25  Behavioral System models

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 18 6/6/ /25  A table to show anticipating risks that might affect the project schedule, and possible actions to avoid.  Risk categories Project: member quits Product: hardware failure Business: competitor with same software  Reference Chapter 22 – Project management Risks (Page ) Risk analysis

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 19 6/6/ /25  Example Risk analysis

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 20 6/6/ /25 Q & A