Gas Agency Management System

Only available on StudyMode
  • Download(s) : 751
  • Published : March 9, 2013
Open Document
Text Preview
Table of Contents
Table of Contentsii
1.Introduction1
1.1Purpose1
1.2Document Conventions1
1.3Intended Audience and Reading Suggestions1
1.4Product Scope1
1.5References1

2.Overall Description1
2.1Product Perspective1
2.2Product Functions2
2.3User Classes and Characteristics2
2.4Operating Environment2
2.5Design and Implementation Constraints2
2.6User Documentation2
2.7Assumptions and Dependencies2

3.External Interface Requirements3
3.1User Interfaces3
3.2Hardware Interfaces3
3.3Software Interfaces3
3.4Communications Interfaces3

4.System Features3
4.1System Feature 14
4.2System Feature 2 (and so on)4

5.Nonfunctional Requirements4
5.1Performance Requirements4
5.2Safety Requirements4
5.3Security Requirements5
5.4Software Quality Attributes5

6.Project Plan5
6.1Team Members5
6.2Division of Work…………..……………………………………………………………………..5 6.3Time Schedule........................................................................................................................5

Appendix A: Glossary6

Appendix B: To Be Determined List6

Introduction
Purpose
* The purpose of this document is to present a detailed description of the Online Gas Agency Management System. It will explain the purpose of making the manual process easier by making it a computerized system for billing and maintaining stock and the constraints under which it must operate and how the system will react to external stimuli. This document made billing for the customer is simple and easier, since a customer order for gas can be accepted only after completing a certain period from the previous delivery. This can be easily maintained and charged accordingly. The stock of gas and all its details are processed swiftly.

Document Conventions
<Describe any standards or typographical conventions that were followed when writing this SRS, such as fonts or highlighting that have special significance. For example, state whether priorities for higher-level requirements are assumed to be inherited by detailed requirements, or whether every requirement statement is to have its own priority.> Intended Audience and Reading Suggestions

<Describe the different types of reader that the document is intended for, such as developers, project managers, marketing staff, users, testers, and documentation writers. Describe what the rest of this SRS contains and how it is organized. Suggest a sequence for reading the document, beginning with the overview sections and proceeding through the sections that are most pertinent to each reader type.> Product Scope

This software system will be a Gas Agency Management System for a customer need for booking of gas; they come and make a booking for refilling of gas. This system will be designed to get the order request through phone calls or by personal from their customers and deliver the gas cylinders to their address based on their demand and previous delivery date.

References
IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software

Requirements Specifications. IEEE Computer Society, 1998
Overall Description
Product Perspective
<Describe the context and origin of the product being specified in this SRS. For example, state whether this product is a follow-on member of a product family, a replacement for certain existing systems, or a new, self-contained product. If the SRS defines a component of a larger system, relate the requirements of the larger system to the functionality of this software and identify interfaces between the two. A simple diagram that shows the major components of the overall system, subsystem interconnections, and external interfaces can be helpful.> Product Functions

<Summarize the major functions the product must perform or must let the user perform. Details will be provided in Section 3, so only a high level summary (such as a bullet list) is needed...
tracking img