1 / 22

Marvel Electronics and Home Entertainment E-Store Project Team 4

Marvel Electronics and Home Entertainment E-Store Project Team 4. April 11, 2007. Team Members. Sean Ngo - Project Manager Enoch Asamoah – Business Analysis Karthick Salem – Requirements Engineer Denis Stetsenko – Design Engineer Prachi Upadhyay – Requirements Engineer.

lana-ramsey
Download Presentation

Marvel Electronics and Home Entertainment E-Store Project Team 4

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


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

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

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

  4. Project Scope • Order Management • Intuitive Organization (easy browsing and searching) • Flexible Services (products, payments and shipping) • Marketing / Sales • Attractive Interface • User Centric (info, interaction) • Products Promotion (product info, aggressive pricing) • Fast response (24/7 customer service) • Inventory Channel • 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 • Multiple NFR are found like Security, Performance, Reliability, Usability, Flexibility etc. • We focus on Security, Performance and Reliability

  13. NFR Model - Security Security Availability Integrity Confidentiality Accuracy Completeness Operationalize Authentication + + Password + Finger Print Finger Print Password + Multiple Single

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

  15. NFR Model - Reliability Reliability Severity of Failure Recoverability Predictability Accuracy

  16. Business Solutions

  17. Standish Report vsProblems encountered

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

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

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

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

More Related