Lp Gas Agency System

1865 Words8 Pages
Table of Contents 1. Introduction 1 2. Problem Statement 1 3. Objectives 2 4. Scope 2 5. Limitations 2 6. Methodology 3 6.1 Data Collection 3 6.1.1 Primary Data Collection 3 6.1.2 Secondary Data Collection 3 6.2 System Requirement Specification (SRS) 3 6.2.1 Functional Requirement 3 6.2.2 Non-Functional Requirement 4 6.3 Feasibility Analysis 4 6.4 Development Model 4 6.5 Hardware and Software Requirements 6 6.5.1 Hardware Requirements 6 6.5.2 Software Requirements 6 6.6 Testing Methods 7 6.6.1 Unit Testing 7 6.6.2 Integration Testing 7 6.6.3 System Testing 7 7. Time Schedule 8 8. Proposed System Overview 9 8.1 System Architecture 9 8.2 Use Case Diagram 10 8.3 E-R Diagram 11 9. Expected Outcome 12 10.…show more content…
6.2.1 Functional Requirement According to the research done, the following aspects have been found out to be the main functional requirements for the system to be developed. * Online consumer registration. * Keep statistical data of brand and number of gas cylinder. * Trace orders and delivery status. * Trace proper payment and return of cylinders. 6.2.2 Non-Functional Requirement * To record paper based details of consumers into database. * To carry out efficient order and delivery. 6.3 Feasibility Analysis The major applications used for the development of this system are Microsoft Visual Studio 2008 and Microsoft SQL Server 2005 which can be used free in Express Editions. So it stands economical in and development operational cost. After using this system, manpower will decrease and efficiency and reliability of the system shall increase its value among the consumers. It will also play a significant role in preserving time that is lost in visiting dealers to order gas or stay in long and boring queue. Hence this system is found to be feasible economically, technically and operationally. 6.4 Development Model The model proposed to be used for the development of the system is the Waterfall Model. The Waterfall Model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the
Get Access