1.1.1 PurposeThis note is to establish a communication between the primary stakeholders in this project, namely,

State Information Commission Appellate Authorities PIO/Kiosk Citizens Assistance Public Info Officers Administrator

Methodology :

SOFTWARE LIFE CYCLE MODELS (SDLC)

Software Engineering is a layered technology. To solve actual problem in industry setting, a software

Engineer must incorporate a development strategy that encompass the process, the method and tools

layers. This strategy is often referred to as a process model or a Software Engineering Paradigm.

There are a series of steps through which the software project progresses during its development process.

These steps together constitute the Life Cycle Model of that project.

The life history of each project is different. Some projects spent much time in conceptual stage but some

are developed and implemented quickly then spend years in maintenance. So a choice needs to be made

depending upon the advantages and disadvantages of the various models and the requirement of our

project.

SDLC Model Used (WATERFALL MODEL)

Waterfall Model is the simplest model with each phase having a well defined starting and ending point,

with identifiable deliveries to the next phase.

The model consists of six distinct stages, namely:

Requirement Analysis Phase:

The problem is specified along with the desired service objective (goals) also the constraints are

identified.

Specification Phase:

The system specification is produced from the detailed definitions requirement analysis phase. This

document should clearly define the product “to do’s”.

System and Software design Phase:

The system specifications are translated into a software representation.

The software engineer at this stage is concerned with:

Data structure Software architecture Algorithmic detail, and Interface representations

The hardware requirements are also determined at this stage along with a picture of the overall system

architecture. By the end of this stage the software engineer should be able to identify the relationship

between the hardware, software and the associated interfaces. Any faults in the specification should

ideally not be passed ‘Down stream’.

Implementation and Testing Phase:

The designs are translated into the software domain also detailed documentation from the design phase

can significantly reduce the coding effort. Testing at this stage focused on making sure that any errors are

identified and that the software meets its required specification.

Integration and System Testing Phase:

All the program units are integrated and tested to ensure that the complete system meets the software

requirements. After this stage the Software is delivered to the customer. The software product is delivered

to the client for acceptance testing.

Maintenance Phase:

This is usually the longest and the last stage of the software. In this phase the software is updated to meet

the changing customer needs, ability to accommodate changes in the external environment, correct errors

and oversights previously undetected in the testing phases, enhancing the efficiently of the software.

Updated Requirements

VerifyRequirements

Verify

Specification

Verify

Design

Verify

Implementation

Test

Integration

Test

Maintenance

Development

Maintenance

Product Deliverable

Phases in Waterfall Model

REASONS FOR CHOOSING WATERFALL MODEL:

In this model, a detailed checking is done at each and every step by software quality assurance (SQA)

group and also by the clients. That is why it involves less risk of rejection by clients.

It is very easy to understand and implement.

It is documentation driven, that is, documentation is produced at every stage.

Testing is inherent to every phase of the waterfall model. So there is no need for a separate testing

phase.

The feed back loops in this model allow for corrections to be incorporated into the model. For example a

problem in the design phase requires a ‘revisit’ to the specifications phase. When changes are made at any

phase, the relevant documentation should be updated to reflect that change

Data required & Data Collection Method:

Collection Method:- Data is being analyzed from the internet only. We have tried to cover all the features of the

administration, searching and request for information as available on the existing portals.

But the entire data is being used on the basis of an organization’s security needs.

Input and Output to Each Process

Request to obtain information’

(i)

User name Registration id

ii)

User name Complaint id

iii)

Designation information

Posted

iv)

PIO user name view public

Requests/personal info/forward request/reply

Registration

Complaint

Request information

Check account

v)

APIO username view requests

/personal info/forward request/reply

vi)

complaintid check

appeal status

vii)

ADMIN status

updated

(viii)

Appellate authorities complaints

(ix)

SIC Citizen /PIO

Check account

View appeal Status

Add/update Employee

REVIEW

ALERT MESSAGES

Online Registration Management:

Input – Citizen entry info Output – Citizen is registered. Data elements-fname, lname, email_id, phone, address

Visitor Information Management:

Input – citizen entry info Output – View citizen details. Data elements-fname, lname, request _applied, email_id, phone, address

Query Information Management:

Input – Enter questions Output – Answers for questions. Data elements-text

` FAQ Information Management:

Input – Enter questions Output – View answers. Data elements-question, answers

Discussion Forum Management:

Input – issue Output – solution to issue Data elements-question, answers

DFD LEVEL 0 : CONTEXT DIAGRAM

CHAPTER – 2

System Requirement Analysis

a) Identify Processc) Identify Data Elements in Each Input & Outputd) Procedure Used for converting Input to Outpute) Validation Rules usedf) Deficiencies of Existing System

WHAT IS SYSTEM ANALYSIS

System Analysis refers to the process of examining a business situation with the intent of improving it

through better procedures and methods Requirement analysis is the first technical step in portal process. It

is a process of discovery, refinement, modelling and specification. It is the systematic use of proven

principles, techniques, languages and tools for the cost-effective analysis, documentation and on-going

evolution of user needs and the specification of external behaviour of a system to satisfy those user needs.

The very first thing is the problem recognition. After the need of the project is identified the

implementation of the project is identified – who is going to use the system, what all are the points

needed in modelling the design of the system.

IDENTIFY PROCESSES

‘Request to obtain information’

Web portal would facilitate the information seeker amongst the citizens to submit an application

to obtain any information pertaining to any departments / corporations / officers & officials.

Processes:

CITIZEN REGISTRATION

COMPLAINT

INFORMATION REQUEST

PIO ACCOUNT

APIO ACCOUNT

USER ACCOUNT MAINTENANCE

EMPLOYEE ACCOUNT MAINTENANCE

APPELATTE AUTHORITIES

SIC

IDENTIFY THE DATA ELEMENTS

CITIZEN REGISTRATION1) REGID2) CITIZEN NAME3) ADDRESS4) PHONE5) EMAIL

COMPLAINT1) COMPLAINTID2) NAME3) ADDRESS4) PHONE5) CITIZEN6) PINCODE7) STATE8) CITY9) COMPLAINT10) REGID

INFORMATION REQUEST1) DESIGNATION.2) DEPARTMENT3) CITY4) REQUEST

PIO ACCOUNT1) EMP_ID2) NAME3) DPT_NO4) DESIGNATION5) SALARY6) DOJ7) COMPLAINT_ID8) STATUS

APIO1) EMP_ID2) NAME3) DPT_NO4) DESIGNATION5) SALARY6) DOJ7) COMPLAINT_IDUSER ACCOUNT MAINTENENANCECOMPLAINT_IDSTATUS

EMPLOYEE MAINTENANCE ACCOUNT 1) EMP_ID2) NAME3) DPT_NO4) DESIGNATION5) SALARY6) DOJ

APEALATTE AUTHORITIESREASONANOTHER COMPLAINT

SIC 1) EMP_ID 2) ALERT MESSAGE

IDENTIFY THE PROCEDURES/RULES/MATHEMATICAL

RELATIONSHIPS USED FOR CONVERTING INPUT INTO OUTPUT

Citizen Registration

1) Citizens approach offices of PIOs/a kiosk to request for information. 2) But they first need to register themselves 3) These requests are then entered into the system and a registration number is generated this unique number is given to the citizen.

Complaint

1) Only registered user can file complaint after login 2) When he file complaint a unique complaint id is generated . 3) It is stored into database and being compared with registration id

Information request 1) Only registered user can request for information. 2) Citizens have to select designation, department and city for which he wants information. 3) Now he can submit request which is being save in database.

PIO Account

1) He can view his personal information after login. 2) He view all the requests and complaints 3) And then check the appeal status of each request 4) And forward if required

APIO account.

1) He can view his personal information after login. 2) He view all the requests and complaints 3) And then check the appeal status of each request 4) And forward if required

User maintenance account

1) user can check his appeal status by entering complaintid. 2)At the same time pio/kiosk/apio can check and update appeal status by updating database.

Employee account maintenance

1) Administrator can add new employee 2) he can update and delete employee by making an entry into database

Appellate authorities

1) These authorities take charge after complaint is being rejected by pio/apio/kiosk. 2) A nominal fee is also collected.

SIC

1) This authority will alert the particular employee against which complaint is being filed.

IDENTIFY THE CONTROLS FOR I/O ACCESS, SECURITYNEEDS, VALIDATION RULES AND CODES USED FOR DATA ELEMENTS

1) Only registered user can login

2) Password checking is used for authorized citizen.

3) Only valid citizen can file complaint

4) Change password facility is provided.

5) Unique Id is allotted to different citizens

6) Different validation controls is used like

Required field Validator Required Expression Validator

Validations are provided in various fields like Phone no. - It should not be greater or less than 10 digits Email- It should have valid expressions defined in the control No blank- No field should be left blank

7) Auto increment is used for incrementing the REGID and COMPLAINTID.

8) If the complaint is rejected then user can file complaint against first appellate authority directly, he does not have to choose any other person.

Deficiencies of Existing System

1. Allow citizen to print the report or messages they get.

2. Allow citizen to submit there forms and message to all visitors of the site.

3. Make it more authenticating to access the data from the web..

4. Allow the employees of an organization to interact/communicate with each other without breaching the discipline factor of an organization.

5. Send files from one employee to the other.

6. Send official messages to their subordinates as well as their superiors, at various levels of the management, in the form of a mail.

7. Searching sufficient amount of study material for brushing up their concepts.

8. Maintain address book of employees and citizens.

9. Saving all the data as backup.

10. Maintaining data in more normalized form.

CHANGES THAT SHOULD BE MAKE IN THE CURRENT SYSTEM

NEW PROCESSESS THAT ARE INTRODUCED

Online Registration Management: In this process admin will manage the details of the Citizen that are registering online.

Visitor Information Management: In this process information related to online visitor Is managed like the sign up detail of the visitor.

Query Information Management: In this process queries asked by the visitor or the registered user is managed.

Form Information Management: In this process forms are downloaded by registered users to request information

Email Information Management: In this process email send by the visitors of the website, send by citizens and send by authorities are managed.

FAQ Information Management: In this process frequently asked questions are prepared with their answers and are updated periodically

Discussion forum management: In this authority can directly interact with citizen and understand their need.

INPUT AND OUTPUT OF THE NEW PROCESSESS

Online Registration Management:

Input – Citizen entry info Output – Citizen is registered. Data elements-fname, lname, email_id, phone, address

Visitor Information Management:

Input – citizen entry info Output – View citizen details. Data elements-fname, lname, request _applied, email_id, phone, address

Query Information Management:

Input – Enter questions Output – Answers for questions. Data elements-text

Email Information Management:

Input – Enter email Output – View email. Data elements-email FAQ Information Management:

Input – Enter questions Output – View answers. Data elements-question, answers

Discussion Forum Management:

Input – issue Output – solution to issue Data elements-question, answers

Deficiencies in existing system can be removed by:

1) Making all the work online

2) Making the login page for new citizen and for authorities

3) Making the authorized login.

4) Different tables are to be maintained containing different information

5) Making online registration facility.

6) .Citizens can participate in discussion forum.

7) Visitors will ask queries.

CHAPTER – 3

System Design

a) Physical Design b) Processing Logic c) Interface Design d) Database and File Design

Physical Design

An Entity-Relationship Model (ERM) is a relational schema database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a top-down fashion.It is a detailed representation of data for an organization and uses three main constructs i.e data entities, relationships and their associated attributes

SYMBOLS USED IN ER DIAGRAMS

ENTITY RELATIONSHIP DIAGRAM

________

ENTITY

WEAK ENTITY

RELATIONSHIP

IDENTIFYING RELATIONSHIP

ATTRIBUTE

KEY ATTRIBUTE

MULTIVALUED ATTRIBUTE

COMPOSITE ATTRIBUTE

A data-flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. It differs from the flowchart as it shows the data flow instead of the control flow of the program.

A data-flow diagram can also be used for the visualization of data processing and for modeling the requirements. It is also known as data flow graph or a bubble chart.

Important points

1) All names should be unique in DFD

2) It suppress logical decisions

3) Details are not required

4) It represent flow of data

SYMBOLS USED IN DATA FLOW DIAGRAMS

DFD LEVEL 0 : CONTEXT DIAGRAM

DATA FLOW

PROCESS

EXTERNAL ENTITY

DATA STORE

USE CASE DIAGRAM:

Update information

Register

View status

View information

Report generation

lodge complaint

login

Complaint forward

View alert messages

admin

PIO/APIO

citizen

Requestinfo

Reply Requests

Send alerts SIC

View complaints