SYSTEM
REQUIRMENT SPECIFICATIONS
OBJECTIVE:
q This project
deals with the medical equipment and drugs given to the Customers, claiming the
bills from the Insurance Companies used by the medical service providers.
q
By using this, project employees of different
organizations can’t cheat their management by claiming medical allowances
without consulting any hospital.
Existing
System:
In current situation
lot of corporate companies are tie-up with different hospitals for their
employee purpose. But they don’t have any interface to communicate with
hospital management whether that employee really consent that hospital or not. Lot of employees are applying for medical allowances with
out consulting any hospital. This is the major disadvantage on current scenario.
To avoid this problem we are going to introduce a web portal for the sake of
corporate companies and major hospitals called “Hospice Management of corporate sector”
Proposed
System:
This
is a project dealing with the computerization of services of Hospice Management
of corporate sector. This project deals with the medical equipment and drugs
given to the Customers, Claiming the bills from the Insurance Companies used by
the medical service providers.
In
the present system of the insurance Claims Management in the Corporate
Hospitals, the work related to the maintenance of Organizations, maintenance of
Claims pertaining to the Insurance companies, information about all sort of
medical services providing to the corporate employees, claim settlements & adjustments
against their services authorizing by the Insurance Companies and payments and
receipts are carried out manually. All sort of information pertaining to the
corporate organizations, Insurance Companies and settlement of various
financial transactions etc., is to be done manually. These types of procedures involve lot of
paper work and it will take a lot of time. All the Medicare Claims Management
work is carried out using physical strength.
Corporate
Hospitals are having thousands of customers under various organizations and
number of dependents for each customer. It is difficult to maintain all these
data manually. It will take lot of time to maintain these types of tasks and
required heavy man power. This is a project dealing with the computerization of
services of Hospice Management of corporate sector. This project deals with the
medical equipment and drugs given to the Customers, Claiming the bills from the
Insurance Companies used by the medical service providers.
Functional Requirements:
Modules: This application has been divided in
to four modules
1. Customer Details
2. Inventory
3. Accounts Module
4. Reports Module
1. Customer module: This is all about customers of this
portal which are belongs to various corporate organizations this module deals
with customer details and Insurance related Medicare Insurance claims. The
Inventory module deal with Drugs and Equipment flow from the vendor supplies to
the customer and on-hand availability. The Accounts module deals with Bills and
Claims of various Insurance Companies. The Database Management module deals
with the integration of all above module and managing the entire Database
System.
¨
Company Info: By using this functionality admin will add their
customer’s company details
¨
Customer Info: By
using this functionality admin will add all customer’s details
¨
Dependent Customer Info: By using this functionality admin will
add details of depends of that customer
¨
Insurance Company Info: By using this functionality admin will
add insurance details of customers.
¨
Claims Info: By using this functionality admin will
add insurance claim details of customer.
2. Inventory module:
This module is all about a
corporate hospital which are having tie-up with major corporate sectors. This
module is having following functionalities.
¨
Vendor Info: By using this functionality admin will
add hospital details
¨
Drugs Store: By using this functionality admin will
add drugs details which are given by selected medical firm.
¨
Equipment Details: By using this functionality admin will
add all equipment details which are used by hospital management to words
selected customers.
¨
Drug Issues: By using this functionality admin will
add issuing drug details along with customer details.
¨
Drug Return: By using this functionality admin will
add deleted drug items from the list.
3. Accounts module:
¨
Bill Generation: By using this functionality admin will
generate bills for each and every customer
¨
Credit Note: By using this functionality admin can
view over all bills of all customers.
4. Reports Module:
In this
module administrator will get different types of reports regarding customers
like Number of customers of this portal and bill details of all customers. This
module is controlled by administrator only.
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 i
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
SCOPE
OF THE PROJECT
This Document plays a vital role in
the development life cycle (SDLC) as it describes the complete requirement 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 2.2: 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
achive 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
·
Portabilility
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
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 hot 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 in the part of 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 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
database’s 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
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 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.
