Synopsis Latest Version

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous
Version 1.0 Date: 15th oct 2007
AMBIDEXTROUS
DISTRICT COLLECTORATE OFFICE INFORMATION INTEGRATION
Software Requirement Specification

Version 1.0
Team Guide Prof.R.T.Sakthidaran
Team Members S.S.Senthil S.Kishore kanna K.S.Ramkumar S.V.Balaji
Ambidextrous/Tamilnadu, 2007
Page 1
REVISION HISTORY
Date 15/oct/2007 Version 1.0 Synopsis Description Author Ambidextrous
Page 2
Table of Contents
1. Introduction
1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms and Abbreviations 1.4 References 1.5 Technologies to be used 1.6 Overview
2. Overall Description
2.1 UseCase Model Survey 2.2 class diagram 2.3 sequence diagram 2.4 Architecture diagram 2.5 database design 2.5.1 ER Diagram 2.5.2 Schema 2.6 Assumptions and Dependencies
3. Specific Requirements
3.1 UseCase Reports
Page 3
Software Requirements Specification

1.0 Introduction
District Collectorate Office Information Integration is to maintain and group together information from various departments of collector office, schools and hospitals.
1.1
Purpose
Conventionally the citizen has to go to collector office in person to get the certificates like Community, Birth, Income and Ration card etc., this result in wastage of time. Here we provide the online registration facility for getting certificate to the citizens. So that they have to visit collector office only once at the time of certificate provision
1.2
Scope
Create different employees and assign corresponding privileges. Maintain a centralized database to provide security to information which can be accessed only by the admin. Employee logs on to his account to approve/decline/reject the forms which are send by citizens to get certificates, under verification. Transfer employee and promotion feature. Track all the employees, citizens and their contact details. All users are authenticated to avail the service. Confirmation link is sent to the new user and employee when signing up.
Page 4
FAQ section is also included for users benefit. Sequential Verification is done for issuing certificates
1.3
Definitions, Acronyms and Abbreviations
Admin Administrator (database administrator), he is the controller of all the employees, citizens and maintaining all records of the citizens and employees. Employees Collector, Tahsildar, Deputy Tahsildar, Revenue Inspector (R.I), Village Administrative Officer (V.A.O) and other officials who are working in govt. office.
Citizen End users, those who only registered in this site. HTML Hypertext Markup Language is to create static web pages. JSP Java Server pages is used to create dynamic web content. J2EE Java 2 Enterprise Edition is a programming platform and it is the part of the java platform for developing and running distributed java applications. WASCE Web sphere application server community edition is an application server that runs and supports the J2EE and web service applications.
WSAD Web sphere studio application developer is a designer toolkit which is designed for develop more complex projects by providing fully dynamic web service.
DB2 Database 2 is the database management system that provides a flexible and efficient database platform to erect strong on demand business applications. . HTTP Hypertext transfer protocol is a transaction oriented client/server protocol between web browser and a web server.
Page 5
1.4
References
Project specification requirement (provided by IBM)
1.5
Technologies to be used
J2EE Application architecture JAVA Application architecture WSAD Development tool WASCE - Web Server DB2 Database Rational Design tool
1.6
Overview
SRS includes two sections overall description and specific requirements Overall description will describe major role of the system components and interconnections. Specific requirements will describe roles & functions of the actors.
Page 6
2.0
Overall Description 2.1 Use-case model survey
Page 7
2.2 Class Diagram
Page 8
2.3 SEQUENCE DIAGRAM NORMAL FLOW FOR APPROVAL OF BIRTH/INCOME/SC/ST CERTIFICATE APPLICATION FORMS
: End user open
: Birth/Income certicate/SC/ST forms
: Village administrative officer
: Revenue inspector
: Tahsildar
: Admin
fill
submit open
primary approval
secondary approval
final approval and sends to database
Page 9
DECLINATION/REJECTION CASES CASE 1: REJECTION OF BIRTH/SC/ST FORMS BY VILLAGE ADMINISTRATIVE OFFICER
: End user open fills
submits open submitted forms
rejects and sends back to end user
Page 10
CASE 2: REJECTION OF BIRTH/SC/ST FORMS BY REVENUE INSPECTOR
: End user open
: Birth/Income certi cate/SC/ST forms
: Vil lage administrative offi cer
: Revenue inspector
fill
submit
open submitted forms primary approval
rejects and send back to end user
Page 11
CASE 3: REJECTION OF BIRTH/SC/ST FORMS BY TAHSILDAR
: End user
: Revenue ins pector
: Tahs ildar
open form
fill form
submit form
open submitted form
primary approval
s econdary approval
Page 12
NORMAL FLOW FOR APPROVAL OF BC/OBC CERTIFICATE APPLICATION FORMS
: End user open
: BC/OBC Certificate forms
: Revenue inspector
: Deputy Tahsildar
: Admin
fill
submit open
primary approval
secondary approval
Page 13
DECLINATION/REJECTION CASES CASE 1: REJECTION OF BC/OBC CERTIFICATE FORMS BY VILLAGE ADMINISTRATIVE OFFICER
Page 14
CASE 2: REJECTION OF BC/OBC CERTIFICATE FORMS BY REVENUE INSPECTOR
: End user open
: Birth/Income certi cate/SC/ST forms
: Revenue inspector
fill
submit
Page 15
CASE 3: REJECTION OF BC/OBC CERTIFICATE FORMS BY TAHSILDAR
: End user
: Revenue inspector
: Tahsildar
open form
fill form
submit form
open submitted form
primary approval
secondary approval
Page 16
NORMAL FLOW FOR APPROVAL OF RATION CARD APPLICATION FORM
: End user open
: Ration card Application form
: Civil supplies Revenue inspector
: civil supplies Tahsildar
: Admin
fill
submit open
primary approval
secondary approval
Page 17
DECLINATION/REJECTION CASES CASE 1: REJECTION OF RATION CARD APPLICATION FORM BY VILLAGE ADMINISTRATIVE OFFICER
:Ration card application form
Page 18
CASE 2: REJECTION OF RATION CARD APPLICATION FORM BY CIVIL SUPPLIES REVENUE INSPECTOR
: End user open
:Ration card
application form
: civil supplies revenue inspector
fill
submit
Page 19
CASE 3: REJECTION OF RATION CARD APPLICATION FORM BY CIVIL SUPPLIES TAHSILDAR
: End user
: Ration card Application form open form
: Civil supplies Revenue inspector
:Civil supplies Tahsildar
fill form
submit form
open submitted form
primary approval
secondary approval
Page 20
2.4 Architecture diagram
Page 21
2.5
Database Design
2.5.1 Schema:
Page 22
2.5.2 E-R Diagram:
2.6
Assumptions and Dependencies

The end user should have a basic knowledge of English and computer usage The end user should be able to scan the required documents and upload while applying for various certificates and ration card
Page 23
3.0
Specific Requirements 3.1 Use-case reports
End user:
Sign up:
In order to apply for various certificates such as birth, community, income and ration card, and end user must sign up by filling the sign up form and get it approved by admin.
Sign in:
After getting the username and password, end users can log on to their account and can access the website.
Open profile:
End user can open their profile which contains the personal details which he/she provided during sign up.
View profile:
End user can view their profile which contains the personal details which he/she provided during signup.
Update profile:
End user can update their profile which contains the personal details which he/she provided during sign up if any updations required.
Page 24
Request for certificate:

End user who signed in can request for various certificates such as birth, community, income and ration card.
Open requested forms:

End user who signed in can open the requisition form and after viewing it he/she can close the form without filling the details.
Enter details:
End user who signed in can open the requisition form and enters the mandatory details required in that form.
Submit form:
After filling the mandatory and other details, End user submits the form.
Sign out:
After completing his/her work in the portal, he/she can sign out
Village Administrative officer(VAO):

Sign in:
First the VAO has to login to his account to start his work.
Open Requested form details:

After signing in the VAO can open the details of Requested forms.
Verify the enclosures:
Page 25
After signing into his account, he does the primary verification for providing certificates such as birth, community, income and ration card.
Approve Forms:
After signing into his account, he approves the forms such as birth, community, income and ration card.
Reject Forms:
After signing into his account, he rejects the forms such as birth, community, income and ration card if he/She is not satisfied with the proofs provided.
Pend Forms:
In case of doubtful cases VAO shall keep the certificate request in pending status till he receives the required documents to be verified.
Send Forms:
After his approval, he/she forwards the form to Revenue Inspector for further approval. Sign out: After completing his/her work in the portal, he/she can sign out
Revenue inspector (RI)

Sign in:
First the RI has to login to his account to start his work.

After signing in, the RI can open the details of Requested forms that are approved
Ambidextrous/Tamilnadu, 2007 Page 26
by VAO.

After signing into his account, he does the secondary verification for providing certificates such as birth, community, and income.
Approve Forms:
After signing into his account, he approves the forms such as birth, community, and income.
Reject Forms:
After signing into his account, he rejects the forms such as birth, community, income if he/She is not satisfied with the proofs provided.
Pend Forms:
In case of doubtful cases RI shall keep the certificate request in pending status till he receives the required documents to be verified.
Send Forms:
After his approval, he/she forwards the form to Tahsildar for further approval..
Check community and send:

RI checks the community and sends it to either Tahsildar or Deputy Tahsildar. Sign out: After completing his/her work in the portal, he/she can sign out
Page 27
Tahsildar:
Sign in:
First the Tahsildar has to login to his account to start his work.

After signing in, the Tahsildar can open the details of Requested forms that are approved by RI.

After signing into his account, he does the final verification for providing certificates such as birth, community (only for Scheduled caste/Scheduled tribe) and income.
Approve Forms:
After signing into his account, he approves the forms such as birth, community (only for Scheduled caste/Scheduled tribe), and income.
Reject Forms:
After signing into his account, he rejects the forms such as birth, community (only for Scheduled caste/Scheduled tribe), and income if he/She is not satisfied with the proofs provided.
Pend Forms:
In case of doubtful cases Tahsildar shall keep the certificate request in pending status till he receives the required documents to be verified.
Page 28
Send completely approved forms:

After giving the final approval to birth, community (only for Scheduled caste/Scheduled tribe) and income, he sends the approved record to be stored in database maintained by the Admin. Sign out: After completing his/her work in the portal, he/she can sign out
Deputy Tahsildar:
Sign in:
First the Tahsildar has to login to his account to start his work.

After signing in, the Tahsildar can open the details of Requested forms that are approved by RI.

After signing into his account, he does the final verification for providing community (only for backward class, most backward class and forward class) certificate.
Approve Forms:
After signing into his account, he approves the forms for community (only for backward class, most backward class and forward class) certificate
Page 29
Reject Forms:
After signing into his account, he rejects the forms for community (only for backward class, most backward class and forward class) certificate
Pend Forms:
In case of doubtful cases Tahsildar shall keep the certificate request in pending status till he receives the required documents to be verified..

After giving the final approval to the forms for community (only for backward class, most backward class and forward class) certificate, he sends the approved record to be stored in database maintained by the Admin. Sign out: After completing his/her work in the portal, he/she can sign out
Civil Supplies RI:

Sign in:
First the RI has to login to his account to start his work.

After signing in, the RI can open the details of Requested forms that are approved by VAO.

After signing into his account, he does the secondary verification for providing ration card.
Approve Forms:
After signing into his account, he approves the forms such as birth, community, and income.
Reject Forms:
After signing into his account, he rejects the forms for ration card if he/She is not satisfied with the proofs provided.
Pend Forms:
In case of doubtful cases RI shall keep the certificate request in pending status till he receives the required documents to be verified.
Send Forms:
After his approval, he/she forwards the form to Tahsildar for further approval. Sign out: After completing his/her work in the portal, he/she can sign out
Civil supplies Tahsildar:
Sign in:
First the Civil supplies Tahsildar has to login to his account to start his work.

After signing in, the Civil supplies Tahsildar can open the details of Requested forms that are approved by Civil supplies RI.
Page 31

After signing into his account, he does the final verification for providing ration card.
Approve Forms:
After signing into his account, he approves the form for ration card.
Reject Forms:
After signing into his account, he rejects the form for ration card if he/She is not satisfied with the proofs provided.
Pend Forms:
In case of doubtful cases Civil supplies Tahsildar shall keep the certificate request in pending status till he receives the required documents to be verified..

After giving the final approval to ration card, he sends the approved record to be stored in database maintained by the Admin. Sign out: After completing his/her work in the portal, he/she can sign out
Hospital user:
Page 32
Sign up:
In order to enter the child birth details the hospital user has to sign up
Sign in:
After getting the username and password, hospital users can log on to their account and can access the website
Provides child birth details:

The hospital user has to provide the specific child birth details such as date and time of birth and name of the childs parents and so on.
Open profile:
Hospital user can open their profile which contains the personal details which he/she provided during sign up.
View profile:
Hospital user can view their profile which contains the personal details which
he/she provided during signup. Update profile:

Hospital user can update their profile which contains the personal details which he/she provided during sign up if any updations required. Sign out: After completing his/her work in the portal, he/she can sign out
School user:
Sign up:
In order to enter the student details, the school user has to sign up
Sign in:
After getting the username and password, hospital users can log on to their account and can access the website
Provides student details:

The school user has to provide the specific child birth details such as community, date of birth of the student and so on.
Open profile:
Hospital user can open their profile which contains the personal details which he/she provided during sign up.
View profile:
Hospital user can view their profile which contains the personal details which
he/she provided during signup. Update profile:

Hospital user can update their profile which contains the personal details which he/she provided during sign up if any updations required. Sign out: After completing his/her work in the portal, he/she can sign out
Admin:
Verify details:
Admin authenticates all the end users and officers by checking their username and password.
Provides login account:

After getting the sign up details from the end user, Admin provides the username and password to the end user that should be kept for future login and also admin checks for uniqueness.
Maintains system server:

Admin maintains the centralized system server which controls the client computers.
Maintains database:
Admin maintains the entire database and he is the only authorized person to add/remove/edit employee records and end user records provided he has to get the order from the highest designation officer.
Add records:
Admin adds the records that are completely approved by all the concerned officers after getting intimation from the highest designation officer who approved that certificate finally. Sign out: After completing his/her work in the portal, he/she can sign out
Page 35

Synopsis Latest Version

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Synopsis Latest Version

Загружено:

Авторское право:

Доступные форматы

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

Software Requirement Specification

Team Guide Prof.R.T.Sakthidaran

Team Members S.S.Senthil S.Kishore kanna K.S.Ramkumar S.V.Balaji

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

Software Requirements Specification

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

Definitions, Acronyms and Abbreviations

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

Overall Description 2.1 Use-case model survey

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

2.2 Class Diagram

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

: End user open

: Birth/Income certicate/SC/ST forms

: Village administrative officer

final approval and sends to database

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

DECLINATION/REJECTION CASES CASE 1: REJECTION OF BIRTH/SC/ST FORMS BY VILLAGE ADMINISTRATIVE OFFICER

: End user open fills

: Birth/Income certicate/SC/ST forms

: Village administrative officer

submits open submitted forms

rejects and sends back to end user

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

CASE 2: REJECTION OF BIRTH/SC/ST FORMS BY REVENUE INSPECTOR

: End user open

: Birth/Income certi cate/SC/ST forms

: Vil lage administrative offi cer

open submitted forms primary approval

rejects and send back to end user

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

CASE 3: REJECTION OF BIRTH/SC/ST FORMS BY TAHSILDAR

: Birth/Income certicate/SC/ST forms

: Village administrative officer

: Revenue ins pector

open submitted form

rejects and sends back to end user

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

NORMAL FLOW FOR APPROVAL OF BC/OBC CERTIFICATE APPLICATION FORMS

: End user open

: BC/OBC Certificate forms

: Village administrative officer

final approval and sends to database

District Collectorate Office Information Integration Software Requirements Specification Ambidextrous

Version 1.0 Date: 15th oct 2007

: End user open fills