UNIT 7: SOFTWARE

DEVELOPMENT LIFE
CYCLE
Assignment 1: Different Types of Software Development Life
Cycle and Feasibility Study

Lin Kaung Myat

Contents
P1.....................................................................................................................................................4

What is SDLC Methodology?...........................................................................................................4

Waterfall Model...........................................................................................................................4

Phases of Waterfall Model...........................................................................................................4

Advantages Of Waterfall Model...................................................................................................5

Disadvantages of Waterfall Model...............................................................................................5

Agile Model..................................................................................................................................6

Spiral Model.................................................................................................................................6

Advantages Of Agile Model..........................................................................................................7

Disadvantages Of Agile Model.....................................................................................................7

V-shaped Model...........................................................................................................................7

V-shaped Model’s Diagram..........................................................................................................8

P2.....................................................................................................................................................9

Risk Management............................................................................................................................9

1. Identify the risk......................................................................................................................10

It need not be depressing for your business to prepare for potential project hazards; on the
other hand, it may really be a source of excitement. The process of identifying risks is one that
your entire team can benefit from and enjoy. Anything that might affect a project's time,
money, or success is considered a risk.......................................................................................10

2. Analyze the risk......................................................................................................................10

In order to determine where to focus first, your team will analyze the probability and impact
of each risk through this stage. You will next decide on an approach for dealing with each risk.
Accurate risk assessment depends on a number of factors, including the severity of the
impact, time wasted, and the possibility of financial loss to the company. By carefully
1
 examining each risk, you may identify any problems that frequently arise during a project and
improve the risk management procedure moving forward.......................................................10

3. Prioritize the risk....................................................................................................................10

This stage reveals the project's overall perspective to you and indicates the areas on which
the team should concentrate its efforts. Most importantly, it will help you come up with
reasonable options for each threat. This prevents significant delays or interruptions to the risk
management workflow throughout the treatment phase........................................................10

4. Treat the risk..........................................................................................................................10

5. Monitor the risk.....................................................................................................................10

P3...................................................................................................................................................11

The Purpose of Feasibility Study....................................................................................................11

Purpose of Economic Feasibility....................................................................................................12

Even though you may be aware of the building costs, it's essential to be aware of its
maintenance costs. You should think about how long it will take for a project to break even
whether it will continue to generate income after it is finished through leasing or commercial
usage. Investors frequently ask for a feasibility study to evaluate a company's level of risk. This
frequently involves a cost-benefit analysis and could help in reducing wasteful spending..........12

Purpose of Schedule Feasibility.....................................................................................................12

Finding the probability that a project will be finished by its scheduled due date and within the
time frame specified limitations is what this technique is all about. A project's schedule
feasibility is rated well if there is a good chance it will be finished on time. If a project takes
longer than expected, it will likely fail in many circumstances because it may lose its advantages,
efficiency, and profitability due to changing external environmental factors...............................12

Purpose of Technical feasibility......................................................................................................12

Purpose of Operational Feasibility.................................................................................................13

2
The organization's ability to implement a certain solution is determined by its feasibility. It
serves as an indication for public opinion of the project or system..............................................13

• Is the system supported by management?.................................................................................13

• How do the system's end users feel about their position in it?.................................................13

• Which managers or end users are going to object to or refuse to utilize the system? Can this
issue be solved? How, if so?..........................................................................................................13

• Testing for usability.....................................................................................................................13

• User satisfaction, ease of use, and ease of learning...................................................................13

P4...................................................................................................................................................13

How technical solutions can be compared....................................................................................13

Economic Feasibility Study............................................................................................................13

M1..................................................................................................................................................18

Hospital Management System.......................................................................................................18

System Overview...................................................................................................................18

Suitable SDLC Model for HMS system...................................................................................19

Reasons why Waterfall Model is selected for HMS system...................................................19

M2..................................................................................................................................................21

Components of a feasibility report................................................................................................21

References.....................................................................................................................................23

3
P1

What is SDLC Methodology?

 SDLC (Software Development Lifecycle) is the software development process which used
in the software industry to develop a new software product.

 The main purpose of SDLC is to produce high-standard software that meets customer’s
expectations and needs in the shortest time of production.

 It includes basically six stages that are planning, analysis, design, implementation and
deployment.

 Methodology is a particular procedure or set of procedures. In fact, SDLC Methodology

means the way of implementing the SDLC phases.

 The goals of SDLC are has never changed but people developed different methodologies
to get a better way of implementing the SDLC.

Waterfall Model
Waterfall Model is one of the SDLC Methodologies which is like the flow, passing step by
step through the all stages – analysis, design, implementation, test, maintain etc. This model
includes progressive execution of each step in full. This process is strictly documented and
predefined with the expected functionality for each phase of this software development life
cycle model.

Phases of Waterfall Model

4
 Diagram 1.1

Advantages Of Waterfall Model

 It is simple to apply and understand
 Managing is simple due to its rigidity: each phase includes a defined result and process
review
 Development breaks out step by step
 The model is for the small or mid-sized level projects where requirements are not
equivocal

Disadvantages of Waterfall Model

 The software is ready to use only after all the stage is over
 There may be high risks and uncertainties
 Not suitable for complex and object-oriented projects
 Should not use for the long-term projects

5
Agile Model
 Agile is and iterative way of making a project which includes customer collaboration.
Moreover, it is highly flexible to make changes.
 This software development methodology is all about delivering small pieces of working
software rapidly to improve customer satisfaction.
 It is an approach to software development that seeks the continuous delivery of working
software created in fast iterations.

Diagram 1.2

Spiral Model
The waterfall model, iterative development, and incremental development are all
components of the software development process called the spiral model. It is a risk-driven
process model which puts an emphasis on risk management and the creation of a strong
prototype.

6
 Diagram 1.3

Advantages Of Agile Model

 High amount of risk analysis
 Useful for large and mission-critical projects.

Disadvantages Of Agile Model

 Can be a costly model to use.
 Risk analysis needed highly particular expertise
 Doesn't work well for smaller projects.

V-shaped Model
 Validation and verification are given priority in the structured approach used in V-shaped
software development.
 This approach makes sure that each stage is thoroughly verified before proceeding. This
approach helps software engineers reduce the possibility of mistakes and rework,
resulting in a well-designed and well tested software product.

7
  The focus remains on meeting customer requirements and satisfying end-user needs,
resulting in a positive software experience.

V-shaped Model’s Diagram

Diagram 1.4

8
P2

Risk Management
The process of identifying, analyzing, and controlling risks to an organization's resources and profits
is known as risk management. These risks have many different causes, such as economic unpredictability, legal
responsibilities, technological problems, strategic management mistakes accidents, and natural calamities.

Diagram 2.1

9
1. Identify the risk
It need not be depressing for your business to prepare for potential project hazards; on
the other hand, it may really be a source of excitement. The process of identifying risks is one
that your entire team can benefit from and enjoy. Anything that might affect a project's time,
money, or success is considered a risk.

2. Analyze the risk

In order to determine where to focus first, your team will analyze the probability and
impact of each risk through this stage. You will next decide on an approach for dealing with
each risk. Accurate risk assessment depends on a number of factors, including the severity of
the impact, time wasted, and the possibility of financial loss to the company. By carefully
examining each risk, you may identify any problems that frequently arise during a project and
improve the risk management procedure moving forward.

3. Prioritize the risk

This stage reveals the project's overall perspective to you and indicates the areas on
which the team should concentrate its efforts. Most importantly, it will help you come up with
reasonable options for each threat. This prevents significant delays or interruptions to the risk
management workflow throughout the treatment phase.

4. Treat the risk

Effectively treating and mitigating the risk also means using your team's resources
efficiently without derailing the project in the meantime. As time goes on and you build a larger
database of past projects and their risk logs, you can anticipate possible risks for a more
proactive rather than reactive approach for more effective treatment.

5. Monitor the risk

Keep the risk register up to date; it should be an ongoing record that you and your team
frequently consult. Risks should be updated in the log so that everyone can observe them as
they change or develop. In this manner, everyone can remain in sync and react to risks more
quickly and pro-actively.

10
P3

The Purpose of Feasibility Study

During the project development life cycle, project feasibility study should be performed
after the business case has been finished. So, why is it important to handle a feasibility study?

An effective feasibility study is needed to points a project in correct way. It helps decision-
makers having a view of potential benefits, disadvantages, barriers and constraints that could
affect its outcome. The main purpose of a feasibility study is to determine whether the project
can be not only viable but also beneficial from a technical, financial, legal and market
standpoint.

Diagram 3.1

11
Purpose of Economic Feasibility

Even though you may be aware of the building costs, it's essential to be aware of its
maintenance costs. You should think about how long it will take for a project to break even
whether it will continue to generate income after it is finished through leasing or commercial
usage. Investors frequently ask for a feasibility study to evaluate a company's level of risk. This
frequently involves a cost-benefit analysis and could help in reducing wasteful spending.

Purpose of Schedule Feasibility 

Finding the probability that a project will be finished by its scheduled due date and
within the time frame specified limitations is what this technique is all about. A project's
schedule feasibility is rated well if there is a good chance it will be finished on time. If a project
takes longer than expected, it will likely fail in many circumstances because it may lose its
advantages, efficiency, and profitability due to changing external environmental factors.

Purpose of Technical feasibility

Technical feasibility determines whether you have the knowledge, skills, equipment, or
tools necessary to carry out the procedures, functions, or methods involved in a project. In this
way, it allows to know if a project is feasible (achievable) with existing technical resources or
expanding these if necessary. These technical or technological resources are those that serve as
support to others such as productive, commercial or financial. For example, a management and
accounting program.

12
Purpose of Operational Feasibility

The organization's ability to implement a certain solution is determined by its feasibility.

It serves as an indication for public opinion of the project or system.

• Is the system supported by management?

• How do the system's end users feel about their position in it?

• Which managers or end users are going to object to or refuse to utilize the system? Can this
issue be solved? How, if so?

• Testing for usability

• User satisfaction, ease of use, and ease of learning

P4

How technical solutions can be compared

Economic Feasibility Study

The Economic Feasibility Study (EFS) mainly consists of two things:

I. Business Case
II. Cost Benefit Analysis

A. Business Case

The Business Case offers the business environment analysis that are the descriptions of
proposed project’s expected customers, the main point of the business and how the proposed
system’s payment should be processed. It consists of the acceptances that was considered in
the economic feasibility analysis and the reasons of those acceptances. If a project is needed to

13
include electronic payment rather than cash payment, why cash payment would not be suitable
for the client’s project is needed to be explained in Business Case.

B. Cost Benefit Analysis

The Cost Benefit Analysis is a kind of process used in Business Organizations to measure the
intangible profits, costs and effects of implementing the proposed project. In more complex
ones, it may include what-if scenario analysis for different options. If the analysis results the
project is in more benefit than costs, the project is considered as the favorable project for the
company to continue working.

14
The table summarize the costs of the project -

The table summarize the benefits of the project -

Comparison of Costs and Benefits

15
Schedule Feasibility Study

In schedule feasibility study, the analyst has to consider about these 3 things.

A. How much time will need to hire the technical expertise or retrain the current
technician to be expert in the technology that is needed to apply in the proposed
system?

The organizations will be capable to implement the technology needed in proposed system, but
there may be the technicians who don’t have the skills required to apply that technology. So, it
will be required to hire new staffs or re-train the current systems staff. Even if there is no hiring,
training the staffs will also affect the project schedule.

B. Assessing the risk in scheduling

The analyst should consider that the project deadlines given to technical expertise are
reasonable or not. When there are specific deadlines, the analyst has to examine are they
mandatory or desirable? If the deadline is desirable, the analyst can present different
alternative schedules.

C. What will be the real constraints on project schedule?

If the project is overrunning there will be some consequences. Sometimes delivering a perfectly
functioning system two months late than deadline is bad but delivering an incomplete system
on time is worse.

Technical Feasibility Study

Technical Feasibility Study includes the analysis of proposed technology or solution. The
analyst has to examine that do the technology team possess the necessary technology and the
required technical expertise? Also, it analyzes what kinds of technology will use. If the required
technology is capable, the analyst finds out the capacity to handle the solution and if the
technology is not available, the analyst has to make report to acquire.

16
Operational Feasibility Study

The proposed system can be said operationally feasible if once it has been installed the
human resources are capable to make the system operate properly and the system is found out
that it is very easy to operate for end-users. So, it can be considered that the Operational
Feasibility Study is dependent on the human resources and their operating skills.

Operational Feasibility Study

17
M1

Hospital Management System

System Overview
Hospital Management System is a general-purpose solution for managing all hospital
operations and information flow. In the recent years, health care providers in hospitals spend
40% of their time in documenting medical records, appointment scheduling, billing process,
inventory records and other operational processes. By using HMS system, certain operational
processes such as patient registration management, scheduling appointments, maintaining
hospital staff information and inventory management can be digitalized and simplified.

Suitable SDLC Model for HMS system

Waterfall model is the best suitable software development methodology for the hospital
management system. The waterfall model is the old traditional SDLC methodology that is a
linear and sequential approach to project management. Although it has some limitations in
changing requirements and iterative way of developing the software system, there are some
reasons why it is the best suitable for HMS system.

Reasons why Waterfall Model is selected for HMS system

Strict documentation and clear requirements: In the matter of HMS, where it has many
complex functionalities, having clear and well-defined requirement specifications is important.
The Waterfall Model mainly focus on in-advance clear documentation and detailed requirement
gathering. So, it ensures that all requirements are documented and agreed upon before moving
on to the next phases, reducing the risk of scope creep.

Well-defined Phases and Goals: The Waterfall Model is a kind of methodology that approach
allowing for division of the project into clear phases like gathering requirements, architecture
design, implementation, testing and deployment. This enables project planning and goal
tracking, making it easier in managing the all-around development process and monitoring the
progress.

18
Limited iterative development and requirement changes: The Waterfall Model makes sure that
requirements are well-defined and remain fairly stable throughout the project or after software
deployment. In HMS system where there are numerous complex workflows and regulatory
constraints, constantly changing in requirements can be confusing and time-consuming during
the development process. By following sequential approach in waterfall model, it prevents the
need for frequent changes and iterations, which help maintain project progress time and
budgets.

Limited resources and budgets: Like mentioned above, the Waterfall Model is a sequential
approach to development process and needs precise planning making it easier to distribute
resources and plan the project scope and timeline. If the HMS system has a limited resources
and budgets, there is a need for defining the scope and project schedule. The Waterfall Model
can offer more predictable and control over the over-all project.

19
 Phases of Waterfall Model

M2

Components of a feasibility report

Executive Summary: This section provides an overview of the project and highlights the main
conclusions and advice from the feasibility study. It gives readers a high-level overview of the
report, enabling them immediately to understand the project's viability and its consequences
for making decisions.

Project Description: Give a thorough description of the project, including its objectives,
deliverables, scope, and expected outcomes. This section makes it clear what the project's
objectives are and what it comprises.

20
Approach: Specify the research techniques and strategies employed to carry out the feasibility
study. Describe the processes used to collect data, conduct analysis, and evaluate applicable
tools. This part guarantees clarity and helps readers in understanding the validity and
dependability of the study's results.

Market Analysis: Give a thorough study of the target market's size, potential for growth,
developments, customer segments, and competitive environment. Examine client demands,
market restrictions, and any other factors that could have an impact on the project's success.

Legal and Regulatory Considerations: Determine and evaluate the legal standards that the
project must meet. Examine any potential legal pitfalls, as well as any required permissions,
licenses, or certificates. Verify to make sure the project complies with all relevant rules and
regulations.

Risk Analysis: Determine and evaluate any possible project risks and uncertainties. Consider
elements including market risks, technological risks, financial risks, regulatory risks, and
operational risks while doing an extensive risk analysis. Create possible plans and risk reduction
methods to deal with these risks.

Environmental and Social Impact Assessment: Evaluate the project's possible impacts on the
social and environmental conditions. For example, identify any negative impacts on the
environment, local economies, general public health, and social well-being. Put forward
strategies for reducing any harmful effects.

21
D1

The merits of applying the Waterfall lifecycle model to a large

software development project
The Waterfall model is an old traditional software development methodology that works
in sequential manners. This methodology is best suitable for type of projects where
requirements are stable and well-defined. Large-scale projects such as Enomy Finance Project
may involve complicated requirements and constantly changing their regulations and demands.
However, there are some potential merits of applying Waterfall model to large scale projects.

As a first one, applying Waterfall Methodology benefits in clarity and structure. It is a

kind of software development methodology that follows a clear and structured development

22
approach. A system like Enomy Finance System which has complexity to manage during the
development needs to be structured the development process clearly. So, Waterfall Model can
provide that benefit.

Enomy Finance System needs strong documentation while it is being developed. It is a

type of large-scale project which has the complex functionalities, so it is better to be
documented in each stage and help developing the system more efficiently. Waterfall Model
mainly focus on documenting comprehensively at each stage. So, we should apply it to Economy
Finance System and get the good effect in proving beneficial for the organization’s future,
maintenance and meeting legal requirements.

There is always risk in developing any kind of software system whether it is a large-scale
or not. We need to reduce it as much as we can. In Waterfall Model, it works sequentially that
the model moves on the next phase only after completing the previous stage accurately. So, it
can help identify the potential risks early in the development process and reduce any kind of
risk after deploying the system to clients.

We clearly define the requirements and project-scope in Waterfall Model before starting
the development process. So, we can predict time scope and cost estimation of the project for
budgeting and resource planning effectively in Economy Finance System.

The Waterfall Model can be remarked as a systematical methodology. Project managers

and all the development team members record their project’s progress in each stage. So, they
can share their completion status and progress information between the teams to confirm to
move on to the next stages. Implementing the Waterfall can benefit in improving client
involvement essentially at the beginning and end of the project.

23
D2

Impact of different feasibility criteria

Feasibility Criteria play an important role in evaluating the viability and potential impacts
of an Economy Finance Project. There are some impacts of feasibility with different criteria in
Economy Finance System.

Financial Impact
This criterion measures the project's financial viability and ability to raise the funding
required for implementation. A project's financial stability is a sign of its probability to be
successful and self-sustaining, contribute favorably to the economy, and perhaps attract
investors.

Economic Impact
Analyzing the financial feasibility of a project determines whether its advantages exceed
its disadvantages and whether it is compatible with the nation's broad economic objectives and
policies. A project's favorable impact on economic growth, job creation, and resource efficiency
can be evaluated by a positive economic feasibility.

Technical Impact
The technical feasibility analyzes whether the project can be effectively implemented
given the current state of technology, infrastructure, and skills. A project's efficient completion
is ensured by positive technical feasibility, which may also encourage the use of new
technologies and raise productivity and competitiveness.

Operational Impact
Operational feasibility assesses how well the project can be integrated with current
procedures and workflows. Positive operational feasibility indicates the project can be
performed without experiencing major obstacles and inefficiencies, resulting in reduced
procedures and enhanced performance.

Schedule Impact
The project's ability to be finished within the time frame given is determined by the
schedule's feasibility. Positive timetable feasibility enables timely benefit delivery, which may
speed up investment returns and economic progress.
Resource Impact

24
 The project's access to the required resources, such as skilled developers, unprocessed
supplies, and money, is assessed using the concept of resource feasibility. Positive resource
feasibility can result in effective resource use, which might increase productivity and economic
growth.

25
References
https://www.kcw-et.com/news/importance-feasibility-study/#:~:text=Schedule%20feasibility
%20can%20determine%20if,chain%20and%20your%20financing%20options

https://www.cs.toronto.edu/~sme/CSC340F/2005/slides/07-feasibility.pdf

https://www.tpptechnology.com/en/blog/risk-management-in-software-development-how-to-
do-it-effectively/

https://www.virtasant.com/blog/sdlc-methodologies

https://www.manaraa.com/post/6068/What-is-the-use-of-feasibility-study

https://www.outsystems.com/case-studies/hospital-management-system/

https://www.bu.edu/sargent/files/2015/10/Orsmond-Cohn-Feasibility.pdf

26