1 / 13

Marvel Electronics and Home Entertainment

Marvel Electronics and Home Entertainment. e-Commerce System Final Status Report April 12, 2005 (Tuesday). Business Objectives. Convert our e-Business mind share to market share. Increase our technology leadership, strengthen our brand, grow our business.

shanna
Download Presentation

Marvel Electronics and Home Entertainment

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-Commerce System Final Status Report April 12, 2005 (Tuesday)

  2. Business Objectives • Convert our e-Business mind share to market share. • Increase our technology leadership, strengthen our brand, grow our business. • Lead in creating the future of e-Business. • Become the premier marketing and sales company in our industry. • Attract, motivate and retain the best talent in our industry. • Transform MEHE into the premier e-Business.

  3. Project Objectives • Provide faster response to customer needs across all segments • Allow product configure-to-order and profit multipliers. • Aligning Development, Integration and Deployment Plans. • Reduce overhead and costs by developing a real-time inventory control system.

  4. Project Scope • Process Scope • Sales Promotions and Marketing Strategies • Order Processing • Job Application and Applicant Selection • Real-Time Support (24/7) • Inventory Control System [Delayed to v2.0] • Geographic Scope • Current plan: implement for United States only. • Potential Geographic Scope • Extend to EMEA, Asia, Canada and Latin America • Time Scope • 4Q2005

  5. Project Timeline(projected phase completion dates) • 14 Apr 2005 – Inception (Modeling, Requirements) • 17 Jun 2005 – Elaboration (Architecture, Analysis and Design) • Construction • 17 Jul 2005 – Beta Release • 30 Sep 2005 – Product Release • 01 Oct 2005 – Transition (Production)

  6. Project Approach • Used Brainstorming, Interviewing, Research, Storyboarding and Input Document Analysis to generate customer wants and needs. • Categorized customer wants and needs into major features. Also generated Business Use Case Diagram (BUCD) and Data Flow Diagram (DFD). [VISION DOCUMENT] • From BUCD and DFD, generated use cases (function requirements), non-functional requirements, and design constraints. Also generated high-level test cases. [SRS]

  7. Deliverables • Revised Vision Document • Software Requirements Specification (including Supplemental Specification, Design Constraints, and Requirements Traceability Matrix) • Test Plan (including Test Guidance) • Software Development Plan (including Requirements Management Process)

  8. Risk Assessment • “Feature Creep” • Aggressive Schedule • Available Technology • Development Team Skill Level • Personnel Availability

  9. Recommended Next Steps • Assuming MEHE internal development • Assign Project Manager, System Architect, QE Lead and SQA Engineer • Assemble Development and Testing Teams • Conduct Architectural Interviews to scope the work and refine schedule

  10. Special Topic - Main • Understanding • User Needs • Quality Measures for Requirements

  11. Special Topic – User Needs • Functional Requirements • What does the customer really want? • User Needs are categorized into Features • Non-Functional Requirements • Identify system requirements that cannot be tied to a Feature

  12. Special Topic – Quality Measures • Non-Functional Requirements • “Goodness” Requirements, such as Reliability, Availability, Usability, Maintainability, and Performance • Quantification (Moving from Abstract to Concrete)

  13. Course Feedback • Re-enforces that in business, determining “What to Build” is usually more important than “How to Build” • Project was very practical and realistic, including the tight deadlines • Real-world examples helped re-enforce the concepts • Follow-up course would be interesting, where we take our requirements, and perform the analysis and design

More Related