Information Center System Or Ceylon Electricity Board

Published Date: 02 Nov 2017

Today it is crystal clear that the business world changing rapidly with the growth of information technology E-Commerce and Web applications directed the business to new era of doing things on the web since it gains more advantages compare to the old desktop software applications.

Ceylon Electricity Board is a national company which deals with electricity as their main product as well as they provides better service to their customers. Currently their break down reporting system is manual and they keep their records manually.

I am going to provide them a facility to computerize their manual system. I will make their databases in mysql, which they can easily handle their break down time, reporting time, finish time, action to be taken etc.

PHP is the Language for the application development. Although there are number of languages support for database applications but are not flexible as PHP. It can be used just by downloading from Internet. It also provides web based access facility for all users. So there is no installation have to do at client side. We have to type the relevant address at the browser.

When we use web based application, it is also have to install Apachi as the web service. All these applications are freely available at the Internet. Some Software applications provide all these applications combine in to one. WAMP for the application for the windows and LAMP is the application for the Linux operating system. So combination of above mentioned tools made this project user friendly and according to needs of organization.

Tables of Contents

1. Introduction

1.1 Introduction to Ceylon Electricity Board………………………………

1.2 Products………………………………………………………………..

1.3 Objectives of the Company……………………………………………

1.4 Scope of the Project……………………………………………………

1.4.1 Data Security…………………………………………………………

1.4.2 Centerized Database………………………………………………….

1.4.3 User Friendly……………………………………………………… ...

1.4.4 Integration…………………………………………………………….

1.4.5 Technology Aspects…………………………………………………..

1.4.6 Web based GUI……………………………………………………….

2. Analysis…………………………………………………………………….

2.0 Requirement gathering and Existing system…………………………...

2.1 System requirement definition…………………………………………

2.1.1 Functional requirements………………………………………………

2.1.2 Properties that system not exhibit…………………………………….

2.2 Techniques used………………………………………………………..

2.2.1Documentation ……………………………………………………….

2.2.2 Interview……………………………………………………………...

2.3 Existing system functionalities………………………………………..

2.4 Drawback of the existing system………………………………………

2.5 Software process model…………………………………………………

2.5.1 What model should I used ……………………………………………

2.5.2 Waterfall and prototype model………………………………………..

2.5.3 Reasons to used waterfall model………………………………………

2.6 Proposed System……………………………………………………….

2.6.1 Functionalities of proposed system…………………………………….

2.6.2 Advantages of proposed system………………………………………..

2.6.3 Efficiency………………………………………………………………

2.6.4 Accuracy……………………………………………………………….

2.6.5 Cost of the system………………………………………………………

2.7 Feasibility Study…………………………………………………………

2.7.1 Operational feasibility……………………………………………………

2.7.2 Technical feasibility……………………………………………………

2.7.3 Social feasibility………………………………………………………..

2.7.4 Economical…………………………………………………………….

2.7.5 Cost Evaluation…………………………………………………………..

2.7.5.1 Hardware Cost……………………………………………………….

5.2.5.2 Development Cost……………………………………………………

5.2.5.3 Installation Cost………………………………………………………

5.2.5.4 Personnel Cost……………………………………………………….

5.2.5.6 Operating Cost……………………………………………………….

5.3 Other Requirements

5.3.1 Hardware requirements

5.3.2 Software requirements

Chapter 6 Risk Management

6.1. What is Risk

6.1.1 Planning Risk

6.1.2 Requirement Risk

6.1.3 Technical Risk

6.2 Major Risk

6.2.1 Product Size Risk

6.2.2 Customer related Risk

6.2.3 Process Risk

6.2.4 Technology Risk

6.3 Risk mitigation plan

Chapter 7 Project Scheduling

7.1 Work break down structure

7.2 Grant Chart

Chapter 8 Design And Analysis

8.1 Database Design

8.2 Normalization

First

Second

Third

8.3 Normalised Table

8.4 Functional Requirements

Login and access support

User session and Status support

Validation control system

8.5 Database Management system

Reporting system

Network support

8.6 Non Requirements

Security Requirements

Performance Requirements

Software Requirements

8.7 Software Requirement for clients

Quality Attributes

Implementation

User Documentation

8.8 E-R Diagrams

Data flow diagrams

Level 0

Level 1

Level 2

8.9 Data Dictionary

8.10 Process

8.11 Software Design

8.12 Modeling UML

8.13 Use Case Diagrams

8.14 Class Diagrams

8.15 Sequence Diagrams

8.16 Collaboration Diagrams

8.17 State Diagrams

Chapter 9 Input Design

9.1 Login Form

9.2 Main Form

9.3 Search Form

Chapter 10 Implementation and Testing

10.1 Implementation View

10.2 Purpose of Implementation

10.3 Implementation Model

Steps in Implementation

Steps in Maintenance

10.4 System testing

Testing objectives

Type of testing

10.5 Black Box Testing

Advantages

Disadvantages

10.6 White Box Testing