Student

Mini MRP System

Product: Flash Light

Requirements

Document ID: 001ps

Document Release Number: version 1.0.0

Document Release Date: 09/19/2002

Document Location: www.cse.fau.edu/~pshah1/001ps.doc

Abstract: This is the requirement document of our proposed software system which will help selling the product - Flash Light. This is the first version of the document written by Paulin Shah and is subject to review and corrections as suggested by all other members in the group and the instructor before it is approved.

Key Words: COP4331

Reviewers:

Position Name

Group Member 1

Group Member 2

Group Member 3

Group Member 4

Group Member 5

Instructor

REVISION HISTORY

Release Number Release Date Author Comments/Types of Release

TABLE OF CONTENTS

1 Introduction 4

1.1 Scope 4

1.2 Purpose 4

1.3 Sponsor 4

1.4 Project Manager 4

1.5 Project Number or Defect Tracking Number 4

1.6 Intended Audience 4

1.7 Definitions, Acronyms, Abbreviations 4

1.8 Overview 4

1.9 Assumptions 5

1.10 Methodology 5

1.11 References 5

1.12 Documentation 5

1.13 Training 5

2 Functional Requirements 6

3 Performance & Availability Requirements 8

3.1 Hardware Requirements 8

3.2 Software Requirements 8

3.3 Network Requirements 8

3.4 Performance Requirement 8

4 Application Security 8

5 Design Constraints 8

6 Impacts and Dependencies 8

6.1 Systems 8

6.2 Interfaces 8

6.3 Global Sites 9

Introduction

Scope:

This software system can be easily used by any company, building products from individual parts and ultimately selling them to the customers online. It will be very user friendly and robust software system, and thus will help in improving the business of the company itself.

Purpose:

This document is written with the sole aim of describing what the proposed software system will comprise of. It will be passed on to the developers so that they could develop the software system fulfilling all the requirements enlisted in this document.

Sponsor:

N.A

Project Manager:

N.A

Project Number or Defect Tracking Number:

A unique alphanumeric number will be given to each final product which will in turn represent the respective parts used in building the complete product itself. For eg. 113a343i343c23d324d

The alphabet will be the delimiter of the 1st part I.D. That is the I.D for Housing used will be 113a and that of the Bulb used will be 343i and that of the bulb reflector will be 343c and so on.

Intended Audience:

The software will give anyone trying to buy a Flash Light, an easily navigable set of options to help him select the different parts of the Flash Light and ultimately get him the complete product with desired functionalities and qualities.

Definitions, Acronyms, Abbreviations:

N.A

Overview:

Once the software system is in place, it will allow a potential buyer to log in to the homepage. Browse through the catalogue of different parts with different attributes. Make a final product and make the payment online. Once the payment info is verified the product will be shipped to the buyer at the shipping address provided by him. The various constraints incorporated in the software will help to make the system totally robust and stable.

Assumptions:

* The database with all the information of different parts is available.

Methodology:

* UML design should be used will coding the software(incorporating object oriented

Concepts.

References:

N.A

Documentation:

It should include two documents:

1) User's Manual.

It should give a detail understanding to the user as to how the software will operate. It should have good and detail screenshots showing various functionalities in use. It should be simple enough for a layman to understand how the software is operated.

2) Administrator's