Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 6/6/2016 1/25 IT076IU Software Engineering Project Review 2."— Presentation transcript:

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

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

3 ©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

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

5 ©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

6 ©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

7 ©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 105 - 107) Functional Requirement

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

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

10 ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 10 6/6/2016 10/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 88 - 90) Non-functional requirements

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

12 ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 12 6/6/2016 12/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 122 - 141) Chapter 6 – Architectural design Application architecture (Page 164) System architecture

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

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

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

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

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

18 ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 18 6/6/2016 18/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 595 - 601) Risk analysis

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

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


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

Similar presentations


Ads by Google