SYSTEM REQUIRMENT SPECIFICATIONS FOR

ACCORD LEAGUE COUNSEL

PURPOSE OF THE SYSTEM

Dynamic Intranet plays a typical role and acts like a link between Units of an
Organization usually a corporate company.
The main objective of Information In charge is to introduce computerized
system in a widely spread organization which can be used as a resource for private
network, in order to fulfill the basic needs of an Organization like Information
sharing, Communication, Document Viewing as well as sharing. This also helps to
provide an easy and fast interface for the employees of an Organization to perform
their tasks quickly and efficiently.
By providing this entirely private network the information regarding the
Organization can be fetched from any corner of the world in a highly secured manner.

Features

Information sharing among employees in organization

Document viewing and sharing.

Managing Branches, Departments and Employees.

EXISTING SYSTEM

Time Delay: It is inefficient to deal with voluminous data manually in the

existing system, record stored in different files. It takes lot of time to
search different files.

Redundancy: As the branches are located in different locations, same files

have to be stored at all branches which involve lot of complications and
duplication works thus causes redundancy.

Accuracy: Since same data is compiled at different branches the

possibility of tabulating data wrong increases also data is more, validation
becomes difficult. It may result in loss of accuracy of data.

PROPOSED SYSTEM

Advantages:
Computerizing of an organization whose branches are situated at different locations
and connecting them through Intranet. This provides easy accessing of shared data and
provides communication channel between employees

Reliability: The project performs intended function with required

precision; hence this project is very reliable.

Feasibility: The project maintenance is very easy and modifications can

be made in the existing system in future. The project can interconnect to
other groups within the organization and also to all other branches under
integrated network.

Online Processing: The online processing of the project is very simple

following the existing manual method without changes and suitable
validation is provided for the easy and correct access of users.

Security: Security measures are taken to avoid mishandling of database.

Password restrictions are provided to enter into database. A correct
password only will access to the database

STUDY OF THE SYSTEM

The customers or policyholders reminders can be generated at lightening

speed just by query for the specific customers.

The information while it is collected can referentially be segregated into

their respective databases from single window, saving the time of multiple
data entries.

The customers policy premium payment status can be viewed in a

systematized manner by the Agents and cross verify the defaulters.

The claim status raised by a specific policyholder can be tracked very

clearly in a transparent manner, and checked until the claim is settled.

Above all the overall system can at any time provide consistent and
reliable information authenticated upon its operations.

FEASIBILITY REPORT:
Preliminary investigation examine project feasibility, the likelihood the system
will be useful to the organization. The main objective of the feasibility study is to test the
Technical, Operational and Economical feasibility for adding new modules and
debugging old running system. All system is feasible if they are unlimited resources and
infinite time. There are aspects in the feasibility study portion of the preliminary
investigation:

Technical Feasibility

Operation Feasibility

Economical Feasibility

Technical Feasibility
The technical issue usually raised during the feasibility stage of the investigation includes
the following:

Does the necessary technology exist to do what is suggested?

Do the proposed equipments have the technical capacity to hold the data required
to use the new system?

Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?

Can the system be upgraded if developed?

Are there technical guarantees of accuracy, reliability, ease of access and data
security?

Earlier no system existed to cater to the needs of Secure Infrastructure Implementation

System. The current system developed is technically feasible. It is a web based user
interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users.
The databases purpose is to create, establish and maintain a workflow among various
entities in order to facilitate all concerned users in their various capacities or roles.
Permission to the users would be granted based on the roles specified. Therefore, it
provides the technical guarantee of accuracy, reliability and security. The software and
hard requirements for the development of this project are not many and are already
available in-house at NIC or are available as free as open source. The work for the project
is done with the current equipment and existing software technology. Necessary
bandwidth exists for providing a fast feedback to the users irrespective of the number of
users using the system.
Operational Feasibility
Proposed projects are beneficial only if they can be turned out into information system.
That will meet the organizations operating requirements. Operational feasibility aspects
of the project are to be taken as an important part of the project implementation. Some of

the important issues raised are to test the operational feasibility of a project includes the
following:

Is there sufficient support for the management from the users?

Will the system be used and work properly if it is being developed and implemented?

Will there be any resistance from the user that will undermine the possible application
benefits?

This system is targeted to be in accordance with the above-mentioned issues. Beforehand,

the management issues and user requirements have been taken into consideration. So
there is no question of resistance from the users that can undermine the possible
application benefits.
The well-planned design would ensure the optimal utilization of the computer resources
and would help in the improvement of performance status.
Economic Feasibility
A system can be developed technically and that will be used if installed must still be a
good investment for the organization. In the economical feasibility, the development cost
in creating the system is evaluated against the ultimate benefit derived from the new
systems. Financial benefits must equal or exceed the costs. The system is economically
feasible. It does not require any addition hardware or software. Since the interface for this
system is developed using the existing resources and technologies available at NIC, There
is nominal expenditure and economical feasibility for certain.

NUMBER OF MODULES

Administrator

The activities that are carried out in this module are related to the maintenance of
master records such as Branch master, Department master and Employee master
for the entire organization. This module provides for performing addition,
deletion, updating and viewing the records in the master tables. This module also
provides viewing profiles of branches, departments and employees.

The master entries can only be accessed by the administrator of the organization.
The master entries provides facilities like view, add, delete, edit, update, cancel,
clear functionalities to the administrator to work on the master records which are
fetched from database. The respected changes will be reflected to the database
after saving.

Manager

The activities that are carried out in this module are related to document
viewing, document forwarding to employees, and document updating, document
deleting and conference. He receives documents created by employees. Manager
changes the document if there are any errors in the documents and forwards to
other employees. He can also view his profile to know the details. He can join the
conference to communicate with people in the Organization. He can also intimate
notifications while he was in conference.

Employee

The activities that are carried out in this module are related to document viewing,
document creation, document updating, document deleting and conference. He
can view his profile. He can create documents and submits it to manager for any
error rectification. He can view the documents forwarded by manager which are
created by other employees. He cannot delete or update documents which are
created by other employees. He can join conference to communicate with the staff
in Organization.

Functional Requirements of Admin:

1) Enter User id and password , if Those are Correct he Can Login into his Account.
2) After that he can add the Branch
3) He can add the Deportment
4) He can add the Employees
5) He can view all the Branches Information and he can edit and delete the Information
6) He can view all the Deportments Information and he can edit and delete the
Information
7) He can view all the Employees Information and he can edit and delete the Information
8) He will be Logout.
Functional Requirements of Employee:
1) Enter User id, password and designation, if those are correct he can Login into his
own account.
2) After that he see his own Profile.
3) He can add the Documents.
4) He can see all the Documents List, he can update and delete.
5) He can participated into online conferences also.
Functional Requirements of Manager:

6) Enter User id, password and designation, if those are correct he can Login into his
own account.
7) After that he see his own Profile.
8) He can add the Documents.
9) He can see all the Documents List.
10) He can participated into online conferences also.
Non Functional Requirements
All the other requirements which do not form a part of the above specification are
categorized as Non-Functional Requirements.
A system may be required to present the user with a display of the number of records
in a database. This is a functional requirement.
How up-to-date this number needs to be is a non-functional requirement. If
the number needs to be updated in real time, the system architects must ensure that
the system is capable of updating the displayed record count within an acceptably
short interval of the number of records changing.
Sufficient network bandwidth may also be a non-functional requirement of a system.
Other examples:

Accessibility

Availability

Configuration Management

Documentation

Extensibility (adding features, and carry-forward of customizations at next major

version upgrade)

Maintainability

Operability

Performance

Portability

Quality (e.g. Faults Discovered, Faults Delivered, Fault Removal Efficacy)

Reliability

Response time

Robustness

Scalability (horizontal, vertical)

Security

Testability

Usability by target user community

Accessibility is a general term used to describe the degree to which a product, device,
service, or environment is accessible by as many people as possible. Accessibility can
be viewed as the "ability to access" and possible benefit of some system or entity.
Accessibility is often used to focus on people with disabilities and their right of
access to the system.

Availability is the degree to which a system, subsystem, or equipment is operable and

in a committable state at the start of a mission, when the mission is called for at an
unknown, i.e., a random, time. Simply put, availability is the proportion of time a
system is in a functioning condition.
Expressed mathematically, availability is 1 minus the unavailability.

Configuration management (CM) is a field that focuses on establishing and

maintaining consistency of a system's or product's performance and its functional and
physical attributes with its requirements, design, and operational information
throughout its life.
Documentation may refer to the process of providing evidence ("to document
something") or to the communicable material used to provide such documentation
(i.e. a document). Documentation may also (seldom) refer to tools aiming at

identifying documents or to the field of study devoted to the study of documents and
bibliographies

Extensibility (sometimes confused with forward compatibility) is a system design

principle where the implementation takes into consideration future growth. It is a
systemic measure of the ability to extend a system and the level of effort required to
implement the extension. Extensions can be through the addition of new functionality
or through modification of existing functionality. The central theme is to provide for
change while minimizing impact to existing system functions.

Maintenance is the ease with which a software product can be modified in order to:

correct defects

meet new requirements

make future maintenance easier, or

cope with a changed environment;

Operability is the ability to keep equipment, a system or a whole industrial

installation in a safe and reliable functioning condition, according to pre-defined
operational requirements.
In a computing systems environment with multiple systems this includes the ability of
products, systems and business processes to work together to accomplish a common
task.
Computer performance is characterized by the amount of useful work accomplished
by a computer system compared to the time and resources used.
Depending on the context, good computer performance may involve one or more of
the following:

Short response time for a given piece of work

High throughput (rate of processing work)

Low utilization of computing resource(s)

High availability of the computing system or application

Fast (or highly compact) data compression and decompression

High bandwidth / short data transmission time

Portability is one of the key concepts of high-level programming. Portability is the

software-code base feature to be able to reuse the existing code instead of creating
new code when moving software from an environment to another. When one is
targeting several platforms with the same application, portability is the key issue for
development cost reduction.
Quality: The common element of the business definitions is that the quality of a
product or service refers to the perception of the degree to which the product or
service meets the customer's expectations. Quality has no specific meaning unless
related to a specific function and/or object. Quality is a perceptual, conditional and
somewhat subjective attribute.
Reliability may be defined in several ways:

The idea that something is fit for purpose with respect to time;

The capacity of a device or system to perform as designed;

The resistance to failure of a device or system;

The ability of a device or system to perform a required function under stated

conditions for a specified period of time;

The probability that a functional unit will perform its required function for a

specified interval under stated conditions.

The ability of something to "fail well" (fail without catastrophic consequences

Response time perceived by the end user is the interval between

(a) The instant at which an operator at a terminal enters a request for a response from
a computer and
(b) The instant at which the first character of the response is received at a terminal.
In a data system, the system response time is the interval between the receipt of the
end of transmission of an inquiry message and the beginning of the transmission of a
response message to the station originating the inquiry.
Robustness is the quality of being able to withstand stresses, pressures, or changes in
procedure or circumstance. A system or design may be said to be "robust" if it is
capable of coping well with variations (sometimes unpredictable variations) in its
operating environment with minimal damage, alteration or loss of functionality.
The concept of scalability applies to technology and business settings. Regardless of
the setting, the base concept is consistent - The ability for a business or technology to
accept increased volume without impacting the system.
In telecommunications and software engineering, scalability is a desirable property
of a system, a network, or a process, which indicates its ability to either handle
growing amounts of work in a graceful manner or to be readily enlarged.
Security is the degree of protection against danger, loss, and criminals.
Security has to be compared and contrasted with other related concepts: Safety,
continuity, reliability. The key difference between security and reliability is that
security must take into account the actions of people attempting to cause destruction.
Security as a state or condition is resistance to harm. From an objective perspective,
it is a structure's actual (conceptual and never fully knowable) degree of resistance to
harm.

Testability, a property applying to an empirical hypothesis, involves two

components: (1) the logical property that is variously described as contingency,
defeasibility, or falsifiability, which means that counter examples to the hypothesis
are logically possible, and (2) the practical feasibility of observing a reproducible
series of such counter examples if they do exist. In short it refers to the capability of
an equipment or system to be tested

Usability is a term used to denote the ease with which people can employ a particular
tool or other human-made object in order to achieve a particular goal. In humancomputer interaction and computer science, usability often refers to the elegance and
clarity with which the interaction with a computer program or a web site is designed.

SDLC METHODOLOGY USED

Object Oriented Analysis and Design (OOAD) is the model, chosen to
design and develop the proposed system.
Features of OOAD:

It users Objects as building blocks of the application rather functions

All objects can be represented graphically including the relation between

them.

All Key Participants in the system will be represented as actors and the
actions done by them will be represented as use cases.

A typical use case is nothing bug a systematic flow of series of events which
can be well described using sequence diagrams and each event can be
described diagrammatically by Activity as well as state chart diagrams.

So the entire system can be well described using OOAD model, hence this
model is chosen as SDLC model.

INPUT DESIGN
Input design is a part of overall system design. The main objective during the input
design is as given below:

To produce a cost-effective method of input.

To achieve the highest possible level of accuracy.

To ensure that the input is acceptable and understood by the user.

INPUT STAGES:
The main input stages before the information gets stored in the database media:
Data recording
Data transcription
Data conversion
Data verification
Data control
Data transmission
Data validation

 Data correction

OUTPUT DESIGN
Outputs from computer systems are required primarily to communicate the results of
processing to users. They are also used to provide a permanent copy of the results for
later consultation. The various types of outputs in general are:

External Outputs, whose destination is outside the organization,.

Internal Outputs whose destination is with in organization and they are the

Users main interface with the computer.

Operational outputs whose use is purely with in the computer department.

Interface outputs, which involve the user in communicating directly with

The outputs were needed to be generated as a hard copy and as well as queries to

be viewed on the screen. Keeping in view these outputs, the format for the output is
taken from the outputs, which are currently being obtained after manual processing. The
standard printer is to be used as output media for hard copies.

ARCHITECTURAL FLOW
The current application is being developed by taking the 3-tier architecture as a
prototype. The 3-tier architecture is the most common approach used for web applications
today. In the typical example of this model, the web browser acts as the client, IIS

handles the business logic, and a separate tier MS-SQL Server handles database
functions.
Although the 3-tier approach increases scalability and introduces a separation of
business logic from the display and database layers, it does not truly separate the
application into specialized, functional layers. For prototype or simple web applications,
the 3-tier architecture may be sufficient. However, with complex demands placed on web
applications, a 3-tiered approach falls short in several key areas, including flexibility and
scalability. These shortcomings occur mainly because the business logic tier is still too
broad- it has too many functions grouped into one tier that could be separated out into a
finer grained model.

The proposed system can be designed perfectly with the three tier model, as all
layers are perfectly getting set as part of the project. In the future, while expanding the
system, in order to implement integration touch points and to provide enhanced user
interfaces, the n-tier architecture can be used. The following diagram will represent the
typical n-tier architecture.

CONTEXT LEVEL DFD