Uml Diagrams for Inventory Control System

Only available on StudyMode
  • Download(s) : 599
  • Published : March 8, 2013
Open Document
Text Preview
[pic]
Factors Contributing to Project Success According to Standish Report: 1. Executive Management Support
2. User involvement
3. Experienced Project Manager
4. Clear Business Objectives
5. Minimized Scope
6. Standard software Infrastructure
7. Firm Basic Requirements
8. Formal Methodology
9. Reliable Estimates
10. Other
The cost of incorrect, misunderstood, and not agreed upon requirements affects the customers and developers in terms of time, money, and lost opportunities.

Applying the CHAOS Ten in our project
User Involvement:
Identified the Users and Customers:
Stakeholder and User description in the Vision Document

Gathered needs from Users and Customers:
Role Playing

Interviews

Questionnaire

Brainstorming

Regular Meetings

Clear Business Objectives:
Identified the following in the vision document:
Business Opportunity

Problem Statement

Product position Statement

Product Perspective

Product Overview

Also performed:
Market Analysis

User Background Analysis

Minimized Scope:

Defined Deliverables
Defined Functionality

To help you define your scope, answered the following questions:

What processes (and what are not) are included in the scope of our project?  Where does each process begin and where does each process end? What systems (and what are not) are used in these processes are included in the scope?  What organizations (and what are not) involved in these processes are included in the scope? 

Standard Software Infrastructure:

Indentified the following in the Vision Document:
System Requirements:
Language, Operating System, Platform
Performance/Reliability Requirements:
Constraints
Quality Ranges
Product overview including assumptions and dependencies

Firm Basic Requirements:

Elicitation:

Statement of work/task definition.
Interviews
Group brainstorming.
Observation.
Questionnaires and/or surveys.
Prototyping

Approval process for all the requirements for both functional and non-functional requirements For interpreting and agreeing upon requirements, in weeding out requirements not considered, identifying potential or real bottlenecks, or deriving requirements we used:

UML collaboration/communications diagram.
UML state chart diagram.
UML sequence diagram.
UML activity chart.

Traceability of requirements:

Each Use Case used (in the Functional Requirements) can be traced back to the respective requirements of the project. Each Non functional requirement can be traced back to the features represented in the Vision Document. Requirements can be traced back to the Product Features defined in the vision document. Each Feature can be traced back to the wants and needs of individual customers (which were generated in the elicitation processes).

Find Store(Store Location Service)
[pic]

Return(Return Policy)
[pic]

Get Support(Customer Support)
[pic]

Customize (Configure products online)

[pic]

Get Advice(Help/Cfg Wizards)
[pic]

Searching (Provide a searchable online catalog, Inventory Tracking)

[pic]

Advertising(Company logo,links,Specials, Highlights, Cookies) [pic]
Promotions ( Promotions section (items on-sale) )

[pic]
Track Order(Track Shipments Online,Status by Email)
[pic]

Purchase (E-mail confirmation, Inventory Tracking,Store Billing Info w/ Profile)

[pic]
Register(Create Profile,Restration)
[pic]

Apply For Credit (Apply for Credit, E-mail confirmation,Financing) [pic]
Shipping(Store Shipping Info w/ Profile,Inventory Tracking,Notification to Shipping Dept.,Multiple Shipping Options)

[pic]

Restock(Inventory Tracking)

[pic]

Update Inventory (Inventory Tracking)

[pic]

Class Diagram

Below is a high-level class diagram for the MEHE E-Store. This diagram depicts the relationship between different departments within the store, as well as the...
tracking img