Transcript A Gantt Chart

Sprint (2) Deliverables
Capstone Courses
What are Sprint (2) Deliverables ?
1.
2.
3.
4.
5.
6.
7.
8.
9.
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)
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)
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.
2-A Stakeholders Identification
- Identify and define all key stakeholders
- Rationalize stakeholders selection
- Map stakeholders in a class hierarchy
diagram
 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
Interactive
Stakeholders
Registered
Users
Tenants
Landlords /
Owners
General
Users
Property
Managers
Apartment
Complexes/
Large
Communities
Real Estate
Agents/Broker
Student
Tenants
General
(Faculty)
Tenants
Highlighted Text: The Focused Areas of planning/development since Sprint 1
2-B Requirements Gathering
Techniques
(2 Minimum for Sprint 2)
Traditional Techniques
•Interviews
•Questionnaires
•Observations & Protocol Analysis
•Document Archeology
Modern Techniques
• Prototyping
• Use Cases
• JAD
• Brainstorming
• Role Playing
• Mind Mapping
• Story boarding
• Snow cards
• Root Cause Analysis
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
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.
FDD Sample Features Diagram
Product Sale Management (PS)
CP-1
CP-1
CP-3
CP-1
Selling
Products
Shipping
Products
Delivering
Products
Invoicing
Sales
(22)
(19)
(10)
(33)
99%
10%
30%
3%
Nov 2001
Dec 2001
Dec 2001
Dec 2001
CP-2
Setting up
Product
Agreements
(13)
CP-2
Inventory Mgmt (IM)
CP-2
CP-3
Opening
New
Accounts
(11)
Logging
Account
Transactions
(30)
Establishing
Storage Units
95%
100%
82%
Oct 2001
Oct 2001
Work In Progress
Dec 2001
Dec 2001
Evaluating
Account
Applications
(23)
KEY:
Making
Product
Assessments
(14)
75%
Customer A/C Mgmt (CA)
CP-2
CP-1
Nov 2001
Attention
CP-3
CP-3
Moving
Content
(26)
Accepting
Movement
Requests
(18)
100%
97%
82%
Nov 2001
Nov 2001
Completed
Progress Bar
(19)
Nov 2001
Not Started
4-Use Case Diagrams
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
Syntax for Use-Case Diagram
Use Case Diagram for
Appointment System
Use-Case Diagram for
Specialized Actor
Extends or Uses Associations
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.
Class Diagram Syntax
Class Diagram for Manage
Appointment
Multiplicity
Association Class
Aggregation and Generalization
Associations
Class Diagram for Customer
Places Order (1)
Class Diagram for Customer
Places Order (2)
Class Diagram for Customer
Places Order (3)
6- Sequence Diagram
Steps in Creating a Sequence
Diagram
1. Identify classes
2. Add messages
3. Place lifeline and focus of control
Sequence Diagram
Syntax for Sequence Diagram
Steps of the Customer Places
Order Scenario
Sequence Diagram for Customer Places
Order Scenario