oneline gas service report
Post on 02-Jun-2018
225 Views
Preview:
TRANSCRIPT
-
8/10/2019 ONELINE GAS SERVICE REPORT
1/77
A PROJECT SYNOPSIS ON
ONLINE GAS SERVICES
Submitted in partial fulfilment of the requirements for the award of the degree of
Bachelor of Computer Applications
To
GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY, DELHI
Submitted To : Submitted By:MS. ITI BATRA ISHA BANSAL(Assistant Professor,
BCA DEPT.) 03424302012
AKANKSHA RAJPUT
04624302012
5th
SEM (E)(2012-2015)
SIRIFORT COLLEGE OF COMPUTER TECHNOLOGY & MANAGEMENT8, Institutional Area, Sector-25,New Delhi -110085
-
8/10/2019 ONELINE GAS SERVICE REPORT
2/77
CERTIFICATE
I, IshaBansal&Enrollment no. 03824302012 student of BCA 5th
semester batch (2012-15) certify that the
Minor Project Report/DissertationentitledONLINE GAS SERVICES is done by me and it is an authentic
work carried out by me at NIIT,Pitampura. The matter embodied in this project work has not been
submitted earlier for the award of any degree or diploma to the best of my knowledge and belief.
IshaBansal
(NAME OF STUDENT)
Date:
Certified that the Project Report/Dissertation entitled ONLINE GAS SERVICES done by Student
IshaBansal&Enrollment no. 03824302012 is completed under my guidance.
Signature of the Guide: DATE:
Name of the Guide: - Mrs. ItiBatra
(Asst. Professor)
Countersigned
Director
-
8/10/2019 ONELINE GAS SERVICE REPORT
3/77
ACKNOWLEDGEMENT
Inspiration and hard work plays a key role in the success of any venture. At the level of practice, it is often
difficult to get knowledge without guidance, project is like bridge between the theoretical and practical.
With this willing we joined this project.
I express my sincere gratitude to my BCA Course Coordinator, Mrs. ItiBatra (Assistant
Professor)and also my project guide, for giving me the opportunity to prepare the project under his
guidance and supervision.
This report conveys my heartiest really grateful thanks to Mr. Sarthak Sharma sirwho has given
their valuable time for giving information about the project and their experience and their active support,
whole hearted guidance, sincere cooperation and pains-taking involvement during the study and in
completing the assignment of preparing the said project within the time stimulated. Their guidance helped
me in completion of this project.
It is a great sense of satisfaction and a matter of privilege for me to work at NIIT. I wish to express
my heartiest thanks to NIIT for providing me the opportunity to undergo training in the esteemed
organization. Under such a nice environment, systematic work approach and target oriented task
management of this division provided me with the much-desired training experience needed for future
software professional.
Finally, thanks to Mrs. ItiBatra (Assistant Professor ) and Mr. Sarthak Sharmasirsuffice it to say that not
only I have learned an immense amount of Asp.net/C# from him, but his general guidance on so many
things helped me over many difficult spot during this project.
IshaBansal
Enrollment No : 03824302012
(BCA 5th
SEM)
(SESSION 2012-15)
-
8/10/2019 ONELINE GAS SERVICE REPORT
4/77
Abstract
Online Gas Services provide the connection of new gas refill. And it also exchange the full refill
instead of empty refill. It includes facilities and services like free home delivry, complaints, order
status, confirmation messages, customer to customer interaction, etc.
You just have to write your consumer id and mobile no. , and on the click of button you are
provided with multiple option of gas services, from them you can easily choose refill booking. It
can be delivered shortly at your home. Now, you dont have to wait for weeks for your cylinder.
Also you dont have to worry about that whether the cylinder is booked or not, because when
cylinder is booked you receive a confirmation message on your mobile and when it has to be
delivered you again get a confirmation message on your mobile. After delivery of cylinder a
message received on user or customers mobile for confirming that cylinder is delivered to your
residence.
Customer can write complaints and feedback regarding the website and its services and also
checks order status of their cylinder.
-
8/10/2019 ONELINE GAS SERVICE REPORT
5/77
Revision History
Version Name Reason for change Date sign
-
8/10/2019 ONELINE GAS SERVICE REPORT
6/77
-
8/10/2019 ONELINE GAS SERVICE REPORT
7/77
-
8/10/2019 ONELINE GAS SERVICE REPORT
8/77
CHAPTER-1
Synopsis
-
8/10/2019 ONELINE GAS SERVICE REPORT
9/77
Introduction
The system shows us the work of the gas agency. It provides the connection of new gas refill. And
it also exchanges the full refill instead of empty refill. For that it needs all information of customer.
For that it has to provide some information. The existing system has all the information present in
written data. It collect customer, stock, booking information. The information is very useful for the
system to work on it, but all this information is present in record book and operations like add and
delete records is difficult to perform daily, as record changes daily. It is very time consuming and
searching record of any person is also very difficult.
So, in order to reduce paper work, man power and to speed up the system we introduce an
online gas system that will keep the records of customers and vendors.The customer information
having such information like customer name, customer address, phone no or the other contact
number and it also give one id as a customer id or consumer id. By that the data can enter. In that
we refer that customer have how many refill, when it issue, etc. The other information is about
stock information in which we have the information of the stock related item which is stored in
vendors database. By that we canknow how many things we have?, How many given?, etc. The
stock is also very important. The last information that we collect is the booking. In that we collect
the information of the booking statements. That customer name, when it orders for another refill,etc.
-
8/10/2019 ONELINE GAS SERVICE REPORT
10/77
ONLINE
GAS
SERVICES
-
8/10/2019 ONELINE GAS SERVICE REPORT
11/77
Objectives
Creating some more facility and remove the current systems problem.
Basic operation like addition and deletion can be done easily by the new system. It have
such easy key and some more facility which can work and operate quickly and save easily.
If we want to check some history of customer or anything else, we can check easily. So, the
work is such accurate.
It have the facility of the password for admin and vendors and consumer id for customers
that help for the security. That can save the document. It make the high security.
It have different module for everything like booking, complaint, etc. which is easy to use
and understand. By the distribution it can done properly and so easily.
Very efficient and Time Saving.
-
8/10/2019 ONELINE GAS SERVICE REPORT
12/77
-
8/10/2019 ONELINE GAS SERVICE REPORT
13/77
Conclusion
Convenience for 24 x 7 on all 365 days.
No extra charges for delivery.
Option of Languages.
Receive Confirmation of Booking and Delivery through SMS.
Separate login for both admin and vendor and also a separate consumer id for customers.
Easy to use.
Have different modules for all information.
Services present in all over India.
-
8/10/2019 ONELINE GAS SERVICE REPORT
14/77
Achievement till day
S. No. Module Date
1 Information Gathering 09/08/2014
2 Analyze Data 19/08/2014
3 Synopsis 25/08/2014
-
8/10/2019 ONELINE GAS SERVICE REPORT
15/77
Remaining Work
S. No. Module
1 Database
2 Software Requirement Specification (SRS)
3 Feasibility Report
4 Software Design Specification
-
8/10/2019 ONELINE GAS SERVICE REPORT
16/77
ONLINE GAS SERVICES
Online Gas Services has been chosen as the title of our Asp.net/c# website because it includes all
the online gas services like gas booking, complaint, etc.
It is a managed system as every process have different table. It includes all online facilities
for gas booking. It have all necessary modules like providing new connection, refill booking,
complaint, etc.
This website helps customers as well as distributors in interacting with each other directly and also
they can store their details so that they can easily put an eye on their activity.
-
8/10/2019 ONELINE GAS SERVICE REPORT
17/77
-
8/10/2019 ONELINE GAS SERVICE REPORT
18/77
1. Introduction
1.1 Purpose
The Online Gas System web application is intended to provide complete solutions for vendors as
well as customers through a single get way using the internet as the sole medium. It will enable
customer to book refill online without having to visit the vendors shop physically. The
administration module will enable a system administrator to modify in the vendors details and
modify in the website to provide new features to the customer.This document is meant to delineate the features of Online Gas System so as to serve as a guide to
the developers on one hand and a software validation document for the prospective client on the
other.
1.2 Document Conventions
Capital letters define the main section or function of the project, bold letters define the special
functionality of quiz, and the highlighted portions define the projects main parts.
1.3 Intended Audience and Reading Suggestions
This Project will be accessed by the users who want to book cylinders online and also for the
vendors who provide facilities to customers online.
1.4 Project Scope
The main intend of this SRS is to provide a simple description to the gas system authorities & system users, about
the behavior of the system. And the entire package is consisting of below parts.
System softwareThe system will contains a database in order to store all details about the customer aswell as vendors.
Software documentationA complete document about the software will be given to the gas systemadministration in order to future maintenance of the system.
Operation ManualA user manual is provided to the system administrator with some simple explanationsabout the system and its features.
User ManualWhen the customer submits his/her details through internet a simple guidance also givento the customer.
2. Overall Description
2.1 Product Perspective
Online Gas System is aimed towards the common people who can be potential customer. This
project envisages bridging the gap between the vendor and the customer. Online Gas System should
be user-friendly, quick to learn and reliable software for the above purpose. Online Gas System isintended to be a stand-alone product and should not depend on the availability of other software. It
should run on both UNIX and Windows based platform.
-
8/10/2019 ONELINE GAS SERVICE REPORT
19/77
2.2 Product Features
It specifies the external system behaviours.
It specifies constraints on the implementation.
It is easy to change. It serves as reference tool for system maintainers.
It record forethought about the life cycle of the system.
It characterizes acceptable response to undesired events.
2.3 User Classes and Characteristics
A wide range of user classes is anticipated.
2.4 Operating Environment
2.5 Design and Implementation Constraints
GUI is only in English.
Customer can only use this application if and only if they have internet connection and have valid
username and password.
2.6 User Documentation
HARDWARE REQUIREMENT
Processor RAM Disk Space
Pentium IV or higher 512 MB or Higher 50MB or more
Software Requirements
Operating System Database
Window XP or higher Microsoft SQL Server 2010
-
8/10/2019 ONELINE GAS SERVICE REPORT
20/77
2.7 Assumptions and Dependencies
These may concern such issues as:
The details related to the product, customer and service transaction provided manually.
Administrator is created in the system already.
Roles and tasks are predefined.
3. System Features
This illustrates organizing the functional requirements for the product by system features, the majorservices provided by the product. There are four main features of the program and all of these are of
prime concern hence each feature have a high and equal priority.
3.1 System Feature 1
3.3.1.1 Description and PriorityThis feature provides Admin to handle every details in the database.
3.3.1.2 Stimulus/Response Sequences
Admin has permission to grant or revoke permission or to add or delete any user.
3.3.1.3 Functional Requirements
REQ-1: Visual Studio 2012REQ-2: SQL Server 2010REQ-3: web browser
3.2 System Feature
The main objective of the proposed system is to design a proper computerized system tokeep track of the all information.
Eliminate the use of register to maintain information.
To save the cost of readymade software.
Design a System that is user friendly and easily operated. Reduce manual labor and human error
4. External Interface Requirements
4.1 User Interfaces
Home PageIt will show the various destination and places in India also shows the description about the place.
-
8/10/2019 ONELINE GAS SERVICE REPORT
21/77
4.2 Hardware Interfaces
4.3 Software Interfaces
4.4 Communications Interfaces
User can connect with the site by internet connection and get the access of package information andother updated information.
HARDWARE REQUIREMENT
Processor RAM Disk Space
Pentium IV or higher 512 MB or higher 50 MB or more
Software Requirements
Operating System Database
Window XP or higher Microsoft SQL Server 2010
-
8/10/2019 ONELINE GAS SERVICE REPORT
22/77
5. Other Nonfunctional Requirements
5.1 Performance Requirements
No such performance requirement is there but while running this project keep some fact in mindthat facts are as follows
One must check the resolution before starting the project.
You can run the project on any system having Windows XP/7/8.
Your system should have minimum 512MB RAM
5.2 Safety Requirements
The product is designed in Asp.net and c#, any loss of a file from the folders can lead to
complete breakdown of the whole application .So, there is need to provide the authenticity for all
the clients that are required to access the application and you have to take care that ambiguity
will not arise in resource folder of the project.
5.3 Security Requirements
There is a need to provide protection or security to the data used or created by the product. As
the data stored in the local files is ordinary data, one can find it in the system. User identity
authentication is introduced in the product and in future, it is implemented in the project.
5.4 Software Quality Attributes
Planned approach towards working, reliability, no redundancy, and immediate retrieval ofinformation.
6. Other Requirements
A regular maintenance is needed for smooth and efficient performance of the software. To dothis the software should be monitored at regular interval of time. If any fault will be noticed, it
should be reported immediately.
-
8/10/2019 ONELINE GAS SERVICE REPORT
23/77
Appendix A: Glossary
Online Gas Services - The name of the web based gas booking system.
Database -Consist of all information related to customers & vendors.
LoginThe process which is related to logging into the system.
PasswordA set of characters which can be used to correctly identify the exact personwho is log intothe system.
GUI- Graphical User Interface
-
8/10/2019 ONELINE GAS SERVICE REPORT
24/77
Appendix B: Analysis Models
ER Diagram
conum
Customer
DistributorId
distributor
from
to
Id
fname
lname
dob
pname
dismname
aproof
proof
email
add
pin
mob
tel
conum
give
books
give
Admin
idadmin id
View
Feedbackrespon
Cylinder booking
conum
mob
date
Payment
Payment made
Date of booking
conum
refrence
-
8/10/2019 ONELINE GAS SERVICE REPORT
25/77
-
8/10/2019 ONELINE GAS SERVICE REPORT
26/77
LEVEL 1 DFD
-
8/10/2019 ONELINE GAS SERVICE REPORT
27/77
LEVEL 2 FOR VENDOR
Booking
Status
2.8.1
Vendor
Complaints
2.8.2
Vendors
Request
Retrieve
Request
Retrieve
-
8/10/2019 ONELINE GAS SERVICE REPORT
28/77
LEVEL 2 FOR ADMIN
Admin
Delete Details
2.11.2
User Details
Request
User Added
Request
User Deleted
Add Details
2.11.1
-
8/10/2019 ONELINE GAS SERVICE REPORT
29/77
Appendix C: Issues List
The current system is in every way ineffective for procedure solutions in these days when timeis more costly than anything and they also pose a threat to the environment when we are amidst
a global crisis and in the need of a Green Revolution.
Multi login crisis.
-
8/10/2019 ONELINE GAS SERVICE REPORT
30/77
CHAPTER-3
Software Design
Specification
-
8/10/2019 ONELINE GAS SERVICE REPORT
31/77
3.1 Document Outline
Introduction
System Overview
Design Considerations
o Assumptions and Dependencies
o General Constraints
o Goals and Guidelines
o Development Methods
Architectural Strategies
o Use of a particular type of product (programming language, database, library, etc. ...)
o Reuse of existing software components to implement various parts/features of thesystem
o Future plans for extending or enhancing the software
o User interface paradigms (or system input and output models)
o Hardware and/or software interface paradigms
o Error detection and recovery
o Memory management policies
o External databases and/or data storage management and persistence
o Distributed data or control over a network
o Generalized approaches to control
o Concurrency and synchronization
o Communication mechanisms
o Management of other resources
System Architecture
o component-1 name or description
o component-2 name or description
o ...
Policies and Tactics
o Choice of which specific product to use (compiler, interpreter, database, library, etc. ...)
o Engineering trade-offs
o Coding guidelines and conventions
o The protocol of one or more subsystems, modules, or subroutines
o The choice of a particular algorithm or programming idiom (or design pattern) to
implement portions of the system's functionality
o Plans for ensuring requirements traceability
o Plans for testing the software
o Plans for maintaining the software
o Interfaces for end-users, software, hardware, and communications
-
8/10/2019 ONELINE GAS SERVICE REPORT
32/77
o Hierarchical organization of the source code into its physical components (files anddirectories).
o How to build and/or generate the system's deliverables (how to compile, link, load, etc....)
Detailed System Design
o Black Box Design
o White Box Design
o Database Design
Glossary
Bibliography
3.2 Document DescriptionHere is the description of the contents (by section and subsection) of the proposed template for
software design specifications:
3.2.1 Introduction
Provide an overview of the entire document:
Definitions, important terms, acronyms, or abbreviations
GUI (Graphical User Interface) - a visually based application that serves to provide
an interactive medium between the user and the application.
SRS (Software Requirement Specification) - Software Requirements Specification
- the explicit requirements definition used to maintain product consistency during
the development process
DFD - Data Flow Diagram
Website - A hierarchy of linked HTML-encoded text files that display on a web
browser as a series of related text pages with embedded graphics and controls
Summarize (or an abstract)
Section 2.0 introduces the project. Section 3.0 provides an abstract view of the system
architecture, including the components, structure and relationships, and user interfaces.
Section 4.0 describes each of these components in more detail, including design and
architectural decisions. Section 5.0 explores the relationships to other products. Section 6.0discusses design decisions, tradeoffs, and the reasoning behind these decisions. Section 7.0
is reserved for policies and tactics. It also discusses design patterns that can be applied.
Section 8.0 has detailed diagrams. It has both black box model and white box model.
Section 9.0 has source code details. It has filename and sloclist.Section 10.0 has output
details. It has output of every page. Section 11.0 has glossary details. Section 12.0 have
bibliography details.
-
8/10/2019 ONELINE GAS SERVICE REPORT
33/77
3.2.2 System Overview
Module Description
Customer
Registration
Form
Customer Login
Form
Booking Form
Complaint
Form
Feedback Form
Cancel Request
Form
Admin Form
Vendor Form
4. Design ConsiderationsThis section describes many of the issues which need to be addressed or resolved before attempting
to devise a complete design solution.
4.1 Assumptions and DependenciesDescribe any assumptions or dependencies regarding the software and its use. These may concern
such issues as:
Related software or hardware
This program will be coded in Visual Studio 2012. We will be using Visual basic and SQLServer 2010 for databases. Preferred operating system is Windows 7 server.
Operating systems
Uses Windows XP/7 as operating system with Pentium IV/higher processor.
RAM needed 512 MB and disk space needed 50 MB.
End-user characteristics
-
8/10/2019 ONELINE GAS SERVICE REPORT
34/77
Customer - The users for Online Gas Services.
Network - The LAN that exists between the two machines that will be involved in
this system.
AdministratorOne of the users of the Online Gas System. This user manages thecontent of the website.
Internet - The internet connection of the users machine to be ableto use Online
Gas Services.
Possible and/or probable changes in functionality
None
4.2 General Constraints
Describe any global limitations or constraints that have a significant impact on the design of the
system's software (and describe the associated impact). Such constraints may be imposed by any of
the following (the list is not exhaustive):
Hardware or software environment
There is a web server requirement. Windows XP/7 is the preferred operating system. ASP
.Net 3.5 Framework needs to be installed.
End-user environment
Administrator, customer and vendor should have network and internet connectivity. Theywill need to login with their user credentials to be able to use Online Gas Services.
Availability or volatility of resources
This depends on the network and internet connection. Booking of cylinders will be donevia online. Stability and availability can be measured with the number of failures on the
internet connection.
Standards compliance
None
Interoperability requirements
None
Interface/protocol requirements
Network connectivity and TPC/IP support are required.
Data repository and distribution requirements
Data will be stored in the database and Web services will be used to store the encrypted
data. Stored processes will be used in some functions. By doing all the connections viastored processes can limit the access to the databases to the stored process level.
-
8/10/2019 ONELINE GAS SERVICE REPORT
35/77
Security requirements (or other such regulations)
It is important to have a secure web site, user credentials and secure web servers hosting
Web services and online forms.
Memory and other capacity limitations
50MB HD space is required.
Performance requirements
No internal failures are acceptable. The only known and accepted failures are from the
network or Internet connection that is providing the communication between the two
machines.
Network communications
Network should be up all the time as part of the functionality is to be able to use Online
gas services tool on the network or internet. Verification and validation requirements (testing)
Two machines on the same network are required to be able to test and verify the network
and internet functionality.
Other means of addressing quality goals
None
Other requirements described in the requirements specification
Design Constraints
None
Purchased Components
None
Interfaces
User Interfaces
Online application and user interface will be designed with APS .Net tools
available.
Hardware Interfaces
Web Server needs to be installed and configured.
Software Interfaces
-
8/10/2019 ONELINE GAS SERVICE REPORT
36/77
SQL Server 2010 is required for the databases.
Communications Interfaces
User can connect with the site by internet connection and get the access of booking
information and other updated information.
Licensing Requirements
Licensing requirements are the same as the licensing requirements for a Visual
Studio 2012 and SQL Server 2010.
Legal, Copyright, and Other Notices
None.
Applicable Standards
None.
4.3 Goals and Guidelines
Goals might be:
Faster speed and efficient utilization of memory
Working, looking, or "feeling" like an OGS have some extra features to enhance the system.
4.5 Development Methods
The basic idea here is that instead of freezing the requirements before a design or coding
can proceed, a throwaway prototype is built to understand the requirements. This prototype
is developed based on the currently known requirements. By using this prototype, the client
can get an actual feel of the system, since the interactions with prototype can enable the
client to better understand the requirements of the desired system. Prototyping is an
attractive idea for complicated and large systems for which there is no manual process or
existing system to help determining the requirements. The prototype are usually not
complete systems and many of the details are not built in the prototype. The goal is to
provide a system with overall functionality.
-
8/10/2019 ONELINE GAS SERVICE REPORT
37/77
Diagram of Prototype model:
Advantages of Prototype model:
Users are actively involved in the development
Since in this methodology a working model of the system is provided, the users get a
better understanding of the system being developed.
Errors can be detected much earlier.
Quicker user feedback is available leading to better solutions.
Missing functionality can be identified easily
Confusing or difficult functions can be identified
Requirements validation, Quick implementation of, incomplete, butfunctional, application.
Disadvantages of Prototype model:
Leads to implementing and then repairing way of building systems.
Practically, this methodology may increase the complexity of the system as scope of
the system may expand beyond original plans.
Incomplete application may cause application not to be used as the
full system was designed
Incomplete or inadequate problem analysis.
When to use Prototype model:
Prototype model should be used when the desired system needs to have a lot of
interaction with the end users.
http://istqbexamcertification.com/wp-content/uploads/2012/01/Prototype-model.jpg -
8/10/2019 ONELINE GAS SERVICE REPORT
38/77
Typically, online systems, web interfaces have a very high amount of interaction with
end users, are best suited for Prototype model. It might take a while for a system to be
built that allows ease of use and needs minimal training for the end user.
Prototyping ensures that the end users constantly work with the system and provide a
feedback which is incorporated in the prototype to result in a useable system. They are
excellent for designing good human computer interface systems.
5. Architectural Strategies Use of a particular type of product (programming language, database, library, etc. ...)
There will be database involved in this system. SQL Server 2010 will be required. Visual
studio 2012 Visual Basic ASP .Net environment will be used for building the system.
Reuse of existing software components to implement various parts/features of the system
For additional features re-use of the forms is possible.
Future plans for extending or enhancing the software
This OGS system is a basic prototype. More additional features can be added if needed.
User interface paradigms (or system input and output models)
Administrators will be able to provide some extra features in the website. Customer will beable to login and book cylinder, complaint and feedback.
Hardware and/or software interface paradigms
None
Error detection and recovery
Error detection and recovery will be done. To be able to separate error-handling code from
the regular code, we will add exception errors in the code.
Memory management policies
Not required. However Sessions will be used to be able to pass the data from one form to
another. This is for transferring data in ASP .Net environment.
External databases and/or data storage management and persistence
None
Distributed data or control over a network
-
8/10/2019 ONELINE GAS SERVICE REPORT
39/77
None
Generalized approaches to control
None
Concurrency and synchronization
None
Communication mechanisms
TCP/IP network communication is required as this application involves network and
internet connectivity to connect to the OGS tool.
Management of other resources
The only additional resource that needs to be managed is the internet and network
resources. The connectivity of the network and internet need to be checked frequently and
throw error messages if there is any connection problem.
-
8/10/2019 ONELINE GAS SERVICE REPORT
40/77
6. System Architecture
About System Architecture
In this section high-level overview of how the functionality and responsibilities of the system
were partitioned and then assigned to subsystems or components are provided. Detail about
the individual components themselves will be discussed in the detailed design part of this
document.
6.1 Architecture Design
ERD (Entity Relationship Diagram)
The object relationship pair can be graphically represented by a diagram called Entity-
Relationship Diagram. It is mainly used in database applications but now it is more
commonly used in data design. The primary purpose of ERD is to represent the relationship
between data objects. Its diagrammatical representation is shown in the report above.
Various components of ERD are:
1. Entity
2. Relationship
3. Attribute
.
DFD (DATA FLOW DIAGRAM)
Data Flow Diagram is one of the Functional Model which are used to represent the
flow of information in any computer based system. Three Generic Functionalities:1. Input
2. Process
3. Output
The data flow diagram depicts the information flow and the transforms that are applied
on the data as it moves from input to output.Its diagrammatical representation is shown in
the report above.
7. Policies and Tactics
Describe any design policies and/or tactics that do not have sweeping architectural implications(meaning they would not significantly affect the overall organization of the system and its high-level
structures), but which nonetheless affect the details of the interface and/or implementation of various
aspects of the system. Such decisions might concern (but are not limited to) things like the following:
Choice of which specific product to use (compiler, interpreter, database, library, etc. ...)
It will be coded in ASP .Net Framework 3.5 with Visual Basic. Visual Studio 2012 will berequired to compile.
-
8/10/2019 ONELINE GAS SERVICE REPORT
41/77
Engineering trade-offs
None.
Coding guidelines and conventions
Design Patterns will be used in the development. Visitor and State Desing patterns will be
applied on some of the modules.
The protocol of one or more subsystems, modules, or subroutines
TCP/IP network communication needs to be established for network module design. It will
be an online application where internet connection will be required.
The choice of a particular algorithm or programming idiom (or design pattern) to implement
portions of the system's functionality
Visitor and State Desing patterns will be applied on some of the modules. Strategy desing
pattern can also be used.
Plans for ensuring requirements traceability
SRS document was provided and all the requirements specified in the document have been
applied in the design. Also use cases are created to make sure that all the functionality willbe defined in the functions according to the requirements.
Plans for testing the software
All the feature set and needed requirements need to be tested with the scenarios created.An additional test document will be provided.
Plans for maintaining the software
Every Quarter bugs will be reviewed. Any reported problems will be fixed. This document
will need to be updated if there are any new additional requirements involved.
Interfaces for end-users, software, hardware, and communications
Online Gas Services system will require end-users to have internet access, user logincredentials, PC and a browser.
Hierarchical organization of the source code into its physical components (files and directories).
How to build and/or generate the system's deliverables (how to compile, link, load, etc. ...)
Program will be compiled from the development machine and placed into the web server.
Visual Studio 2012, SQL Server 2010 are the two main server application required to be
able to run this web site.
-
8/10/2019 ONELINE GAS SERVICE REPORT
42/77
8. Detailed System DesignMost components described in the System Architecture section will require a more detailed discussion.
Other lower-level components and subcomponents may need to be described as well. Each subsection
of this section will refer to or contain a detailed description of a system software component. The
discussion provided should cover the following software component attributes:
8.1 Classification
The kind of component, such as a subsystem, module, class, package, function, file, etc.
8.2 Definition
The specific purpose and semantic meaning of the component. This may need to refer back to the
requirements specification.
8.3 Responsibilities
The primary responsibilities and/or behavior of the forms are:
Customer Registration Form: This is the Registration form. Customer fill his/her information in
this form. After filling , a unique consumer is generated which is further used by customer for
login.
Customer Login Form: This is the login form. Login credentials will be provided by the
Administrator. According to the login credentials users will be connected to the Booking,
feedback and complaint pages.
Booking Form: This form is accessible by customers. They will be able to book cylinders online
through this form.
Feedback Form: This form is accessible by customers. They will be able to give feedback about
the services.
Complaint Form: This form is accessible by customers. They will be able to register their
complaint related to the service.
Cancel Request Form: This form is accessible by customers. They will be able to delete their
online gas account from database.
Admin Form: This form is accessible by Administrator. The Administrator will be able to saw
every table.
Vendor Form: This form is accessible by Vendor. The Vendor will be able to saw only
customers booking and complaint table
8.4 Constraints
There wont be any constraints on completing this project. It will be completed on time.
-
8/10/2019 ONELINE GAS SERVICE REPORT
43/77
8.5 Composition
A description of the use and meaning of the subcomponents that are a part of this component.
8.6 Database Design
The database design specifies how the date of the software is going to be stored.
8.7 Table schemasThe complete (compliable) set of CREATE TABLE statements (and other SQL statements) that declare
the database schema, including integrity constraints, domain specifications, assertions, and access
privileges -- documented in a template with the intended use of each table and column.
Tables:
Admin
Description Information related to the admin
Attribute Description Type Examples of values
Id Id of admin Integer Between 1 and
999999999
admin id Integer Between 1 and
999999999
Primary KeyId
Foreign Keys
SQL Code
Complaints
Description Have all the complaints registered by customer
Attribute Description TypeExamples of values
Conum Consumer no. of
customer
Integer Between 1 and
999999999
Mob Mobile no. of customer Integer Between 1 and
999999999
Compabout Complaints selected by
customer
Varchar 123 or ABC
-
8/10/2019 ONELINE GAS SERVICE REPORT
44/77
Primary KeyConum
Foreign KeysConum
SQL CodeCREATETABLE[dbo].[complaints](
[connum] INTNOTNULL,
[mob] INTNULL,[compabout] VARCHAR (50)NULL,
PRIMARYKEYCLUSTERED ([connum] ASC)
);
cylinderBooking
Description Have information related to the cylinder booking i.e., how manycylinders were booked, on which date they are booked, etc.
Attribute Description TypeExamples of values
Conum Consumer no. of
customer
Integer Between 1 and
999999999
Mob Mobile no. of customer Integer Between 1 and
999999999
Primary KeyConum
Foreign KeysConum
SQL CodeCREATETABLE[dbo].[cylinderBooking](
[connum] INTNOTNULL,
[mob] INTNULL,
PRIMARYKEYCLUSTERED ([connum] ASC)
);
Distributor
Description It have information related to the distributor id, name, etc.
Attribute Description TypeExamples of values
Id Id of distributor or
vendor
Integer Between 1 and
999999999
-
8/10/2019 ONELINE GAS SERVICE REPORT
45/77
Distributor Name of the distributor varchar 123 or ABC
Primary KeyId
Foreign Keys
SQL Code
Feedback
Description Stores feedback given by the customers
Attribute Description TypeExamples of values
Conum Consumer no. of
customer
Integer Between 1 and
999999999
Response Response or feedbackof customer
varchar 123 or ABC
Primary KeyConum
Foreign KeysConum
SQL CodeCREATETABLE[dbo].[feedback](
[connum] INTNOTNULL,
[response] VARCHAR (50)NULL,
PRIMARYKEYCLUSTERED ([connum] ASC)
);
Userdetail
Description Stores Information of the customer
Attribute Description TypeExamples of values
Refill Refill number Integer Between 1 and
999999999
Fname First name of customer varchar 123 or ABC
Lname Last name of customer varchar 123 or ABC
Dob Date of birth of
customer
varchar 123 or ABC
pname Fathers name of varchar 123 or ABC
-
8/10/2019 ONELINE GAS SERVICE REPORT
46/77
customer
Mname Mothers name of
customer
varchar 123 or ABC
Add Address of customer varchar 123 or ABC
Dis District of customer varchar 123 or ABC
Pin Pin no. of city where
customer lives
Integer Between 1 and
999999999
Tel Telephone no. of
customer
Integer Between 1 and
999999999
Mob Mobile no. of customer Integer Between 1 and
999999999
Email Email id of customer varchar 123 or ABC
Proof Identity proof of
customer
varchar 123 or ABC
Aproof Address proof of
customer
Integer Between 1 and
999999999
Connum Consumer no. of
customer
Integer Between 1 and
999999999
Distri Distributor selected by
customer
varchar 123 or ABC
-
8/10/2019 ONELINE GAS SERVICE REPORT
47/77
Primary KeyRefill
Foreign Keys
SQL CodeCREATETABLE[dbo].[userdetail](
[refill] INTIDENTITY (111,1)NOTNULL,
[fname] VARCHAR (50)NULL,[lname] VARCHAR (50)NULL,[dob] VARCHAR (50)NULL,
[pname] VARCHAR (50)NULL,
[mname] VARCHAR (50)NULL,[add] VARCHAR (50)NULL,
[dis] VARCHAR (50)NULL,[pin] INTNULL,
[tel] INTNULL,[mob] INTNULL,[email] VARCHAR (50)NULL,
[proof] VARCHAR (50)NULL,[aproof] INTNULL,
[connum] INTNOTNULL,[distri] VARCHAR (50)NULL,
PRIMARYKEYCLUSTERED ([refill] ASC));
Vendor
Description Information About the vendor
Attribute Description TypeExamples of values
distributor Information about the
distributor
String John
Primary KeyNone
Foreign KeysNone
SQL Code
Tables data:
The tables have to be populated by you and your client. Each table must contain an appropriate
number of data. The contents of the tables have to be provided (in an organized way.)
-
8/10/2019 ONELINE GAS SERVICE REPORT
48/77
SQL queries:
User Detail:
CREATETABLE[dbo].[userdetail]([refill] INTIDENTITY (111,1)NOTNULL,
[fname] VARCHAR (50)NULL,[lname] VARCHAR (50)NULL,[dob] VARCHAR (50)NULL,
[pname] VARCHAR (50)NULL,[mname] VARCHAR (50)NULL,
[add] VARCHAR (50)NULL,[dis] VARCHAR (50)NULL,
[pin] INTNULL,[tel] INTNULL,[mob] INTNULL,
[email] VARCHAR (50)NULL,[proof] VARCHAR (50)NULL,[aproof] INTNULL,[connum] INTNOTNULL,
[distri] VARCHAR (50)NULL,PRIMARYKEYCLUSTERED ([refill] ASC));
Cylinder Booking:
CREATETABLE[dbo].[cylinderBooking](
[connum] INTNOTNULL,
[mob] INTNULL,
PRIMARYKEYCLUSTERED ([connum] ASC)
);
Feedback:
CREATETABLE[dbo].[feedback](
[connum] INTNOTNULL,
[response] VARCHAR (50)NULL,
PRIMARYKEYCLUSTERED ([connum] ASC)
);
Complaints:
CREATETABLE[dbo].[complaints](
[connum] INTNOTNULL,
[mob] INTNULL,
[compabout] VARCHAR (50)NULL,
-
8/10/2019 ONELINE GAS SERVICE REPORT
49/77
PRIMARYKEYCLUSTERED ([connum] ASC)
);
Transactions implementation:
For implementation we are using ACID (atomicity, consistency, isolation and durability) properties of
transactions (programs that access databases.)
Graphical User Interface
Provide, in an organized way, the pictures of all the forms in the graphical user interface with
a reference to the functional requirement it implements. You may use html to present the
graphical user interfaces.
For each form in the graphical user interface, provide:
o The names of the controls and fields on that form,
o The names of the events, methods, or procedures that cause that form to be
displayed, and
o The names of the events, methods, or procedures triggered by each control.
8.8 Class Diagrams and Classes
Provide a class diagram and an inheritance tree/diagram.
Each method has to be defined1:
1. Method Name
2. Parameters, each documented with its intended use3. Return Value, suitably documented
4. Informal description of what the procedure does
5. Data structure and tables it accesses
6. Pre-conditions: Assumptions the method can make about the state of the global data
structures and database when it starts
7. Validity Checks, Errors, and other Anomalous Situations: Validity checks the method must
make about the state of the global data structures, the database, and its parameters,
including the actions that must be taken when such a check fails.
8. Post-conditions: The changes the method is supposed to make to the global data structures
and database.
9. Called by: The methods or events that call it
10.Calls: The methods it calls and any events it causes.
8.9 Uses/Interactions
A description of this components collaborations with other components. What other components is
this entity used by? What other components does this entity use (this would include any side-effects
-
8/10/2019 ONELINE GAS SERVICE REPORT
50/77
this entity might have on other parts of the system)? This concerns the method of interaction as well
as the interaction itself. Object-oriented designs should include a description of any known or
anticipated subclasses, superclasses, and metaclasses.
8.10 Resources
A description of any and all resources that are managed, affected, or needed by this entity. Resourcesare entities external to the design such as memory, processors, printers, databases, or a software
library. This should include a discussion of any possible race conditions and/or deadlock situations,
and how they might be resolved.
8.11 ProcessingA description of precisely how this component goes about performing the duties necessary to fulfill its
responsibilities. This should encompass a description of any algorithms used; changes of state;
relevant time or space complexity; concurrency; methods of creation, initialization, and cleanup; and
handling of exceptional conditions.
8.12 Interface/Exports
The set of services (resources, data, types, constants, subroutines, and exceptions) that are provided
by this component. The precise definition or declaration of each such element should be present, along
with comments or annotations describing the meanings of values, parameters, etc. .... For each
service element described, include (or provide a reference) in its discussion a description of its
important software component attributes (Classification, Definition, Responsibilities, Constraints,
Composition, Uses, Resources, Processing, and Interface).
Much of the information that appears in this section is not necessarily expected to be kept separate
from the source code. In fact, much of the information can be gleaned from the source itself
(especially if it is adequately commented). This section should not copy or reproduce information that
can be easily obtained from reading the source code (this would be an unwanted and unnecessary
duplication of effort and would be very difficult to keep up-to-date). It is recommended that most of
this information be contained in the source (with appropriate comments for each component,subsystem, module, and subroutine). Hence, it is expected that this section will largely consist of
references to or excerpts of annotated diagrams and source code. Any referenced diagrams or source
code excerpts should be provided at any design reviews.
8.13 Detailed Subsystem DesignProvide a detailed description of this software component (or a reference to such a description).
Complex diagrams showing the details of component structure, behavior, or information/control flow
may be included in the subsection devoted to that particular component (although, unless they are
very large or complex, some of these diagrams might be more appropriately included in the System
Architecture section. The description should cover any applicable software component attributes (some
of which may be adequately described solely by a source code declaration or excerpt).
-
8/10/2019 ONELINE GAS SERVICE REPORT
51/77
9. Source Code Details
S.No Filename SLOC
1. a.aspx 11
2. a.aspx.cs 39
3. a1.aspx 16
4. a1.aspx.cs 14
5. Auto LPG.aspx 58
6. Auto LPG.aspx.cs 14
7. b.aspx 8
8. b.aspx.cs 14
9. bharat metal cutting.aspx 81
10. bharat metal cutting.aspx.cs 14
11. bharatgas emergency service cell.aspx 22
12. bharatgas emergency service cell.aspx.cs 14
13. central delhi.aspx 75
14. central delhi.aspx.cs 14
15. change of distributor.aspx 321
16. change of distributor.aspx.cs 14
17. citizencorner.aspx 76
18. citizencorner.aspx.cs 14
19. complaint.aspx 34
20. complaint.aspx.cs 64
21. complaint1.aspx 8
22. complaint1.aspx.cs 14
-
8/10/2019 ONELINE GAS SERVICE REPORT
52/77
23. customer first.aspx 103
24. customer first.aspx.cs 14
25. cylinder booking.aspx 55
26. cylinder booking.aspx.cs 66
27. cylinderbooking1.aspx 8
28. cylinderbooking1.aspx.cs 14
29. delhi new delhi.aspx 43
30. delhi new delhi.aspx.cs 14
31. delhi north east.aspx 59
32. delhi north east.aspx.cs 14
33. delhi north west.aspx 91
34. delhi north west.aspx.cs 14
35. distributor appointment.aspx 62
36. distributor appointment.aspx.cs 14
37. distributor locator.aspx 50
38. distributor locator.aspx.cs 51
39. east delhi.aspx 99
40. east delhi.aspx.cs 14
41. eo_web.ashx 1
42. feedback.aspx 14
43. feedback.aspx.cs 14
44. feedback1.aspx 46
45. feedback1.aspx.cs 63
46. home.aspx 12
-
8/10/2019 ONELINE GAS SERVICE REPORT
53/77
47. home.aspx.cs 35
48. IVRs services.aspx 208
49. IVRs services.aspx.cs 14
50. login.aspx 39
51. login.aspx.cs 65
52. login1.aspx 33
53. login1.aspx.cs 58
54. login2.aspx 30
55. login2.aspx.cs 22
56. MasterPage.master 156
57. MasterPage.master.cs 134
58. multiple connection.aspx 28
59. multiple connection.aspx.cs 14
60. multiple ordering channels.aspx 518
61. multiple ordering channels.aspx.cs 14
62. new domestic lpg connection.aspx 24
63. new domestic lpgconnection.aspx.cs 22
64. new domestic lpg connection1.aspx 168
65. new domestic lpg connection1.aspx.cs 94
66. new domestic lpg connection2.aspx 72
67. new domestic lpg connection2.aspx.cs 49
68. north delhi.aspx 75
69. north delhi.aspx.cs 14
70. online booking.aspx 31
http://home.aspx.cs/http://home.aspx.cs/http://home.aspx.cs/ -
8/10/2019 ONELINE GAS SERVICE REPORT
54/77
71. online booking.aspx.cs 63
72. overview.aspx 165
73. overview.aspx.cs 14
74. piped gas.aspx 338
75. piped gas.aspx.cs 14
76. png consumer.aspx 85
77. pngconsumer.aspx.cs 14
78. punjab.aspx 6
79. punjab.aspx.cs 14
80. regional.aspx 299
81. regional.aspx.cs 14
82. safety.aspx 34
83. safety.aspx.cs 28
84. select.aspx 32
85. select.aspx.cs 29
86. select123.aspx 31
87. select123.aspx.cs 29
88. shahadra.aspx 51
89. shahadra.aspx.cs 14
90. south delhi.aspx 107
91. south delhi.aspx.cs 14
92. south east delhi.aspx 75
93. south east delhi.aspx.cs 14
94. territory.aspx 834
-
8/10/2019 ONELINE GAS SERVICE REPORT
55/77
95. territory.aspx.cs 14
96. value added services.aspx 769
97. value added services.aspx.cs 14
98. veiwcust detail.aspx 28
99. veiwcustdetail.aspx.cs 14
100. vender.aspx 33
101. vender.aspx.cs 66
102. view booking details.aspx 16
103. view booking details.aspx.cs 18
104. view complaint.aspx 15
105. view complaint.aspx.cs 14
106. vision and mision.aspx 25
107. vision and mision.aspx.cs 14
108. Web.config 127
109. Web.sitemap 30
110. west delhi.aspx 181
111. west delhi.aspx.cs 14
-
8/10/2019 ONELINE GAS SERVICE REPORT
56/77
10. Output
Figure 1.0:-HOME
-
8/10/2019 ONELINE GAS SERVICE REPORT
57/77
-
8/10/2019 ONELINE GAS SERVICE REPORT
58/77
Figure 1.2.1:-HOME>Products>Auto LPG
Figure 1.2.2:-HOME>Products>Bharat Metal Cutting
-
8/10/2019 ONELINE GAS SERVICE REPORT
59/77
Figure 1.2.3:-HOME>Products>Piped Gas
Figure 1.3.1:-HOME>Customer Care>Customer First
-
8/10/2019 ONELINE GAS SERVICE REPORT
60/77
Figure 1.3.2:-HOME>Customer Care>PNG Consumer
Figure 1.3.3:-HOME>Customer Care>Multiple Connection
-
8/10/2019 ONELINE GAS SERVICE REPORT
61/77
Figure 1.3.4:-HOME>Customer Care>Multiple Ordering Channel
Figure 1.3.5:-HOME>Customer Care>IVRs Services
-
8/10/2019 ONELINE GAS SERVICE REPORT
62/77
Figure 1.3.6:HOME>Customer Care>Bharatgas Emergency Cell Services
Figure 1.4.1:-HOME>Distributor>Selection Guidelines
-
8/10/2019 ONELINE GAS SERVICE REPORT
63/77
Figure 2.0:-Regional Offices
Figure 3.0:-Territory Offices
-
8/10/2019 ONELINE GAS SERVICE REPORT
64/77
Figure 4.0:-Safety First
Figure 5.0:-Change Of Distributor
-
8/10/2019 ONELINE GAS SERVICE REPORT
65/77
Figure 6.0:-Value Added Services
Figure 7.0:-Distributor Locator
-
8/10/2019 ONELINE GAS SERVICE REPORT
66/77
Figure 7.0:-Distributor Locator>
Figure 8.0:-New Domestic LPG Connection
-
8/10/2019 ONELINE GAS SERVICE REPORT
67/77
Figure 8.1.1:-New Domestic LPG Connection>New Request
Figure 8.1.2:-New Domestic LPG Connection>New Request
-
8/10/2019 ONELINE GAS SERVICE REPORT
68/77
Figure 8.2.1:-New Domestic LPG Connection>Cancel Request
Figure 8.2.2:-New Domestic LPG Connection>Cancel Request
-
8/10/2019 ONELINE GAS SERVICE REPORT
69/77
Figure 9.0:-Online Booking
Figure 9.1:-Online Booking>
-
8/10/2019 ONELINE GAS SERVICE REPORT
70/77
Figure 9.1.1.1:-Online Booking>Cylinder Booking
Figure 9.1.1.2:-Online Booking>Cylinder Booking
-
8/10/2019 ONELINE GAS SERVICE REPORT
71/77
Figure 9.1.2.1:-Online Booking>Complaints
Figure 9.1.3.1:-Online Booking>Feedback
-
8/10/2019 ONELINE GAS SERVICE REPORT
72/77
Figure 9.1.3.2:-Online Booking>Feedback
Figure 10.0:-Login>
-
8/10/2019 ONELINE GAS SERVICE REPORT
73/77
Figure 10.1:-Login>Admin
Figure 10.1.1:-Login>Admin
-
8/10/2019 ONELINE GAS SERVICE REPORT
74/77
Figure 10.1.1:-Login>Admin>
View customer details, View Booking details, View complaint details, View
Feedback details
Figure 10.2:-Login>Vendor
-
8/10/2019 ONELINE GAS SERVICE REPORT
75/77
-
8/10/2019 ONELINE GAS SERVICE REPORT
76/77
11. Glossary HTML(Hypertext Markup Language)A document-layout and hyperlink-specification
language. HTML is used to describe how the contents of a document (e.g., text, images, and
graphics) should be displayed on a video monitor or a printed page. HTML also enables a
document to become interactive with other documents and resources by using hypertext links
embedded into its content. HTML is the standard content display language of the World Wide
Web (WWW), and is typically conveyed between network hosts using theHTTPprotocol.
SeeXHTML.
HTTP(Hyper Text Transfer Protocol)An Internet protocol used to transport content and
control information across the World Wide Web (WWW). Web content typically originates from
Web servers (also calledHTTP servers) that run services that support the HTTP protocol. Web
clients (i.e., Web browsers) access the content on the server using the rules of the HTTP protocol.
The actual Web content is encoded using theHTMLorXHTMLlanguages.
C#(C Sharp)-C# is a multi-paradigm programming language encompassing strong typing,
imperative, declarative, functional, generic, object-oriented (class-based), and component-
orientedprogramming disciplines. It was developed byMicrosoftwithin its .NETinitiative and
later approved as a standard by ECMA and ISO. C# is one of the programming languages
designed for the Common Language Infrastructure .C# is intended to be a simple, modern,
general-purpose, object-oriented programming language.
CSS3 (Cascading Style sheets)- CSS3 is the latest specification of Cascading Style sheets and
contain a plethora of new properties that will help you transform the quality and interaction of
your pages, whilst reducing reliability on scripts.
Asp.net(Active Server Page . net)-ASP.NET is an open sourceserver-sideWeb application
frameworkdesigned forWeb developmentto producedynamic Web pages.It was developed by
Microsoftto allowprogrammersto build dynamicweb sites,web applicationsandweb services.
SQL(Structured Query Language)-SQL is aspecial-purpose programming languagedesigned for
managing data held in a relational database management system (RDBMS), or for stream
processing in a relational data stream management system (RDSMS) .Originally based upon
relational algebraandtuple relational calculus,SQL consists of adata definition languageand a
data manipulation language. The scope of SQL includes data insert, query, update and delete,
schemacreation and modification, and data access control. Although SQL is often described as,
and to a great extent is, adeclarative language,it also includesproceduralelements.
SRS- Software Requirements Specification
SDS- Software Design Specification
DFD-Data Flow Diagram
GUI-Graphical User Interface
http://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#HTTPhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#HTTPhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#HTTPhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#XHTMLhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#XHTMLhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#XHTMLhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#HTMLhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#HTMLhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#HTMLhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#XHTMLhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#XHTMLhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#XHTMLhttp://en.wikipedia.org/wiki/Multi-paradigm_programming_languagehttp://en.wikipedia.org/wiki/Multi-paradigm_programming_languagehttp://en.wikipedia.org/wiki/Strong_typinghttp://en.wikipedia.org/wiki/Strong_typinghttp://en.wikipedia.org/wiki/Imperative_programminghttp://en.wikipedia.org/wiki/Imperative_programminghttp://en.wikipedia.org/wiki/Declarative_programminghttp://en.wikipedia.org/wiki/Declarative_programminghttp://en.wikipedia.org/wiki/Functional_programminghttp://en.wikipedia.org/wiki/Functional_programminghttp://en.wikipedia.org/wiki/Generic_programminghttp://en.wikipedia.org/wiki/Generic_programminghttp://en.wikipedia.org/wiki/Object-oriented_programminghttp://en.wikipedia.org/wiki/Object-oriented_programminghttp://en.wikipedia.org/wiki/Class_(computer_science)http://en.wikipedia.org/wiki/Class_(computer_science)http://en.wikipedia.org/wiki/Class_(computer_science)http://en.wikipedia.org/wiki/Component-based_software_engineeringhttp://en.wikipedia.org/wiki/Component-based_software_engineeringhttp://en.wikipedia.org/wiki/Component-based_software_engineeringhttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/.NET_Frameworkhttp://en.wikipedia.org/wiki/.NET_Frameworkhttp://en.wikipedia.org/wiki/.NET_Frameworkhttp://en.wikipedia.org/wiki/International_Organization_for_Standardizationhttp://en.wikipedia.org/wiki/International_Organization_for_Standardizationhttp://en.wikipedia.org/wiki/Common_Language_Infrastructurehttp://en.wikipedia.org/wiki/Common_Language_Infrastructurehttp://en.wikipedia.org/wiki/Open_sourcehttp://en.wikipedia.org/wiki/Web_application_frameworkhttp://en.wikipedia.org/wiki/Web_application_frameworkhttp://en.wikipedia.org/wiki/Web_application_frameworkhttp://en.wikipedia.org/wiki/Web_developmenthttp://en.wikipedia.org/wiki/Web_developmenthttp://en.wikipedia.org/wiki/Web_developmenthttp://en.wikipedia.org/wiki/Dynamic_Web_pageshttp://en.wikipedia.org/wiki/Dynamic_Web_pageshttp://en.wikipedia.org/wiki/Dynamic_Web_pageshttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Programmerhttp://en.wikipedia.org/wiki/Programmerhttp://en.wikipedia.org/wiki/Programmerhttp://en.wikipedia.org/wiki/Web_sitehttp://en.wikipedia.org/wiki/Web_sitehttp://en.wikipedia.org/wiki/Web_sitehttp://en.wikipedia.org/wiki/Web_applicationhttp://en.wikipedia.org/wiki/Web_applicationhttp://en.wikipedia.org/wiki/Web_applicationhttp://en.wikipedia.org/wiki/Web_servicehttp://en.wikipedia.org/wiki/Web_servicehttp://en.wikipedia.org/wiki/Web_servicehttp://en.wikipedia.org/wiki/Special-purpose_programming_languagehttp://en.wikipedia.org/wiki/Special-purpose_programming_languagehttp://en.wikipedia.org/wiki/Special-purpose_programming_languagehttp://en.wikipedia.org/wiki/Relational_database_management_systemhttp://en.wikipedia.org/wiki/Relational_database_management_systemhttp://en.wikipedia.org/wiki/Relational_data_stream_management_systemhttp://en.wikipedia.org/wiki/Relational_data_stream_management_systemhttp://en.wikipedia.org/wiki/Relational_algebrahttp://en.wikipedia.org/wiki/Relational_algebrahttp://en.wikipedia.org/wiki/Tuple_relational_calculushttp://en.wikipedia.org/wiki/Tuple_relational_calculushttp://en.wikipedia.org/wiki/Tuple_relational_calculushttp://en.wikipedia.org/wiki/Data_definition_languagehttp://en.wikipedia.org/wiki/Data_definition_languagehttp://en.wikipedia.org/wiki/Data_definition_languagehttp://en.wikipedia.org/wiki/Data_manipulation_languagehttp://en.wikipedia.org/wiki/Data_manipulation_languagehttp://en.wikipedia.org/wiki/Database_schemahttp://en.wikipedia.org/wiki/Database_schemahttp://en.wikipedia.org/wiki/Declarative_programminghttp://en.wikipedia.org/wiki/Declarative_programminghttp://en.wikipedia.org/wiki/Declarative_programminghttp://en.wikipedia.org/wiki/Procedural_programminghttp://en.wikipedia.org/wiki/Procedural_programminghttp://en.wikipedia.org/wiki/Procedural_programminghttp://en.wikipedia.org/wiki/Procedural_programminghttp://en.wikipedia.org/wiki/Declarative_programminghttp://en.wikipedia.org/wiki/Database_schemahttp://en.wikipedia.org/wiki/Data_manipulation_languagehttp://en.wikipedia.org/wiki/Data_definition_languagehttp://en.wikipedia.org/wiki/Tuple_relational_calculushttp://en.wikipedia.org/wiki/Relational_algebrahttp://en.wikipedia.org/wiki/Relational_data_stream_management_systemhttp://en.wikipedia.org/wiki/Relational_database_management_systemhttp://en.wikipedia.org/wiki/Special-purpose_programming_languagehttp://en.wikipedia.org/wiki/Web_servicehttp://en.wikipedia.org/wiki/Web_applicationhttp://en.wikipedia.org/wiki/Web_sitehttp://en.wikipedia.org/wiki/Programmerhttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Dynamic_Web_pageshttp://en.wikipedia.org/wiki/Web_developmenthttp://en.wikipedia.org/wiki/Web_application_frameworkhttp://en.wikipedia.org/wiki/Web_application_frameworkhttp://en.wikipedia.org/wiki/Open_sourcehttp://en.wikipedia.org/wiki/Open_sourcehttp://en.wikipedia.org/wiki/Common_Language_Infrastructurehttp://en.wikipedia.org/wiki/International_Organization_for_Standardizationhttp://en.wikipedia.org/wiki/.NET_Frameworkhttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Component-based_software_engineeringhttp://en.wikipedia.org/wiki/Component-based_software_engineeringhttp://en.wikipedia.org/wiki/Class_(computer_science)http://en.wikipedia.org/wiki/Object-oriented_programminghttp://en.wikipedia.org/wiki/Generic_programminghttp://en.wikipedia.org/wiki/Functional_programminghttp://en.wikipedia.org/wiki/Declarative_programminghttp://en.wikipedia.org/wiki/Imperative_programminghttp://en.wikipedia.org/wiki/Strong_typinghttp://en.wikipedia.org/wiki/Multi-paradigm_programming_languagehttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#XHTMLhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#HTMLhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#XHTMLhttp://www.developer.com/net/asp/article.php/1756291/Microsoft-NET-Glossary.htm#HTTP -
8/10/2019 ONELINE GAS SERVICE REPORT
77/77
OGS-Online Gas Services
12.Bibliography previously developed documents relating to the project
Documentation concerning related projects
https://www.google.co.in/
www.w3cschools.org
http://en.wikipedia.org/wiki/.NET_Framework
http://dotnet.wikis.com/wc.dll?dotnet~DotNetWiki
http://en.wikipedia.org/wiki/Microsoft_SQL_Server
http://msdn.microsoft.com/en-us/sqlserver/bb671246
https://www.google.co.in/https://www.google.co.in/http://www.w3cschools.org/http://www.w3cschools.org/http://en.wikipedia.org/wiki/.NET_Frameworkhttp://dotnet.wikis.com/wc.dll?dotnet~DotNetWikihttp://en.wikipedia.org/wiki/Microsoft_SQL_Serverhttp://msdn.microsoft.com/en-us/sqlserver/bb671246http://msdn.microsoft.com/en-us/sqlserver/bb671246http://en.wikipedia.org/wiki/Microsoft_SQL_Serverhttp://dotnet.wikis.com/wc.dll?dotnet~DotNetWikihttp://en.wikipedia.org/wiki/.NET_Frameworkhttp://www.w3cschools.org/https://www.google.co.in/
top related