Uml Diagrams for Inventory Control System
[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
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