Final Status Report

1
Final Status Report

• For Marvel Electronics and Home Entertainment
• Team 5

2
Purpose for Todays Meeting

• Report on progress made since inception
• Review Team Organization, Brain Storming, Vision
  Document
• Show progress for Standish Report, Use Case,
  Structural, and Behavioral Diagrams, Non
  Functional Requirements, Mockup

3
Project Deliverables

• To Do
• Finish SRS
• Done
• Vision Document
• Project Plan Draft
• Status Report 1 2
• Final Status Report

4
The last few weeks

• Created..
• Use Case Diagram
• Structure Diagram
• Behavior Diagram
• Non-Functional Requirements Diagram

5
Organizing the Team

• Exchanged contact information
• Setup Yahoo! Group for communication and file
  sharing/storage
• Group Meetings to discuss project plan

6
Brainstorming Session

• Brainstorming for product needs and wants
• Brainstorming session with appropriate
  stakeholders
• Revised Brainstormed Ideas
• Accepted or Rejected wants/needs
• Created a comprehensive Feature list

7
Vision Document Sections 1-7

• 1. Introduction
• 2. Positioning

8
Section 3 - Stakeholders

• Understand who is involved in the current
  business process
• Understand who will be involved in the improved
  process
• Identify features with Stakeholders for
  traceability

9
Vision Document Sections 4-8

• 4. Product Overview
• 5. Product Features
• 6. Constraints
• 7. Quality Ranges
• 8. Precedence and Priority

10
(No Transcript)
11
Vision DocumentSections 9-10

• 9. Other Product Requirements
• 10. Documentation
• User Manual
• Online Help
• Labelling and Packaging
• Appendix A. Feature Attributes
• Status, Benefit, Effort, Risk, Stability, Target
  Release, Assigned To, Reason

12
Standish Report

• Factors Contributing to Project Success
  According to Standish Report
• 1. Executive Management Support
• 2. User involvement
• 3. Experienced Project Manager
• 4. Clear Business Objectives
• 5. Minimized Scope
• 6. Standard software Infrastructure
• 7. Firm Basic Requirements
• 8. Formal Methodology
• 9. Reliable Estimates
• 10. Other
• The cost of incorrect, misunderstood, and not
  agreed upon requirements affects the customers
  and developers in terms of time, money, and lost
  opportunities.

13
Standish Report

• Applying the CHAOS Ten in our project
• User Involvement
• Identified the Users and Customers
• Stakeholder and User description in the Vision
  Document
• Gathered needs from Users and Customers
• Role Playing
• Interviews
• Questionnaire
• Brainstorming
• Regular Meetings

14
Standish Report

• Clear Business Objectives
• Identified the following in the vision document
• Business Opportunity
• Problem Statement
• Product position Statement
• Product Perspective
• Product Overview
• Also performed
• Market Analysis
• User Background Analysis

15
Standish Report

• Minimized Scope
• Defined Deliverables
• Defined Functionality
• To help you define your scope, answered the
  following questions
• What processes (and what are not) are included in
  the scope of our project?  Where does each
  process begin and where does each process end?
• What systems (and what are not) are used in these
  processes are included in the scope? 
• What organizations (and what are not) involved in
  these processes are included in the scope? 

16
Standish Report

• Standard Software Infrastructure
• Identified the following in the Vision Document
• System Requirements
• Language, Operating System, Platform
• Performance/Reliability Requirements
• Constraints
• Quality Ranges
• Product overview including assumptions and
  dependencies

17
Standish Report

• Firm Basic Requirements
• Elicitation
• Statement of work/task definition.
• Interviews
• Group brainstorming.
• Observation.
• Questionnaires and/or surveys.
• Prototyping
• Approval process for all the requirements for
  both functional and non-functional requirements

18
Standish Report

• For interpreting and agreeing upon requirements,
  in weeding out requirements not considered,
  identifying potential or real bottlenecks, or
  deriving requirements we used
• UML collaboration/communications diagram.
• UML state chart diagram.
• UML sequence diagram.
• UML activity chart.
• Reliable Estimation
• Based on scope of the project prepared a
  Preliminary master schedule
• For deliverables according to the deadline
• Resources required to complete a deliverable.

19
Standish Report

• Traceability of requirements
• Each Use Case used (in the Functional
  Requirements) can be traced back to the
  respective requirements of the project.
• Each Non functional requirement can be traced
  back to the features represented in the Vision
  Document.
• Requirements can be traced back to the Product
  Features defined in the vision document.
• Each Feature can be traced back to the wants and
  needs of individual customers (which were
  generated in the elicitation processes).

20
User Case Diagram
21
Structural
22
Behavioral - Sequence

• These diagrams map out the sequence of actions
  that are required to accomplish each business
  task in the use case diagram

23
Behavioral Sequence 2

• Each Diagram is directly traceable to a use case
• Also the actions in the diagrams can be traced to
  features in the Vision Document

24
Registration Sequence
25

SECURITY



INTEGRITY

AVAILABILITY

CONFIDENTIALITY


ACCURACY
COMPLETENESS

AUTHORIZATION


CONSISTENCY
REGISTRATION
_




PERFORMANCE
PASSWORD
USERNAME

_


INDIVIDUAL PASSWORD
SHARED PASSWORD
26
Mockup - Customer Service
27
Mockup - Advertising/Promotions
28
Search MethodsAdvanced Configuration
29
Mockup - Login
30
Mockup - Registration
31
Mockup - Purchase/Shipping
32
A few Problems

• Meeting time for group
• In progress
• Creating Diagrams based on vague descriptions
• In progress

33
The next two weeks

• Finish work on SRS

34
Questions?