230 likes | 424 Views
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.
E N D
Marvel Electronics and Home Entertainment E-Store ProjectTeam 4 April 11, 2007
Team Members • Sean Ngo - Project Manager • Enoch Asamoah – Business Analysis • Karthick Salem – Requirements Engineer • Denis Stetsenko – Design Engineer • PrachiUpadhyay – RequirementsEngineer
Presentation Purpose • Layout the Design Requirements (features and baseline architecture) • Eliminate ambiguity on the problem domain • Avoid mistakes from the Standish Report
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
Where we stand now? Rational Unified Process
Timeline We are here
Non Functional Requirements • Brainstorming Session • Multiple NFR are found like Security, Performance, Reliability, Usability, Flexibility etc. • We focus on Security, Performance and Reliability
NFR Model - Security Security Availability Integrity Confidentiality Accuracy Completeness Operationalize Authentication + + Password + Finger Print Finger Print Password + Multiple Single
NFR Model - Performance Performance Response time Throughput Speed Efficiency Resource usage
NFR Model - Reliability Reliability Severity of Failure Recoverability Predictability Accuracy
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
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
Recommended Next Steps • Get our project requirements specification approved • Focus on the architecture and design specification • Generate the Software Design Specification • Implement project prototype
Demo • Prototype based on functional and non functional requirements. • Organized • Attractive