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



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
Business Use Case Diagram
Possible Design Use Case Diagram
Business Class Diagram
Business Sequence Diagram
Possible Design Sequence Diagram
for sales process
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
Integrity
Accuracy
Availability
Confidentiality
Operationalize
Completeness
Authentication
Password
+
+
Single
Multiple
+
Finger Print
Password +
Finger Print
NFR Model - Performance
Performance
Speed
Efficiency
Resource
usage
Throughput
Response
time
NFR Model - Reliability
Reliability
Severity of
Failure
Recoverability
Predictability
Accuracy
Business Solutions
Business Requirements
Solution
Open up new markets
e-Commerce will allow its business in
a broader scale world wide.
Cost Saving for MEHE
Lower expenditure in creating new
stores.
Improve customer satisfaction
The e-Store will merge online and
local customer service into one kind
of solution leading to more customer
comfort and satisfaction
Faster inventory reduction
The system will support online
orders leading to reduce
unnecessary inventory consumption.
Security
Online payment provides more
secured transactions.
Accessibility
Web based system leads to more
and fast accessibility to MEHE.
Standish Report vs
Problems encountered
Standish Report
Our Problems
Lack of User involvement
Incomplete Requirements
Lack of feedback from
customers.
Unrealistic Expectations
Unclear Objectives
Lack actual system
understanding.
Changing requirements
Change in customer
representatives
Schedule limitations
Unrealistic time frame
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