Final Status Report Team 5 Marvel Electronics

Final Status Report Team 5 Marvel Electronics & Home Entertainment Sonali Pagade Nibha Dhagat David Ziman Reginald Bradshaw II Sebastian Schagerer Janet Xu Phan 1

Purpose for Today’s Meeting Report on progress made sinception Review: Team Organization, Brain Storming, Vision Document Show past few weeks progress: Standish Report Use Case, Structural, and Behavioral Diagrams Non Functional Requirements, Mockup 2

Project Deliverables To Do: Finish SRS Peer ratings Project Evaluation Completed: Vision Document Project Plan Draft Status Report 1 & 2 Final Status Report 3

Organizing the Team Exchanged contact information Setup Yahoo! Group for communication and file sharing/storage Group Meetings to discuss project plan 4

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 5

Vision Document Sections 1 -7 1. Introduction 2. Positioning 6

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 7

Vision Document Sections 4 -8 4. Product Overview 5. Product Features 6. Constraints 7. Quality Ranges 8. Precedence and Priority 8

Feature Priority Browse History 1 Business Information 3 Catalog 5 Compatibility 5 Customer Service 5 Customer Support 3 Feedback 1 Information Sharing 3 Inventory Tracking 5 Legal 5 Localization 3 Maintenance 5 Order Confirmation 5 Order Scheduling 5 Order Tracking 5 Order Translation 5 Payment 5 Pricing 3 Product Configuration 5 Profile 5 Profiling 1 Promotions 5 Returns 3 Security 5 Shipping 5 Shopping Cart 5 Site Design 5 Wish List 1 9

Vision Document Sections 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 10

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. 11

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 Brainstorming Regular Meetings 12

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 13

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? 14

Standish Report Firm Basic Requirements: Elicitation: Statement of work/task definition. Interviews Group brainstorming. Observation. Prototyping Approval process for all the requirements for both functional and non-functional requirements 15

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 Use Case diagram. UML class diagram. UML sequence diagram. Non-Functional SIGs 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. 16

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). 17

Stakeholders’ wants and needs Vision Document Functional Requirements Non-Functional Requirements Models 18

User Case Diagram 19

Structural 20

Register Create Profile, Restration 21

Advertising Company logo, links, Specials, Highlights, Cookies 22

SECURITY ++ + INTEGRITY AVAILABILITY COMPLETENESS CONFIDENTIALITY ACCURACY AUTHORIZATION CONSISTENCY + REGISTRATION _ ++ PERFORMANCE PASSWORD + INDIVIDUAL PASSWORD USERNAME _ SHARED PASSWORD 23

PERFORMANCE CAPACITY RESPONSE TIME IMPROVES RESPONSE TIME ++ SPACE UTILIZATION THROUGHPUT + + COMPRESSED FORMAT INDEXING SINGLE LEVEL KEYWORD BASED MULTI LEVEL CATEGORY BASED 24

RELIABILITY INTEGRITY ACCURACY AVAILABILITY ++ COMPLETENESS ! EFFICIENCY MINIMUM NUMBER OF HOPS CONSISTENCY ++ PERFORMANCE (RESPONSE TIME) 25

MAINTAINABILITY ! + EXTENSIBILITY _ AVAILABILITY TESTABILITY ++ BREAKDOWN TIME UNDERSTANDABILITY MODIFIABLE USABILITY USER FRIENDLY 26

USABILITY FLEXIBILITY USER FRIENDLY ACCESSIBILITY + LANGUAGE RELIABILITY AESTHETICS CHANGE/CANCEL ORDER DEFAULT MULTILINGUAL 27

Mockup - Registration 28

Mockup - Login 29

Mockup - Advertising/Promotions 30

Search Methods Advanced Configuration 31

Mockup - Purchase/Shipping 32

Mockup - Customer Service 33

Summary & Things Learned Standish Report Traceability Tools NFR Modeling 34

The next two weeks Finish work on SRS Peer Ratings Project Evaluations 35

Questions? 36