Information Kiosk: Vivid Winners
Information Kiosk: Vivid Winners
Information Kiosk: Vivid Winners
Vivid Winners
Information Kiosk
Software Requirements Specification
Version 4.0
Team Guide: T.Revathi,HOD of IT Department, Mepco Schlenk Engineering College Members: R.Dhivya, V.Kathimathi, R.Senbagarekka, D.Jothi College Name: Mepco Schlenk Engineering College,Sivakasi Department: Information Technology State: TamilNadu
Page 1
Revision History
Date 21-12-10 30-12-10 04-02-11 03-30-11 Version 1. 0 2. 0 3 4 Description Synopsis Synopsis Synopsis Author Vivid Winners Vivid Winners Vivid Winners Vivid Winners
Page 2
Table of Contents
Description 1.0 Introduction 1.1 1.2 1.3 1.4 1.5 1.6 2.0 Purpose Scope Definition, Acronyms, and Abbreviations References Technologies to be used Overview Page No. 5-7 5 5 5 6 7 7 8 - 14 8 8 8 8 9 9 9 10 11
Overall Description 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 Product Perspective Software Interface Hardware Interface Product Function User Characteristics Constraints Architecture Design Use Case Model Description Class Diagram
2.10
Design Diagrams
Page 3
12-14
Information Kiosk
Version 4.0
12 13 14
2.11 Assumptions and Dependencies 15 3.0 Specific Requirements 3.1 3.2 Use Case Reports Supplementary Requirements 15-17 15 17
Page 4
Information Kiosk
Version 4.0
Introduction:
Most customers of modern age prefer choosing, deciding, and transacting privately or on their own, or with minimal interference from sales agents. They prefer to seek technical opinion only when they need it. In such an evolving nature of client base, kiosks prove to be a perfect interface since it is entirely designed on the notion of self service. Kiosks effectively do the job of marketing, sales, or public relations personnel. Effectively, they reduce workload and cost of having commensurate number of personnel at late hours and remote locations.
1.1 Purpose:
The purpose of this kiosk is to make aware of all the facilities provided to the people by both the government organizations and NPOs. This will avoid misguidance and wrong information and one can get what they want.
1.2 Scope:
The Scope of the project includes:
The Information Kiosk is useful in gathering data regarding the village, service available,
occupation, tourism, transportation, schemes implemented, weather report, utilities, etc.,. The Information Kiosk also provides people to utilize all the e-services provided by the government without the PC. The information Kiosk is one of the best self services provided to the human.
Java platform, which is used for developing and running distributed java applications. WASCE (WebSphere Application Server Community Edition): It is an application
server that runs and supports the J2EE and the web service applications.
Page 5
Information Kiosk
Version 4.0
which is designed to develop more complex projects by providing a complete dynamic web service. DB2 (IBM Database 2): It is a database management system that provides a flexible
and efficient database platform to raise a strong "on demand" business applications. HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server
to transport and store data. Ajax (Asynchronous Java Script and XML): It is a technique used in java script to
create dynamic web pages. Web 2.0: It is commonly associated with web applications which facilitate
interactive information sharing, interoperability, user-centered design and collaboration on the World Wide Web.
1.4 References:
http://municipality.tn.gov.in/sivakasi/ http://www.sivakasi.com/ http://en.wikipedia.org/wiki/Sivakasi http://virudhunagar.nic.in/industry/svkindustries.htm http://wikitravel.org/en/Sivakasi
Information Kiosk
Version 4.0
J2EE: (Servlet, JSP, JAXP, Java Beans) Application architecture. JAVA: Application architecture.
WASCE: (WebSphere Application Server Community Edition) Web Server DB2: IBM Database. Ajax: Asynchronous Java Script and XML.
XML: Extension Markup Language. Web 2.0: RSS Feed 2.0. Eclipse Helios: Development tool.
1.6 Overview: The SRS will include two sections, namely: -I- Overall Description: This section will describe major components of the system, interconnections, and external interfaces. -I- Specific Requirements: This section will describe the functions of actors, their roles in the system and the constraints faced by the system.
Page 7
Information Kiosk
Version 4.0
4- Server
Provides services to get information about the following: Transportation Emergency Government Hotels Recreation Institution Organization Industry
The user should have some knowledge about using the system.
Information Kiosk
Version 4.0
The user interface will be provided in the English language and Tamil language. Only the government employee can update the data. 2.7 Architecture Design: Information Kiosk:
DATABASE
RESULT
REQUEST UPDATED
QUERY
USER
Process information
RESPONSE
WEBSERVICE S
Page 9
Information Kiosk
Version 4.0
View Report
User
Access Service
login
Adminstrator
Generate report
Web Server
Maintain Database
Page 10
Information Kiosk
Version 4.0
Service servName : String = null servID : String = null Request reqID : String = null reqService : String = null getReqID() getReqService() request() getServID() getServName() service()
Page 11
Information Kiosk
Version 4.0
User Start
Administrator
accepted
denied
Page 12
Information Kiosk
Version 4.0
Recreati on
University
Industry
Petrol Bulk
Has Name ID
Railway Station
Bus stand
Has Name ID
Page 13
Information Kiosk
Version 4.0
2.10.3 ER Diagram:
Film running TotalSe ats Theatre Police Park IS A Templ e History Industry NoOfRoo ms Lodge IS A Na me Recreati on IS A Emerge ncy Street Addres s Place Phon e Post Office PINCO DE Hospit al Fire Station ID Cours e College
H as
University
Branch
From Timin g To To
Timin g
From
The system assumes the user will know the basic knowledge to how to use the hardware interface to access services It depends on the database management system to use efficient the memory and also it
Page 14
Information Kiosk
Version 4.0
Information Kiosk Software Requirements Specification Vivid Winners should be easy to process the query.
3.Specific Requirements:
3.1 Use Case Reports:
UC.1 Login Description: The administrator has to gve login into the system so that he can able to modify the database and can generate reports. Actors: Administrator Flow of Events: MAIN FLOW: 1. The administrator must give the user id and password. 2. The administrator has to click the login button. ALTERNATIVE FLOW: 1. If the user id or password is wrong the error message will be thrown. Pre-condition: 1. The Administrator has to switch on the system. Post-condition: 1. The administrator can modify the database 2. The administrator can generate reports UC.2 Generate Report Description: This use case allows the administrator to generate the report for the user so that they will be more satisfied with the system. Actors: Administrator Flow of Events: MAIN FLOW: 1. The administrator must give the query which has to be displayed as a report. 2. If the query is correct he can provide that report to the user to use. ALTERNATIVE FLOW: 1. If the query is not correct then the report will not be generated 2. Administrator have to select the values to be displayed from the right table Pre-condition: 1. The administrator has to successfully login into the system Post-condition: 1. The new reports will be available to use UC.3 Maintain Database Description: This use case allows the administrator to insert a new table, delete existing table and can update the table. Actors: Administrator Flow of Events: MAIN FLOW: 1. The administrator must give the table name which he has to create. 2. The administrator can view all the existing tables if he wants he can delete it or update its
Page 15
Information Kiosk
Version 4.0
values. ALTERNATIVE FLOW: 1. If the new table name is already exist the error message will be thrown and ask the administrator to change the name. Pre-condition: 1. The administrator has to successfully login into the system Post-condition: 1. The new table will be created 2. The values will be updated successfully UC.4 Access Services Description: This use case allows the user to get information about the particular places or he can get more information about the each services provided to the user. Actors: User Flow of Events: MAIN FLOW: 1. The user has to select the service. 2. He/She can also give the voice input to access the service. ALTERNATIVE FLOW: 1. If user chooses the voice input then if the user spelled the service provided to him wrongly then the error message will be thrown. Pre-condition: 2. The user has to switch on the system. Post-condition: 1. He can be provided with the more details about the service he had requested for. 2. He can save it in the pdf format if he wants. UC.5 View Report Description: This use case allows the user to view the reports that is available. Actors: User Flow of Events: MAIN FLOW: 1. The user has to select the report he wants 2. He can view the report ALTERNATIVE FLOW: 1. If the report that user requeted is not available then the error message will be thrown. Pre-condition: 1. The user has to switch on the system. Post-condition: 1. He can be provided with the report he has requested 2. He can save it in the pdf format if he wants.
Page 16
Information Kiosk
Version 4.0
The input data must be precise to avoid confusions among the results and to provide the accurate results.
The interactive environment must be a Touch screen system with all enhanced capabilities.
Page 17