1 / 20

IT076IU Software Engineering

IT076IU Software Engineering. Project Review 2. Topics. Team setup Goal Project plan System requirements System architecture Risk analysis Q & A. Team setup. Team – Members – Leader – Topics (30/09/12) 1 4 Trần Nguyễn Ngọc Đường Event 2 2 Nguyễn Minh Vương Bus Schedules

lavonn
Download Presentation

IT076IU Software Engineering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IT076IU Software Engineering Project Review 2

  2. Topics • Team setup • Goal • Project plan • System requirements • System architecture • Risk analysis • Q & A

  3. Team setup • Team – Members – Leader – Topics (30/09/12) 1 4 Trần Nguyễn Ngọc Đường Event 2 2 Nguyễn Minh Vương Bus Schedules 3 5 Phan Tien Nhut News 4 ? ? ?

  4. Goal

  5. Project Plan • Outline • Introduction • Project organization • Resource requirements • Work breakdown • Project schedule • System requirements • System architecture • Risk analysis

  6. System requirements • 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)

  7. Functional Requirement • 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)

  8. Story / Scenario • Example

  9. Use cases • Example

  10. Non-functional requirements • 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)

  11. Non-functional requirements • Example

  12. System architecture • 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)

  13. System architecture • Architecture diagram

  14. System models • Context

  15. System models • Interaction

  16. System models • Structural

  17. System models • Behavioral

  18. Risk analysis • 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)

  19. Risk analysis • Example

  20. Q & A

More Related