E-Store System for MEHE Final status report Team #2 Sandeep, Vijay, Jennifer, Ali, Meghna April 6 th, 2007.

Slides:



Advertisements
Similar presentations
Project Analysis Course ( ) Final Project Report Overview.
Advertisements

Project Management Shuffle Directions: take the definitions from the following cards and write a song using the tune from “Cupid Shuffle”
Quick Recap. Quick Recap The Project Plan Plan Your Work, then Work Your Plan.
Marvel Electronics and Home Entertainment E-Store Project Team 4 April 11, 2007.
1 Marvel Electronics and Home Entertainment e-Commerce System Final Status Report April 12, 2005 (Tuesday)
Object-Oriented Analysis and Design
Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
Online Hotel Reservation System
Internet Sellouts Final Presentation Enterprise Architecture Group.
OO Process Steps  Define requirements Allocate and Derive requirements Map requirements to use cases Map requirements to classes  Define use cases Draw.
Final Presentation Team Crutch. Agenda Process – Justin Vision Document Issues Use Case Diagram Domain Diagram SIG Prototype Why Team Crutch?
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
Unit 211 Requirements Phase The objective of this section is to introduce software system requirements and to explain different ways of expressing these.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
Documenting Requirements using Use Case Diagrams
Requirements Specification MAJIK Software Solutions 1 Virtual Network Device Mapping System Requirements Specification By MAJIK Software Solutions October.
School of Science Network Device Display System Requirements Specification by Orion Technologies Roger Bacon Hall Room 328 October 24, :15 AM.
4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.
Systems Analysis and Design in a Changing World, 6th Edition
Team Members Rachid Alaoui Medarhri (Senior Student). Tarek Bougroug (Senior Student). Supervised By : Dr. Driss Kettani.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
NJIT Inception is not the Requirements Phase Chapter 4 Applying UML and Patterns Craig Larman.
G.Chiozzi European Southern Observatory Trieste 04/10/1999 Icalepcs 99 Tutorial Use Cases for Requirements Capture and Tracing.
Team Crutch. Vision Statement Team crutch aims to develop portable, inexpensive, user-friendly software for the Android platform that mitigates communication.
Recreation and Wellness Intranet Project
RUP Requirements RUP Artifacts and Deliverables
RUP Fundamentals - Instructor Notes
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
MSF Requirements Envisioning Phase Planning Phase.
Online Music Store MSE Project Presentation I Presented by: Reshma Sawant Major Professor: Dr. Daniel Andresen.
CIS 895 – MSE Project KDD-Research Entity Search Tool (KREST) Presentation 2 Eric Davis
1 Create and Manage Shopping Carts and Receive Goods (Requester) Take the journey. Enjoy the view.
Hobb-IT Hobby Information Tracker By Illumination Technologies Requirements Specification October 28 rd Illumination Technologies Hobb-IT.
Nick Small, Shawn Boughey, Karolina Latkoska Project Briefing 1.
Project Scope Management Project management Digital Media Department Unit Credit Value : 4 Essential Learning time : 120 hours.
Chapter 7 Applying UML and Patterns -Craig Larman
Chapter 7 Applying UML and Patterns Craig Larman
Project Life Cycle.
Facility Integration Project Update Chelsea Smith – Project Manager Lake Shore Solutions.
1 Final Status Report Sonali PagadeNibha Dhagat David Ziman Reginald Bradshaw II Sebastian Schagerer Janet Xu Phan Marvel Electronics & Home Entertainment.
1 אירוע אמאזון. 2 שלבי הפיתוח עם דיאגרמות UML 3 אמאזון תרשים תוכן.
The link to the Custom Point Login is:
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
Deliverable 10. Deliverable #10 Class Design and Implementation #1 due 9 April Executive Summary and Statement of Work Iteration Plan (Updated) for remaining.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
 SAP AG 2007, SAP CSUN 2007 Conference Presentation / 1 Presented by Team “Call of Duty” 29 th April 2010 CS 6361, University of Texas At Dallas.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
Training Guide. The Punch Out Catalog System The Punch Out shopping catalog for Corporate Express takes the user directly into the vendor’s website and.
Requirement Engineering
User Interface Design Storyboarding Wireframe Diagram AP Inventor.
Requirements Analysis
SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)
A Project Report On Online Shopping By: Ruchi Kumari (08ERWCS089)
Work In Progress Presentation. Orders Alex Thornton.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
Project Management PTM721S
Elaboration popo.
Applying UML and Patterns
Customer Online Ordering
B2C Online Store. B2C Online Store Group Members Introduction Name: Muhammad Gulfam VU ID: MC Program: MCS Supervisor: Muhammad Qamar Usman.
TPM – A Tailored Approach Project Management Web Button Design
Guidance notes for Project Manager
Project Analysis Course
Other Requirement Artifacts
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Introduction to Project Management
CSCI 360: Software Architecture & Design
Presentation transcript:

E-Store System for MEHE Final status report Team #2 Sandeep, Vijay, Jennifer, Ali, Meghna April 6 th, 2007

Agenda Introduction Inception phase Problem analysis and understanding the stakeholder phase System definition phase Project status

Introduction Perform Requirements Engineering process A0 Executive Summary _EXEC.htm _EXEC.htm Requirements Specification Requirements Specifier Stakeholder input

A0 Executive Summary Requirements Specification Requirements Specifier Stakeholder input ? ​?​? ? A01 A02 A03

A0 Executive Summary Requirements Specification Requirements Specifier Stakeholder input Inception ​?​? ? A01 A02 A03 Vision doc

Inception i/p: executive summary, and stakeholder i/p o/p: vision document (problem statement, system scope, product perspective, stakeholders and users)‏

Problem statement

Product perspective Develop an e-store that will enable the Marvel Electronics and Home Entertainment achieve its e-market goal

A0 Executive Summary Requirements Specification Requirements Specifier Stakeholder input Inception ​ Problem analysis & understanding stakeholders ? A01 A02 A03 Vision doc Business model

Problem analysis and understanding the stakeholder i/p: vision document, stakeholder i/p o/p: business model (business use case and business sequence diagram)‏

Business Use Case

Purchase Item

Process Order

Package and Ship

Inventory Management

Customer Service

Domain Model

A0 Executive Summary Requirements Specification Requirements Specifier Stakeholder input Inception ​ Problem analysis & understanding stakeholders System definition A01 A02 A03 Vision doc Business model

System definition i/p: vision document, business model, stakeholder i/p o/p: complete requirement specification (system use case, sequence diagram, class diagram, glossary, NFR document, non- working prototype)‏

Use case

Sequence diagram – Purchase item use case

Class diagram

NFR

NFR cont…

Non-working prototype - Home

Login

Register

View search results

View product catalog

View cart details

Option to check out as guest

Provide shipping & payment details

Confirmation of order

View order status

Project status Preliminary Investigation Produce Presentation Produce NFR document Produce Business model Problem Analysis Produce Prototype Produce Design model Produce Vision document

Addressing the problem of incomplete, ambiguous and confusing requirements

Lessons learned Team co-ordination Estimation of project scope UML modeling tools

Questions?