Beruflich Dokumente
Kultur Dokumente
net/publication/320110839
CITATIONS READS
0 1,160
2 authors:
Some of the authors of this publication are also working on these related projects:
All content following this page was uploaded by Sanjog Sigdel on 29 September 2017.
1
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions & Acronyms
1.4 References
3 Specific Requirements
3.1 External Interface Requirements
3.4 Design Constraints
3.5 Software system attributes
3.6 Functional Requirements
3.7 Non-Functional Requirements:
4 System Evolution
2
1. Introduction
This section gives a scope description and overview of everything included in this SRS
document. Also, the purpose for this document is described and a list of abbreviations and
definitions is provided.
1.1 Purpose
The purpose of this document is to give a detailed description of the requirements for proposing
an efficient “E-Health Architecture for Nepal”. It will illustrate the purpose and complete
declaration for the development of system. This document is primarily intended for a customer’s
approval and as a reference for developing the demo version.
1.2 Scope
The title “E-Health Architecture for Nepal” itself describes its objective. E-Health Architecture
is a hardware and software-based integrated web architecture which aims to provide online
health facilities for Nepal. This architecture will help an organization launch any web-based
health program over the country.
Dashboard: A dashboard is the panel for any system which contains tools as softwares to
monitor and deploy services.
Dedicated Server: A dedicated server is a single computer in a network reserved for serving
the needs of the network
Health Facilities: Health facilities are places that provide health care. They include hospitals,
clinics, outpatient care centers, and specialized care centers, such as birthing centers and
psychiatric care centers.
1.4 References
[1] Software Requirements Specification, Computer Information Systems Program, Janusz
Zalewski, Ph.D. College of Business,Florida Gulf Coast University
[2] Software Engineering: A Practitioner’s Approach, Seventh Edition, 2010
[3] Software Engineering, Ninth Edition, Ian Sommerville, 2011
[4] Web Based Project Management System, Anne-Mai Adamson, 2010
[6] Software project management / Bob Hughes and Mike Cotterell, London
[7] eHealth Interoperability Framework, Version 1.1, National E-Health Transition Authority
Ltd, NEHTA managed specification, April 2012,
4
2 Description of Project
Hardware configuration
part simply enables
establishment of an
integrated server-client
architecture. This includes
establishment of a high
5
performance dedicated server in central unit of Ministry of Health and Population MoHP. Each
hardware components of health facilities all over country ranging from lower level health
facilities to the MoHP will be connected online which will be web hosted by some relevant
Internet Service Provider(ISP). A web portal also known as dashboard will be installed in the
central server. Any web based health applications can be launched from the server and all its
clients throughout the nation will easily be able to use it. Client side dashboard will only be able
to view the permitted applications and use them.
Lower level health facilities users are only concerned with limited objectives like data input to
the server. They will input all medical or patient related data to the server. To input data users
must be able to search and view their required application online in the repository.
Data engineers are only concerned with data and data operations. Data engineers will be
filtering the raw data. They will classify it from data sets. From the generated datasets; data will
be analysed using applications provided by the architecture. Then furthermore report generation
according to the necessity of high level managers is also done by the data engineers.
High Level Officers are only concerned with the use of the dashboard. High level officers are
also client-side users. They use the architecture to use certain components like report generating,
viewing and exporting tools.
Besides these four user characteristics, for the development of softwares and its stability:
Software Developers and Support Communities are also essential. They are responsible for
assessment activities and communicating with various stakeholders of the system. Details about
these users are described in APPENDIX 1
6
2.5 Constraints
The architecture is targeted to run all over the country. So being a huge system it needs to face
several constraints and limitations which may lag the performance of architecture. As Nepal has
a unique geography of hills and terrains, deployment of architecture will be a constraint. As the
architecture will be set up with government support, after the system is set up, skilled manpower
will also play key role in delivering the quality service to the users. As E-Health architecture is
about providing services online, we should make sure the power supply, internet, internet
bandwidth and communication with central server is always up and functioning. The architecture
will receive huge no. of data so the classification of applications, targeted user groups and
classification of data are some essential constraints to be considered throughout the development
and use of system.
7
3 Specific Requirements
This section contains all of the functional and quality of the system. It gives a detailed
description of the system and all its features.
8
The figure shown above is the interface of a dashboard. Almost all the interfaces like
UploadSoftware(), ViewSoftware(), GenerateReport(), DataExport(), SysAdmin() will be
accessed from the dashboard. It it the system administrator who assigns the access to each type
of users. From the dashboard all types of users will access the softwares. System Administrator
will upload a project, data engineers will export the data and prepare report and the high level
officials will view them. And all activities will be done through the Dashboard shown above.
UploadSofware()
This interface is accessible to system administrator who will upload E-Health Projects to the
architecture.
ViewSoftware()
Here all the software uploaded by system administrator is collected. Users will view application
only assigned to them.
GenerateReport()
This interface will be used mainly by Data Engineer to analyze data and produce report. Also
high level managers will see this interface.
9
Use Case Diagram: A use case diagram is shown below :
In above use case diagram, four level of users system administrator, lower level users, data
engineers and decision makers are displayed. With all users the way they access their own
customized dashboard is displayed.
Even though this architecture is hardware-software integrated web architecture, we will not be
designing any specific hardware interface to run the system. Our system is a web based system,
so we will be launching it in several computers online.
10
3.4 Design Constraints
This section includes the design constraints on the architecture caused by the hardware.
11
ID : FR4
TITLE : User Verification:
DESC : User should be able to verify them through their email. A link in the email
should be provided for the user to follow if he/she is logging for the very first time.
RAT : In order for a real user to register
DEP : FR1, FR3
12
ID : FR8
TITLE : Acquisition
DESC : The system should be able to discover critical information/knowledge required
by the the government or the health ministry.
RAT : In order for the system to acquire the data entered by the user
DEP : FR6, FR7
13
ID : FR12
TITLE : Maintenance
DESC : The system will keep receiving new health information and knowledge, and also
periodically removes what are replicated and outdated.
RAT : In order for the system to remove redundancy
DEP : FR8, FR9, FR10, FR11
Server Requirements
The server hardware specification depends on the amount of data to be processed and the
number of users accessing the server database. The specification of server usually
increases with increase in the number of end users. However, a general estimate for a
5000+ users sever is given below
14
No. of users : 5000 +
Processor : Dual Hexacore Xeon L5640 ( or better )
Memory : 32 GB +
Hardware : 15k SAS2 drives RAID 10
The above mentioned mobile requirements are not necessary but recommended hardware
requirement for the use of webportal.
15
4 System Evolution
The preliminary stage of E-Health Architecture, gives a high chance to evolve into better system
with many stable features in upcoming future. Gaining its stability, the system targets to
incorporate more hardware and software tools, security and software updates. With the evolution
of the system, it becomes more and more stable and shall become robust E-Health architecture in
Nepal.
Following are some new features which can be expanded in the architecture:
1. Present architecture focuses only in available internet facility, but in future the
architecture can provide internet facility of its own( Government as ISP).
2. Bandwidth allocation and routing feature can be integrated in future, so that data can be
available everywhere and reliable for every targeted user groups.
3. The architecture can incorporate documents and tools to teach users about the uses,
objectives and ways of troubleshooting them.
4. The system can also incorporate error reporting, error logging features with the help of
GUI.
16
APPENDIX 1: CONFORMITY ASSESSMENT ACTIVITIES AND
STAKEHOLDERS (CAAS)1
eHealth Interoperability Framework, Version 1.1, National E-Health Transition Authority Ltd,
1
17
View publication stats
Consistency is a characterisation of the logical coherence of the artefacts that are defined in the
specification viewpoints.
PHASE 1
After the architecture is approved, necessary hardwares as mentioned in section 3.4 Design
Constraints of this document will be setup. Hardware components like switch, router, LAN
cable, power backup dedicated server will be set up. Each and every components will be tested
and phase 2 release will begin. PHASE 1 will take maximum one month.
PHASE 2
In this phase user will fetch live data from the central server. User will test whether the
applications are installed and if they are working properly. At the same time system
administrator will monitor the performance of server. System administrator will add the
necessary applications and tools to be used by users. PHASE 2 will take two months to be
completed. This phase will face many errors and bugs. This phase will take more time if various
users will make errors.
18