Download presentation
Presentation is loading. Please wait.
Published byJocelyn Warner Modified over 9 years ago
1
Sprint (2) Deliverables Capstone Courses
2
What are Sprint (2) Deliverables ? 1.Revised High level planning and scheduling WBS and Gannt (with risk assessment). 2.Stakeholders Identification and Requirements Gathering Techniques (“2” techniques minimum). 3.Revised High level features diagram. 4.Use Case Diagram. 5.Revised High level UML class diagram. 6.Sequence Diagram. 7.Second prototype (showing the “before: first prototype” and the “after: second prototype”). 8.Well-organized documentation Report on CD (no hard copies) that includes Sprint 1 and Sprint 2 deliverables (excluding implementation). 9.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 copies of 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
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
8
2-B Requirements Gathering Techniques (2 Minimum for Sprint 2)
9
Interviews Questionnaires Observations & Protocol Analysis Document Archeology Traditional Techniques
10
Modern Techniques Prototyping Use Cases JAD Brainstorming Role Playing Mind Mapping Story boarding Snow cards Root Cause Analysis
11
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 Classify and Specify Requirements
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) Invoicing Sales (33) Dec 2001 CP-1 Setting up Product Agreements (13) Dec 2001 Selling Products (22) Nov 2001 CP-1 Shipping Products (19) Dec 2001 CP-1 10% Delivering Products (10) Dec 2001 CP-3 30% Making Product Assessments (14) Dec 2001 75% 99% 3% Customer A/C Mgmt (CA) Evaluating Account Applications (23) Oct 2001 95% Logging Account Transactions (30) Nov 2001 82% Opening New Accounts (11) Oct 2001 100% Inventory Mgmt (IM) Establishing Storage Units (26) Nov 2001 100% Moving Content (19) Nov 2001 82% CP-3 Accepting Movement Requests (18) Nov 2001 97% CP-3 KEY:Work In Progress Attention Completed Progress Bar Not Started CP-2CP-1 CP-2 CP-3 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 G roup 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
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.