Feasibility Study:Inventory System of avon
Computerized Sales Inventory System for Avon – Sogod Branch Requirements Specification
Version 1.0
October 18, 2013
Use this Requirements Specification template to document the requirements for your product or service, including priority and approval. Tailor the specification to suit your project, organizing the applicable sections in a way that works best, and use the checklist to record the decisions about what is applicable and what isn't.
The format of the requirements depends on what works best for your project.
This document contains instructions and examples which are for the benefit of the person writing the document and should be removed before the document is finalized.
Table of Contents Computerized Sales Inventory System 1 for Avon – Sogod Branch Requirements Specification 1 Version 1.0 1 October 18, 2013 1
1. Executive Summary 3
1.1 Project Overview 3
1.2 Purpose and Scope of this Specification 3
2. Product/Service Description 4
2.1 Product Context 5
2.2 User Characteristics 5
2.3 Assumptions 5
2.4 Constraints 5
2.5 Dependencies 7
3. Requirements 7
3.1 Functional Requirements 8
3.2 User Interface Requirements 9
3.3 Usability 9
3.4 Performance 10
3.5 Manageability/Maintainability 11
3.6 Security 12
3.7 Data Management 13
3.8 Standards Compliance 14
4. User Scenarios/Use Cases 14
5. Deleted or Deferred Requirements 15
6. Requirements Confirmation/Stakeholder sign-off 15
1. Executive Summary
1.1 Project Overview
The following proposed system is intended for the sales staff of Avon-Sogod branch. The sales staff client will be represented by Ms. Emma D. Alvarez (primary client) and branch officer-in-charge Ms. Diane Anzano. Ms. Alvarez wants a computerized sales inventory to be able to minimize the inventory time when using the manual system and improved the inventory system of Avon-Sogod branch and Ms. Anzano is a project participant. Ms. Alvarez will be our
Version 1.0
October 18, 2013
Use this Requirements Specification template to document the requirements for your product or service, including priority and approval. Tailor the specification to suit your project, organizing the applicable sections in a way that works best, and use the checklist to record the decisions about what is applicable and what isn't.
The format of the requirements depends on what works best for your project.
This document contains instructions and examples which are for the benefit of the person writing the document and should be removed before the document is finalized.
Table of Contents Computerized Sales Inventory System 1 for Avon – Sogod Branch Requirements Specification 1 Version 1.0 1 October 18, 2013 1
1. Executive Summary 3
1.1 Project Overview 3
1.2 Purpose and Scope of this Specification 3
2. Product/Service Description 4
2.1 Product Context 5
2.2 User Characteristics 5
2.3 Assumptions 5
2.4 Constraints 5
2.5 Dependencies 7
3. Requirements 7
3.1 Functional Requirements 8
3.2 User Interface Requirements 9
3.3 Usability 9
3.4 Performance 10
3.5 Manageability/Maintainability 11
3.6 Security 12
3.7 Data Management 13
3.8 Standards Compliance 14
4. User Scenarios/Use Cases 14
5. Deleted or Deferred Requirements 15
6. Requirements Confirmation/Stakeholder sign-off 15
1. Executive Summary
1.1 Project Overview
The following proposed system is intended for the sales staff of Avon-Sogod branch. The sales staff client will be represented by Ms. Emma D. Alvarez (primary client) and branch officer-in-charge Ms. Diane Anzano. Ms. Alvarez wants a computerized sales inventory to be able to minimize the inventory time when using the manual system and improved the inventory system of Avon-Sogod branch and Ms. Anzano is a project participant. Ms. Alvarez will be our