Unit - 07

Software Development Lifecycles

W. Renato croos
00196592
ESOFT metro campus Negombo
Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)
INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title BITEC Higher National Diploma in Computing

Assessor Internal Verifier

Unit 7 – Software Development Lifecycles
Unit(s)
Software Development Lifecycles Assignment
Assignment title

Student’s name
List which assessment criteria Pass Merit Distinction
the Assessor has awarded.

INTERNAL VERIFIER CHECKLIST

Do the assessment criteria awarded match

those shown in the assignment brief? Y/N

Is the Pass/Merit/Distinction grade awarded

justified by the assessor’s comments on the Y/N
student work?
Has the work been assessed Y/N
accurately?
Is the feedback to the student:
Give details:
• Constructive? Y/N
• Linked to relevant assessment criteria? Y/N
Y/N
• Identifying opportunities for
improved performance?
Y/N
• Agreeing actions?
Does the assessment decision need Y/N
amending?

Assessor signature Date

Internal Verifier signature Date

Programme Leader signature (if required)
Date
Confirm action completed
Remedial action taken
Give details:

Assessor signature Date

Internal Verifier
signature Date
Programme Leader
signature (if required) Date
Assignment Feedback Form
Student Name/ID

Unit Title Unit 7 – Software Development Lifecycles

Assignment Number Assessor

Date Received
Submission Date 1st submission
Date Received 2nd
Re-submission Date submission
Assessor Feedback:
LO1 Describe different software development lifecycles
Pass, Merit & Distinction P1 P2 M1 D1
Descripts
LO2 Explain the importance of a feasibility study
Pass, Merit & Distinction P3 P4 M3 D2
Descripts

LO3 Undertake a software development lifecycle

Pass, Merit & Distinction P5 P6 M3 M4 D3

Descripts
LO4 Discuss the suitability of software behavioural design techniques.

Pass, Merit & Distinction P7 M5 M6 D4

Descripts

Grade: Assessor Signature: Date:

Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

* Please note that grade decisions are provisional. They are only confirmed once internal and external moderation has taken place and grades
decisions have been agreed at the assessment board.

Assignment Feedback

3
W. Renato croos 00196592 Software development lifecycle
Formative Feedback: Assessor to Student

Action Plan

Summative feedback

Feedback: Student to Assessor

Assessor signature Date

Student signature Date

4
W. Renato croos 00196592 Software development lifecycle
 Pearson Higher Nationals in
Computing
Unit 7: Software Development Lifecycles
Assignment

General Guidelines

1. A Cover page or title page – You should always attach a title page to your assignment. Use
previous page as your cover sheet and make sure all the details are accurately filled.
2. Attach this brief as the first section of your assignment.
3. All the assignments should be prepared using a word processing software.
4. All the assignments should be printed on A4 sized papers. Use single side printing.
5. Allow 1” for top, bottom, right margins and 1.25” for the left margin of each page.

5
W. Renato croos 00196592 Software development lifecycle
Word Processing Rules

1. The font size should be 12 point, and should be in the style of Time New Roman.
2. Use 1.5 line spacing. Left justify all paragraphs.
3. Ensure that all the headings are consistent in terms of the font size and font style.
4. Use footer function in the word processor to insert Your Name, Subject, Assignment No, and
Page Number on each page. This is useful if individual sheets become detached for any reason.
5. Use word processing application spell check and grammar check function to help editing your
assignment.

Important Points:

1. It is strictly prohibited to use textboxes to add texts in the assignments, except for the
compulsory information. eg: Figures, tables of comparison etc. Adding text boxes in the body
except for the before mentioned compulsory information will result in rejection of your work.
2. Carefully check the hand in date and the instructions given in the assignment. Late submissions
will not be accepted.
3. Ensure that you give yourself enough time to complete the assignment by the due date.
4. Excuses of any nature will not be accepted for failure to hand in the work on time.
5. You must take responsibility for managing your own time effectively.
6. If you are unable to hand in your assignment on time and have valid reasons such as illness, you
may apply (in writing) for an extension.
7. Failure to achieve at least PASS criteria will result in a REFERRAL grade.
8. Non-submission of work without valid reasons will lead to an automatic RE FERRAL. You will
then be asked to complete an alternative assignment.
9. If you use other people’s work or ideas in your assignment, reference them properly using
HARVARD referencing system to avoid plagiarism. You have to provide both in-text citation and
a reference list.
10. If you are proven to be guilty of plagiarism or any academic misconduct, your grade could be
reduced to A REFERRAL or at worst you could be expelled from the course

Student Declaration

I hereby, declare that I know what plagiarism entails, namely to use another’s work and to present it as
my own without attributing the sources in the correct form. I further understand what it means to copy
another’s work.

1. I know that plagiarism is a punishable offence because it constitutes theft.

6
W. Renato croos 00196592 Software development lifecycle
 2. I understand the plagiarism and copying policy of Pearson UK.
3. I know what the consequences will be if I plagiarise or copy another’s work in any of the
assignments for this program.
4. I declare therefore that all work presented by me for every aspect of my program, will be my
own, and where I have made use of another’s work, I will attribute the source in the correct
way.
5. I acknowledge that the attachment of this document signed or not, constitutes a binding
agreement between myself and Pearson UK.
6. I understand that my assignment will not be considered as submitted if this document is not
attached to the assignment.

E208479@esoft.academy 01/11/2024
Student’s Signature: Date:
(Provide E-mail ID) (Provide Submission Date)

7
W. Renato croos 00196592 Software development lifecycle
Higher National Diploma in Business
Assignment Brief
Student Name /ID Number 00196592
Unit Number and Title Unit 7: Software Development Lifecycles

Academic Year 2023/24

Unit Tutor Mr. Vishmal gamage
Assignment Title Software Development Lifecycles Assignment

Issue Date

Submission Date

IV Name & Date

Submission format

This assignment consists of section A and section B.

The submission should be in the form of an individual report written in a concise, formal business
style using single spacing (refer to the assignment guidelines for more details). You are required to
make use of headings, paragraphs, and subsections as appropriate, and all work must be supported
with research and referenced using Harvard referencing system. Please provide in-text citation and a
list of references using Harvard referencing system.

The recommended word count is 4,500–5,000 words excluding annexures..

Minimum word count – 4,500
Maximum word count – 5,000

8
W. Renato croos 00196592 Software development lifecycle
 Unit Learning Outcomes:

By the end of this unit students will be able to:

LO1 Describe different software development lifecycles

LO2 Explain the importance of a feasibility study
LO3 Undertake a software development lifecycle
LO4 Discuss the suitability of software behavioral design techniques.

9
W. Renato croos 00196592 Software development lifecycle
 Assignment Brief and Guidance:

Section A

Case 1: In the wildlife ministry of Sri Lanka intend to develop a wildlife safari system which links
all the details of sanctuaries, wetland, and national parks across Sri Lanka. Through this the
government wants to track all the details of safari drivers and to count local and foreign visitors
entering these premises. The IT department of wildlife ministry have little experience on
developing this kind of system and they have two years to complete this project.

Case 2: “ChangeU” salon needs to have a system to track their bookings and they expect to
provide better customer service through the system. This is not incredibly challenging, and the
development team also has some early experience of this kind of a project. And the main
requirement of the client is to get a high-quality product without considering the budget and
time constraints.

Activity 1

Describe two sequential models and two iterative models you have learned which can be used to
design the systems explained in the 2 given cases. Explain how the risk is managed in each
software lifecycle model identified. Pick one case out of two and select the most suitable SDLC
model along with a discussion elaborating the reasons to select the particular SDLC model.

Which system out of the given two is most suitable to be developed using the waterfall model?
Assess the merits of applying the waterfall model to the system chosen by you.

Section B

Assume yourself as a system analyst assign to analyse and design a software system for an

10
W. Renato croos 00196592 Software development lifecycle
 organization of your choice. Investigate the business and system requirements using appropriate
tools/ techniques and develop the system design with the findings.

Activity 2

Explain and discuss the purpose and the components of the feasibility report that you have to
develop in order to check the feasibility of the chosen system. Assess the impact of different
feasibility criteria included in your report to investigate the software system.

Suggest , describe and compare two technical solutions for the proposed system and pick the most
suitable one with the justification for the selection.

Activity 3

Undertake the system investigation to identify business and system requirements using
appropriate investigation tools/ techniques and develop the software system specification for the
chosen system.

Evaluate the effectiveness of the system investigation process chosen by you to fulfil the
requirements of the users and analyse the effectiveness of the SDLC followed in order to trace
the system requirements. Discuss two approaches that can be used to improve the quality of the
system in the future.

Activity 4

Analyse the software behavioural tools and techniques that could be used for the proposed
system and discuss suing examples, the most suitable behavioural techniques that could be used
for your system.

Differentiate the finite state machine (FSM) and extended FSM providing an application for
each . Justify how the data driven software can improve the reliability and the effectiveness of
the software system proposed by you.

11
W. Renato croos 00196592 Software development lifecycle
12
W. Renato croos 00196592 Software development lifecycle
Grading Rubric

Grading Criteria Achieved Feedback

LO1 Describe different software development lifecycles

P1 Describe two iterative and two sequential software

lifecycle models.
P2 Explain how risk is managed in software lifecycle
models.
M1 Discuss using an example, why a particular lifecycle
model is selected for a development environment.
D1 Assess the merits of applying the Waterfall lifecycle
model to a large software development project.

LO2 Explain the importance of a feasibility study

P3 Explain the purpose of a feasibility report.

P4 Describe how technical solutions can be compared.

M2 Discuss the components of a feasibility report.

D2 Assess the impact of different feasibility criteria on a

software investigation.

13
W. Renato croos 00196592 Software development lifecycle
 LO3 Undertake a software development lifecycle
P5 Undertake a software investigation to meet a business need.

P6 Use appropriate software analysis tools/techniques to carry

out a software investigation and create supporting
documentation.

M3 Analyse how software requirements can be traced

throughout the software lifecycle.

M4 Discuss two approaches to improving software quality

D3 Evaluate the process of undertaking a systems investigation

with regard to its effectiveness in improving a software quality.

LO4 Discuss the suitability of software behavioural design techniques

P7 Discuss, using examples, the suitability of software

behavioural design techniques

14
W. Renato croos 00196592 Software development lifecycle
 M5 Analyze a range of software behavioural tools
and techniques.

M6 Differentiate between a finite state machine

(FSM) and an extended FSM, providing an
application of use for both

D4 Present justifications of how data-driven software can

improve the reliability and effectiveness of
software

15
W. Renato croos 00196592 Software development lifecycle
Table of Contents

LO1 Describe different software development lifecycles.......................................................21

Introduction to software development lifecycle............................................................................21

1.1 Sequential Model.......................................................................................................................25

1.2 Iterative model...........................................................................................................................28

1.2.1 Types of Iterative model......................................................................................................................29
1.3.1 Waterfall model Risk Management.....................................................................................................34

1.4 Agile model Risk Management.................................................................................................35

1.5 Spiral model Risk Management...............................................................................................38

1.6 Iterative Model Example - Case 1: Wildlife Safari System:..................................................39

1.8 The merits of applying the Waterfall lifecycle model to a large software development
project...............................................................................................................................................42

1.2 Implementation of a software development model in a Case study...............................44

1.5 Assessing the merits of applying the Waterfall lifecycle model between both case.............46

studies...............................................................................................................................................46

LO2 Explain the importance of a feasibility study................................................................48

2.1 Introduction about Hemas Holdings PLC..............................................................................48

2.2 Software System Development for PLC..................................................................................49

2.3 Purpose of Feasibility Report for Hemas Hospital.................................................................52

2.4 Evaluation of Technical Solutions for Hemas Hospital.........................................................53

2.5 The components of a feasibility report....................................................................................57

LO3 Undertake a software development lifecycle..................................................................64

3.1 Investigation Report for Wattala Hemas Hospital.................................................................64

3.1.1 Investigation Team..............................................................................................................................65
3.1.2 Scope...................................................................................................................................................66
3.1.3 Business Objectives.............................................................................................................................69
3.1.4 Existing Systems and Processes..........................................................................................................70
3.1.5 Market Analysis...................................................................................................................................71
3.1.6 Regulatory Requirements....................................................................................................................74

16
W. Renato croos 00196592 Software development lifecycle
 3.3 Managing Requirement Traceability During Software Development.................................86

3.4 Enhancing Software Quality: Exploring Two Vital Approaches..........................................89

LO4 Discuss the suitability of software behavioral design techniques.................................94

4.1 ERD for Hemas Hospitals Wattala..........................................................................................94

4.2 Use Case Diagram for Hemas Hospitals Wattala...................................................................97

4.3 Finite state machine (FSM) and Extended Finite State Machine (EFSM).........................100
4.3.1 Finite state machine (FSM)...............................................................................................................100
4.3.2 Extended Finite State Machine (EFSM)............................................................................................102
4.3.3 Differentiate between a Finite State Machine (FSM) and an Extended Finite State Machine (EFSM):
....................................................................................................................................................................104

4.4 dependability and efficacy of SPF (Special Provident Fund) software..............................105

4.4.1 Components related to data driven....................................................................................................107
4.4.2 justifications of driven software improve the reliability and effectiveness of SPF (Special Provident
Fund) web base software............................................................................................................................109

Reference:.............................................................................................................................111

17
W. Renato croos 00196592 Software development lifecycle
Table of Figures

Figure 1: Software development lifecycle stages.....................................................................21

Figure 2: Sequential Model......................................................................................................25
Figure 3: Waterfall model........................................................................................................26
Figure 4: V- model...................................................................................................................27
Figure 5: Iterative model..........................................................................................................28
Figure 6: RAD Model..............................................................................................................29
Figure 7: Incremental model....................................................................................................31
Figure 8: Big Bang model........................................................................................................32
Figure 9: waterfall model vs agile model.................................................................................37
Figure 10: Spiral model............................................................................................................38
Figure 11: Hemas Hospital Wattala.........................................................................................49
Figure 12: Benefits of feasibility report...................................................................................61
Figure 13: Software Analysis Tools.........................................................................................85
Figure 14: Test-Driven Development (TDD)..........................................................................90
Figure 15: Code Review...........................................................................................................91
Figure 16: ERD........................................................................................................................94
Figure 17: Use Case Diagram..................................................................................................97

18
W. Renato croos 00196592 Software development lifecycle
Table of tables

Table 1: Investigation Team.....................................................................................................66

Table 2: Advantages & disadvantages of FSM......................................................................101
Table 3: Advantages & disadvantages of EFSM...................................................................103
Table 4: Differentiate between FSM and EFSM....................................................................105
Table 5: dependability and efficacy of SPF (Special Provident Fund) software...................106

19
W. Renato croos 00196592 Software development lifecycle
Acknowledgment

I would like to extend my sincere gratitude to Mr. Vishmal Gamage, my instructor at ESoft
Metro Campus, for his invaluable guidance and support throughout the completion of this
assignment on the Software Development Lifecycle. His expertise and insights have been
instrumental in deepening my understanding of the concepts and practical applications of
software development methodologies. I am also grateful to the entire faculty and staff at
ESoft Metro Campus for providing a conducive learning environment that has greatly
contributed to my academic growth.
Thank you for your encouragement and for fostering an educational experience that continues
to inspire my passion for software development.

20
W. Renato croos 00196592 Software development lifecycle
LO1 Describe different software development lifecycles.
Introduction to software development lifecycle

Figure 1: Software development lifecycle stages

Source: (Data rob, Understanding the software development life cycle 2020)

The Software Development Life Cycle (SDLC) is a fundamental framework in software

engineering, providing a step-by-step methodology for designing, building, testing,
deploying, and maintaining software applications. A well-defined SDLC ensures that
development teams create high-quality software that aligns with user requirements and meets
industry standards. This framework emphasizes the SDLC's vital role and broad applicability
within software development.
The SDLC begins with the Requirement Gathering phase, where user needs and business
objectives are gathered, analyzed, and documented. This phase is essential for gaining a
comprehensive understanding of project expectations, as it sets the foundation for the entire
development process and aligns the software with stakeholder needs.
With requirements in hand, the Design phase follows. Here, software architects and designers
create a detailed blueprint for the system’s architecture, components, and interactions. This
blueprint is crucial, as it ensures that the system will be built with scalability, efficiency, and
maintainability in mind.

21
W. Renato croos 00196592 Software development lifecycle
The Development phase comes next, during which developers code the software according to
the design specifications. This stage underscores the importance of adhering to the predefined
design, enabling the development team to deliver a consistent, high-quality product.
After development, the software enters the Testing phase. At this stage, the application is
rigorously tested to identify and correct any defects or bugs. This phase is vital, as it ensures
the final product is stable, functional, and user-ready by addressing any issues before
deployment.
Upon successful testing, the software transitions to the Deployment phase, where it is
launched in the production environment. Deployment involves essential activities like
installation, configuration, and data migration, marking the software’s shift from
development to operational use.
Finally, the Maintenance and Support phase ensures the software remains effective and up to
date. This ongoing phase involves updates, improvements, and adaptations as user needs or
business conditions evolve.
By following each phase in the SDLC, development teams can create software that is robust,
aligned with user needs, and equipped to meet future requirements.

22
W. Renato croos 00196592 Software development lifecycle
Introduction to Case 1 - Development of the Wildlife Ministry's Safari System:
In Case 1, an exciting initiative is emerging within Sri Lanka's wildlife ministry,
aiming to showcase the captivating biodiversity found in the country’s national
parks, marshlands, and sanctuaries. This project envisions the creation of a
comprehensive wildlife safari system, with objectives that include tracking
safari drivers’ activities and accurately documenting the flow of both local and
international tourists into these pristine natural areas. However, this ambitious
endeavor presents a significant challenge: the IT department of the wildlife
ministry, which is responsible for delivering the project, lacks experience with
similar large-scale developments. Adding to the complexity, the project is
expected to be completed within a two-year timeline. Selecting an appropriate
lifecycle model for this endeavor will be crucial to its success, requiring careful
consideration of the project’s unique demands.

Introduction to Case 2 - Implementation of "ChangeU" Salon's Booking

System:

In Case 2, attention shifts to a specialized area where design and customer

experience take center stage. The "ChangeU" salon is eager to step into the
digital age by implementing an advanced booking system, enhancing both the
style and service quality it offers to clients. Unlike the complexity of Case 1’s
wildlife project, this task appears more straightforward, especially as the
development team already has experience with similar projects. The client’s
primary requirement is a top-quality result, with the added advantage of flexible
timelines and budget. This flexibility allows for a unique range of possibilities.
Choosing an optimal lifecycle model will be key to achieving the client’s vision
while maintaining the high standards that define the "ChangeU" brand.

23
W. Renato croos 00196592 Software development lifecycle
24
W. Renato croos 00196592 Software development lifecycle
1.1 Sequential Model

Figure 2: Sequential Model

Source: (Sequential development process. | download scientific diagram)

The sequential model is a development process where the entire system is built
through distinct stages, each following the previous one without overlap. In this
approach, each phase must be fully completed before advancing to the next,
providing a clear roadmap for development. Key phases typically include
requirement analysis, system design, implementation, testing, deployment, and
maintenance.
Examples of sequential models include the Waterfall Model and the V-Model.
The V-Model enhances the Waterfall approach by integrating validation and
verification stages alongside development phases, ensuring a strong alignment
between testing and requirements.

25
W. Renato croos 00196592 Software development lifecycle
This model is particularly advantageous for projects with well-defined and
stable requirements, as it promotes meticulous planning and structured progress.
However, its rigidity may limit adaptability, making it less suitable for projects
that require ongoing customer feedback or frequent changes.

Waterfall Model

Figure 3: Waterfall model

Source: (K, The waterfall model: A linear approach to software development 2023)

The Waterfall Model is a straightforward, structured approach to software development,

where each phase flows sequentially from the previous one. This linear progression makes
the process easy to understand, control, and document, making it ideal for projects with clear
requirements and minimal need for changes.
Typically, the model includes phases such as Requirements Gathering, System Design,
Implementation, Testing, Deployment, and Maintenance. One of its key advantages is the
emphasis on documentation, which enhances communication among team members and aids
in onboarding new staff.

26
W. Renato croos 00196592 Software development lifecycle
However, the Waterfall Model's inflexibility can pose challenges, as it is difficult to
accommodate changes once a phase is completed. This rigidity may hinder projects with
evolving requirements or those that require continuous user feedback, so teams should
carefully assess its suitability for their specific project needs.

V-Model

Figure 4: V- model
Source: (What is the V-model? (definition, examples))
The V-Model, also known as the Verification and Validation Model, emphasizes the
integration of development and testing stages to ensure thorough verification and validation
of the software. In this model, each development phase is directly paired with a
corresponding testing phase, allowing testing to commence as soon as each stage is
completed, continuing through to the final testing phase. The V shape of the model visually
represents the close relationship between development and testing activities.

This approach enhances the quality of the software by ensuring that requirements are
validated at every stage, reducing the likelihood of defects at later phases. The model
typically includes phases such as Requirements Analysis, paired with Acceptance Testing;
System Design, linked to System Testing; Implementation, associated with Integration
Testing; and Unit Testing, which corresponds to coding efforts.

27
W. Renato croos 00196592 Software development lifecycle
One of the significant advantages of the V-Model is its focus on early testing, which can lead
to more efficient development processes and higher-quality outcomes. However, similar to
the Waterfall Model, it can be inflexible when handling changing requirements. Therefore, it
is most effective in projects where requirements are well-defined and unlikely to change
significantly throughout the development lifecycle.
1.2 Iterative model

Figure 5: Iterative model

Source: (Jin, Software development framework - iterative model 2023)

The Iterative Model is a software development approach that starts with a basic
version of the system, which is then improved and expanded over multiple
cycles, or iterations, until the final product is achieved. Each iteration involves
revisiting the phases of development—such as planning, design, coding, and
testing—allowing the software to evolve progressively. With every cycle, the
application becomes more complex and feature-rich, incorporating user
feedback to refine and enhance the solution until it is ready for deployment.
This model is particularly beneficial because it allows teams to respond quickly
to changes and incorporate user feedback throughout the development process,
leading to a more user-centered final product. Two specific types of the Iterative
Model are the Agile Model and the Rapid Application Development (RAD)
Model.

28
W. Renato croos 00196592 Software development lifecycle
The Agile Model promotes flexibility and encourages adaptive planning, where
changes can be made at any stage of development based on continuous feedback
from stakeholders. It emphasizes collaboration and cross-functional teams,
allowing for quicker delivery of small, functional increments of the software.
The RAD Model, on the other hand, focuses on rapid prototyping and quick
iterations to create high-quality software in a shorter time frame. It prioritizes
user involvement throughout the process, resulting in applications that better
meet user needs and expectations.
Overall, the Iterative Model fosters a more dynamic and responsive
development environment, making it well-suited for projects where
requirements are likely to evolve, and user engagement is crucial.
1.2.1 Types of Iterative model
RAD Model

Figure 6: RAD Model

Source: (Rana, Rad Model - phases, Advantages & Disadvantages 2023)

The Rapid Application Development (RAD) Model is a software development

methodology that prioritizes quick prototyping and rapid feedback over lengthy planning and
development phases. Unlike traditional models, RAD emphasizes a fast-paced approach,
enabling teams to quickly build functional prototypes that can be refined based on user input.
This iterative process allows developers to adjust features and functionality throughout the
development cycle, resulting in software that closely aligns with user needs and expectations.

29
W. Renato croos 00196592 Software development lifecycle
Key Phases of the RAD Model:
1. Requirements Planning: This phase is a short, initial planning session where
developers, users, and stakeholders discuss project goals and identify the core
requirements. Unlike in traditional models, extensive documentation is minimized,
focusing instead on gathering essential user needs.
2. User Design and Prototyping: In this phase, rapid prototyping is used to create early
versions of the software. Users interact with these prototypes, providing feedback that
guides further development. Prototypes are repeatedly refined until the system meets
user expectations.
3. Rapid Construction: Here, developers quickly build the software based on user-
approved prototypes. This phase involves coding, testing, and integrating different
modules, allowing for frequent user reviews and modifications as needed.
4. Cutover (Deployment): The final, refined system is implemented in the production
environment. This phase includes final testing, data migration, training, and system
deployment, ensuring a smooth transition from prototype to operational software.

Overall, the RAD Model is an effective approach for projects where rapid delivery, user
involvement, and flexibility are priorities, and is particularly suited to projects where
requirements are likely to change or where there is a need for rapid iteration.

[Space left intentionally]

30
W. Renato croos 00196592 Software development lifecycle
Incremental Model

Figure 7: Incremental model

Source: (Sachan, Incremental model in software engineering 2023)

The Incremental Model is a software development approach where the system is built and
delivered in small, manageable parts called increments. Each increment adds functionality to
the existing system, gradually building up to the complete product. This model is particularly
useful for projects where requirements may evolve or for complex systems that can benefit
from early feedback on partially completed features.
Key Phases of the Incremental Model:
1. Requirements Gathering and Analysis: The essential requirements are identified
and divided into smaller sets that will be addressed in each increment. This allows
developers to focus on implementing specific features incrementally rather than
tackling the entire system at once.
2. Design and Development of Each Increment: For each increment, the system’s
design is refined, and coding is carried out based on the current set of requirements.
Each increment is a mini project, including all steps of design, development, and
testing.
31
W. Renato croos 00196592 Software development lifecycle
 3. Testing and Integration: Each increment is rigorously tested before being integrated
into the existing system, ensuring that newly added features work correctly with
previously developed parts. This step is repeated for every new increment.
4. Deployment: Once tested and integrated, each increment is released to users, who can
begin using the system and providing feedback.
5. Maintenance: After each increment is deployed, minor updates and fixes may be
applied as part of ongoing maintenance.
The Incremental Model is well-suited for medium to large projects with evolving
requirements, as it enables early delivery of functional parts, allowing users to interact with
the system and providing valuable insights for refining future increments.

Big Bang model

Figure 8: Big Bang model

Source: (GeeksforGeeks, Overview of big bang model 2021)

The Big Bang Model is a straightforward and informal software development approach
where all resources and efforts are directed toward development with little to no initial
planning. In this model, developers create software without a structured process or predefined
requirements, aiming to build the entire system at once. It relies on the idea that the final
requirements and system functionality will emerge during development, making it ideal for
small projects or proof-of-concept work.
Key Characteristics of the Big Bang Model:

32
W. Renato croos 00196592 Software development lifecycle
  Minimal Planning: There is little initial planning or structured requirement analysis.
Development starts based on vague or high-level ideas, and details are figured out
along the way.
 Flexible Approach: Since there is no structured phase-wise progression, changes can
be made at any point in development. This flexibility can be beneficial in small
projects where requirements are loosely defined or experimental.
 Single Deployment Phase: Typically, the entire system is completed and deployed in
a single release rather than through incremental or phased rollouts.

[Space left intentionally]

33
W. Renato croos 00196592 Software development lifecycle
1.3.1 Waterfall model Risk Management
The Waterfall Model employs a predictive risk management approach, focusing
on early risk identification and analysis. The project manager and team assess
potential risks by estimating both their likelihood and their possible impact on
the project. This proactive strategy enables the team to tackle identified risks
before they escalate into major issues. Typically, risk assessment and planning
happen before or at the project’s start, enabling the team to have a broad risk
outlook early on.

However, since Waterfall emphasizes front-loaded risk analysis, it can restrict

adaptability later in the project. Predicting all potential issues upfront is
challenging, and this approach can result in a somewhat inaccurate risk plan as
unforeseen risks arise. Additionally, the focus on following a set plan may
discourage team members from addressing new risks until they become
problematic.

Risk Management in the Waterfall Model

 Comprehensive Requirements Gathering: Waterfall emphasizes
detailed requirements collection at the project’s start. This approach
reduces the chance of misunderstandings or late-stage changes by
ensuring all requirements are clear from the beginning.
 Detailed Design and Planning: During the design phase, the team
focuses on creating a robust plan and design, assessing potential risks,
and creating contingency strategies for those identified early.
 Sequential Process: Waterfall’s linear workflow helps avoid scope creep
by completing each phase before moving to the next. However, this
structured progression may limit flexibility in adapting to changing user
needs.

34
W. Renato croos 00196592 Software development lifecycle
By front-loading risk management activities, the Waterfall Model provides a
structured approach to handling foreseeable risks, though it is less effective in
addressing evolving risks throughout the project lifecycle.

1.4 Agile model Risk Management

Agile methodology uses an adaptive approach to risk management, keeping

risks manageable by iteratively delivering system functionality. This enables the
Scrum Master and team to address potential issues as they arise. Continuous
monitoring of Scrum-based projects further minimizes the impact of individual
risks, as issues are handled swiftly and in small increments.
This method emphasizes identifying and assessing risks at the beginning of each
sprint, with a short-term planning focus. As the team progresses, they can detect
new risks in each phase, adapting their plans accordingly. Since risk
management is integrated directly into the development process, it streamlines
the approach and enhances success rates by avoiding unnecessary
complications.
By using this adaptive strategy, Agile teams incorporate risk management into
their daily activities, leading to better risk identification, evaluation, and a
higher likelihood of project success.
Risk Management in Agile Models
 Frequent Iterations: Agile relies on short development cycles and
iterative releases, providing a functional product increment at each stage.
This iterative nature enables continuous risk assessment and allows the
team to make timely adjustments.
 Client Involvement: Agile fosters constant collaboration with the client
or product owner, facilitating frequent feedback and interactions. This
ongoing communication helps identify and address risks as they appear,
adjusting smoother.

35
W. Renato croos 00196592 Software development lifecycle
  Risk Prioritization: Agile teams focus on risks that pose the highest
threat to the project, addressing them promptly while postponing lower-
priority risks. This prioritization ensures that the team tackles critical
issues early.
 Continuous Testing and Validation: Agile models incorporate ongoing
testing, enabling early detection and management of risks. By delivering
a functional product after each iteration, Agile reduces the risk of
significant failures at the project’s end.

Figure 9: waterfall model vs agile model

Source: (Eleks, Waterfall Project Management vs agile: Which is best for you? 2023)

36
W. Renato croos 00196592 Software development lifecycle
1.5 Spiral model Risk Management

Figure 10: Spiral model

Source: (Sitesbay.com, What is spiral model)

The Spiral Model places a strong emphasis on risk management, making it a central focus of
its development approach. Here’s how the model handles risks:
 Risk Analysis: At the start of each spiral phase, the team conducts an in-depth risk
analysis. This involves identifying potential risks, assessing their impact, and creating
mitigation strategies before moving forward.
 Iterative Prototyping: Prototyping and iterative design are key in the Spiral Model.
By developing prototypes and refining them with each cycle, the team can manage
uncertainties and reduce risks effectively.

37
W. Renato croos 00196592 Software development lifecycle
  Phased Development: The project is divided into smaller, manageable phases,
allowing for incremental risk management. This phased approach minimizes the
effect of unforeseen challenges as the project advances.
 Client Feedback: Frequent client input and reviews are essential to the Spiral Model,
enabling continuous risk management through regular customer engagement. This
process helps the team address changing requirements and emerging risks throughout
development.
Through these practices, the Spiral Model provides a structured, responsive approach to
managing risks in complex projects.

1.6 Iterative Model Example - Case 1: Wildlife Safari System:

Wildlife Safari System Project Using an Iterative Model: Case 1 Example

In this example, the Sri Lankan wildlife ministry aims to implement an advanced wildlife
safari system, integrating information from various sanctuaries, wetlands, and national parks
throughout Sri Lanka. Key goals include real-time monitoring of safari drivers and tracking
visitor data to improve oversight and management. The project, however, poses unique
challenges: it has been assigned to the ministry’s IT department, which has limited
experience with such large-scale, multifaceted projects, and it also needs to be completed
within a tight two-year timeframe. Selecting an iterative lifecycle model—particularly the
Agile framework—will be essential to navigate these complexities effectively.

Rationale for Choosing an Iterative (Agile) Approach

Given the project’s complexity and the team’s relative inexperience, the Agile approach is
well-suited to adapt to dynamic requirements and help the team manage its learning curve.
Here’s why Agile is appropriate:

 Managing Complexity and Changing Requirements: This system involves diverse

elements, from sanctuary locations to visitor monitoring. Agile's flexibility allows for
adaptations as the project progresses, with regular feedback integrated to address
evolving needs, regulations, or stakeholder input.
 Stakeholder Engagement and Continuous Feedback: Ongoing involvement of
stakeholders, such as sanctuary managers, government agencies, and potential

38
W. Renato croos 00196592 Software development lifecycle
 tourists, will be critical. Agile encourages regular feedback loops, ensuring that each
iteration aligns closely with the needs and insights of these key participants.
 Incremental Development for Early Value Delivery: Agile delivers progress in
incremental phases, allowing the IT team to release functional portions of the system
regularly. This approach fits well within the two-year deadline, ensuring that
stakeholders start benefiting from the system sooner rather than later.
 Supporting the Team’s Learning Curve: The iterative nature of Agile allows the IT
team to gain experience and improve over time. Each iteration offers a chance to
refine skills, address challenges, and learn from each cycle, gradually building
confidence and capability within the team.
 Adapting to New Requirements Flexibly: Agile’s flexibility is ideal for
accommodating changes driven by updated environmental policies, tourism needs, or
technology trends. For instance, if new conservation laws necessitate additional data
tracking, Agile enables adjustments in the upcoming iteration without disrupting the
entire project.

By leveraging Agile’s adaptability, iterative improvements, and close stakeholder

collaboration, the wildlife ministry's IT department can more effectively manage the
challenges and evolving demands of the wildlife safari system, increasing the likelihood of
success within the given timeframe.

39
W. Renato croos 00196592 Software development lifecycle
 Sequential Model Example - Case 2: "ChangeU" Salon Booking System
In Case 2, the "ChangeU" salon, known for its commitment to quality and customer
satisfaction, is advancing its digital services by implementing a booking system to streamline
appointments. This project is more straightforward compared to Case 1, as the development
team has previous experience with similar systems. The client’s primary goal is a high-
quality product that reflects the salon’s reputation, with no strict budget or time constraints.
For these reasons, the Sequential Model, or Waterfall Model, is an ideal choice for this
project.

Rationale for Choosing a Sequential Model (Waterfall)

The Waterfall Model is well-suited to the "ChangeU" salon project due to several key factors:

 Defined and Stable Requirements: The project has clearly defined requirements and
a stable scope, allowing the Waterfall model’s requirements-focused approach to
deliver accurately and precisely. The sequential nature ensures that every aspect is
documented before moving forward, creating a solid foundation for later stages.
 Experienced Development Team: With experience in similar projects, the team is
prepared to handle each phase efficiently. The Waterfall model’s structured, linear
flow complements the team's expertise, allowing them to build, test, and deploy the
system smoothly while maintaining high standards at each stage.
 Quality Focus: The client’s emphasis on quality aligns with the Waterfall model,
which involves rigorous documentation, structured development, and comprehensive
testing. This phase-by-phase focus ensures that the final product meets the high
standards expected by the salon.
 Flexibility in Time and Budget: With no budget or time pressures, the Waterfall
model’s thorough planning and structured execution are advantageous. This flexibility
allows the team to dedicate time to each phase, ensuring every detail is addressed and
the final product is fully tested.
 Clarity and Predictability: The model’s structured approach provides a predictable
timeline, which is valuable in projects with straightforward requirements. This clarity
ensures that both the team and client can track progress and maintain confidence in a
successful outcome.

40
W. Renato croos 00196592 Software development lifecycle
 The decision to use the Waterfall methodology for the "ChangeU" salon booking system
aligns with the project’s well-defined requirements, the team's experience, and the client's
focus on quality. The model’s structure supports high standards and predictability, making it
the ideal choice to deliver a polished product that meets the salon’s expectations.

1.8 The merits of applying the Waterfall lifecycle model to a large software development
project.

Using the Waterfall lifecycle model for a large-scale software project offers several key
advantages, although these benefits should be weighed against the project's specific needs
and constraints. Here are the main benefits of applying the Waterfall model in large software
development:
1. Clear Structure and Organization: The Waterfall model organizes development
into distinct phases—requirements, design, implementation, testing, deployment, and
maintenance. This step-by-step approach is particularly useful for large projects,
helping keep each stage well-defined and preventing confusion.
2. In-Depth Requirements Analysis: Waterfall emphasizes gathering and analyzing
requirements at the start of the project. For large projects, this comprehensive initial
planning ensures that all requirements are documented and fully understood, reducing
misunderstandings and the risk of missing critical specifications later.
3. Predictable Milestones and Timelines: The sequential nature of Waterfall makes
milestones and deliverables predictable. For large projects with significant
investments, this predictability aids project managers in estimating timelines, budgets,
and resource needs more accurately.
4. Defined Project Scope: Waterfall establishes a clear scope early on, essential in large
projects with multiple stakeholders and high complexity. A well-defined scope helps
manage expectations and avoids scope creep, where new features or changes disrupt
the project’s timeline and budget.
5. Detailed Documentation: The model emphasizes thorough documentation at every
phase. This is critical in large projects, where complexity requires comprehensive
records for future maintenance and updates. Detailed documentation supports team
understanding and ensures long-term project sustainability.

41
W. Renato croos 00196592 Software development lifecycle
These advantages make the Waterfall model a strong option for large-scale projects that
benefit from a structured, predictable approach with clearly defined phases and
comprehensive documentation.

[Space left intentionally]

42
W. Renato croos 00196592 Software development lifecycle
1.2 Implementation of a software development model in a Case study

The Agile methodology is ideal for Case 1, where the Sri Lankan wildlife
ministry seeks to create a wildlife safari system. Agile’s flexible, adaptive
nature suits projects where requirements are expected to evolve over time. In
this case, as the government gains a better understanding of the safari system's
needs and limitations, their requirements may change. Agile’s iterative
approach allows for regular assessment and adjustment of requirements,
ensuring the final system aligns closely with the ministry’s evolving needs.

Given the limited experience of the IT department in building such a system,

Agile’s incremental and iterative cycles also support continuous feedback and
learning. The team can develop the system in stages, addressing issues and
incorporating input from stakeholders, such as safari drivers and government
officials. This adaptability is essential for managing complex projects where
requirements may not be fully defined initially.

Agile further promotes close collaboration between cross-functional teams and

stakeholders. For the safari system, involving safari drivers and officials in
feedback sessions ensures the system meets their unique needs. This continuous
collaboration builds stakeholder ownership and leads to a more successful
implementation.

In Case 2, the Waterfall methodology is well-suited for ChangeU salon’s

booking system, as the development team has prior experience with similar
projects. Waterfall is a sequential, linear model where each phase must be
completed before the next begins. This structured approach works well for the
salon booking system, where the requirements are well-defined, and major
changes are unlikely during development.

43
W. Renato croos 00196592 Software development lifecycle
The Waterfall model provides a clear development roadmap, allowing for
detailed planning and execution of each phase. In this straightforward project,
Waterfall minimizes miscommunication by clearly defining each step from start
to finish.
The salon’s main goal is to achieve a high-quality product, and the Waterfall
model’s thorough approach to testing and validation supports this. Additionally,
the Waterfall model is suited to fixed budget and time constraints, which align
with the salon’s priorities. By providing a clear timeline and resource estimates,
Waterfall ensures the project’s progress is transparent from initiation through
deployment.

[Space left intentionally]

44
W. Renato croos 00196592 Software development lifecycle
1.5 Assessing the merits of applying the Waterfall lifecycle model between both case
studies.

Using the Waterfall Model for the Wildlife Safari System

The Waterfall model offers several benefits when applied to the wildlife safari system for
the Sri Lankan wildlife ministry. Its structured, sequential nature makes it a strong fit for
managing a large and complex project. The system involves integrating data from various
locations, such as sanctuaries, wetlands, and national parks across Sri Lanka, requiring a
systematic approach to development. Each phase of the Waterfall model—starting from
conception through to maintenance—aligns well with the ministry's need for a detailed and
thoroughly documented system.

The clear and stable requirements for the wildlife safari system make Waterfall a suitable
choice, as the government’s specifications are unlikely to change drastically over the
estimated two-year development period. This stability supports an in-depth planning phase at
the outset, resulting in more accurate predictions of resources, timelines, and potential risks.
Given the IT team’s limited experience with such a project, the Waterfall model’s phase-by-
phase structure serves as a valuable guide, ensuring each step is completed before progressing
to the next. This structure helps the team manage the learning curve and minimizes the risk of
overlooking essential stages in development.

Challenges of Using Waterfall for the Safari System

However, the Waterfall model’s rigidity presents certain challenges for the wildlife safari
system, which is complex and may require flexibility to address unforeseen issues.
Waterfall’s linear approach doesn’t easily accommodate changes mid-project, whereas
iterative methods like Agile are more adaptable in projects where requirements may evolve.

The Waterfall model typically involves limited stakeholder engagement until later stages. For
the safari system, early and frequent input from stakeholders—such as safari drivers and
government officials—is crucial to ensure the system meets their needs and expectations.
Agile, with its focus on collaboration and continuous feedback, may be better suited for
projects where stakeholder interaction is essential.

45
W. Renato croos 00196592 Software development lifecycle
In Waterfall, testing usually takes place only after development is complete, which could lead
to the discovery of issues late in the process. In a project as complex as the wildlife safari
system, with an inexperienced IT department, finding defects late can create additional
challenges and costs. Agile methods emphasize ongoing testing, allowing early identification
and correction of issues.

Using the Waterfall Model for the Salon Booking System

In Case 2, the simpler, well-defined requirements of the salon booking system align well with
the Waterfall model’s linear approach. With clear objectives and minimal expected changes,
the Waterfall model’s structured planning and execution are suitable for this project.
The development team’s previous experience with similar projects makes Waterfall an
efficient choice, as familiarity with the process allows the team to progress confidently
through each stage. The clear and organized nature of Waterfall ensures that the team can
complete each phase with an understanding of the overall project structure.

For projects with strict budgets and timelines, the Waterfall model offers a clear framework
for resource allocation and scheduling. In this case, the client’s priority is a high-quality
product, and the Waterfall model’s focus on thorough testing and validation aligns well with
this objective, providing a structured path toward a reliable, well-tested final product.

46
W. Renato croos 00196592 Software development lifecycle
LO2 Explain the importance of a feasibility study

2.1 Introduction about Hemas Holdings PLC

Hemas Hospital Wattala, a flagship branch of the Hemas Hospital network, is a trusted
healthcare provider located in the heart of the Wattala region. Established to deliver
international-standard medical services to local communities, this hospital quickly became
known for its quality care, cutting-edge facilities, and compassionate patient-centered
approach. The Wattala facility was designed to serve as a model for private healthcare,
equipped with advanced technology, specialized treatment units, and a comprehensive range
of services, including emergency care, diagnostics, and surgeries.

With a strong emphasis on continuous improvement, Hemas Hospital Wattala incorporates

globally recognized healthcare practices, with a team of experienced medical professionals
dedicated to patient well-being. This commitment to excellence is backed by rigorous quality
control and safety standards that align with both national and international healthcare
certifications. The hospital also places a high priority on sustainability, adopting eco-friendly
practices to minimize environmental impact.

Today, Hemas Hospital Wattala stands out as a leader in private healthcare in the region,
providing personalized care and innovative treatments that meet the evolving needs of its
patients. Through digital transformation initiatives and a strong focus on clinical excellence,
Hemas Hospital Wattala reinforces its role as a key healthcare provider, bringing advanced
medical care closer to the community.

47
W. Renato croos 00196592 Software development lifecycle
Figure 11: Hemas Hospital Wattala
Source: (Lanka Business News, A statement from Hemas Hospital Wattala 2020)

2.2 Software System Development for PLC

The development of a software system for Hemas Hospital, a leading healthcare provider in
Sri Lanka, requires a structured approach tailored to the healthcare industry’s specific needs
and operational complexities. Below is a detailed plan for the analysis, design, and
development of a comprehensive software system to enhance Hemas Hospital's service
delivery and operational efficiency:

1. Understanding the Business:

 Company Overview: Research the history and services offered by Hemas
Hospital, focusing on its role as a trusted healthcare provider known for
quality, patient-centered care across multiple facilities in Sri Lanka.
 Stakeholders: Identify the key stakeholders, including medical professionals,
administrative staff, and IT teams, as well as patients who interact directly
with the hospital's systems.
 Healthcare Process: Gain insights into critical hospital operations, from
patient admission and treatment to discharge and follow-up. Understanding
workflows such as appointment scheduling, diagnostic procedures, and patient
records is essential.
 Service Expansion: Explore any recent expansions or partnerships, especially
in digital health and telemedicine, that affect patient care or introduce new
service offerings.

2. Business Requirements Analysis:

 Conduct interviews and workshops with stakeholders to gather core business
requirements, such as:
 Patient management and appointment scheduling.
 Electronic Health Records (EHR) management.
 Inventory and supply chain management for medical equipment and
pharmaceuticals.
 Billing and insurance claim management.
 Compliance with healthcare regulations and data privacy laws.

48
W. Renato croos 00196592 Software development lifecycle
  Data analytics for hospital performance metrics, patient satisfaction,
and operational improvements.
 Current Challenges: Identify pain points in existing systems, such as data
silos between departments, manual workflows, or limited system integration
across branches.

3. System Requirements Analysis:

 Existing IT Systems Evaluation: Assess any current systems in place, such
as Electronic Health Records (EHR) systems or hospital management
software.
 System Requirements: Determine system capabilities, including:
 Real-time monitoring of patient data and hospital occupancy.
 Integration of patient care and administration data across departments.
 Multi-branch inventory and supply chain management.
 Secure access to patient records, diagnostics, and treatment plans.
 Scalability to accommodate future facility expansions and service
additions.

4. Feasibility Study:
 Conduct a feasibility analysis, evaluating the technical, economic, and
operational feasibility of developing a new software system.
 Ensure that the proposed system aligns with Hemas Hospital’s budget,
regulatory requirements, and strategic objectives.

5. System Design:
 Architecture Design: Develop a robust system architecture to support multi-
location operations, integrating patient management, diagnostic, and
administrative data.
 Database Design: Design a scalable, secure database for patient records,
medical histories, inventory, billing, and compliance data.
 User Interface Design: Create intuitive interfaces for different user roles,
including doctors, nurses, administrative staff, and patients.

49
W. Renato croos 00196592 Software development lifecycle
  Process Flow Design: Map the flow of information from patient registration
to discharge and ensure integration across departments.

6. Technology Stack Selection:

 Select an appropriate technology stack, considering scalability, data security,
and integration with existing hospital systems (e.g., JavaScript frameworks for
front-end, relational databases like MySQL, cloud infrastructure to support
remote access).

7. Development and Implementation:

 Iterative Development: Develop the system in phases, with iterative feedback
from stakeholders to ensure alignment with Hemas Hospital’s goals.
 Implementation Plan: Deploy the system across all Hemas Hospital
branches, ensuring integration with the central database and training for
hospital staff.

8. Testing and Quality Assurance:

 Conduct extensive testing to verify the system’s functionality, performance,
and data security, ensuring that it complies with healthcare regulations.
 User Acceptance Testing (UAT): Involve end-users in UAT to confirm that
the software meets the operational and clinical needs of the hospital.
 Quality Control: Address any quality control issues promptly to maintain
high standards of patient care and operational efficiency.


50
W. Renato croos 00196592 Software development lifecycle
2.3 Purpose of Feasibility Report for Hemas Hospital
The purpose of a feasibility report for Hemas Hospital, a leading healthcare provider in Sri
Lanka, is to evaluate the practicality and potential success of proposed projects or initiatives
within the hospital’s complex healthcare environment. These reports are crucial for guiding
strategic decisions, ensuring that resources are allocated effectively, and aligning projects
with the hospital’s mission of quality healthcare. Here are the key purposes of a feasibility
report tailored to Hemas Hospital:

1. Assessing Project Viability:

 Evaluating practicality: Hemas Hospital relies on feasibility reports to assess
the viability of new projects, such as adding specialized departments,
expanding facilities, or implementing new technologies like telemedicine. This
ensures that projects are practical, align with the hospital's healthcare
objectives, and have a high likelihood of success.

2. Minimizing Risks:
 Risk identification and mitigation: The report helps Hemas Hospital identify
potential risks, such as patient privacy concerns, regulatory compliance issues,
or operational disruptions. By analyzing these challenges, the hospital can
develop strategies to mitigate risks, safeguarding project success and
maintaining continuity in patient care.

3. Cost-Benefit Analysis:
 Financial planning and analysis: Feasibility reports provide Hemas Hospital
with financial insights, including cost estimates, expected benefits, and
potential return on investment (ROI). This enables the hospital to determine if
a project is financially sustainable and aligns with its budgetary goals and
resource capabilities.

4. Operational Feasibility:
 Assessing operational integration: Feasibility reports assess how well a
proposed project would integrate with existing healthcare processes, medical
equipment, and staffing capabilities. This analysis ensures that Hemas

51
W. Renato croos 00196592 Software development lifecycle
 Hospital can implement new initiatives without disrupting essential services or
impacting patient care quality.

5. Legal and Regulatory Compliance:

 Adherence to healthcare standards: As a significant healthcare provider,
Hemas Hospital must comply with strict healthcare regulations, including
patient safety and data privacy laws. Feasibility reports help verify that
proposed projects meet all regulatory requirements, protecting the hospital’s
reputation and reducing legal risks.

Feasibility reports are vital tools for Hemas Hospital, enabling it to assess the feasibility of
new initiatives, minimize potential risks, ensure financial viability, and maintain operational
and regulatory compliance. This thorough evaluation allows Hemas Hospital to make
informed decisions that align with its mission to provide high-quality healthcare and
contribute to the well-being of the communities it serves.

2.4 Evaluation of Technical Solutions for Hemas Hospital

Evaluating technical solutions for Hemas Hospital involves a thorough analysis of available
technologies that meet the hospital’s healthcare, operational, and data management needs.
This process ensures that selected solutions are compatible with the hospital’s existing
infrastructure, scalable for future growth, and economically feasible. The ultimate goal is to
enhance hospital operations, improve patient care, and maintain data security.
Key Factors to Consider in Technical Evaluation
1. System Requirements
 Functional Requirements: Identify essential functionalities, such as patient
management, electronic health records (EHR), billing, inventory control, and
reporting.
 Non-Functional Requirements: Consider system performance, security,
scalability, and reliability to ensure optimal support for medical staff and
patient care demands.

2. Current Infrastructure Analysis

52
W. Renato croos 00196592 Software development lifecycle
  Technology Stack: Review Hemas Hospital’s existing IT infrastructure,
including networks, databases, and EHR systems, to determine compatibility
with proposed solutions.
 Legacy Systems: Identify where legacy systems might need upgrades or
replacements to ensure smooth integration with new technologies.

3. Software Options
 Off-the-Shelf vs. Custom Software: Evaluate ready-made solutions, which
may offer quick deployment and lower costs, versus custom software tailored
to Hemas Hospital’s specific workflows and patient care needs.

4. Hardware Requirements
 Additional Hardware Needs: Determine if new hardware, such as upgraded
servers, diagnostic devices, IoT sensors, or patient monitoring systems, is
necessary for the proposed solutions.

5. Cloud vs. On-Premises Solutions

 Cloud-Based Solutions: Cloud options offer flexibility and scalability,
potentially lowering upfront costs and facilitating data access across multiple
locations.
 On-Premises Solutions: These provide more control over sensitive patient
data but may require a larger initial investment and ongoing maintenance.

6. Integration with Existing Systems

 Seamless Integration: Assess the compatibility of proposed solutions with
existing systems, such as EHR, patient billing, and inventory management.
Evaluate available APIs or middleware to enable efficient data flow.

7. Scalability
 Growth Potential: Determine if the solutions can scale with the hospital’s
growth, accommodating increased patient data, additional services, or facility
expansions.
8. Security

53
W. Renato croos 00196592 Software development lifecycle
  Data Protection: Ensure solutions have robust data security measures,
including encryption, secure access, and compliance with healthcare data
regulations like HIPAA.
 Cybersecurity: Review system capabilities for safeguarding against cyber
threats, with features such as regular updates, firewalls, and vulnerability
scanning.

9. Cost Evaluation
 Total Cost of Ownership (TCO): Compare the overall costs of each solution,
considering software licensing, hardware expenses, development, and ongoing
maintenance. Both initial and long-term costs should align with Hemas
Hospital’s budget.

10. Vendor Support and Reliability

 Vendor Evaluation: Assess vendor reliability, support options, and update
frequency. Consider vendors who provide ongoing support, training, and
customization to ensure long-term effectiveness and adaptability for Hemas
Hospital.

Each of these evaluation areas is critical for Hemas Hospital to select a solution that
strengthens healthcare delivery, enhances operational efficiency, and supports its long-term
strategic goals.

Evaluation of Specific Technical Solutions for Hemas Hospital

1. Hospital Management System (HMS)

 SAP Healthcare: A comprehensive HMS solution that integrates patient
management, inventory, billing, and financial modules, ideal for streamlined
healthcare operations.
 Oracle Health Management Platform: A cloud-based platform providing
advanced tools for patient care management, staff scheduling, and data
analytics, suitable for hospitals of various sizes.

54
W. Renato croos 00196592 Software development lifecycle
  Custom HMS Solution: Tailored to Hemas Hospital’s unique patient
workflows, a custom-built HMS can offer high flexibility, integrating clinical
and administrative features specific to the hospital’s needs.

2. Inventory and Supply Chain Management Solutions

 Odoo ERP: A modular, cloud-based ERP system with strong inventory
management capabilities, providing an affordable and scalable solution for
managing hospital supplies.
 Fishbowl Inventory for Healthcare: Designed for healthcare providers,
Fishbowl offers real-time inventory tracking, supply chain optimization, and
critical alerts for low-stock items.
 Custom Inventory Solution: Tailored specifically for Hemas Hospital,
offering features like multi-location tracking, integration with the HMS, and
customized reporting on supply usage.

3. Patient Monitoring and Quality Control

 IoT-Enabled Patient Monitoring: IoT sensors can be used for real-time
monitoring of patient vital signs, ensuring patient safety and efficient
healthcare delivery.
 Philips Health Suite: A cloud-based platform for managing patient data from
IoT devices, Health Suite provides real-time monitoring, predictive analytics,
and helps in preventive healthcare.
 Custom Monitoring Solution: A tailored solution that focuses on Hemas
Hospital’s specific quality control requirements, integrating real-time data
with the hospital’s HMS for streamlined patient care and compliance.

4. Cloud Hosting Services

 Amazon Web Services (AWS): AWS offers scalable and secure cloud
solutions for healthcare, with strong data protection and storage options ideal
for handling sensitive patient data.
 Microsoft Azure: Known for its healthcare-focused compliance and tools,
Azure provides secure hosting for health data, along with advanced AI
services for predictive analytics.

55
W. Renato croos 00196592 Software development lifecycle
  Google Cloud Platform (GCP): GCP offers strong data analytics and
machine learning capabilities, beneficial for patient care optimization and
data-driven decision-making.

Recommendations
 Cloud-Based Solutions: Cloud-based HMS and inventory management systems are
recommended due to their scalability, flexibility, and secure data management, which
support Hemas Hospital’s growing operations and expansion.
 Custom Development for Specialized Needs: Custom solutions are advised for
patient monitoring and quality control to ensure that specific hospital workflows are
seamlessly integrated and optimized.
 Integrated HMS Solution: Implementing a comprehensive HMS like SAP
Healthcare or Oracle Health Management will streamline operations across patient
management, inventory, and billing, enhancing the hospital’s operational efficiency
and patient experience.

This thorough evaluation will enable Hemas Hospital to select the most suitable technical
solutions to enhance operational efficiency, support future scalability, and maintain its
reputation for quality healthcare.

2.5 The components of a feasibility report

A feasibility report for Hemas Hospitals would involve a comprehensive assessment of a

proposed project’s technical, financial, operational, and market viability. This analysis helps
Hemas make informed decisions on whether a project aligns with its strategic goals and has a
high potential for success.

1. Executive Summary
 Overview: Briefly summarize the key findings and conclusions of the feasibility
study.
 Project Feasibility: Outline the project’s objectives and give a high-level
recommendation on whether it should proceed.

56
W. Renato croos 00196592 Software development lifecycle
 2. Introduction
 Objective: Describe the project’s goals, such as improving patient care or expanding
into new service areas.
 Problem Statement: Identify the specific healthcare challenges or opportunities the
project addresses.
 Scope: Define the scope of the feasibility study, including which business areas will
be evaluated.

3. Technical Feasibility
 Current Infrastructure: Review Hemas’s existing healthcare technology, such as
patient management systems, diagnostic equipment, and IT infrastructure.
 Technology Requirements: Identify necessary technologies, like cloud platforms,
electronic health records (EHR), or IoT for patient monitoring.
 Resource Availability: Assess if Hemas has in-house technical expertise or requires
external support for the project.
 Integration: Evaluate how the new system will integrate with existing systems, like
EHR, CRM, and other hospital management tools.

4. Operational Feasibility
 Business Processes: Examine how the project aligns with current workflows in
patient care, inventory, and administration.
 Staffing: Determine if existing staff can manage the new system or if additional
recruitment or training is needed.
 Operational Challenges: Identify potential implementation disruptions and develop
mitigation strategies.
 User Acceptance: Evaluate staff readiness for system adoption and recommend
change management approaches.

5. Economic/Financial Feasibility
 Cost Analysis: Provide a detailed breakdown of costs, including software, hardware,
and implementation expenses.
 Return on Investment (ROI): Estimate financial benefits like cost savings or
revenue growth and calculate the expected ROI.

57
W. Renato croos 00196592 Software development lifecycle
  Break-even Analysis: Determine when the project will start generating returns.
 Funding: Assess Hemas’s financial capacity and potential funding sources, such as
internal funds or external financing.

6. Market Feasibility
 Customer Expectations: Analyze how the project will enhance the patient
experience, such as reduced wait times or improved care.
 Competitor Analysis: Evaluate what competitors are doing and how Hemas can gain
a competitive advantage.
 Industry Trends: Explore trends in the healthcare industry relevant to the project,
such as digital health or patient-centered care.

7. Legal and Regulatory Feasibility

 Compliance: Identify relevant regulations, including healthcare standards, data
privacy, and safety protocols.
 Licensing: Outline any licenses or certifications necessary for the project.
 Risk Management: Develop strategies to mitigate potential legal risks, such as
compliance issues or contractual matters.

8. Schedule Feasibility
 Timeline: Provide an estimated project timeline, from planning to full
implementation and post-launch support.
 Milestones: Identify major milestones, such as system design, testing, and
deployment.
 Dependencies: Highlight dependencies like vendor timelines or software
development that could impact the schedule.

9. Risk Assessment
 Technical Risks: Outline possible technical risks, such as compatibility or integration
issues.
 Operational Risks: Assess risks to hospital operations, including system downtime
or disruptions.

58
W. Renato croos 00196592 Software development lifecycle
  Financial Risks: Analyze financial risks like budget overruns or lower-than-expected
ROI.
 Mitigation Strategies: Propose measures to manage each identified risk.

10. Human Resource Feasibility

 Skill Assessment: Evaluate if Hemas’s staff has the required skills for project
implementation.
 Training Needs: Identify necessary training for employees to effectively use and
maintain the new system.
 Recruitment: Develop a plan to recruit additional skilled staff if needed.

11. Environmental Feasibility (Optional)

 Environmental Impact: Assess the environmental impact, such as energy usage or
sustainability practices, relevant to Hemas Hospitals.

12. Conclusion and Recommendations

 Summary of Findings: Summarize the major findings from the feasibility study.
 Recommendation: Make a clear recommendation on whether to proceed based on
key factors like ROI and risk alignment with Hemas’s goals.
 Alternative Solutions: If the project is not feasible, suggest alternative options that
may be viable.

13. Appendices (Optional)

 Supporting Documents: Include additional documents, such as cost models,
technical specs, or vendor proposals, to support the findings.

This structured feasibility report will help Hemas Hospitals make a well-informed decision
on implementing new projects that align with their strategic objectives and resource
availability.

59
W. Renato croos 00196592 Software development lifecycle
Figure 12: Benefits of feasibility report
Source: (What are the benefits of a feasibility study)

2.6 Impact of Feasibility Criteria on Wattala Hemas Hospital

Evaluating the feasibility of new projects at Wattala Hemas Hospital is vital for determining
if proposed initiatives align with operational needs, financial goals, and strategic vision. Each
criterion influences the hospital’s service quality, patient outcomes, and overall efficiency,
ensuring that any project supports the hospital's mission.

1. Technical Feasibility
 Positive Impact: If technically feasible, the hospital can implement advanced
healthcare technology, such as electronic health records (EHR) systems or
diagnostic tools, leading to streamlined processes and improved patient care.
 Negative Impact: If the project faces technical constraints, it may result in
costly upgrades or delays, impacting service delivery and patient satisfaction.

2. Operational Feasibility
 Positive Impact: Projects that align with existing operations can improve
patient flow, reduce wait times, and optimize resource allocation across
departments.

60
W. Renato croos 00196592 Software development lifecycle
  Negative Impact: Poor operational fit, such as integration challenges with
current workflows or insufficient staff training, may lead to inefficiencies,
errors, and lower patient care quality.

3. Financial Feasibility
 Positive Impact: A financially viable project can bring high returns on
investment (ROI) by reducing operational costs or enhancing revenue streams,
allowing the hospital to expand its services and enhance patient care.
 Negative Impact: If financially unfeasible, high costs can strain the hospital's
budget, limiting funds for essential areas like staff training or medical
equipment.

4. Market Feasibility
 Positive Impact: Projects that align with healthcare trends, such as digital
health or sustainable practices, can attract patients seeking modern and reliable
healthcare, strengthening the hospital’s market position.
 Negative Impact: Projects that fail to meet market needs or patient
expectations may lead to a decline in patient visits, affecting revenue and
reputation.

5. Legal and Regulatory Feasibility

 Positive Impact: Compliance with healthcare regulations safeguards the
hospital against legal penalties and maintains its accreditation, building trust
with patients and stakeholders.
 Negative Impact: Non-compliance could lead to fines, service interruptions,
and reputational damage, impacting patient trust and hospital credibility.

6. Schedule Feasibility
 Positive Impact: A realistic timeline minimizes service disruptions, allowing
the hospital to maintain quality care while transitioning to new systems or
processes.
 Negative Impact: Unrealistic timelines or delays can lead to operational
challenges, affecting service delivery and patient satisfaction.

61
W. Renato croos 00196592 Software development lifecycle
 7. Risk Assessment Feasibility
 Positive Impact: Proactively managing risks helps address potential
challenges before they escalate, supporting smooth project execution and
reducing unexpected costs.
 Negative Impact: Failure to manage risks can result in setbacks, such as IT
failures or supply issues, leading to service interruptions and financial losses.

8. Human Resource Feasibility

 Positive Impact: Adequately trained staff for new systems enhances
efficiency, reduces errors, and improves the quality of patient care.
 Negative Impact: Lack of skilled personnel or resistance to change may
reduce productivity and lead to increased training costs or reliance on
consultants.

9. Environmental Feasibility (Optional)

 Positive Impact: Environmentally sustainable initiatives, such as waste
reduction or energy-efficient systems, can lower costs and appeal to eco-
conscious patients, strengthening the hospital’s image.
 Negative Impact: Ignoring environmental considerations may result in higher
long-term costs and reputational risks, especially as patients increasingly value
sustainability.

By thoroughly evaluating these feasibility criteria, Wattala Hemas Hospital can reduce
potential risks, maximize its investment, and implement projects that improve its operational
efficiency, financial health, and competitive position in Sri Lanka’s healthcare landscape.

62
W. Renato croos 00196592 Software development lifecycle
LO3 Undertake a software development lifecycle

3.1 Investigation Report for Wattala Hemas Hospital

Wattala Hemas Hospital

Table of Contents

1. Investigation Team

2. Scope

3. Business Objectives

4. Existing Systems and Processes

5. Market Analysis

6. Regulatory Requirements

7. Technology Assessment

8. Prioritize Requirements

9. Gap Analysis

10. Cost Analysis

63
W. Renato croos 00196592 Software development lifecycle
3.1.1 Investigation Team

Role Description
Team Leader The IT Director will lead the investigation and oversee the entire process.
(IT Director) Responsible for aligning technology solutions with Hemas Hospital's
business objectives, they ensure that new systems or upgrades enhance
operational efficiency and support long-term goals. The role includes
evaluating current IT infrastructure, coordinating with departments, and
guiding the implementation of recommended improvements.
IT Analyst The IT Analyst assesses Hemas Hospital’s current technology
infrastructure, including hardware, software, networks, and data
management systems. They identify strengths, weaknesses, and future
compatibility. By analyzing system performance, security, and scalability,
the IT Analyst provides insights to optimize technology and support
operational needs. Their recommendations aim to enhance efficiency,
reduce costs, and align with strategic goals.
Operations The Operations Manager reviews and analyzes operational workflows and
Manager processes within Hemas Hospital. They assess the efficiency of current
practices and identify bottlenecks in patient flow, supply chain, and daily
operations. By working closely with department heads, they recommend
improvements that align workflows with business objectives, improve
productivity, and support enhanced patient care.
Financial The Financial Analyst conducts financial feasibility and cost analysis for
Analyst proposed initiatives at Hemas Hospital. This includes evaluating costs
associated with new technologies and upgrades against projected benefits
such as cost savings and increased revenue. The Financial Analyst assesses
the return on investment (ROI) and break-even points, ensuring financial
viability and alignment with the hospital’s long-term financial strategy.
Market The Market Researcher analyzes healthcare trends, patient expectations, and
Researcher competitor strategies. By studying market dynamics and competitor
positioning, they help Hemas Hospital make informed decisions regarding
service offerings, marketing, and patient engagement. Their insights support
strategic alignment with patient needs and healthcare trends, ensuring

64
W. Renato croos 00196592 Software development lifecycle
 competitiveness and growth in the healthcare sector.
Legal Expert The Legal Expert ensures compliance with healthcare regulations, including
patient data protection, labor laws, and environmental regulations. They
assess legal risks and advise on regulatory requirements, protecting Hemas
Hospital from potential legal issues, penalties, and reputational damage.
Their role is essential in maintaining ethical and lawful practices across new
projects and business processes.

Table 1: Investigation Team

Source: Author’s work

3.1.2 Scope
The scope of this investigation for Hemas Hospital Wattala focuses on a comprehensive
evaluation of the hospital's current operational, technical, financial, and regulatory
environment. The primary objective is to assess the feasibility of upgrading systems and
processes to drive efficiency, improve patient care, and strengthen competitiveness within the
healthcare sector. This investigation will lay the foundation for making informed decisions on
potential technological improvements, operational enhancements, and strategic changes that
align with Hemas Hospital's mission to provide high-quality healthcare services.

Key Areas of Focus

1. Technical Systems: IT Infrastructure and Medical Technology

A core focus of the investigation is Hemas Hospital’s existing technical systems, including IT
infrastructure and medical technologies. This involves analyzing the hospital’s current
hardware, software, network capabilities, and data management systems to ensure that they
support future growth and align with the hospital's strategic goals. Identifying gaps will
enable recommendations for potential upgrades, modernization efforts, or adoption of
advanced technologies such as electronic health records (EHR), telemedicine platforms, or
cloud-based data management to enhance patient care and operational efficiency.

Additionally, an in-depth evaluation of the medical technology used in patient diagnostics

and treatment will be conducted. This includes assessing the efficiency of current equipment
and exploring the feasibility of adopting new technologies, such as AI-assisted diagnostics,

65
W. Renato croos 00196592 Software development lifecycle
robotic surgery tools, and Internet of Things (IoT) devices for real-time patient monitoring.
These innovations can improve diagnostic accuracy, enhance patient outcomes, and
streamline hospital workflows.

2. Operational Processes and Workflow Efficiency

This section of the investigation will examine the hospital's operational processes and
workflow efficiency across patient care, administrative, and support functions. The analysis
will identify inefficiencies, bottlenecks, and areas where workflow optimization can reduce
delays and improve the patient experience.

For example, the investigation will review scheduling, supply chain management, and
inventory control systems to assess their ability to support increased patient demand,
maintain continuity of care, and enhance patient satisfaction. Additionally, the integration
between various departments—such as emergency services, outpatient clinics, and inpatient
units—will be examined to ensure smooth information flow, facilitating quick and informed
decision-making. Recommendations may include process reengineering or the adoption of
management tools like hospital information systems (HIS) and enterprise resource planning
(ERP) systems.

3. Market Position and Competitor Analysis

An essential component of this investigation is analyzing Hemas Hospital's market position
and the competitive healthcare landscape. This involves assessing the hospital's strengths,
weaknesses, opportunities, and threats (SWOT) in both domestic and regional contexts. An
in-depth competitor analysis will be conducted to understand how Hemas compares to other
healthcare providers in terms of services, patient care quality, pricing, and technology use.

The market analysis will also explore emerging trends in the healthcare industry, such as the
rise of telemedicine, patient-centric care models, and increasing demand for specialized
services. Understanding these trends will help Hemas Hospital identify opportunities for
service expansion, patient engagement, and innovation. Ultimately, the investigation will
provide insights on how Hemas Hospital can capitalize on market dynamics and maintain its
competitive edge.

66
W. Renato croos 00196592 Software development lifecycle
4. Regulatory Compliance and Sustainability Practices
Regulatory compliance is a critical focus of the investigation, including adherence to
healthcare regulations, patient data privacy laws, labor practices, and environmental
standards. The investigation will assess the hospital's current compliance levels, identify
potential risks, and recommend measures to strengthen regulatory adherence to minimize
legal liabilities and maintain high ethical standards.

Additionally, the investigation will evaluate Hemas Hospital's sustainability practices,

examining its environmental impact and resource efficiency. Considering the growing
importance of sustainability, recommendations will include adopting eco-friendly practices,
such as waste reduction, energy conservation, and use of sustainable materials, to align with
both regulatory requirements and community expectations.

5. Financial Implications of Proposed System Upgrades

The financial feasibility of proposed system and process upgrades will be a major area of
investigation. This involves performing a detailed cost-benefit analysis of investments in new
technologies, operational changes, and sustainability initiatives, assessing the potential return
on investment (ROI) and impact on long-term profitability.

The analysis will consider initial costs, ongoing maintenance expenses, and potential
financial benefits, providing hospital management with a clear understanding of financial
risks and opportunities associated with these upgrades. Additionally, the investigation will
explore alternative financial strategies, such as phased implementation or seeking external
funding, to support a sustainable investment approach for Hemas Hospital.

This investigation will ultimately provide Hemas Hospital with a roadmap for strategic
improvements that support its mission, improve patient care, and ensure financial
sustainability in a competitive healthcare landscape.

67
W. Renato croos 00196592 Software development lifecycle
3.1.3 Business Objectives

Hemas Hospital Wattala has established several strategic objectives to strengthen its
competitive position in the healthcare sector and ensure long-term sustainability. These
objectives serve as a roadmap for the hospital’s growth, operational excellence, and
commitment to delivering high-quality patient care.

1. Operational Efficiency
A primary goal for Hemas Hospital is to enhance operational efficiency across all
departments. By implementing advanced healthcare technologies and optimizing workflows,
the hospital aims to minimize waiting times, reduce patient turnover rates, and improve
resource utilization. Strategies may include adopting automation in administrative processes,
streamlining patient scheduling, and utilizing data analytics to identify bottlenecks in patient
flow and treatment processes. This focus on operational efficiency ensures high-quality
standards in patient care while managing costs effectively.

2. Service Expansion
To achieve sustained growth, Hemas Hospital aims to broaden its service offerings and
increase its reach within the healthcare sector. This objective includes exploring new
healthcare services, expanding into underserved areas, and enhancing its telemedicine
capabilities to meet the needs of remote patients. By diversifying its services and expanding
its patient base, the hospital seeks to cater to a broader demographic and become a leading
provider in the healthcare industry in Sri Lanka.

3. Sustainability and Environmental Responsibility

Recognizing the importance of environmental stewardship, Hemas Hospital is committed to
adopting sustainable practices throughout its operations. This objective involves reducing
energy consumption, minimizing waste, and implementing eco-friendly practices across
departments. By aligning operations with sustainable practices, the hospital not only meets
regulatory requirements but also contributes to the well-being of the community and responds
to the increasing demand for environmentally responsible healthcare providers.

68
W. Renato croos 00196592 Software development lifecycle
4. Financial Stability and Profitability
Hemas Hospital aims to ensure financial stability and improve profitability through careful
cost management and efficiency improvements. This includes ongoing evaluation of the
hospital’s cost structure, identifying areas for cost reduction, and investing in innovations that
enhance service delivery without compromising patient care quality. By focusing on financial
sustainability, Hemas Hospital can reinvest in growth initiatives, improve facilities, and
maintain affordable care for patients.

Together, these strategic objectives will guide Hemas Hospital Wattala in navigating the
challenges of the healthcare industry, ensuring long-term success and continuing its mission
to provide high-quality, accessible healthcare.

3.1.4 Existing Systems and Processes

Hemas Hospital Wattala currently utilizes an Enterprise Resource Planning (ERP) system to
manage various aspects of its operations, including patient management, inventory control,
and financial tracking. While this system provides a basic framework for integrating critical
hospital functions, it faces several challenges, particularly in terms of data integration across
departments. The lack of seamless data flow between departments creates silos that limit
effective communication and collaboration, leading to operational inefficiencies. For
example, discrepancies in inventory levels between pharmacy and procurement can result in
stockouts of critical supplies, affecting patient care and operational costs.

The hospital’s patient care processes rely heavily on manual workflows, with limited
automation in place for administrative and clinical procedures. This dependence on manual
labor not only slows down patient handling but also increases the risk of human error in
record-keeping, billing, and patient tracking. The lack of automation in these areas results in
longer wait times for patients and increased administrative burdens for staff. Moving towards
a more automated system would enable Hemas Hospital to streamline patient care, reduce
wait times, and improve accuracy in patient records.

In terms of inventory and supply chain management, Hemas Hospital has established
functional processes; however, there is significant room for improvement. Specifically, the
hospital’s inventory management and demand forecasting practices need refinement. Current
methods lack advanced data analytics capabilities, which makes it challenging to predict

69
W. Renato croos 00196592 Software development lifecycle
demand accurately and efficiently manage inventory. This can lead to both excess inventory
and shortages of essential items. Implementing better forecasting tools and more
comprehensive inventory control systems would optimize the hospital’s supply chain, reduce
inventory costs, and enhance patient care by ensuring that necessary supplies are always
available.

In summary, while Hemas Hospital Wattala has foundational IT systems and established
processes, addressing the challenges of data integration, manual workflows, and inventory
management will be essential for improving operational efficiency, patient satisfaction, and
overall competitiveness in the healthcare sector.

3.1.5 Market Analysis

1. Industry Overview
The healthcare industry in Sri Lanka is growing rapidly, driven by rising health awareness,
increasing incidence of lifestyle diseases, and a demand for high-quality medical services.
With both public and private sectors contributing to the healthcare landscape, private
hospitals like Hemas Hospital Wattala are in high demand for their quality of care,
specialized services, and modern facilities. However, the sector faces challenges, including
regulatory compliance, high operating costs, and competition from government hospitals that
offer subsidized services.

2. Target Market
Hemas Hospital primarily targets the middle- and upper-income segments in the Colombo
and Gampaha districts, who seek reliable, high-quality healthcare services. These patients
value access to advanced medical treatments, shorter waiting times, and a more personalized
healthcare experience than what is typically available in public hospitals. Additionally, there
is a growing demand for preventive care, diagnostic services, and specialized treatments
among health-conscious consumers.

3. Market Trends
 Digital Transformation: There is an increasing demand for digital health solutions,
such as telemedicine, mobile health apps, and electronic health records, especially

70
W. Renato croos 00196592 Software development lifecycle
 after the COVID-19 pandemic. Patients expect online appointment scheduling, virtual
consultations, and easy access to medical records, which enhances convenience and
accessibility.

 Preventive and Outpatient Care: The shift towards preventive care and wellness
services is evident, with patients showing interest in health checkups, screening
services, and wellness programs to prevent chronic illnesses. Hemas could benefit
from expanding its preventive care offerings to cater to this growing trend.

 Sustainable Practices: Patients and their families are becoming more conscious of
environmental sustainability, favoring healthcare providers that prioritize eco-friendly
practices, such as waste reduction, energy-efficient operations, and sustainable
building designs.

4. Competitive Landscape
Hemas Hospital Wattala competes with both public and private healthcare providers in the
Colombo and Gampaha areas. Public hospitals attract patients with their free or low-cost
services, while private hospitals differentiate themselves by offering higher standards of care,
specialized services, and modern facilities. Hemas faces competition from other leading
private hospitals, such as Lanka Hospitals, Nawa Loka Hospitals, and Asiri Health, all of
which invest heavily in technology, service expansion, and patient experience improvements.
Additionally, some competitors are integrating advanced medical technology and artificial
intelligence (AI) to improve diagnostic accuracy and operational efficiency.

5. Opportunities for Hemas Hospital Wattala

 Expansion of Telemedicine Services: With the rising demand for remote healthcare
services, Hemas has an opportunity to expand its telemedicine offerings, which would
cater to patients who prefer virtual consultations and enable the hospital to serve a
broader demographic.

 Investment in Specialized Services: Specializing in high-demand areas, such as

cardiology, oncology, and orthopedics, could help Hemas attract more patients
seeking advanced treatments and position itself as a center of excellence.

71
W. Renato croos 00196592 Software development lifecycle
  Health and Wellness Programs: Expanding preventive health programs, wellness
checkups, and lifestyle management services could appeal to a growing segment of
health-conscious consumers.

 Focus on Sustainability: By implementing sustainable practices, such as reducing

waste, energy-efficient operations, and sustainable procurement, Hemas can appeal to
environmentally conscious patients and align with global healthcare sustainability
trends.

6. Challenges
 High Operational Costs: Managing costs is challenging, especially with the need to
maintain high standards of care, invest in technology, and ensure compliance with
healthcare regulations.

 Retention and Training of Skilled Staff: The hospital industry faces a shortage of
skilled healthcare professionals, and retaining qualified staff is critical to maintaining
service quality.

 Regulatory Compliance: Compliance with government regulations, especially

related to patient safety, data protection, and environmental standards, can be
demanding and costly for private healthcare providers.

Conclusion
To stay competitive, Hemas Hospital Wattala should leverage digital healthcare solutions,
enhance patient experience through specialized services, and prioritize sustainable practices.
Focusing on the evolving needs of patients and aligning with industry trends can help Hemas
strengthen its market position, attract a broader range of patients, and secure its reputation as
a leading private healthcare provider in Sri Lanka.

72
W. Renato croos 00196592 Software development lifecycle
3.1.6 Regulatory Requirements

1. Healthcare Compliance and Safety Standards

As a leading healthcare provider in Sri Lanka, Hemas Hospital Wattala is committed to
complying with stringent healthcare regulations and safety standards that govern patient care,
facility management, and overall operations. The hospital adheres to local regulations
mandated by the Ministry of Health, which include protocols for infection control, medical
waste disposal, and patient safety. By following these standards, Hemas ensures the highest
quality of care for patients and maintains its reputation as a trusted healthcare provider.
Compliance with healthcare regulations is essential for avoiding legal risks and ensuring that
the hospital operates within ethical and safety guidelines.

2. Environmental Sustainability Regulations

In line with global trends towards sustainable healthcare, Hemas Hospital is dedicated to
reducing its environmental impact. The hospital complies with environmental regulations
related to waste management, energy consumption, and water usage. Initiatives such as eco-
friendly waste disposal, efficient energy systems, and water conservation help Hemas
minimize its carbon footprint. Compliance with these environmental standards not only helps
meet regulatory requirements but also supports the hospital’s commitment to corporate social
responsibility, appealing to environmentally conscious patients and stakeholders.

3. Data Protection and Patient Privacy

With the increasing reliance on digital health records and telemedicine, Hemas Hospital
prioritizes data protection and patient privacy. The hospital adheres to data protection laws in
Sri Lanka, such as the Personal Data Protection Act, which mandates secure handling of
patient information. Implementing robust data security measures and following best practices
for data confidentiality ensures that patient information is safeguarded against breaches.
Compliance with data protection regulations helps Hemas build trust with patients, reduces
the risk of data-related penalties, and aligns the hospital with global healthcare privacy
standards.

4. International Quality Certifications

To ensure the highest standards of care and to appeal to a broader patient base, Hemas
Hospital pursues internationally recognized quality certifications, such as ISO certifications

73
W. Renato croos 00196592 Software development lifecycle
for healthcare services. These certifications validate the hospital’s commitment to delivering
safe, effective, and high-quality care. Compliance with international healthcare standards not
only boosts Hemas’s reputation but also enhances operational efficiency, safety, and patient
satisfaction. Meeting these standards is crucial for Hemas to maintain its competitive
advantage in the healthcare market and to continue attracting both local and international
patients.
By adhering to these regulatory requirements and industry standards, Hemas Hospital Wattala
can continue to operate responsibly, enhance its service quality, and uphold its position as a
leading private healthcare provider in Sri Lanka.

Technology Assessment
1. Current IT Infrastructure
Hemas Hospital Wattala utilizes an integrated IT infrastructure that supports patient care,
administrative functions, and operational processes. This infrastructure includes electronic
health records (EHR) systems, patient management systems, and other digital solutions
essential for efficient healthcare delivery. However, with the rapid advancements in
healthcare technology, it’s essential for the hospital to periodically assess the capabilities of
its existing infrastructure to ensure it meets the demands of modern healthcare. Upgrading to
more advanced, cloud-based EHR systems could enhance data accessibility, reduce
downtime, and improve interdepartmental communication, ultimately leading to more
efficient patient care.

2. Telemedicine and Remote Patient Monitoring

Telemedicine has become a crucial aspect of modern healthcare, especially in light of the
COVID-19 pandemic. While Hemas Hospital currently offers some telehealth services,
expanding these capabilities would increase access to care for patients unable to visit the
hospital. Integrating remote patient monitoring tools could also help manage chronic
conditions more effectively, allowing doctors to track patient health metrics in real-time. This
technology can reduce the need for in-person visits, lower healthcare costs, and improve
patient outcomes by enabling proactive care management.

3. Automation and Workflow Optimization

The healthcare sector increasingly relies on automation to enhance workflow efficiency and
reduce human error. Hemas Hospital could benefit from automated systems in areas such as

74
W. Renato croos 00196592 Software development lifecycle
appointment scheduling, billing, inventory management, and supply chain operations. For
instance, an automated inventory system could track medication and supply levels, alerting
staff when restocking is needed. This would reduce manual tracking errors, minimize supply
shortages, and improve overall operational efficiency. Automating repetitive administrative
tasks allows healthcare professionals to focus more on patient care, ultimately enhancing
service quality.

4. Data Analytics and Decision Support Systems

Leveraging data analytics in healthcare can significantly improve decision-making, patient
outcomes, and operational efficiency. Hemas Hospital could benefit from advanced data
analytics to analyze patient trends, predict hospital admissions, manage resource allocation,
and improve patient care strategies. Implementing decision support systems, such as
predictive analytics for disease management, could help doctors make more informed clinical
decisions. By utilizing data-driven insights, Hemas can optimize treatment plans, reduce wait
times, and enhance patient satisfaction. These technologies align with global trends towards
precision medicine and patient-centered care.

5. Cybersecurity and Data Protection

As Hemas Hospital expands its digital presence, cybersecurity and data protection are critical
priorities. The hospital handles a large volume of sensitive patient data, making it a target for
potential cyber threats. Enhancing cybersecurity protocols, including data encryption, multi-
factor authentication, and regular security audits, is essential for protecting patient
information and complying with data protection regulations. Implementing comprehensive
cybersecurity measures safeguards against data breaches, builds patient trust, and aligns with
the hospital’s commitment to data privacy.

6. Artificial Intelligence (AI) and Machine Learning (ML) in healthcare

Artificial intelligence and machine learning offer transformative potential in diagnostics,
patient monitoring, and personalized medicine. For Hemas Hospital, integrating AI-driven
tools could support radiology, pathology, and other diagnostic services by providing faster
and more accurate analysis. Machine learning algorithms could help in early detection of
diseases by analyzing patterns in patient data that may not be immediately apparent to human

75
W. Renato croos 00196592 Software development lifecycle
clinicians. Implementing AI could reduce diagnostic errors, improve treatment outcomes, and
support staff in making more efficient decisions, ultimately enhancing the quality of care.
7. IoT (Internet of Things) for Patient Monitoring and Facility Management
The Internet of Things (IoT) allows for interconnected devices that can enhance patient care
and streamline facility management. For example, wearable IoT devices could be used to
monitor patient vitals in real-time, alerting healthcare providers to potential issues before they
become critical. Additionally, IoT sensors can improve hospital management by monitoring
equipment usage, tracking asset locations, and managing energy consumption, which could
reduce operational costs. Adopting IoT technology would help Hemas Hospital deliver more
proactive care and maintain efficient facility operations.

Conclusion
To stay at the forefront of healthcare excellence, Hemas Hospital Wattala should consider
strategic investments in these emerging technologies. Enhancing IT infrastructure, expanding
telemedicine services, adopting automation, and leveraging data analytics can improve
operational efficiency, patient outcomes, and overall service quality. Prioritizing
cybersecurity and exploring AI, ML, and IoT applications will further ensure that Hemas
remains a trusted, innovative healthcare provider in Sri Lanka.

Prioritize Requirements
Based on an in-depth evaluation of Hemas Hospital Wattala's operational, technical, and
strategic needs, the following prioritized requirements have been identified. Fulfilling these
requirements will strengthen the hospital’s efficiency, improve patient satisfaction, and
ensure compliance with healthcare industry standards.

1. Electronic Health Records (EHR) System Enhancement

Upgrading the current Electronic Health Records (EHR) system is a top priority to improve
data accessibility and coordination among departments. An enhanced EHR system will
support seamless sharing of patient data, enabling quicker and more accurate clinical
decisions. This system upgrade is expected to reduce paperwork, minimize errors, and
enhance patient care by providing real-time information to healthcare providers. Additionally,
this would pave the way for future integrations with telemedicine and patient management
systems.

76
W. Renato croos 00196592 Software development lifecycle
 2. Automation of Key Administrative Processes
Automating essential administrative tasks, such as appointment scheduling, billing, and
inventory management, will improve efficiency, reduce manual errors, and enhance patient
experience by cutting down wait times. This automation will also streamline operations,
allowing staff to allocate more time to patient care. A robust automated system can enhance
operational efficiency, reduce resource wastage, and help manage fluctuating patient volumes
more effectively.

3. Cybersecurity Enhancements
Strengthening cybersecurity is critical to protecting patient data and maintaining trust.
Implementing advanced security protocols, including data encryption, regular vulnerability
assessments, and multi-factor authentication, will mitigate the risks of data breaches.
Enhanced cybersecurity measures will ensure compliance with international standards like
GDPR, prevent data loss, and protect sensitive health information.

4. Training and Change Management

To successfully implement new systems and processes, comprehensive training and change
management programs for staff are essential. This will enable a smoother transition to new
technologies and minimize resistance to change. Staff training initiatives will ensure that
healthcare professionals and administrative staff can effectively utilize upgraded systems,
maximizing productivity and system benefits. Change management strategies will foster a
positive adoption environment, essential for long-term success.

5. Patient-Centered Care Enhancements

Improving patient-centered care practices by upgrading patient engagement tools, such as
mobile health apps and digital patient portals, will enhance the patient experience. These
tools can allow patients to access their health records, schedule appointments, and receive test
results digitally. By focusing on patient-centered care, Hemas can increase patient
satisfaction, build stronger patient relationships, and improve overall patient outcomes.

6. Sustainability Initiatives

77
W. Renato croos 00196592 Software development lifecycle
Incorporating sustainability practices, such as energy-efficient systems, waste reduction
programs, and eco-friendly materials, will help Hemas reduce its environmental impact.
Prioritizing sustainability initiatives will also align with increasing global standards and
demonstrate corporate social responsibility. These efforts can improve the hospital’s
reputation, attract eco-conscious stakeholders, and potentially reduce operational costs in the
long run.

By focusing on these prioritized requirements, Hemas Hospital Wattala can improve

operational efficiency, enhance the quality of patient care, safeguard data security, and foster
a sustainable approach to healthcare delivery.

Gap Analysis
Gap Analysis for Hemas Hospital Wattala
To bridge the gap between Hemas Hospital’s current capabilities and its desired state, a
thorough gap analysis can pinpoint specific areas where enhancements and software solutions
are essential. This approach will enable Hemas to optimize patient care, operational
efficiency, and compliance with healthcare standards.

1. Identify Current Capabilities

 Objective: Begin by gathering detailed information about the hospital’s current
capabilities across critical areas such as patient care, administrative processes, data
security, supply chain management, and sustainability initiatives.
 Scope: This assessment should cover all existing resources, technologies, and systems
in use, providing a comprehensive view of operational strengths and limitations.
 Approach: Document workflows, analyze the effectiveness of current software
solutions, and map out existing infrastructure to understand Hemas Hospital’s
operational foundation.

2. Define Desired Capabilities

 Objective: Outline a clear vision of the hospital's ideal state across all functional
areas, focusing on areas like advanced patient care technology, automated
administrative processes, and enhanced data security.
 Scope: Define specific objectives, such as improved patient engagement, integrated
systems for real-time data access, and compliance with industry standards.
78
W. Renato croos 00196592 Software development lifecycle
  Approach: Align desired capabilities with Hemas Hospital’s strategic goals and
healthcare standards. This includes identifying the skills, technologies, and processes
required to achieve these targets.

3. Assess Disparities
 Objective: Conduct a comparative analysis between current and desired capabilities,
identifying gaps in resources, technology, and processes.
 Scope: This assessment should highlight specific areas where Hemas Hospital’s
current systems fall short, such as manual processes that could benefit from
automation, outdated data security measures, or limited patient engagement tools.
 Approach: Use data collection methods like performance metrics, employee
interviews, patient feedback, and workflow evaluations to gain a comprehensive
understanding of these disparities.

4. Prioritize Areas for Improvement

 Objective: Rank the identified gaps based on their impact on hospital performance,
patient satisfaction, and operational efficiency.
 Scope: Prioritize high-impact areas, such as automating manual tasks, upgrading
cybersecurity, and enhancing patient-centered digital tools.
 Approach: Use criteria such as cost-effectiveness, feasibility, and alignment with
strategic goals to guide prioritization.

5. Develop a Roadmap for Implementation

 Objective: Create a detailed roadmap outlining the steps needed to address identified
gaps and move towards the desired state.
 Scope: This roadmap should include timelines, budget estimates, and resource
allocation for each improvement initiative, ensuring that Hemas Hospital has a clear
path toward its goals.
 Approach: Phase the implementation to allow for manageable transitions, starting
with high-priority areas such as EHR upgrades and administrative automation.

By conducting a comprehensive gap analysis, Hemas Hospital Wattala can identify where
software and process improvements are essential to closing gaps between its existing and

79
W. Renato croos 00196592 Software development lifecycle
desired capabilities. This approach will provide a clear, actionable plan to enhance service
delivery, operational efficiency, and overall patient satisfaction.

Cost Analysis for Hemas Hospital Wattala

A comprehensive cost analysis is essential to estimate the financial investment required for
Hemas Hospital to close gaps identified in the gap analysis and improve operational
capabilities. This analysis breaks down costs in Sri Lankan Rupees (LKR) across key areas
including software upgrades, automation, training, and compliance measures.

1. ERP and IT System Upgrades

 ERP System Upgrade: To facilitate seamless data integration across departments, an
ERP upgrade is essential.
o Estimated Cost: LKR 8,000,000 - 10,000,000
o Description: Includes software licensing, customization, and integration with
existing systems.

 IT Infrastructure Enhancement: Improved servers, network enhancements, and

security upgrades.
o Estimated Cost: LKR 5,000,000 - 7,000,000
o Description: Covers hardware upgrades, data storage expansion, and
cybersecurity tools.

2. Automation of Administrative and Clinical Processes

 Automation Software for Administration: For tasks such as billing, appointments,
and record management.
o Estimated Cost: LKR 3,500,000 - 4,500,000
o Description: Includes licensing, customization, and implementation for
automating workflows.
 Clinical Process Automation: Streamlining patient intake, discharge, and inventory
tracking in pharmacy and labs.
o Estimated Cost: LKR 4,000,000 - 5,000,000
o Description: Primarily for integrating automation in clinical settings to reduce
wait times and improve accuracy.

80
W. Renato croos 00196592 Software development lifecycle
3. Staff Training and Change Management
 Training for ERP and Automation Systems: Training for medical, administrative,
and support staff.
o Estimated Cost: LKR 2,000,000 - 2,500,000
o Description: Cost includes trainer fees, training materials, and temporary
staffing for uninterrupted service.
 Change Management Program: Program to facilitate smooth transitions and reduce
resistance to new systems.
o Estimated Cost: LKR 1,000,000 - 1,500,000
o Description: Involves workshops, communications, and support resources to
manage organizational change.

4. Sustainability Initiatives
 Energy-Efficient Equipment: For eco-friendly lighting, HVAC systems, and energy
management solutions.
o Estimated Cost: LKR 3,000,000 - 4,000,000
o Description: Replacing old equipment with energy-efficient models to reduce
long-term operational costs.
 Waste Management System: Investment in systems to handle medical waste and
reduce environmental impact.
o Estimated Cost: LKR 1,500,000 - 2,000,000
o Description: Includes waste segregation and disposal technology and ongoing
waste handling contracts.

5. Compliance and Regulatory Costs

 Data Protection (GDPR Compliance): Upgrading data storage and access controls
to comply with data protection standards.
o Estimated Cost: LKR 2,500,000 - 3,500,000
o Description: Primarily includes software, encryption, and consultation fees to
ensure compliance.
 Certification and Quality Standards (ISO): Achieving and maintaining ISO
certification to uphold service quality.
o Estimated Cost: LKR 1,200,000 - 1,800,000

81
W. Renato croos 00196592 Software development lifecycle
 o Description: Includes audit fees, compliance resources, and certification
costs.

Total Estimated Cost Range: LKR 31,700,000 - 42,300,000

Summary
This cost analysis provides Hemas Hospital Wattala with a breakdown of the estimated
financial requirements to achieve improvements. The total investment focuses on building
operational efficiency, enhancing patient care, and ensuring compliance with regulatory
standards.

Analyzing the Software at Hemas Hospital Wattala with Software Analysis Tools
Digital transformation at Hemas Hospital Wattala is key to advancing healthcare services,
streamlining operations, and supporting data-driven decision-making. Through software
analysis tools, Hemas can enhance data collection, analysis, and reporting across multiple
departments, ensuring modern, effective, and compliant healthcare services. Below are
essential tools and methodologies that Hemas Hospital Wattala employs in its software
analysis processes:

1. Data Analytics Tools

o Purpose: Data analytics tools provide insights into patient demographics,
treatment patterns, and operational trends. They are essential for evaluating
patient outcomes, identifying resource allocation needs, and understanding key
performance metrics.
o Examples: Hemas uses tools such as Tableau, Power BI, and Google
Analytics to visualize and interpret data trends, which aids in strategic
planning, patient care enhancements, and hospital performance reviews.

2. Regulatory Compliance Software

o Purpose: In the healthcare sector, compliance with regulations (e.g., GDPR,
HIPAA) is essential to safeguard patient data and ensure legal adherence.
Compliance software helps Hemas to track, document, and meet necessary
regulatory standards.

82
W. Renato croos 00196592 Software development lifecycle
 o Examples: Hemas utilizes compliance management tools that automate the
tracking of regulatory updates, streamline data protection measures, and
provide documentation for audits, which reduces risk and supports patient
trust.

3. Financial Modeling Software

o Purpose: Financial modeling tools allow the hospital to conduct cost-benefit
analyses of new software implementations, assess the financial impact of
operational changes, and forecast revenue growth or cost reductions.
o Examples: Microsoft Excel and specialized financial modeling platforms are
used to evaluate the return on investment (ROI) of new technology
acquisitions and operational enhancements, supporting financially sound
decision-making.

4. Project Management Software

o Purpose: Project management software supports collaboration, task
allocation, and project tracking among teams. Hemas uses these tools to
ensure that software implementation projects are on schedule and align with
strategic objectives.
o Examples: Tools like Asana, Trello, and Microsoft Project facilitate
communication and tracking across departments, ensuring efficient task
completion and accountability in technology projects.

5. Market Research Tools

o Purpose: Understanding patient needs and preferences is crucial for service
improvement. Market research tools assist Hemas in gauging patient
satisfaction, identifying healthcare trends, and analyzing competitor offerings.
o Examples: Hemas may employ survey tools, focus group studies, and
competitive analysis software to understand market demands and guide
service expansions or improvements.

6. Security and Compliance Tools

83
W. Renato croos 00196592 Software development lifecycle
 o Purpose: Security tools are essential to protect sensitive patient information,
adhere to data privacy laws, and prevent data breaches. These tools assist in
managing cybersecurity risks and enforcing data protection protocols.
o Examples: Hemas uses advanced security platforms to safeguard data
integrity and confidentiality, supporting a secure healthcare environment for
both staff and patients.

7. Technology Assessment Software

o Purpose: Technology assessment tools help Hemas evaluate the compatibility
and scalability of its current software and hardware systems. This ensures that
any new technology fits well with existing infrastructure.
o Examples: Compatibility testing and technology assessment platforms enable
Hemas to assess the readiness of its technology stack for integration,
facilitating smoother digital transformations.

Through the strategic use of these tools, Hemas Hospital Wattala can improve its software
analysis capabilities, drive operational improvements, and maintain compliance. By enabling
data-driven, efficient, and secure healthcare delivery, Hemas enhances its service quality,
ensuring positive patient outcomes and setting a benchmark in modern healthcare practices.

84
W. Renato croos 00196592 Software development lifecycle
Figure 13: Software Analysis Tools
Source: (DucHiro et al., BA-Tools-thinhnotes 2019)

3.3 Managing Requirement Traceability During Software Development

Managing Requirement Traceability During Software Development for Hemas
Hospitals
Tracing software requirements is a fundamental method to ensure that the finished product
meets all specifications, adheres to timelines, and aligns with customer expectations.
Requirement traceability involves connecting each requirement to the design,
implementation, and testing phases of the software development lifecycle (SDLC). Below is a
detailed breakdown of how this process is implemented and its significance for Hemas
Hospitals.

1. Requirement Elicitation and Documentation

In the initial stages of a software project, stakeholders collaborate to elicit and document
requirements. This step is crucial as it establishes the foundation for the entire project.
Requirements are typically gathered through interviews, surveys, and discussions with clients
and end-users to ensure a comprehensive understanding of their needs.

85
W. Renato croos 00196592 Software development lifecycle
2. Requirement Analysis and Prioritization
Once requirements are collected, they undergo thorough analysis to verify their precision,
completeness, and feasibility. The requirements are then prioritized based on their importance
and relevance to the project objectives. This prioritization helps focus resources on the most
critical aspects of the project.

3. Requirement Traceability Matrix (RTM)

An essential tool for connecting requirements to subsequent stages of the software
development process is the Requirement Traceability Matrix (RTM). This matrix tracks each
requirement from its inception through to implementation and testing, serving as a reference
point to ensure that no requirement is overlooked throughout the project lifecycle.

4. Design Phase
During the design phase, system architects and designers create blueprints based on the
documented requirements. It is imperative that each design element corresponds to one or
more requirements in the RTM. This alignment ensures that the design adheres to the original
specifications and facilitates subsequent validation.

5. Implementation Phase
In the implementation phase, software developers utilize the design documents to write the
code. They should be able to trace each code component back to the design and ultimately to
the original requirements. Adopting good coding practices and including comments can
significantly ease this tracing process.

6. Testing Phase
Testers refer to the RTM to create test cases that validate whether the software satisfies each
requirement. This phase is critical for confirming that the software performs as intended and
meets the specified needs of the client. Thorough testing against documented requirements
enhances software quality and reliability.

7. Change Management
As changes and updates occur throughout the software development process, it is essential to
track these modifications back to the corresponding requirements. This practice ensures that

86
W. Renato croos 00196592 Software development lifecycle
any changes align with the original intent of the project and do not inadvertently introduce
new issues.

8. Validation and Verification

Once the software is complete, it undergoes validation and verification processes. Validation
confirms that the software meets the user’s needs as per the initial requirements, while
verification ensures that the software was developed according to the specified criteria. This
dual approach helps maintain high quality.

9. Post-release Monitoring
Even after the product has been launched, requirement traceability remains vital. It facilitates
ongoing updates, bug fixes, and feature additions, ensuring that any modifications reference
the pertinent requirements to maintain alignment with user needs and organizational goals.

Significance of Requirement Traceability

The importance of tracing requirements throughout the software lifecycle is multifaceted:
1. Alignment with User Needs: Requirement traceability ensures that the software
aligns with the needs of clients and end-users, which is crucial for achieving user
satisfaction.
2. Quality Assurance: It enhances software quality by verifying that all documented
criteria are met, reducing the likelihood of defects and rework.
3. Change Control: Effective requirement traceability facilitates change management,
ensuring that updates or modifications do not inadvertently affect other parts of the
software.
4. Risk Mitigation: By identifying issues early in the development process, requirement
traceability helps mitigate risks, making it easier and less expensive to address
potential problems.
5. Compliance: In regulated industries like healthcare, traceability is essential for
demonstrating compliance with standards and regulations, thereby protecting the
organization’s integrity.

Conclusion

87
W. Renato croos 00196592 Software development lifecycle
In conclusion, managing requirement traceability throughout the software lifecycle is a
systematic and rigorous approach to ensuring that software development remains on track,
meets client demands, mitigates risks, and maintains high-quality standards. By serving as a
link between initial requirements and the finished product, requirement traceability supports a
smooth software development process that ultimately benefits Hemas Hospitals and its
stakeholders.

3.4 Enhancing Software Quality: Exploring Two Vital Approaches

In software development, the quality of software is paramount, directly influencing the
reliability, functionality, and overall customer satisfaction of software products. Developers
and organizations employ various strategies and processes to ensure that software not only
meets but exceeds established quality standards. Among these strategies, Test-Driven
Development (TDD) and the combination of Code Review with Static Analysis stand out as
two fundamental methods for enhancing software quality.

Test-Driven Development (TDD) is a structured approach that initiates the development

process by writing tests prior to the actual coding. This method fosters a proactive, quality-
focused mindset by ensuring that the software functions as intended right from the beginning.
In contrast, Code Review and Static Analysis involve careful examination of the code by
peers and automated tools to identify potential issues and vulnerabilities. These techniques
are crucial for detecting defects and improving software maintainability.

88
W. Renato croos 00196592 Software development lifecycle
This discussion will delve into the principles, advantages, and disadvantages of Test-Driven
Development, as well as the combined use of Code Review and Static Analysis as key
methodologies for elevating software quality. Although each approach has distinct
characteristics, together they form a comprehensive strategy aimed at delivering reliable,
efficient, and secure software products.

1. Test-Driven Development (TDD)

Test-Driven Development is a methodology that prioritizes the creation of tests for software
components before writing the corresponding code. The TDD process typically follows these
steps:
 Write a Test: The developer formulates a test case that outlines the expected
behavior of a specific software component or function.
 Run the Test: Initially, the test fails since the necessary code has not yet been
implemented.
 Write the Code: The developer writes the minimal code required to pass the test.
 Rerun the Test: The test is executed again. If it passes, it indicates that the code
meets the specified requirements. If it fails, the developer adjusts the code until the
test passes.
 Refactor: Once the test passes, the developer can refine the code for better efficiency
and readability.

Figure 14: Test-Driven Development (TDD)

89
W. Renato croos 00196592 Software development lifecycle
Source: (ZealousSystemPvtLtd, What is Test Driven Development (TDD)? examples,
benefits, implementation 2024)

Code Review and Static Analysis

Code Review is a structured evaluation of source code conducted by peers or automated
tools, aimed at identifying and correcting issues, bugs, and breaches of coding standards.
Static Analysis, in contrast, entails reviewing the code without executing it. Both methods
are vital for enhancing software quality.

 Peer Code Review: In this process, developers examine each other's code to spot
issues, provide constructive feedback, and ensure adherence to coding standards and
best practices. Peer reviews are effective in identifying logical errors, security
vulnerabilities, and design flaws.
 Static Analysis Tools: These automated tools assess the source code for potential
problems without running the program. They can uncover issues such as memory
leaks, incorrect variable usage, and security vulnerabilities. Static analysis tools are
particularly beneficial for managing large and complex codebases.

90
W. Renato croos 00196592 Software development lifecycle
Figure 15: Code Review
Source: (Miquido & Boruń, What is a code review: Process, Benefits & Best Practices 2023)

TDD and code review/static analysis are complementary approaches that, when used
together, can significantly elevate software quality and reliability. TDD (Test-Driven
Development) emphasizes writing tests before coding to validate that each function performs
as intended, promoting a proactive quality-first approach. This ensures that every aspect of
the code meets functional requirements from the beginning.

In contrast, code review and static analysis focus on refining the code’s structure, correctness,
and maintainability. Code reviews, conducted by peers, help catch logic flaws, design issues,
and security risks, fostering collaborative improvement and knowledge sharing. Static
analysis tools go further by scanning code without execution, automatically detecting issues
like memory leaks, improper resource handling, and syntax violations, which are particularly
valuable in large and complex codebases.

By combining TDD with code review and static analysis, developers can create a robust,
high-quality codebase. TDD provides a functional foundation, while code review and static
analysis refine the code, aligning it with best practices and standards. Together, these

91
W. Renato croos 00196592 Software development lifecycle
methods help minimize bugs, reduce vulnerabilities, and produce software that is both
reliable and resilient.
3.5 Effectiveness of Systems Investigation in Enhancing Software Quality
In today’s dynamic digital landscape, software quality is essential for organizations aiming to
bolster competitiveness, operational efficiency, and customer satisfaction. For a leading
conglomerate like Hemas, which operates across sectors such as healthcare, FMCG, and
leisure, a rigorous systems investigation is key to ensuring high software quality that supports
its multifaceted operations.

Hemas's commitment to quality and market leadership is tightly linked to an effective

systems investigation process. This process centers on analyzing business and system
requirements, identifying gaps, ensuring regulatory compliance, and aligning technology with
business needs—foundations that are crucial for enhancing software quality.

This analysis highlights how Hemas’s tailored approach to systems investigation enhances
software quality by clarifying requirements, managing risks, adhering to regulations,
engaging stakeholders, and aligning with larger business objectives. A well-executed systems
investigation is integral to Hemas’s pursuit of high-quality software that supports operational
excellence.

1. Technology Assessment
Evaluating Hemas’s current technological infrastructure is essential. Outdated systems can
hinder software quality and reliability. Through systems investigation, Hemas can identify
areas in need of updates, ensuring a modern tech stack that supports efficient, high-quality
software development.

2. Risk Mitigation
A critical aspect of the investigation process is risk assessment, which helps Hemas identify
potential issues early on. By proactively addressing these risks, Hemas safeguards software
quality, ensuring the final product is secure and dependable.

3. Alignment with Business Goals

92
W. Renato croos 00196592 Software development lifecycle
The systems investigation process ensures that software aligns with Hemas’s business
objectives. This alignment is crucial for developing solutions that add value, enhance service
delivery, and meet strategic goals, ultimately elevating software quality.
4. Cost-Benefit Analysis
Conducting a cost-benefit analysis helps Hemas balance the costs of software implementation
with expected returns. This strategic allocation of resources fosters cost-effective solutions
that contribute to higher software quality and long-term operational efficiency.

5. Stakeholder Engagement
Engaging stakeholders across Hemas’s various sectors enriches the investigation by
incorporating diverse insights and needs. This involvement leads to software that is not only
high in quality but also tailored to user expectations and business requirements.

In conclusion, Hemas leverages systems investigation as a fundamental tool for advancing

software quality and achieving excellence across its operations. This process plays a crucial
role in ensuring that software meets high standards, an essential factor in the fast-paced
digital environment.

Through this customized approach, Hemas ensures regulatory compliance, mitigates risks,
and enhances stakeholder confidence. By engaging stakeholders and aligning with key
business objectives, Hemas fosters a collaborative culture that prioritizes continuous quality
improvement. This solid foundation of software quality supports Hemas’s vision for
innovation and operational excellence, reinforcing its status as a leader in multiple industries.

93
W. Renato croos 00196592 Software development lifecycle
LO4 Discuss the suitability of software behavioral design techniques.

4.1 ERD for Hemas Hospitals Wattala

Figure 16: ERD

Source: Author’s work

The image shows an Entity-Relationship Diagram (ERD), visually representing the data and
relationships within a system. This ERD could be applied to a healthcare management system
like Hemas Hospital, illustrating key entities and their interconnections.

Entities and Relationships:

To design an ERD (Entity-Relationship Diagram) for Hemas Wattala Hospital, we would

typically identify the key entities involved in hospital operations, such as patients, doctors,
appointments, departments, and billing. Here’s an example of how an ERD for a hospital
might be structured:

94
W. Renato croos 00196592 Software development lifecycle
 1. Entities and Attributes:
o Patient
 Patient_ID (Primary Key)
 Name
 Address
 Date_of_Birth
 Contact_Number
 Gender
 Medical_History
o Doctor
 Doctor_ID (Primary Key)
 Name
 Specialty
 Contact_Number
 Department_ID (Foreign Key referencing Department)
 Schedule
o Appointment
 Appointment_ID (Primary Key)
 Patient_ID (Foreign Key referencing Patient)
 Doctor_ID (Foreign Key referencing Doctor)
 Appointment_Date
 Appointment_Time
 Status (e.g., Scheduled, Completed, Canceled)
o Department
 Department_ID (Primary Key)
 Name
 Location
 Head_ID (Foreign Key referencing Doctor for Head of Department)
o Billing
 Billing_ID (Primary Key)
 Appointment_ID (Foreign Key referencing Appointment)
 Patient_ID (Foreign Key referencing Patient)

95
W. Renato croos 00196592 Software development lifecycle
  Billing_Date
 Amount
 Payment_Status (e.g., Paid, Pending)
o Medical_Record
 Record_ID (Primary Key)
 Patient_ID (Foreign Key referencing Patient)
 Doctor_ID (Foreign Key referencing Doctor)
 Diagnosis
 Treatment
 Prescription
 Record_Date
Here’s a summary of the relationships depicted in the Entity-Relationship Diagram (ERD) for
Hemas Hospital:
1. Patient and Appointment: Each patient can book multiple appointments, and each
appointment is linked to a specific patient. This relationship helps track patient visits
and appointment details.
2. Doctor and Appointment: Each doctor can have multiple appointments, and each
appointment is associated with one doctor. This relationship allows the system to
allocate doctors to appointments and manage their schedules.
3. Patient and Billing: Each patient can have multiple billing records, and each billing
record is linked to a specific patient. This relationship is essential for managing
patient invoices and payment histories.
4. Doctor and Department: Each doctor belongs to one department, and each
department can have multiple doctors. This relationship organizes doctors within their
specialized departments (e.g., Cardiology, Pediatrics).
5. Department and Staff: Each department can have multiple staff members, while
each staff member is associated with a specific department. This helps in assigning
and managing hospital staff according to their department roles.
6. Staff and Billing: Staff members, such as billing clerks, manage and process billing
records. This relationship connects billing records to the staff responsible for handling
them.

96
W. Renato croos 00196592 Software development lifecycle
 7. Medical Records and Patient: Each patient has medical records, which store
important health information. This one-to-many relationship helps track a patient's
medical history over time.
These relationships form the backbone of the hospital’s data structure, ensuring an organized
and interconnected flow of information across patients, doctors, staff, appointments, and
billing.

4.2 Use Case Diagram for Hemas Hospitals Wattala

Figure 17: Use Case Diagram

Source: Author’s work

97
W. Renato croos 00196592 Software development lifecycle
Actors
1. Patient: Represents the hospital’s patients who can interact with the system to
manage their healthcare needs.
2. Admin: Represents the hospital administrative staff responsible for managing hospital
records, appointments, billing, and overall operations.
3. Doctor: Represents the doctors in the hospital who interact with patient records and
appointments.

Use Cases
Patient Use Cases
1. Book Appointment
o The Patient schedules an appointment with a doctor.
o The system checks the doctor’s availability before confirming the
appointment.
2. View Appointment Details
o The Patient views details of their scheduled appointments, including date,
time, and doctor’s name.
3. Access Medical History
o The Patient can view their medical records, including past diagnoses,
treatments, and lab results.
4. View Billing Information
o The Patient reviews their billing information, including invoices for treatments
and consultations.
5. Make Payment
o The Patient makes payments for services rendered, such as consultations,
treatments, or lab tests.
Admin Use Cases
1. Manage Patient Records
o The admin adds, updates, and maintains patient information, including
personal and medical details.
2. Schedule Appointments
o The admin schedules appointments for patients, checking doctor availability
and confirming the time and date.

98
W. Renato croos 00196592 Software development lifecycle
 3. Update Appointment Status
o The admin updates the status of appointments (e.g., confirmed, rescheduled, or
canceled) based on patient or doctor inputs.
4. Manage Billing
o The admin creates and updates billing records for patients, detailing charges
for various hospital services.
5. Generate Reports
o The admin generates reports on hospital operations, such as patient visits,
revenue, and department efficiency.
6. Manage Doctor and Staff Records
o The admin manages records for doctors and staff, including roles, schedules,
and department assignments.
Doctor Use Cases
1. View Patient Records
o The Doctor accesses patient records for review before or during consultations.
2. Update Medical Records
o The Doctor updates medical records after consultations, recording diagnoses,
prescriptions, and follow-up instructions.
3. View Appointments
o The Doctor views their scheduled appointments to manage their daily
schedule.

99
W. Renato croos 00196592 Software development lifecycle
4.3 Finite state machine (FSM) and Extended Finite State Machine (EFSM)
4.3.1 Finite state machine (FSM)
A Finite State Machine (FSM) is a mathematical model used by programmers, engineers,
and mathematicians to represent systems that have a limited number of defined states. It helps
model systems where actions depend on certain conditions or inputs. A common example is a
video game controller, where pressing specific buttons triggers corresponding actions in the
game.

Components of a Finite State Machine

An FSM consists of:
 A set of possible input events: Different actions or signals that can affect the system.
 A set of potential output events: Actions or responses triggered by the inputs.
 A set of defined states: Conditions that the system can exist in, with the FSM
transitioning between them based on inputs.

FSMs can be implemented in software or hardware to simplify complex problems by

allowing a system to exist in only one state at a time from a finite list. This makes it easier to
analyze and test every input-output scenario.

FSMs range from abstract representations, like business models in illustrations, to concrete
applications, such as vending machines or computers. Unlike an FSM, a fuzzy state
machine allows for data that doesn't fit into strict categories, handling more ambiguous
information.
Though the term “machine” usually implies a physical component, here it refers to an
abstract model that could be represented in many forms, from digital inputs to theoretical
models. This ties into automata theory, a field of computer science and discrete
mathematics focused on the logic of computational models. The main types of models in
automata theory are:

 Finite State Machines (FSMs): Represent systems with a limited number of defined
states.
 Pushdown Automata: Use memory stacks to handle more complex models than
FSMs.

100
W. Renato croos 00196592 Software development lifecycle
  Linear-Bounded Automata (LBA): Similar to a Turing machine but limited to finite
input data.
 Turing Machines: The most advanced model, capable of testing various input
combinations for complex analysis.

These computational models are foundational in automata theory and are widely used in
fields where system logic and conditional behavior need to be systematically modeled and
analyzed.

Advantages of FSM Disadvantages of FSM

1. Simple Design: FSMs are easy to create and 1. Scalability Challenges: Managing
suitable for systems with defined states and FSMs becomes complex as the system
transitions. grows with more states and transitions.
2. Clear and Defined Behavior: Each state 2. Limited Flexibility: FSMs may not
and transition is explicitly defined, making the handle dynamic or complex conditions
system operation understandable. requiring context or variable data well.
3. Ease of Debugging: With a known state at 3. State Explosion: An increase in
any time, tracing and debugging errors is possible inputs and outputs can lead to an
straightforward. exponential growth in states, complicating
management.
4. Predictability: FSMs have deterministic 4. Parallelism Limitations: FSMs do not
behavior, providing predictable outcomes for handle parallel or concurrent states
given inputs, ensuring stability. effectively, making them unsuitable for
multitasking.
5. Ideal for Control Systems: FSMs are well- 5. Memory Consumption: Large FSMs
suited for systems requiring repeatable, specific with numerous states may require
control processes like workflow and hardware considerable memory and processing
management. power.
6. Efficiency in Simple Systems: For systems 6. Rigid Structure: FSMs have a fixed
with few states and transitions, FSMs are structure, limiting adaptability to real-time
resource efficient. changes or complex decision-making.

Table 2: Advantages & disadvantages of FSM

101
W. Renato croos 00196592 Software development lifecycle
Source: Author’s work

102
W. Renato croos 00196592 Software development lifecycle
4.3.2 Extended Finite State Machine (EFSM)

An Extended Finite State Machine (EFSM) builds upon the basic Finite State Machine (FSM)
by introducing advanced features that allow for handling complex and dynamic system
behaviors. While FSMs model systems with a limited set of states and transitions, EFSMs
add extra components to increase control and flexibility. Here are the main features of
EFSMs:
 Variables:
EFSMs incorporate variables to store data that can change during system execution.
These variables enable EFSMs to model transitions that depend on conditions or
specific data values in addition to events, facilitating more complex system behaviors.

 Parameterized Actions:
Actions triggered by transitions in EFSMs can accept parameters. This flexibility
allows the system to react based on input values or stored data, providing dynamic
control over transition effects, which is not achievable in a standard FSM.

 Guards:
Guards are conditions that must be fulfilled for a transition to occur. EFSMs allow
guard conditions on transitions, which means state changes can depend on specific
criteria. This adds a layer of logic to transitions, supporting more sophisticated
decision-making.

 Expanded Notation:
EFSMs often use detailed notations to represent complex relationships between states,
actions, and conditions. These notations include additional symbols or annotations,
making EFSMs more appropriate for designing intricate systems.

 Hierarchical Structure:
EFSMs can represent states in a hierarchical layout, grouping related states in layers.
This structure helps organize and visualize systems with multiple abstraction levels,
making the design more understandable and manageable. Hierarchical states also
allow for efficient modeling of systems with nested behaviors.

103
W. Renato croos 00196592 Software development lifecycle
EFSMs are well-suited for systems requiring detailed behavior modeling, where conditions,
variables, and external data influence state transitions. They are commonly applied in fields
such as software engineering, protocol design, and web applications, offering a powerful tool
for analyzing and modeling complex systems.

Advantages of Extended Finite StateDisadvantages of Extended Finite State

Machine (EFSM) Machine (EFSM)
Enhanced Flexibility: EFSMs can handleIncreased Complexity: The added features like
complex behaviors and conditions throughvariables, guards, and hierarchical states make
variables, guards, and parameterized actions,EFSMs more complicated to design and
making them suitable for sophisticatedunderstand, especially for larger systems.
systems.
Dynamic Decision-Making: EFSMs supportDifficult to Debug: Due to the complexity of
conditional transitions based on data and additional states and conditions, tracing errors
events, enabling more intelligent, context- and debugging EFSMs can be challenging.
sensitive responses.
Hierarchical Modeling: EFSMs allow statesResource Intensive: Implementing EFSMs
to be organized hierarchically, which isoften requires more memory and processing
useful for visualizing and managing systems power compared to standard FSMs, as the
with multiple levels of abstraction. system must manage additional variables and
conditions.
Greater Modeling Power: EFSMs canRisk of State Explosion: With increased states
model complex systems and scenarios thatand conditions, there is a risk of state explosion,
standard FSMs cannot, such as those making it hard to manage and maintain all
involving intricate workflows and protocols. possible state combinations.
Suitable for Complex Applications: EFSMsSteeper Learning Curve: Understanding and
are ideal for applications with complex logic, implementing EFSMs requires more advanced
such as protocol design, embedded systems,knowledge compared to FSMs, leading to a
and software workflows. steeper learning curve for developers.
Table 3: Advantages & disadvantages of EFSM
Source: Author’s work

104
W. Renato croos 00196592 Software development lifecycle
4.3.3 Differentiate between a Finite State Machine (FSM) and an Extended Finite State
Machine (EFSM):

Aspect Finite State Machine (FSM) Extended Finite State Machine

(EFSM)
Basic Structure Consists of a finite number of Adds more complexity by
states and transitions based on incorporating variables, guards, and
input events. parameterized actions.
Transition Transitions occur based solely on Transitions depend on events as well
Conditions events or inputs. as specific conditions (guards) or
data values.
Variables Lacks the ability to store data; Uses variables to store data, which
states do not retain variables. can influence state transitions.
Flexibility Limited to simple systems with Offers greater flexibility and can
predictable state changes. model systems with complex,
dynamic behaviors.
Modeling Suitable for straightforward Ideal for complex applications where
Complexity applications where each state decision-making requires conditional
change is clearly defined. transitions.
Decision Logic Limited decision-making based Allows for complex decision-making
only on predefined states and by using guards and conditions on
inputs. transitions.
Hierarchical Typically lacks a hierarchy, each Supports hierarchical structuring,
States state stands alone. making it easier to model nested or
layered states.
Applications Commonly used for basic control Suitable for intricate systems like
systems, simple workflows, or protocol design, web applications,
sequential logic. and advanced workflows.
Resource Generally lightweight and efficient, Often resource-intensive due to the
Requirements with minimal memory and additional data and logic involved.
processing needs.
Ease of DebuggingEasier to debug and analyze due to More challenging to debug because
straightforward structure. of added variables, guards, and

105
W. Renato croos 00196592 Software development lifecycle
 complex conditions.
Example Simple vending machine or Software workflows or protocols
turnstile with a fixed set of inputs requiring conditional logic and
and outputs. dynamic states.
Table 4: Differentiate between FSM and EFSM
Source: Author’s work

In summary, FSMs are simpler models best suited for straightforward systems with limited
states and fixed transitions. EFSMs, on the other hand, are more advanced and better suited
for complex, dynamic systems where state changes depend on conditions, data, and
hierarchical structures.

4.4 dependability and efficacy of SPF (Special Provident Fund) software

Aspect Dependability Efficacy
Reliability Operates without interruptions, Ensures smooth processing of
ensuring continuous service; transactions and access to records
includes backups and error for users without performance
recovery systems. issues.
Accuracy & Accurate calculation of Ensures accurate and consistent
Consistency contributions, interest, and results for users, reducing manual
balances; applies updates correction needs.
consistently.
Security & Data Implements strong security Protects user and financial data
Integrity measures (e.g., encryption, role- from unauthorized access,
based access) to protect sensitive enhancing user trust in the
data. software.
Fault Tolerance Has redundancy and failover Minimizes downtime and data
mechanisms to handle unexpected corruption, keeping the system
events and prevent data loss. functional in case of issues.
User-Friendly N/A Intuitive interface for easy
Interface navigation, reducing the learning
curve for administrators and
employees.

106
W. Renato croos 00196592 Software development lifecycle
Performance & N/A Maintains fast response times, and
Scalability can handle increasing users or
transactions as the organization
grows.
Compliance & N/A Supports compliance with
Reporting regulations and provides detailed
reporting for audits and reviews.
Automated ProcessesN/A Automates tasks (e.g., contribution
& Notifications updates), and provides alerts to
streamline operations.
Flexibility & N/A Allows customization for specific
Customization policies and integrates with
payroll/HR systems for smooth
workflows.
Table 5: dependability and efficacy of SPF (Special Provident Fund) software
Source: Author’s work

The development of data-driven, web-based software for the Special Provident Fund (SPF)
significantly enhances decision-making and operational efficiency. Key features include:

 Real-Time Monitoring: Continuous tracking of fund contributions, withdrawals, and

balances to ensure better transparency.
 Predictive Capabilities: Forecasting trends related to future fund needs and
employee withdrawal patterns, enabling proactive management.
 User Feedback Analysis: Collecting and analyzing user feedback to continually
improve system performance and enhance user experience.
 Security Advancements: Implementing robust data-driven security measures,
including fraud detection and anomaly monitoring, to safeguard sensitive financial
information.
 Efficient Claims Processing: Streamlining and automating claims submission,
verification, and disbursement through data-driven workflows, resulting in faster and
more accurate processing.
 Regulatory Compliance: Automatically updating the system to adhere to changing
legal and financial regulations, ensuring ongoing compliance.
107
W. Renato croos 00196592 Software development lifecycle
  Cost Optimization: Analyzing operational data to identify opportunities for cost
reduction in system maintenance, employee management, and fund disbursements.

Together, these features contribute to the stability, effectiveness, and efficiency of SPF
software in managing provident funds for employees.

4.4.1 Components related to data driven

Here are key components related to data-driven software and decision-making:

1. Data Collection:
o Sources: Various sources of data, including user interactions, transactions,
sensors, and external APIs.
o Techniques: Methods for gathering data, such as surveys, web scraping, or
IoT devices.

2. Data Storage:
o Databases: Use of relational databases (e.g., MySQL, PostgreSQL) and
NoSQL databases (e.g., MongoDB, Cassandra) for storing structured and
unstructured data.
o Data Warehouses: Centralized repositories (e.g., Amazon Redshift, Google
BigQuery) for aggregating data from multiple sources for analysis.

3. Data Processing:
o ETL (Extract, Transform, Load): Processes that extract data from various
sources, transform it into a usable format, and load it into data storage
systems.
o Real-time Processing: Technologies like Apache Kafka or Apache Flink that
enable processing data in real time for immediate insights.

4. Data Analysis:
o Statistical Analysis: Techniques for interpreting data using statistical methods
to derive insights.
o Machine Learning: Algorithms that learn from data to identify patterns and
make predictions (e.g., supervised and unsupervised learning).
108
W. Renato croos 00196592 Software development lifecycle
 5. Data Visualization:
o Tools: Software for creating visual representations of data (e.g., Tableau,
Power BI, D3.js) to help stakeholders understand complex datasets.
o Dashboards: Interactive interfaces that display key metrics and insights in
real time.

6. Predictive Analytics:
o Modeling Techniques: Use of regression analysis, time series analysis, and
machine learning models to forecast future trends based on historical data.

7. User Feedback and Interaction:

o Feedback Loops: Systems for capturing user feedback to continuously
improve software performance and user experience.
o A/B Testing: Experimental approach to compare two versions of a software
feature to determine which performs better.

8. Data Security:
o Protocols: Implementing security measures such as encryption, access
controls, and anomaly detection to protect sensitive data.
o Compliance: Adhering to regulations (e.g., GDPR, HIPAA) to ensure data
protection and privacy.

9. Infrastructure:
o Cloud Computing: Utilizing cloud platforms (e.g., AWS, Azure, Google
Cloud) for scalable storage and computing power.
o Big Data Technologies: Tools like Hadoop and Spark for processing and
analyzing large datasets that traditional tools cannot handle.

10. Integration:
o APIs: Application Programming Interfaces that allow different software
systems to communicate and share data.
o Middleware: Software that connects different applications or services,
facilitating data exchange and integration.

109
W. Renato croos 00196592 Software development lifecycle
These components work together to enable organizations to harness the power of data,
leading to more informed decision-making, enhanced operational efficiency, and improved
user experiences.

4.4.2 justifications of driven software improve the reliability and effectiveness of SPF
(Special Provident Fund) web base software

Data-driven software has emerged as a transformative force in enhancing the reliability and
effectiveness of software applications. Its core capability lies in gathering, processing, and
utilizing data to inform decision-making and actions. Integrating data-driven techniques into
software development and operation offers significant advantages across various sectors.
Below are key justifications for how data-driven software improves both reliability and
efficacy:
1. Informed Decision-Making:
Data-driven applications leverage historical and real-time data to facilitate agile
decision-making. This capability is crucial in fields such as banking, healthcare, and
autonomous systems, where timely decisions are essential. For instance, in
algorithmic trading, data-driven software can analyze market conditions and execute
trades automatically, optimizing investment strategies and minimizing risks. In
healthcare, it can assess patient data to personalize treatment plans and identify
illnesses early.

2. Predictive Analytics:
Predictive analytics empowers data-driven software to forecast future trends and
events. By examining historical data for patterns, software can assist in resource
allocation, risk management, and proactive decision-making. For example, in supply
chain management, data-driven software can optimize inventory levels and anticipate
demand fluctuations, ensuring that products are available when needed. In
manufacturing, predictive maintenance helps reduce costly downtime by predicting
equipment failures.

3. Continuous Improvement:
Reliable software necessitates ongoing monitoring and enhancement. Data-driven
software continually collects and analyzes performance data, user behavior, and

110
W. Renato croos 00196592 Software development lifecycle
 system health, facilitating proactive maintenance and optimization. This continuous
improvement cycle, exemplified by DevOps practices, allows software systems to
evolve and become more reliable over time.

4. Personalization and User Experience:

Data-driven software has transformed user experiences through personalized content
and recommendations. E-commerce platforms like Amazon analyze user behavior to
suggest tailored product recommendations, enhancing engagement and increasing
sales. Similarly, streaming services such as Netflix utilize viewing history and
feedback to recommend content that aligns with individual preferences.

5. Enhanced Security:
In software development, security is paramount. Data-driven techniques have
strengthened security measures through anomaly detection systems that monitor
network traffic and user behavior for unusual patterns indicative of cyberattacks.
These systems can respond automatically to mitigate threats, thereby improving
system reliability and safeguarding sensitive data.

In conclusion, data-driven software is indispensable for enhancing the reliability and

effectiveness of software applications. By leveraging real-time and historical data, predictive
analytics, continuous improvement practices, and automation, organizations can make
informed decisions, optimize operations, and enhance user experiences. Furthermore, data-
driven software ensures regulatory compliance, strengthens security, and personalizes
content. Its adaptability also enhances fault tolerance, scalability, and energy efficiency,
streamlining business processes and reducing manual workloads.

As software systems continue to grow in complexity and relevance, data-driven techniques

pave the way for increased reliability and effectiveness. By harnessing the power of data,
organizations can improve customer service, manage resources more efficiently, and make
informed decisions. In today’s information-driven environment, data-driven software is
essential for achieving efficacy and reliability, enabling applications to evolve, adapt, and
thrive in their respective domains.

111
W. Renato croos 00196592 Software development lifecycle
Reference:

Datarob (2020) Understanding the software development life cycle, Datarob. Available at:
https://datarob.com/essentials-software-development-life-cycle/ (Accessed: 29 October
2024).

K, S. (2023) The waterfall model: A linear approach to software development, Medium.

Available at: https://medium.com/@ksandhya/the-waterfall-model-a-linear-approach-to-
software-development-73bb48e154b4 (Accessed: 29 October 2024).

What is the V-model? (definition, examples) (no date) Built In. Available at:
https://builtin.com/software-engineering-perspectives/v-model (Accessed: 29 October
2024).

(No date) Sequential development process. | download scientific diagram. Available at:
https://www.researchgate.net/figure/Sequential-development-process_fig1_318181157
(Accessed: 31 October 2024).

Rana, K. (2023) Rad Model - phases, Advantages & Disadvantages, ArtOfTesting. Available
at: https://artoftesting.com/rad-model (Accessed: 31 October 2024).

Lanka Business News (2020) A statement from Hemas Hospital thalawathugoda, Lanka
Business News. Available at: https://www.lankabusinessnews.com/a-statement-from-
hemas-hospital-thalawathugoda/ (Accessed: 31 October 2024).

What are the benefits of a feasibility study (no date) FasterCapital. Available at:
https://fastercapital.com/topics/what-are-the-benefits-of-a-feasibility-study.html
(Accessed: 31 October 2024).

DucHiro et al. (2019) BA-Tools-thinhnotes, Thinhnotes. Available at:

https://thinhnotes.com/chuyen-nghe-ba/ky-nang-can-co-cua-nguoi-lam-ba-tap-cuoi/
attachment/ba-tools-thinhnotes/ (Accessed: 01 November 2024).

ZealousSystemPvtLtd (2024) What is Test Driven Development (TDD)? examples, benefits,

implementation, Zealous System. Available at: https://www.zealousys.com/blog/what-is-
test-driven-development/ (Accessed: 01 November 2024).

Miquido and Boruń, Ł. (2023) What is a code review: Process, Benefits & Best Practices,
Miquido. Available at: https://www.miquido.com/blog/what-is-code-review/ (Accessed: 01
November 2024).

Software engineering: Spiral model (2023) GeeksforGeeks. Available at:

https://www.geeksforgeeks.org/software-engineering-spiral-model/ (Accessed: 12
October 2023).

112
W. Renato croos 00196592 Software development lifecycle
Faculty, P.S. et al. (2022) Software development life cycle approaches: SDLC
models, H2kinfosys Blog. Available at: https://www.h2kinfosys.com/blog/sdlc-
models/ (Accessed: 12 October 2023).

Iterative model: Examples: Advantages and disadvanatges (2023) EDUCBA.

Available at: https://www.educba.com/iterative-model/ (Accessed: 12 October
2023).

Kumar, A. (2023) Sequence to sequence models: Types, examples, Analytics Yogi.

Available at: https://vitalflux.com/sequence-models-data-types-examples/
(Accessed: 12 October 2023).

113
W. Renato croos 00196592 Software development lifecycle