1. Marvel Electronics and Home Entertainment E-Store Project Team 4 April 11, 2007

2. Team Members Sean Ngo - Project Manager Sean Ngo - Project Manager Enoch Asamoah – Business Analysis Enoch Asamoah – Business Analysis Karthick Salem – Requirements Engineer Karthick Salem – Requirements Engineer Denis Stetsenko – Design Engineer Denis Stetsenko – Design Engineer Prachi Upadhyay – Requirements Engineer Prachi Upadhyay – Requirements Engineer

3. Presentation Purpose Layout the Design Requirements (features and baseline architecture) Layout the Design Requirements (features and baseline architecture) Eliminate ambiguity on the problem domain Eliminate ambiguity on the problem domain Avoid mistakes from the Standish Report Avoid mistakes from the Standish Report

4. Project Scope Order Management Order Management Intuitive Organization (easy browsing and searching) Intuitive Organization (easy browsing and searching) Flexible Services (products, payments and shipping) Flexible Services (products, payments and shipping) Marketing / Sales Marketing / Sales Attractive Interface Attractive Interface User Centric (info, interaction) User Centric (info, interaction) Products Promotion (product info, aggressive pricing) Products Promotion (product info, aggressive pricing) Fast response (24/7 customer service) Fast response (24/7 customer service) Inventory Channel Inventory Channel Streamline with exiting inventory Streamline with exiting inventory

5. Where we stand now? Rational Unified Process

6. Timeline We are here

7. Business Use Case Diagram

8. Possible Design Use Case Diagram

9. Business Class Diagram

10. Business Sequence Diagram

11. Possible Design Sequence Diagram for sales process

12. Non Functional Requirements Brainstorming Session Brainstorming Session Multiple NFR are found like Security, Performance, Reliability, Usability, Flexibility etc. Multiple NFR are found like Security, Performance, Reliability, Usability, Flexibility etc. We focus on Security, Performance and Reliability We focus on Security, Performance and Reliability

13. NFR Model - Security SecuritySecurity IntegrityIntegrity ConfidentialityConfidentiality AvailabilityAvailability AccuracyAccuracyCompletenessCompleteness AuthenticationAuthentication PasswordPassword Finger Print Password + Finger Print SingleSingle MultipleMultiple Operationalize + + +

14. NFR Model - Performance PerformancePerformance Speed Efficiency Resource usage ThroughputThroughput Response time

15. NFR Model - Reliability ReliabilityReliability Severity of Failure RecoverabilityRecoverabilityPredictabilityPredictability AccuracyAccuracy

16. Business Solutions Business RequirementsSolution Open up new marketse-Commerce will allow its business in a broader scale world wide. Cost Saving for MEHELower expenditure in creating new stores. Improve customer satisfactionThe e-Store will merge online and local customer service into one kind of solution leading to more customer comfort and satisfaction Faster inventory reductionThe system will support online orders leading to reduce unnecessary inventory consumption. SecurityOnline payment provides more secured transactions. AccessibilityWeb based system leads to more and fast accessibility to MEHE.

17. Standish Report vs Problems encountered Standish ReportOur Problems Lack of User involvement Incomplete Requirements Lack of feedback from customers. Unrealistic Expectations Unclear Objectives Lack actual system understanding. Changing requirementsChange in customer representatives Unrealistic time frame Schedule limitations

18. Proposed Solutions Involve users throughout the requirements gathering process Involve users throughout the requirements gathering process Have users attend reviews and receive incremental feedback from users Have users attend reviews and receive incremental feedback from users Give realistic expectations Give realistic expectations To solve communication issues, employ specialists in business or system analysis To solve communication issues, employ specialists in business or system analysis

19. What we have learnt from this project Requirements are not obvious Requirements are not obvious To understand the customers wants/needs To understand the customers wants/needs To distinguish requirements and design To distinguish requirements and design Documentation traceability is important Documentation traceability is important To work as a team To work as a team

20. Recommended Next Steps Get our project requirements specification approved Get our project requirements specification approved Focus on the architecture and design specification Focus on the architecture and design specification Generate the Software Design Specification Generate the Software Design Specification Implement project prototype Implement project prototype

21. Demo Prototype based on functional and non functional requirements. Prototype based on functional and non functional requirements. Organized Organized Attractive Attractive