1 / 34

Sprint (2) Deliverables Capstone Courses

Sprint (2) Deliverables Capstone Courses. What are Sprint (2) Deliverables ?. Revised High level planning and scheduling WBS and Gannt (with risk assessment). Stakeholders Identification and Requirements Gathering Techniques (“2” techniques minimum). Revised High level features diagram.

waite
Download Presentation

Sprint (2) Deliverables Capstone Courses

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. Sprint (2) Deliverables Capstone Courses

  2. What are Sprint (2) Deliverables ? • Revised High level planning and scheduling WBS and Gannt (with risk assessment). • Stakeholders Identification and Requirements Gathering Techniques (“2” techniques minimum). • Revised High level features diagram. • Use Case Diagram. • Revised High level UML class diagram. • Sequence Diagram. • Second prototype (showing the “before: first prototype” and the “after: second prototype”). • Well-organized documentation Report on CD (no hard copies) that includes Sprint 1 and Sprint 2 deliverables (excluding implementation). • No introductory parts are required for Sprint 2 presentation. (Please read instructions next slide)

  3. Sprint (2) Instructions - A PPT presentation should be used and posted by the due date on the main discussion board on Webct. - Introduce your team (very briefly) in the first slide. - All team members should participate (no exceptions!). - Invite your sponsor to your class presentation (you will get extra credits if they attended). Outstanding efforts will be always rewarded. - Presentations are limited to 10 minutes each ( 4 minutes minimum should be dedicated to a live demo of the solution). - A documentation report of Sprint 1 and Sprint 2 deliverables is required on CD per team (not from each member).No hard copiesof your report are needed - Your report should have a title page, table of contents, numbered pages and sections and a references page( see samples and examples on our capstone roadmap) - No dress code is required in the second sprint (Yet, professionally dressed teams get extra credit for Sprint (2) [Midterm]. This will be a requirement though for both final presentation and the showcase)

  4. 1- Revised High Level Planning/Scheduling • Fine tune and include revised WBS. • Fine tune and include revised Gannt chart (that covers 5 sprints). • Fine tune and include revised Risk Assessment. Please note that you don’t need to re-invent the wheel here. Only reuse, revise and include your latest version of the above.

  5. 2-A Stakeholders Identification • Identify and define all key stakeholders • Rationalize stakeholders selection • Map stakeholders in a class hierarchy diagram

  6. Stakeholders Updated • Interactive Viewpoint Stakeholders • General Users • Registered Users • Tenants: • Student Tenants • General (Faculty) Tenants • Landlords and Owners • Property Managers • Apartment Complexes and Large Communities • Real Estate Brokers and Agents Highlighted Text: The Focused Areas of planning/development since Sprint 1

  7. Stakeholders Structure Updated Highlighted Text: The Focused Areas of planning/development since Sprint 1

  8. 2-B Requirements Gathering Techniques (2 Minimum for Sprint 2)

  9. TraditionalTechniques • Interviews • Questionnaires • Observations & Protocol Analysis • Document Archeology

  10. Modern Techniques • Prototyping • Use Cases • JAD • Brainstorming • Role Playing • Mind Mapping • Story boarding • Snow cards • Root Cause Analysis

  11. Classify and Specify Requirements • Functional Requirements • A process the system hast to perform • Information the system must contain • Nonfunctional Requirements • Behavioral properties the system must have • Operational • Performance • Security • Cultural and political

  12. 3- Revised High level features diagram • Include functional and non-functional requirements. • Fine tune and include revised Mapped Features (FDD Diagram). • Schedule/Track Features optional Please note that you don’t need to re-invent the wheel here. Only reuse, revise and include your latest version of the above.

  13. Product Sale Management (PS) CP-1 CP-1 CP-3 CP-1 CP-2 CP-1 Invoicing Sales (33) Making Product Assessments (14) Setting up Product Agreements (13) Delivering Products (10) Selling Products (22) Shipping Products (19) 99% 75% 30% 3% 10% Dec 2001 Dec 2001 Dec 2001 Dec 2001 Nov 2001 Dec 2001 Customer A/C Mgmt (CA) Inventory Mgmt (IM) CP-2 CP-2 CP-2 CP-3 CP-3 CP-3 Opening New Accounts (11) Logging Account Transactions (30) Accepting Movement Requests (18) Moving Content (19) Evaluating Account Applications (23) Establishing Storage Units (26) 100% 97% 82% 82% 95% 100% Oct 2001 Nov 2001 Nov 2001 Nov 2001 Oct 2001 Nov 2001 KEY: Work In Progress Attention Completed Progress Bar Not Started FDD Sample Features Diagram

  14. 4-Use Case Diagrams

  15. Steps in Creating the Use Case Diagram 1. Identify use cases 2. Draw the system boundary 3. Place use cases on the diagram Group use cases into packages Add special use case associations 4. Identify the actors 5. Add Associations

  16. Syntax for Use-Case Diagram

  17. Use Case Diagram for Appointment System

  18. Use-Case Diagram for Specialized Actor

  19. Extends or Uses Associations

  20. 5- Revised UML class diagram • Identify Classes, attributes and methods • Identify relationships (associations, aggregations an inheritance) • Determine multiplicities (or cardinalities) • Draw a UML class diagram to map all these components Please note that you don’t need to re-invent the wheel here. Only reuse, revise and include your latest version of the above.

  21. Class Diagram Syntax

  22. Class Diagram for Manage Appointment

  23. Multiplicity

  24. Association Class

  25. Aggregation and Generalization Associations

  26. Class Diagram for Customer Places Order (1)

  27. Class Diagram for Customer Places Order (2)

  28. Class Diagram for Customer Places Order (3)

  29. 6- Sequence Diagram

  30. Steps in Creating a Sequence Diagram 1. Identify classes 2. Add messages 3. Place lifeline and focus of control

  31. Sequence Diagram

  32. Syntax for Sequence Diagram

  33. Steps of the Customer Places Order Scenario

  34. Sequence Diagram for Customer Places Order Scenario

More Related