Software Requirements Specification

For

E-GAS SEVA
TEAM GUIDE NAME: POONAM SHARMA TEAM MEMBERS: APEKSHA JADON

KRATIKA SINGHAL PRERNA GUPTA SUWETA SHAKYA

COLLEGE NAME: MADHAV INSITUTE OF TECHNOLOGY AND SCIENCE (MITS)-GWALIOR DEPARTMENT: IT (INFORMATION TECHNOLOGY) STATE: MADHYA PRADESH

CONTENTS
Introduction Advantages of E gas technology Purpose Scope Definitions Tools References Technologies Overview Technology E-R Diagram System features and Requirements

Introduction
E-gas has the potential to make use of our most abundant energy resource coal in such a way as to dramatically reduce its environmental impact. The Rational Unified Process an iterative software development process framework created by the Rational Software Corporation, a division of IBM . has shows a great enhancement in providing elements from all the models of ONLINE gas sewa techniques. The RUP is normally described from three perspectives: A dynamic perspective that shows the phases of the model over time. A static perspective that shows the process activities that are enacted. A practice perspective that suggests good practices to be used during the process.

The different phases in RUP are Inception The goal of the inception phase is to establish a business case for the system. Identifying all external entities that will interact with the system and defining these interaction. This information is used to assess the contribution of system to business. Elaboration The goals of the elaboration phase are to develop an understanding of the problem domain, establish an architectural framework, develop project plan and identify key project risks. Construction This phase is concerned with system design, programming and testing. Parts of the system are developed in parallel and integrated during this phase. Transition Virtual Medical Home 2009 Page 4 This is the final phase of RUP and is concerned with moving the system from the development community to the user community and making it work in real environment.

Advantages of E-Gas Technology

The E-Gas Technology for Gasification features a proprietary two-stage, slurry-fed, oxygenblown, entrained-flow design, which converts feedstock energy into high-quality synthesis gas at a high conversion efficiency. The two-stage gasifier design, coupled with our unique continuous slag removal system results in a very compact plant design, reducing both capital and operating cost. The use of a fire-tube boiler for synthesis gas cooling was pioneered during the early development of the E-Gas process, and now this proven design provides an additional cost and operations advantage to the E-Gas technology. Other unique features of the E-Gas process can be found in particulate removal, sulfur hydrolysis, and sulfur removal from the synthesis gas. The many advantages of the process are brought together by the experienced ConocoPhillips team to meet the licensee's needs for today's stringent project requirements. Our breadth of experience, from research, development, process design, engineering, operation and maintenance, allows us to offer licenses as well as the support services needed by the client.

PU RPOSE OF THE PROJECT - e-SEVA

The proposed study is to ascertain the extent to which the intended outcomes of the project e-Seva have been achieved that includes the qualitative, quantitative and factual analysis. Qualitative Analysis The following are the objectives of eSeva as originally defined and as they continue to be. Providing one-stop services to the citizens through a chain of Integrated Citizen Service centers. All the counters in all the service centres should provide all the services offered by eSeva. The citizen can walk into any service center and experience the same quality of service. Citizens should not be required to travel more than a kilometre to reach the eSeva center nearest their home. The architecture adopted should be scalable and secure. The service time should be below 3 minutes per transaction and the total time spent by a citizen including the time spent on waiting for ones turn should be less than 10 minutes. All the services should be available at the centres for 12 hours a day and selected services, 24 hours over the Internet. Citizens should not stand in queues. The services that do not involve an inspection or attestation should be offered over the Internet also, so that citizens can avail them from home or office. The cost of transacting with government should be reduced. The business model should be such that the operations are sustainable over long period. The need for the citizens to go to government offices should be minimized over a period of time.

Scope
This is a worldwide major application.

1. There are four major users kiosk, customer, organization, receptionist. 2. All users have their own profile in ONGC 3. The web cam interaction between receptionist and customer 4. Customer can form their online queues if status being busy and or otherwise can fill up their forms make themselves free until their number comes 5. Organization can show send their bills online and even can show the facilities available online and help the customers otherwise 6. Kiosk manager views and manages the appointments of the customer and open and close activities and calculates his commission activities. He also sends reports to admin. performs day

1.4 Definitions, Acronyms and Abbreviations

WASCE :WebSphere Application Server Community Edition. It is an application server that runs and supports J2EE and web service applications.

DB2 :Database_2.A database management system that provides a flexible and efficient database platform to maintain records of students, teachers, admin and dm.

JSP :Java Server Pages. It is used to create dynamic web content.

UML :Unified Modeling Language is a standard language for writing software blueprints. The UML may be used to visualize, specify, construct and document RAD :Rational Application Developer is a development tool that helps to design web pages and also helps to design the diagrams like ER, Database schema diagrams and to generate DDL XML :Extensible Markup Language is a text based format that let developers describe, deliver and exchange structured data between a range of applications to client for display and manipulation. EJB: Enterprise Java Beans. J2EE: Java 2 Enterprise Edition is a programming platform part of the Java Platformfor developing and running distributed multitier architecture Java applications, based largely on modular software components running on an application server. MY SQL: MY SQL Database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications. TOM-CAT: TOMCAT application server is an application server that runs business applications and supports the J2EE and web services standards. HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).
TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP.

Tools used
Web server WASCE
WebSphere Application Server Community Edition (from now on WASCE) is a free, certified Java EE 5 server for building and managing Java applications. It is IBM's supported distribution of Apache Geronimo that uses Tomcat for servlet container and Axis 2 for web services. Over 15 WASCE developers are committers in the Apache Geronimo project.

Development tool RAD

IBM Rational Application Developer for WebSphere Software (RAD) is an integrated development environment (IDE), made by IBM's Rational Software division, for visually designing, constructing, testing, and deploying Web services, portals, and Java (J2EE) applications.

Database platform DB2

DB2 Database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications and supports the J2EE and web services standards.

Design tool Rational Software Modeler

IBM Rational Software Modeler, (RSM) made by IBM's Rational Software division, is a Unified Modeling Language UML 2.0-based visual modeling and design tool. Rational Software Modeler is built on the Eclipse open-source software framework and includes capabilities focused on visual modeling and model-driven development (MDD) with the UML for creating resilient, thought-out applications and web services.

REFERENCES
e-Seva Official website - http://esevaonline.com B. Internet article - http://www.mit.gov.in/content/common-services-centrescsc C. AP Online Website - List of Services provided https://secure.aponline.gov.in/CitizenPortal/userinterface/citizen/ListOfServices.aspx D. AP Online Website List of Franchise Centres http://www.aponline.gov.in/MapsAPOnline/APOnlineCentersNew.aspx E. e-Seva Brochure and Material (Courtesy: Mr.Yedukundalu) F. Various Media articles on Internet G. Reports provided by e-Seva Deputy Director Urban H. Google Search Engine IBM www.ibm.in/developerworks . Wikipedia - www.wikipedia.com

.7 Technologies to be used
DB2: Relational Database Management System. RAD: Rational Application Developer. WASCE: Websphere Application Server Community Edition. Rational Software Modeler.

1.8 Overview
Existing System:
Registration for users Discussion forum

Advantages
Single window system Adequate seating arrangement Good ambience Women manned counters Citizen satisfied with utility payment services Easy access to e-Seva Centers (radius of 5-6 kms) Citizen-friendly behavior of staff Smooth disbursement of services

Drawbacks
Issues of infrastructure maintenance (Digital display, generator sets, PC Minimal maintenance engineers (only 1 or 2 available across the city) Bleak response/backup from the Head Office Long waiting time for Passport, Voter Card and Municipal services Frequent visits regarding the status of certificates Less operational counters No announcement system for tokens (Missing of turns) Difficulty in filling up forms No drinking water facilities problems)

No provision for security No public convenience

Our Plan:
Registration for users. Online maintenance of records. .

Overall description

SERVICE DELIVERY PROCESS AT SERVICE COUNTERS Citizen comes to eSeva Centre and approaches Token Counter Electronic Queue Management System (EQMS) integrated time stamp: i. when customer arrives at the Token Counter and obtains Token ii. when customer token is called iii.

on completion of service delivery Counter operator enters customer details to display details Acceptance of payment in form of Cash/Cheque/Demand/Credit Card Issue of Receipt and completion of delivery of service Transmission/Communication of transaction details to eSeva Data centre and department server Cancelling the receipt and reversing the transaction done due to mistakes and treating this transaction as a new transaction with a unique transaction code.

Storing the cancelled transaction details and transaction code in the database at the ESEVA data center along with a text explanation for cancellation In case of Cheque Bounce, provision for reverse entry in Data base of eSeva and department server. Provision to prepare refund claim statement for claiming refund from department. Locking Customer account for payment through cheque till account is unlocked under orders of EDS. Warning display to counter operator of such accounts whenever such customer visits eSeva, to help recovery of amount.

FINDINGS
1)Customers are satisfied with utility bill payment services. 2)Proximity of eSeva Centers for Citizens is an added advantage 3)There is longer waiting period for new services (Passport, EPIC Card) added. 4)Citizens have Grievance for Municipal Services, gas connection because the departments do not cooperate. 5)Complete Insurance coverage is available for the cash handled in the e-Seva Centre 6)There is lack of internal coordination within the levels of private partner and hence there is no proper response from the Head Office when there are maintenance complaints. 7)Grievance Redressal Mechanism is available for the citizens and the channels are a.Citizen can file the complaint Online b.Citizen can drop the complaint in the Complaints Box at the e-Seva Centre. c.Citizen can call Parishkaram (Toll Free Number 1100)

Technology

e-Seva is developed on a 3-tier architecture with Clients at first-tier Central server at second-tier Departmental server at third-tier Advanced Technologies in application design and development (Web based applications). Connectivity among all participants of the system (e-Seva Data Center, Line Departments and e-Seva e-Seva is developed on a 3-tier architecture with Clients at first-tier Central server at second-tier

 Departmental server at third-tier Advanced Technologies in application design and development (Web based applications). Connectivity among all participants of the system (e-Seva Data Center, Line Departments and e-Seva Centres) is chosen in tune with the Line Departmental compatibility and latest technologies available in the market. Quickly adopting to emerging technologies and modifying the existing applications in tune with the departmental and service requirements is being done regularly. e-Seva Data Center works a HUB where in participating departments and all e-Seva Centres are connected facilitating any centre, any counter any service approach with 64 kbps Leased lines of Teleoperator BSNL. It is upgraded to the size based on the volume of transactions and % of utilization. Connectivity is now at the size of 256 kbps. As the service requires high availability and quick restoration from connectivity break down. It is further upgraded to 256 kbps MLLN connectivity.

ER DIAGRAM

SYSTEM FEATURES AND REQUIREMENTS

HARDWARE REQUIREMENTS
COMPUTER/LAPTOP PROCESSOR-1.5GHZ,PLATINUM 4,DUAL CORE ,CORE 2 DUO RAM-MIN 512MB OS-MIN WINDOWS 2000

SOFTWARE REQUIREMENTS: -

FRONT END
JSP J2EE

BACK END
MY SQL DATABASE TOMCAT SERVER JAVABEAN ENTERPRIZE

Name of Use: Description: Main Scenario: Alternate Scenario: Post Condition :

3.2) Supplementary Requirements: Have hours of operation that are 24 x 7 - Because system can be an automated process, so it can stay open for 24 hours a day. If the base is now the entire world, staying open 24 hours a day becomes critical. System is required to be available 24X7 so UPS support must be on server site for at least 8 hours in case of power failure. System will remain inaccessible to users at 2:00 to 4:00 am for backup and maintenance purpose. Provide good performance and the ability to scale the server The Web Application Server should provide good performance and the ability to manage performance with techniques, such as support for caching, clustering, and load balancing. Providing session management capability - Web application developers should not spend valuable time worrying about how to maintain sessions within the application. The Web Application Server should provide these services.

External Interface Requirements User Interfaces Will make use of the existing Web Browsers such as Internet Explorer or Firefox. The user-interface of the system shall be designed as shown in the user-interface prototypes. Hardware Interfaces Software Interfaces The existing Local Area Network (LAN) will be used for collecting data from the users and also for updating the Library Catalogue. Communications Interfaces The Online Library System will be connected to the World Wide Web.

Other Nonfunctional Requirements Performance Requirements Safety Requirements <Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must

be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the products design or use. Define any safety certifications that must be satisfied.> Security Requirements <Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.> Software Quality Attributes <Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.> Other Requirements <Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.>