Assignment Cover Sheet

Qualification Module Number and Title

Higher National Diploma in Computing & System Analysis & Design- Sri Lanka COVID-19
Software Engineering Information Management System (SLCIMS)
Student Name & No. Assessor
H.M.H.S.Thilakarathna / KDHDCSE 51-05 Mr. Induranga De Silva

Hand out date Submission Date

Assessment type Duration/Length of Weighting of Assessment

Coursework Assessment Type 100%
4 weeks

Learner declaration

Marks Awarded
First assessor

IV marks

Agreed grade

Signature of the assessor Date

1
 FEEDBACK FORM
INTERNATIONAL COLLEGE OF BUSINESS & TECHNOLOGY
Module: System Analysis and Designing
Student: H.M.H.S.Thilakarathna
Assessor: Induranga De Silva
Assignment: Sri Lanka COVID-19 Information Management System (SLCIMS)

Strong features of your work:

Areas for improvement:

Marks Awarded:

2
Task (1) contains 20 marks.

Marks Marks obtained

Criteria by the student

Out of 20 for the answer

provided
Fail •

Provide clear idea about the organization to

which the information system is proposed based 0-8
on vision, mission, objectives, and goals of the
organization.

Pass
• Provide clear idea about the organization to
which the information system is proposed based
on vision, mission, objectives, and goals of the 8-12
organization.
• Management hierarchy of the organization is
included

Good •
Provide clear idea about the organization to
which the information system is proposed based
on vision, mission, objectives, and goals of the
organization.
• Management hierarchy of the organization is
included

• Description of the selected one of current systems

& its nature of operation

3
• (Computerized/ manual/ Semi Computerized) 12-14
have been done that belongs to a specific
department/functional process of the
organization.

Explanation has been done based on main

objectives expected by the organization from the
selected current system.

4
Excellent
• Provide clear idea about the organization to which the
information system is proposed based on vision, mission,
objectives, and goals of the organization.
• Management hierarchy of the organization is
included

• Description of the selected one of current systems & its

nature of operation (Computerized/ manual/ Semi
Computerized) have been done that belongs to a specific
department/functional process of the organization.

• Explanation has been done based on main objectives

expected by the organization from the selected current
system.

• Justification has been done based on the purpose &

relevancy of the tool/s selected for gathering information.
14-20
• Samples of the Questionnaire & Interviews attached.

• The sample questioner contains open type & close type

questions in order to specifically gather information
relevant to current system.

• Standard questionnaire model like Pyramid, Funnel or

Diamond has been used to prepare questionnaire.

• At least economic, technical, operational, legal feasibility

study explained based on proposing system

• Proper justifications have provided for system adaptation

based on feasibility study.

5
Task (2) contains 20 marks.

Marks Marks obtained

Criteria by the student

Out of 20 for the answer

provided
Fail •

System Development life cycle explained such

as Communication, planning, Designing,
Development & Testing, Implementation but no 0-8
mapping has been done with system
implemented.

Pass •
At least Five stages of the System Development
life cycle explained such as Communication,
planning, Designing, Development & Testing,
Implementation. 8-12

• Every stage has been mapped with proposing

system development & designing activities.

Good •
At least Five stages of the System Development
life cycle explained such as Communication,
planning, Designing, Development & Testing,
Implementation.
• 12-14
Every stage has been mapped with proposing
system development & designing activities.
• The description based on
Prescriptive,Incremental,Evolutionary,Agile &
Specialized Process Models

6
Excellent •

At least Five stages of the System Development

life cycle explained such as Communication,
planning, Designing, Development & Testing,
Implementation.
•
14-20
Every stage has been mapped with proposing
• system development & designing activities. The
description based on
Prescriptive,Incremental,Evolutionary,Agile &
Specialized Process Models
•
Justifications have been done based on the
qualities of the proposing system.

Task (3) contains 20 marks.

Marks Marks obtained

Criteria by the student

Out of 20 for the answer

provided
Fail •
Use ER diagrams to design data model of the
0-8
proposing system but some errors exists.

Pass Use ER diagrams to design data model of the

• proposing system.

• Find entities, Attributes, relationships, Primary

keys, foreign keys, different cardinalities,

7
 candidate keys, composite keys, and associate 8-12
entities.

Attributes, Entities, Relationships &

•
Cardinalities properly selected & illustrated.

• Write a data dictionary for the ER diagram.

Good
Use EER diagrams to design data model of the
• proposing system.

• Find entities, Attributes, relationships, Primary

keys, foreign keys, different cardinalities,
candidate keys, composite keys, and associate
entities.
12-14
• Attributes, Entities, Relationships &
Cardinalities properly selected & illustrated.

• Enhanced Entity Relationships have been

thought & illustrated.

• Write a data dictionary for the EER diagram.

Excellent
Use EER diagrams to design data model of the
• proposing system.

• Find entities, Attributes, relationships, Primary

keys, foreign keys, different cardinalities,
candidate keys, composite keys, and associate
entities.

• Attributes, Entities, Relationships &

Cardinalities properly selected & illustrated.

8
 • 14-20
Enhanced Entity Relationships have been
thought & illustrated.
•
Write a data dictionary for the EER diagram.

•
Entities’ Attributes described based on Data
Tyep,Size,Format,& Nature (Primary.Foreign,Non
Key)
•
Has been used standard format for the Data
dictionary.

Task (4) contains 20 marks.

Marks Marks obtained

Criteria by the student

Out of 20 for the answer

provided
Fail •
Draw context level Data Flow Diagram to
illustrate functional model of the proposing 0-8
system with some errors.

Pass •
Draw context level Data Flow Diagram to
illustrate functional model of the proposing
system.
• External Entitles, Main Information System &
Information Initial flow between External 8-12
Entities & Main Information System have been
identified & illustrated.

Proper Process & data flow labeling used

•
Good • Draw context level Data Flow Diagram to
illustrate functional model of the proposing
system.

9
 • External Entitles, Main Information System &
Information Initial flow between External
Entities & Main Information System have been
identified & illustrated.

• Draw Level 0 Data Flow Diagram to illustrate 12-14

functional model of the proposing system.
showing at least five different transaction
processes.

•
External Entities, Major Processes, Data
Storages & initial Data Flows & Intermediate
Data Flows in between them have been
Identified & illustrated.
•
Draw a Level 0 Data Flow Diagram to illustrate
functional model of the proposing system

considering detailed analysis.

• External Entities, Sub Processes, Data Storages

& initial Data Flows & Intermediate Data Flows
in between them have been Identified &
illustrated.

• Proper Process & data flow labeling used

Excellent
Draw context level Data Flow Diagram to illustrate
• functional model of the proposing system.

• Draw Level 0 Data Flow Diagram to illustrate

functional model of the proposing system. showing
at least five different transaction processes.

• External Entitles, Main Information System &

Information Initial flow between External Entities &
Main Information System have been identified &
illustrated.
In order to further explain internal logic of the
•
major processes’ of the information system,
Structured English, Decision Trees & Decision

10
 Tables properly used for DFD level 0 processes. 14-20
• Draw a Level 1 Data Flow Diagram to illustrate
functional model of the proposing system
considering detailed analysis.

• Proper Process & data flow labeling used

• Process specifications have been included using

standard process specification format

• Object type, Data Type, Data Inflow & Data Out

Flow have been described.

• Write a data dictionary for the DFD level 0 using

standard format.

• Top down designing technique & the bottom up

designing technique should be properly explained
considering the functional design.

Task (5) contains 20 marks.

Marks Marks obtained
Criteria by the student

Out of 20 for the answer

provided
Fail Poor conclusion has been provided without based 0-8
• on system’s functionalities.

11
Pass
• Conclusion should be given based on the
proposing information system’s functionalities
8-12
& those benefits for the organization’s goals to
achieve.

Good
Conclusion should be given based on the
• proposing information system’s functionalities
& those benefits for the organization’s goals to
achieve.

Explanation has been given by incorporating 12-14

•
BSO(Business System Options) and TSO
(Technical System Options) .

Clearly explain how does business system

•
options supported by technical system options

Excellent • Conclusion should be given based on the

proposing information system’s functionalities
& those benefits for the organization’s goals to
achieve.

• Explanation has been given by incorporating

BSO (Business System Options) and TSO
• (Technical System Options). 14-20

Clearly explain how does business system

• options supported by technical system options.

Future recommendations should be given based

on the possible enhancements of the proposing
information system.

Introduction

12
An extremely significant subject area in the context of information systems is system analysis
and design. How well the system investigation and designing activities are carried out throughout
the system development life cycle determines the long-term viability, validity, efficiency, and
correctness of information systems. For the aforementioned tasks, a system analyst must become
proficient in and use the finest tools available, such as entity relationship diagrams, data flow
diagrams, flowcharts, and diagrams in the Unified Modelling Language.

Software development teams may maintain product quality, monitor project progress, project
budget, and product nature to a better level of satisfaction by having a clear understanding of the
Software Development Life Cycle model stages and the specific responsibilities allocated to
those. For an information system project, choosing the optimal software development process
model is essential since the process model's systematic approach can determine the product's
success or failure.

Executive Summary
System Analysis & Design is a very important subject domain related to Information
systems. Information systems durability, Validity, efficiency & accuracy depends on how
well the system investigation & designing activities are accomplished during the system
development life cycle. This assignment is mainly done for the Sri Lanka COVID-19
Information Management System of the Ministry Of Health. This assignment includes all the
necessary information that the SLCIMS needed. By doing this assignment it was able to gain
these following;

1. Understand system designing methodologies, tools and the techniques.

2. Evaluate different systems development life cycle models.
3. be able to perform a systems investigation.
4. be able to design a solution using appropriate system design methodologies, tools
and the techniques.

Contents
Introduction....................................................................................................................................17
Executive Summary.......................................................................................................................17

13
Task 01...........................................................................................................................................21
Organization Name:...................................................................................................................21
Organization Introduction..........................................................................................................21
Organization LOGO:.................................................................................................................21
Vision:........................................................................................................................................21
Mission:......................................................................................................................................21
Organization Hierarchy..............................................................................................................22
Current System...........................................................................................................................23
Justification................................................................................................................................23
Information Gathering...............................................................................................................24
Interviewing...............................................................................................................................24
Interviewing is the meeting of two people for the purpose of exchanging information and ideas
through questions and responses. This exchange involves communication and leads to joint
understanding about a particular topic (wisestep, 2021).........................................................24
Questionnaires............................................................................................................................24
Observation................................................................................................................................25
Record review and secondary research......................................................................................25
Feasibility Report.......................................................................................................................26
A feasibility study can be thought of as a preliminary investigation that helps the management
to need selection about whether or not a study of the system should be realizable for
development or not ..................................................................................................................26
Economic feasibility.............................................................................................................26
Technical feasibility.............................................................................................................26
Operational feasibility.........................................................................................................26
It determines whether or not the system is operating effectively once it's developed and
implemented..........................................................................................................................26
Legal feasibility....................................................................................................................26
Task 02...........................................................................................................................................27
Systems Development Life Cycle (SDLC)....................................................................................27
Requirement Analysis................................................................................................................28
Planning.....................................................................................................................................28
Design........................................................................................................................................28
Software Development...............................................................................................................29

14
 Testing........................................................................................................................................29
Black box...............................................................................................................................29
White box...............................................................................................................................30
Deployment & Maintenances....................................................................................................30
Implementation..........................................................................................................................30
System Development Life Cycle (SDLC) models.........................................................................31
Waterfall Model...................................................................................................................31
V-Shaped Model........................................................................................................................32
Prototype model.........................................................................................................................33
Spiral model...............................................................................................................................33
Big Bang model.........................................................................................................................34
Agile model................................................................................................................................34
Suitable one for this Organization.............................................................................................35
Task 3.............................................................................................................................................35
EER Diagram.............................................................................................................................35
The Data Dictionary of the EER Diagram.............................................................................37
Task 04...........................................................................................................................................38
DFD Diagrams...........................................................................................................................38
Context Level........................................................................................................................38
Level 0.......................................................................................................................................39
Level 1.......................................................................................................................................40
Data Dictionary for Level 0.......................................................................................................41
Level 0 Process Specification From..........................................................................................43
Process specification form.........................................................................................................43
Process specification form.........................................................................................................44
Process specification form.........................................................................................................45
Process specification form.........................................................................................................46
Approach models.......................................................................................................................47
Top-Down and Bottom-Up Design Approach...........................................................................47
Top-Down Approach...........................................................................................................47
Down-Top approach model.......................................................................................................48
Different between BSO and TSO..............................................................................................49

15
 BSO........................................................................................................................................49
TSO........................................................................................................................................49
Conclusion and Recommendation.................................................................................................50
Conclusion.................................................................................................................................50
Recommendation.......................................................................................................................50
Gantt chart..................................................................................................................................51
51
References......................................................................................................................................51

Table of Figures

Figure 1 Ministry Of Health logo..................................................................................................22

Figure 2 Organization Hierarchy...................................................................................................23
Figure 3 Systems Development Life Cycle (SDLC).....................................................................28
Figure 4 EER Diagram...................................................................................................................37
Figure 5 Context Level..................................................................................................................40
Figure 6 Level 0.............................................................................................................................41
Figure 7 Level 1.............................................................................................................................42
Figure 8 Top-Down and Bottom-Up Design Approach................................................................49

Table of Table
Table 1 Waterfall Model................................................................................................................32
Table 2 V-Shaped Model...............................................................................................................33
Table 3 Prototype model................................................................................................................34
Table 5 Spiral model......................................................................................................................34
Table 6 Agile model.......................................................................................................................35
Table 7 The Data Dictionary of the EER Diagram........................................................................39
Table 8 Data Dictionary for Level 0..............................................................................................43
Table 9 TSO...................................................................................................................................50
Table 10 Gantt chart.......................................................................................................................52

Task 01

16
 Organization Name: Ministry Of Health

Organization Introduction:
The name was formally changed to Sri Lanka with the adoption of the new constitution in
1972. Over the years, the history of medicine in Sri Lanka has been shaped by the synthesis
of numerous internal and extrinsic influences, some of which were unique to the country.
Because it is an island, Sri Lanka is mostly immune to external pressures influencing
medicine. The British were deeply worried about the local population's health. Several
Governors expressed concern for the people's health in their presentations to the Legislative
Council.

Organization LOGO:

Figure 1 Ministry Of Health logo

Vision: A healthier nation that contributes to its economic, social, mental, and spiritual
development.
Mission: To contribute to the social and economic development of Sri Lanka by achieving the
highest attainable health status through promote, preventive, curative, and rehabilitative services
of high quality made available and accessible to the people of Sri Lanka.
 
Company Objectives:

 To empower the community for maintaining, promoting their health.

 To improve comprehensive health services delivery actions.
 To strengthen stewardship management functions.
 To improve the management of human resources.
17
 

Company Goals:

 To give technical guidance on health promotion policy formation, planning, and

programming through Advocacy, Behaviour Change Communication, Social
Marketing, and Community Mobilization.

 To assist the Department of Health Services and other health-related sectors in

carrying out various health initiatives through advocacy, behaviour change
communication, and social mobilization for health actions.

 To promote, support, and carry out health promotion program development,

implementation, monitoring, and evaluation in various settings.

 To raise public awareness of health issues through the media.

 To educate and empower the public on health concerns in order to give them more
control over their health and to enhance individual and community health.

 To promote and conduct research on community behaviour change and social

mobilization. (Ministry Of Health, 2022)

Organization Hierarchy

18
 Figure 2 Organization Hierarchy

Current System

The Ministry of Health uses an antiquated manual system. A manual system is an accounting
method in which records are kept by hand rather than through a system. Instead, details are
put in diaries, and disparate information is painstakingly compiled into a set of critical
reports. These systems have a high mistake rate and are significantly slower than
computerized systems. The HR department is still writing important reports in a book. Every
human resources officer has a book like this. When documents generated by manual
processes are misplaced, the effect on service delivery is also fairly visible, as patients'
irritation escalates and companies' reputations suffer.

Disadvantages of this manual system,

 Report creation is time-consuming and expensive.

 Inadequate security.
 Significant continuous employee training costs.
 There are no data backups.
 Mistakes in handwriting occur.

Justification

Nowadays, technology is advancing. As a result, all procedures will be converted into

computerized systems. So it's preferable if these organizations have a computerized system.
Computerized organization systems make it easy to retrieve, categorize, analyze, process,
store, and generate crucial reports. Everyone will eventually need to utilize this type of
system to organize and submit their information. The previous system did not adopt an
information system to extract, develop, and manage information relevant to the COVID-19
pandemic on the island, but the computerized system must benefit in this way.
Advantages: Data is protected, data backups are available, fewer human errors occur, less
time is spent, and staff efficiency is improved.

19
 After examining all of these factors, a computerized system appears to be the best fit for this
organization.
Information Gathering

Managing information entails acquiring and delivering necessary information as well as

incorporating it into project management activities and processes. The information-gathering
procedures are repetitive activities that are used to create and arrange data from a variety of
sources.
(GeneratePress, 2022)

Interviewing

The meeting of two people with the goal of exchanging information and ideas through questions
and responses is known as an interview. This exchange involves communication and results in a
shared understanding of a specific topic. (wisestep, 2022)

Questionnaires

A questionnaire is an analysis tool that consists of a series of questions designed to elicit

information from respondents. Questionnaires can be regarded of as a type of written interview.
(kamuni, 2018)

There are two main types

1. Open ended questionnaires

It is made up of questions that are simple to answer and right. These types of queries
might uncover issues and point you in the right direction for answers.

2. Close ended questionnaires

Closed-ended questions can only be answered with a limited number of options, but
quantitative data is simple to analyze.

20
 (Flatworld Solutions, 2022)

Close-ended questions

Would you suggest our system to others?

Do you enjoy the manual system?
Do you believe that storing data in books is secure?
Do you enjoy using computers?
How did you find our system?
Would you like to use our system again?
Do you believe this new system will make your job easier?

Open-ended questions

What is your function in this office?

What are the primary issues with the existing system?
What factors influenced your decision to use our system?
What are the advantages of a computerized system over the current system?
What do you think is the most significant aspect of our system?
How would you sum up your interaction with us?

Observation

This strategy can obtain information through noting and watching events, people, employees,
and items. This strategy aids in identifying present system requirements and what needs to be
added to the new system. (Betts, 2022)

Record review and secondary research

21
This method can identify the current system's flaws. We can use internal or external sources to
gather previously gathered information. (ucsd, 2022)

Feasibility Report

A feasibility study can be regarded of as a preliminary examination that assists management in

making a decision regarding whether or not a system study should be feasible for development.

Economic feasibility

When a manual system is replaced with a computerized system, the organization must bear
the financial cost. However, after the replacement, the organization can save money because
the computerized system does not require books, pens, or more space for storing books.
Additionally, the computerized system requires less crew than a manual system.

Technical feasibility

The goal of a feasibility technical is to determine whether or not a proposed solution is likely
to provide the desired business benefits, as well as to identify any hurdles or hazards that
could potentially effect solution viability, worth, or benefit.

Operational feasibility

It determines whether or not the system is running effectively once it has been built and
implemented.

Legal feasibility

For data processing and storage, the new system follows local data protection rules.
(tutorialspoint, 2022)

22
Task 02

Systems Development Life Cycle (SDLC)

The Software Development Life Cycle (SDLC) is a technique for creating high-quality software
that has well defined processes. In particular, the SDLC technique focuses on the subsequent
stages of software development.

1. Requirement analysis
2. Planning
3. Design
4. Software development
5. Testing
6. Deployment & Maintenances

Figure 3 SDLC

23
Requirement Analysis

The purpose of requirement analysis is to assess present challenges and validate strengths and
weaknesses. It is extremely beneficial to the team in understanding and correcting current issues.
The following individuals perform requirement analysis:

o Conducting user management interviews.

o Summarizing what you've learned.
o Estimating the project's scope.
o Recording the outcomes.

Risky problems are emitted when engaged in requirement analysis. The biggest disadvantage of
Sri Lanka's COVID-19 Information Management System is the likelihood of data loss and the
inability to locate the history of COVID-19 cases. It is possible to avoid or eliminate these issues
with the newly recommended solution. This system is extremely beneficial to the Ministry of
Health.

Planning

When planning software or a system, the team or person first evaluates the cost for the required
items to form the software and the resources required for the program to implement the studied
requirements, as well as the dangers that they will face in the future. This planning strategy
includes sub-plans to simplify risks. These sub-plans are recorded during the planning process.
This planning is carried out by recognizing the challenges that developed during the
requirements analysis.

Sri Lanka COVID-19 Information Management System is one example of such a scheme.

Design

24
This is the third stage of SDLC. This converts the software specifications into design
specifications. This design has been created in accordance with the specification. This
contributes to the overall software architecture. This must be done in the following stages:

 Create data entry techniques

 Create a human-computer interface
 Create system controls.
 Create a database and/or files.
 Create back-up processes.

The next phase is to build a software structure, which is simple because the prior step defined
government personnel, hospital staff, and third-party people's expectations and system
requirements. After completing the design, developers create a suitable design document known
as the Design Document Specification.

Software Development

This comes after the design process. This is the most time-consuming aspect of the entire system,
and the developers have the most responsibility since if the coding is incorrect, the entire system
will be incorrect. Development for the full software begins at this point. The developer must
respect the Organization's guidelines. Programmers utilize high-level languages such as C++, C,
Java, Pascal, and PHP, depending on the needs of the organization, after completing the
architecture (DB, API, etc.) and functions, the program is ready for testing.

Testing
After the software is completed and deployed at the testing location, the team or individual must
test the entire system to see how it functions. This is a must since the client requires it, and in
other words, the consumer requires its optimum functioning to be done. This takes a long time
since it must be checked extremely carefully. The major goal of testing is to detect problems,
which are referred to as BUGS. System testing is divided into two categories: the white box and
the black box.

25
  White box
This approach is used to locate system errors such as code statements, branches, pathways, or
conditions. This test is considered low-level testing, and it is performed by someone who is
familiar with programming.

 Black box
The tester is unaware of any internal system throughout the black box test. This strategy is used
to learn about system behavior through end-user prospecting.

If any bugs are discovered in the system after applying these two methods, the next step is to
solve the bugs, which is known as DEBUGGING.

Deployment & Maintenances

The SDLC concludes with software deployment and maintenance. The primary purpose of
software deployment is to get it into the production environment. However, many organizations
typically deploy it in various locations such as testing or staging. It is feasible to work with the
program before releasing it once it has been deployed into the production stage. This deployment
aids in identifying the software's last errors. Simply put, software maintenance is the managing
of the software after it has been launched. As the world changes, so must software, hardware,
and technology. Because of this issue, the Sri Lanka COVID-19 Information Management
System should also be upgraded. Aside from software updates, the following should be kept in
mind.

Bug fixing
Issues are reported as a result of some circumstances that were not tested at all.

Upgrade
26
Changing the application to a newer version of the software.

Enhancement
Adding additional functionality to existing software.

Implementation

Code the design into source code. A test report with mistakes is created using a test to arrange
process that includes test-related tasks such as test case preparation, testing criteria, and testing
resource allocation. Integrates the information system into its context and installs the new
system. (tutorialspoint, 2022)

System Development Life Cycle (SDLC) models

Various software development life cycle models have been established and designed, and they
are followed throughout the software development process. These models are known as Software
Development Process Models. To ensure success in the software development process, each
process model follows a unique set of procedures.

There are five prominent software development paradigms in use today:

i. Waterfall Model
ii. V-Shaped Model
iii. Prototyping Model
iv. Spiral Method
v. Big Bang Method
vi. Agile Method

27
Waterfall Model

The waterfall model is a linear sequential flow. Furthermore, this is the oldest, most certain,
and most straightforward software system development methodology. It is envisioned as a
constant downhill flow, similar to a waterfall, through the phases of software system
implementation. This indicates that any step of the development process can begin only after
the previous segment has been completed. The waterfall approach does not describe the
process for returning to the previous section to address changes in requirements. The
waterfall approach was the first and most frequently utilized approach for developing
software systems.

Advantages Disadvantages
It is simple to explain to users. Assumes that a system's requirements can
be frozen.
It's quite tough to return to any stage after
Approach based on structures it's ended.
Each phase has its own set of deliverables. It is difficult and costly to modify scope
with a little flexibility.
Verification at each level ensures that In addition to the precise plan, it was costly
errors/misunderstandings are detected and time-consuming.
early.
Activities and stages are well specified.
Aids in project planning and scheduling.

Table 1 Waterfall Model

V-Shaped Model

Instead of progressing down in a linear fashion, the process steps are curved upwards when
the implementation and coding sections create the characteristic V shape. The main

28
 difference between the v-shaped model and the waterfall model is the early test planning
within the v-shaped model.

Advantages
Simple and simple to use
Each step has distinct deliverables.
Because test plans are developed earlier in
the life cycle, the waterfall model has a
better likelihood of success.
When the criteria are simple, it works
nicely.
Verification and validation of the product
at the early stages of development.
Table 2
Disadvantages
The waterfall model is very rigid.
Scope adjustment is complex and costly.
Because the software is developed during
the implementation phase, no early
prototypes are created.
The model does not give a clear avenue
for problems discovered during the testing
phases.
It was costly and time-consuming, as well
as requiring a precise plan.
V-Shaped Model

Prototype model

The prototype model begins with gathering data about the system's requirements by meeting with
users and defining the goal of the software, determining needs, and so on. As a result, it's become
a highly popular model.

Advantages Disadvantage
The users participate actively in the This model is costly.
development.
Because this methodology includes a Requests can vary way too much.
functioning model of the system, users
gain a better grasp of the system under
development.
Errors can be discovered much earlier. Developers do not always prefer too much
client interaction.
Quicker user feedback leads to better Risk of insufficient necessary analysis due
solutions. to excessive prototype dependence.
Table 3 Prototype model

Spiral model

29
 The spiral model is a risk-driven process paradigm. This SDLC model assists the team in
implementing aspects of one or more process models such as waterfall, incremental,
waterfall, and so on. This paradigm combines the greatest features of the prototyping
approach and the waterfall model. The spiral process combines rapid prototyping and
concurrent design and development activities.

Advantages Disadvantages
Estimates become more realistic as work The finished product is expensive and takes
progresses because critical concerns are a long time to produce.
found earlier.
Early developer engagement To evaluate the risks and assumptions,
particular abilities are required.
Manages hazards and divides the system Customization limits reusability.
into phases.
. Table 4 Spiral model

Big Bang model

This paradigm focuses on all areas of software development and coding tools, yet it is also
simple and requires little to no planning. This model is appropriate for small-scale applications.

Advantages Disadvantages
Good instructional aid for newcomers or Not a food model for complex projects or
students. object-oriented ones.
Little or no planning needed. Can be very expensive if requirements are
misunderstood.
Very few resources needed. Poor model for long and protracted
projects.
Gives developers flexibility. Very high uncertainty and risk.
Table 5 Spiral model

Agile model

Agile approach is a concept that encourages continuous interaction between development and
testing throughout the SDLC process of any project. The Agile methodology divides the entire
project into small incremental builds. (tutorialspoint, 2022)

30
 Advantages Disadvantages
It is a very practical method to designing Not suitable for dealing with complex
applications. addictions.
Encourages collaboration and planning More sustainability risk, maintenance risk,
across boundaries. and extensibility risk.
Functionality can be readily established It will not work unless there is an overall
and proved. plan, an agile leader, and agile PM
practice.
It is primarily reliant on consumer
The infrastructural requirements are engagement, therefore if the customer is
modest. unclear, the team may be led astray.
Table 6 Agile model

Suitable one for this Organization

The agile model is the best fit for this case. Because this is a complex system that is difficult to
construct, this method allows developers to break big programs into smaller components,
allowing them to develop the system piece by piece. Developers can utilize prototypes as a
development tool to receive input on the system. The primary benefit of pursuing agile growth is
increased productivity inside the firm. The team has defined goals, a set schedule, and each team
member is aware of his or her specific responsibilities. The program's development is also
transparent and apparent. This model is the best fit for this case.

Task 3
EER Diagram

31
 Figure 4 EER Diagram

The Data Dictionary of the EER Diagram

Table Name Field Name Type and Size Primary Key ,
Foreign Key/Not
Null
1.Registration
Department RID Varchar (10) Primary
key/True
DOB Varchar (2) False/False
Age Varchar (30) False/False
Reason Varchar (40) False/False
Ward Varchar (20) False/False
PID Varchar (10) Foreign
Key/True

32
2.Patient PID Varchar (10) Primary key/True
Gender Varchar (3) False/False
FName Varchar (10) False/False
LName Varchar (20) False/False

Age Varchar (2) False/False

DOB Varchar (10) False/False
RID Varchar (10) Foreign Key/True

3.Doctor DID Varchar (10) Primary key/True

Age Varchar (2) False/False

DOB Varchar (10) False/False

FName Varchar (10) False/False

LName Varchar (20) False/False
Specializations Varchar (10) False/False

PID Varchar (10) Foreign Key/True

4.Medica Report MRID Varchar (10) Primary key/True

Drugs Varchar (10) False/False

Date Date(8) False/False

DID Varchar (10) Foreign Key/True

RID Varchar (10) Foreign Key/True
5.Administration TestID Varchar (10) Primary key/True
MRID Varchar (10) Foreign Key/True

Enter Varchar (40) False/False

Manage Varchar (100) False/False
Report_Document Varchar (40) False/False
6.Ministry of Health Ministry_Report_No Varchar (10) Primary key/True

TestID Varchar (10) Foreign key/True

33
 Reception Varchar (30) False/False

Manage Varchar (100) False/False

Analyst Varchar (100) False/False

Job_Role Varchar (30) False/False

7.NOCPCO Support Varchar (100) False/False
Report Varchar (100) False/False

8.Patient-Doctor PID Varchar (10) Primary key, Foreign

Key/True
DID Varchar (10) Primary key, Foreign
Key/True
Positive Text False/False
Negative Text False/False
9.WHO _ _ _
_ _ _
10.Ministry Of Defense

11.Case_Details Confirmed_Cases INT False/False

Active_Cases INT False/False
New_Cases INT False/False
Recovered_Cases INT False/False
Suspected_Cases INT False/False
Death_Cases INT False/False

34
 Table 7 The Data Dictionary of the EER Diagram

Task 04

DFD Diagrams

Context Level

Figure 5 Context Level

Level 0

35
 Figure 6 Level 0

Level 1

36
 Figure 7 Level 1

Data Dictionary for Level 0

Object Object Data Type and Sourc Data Type Destinati Description
Name Type Inflow Size e Outflow and on

37
 Size
1.Officer Extern Login Varchar Login Can control
al Info System login system
Entity
2.Login Proces Login Info String User Login Varchar Main Login to
s Info Menu System
(Process
1)
3.Main Proces Option Number Integer User Case Varchar Process A major
Menu s details, , 3, process
Display date/tim Process
Record, e, 4,
User integer Process
Manageme
5,
nt,
Log Process 6
out
4.Case Proces Add/Update/ Varcher,Da User Add/ Varchar Case Can
Details s Delete Case, te/ Update/ , details add/update/de
Case time, Delete date/tim lete records
Id ,feedback Integer Case, Case e,
Id integer
5.Display Proces Case Id, User Varcher,Da Case View Varchar User Can view all
Record s Id ,Feedback te/ detail details , case details
time, s, date/tim and user
Integer User e, details
Detail integer
s
6.User Proces Add/Update/ Varcher,Da User Add/ Varchar User Can
Managem s Delete Case, te/ Update/ , details add/update/de
ent Case time, Delete date/tim lete records
Id Integer Case, Case e,
Id integer
7.Log Out Proces User Id User Login Log
s page Out form
system
8.Case Storag Add/Update/ Varcher,Da Proce Record Varchar Process 4 Store all case
details e Delete record te/ ss 3 details, , details
time, Feedback date/tim
Integer e,
9.User Storag Add/Update/ Varcher,Da Proce User Varchar Process 1 Store all user
Details e Delete record te/ ss 5 Details, , Process 4 details
time, Feedback date/tim
Integer e,
Table 8 Data Dictionary for Level 0

Level 0 Process Specification From

38
 Process specification form.
Number: 1
Name: Login
Description: Login for System

Input data flow: User name and password

Output data flow: Success or error massage
Type of process: Subprogram/Function name:
Online Batch Manual
Process Logic:
If(User name = User name && Password = Password) = login successful;
Else If (Error massage)= log in fail;

End if;

Refer to: Name:

Structured English Decision table Decision tree

Unsolved issues:

39
 Process specification form.
Number: 2
Name: Main menu
Description: User can select four options.

Input data flow: Option number

Output data flow: Advance to four options
Type of process: Subprogram/Function name:
Online Batch Manual
Process Logic:
If(option number = 1) =‘Case Details’;

Else if(option number = 2) =‘Display record’;

Else if(option number = 3) =‘User management’;

Else if( option number = 4) =‘Log out’;

End if;

Refer to: Name:

Structured English Decision table Decision tree

Unsolved issues:

40
 Process specification form.
Number: 3
Name: Case Details
Description: Add/Update/Delete cases

Input data flow: Case details

Output data flow: Success or error massage
Type of process: Subprogram/Function name:
Online Batch Manual
Process Logic:
If(option = Add) = add new case;

Else if(option = Update)= Update case record;

Else if(option = Delete)= Delete case record;

End if;

Refer to: Name:

Structured English Decision table Decision tree

Unsolved issues:

41
 Process specification form.
Number: 5
Name: User Management
Description: Add/Update/Delete Users

Input data flow: User details

Output data flow: Success or error massage
Type of process: Subprogram/Function name:
Online Batch Manual
Process Logic:
If(option = Add) = add new user;

Else if(option = Update)= Update user record;

Else if(option = Delete)= Delete user record;

End if;

Refer to: Name:

Structured English Decision table Decision tree

Unsolved issues:

42
Approach models

Top-Down and Bottom-Up Design Approach

Both top-down and bottom-up methods of information processing and knowledge ordering are
utilized in a range of domains, including software, humanistic and scientific ideas, and
management and organization.

Top-Down Approach
The entire system is organized into a hierarchy of subsystems using the top-down design
technique. An activity description is utilized at the top level. This description is divided
between a structural description and behavioral descriptions of the components. This process
of breakdown is then repeated for the components until sufficiently simple components are
obtained. The end result is a functional description of the system. A top-down technique is
employed for a less advanced project. As a result, the top-down approach strategy is
inconvenient for Sri Lanka. COVID-19 Information Management System.

Sri Lanka COVID-19 Information Management System

Administration

Covid-19 Reports

43
 Bottom-Top approach model

Bottom-up project management is quickly gaining traction, especially in industries where

projects frequently include new difficulties that necessitate creative solutions. The corporate
National Operation Centre for Prevention still decides project goals in the bottom-up model,
but the Administration who will be executing the work is requested to provide comments on
how the project goals will be met.
The top-down approach is the most appropriate for developing this system. The main reason
for choosing this approach is the higher engagement of the Higher Authority, which can
improve morale and accountability. Additionally, as a result of employee higher engagement,
there is a lower risk of unexpected problems because Administration is aware of the Higher
Authority's capacity. Looking at all of the elements, the Down to Top Approach model is the
best fit for Sri Lanka's COVID-19 Information Management System (SLCIMS).

Figure 8 Top-Down and Bottom-Up Design Approach

(Malsam, 2022)

44
Different between BSO and TSO

BSO

This is intended to aid management in making an informed decision about the system. They
are produced and presented with a variety of business system options, each of which
describes the scope and features supplied by a particular development/implementation
strategy. Identify system solutions that meet the needed standards and from which the user
can select.

TSO

It simply refers to the entire technical environment in which the system can be implemented.
This will include an overview of hardware and software, as well as technical support plans.
Its primary goal is to identify and characterize all physical implementation approaches that
could be used to meet the feature definitions.

Processor i3 or higher
RAM 8GB or higher
VGA On board 4GB or higher
Storage 500 GB
OS Windows 10/7/8
Output Monitor
Printer
Projector
Speaker
Input Keyboard
Mouse
Scanners
Finger print scanners

Table 9 TSO

45
Conclusion and Recommendation

Conclusion

This decision has been reached in relation to the newly suggested COVID-19 cases. Sri Lanka's
COVID-19 Information Management System the Ministry of Health can save critical time by
utilizing this system, as well as evaluate, manage, and retain a large amount of essential
information without losing it. SLCIMS is a great time-saving system for the Ministry of Health.
The Ministry of Health can acquire basic information regarding COVID-19 patients by using this
SLCIMS. Organizational management can gain a thorough understanding of the new system, its
characteristics, aims, and features based on the information contained in this report. This paper
contains all information, diagrams, the Sri Lanka COVID-19 Information Management System
(SLCIMS) model, feasibility studies, and data collection methodologies. I hope you have a good
understanding of the new system.

Recommendation
It is difficult to provide advice about the just introduced system. Because the system should be
extremely well suited for the present time and cannot predict what the technology will be like in
the future. If a COVID-19 patient is at home, it is preferable to have his information in this
system as well. This system can also be used on mobile devices, allowing an administration
officer to accomplish his job on the go. Capable of creating a user interface for this system. As a
result, this method is extremely beneficial to the Ministry of Health. As a result, people receive
proper service, and the Ministry of Health can easily carry out its duties.

46
Gantt chart
October
Task Name Start Date End Date
1 18 19 2 21 2 23 2 25
7 0 2 4
Task 1 10/17/2022 10/18/2022

Task 2 10/19/2022 10/20/2022

Task 3 10/21/2022 10/22/2022
Task 4 10/23/2022 10/24/2022
Task 5 10/24/2022 10/25/2022

Table 10 Gantt chart

References
Betts, J., 2022. Examples of Observation. [Online]
Available at: https://examples.yourdictionary.com/examples-of-observation.html
[Accessed 18 October 2022].
Flatworld Solutions, 2022. WHAT ARE DIFFERENT TYPES OF QUESTIONNAIRES.
[Online]
Available at: https://www.flatworldsolutions.com/research-analysis/articles/different-types-
questionnaires.php
[Accessed 18 october 2022].
GeneratePress, 2022. Information Gathering Techniques and Process, Hacker must Know.
[Online]
Available at: https://www.cyberpratibha.com/information-gathering-techniques-and-process/
[Accessed 17 october 2022].
kamuni, j., 2018. Questionnaire: Definition, Examples, Design and Types | QuestionPro.
[Online]
Available at: https://medium.com/@jagadishkamuni/questionnaire-definition-examples-
design-and-types-questionpro-34c9e3f488b
[Accessed 04 april 2021].
Malsam, W., 2022. Top Down vs. Bottom Up Management: What’s the Difference?. [Online]

Available at: https://www.projectmanager.com/blog/top-down-vs-bottom-up-management

[Accessed 19 october 2022].
Ministry Of Health, 2022. Ministry Of Health. [Online]
Available at: http://www.health.gov.lk/moh_final/english/

47
[Accessed 17 october 2022].
tutorialspoint, 2022. SDLC - Quick Guide. [Online]
Available at: https://www.tutorialspoint.com/sdlc/sdlc_quick_guide.htm
[Accessed 18 october 2022].
tutorialspoint, 2022. System Analysis & Design - System Planning. [Online]
Available at:
https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_pl
anning.htm
[Accessed 18 october 2022].
tutorialspoint, 2022. System Development Life Cycle. [Online]
Available at:
https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_d
evelopment_life_cycle.htm
[Accessed 18 October 2022].
ucsd, 2022. Secondary Use Research. [Online]
Available at: https://irb.ucsd.edu/Secondary-Use-Research.shtml
[Accessed 18 October 2022].
wisestep, 2022. What is an Interview: Definition, Objectives, Types & Guidelines. [Online]
Available at: https://content.wisestep.com/what-is-an-interview/
[Accessed 18 October 2022].

48