SYSTEM REQUIREMENT SPECIFICATIONS
Existing System:
The
problem that we specify is that now days it is too difficult for both writing
and maintaining records manually. It takes much time for writing records
manually. Even there is chance of missing of Information before it is entered
to the Manual records. It may not update in time due to delay in one
transaction, which may affect the other. After our information has been entered
and if any mistakes are there then our transaction may not be valid which may
take some time or even a few days to rectify.
It is a
long process that takes more time and money. The authority has to keep the
details of each and every registered employee manually. They have to generate
pay slips for every Employee within time. Even they has to keep the duplicate
copy of reports generated because if some Employees won’t get their pay slips,
they should contact the authority directly to receive their pay slips, loans
etc.
Proposed System:
To overcome the above specified problem we
have introduced a software application, any user can operate this portal very
easily and it is very user friendly.
To register an
employee we need to login as a system administrator who will only have the
permission to add, delete and update the information. Hence it make easier for
the user to give attendance.
STUDY OF THE SYSTEM:
To provide flexibility to the users,
the interfaces have been developed that are accessible through a browser. The
GUI’S at the top level have been categorized as
- Administrative user interface
- The operational or generic user interface
The ‘administrative user interface’ concentrates on the consistent
information that is practically, part of the organizational activities and
which needs proper authentication for the data collection. These interfaces
help the administrators with all the transactional states like Data insertion,
Data deletion and Date updation along with the extensive data search
capabilities.
The ‘operational or generic user interface’ helps the end users of the
system in transactions through the existing data and required services. The
operational user interface also helps the ordinary users in managing their own
information in a customized manner as per the included flexibilities.
Functional
Requirements:
Number of Modules
The
project is divided into the following modules:
1.
HR module.
2. Projects Information
3.
Training program of employee
4.
Reports module
1. HR
Module
This
module is all about an administrator who is having full rights on this portal.
Administrator can do following operations.
¨Employee Information
¨Visa & Foreign travel details
¨Performance appraisal
Employee
Information:
By using this
functionality administrator can store employee details like name, designation,
department etc.
Visa &
Foreign travel details:
By using this
functionality administrator can maintain visa and foreign details of employee
who got onsite opportunities.
Performance appraisal:
By using this functionality
administrator can maintains all employee details who got appraisals from
organization.
2. Projects
Information:
By using this functionality
administrator can store employee project details like project name, project
duration etc.
3. Training
program of employee:
By
using this functionality administrator can maintain training program details of
employee like training on which technology and duration etc.
4. Report
Module
In this module
administrator will get different types of reports regarding employee like
Number of employee of organization and other related details of employee etc.
And this module is controlled by administrator only. Administrator can get the
reports like
¨
Department
wise reports
¨
Location
wise reports
¨
Seniority
wise reports
¨
Skill
set wise reports
¨
Visa
reports
¨ Project wise allocation reports
¨ Training reports
Software Engineering
Methodology:
Object
Oriented Analysis and Design (OOAD Standards)
Non-Functional Requirements:
Software requirements:
Operating System : Windows
Technology : Java/j2ee
(JDBC, Servlets, JSP)
Web Technologies : Html, JavaScript, CSS
Web Server : Tomcat
Database : Oracle
Software’s : J2SDK1.5, Tomcat 5.5,
Oracle 9i
Hardware
requirements:
Hardware Pentium based systems
with a minimum of p4
RAM 256MB (minimum)
Additional Tools:
HTML Designing : Dream weaver Tool
Development Tool kit : My Eclipse
Project Approach:
This Document plays a vital role in
the development life cycle (SDLC) as it describes the complete requirements of
the system. It is meant for use by the developers and will be the basic during
testing phase. Any changes made to the requirements in the future will have to
go through formal change approval process.
OOAD MODEL was being chosen because
all requirements were known beforehand and the objective of our software
development is the computerization/automation of an already existing manual
working system.
Fig: SDLC Model
The developer is responsible for:
·
Developing
the system, which meets the SRS and solving all the requirements of the system?
·
Demonstrating
the system and installing the system at client's location after the acceptance
testing is successful.
·
Submitting
the required user manual describing the system interfaces to work on it and
also the documents of the system.
·
Conducting
any user training that might be needed for using the system.
·
Maintaining
the system for a period of one year after installation.
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 can be listed as
below:
·
Data
recording
·
Data
transcription
·
Data
conversion
·
Data
verification
·
Data
control
·
Data
transmission
·
Data
validation
·
Data
correction
INPUT TYPES:
It is necessary to determine the
various types of inputs. Inputs can be
categorized as follows:
·
External
inputs, which are prime inputs for the system.
·
Internal
inputs, which are user communications with the system.
·
Operational,
which are computer department’s communications to the system?
·
Interactive,
which are inputs entered during a dialogue.
INPUT MEDIA:
At this stage choice has to be made
about the input media. To conclude about
the input media consideration has to be given to;
·
Type
of input
·
Flexibility
of format
·
Speed
·
Accuracy
·
Verification
methods
·
Rejection
rates
·
Ease
of correction
·
Storage
and handling requirements
·
Security
·
Easy
to use
·
Portability
Keeping in view the above description
of the input types and input media, it can be said that most of the inputs are
of the form of internal and interactive.
As
Input data is to be the directly keyed
in by the user, the keyboard can be considered to be the most suitable input
device.
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 User’s
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 system.
OUTPUT DEFINITION
The outputs should be
defined in terms of the following points:
§
Type
of the output
§
Content
of the output
§
Format
of the output
§
Location
of the output
§
Frequency
of the output
§
Volume
of the output
§
Sequence
of the output
It is not always desirable to print or
display data as it is held on a computer. It should be decided as which form of
the output is the most suitable.
For Example
·
Will
decimal points need to be inserted
·
Should
leading zeros be suppressed.
OUTPUT
MEDIA:
In the next stage it is to be decided
that which medium is the most appropriate for the output. The main
considerations when deciding about the output media are:
- The
suitability for the device to the particular application.
- The
need for a hard copy.
- The
response time required.
- The
location of the users
- The
software and hardware available.
Keeping in view the above description
the project is to have outputs mainly coming under the category of internal
outputs. The main outputs desired according to the requirement specification
are:
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.
Context Diagram:
|
 |
|
|
|||
 |
|||
|
|
Architecture flow:
 |
URL Pattern:
 |
Performance Requirements:
Performance is measured in terms of
the output provided by the application. Requirement specification plays an
important part in the analysis of a system. Only when the requirement specifications
are properly given, it is possible to design a system, which will fit into
required environment. It rests largely with the users of the existing system to
give the requirement specifications because they are the people who finally use
the system. This is because the
requirements have to be known during the initial stages so that the system can
be designed according to those requirements.
It is very difficult to change the system once it has been designed and
on the other hand designing a system, which does not cater to the requirements
of the user, is of no use.
The requirement specification for any
system can be broadly stated as given below:
·
The
system should be able to interface with the existing system
·
The
system should be accurate
·
The
system should be better than the existing system
The existing system is completely
dependent on the user to perform all the duties.
Feasibility Report:
Preliminary investigation examines
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 systems are feasible if they are given
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?
Operational
Feasibility:
Proposed projects are beneficial only
if they can be turned out into information systems, that will meet the
organization’s 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 additional hardware or
software.
