Software development lifecycles

- A new computer system to support all employees of the

( Enomy - Finances) company

Introduction:
LO1 : Describe different software development lifecycles :

The Software Development Life Cycle (SDLC) is a diagram that depicts the
activities that must be completed at each stage of the software
development process. SDLC is a design philosophy pursued by a software
development team.

- It is a detailed strategy that specifies how to create, maintain, and replace

certain software. The life cycle describes a way for enhancing software
quality and the development process as a whole.

- The software development process is another name for the software

development life cycle.

Stages of Software Development Life Cycle (SDLC):

1- Requirement collection and Analysis:

The most critical step of the software development lifecycle is requirement collection and analysis.
The Business Analyst collects requirements from the Customer/Client in accordance with the client's
business needs and documents the requirements in the Business Requirement Specification
(document name changes based on the Organization). Customer Requirement Specification (CRS),
Business Specification (BS), and other similar documents are provided to the Development Team.

2- Analysis Phase:
Once the needs have been gathered and analyzed, the following stage is to define and record the
product requirements, which must be authorized by the client. This is accomplished through the use
of the SRS (Software Requirement Specification) document. SRS includes all of the product
requirements that must be planned and produced over the project's life cycle. The Project Manager,
Business Analyst, and Senior Team Members are key players in this phase. The Software
Requirement Specification is the result of this step.
3- Design Phase:
It consists of two steps:
HLD stands for High-Level Design, and it is completed by architects and senior developers.
Senior developers do LLD (Low-Level Design). It explains how each aspect of the product, as well as each
component, should function. Only the design will be displayed here, not the code.
This phase produces a High-Level Document and a Low-Level Document, which serve as input to the
following step.

4- Development Phase:
This phase involves developers of all levels (seniors, juniors, and freshers). This is the stage at
which we begin developing the program and creating the product's code. This phase produces the
Source Code Document (SCD) and the developed product.
5- Testing and Integration:
Once the program is complete, it is given to the testing department, where the testing team
extensively tests it for various flaws. They either manually test the program or use automated
testing tools, based on the procedures outlined in the STLC (program Testing Life Cycle), to
guarantee that every component of the product functions properly. After QA ensures that the
program is error-free, it moves on to the next stage, which is testing.
Implementation. This step yields the Quality Product and the Testing Artifacts. After the application
has been successfully tested, we must integrate the various modules such as login, signup, upload,
claim, and services.
6- Deployment and Maintenance Phase:
Following successful testing, the product is delivered/deployed to the client. The
Deployment/Implementation engineers are in charge of deployment. When clients begin utilizing the
established system, genuine problems will arise and must be addressed on a regular basis. The
maintenance phase includes resolving any concerns discovered by the customer. Because the
method testers test the product differs from the way customers use the product, 100% testing is not
achievable. Maintenance should be performed in accordance with the SLA (Service Level
Agreement).

P1 Describe two iterative and two sequential software lifecycle

models.

Iterative Models:
The iterative models are specific examples of a software development lifecycle that
emphasizes an early, basic implementation before progressively gaining complexity and a
wider feature set until the final system is finished. Improvements in this kind of model may
be seen immediately after being implemented throughout each cycle. The two iterative
models I'll discuss are the agile and prototype approaches.

dynamic model, Add sprint and scum, please. Client input, a standup meeting, the
backlog, and the sprint backlog. Please include the agile manifesto.

The Agile SDLC model combines iterative and incremental process models, with an
emphasis on process flexibility and customer satisfaction through the quick delivery of
functional software. The product is divided into smaller incremental builds using agile
methods. Iterations of these builds are supplied. (n.d, 2018) According to this paradigm,
each project is handled differently and current techniques are adjusted to better meet the
project's needs. For the purpose of providing certain features in the release, all jobs are
separated into manageable time spans. Working software and client interaction are
prioritized over thorough documentation and contract negotiations. A cross-functional team
collaborates on each iteration of the project under this paradigm, which also enables
proper responsiveness to change rather than just following the project plan.

The agile model is an iterative and team-based way to develop. This approach places a
high priority on the quick delivery of the system in fully operational components. Instead
of setting up tasks and timelines for system development, all time is time boxed in sprints.
Each sprint has a set time limit before it begins, however this might change depending on
the project and the ongoing list of deliverables. When scheduled work for a sprint cannot
be finished, it may be reprioritized again and the knowledge utilized to plan future sprints.
The team and clients analyze and assess the work once it has been finished. This
paradigm depends on substantial client participation throughout the development process,
but particularly during the system evaluation.

There are various phases in the agile model which are illustrated
below:
Requirements: Gathering the system requirements is the first stage in this model. A
meeting is held and all choices are put into action because this technique doesn't require extensive
paperwork to gather software requirements.

Design: The software design is being prepared at this stage with the aid of several software
designing tools. It can be ready as a demo version, and as the project progresses, more crucial
features can be added. Customers submit input to the system in this instance as well, and it is
modified to meet their demands.

Development: In this phase, the intended demo version is implemented for user feedback
and the system will virtually be finished. In this stage, customer participation and input are crucial.

Testing and feedback : This last stage involves finishing up the entire system and doing
all necessary testing. When the client is happy with the system that has been created, it is given to
the client.

Advantages : Disadvantages :
It is so easy, realistic approach that There will be highly individual
provides flexibility to developers. And dependency as minimum documentation
promotes teamwork and cross-training. is generated.
It provides continuous attention to As there are strict delivery management
technical excellence and good design. adjustments can be dictated to meet
 deadlines.
It provides continuous attention to It is very difficult to implement this
technical excellence and good design. model without an overall plan, an agile
leader, and an agile project manager.
It is best suitable for environments If the customer representative is not
where requirements may change during clear about the outcome of the project
the development process. then the team can easily get off track.
Resource requirements are minimum During the development transfer or
and only a little planning is required. recruiting of a new member in the
project will be quite challenging due to
lack of documentation.

Sequential models:

In this kind of approach, developers are required to complete the project in accordance
with a set of rules, regulations, and established orders. The waterfall model and the V
model are two sequential software development approaches that I will discuss in this
article.

Waterfall Model:

One of the oldest and most frequently employed software development approaches is the waterfall
model. This life cycle model is frequently referred to as the traditional approach to software
development. The software development process is described in this model as having a linear
sequential flow, meaning that each phase may only start after the one before it has finished. The
procedure for going back to the earlier phase to accommodate changes in requirements is not
specified by this development strategy.

The waterfall model includes a number of successive phases, as seen in

the above graphic, which are described below.

1. Requirement Gathering and analysis: A specification document is

created after collecting and analyzing all the system requirements
that need to be built. Here, the completed product's specifications are
noted and examined.
 2. System Design: After reviewing the required requirements acquired
in the first step, system design is created. Thus, a well-prepared
system design aids the developer in defining the hardware and
system requirements as well as the overall system's architecture.

3. Implementation: The system is built in small units that are compiled

in the following phase with input from the system design. Unit
testing is the process of functionally testing each developed unit.

4. Integration and testing: Following each unit test, the units created in
the preceding phase are integrated into the system. To ensure that the
client does not experience a problem when installing and afterwards
using the software, the complete system is checked for any flaws and
failures.

5. System deployment: Following the conclusion of both functional and

non-functional testing, the product is deployed in the client
environment or released to the market as needed.

6. Maintenance: Client environment problems can arise even after the

system has been deployed, so patches are supplied to address these
problems. In the maintenance phase, new versions are published to
further improve the product. Until the software is destroyed, this step
is completed.
Advantages : Disadvantages :
Because the waterfall model is a highly Only when extremely specific upfront
straightforward and user-friendly criteria are given may this strategy be
process, it is especially helpful for new employed.
or inexperienced developers.
Because of the rigidity of the model, it is This model cannot be used for
 simple to manage. In addition, each maintenance-related work.
phase has a unique review procedure
and deliverables.
This model processes and completes The biggest disadvantage of this
stages all at once, which significantly approach is that it is impossible to go
reduces processing time. back and make changes to an
application after it has entered the
testing phase.
This kind of development strategy Up until the cycle's conclusion, there is
performs better on smaller projects with no chance of producing any functional
clearly defined needs. software.
---- This approach does not offer a way to
determine the project's final outcome.
This kind of development strategy This paradigm works well for little tasks
performs better on smaller projects with but is less suited for continuous, lengthy
clearly defined needs. initiatives. Not the best choice for
projects with few criteria and lots of
room for adjustment

Application of Waterfall Model :

The first paradigm of software development, it can only be used when the requirements are crystal
clear, well-defined, and fixed. It cannot be used if the user requirements are not properly
documented. When the product description is fixed and technology is known, this approach can also
be applied. Developers should only go to the next phase after properly evaluating and assessing
each stage, and after properly documenting user requirements. It also applies in cases when there
is no likelihood of consumer involvement in the project and contract negotiations serve as the sole
means of accomplishing the goal. This paradigm may be used to tasks that have clear criteria. The
waterfall paradigm is also appropriate for projects that move from one platform to another, when all
requirements remain the same and just the system environment or programming language changes.
Small tasks are more appropriate for this than time-consuming, complex large projects.
 Done P1

P2 Explain how risk is managed in software lifecycle

.models

Risks in Software Development Life Cycle :

Risk is a prospective issue that might arise in the future but is not guaranteed to do so. Generally
speaking, it is brought on by a lack of knowledge, control, or time. A software risk is the potential for
financial loss throughout the software development process. Loss can take many different forms,
including a rise in manufacturing costs, the creation of subpar software, or failing to finish the
project on schedule. Wilson (2011). These risks exist for our project or emerging system since the
future is unpredictable and there are several facts that are currently known and unknown that we
cannot account for in the project plan. Risks during system development might be of two categories.
First, there are internal risks that the project manager has control over, and second, there are
external hazards that the project manager has no control over.

Explain the Spiral lifecycle model's approach to risk

management.
Boehm presented the spiral model as a risk-driven software development process model in 1988,
with the development process being influenced by the risks involved. The goal of this approach is to
recognize, assess, and assist mitigate the risks associated with software projects. Despite being
risk-driven, this model's principal sources of risk are due to a heavy dependence on human factors
and a thorough risk management procedure. Boehm claims that this model spends roughly 25% of
its time on risk analysis, which is primarily used to identify project risks. It not only gives projects
flexibility, but it also informs us of impending threats.

The following list of ways that spiral development supports risk

management in software projects is an overview of those ways:
 The first risk analysis, which serves as a look-ahead stage, strives to:
▫ Identify the risks that pose the greatest danger to the project.
▫ Subdividing hazards into development risks and user interface risks
▫ *Assess these risks to determine which ones should be managed during each cycle.
Additionally, this categorization aids programmers in using risk-reduction strategies like
benchmarking and prototyping.
 the spirals of evolutionary prototyping intended to address performance- and user-interface-
related issues. Before beginning the development process, these spirals aid in lowering
significant risks.
  Each cycle's risk analysis stage, which comes before each waterfall phase, serves the
following purposes:
▫ * Resolving program development and interface control risks that were present from the
beginning of the project;
▫ * Evaluating and resolving any new risks that might develop as a result of altering any of the
objectives, alternatives, or constraints at the cycle's start.
 The spiral's iterative structure enables the development process to return to the first quadrant
at any time, allowing for the following flexibility:
▫ Objectives, alternatives, and constraints can be changed as more desirable alternatives
emerge;
▫ New technology can be easily incorporated during the development process.
▫ The most effective use of project resources;
▫ The resolution of badly executed tasks from earlier phases.
 The evaluation undertaken with key stakeholders at the conclusion of each cycle serves as a
decision-making point to reduce the risk of lack of commitment throughout the following
cycle.
Due to the risk analysis step that is carried out at each cycle, spiral development is the best 
method for managing time and expense overrun concerns. To present a clear image of the
project's crucial status, the cost and time needed for each cycle are examined in advance
.during this stage

By doing this, the project manager and the developers are better able to handle these risks.
 Spiral is also used to control risks associated with the project's growing complexity.
This is accomplished by the partitioning exercise carried out during the planning phase.
▫ Since more work might be completed in the same amount of time, breaking the project into
sections that will be developed in parallel spirals definitely minimizes time contention-related
hazards.
Significant Risk Sources in the Spiral Model Although spiral is risk-driven, the sources of
dangers it faces may be summed up as follows:
 Significant dependence on the human element.
▫ Developers' experience and their capacity for detecting and managing risks are relied upon in
all actions connected to identifying, assessing, and resolving hazards. Major dangers may go
unnoticed for multiple lifecycles and only be found after they have developed into actual
issues if these skills are not present. At that point, the cost of redoing the work to mitigate
these risks skyrockets.
 A thorough risk management procedure.
▫ Due to its iterative nature, spiral may raise cost and schedule concerns, especially for low-
risk projects where this degree of depth in risk assessment is not necessary.

DONE P2

M1 Discuss using an example, why a particular lifecycle

model is selected for a development environment.

 Copy from above

 Adaptive model
 Client’s continuous feedback
 Iterative model
 Continuous testing
 Less documentation
  Manifesto of Agile
 Daily Standup meeting, Sprint board.

Agile :

Selecting the right Software Development Life Cycle (SDLC) methodology is undoubtedly a difficult
issue for all businesses and project managers. Each model has limitations, therefore we must select
the most appropriate one depending on the requirements of the situation. Each project manager has
to be aware of their technical capabilities, technological limitations, scenario requirements and
features, and the advantages and disadvantages of the project model they have chosen. We may
utilize several models in relation to various scenarios and criteria, such as the RAD model for quick
and rapid software development, the waterfall model based on requirements, the spiral model based
on risk and risk mitigation, and so on. In the hypothetical situation, I was tasked with developing an
application with a variety of features for a big insurance firm. Initially, it was quite difficult for me to
select the ideal model since each one has advantages and disadvantages. However, after carefully
examining the scenario and client requirements, I decided that the agile model was the best option.

Definition :

The Agile SDLC model combines iterative and incremental process models with an emphasis on
customer satisfaction and process adaptation through quick delivery of functional software. The
product is divided into smaller incremental builds using agile methods. Iterations of these builds are
supplied. (n.d, 2018) According to this concept, each project is managed uniquely and current
techniques are adjusted to better meet the project's needs. For the delivery of certain features in
releases, all jobs are separated into brief time spans. Working software and customer participation
are prioritized above thorough documentation and contract negotiations. The project plan cannot be
followed well with this paradigm, and cross-functional teams must collaborate during each iteration.
Each of the iteration need cross functional team which works simultaneously on areas like: -
 Planning
 Requirement Analysis
 Design
 Coding
 Unit testing
 Acceptance testing
Justification for Selection:
.

As stated in the scenario I was provided, I was recruited to create an application for an insurance
firm that would include a variety of capabilities, like storing all customer information, notifying clients
of significant updates, and others

When necessary, firm members will provide documents and provide guidance and counseling,
among other things. I chose the agile paradigm for software development in light of these
requirements. There are a number of reasons to select this model over others like RAD, Spiral,
Waterfall, Prototype, and so on. There was no need for in-depth planning because company
management made it clear to me the features they desired in the application. Since our
development team was based in the same area as us and we frequently worked from offices, it was
simple for me to keep an eye on things. This strategy allows for speedier software development
because we were likewise constrained by the company's time constraints. We were able to collect
input from actual consumers using the agile concept. Since there was never a chance that we
would spend all of our time creating an application that the customer didn't want, this approach
allowed the administration to provide feedback on our work and keep us on course. This approach
gives us the option of incremental delivery, which enabled us to create software according to the
client's specifications. In order to provide the firm the chance to examine the developing product
and respond to it, we could offer information on the project whenever they requested it. Thus, this
model could aid in our and the client's convergence on the optimal result. The early risk reduction
provided another justification for selecting the agile methodology. By giving software to the
organization early and receiving input, we could lower the chance of developing the incorrect
software. We might lower the danger of creating the incorrect software before providing the finished
product to the client by continually integrating and producing bug-free software. In addition to
providing us with the instruments for altering commercial and technical scope, this model assisted
us in fixing cost, time, and quality. We were certain that we met their needs as we created our
program and finally delivered it to the organization. Agile also helped us provide higher-quality
products in this way. In addition to these factors, another justification for choosing the agile
approach was its guiding philosophy, which emphasizes customer satisfaction with the product we
produce. By regularly upgrading the software and introducing new features based on consumer
input, this methodology will enable us to improve relationships with our customers. We would benefit
in many ways from building stronger relationships with the administration of such a large
corporation. Gaining their trust and satisfying them might help us secure future projects from them
in the competitive environment of today. The last justification for picking this paradigm was that it is
popular in the current software development environment. Because of its qualities that are
applicable to all circumstances, this model is being used by the majority of businesses.
 DONE M1

D1 Assess the merits of applying the Waterfall lifecycle model to a

large software development project.

waterfall model:
Popular in software engineering and product development, the waterfall model is a linear, sequential
approach to the software development lifecycle (SDLC).
The waterfall approach applies a logical sequence of SDLC processes to a project in a manner akin
to how water cascades from a cliff. For each stage of development, it establishes clear endpoints or
objectives. Once certain endpoints or objectives have been achieved, they cannot be revisited.
In a report on his experience writing software for satellites that was published in 1970, Dr. Winston
W. Royce of the Lockheed Software Technology Center suggested the idea. Although Royce used
the phrase "waterfall," he actually meant "the downstream value of documentation.
" In applications related to industrial design, the waterfall approach is still employed. It is generally
referred to be the original software development technique. For complex, diverse projects, the
model is often employed more broadly as a high-level project management technique.
Who uses the waterfall model?

The waterfall model is used by project teams and project managers to accomplish tasks according
to business requirements. The paradigm is utilized across a wide range of project management
domains, including manufacturing, IT, software development, and construction.
Each phase of the waterfall approach is reliant on the results of the one before it. The development
of these initiatives follows a linear pattern.
For instance, these three standard processes are often followed in construction:
1. A building's physical design is created before any construction begins.
2. The foundation is poured before the skeleton of a building is erected.
3. The skeleton of the building is completed before the walls are built.

On a production line, processes are carried out progressively in a predetermined order while
creating a product until the final delivery is produced.

Unlike other development approaches, the waterfall model does not incorporate a project's customer
or end user as much. When gathering and establishing requirements in the beginning, users are
contacted; after that, client input is taken into account. The waterfall technique speeds up project
development since it excludes the customer from the majority of its steps.

This technique works well for teams and projects who wish to construct a project in accordance with
established, initial criteria that don't change. Waterfall programs have low to no output variability and
a high degree of process clarity. If the project is limited by money or time, waterfall is another
excellent option.

The waterfall paradigm produces projects that are well defined, predictable, and with detailed
documentation. They also exhibit the following traits:
 fixed requirements;
 ample resources;
 an established timeline;
 well-understood technology; and
 unlikely to require significant changes.

Waterfall is a good software development process because it sets out to accomplish that goal,
which is important if an application must function correctly on the first try or risk losing clients. As an
alternative, consider the project management and development technique of Agile. Continuous
iteration, a strategy used by agile methodologies, entails designing, creating, and testing software in
successive cycles that build on one another.
 : Phases of the waterfall model

When used for a software development process, the waterfall methodology has seven stages:

1- Requirements. Potential requirements, deadlines and guidelines for the project are analyzed
and placed into a formal requirements document, also called a functional specification. This
stage of development defines and plans the project without mentioning specific processes.

2- Analysis. The system specifications are analyzed to generate product models and business
logic to guide production. This is also when financial and technical resources are audited for
feasibility.

3- Design. A design specification document is created to outline technical design requirements,

such as the programming language, hardware, data sources, architecture and services.

4- Coding and implementation. The source code is developed using the models, logic and
requirement specifications designated in the prior phases. Typically, the system is coded in
smaller components, or units, before being put together.
5- Testing. This is when quality assurance, unit, system and beta tests identify issues that must
be resolved. This may cause a forced repeat of the coding stage for debugging. If the system
passes integration and testing, the waterfall continues forward.

6- Operation and deployment. The product or application is deemed fully functional and is
deployed to a live environment.
 7- Maintenance. Corrective, adaptive and perfective maintenance is carried out indefinitely to
improve, update and enhance the product and its functionality. This could include releasing
patch updates and new versions.

In the waterfall process, there is often a review and sign off to make sure all established goals have
been completed before going on to the next step. Before going on to the testing phase, for instance,
developers would make sure each piece of technology was correctly integrated during installation.
Advantages of the waterfall model :
The waterfall paradigm is now frequently replaced with agile methods. The waterfall method does
have several benefits, including the following:
 allows for the advancement of large or dynamic teams toward a predetermined common
objective;
 forces structured, disciplined organization;
 simplifies task comprehension, execution, and organization
  facilitates departmentalization and managerial control based on the schedule or deadlines;
 strengthens the practice of defining before implementing a design and then writing code;
 allows for simple early system design and specification adjustments;
 Clearly states deadlines and milestones.

Disadvantages of the waterfall model

The danger associated with a lack of revision and flexibility is usually at the heart of the waterfall
model's drawbacks. The following are specific issues:
1. Design isn't adaptive; when a flaw is found, the entire process often needs to start over.
2. Method doesn't incorporate midprocess user or client feedback, and makes changes based
on results.
3. Waterfall model delays testing until the end of the development lifecycle.
4. It doesn't consider error correction.
5. The methodology doesn't handle requests for changes, scope adjustments and updates well.
6. Waterfall doesn't let processes overlap for simultaneous work on different phases, reducing
overall efficiency.
7. No working product is available until the later stages of the project lifecycle.
8. Waterfall isn't ideal for complex, high-risk ongoing projects.

Waterfall model software and tools :

For waterfall projects, Gantt charts are a typical management tool. Project managers may easily
connect dependencies and subtasks to each step of the process using these charts, which make it
simple to see successive phases. They give a clear picture of the schedules and due dates for each
stage.
Some project management software products that feature Gantt
charts include the following:
 Asana,
 Jira,
 Microsoft Excel,
 Microsoft Project,
 Microsoft SharePoint,
 ProjectManager,
 Smartsheet and
 Wrike.
Other features are frequently included in project management
software to aid waterfall-based teams in completing their work.
The following are some crucial features that project management
software should have:
teamwork, taking notes, developing and testing, as well as data
analytics and visualization.
 Done D1

LO2 Explain the importance of a feasibility study.

P3 Explain the purpose of a feasibility report.

Introduction:
"A feasibility study is an examination performed to gauge a project's potential and chances of
success while taking into account all pertinent aspects. It must take into consideration all relevant
variables, including those affecting the economy, technology, law, and schedule. Specific business
situations may be investigated in-depth by using the feasibility study to "frame" and "flesh-out" them.
Before devoting a significant amount of time and money to a project, project managers conduct
feasibility studies to ascertain its possible positive and negative repercussions. Posted by Don
Hofstrand in October 2009. It evaluates if an idea, a project, or even a new business is viable.
Before the project's actual work begins, a preliminary research is conducted to determine the
project's chances of success.The main goal of a feasibility study is to highlight potential issues that
might arise from pursuing a project and to decide if the project is a good idea after taking into
account all important considerations. For instance, if we want to create a web application for our
company, we may do a feasibility study to decide if it should be implemented, taking into account
the time and money required, the views of relevant parties, and any potential legal ramifications.

A feasibility study is a piece of writing that evaluates prospective solutions to company problems or
opportunities and decides which ones are viable enough to move on with further investigation. Its
primary advantages include aiding in the presentation of the project's characteristics and the
identification of viable solutions to the identified issue, need, or opportunity. The study analyzes
many potential solutions to a problem and makes recommendations for the best one to implement.
It also includes thorough data on the financial and operational effect, as well as benefits and
drawbacks of both the present state and the suggested plan. The report created after the feasibility
study is completed lists and evaluates a number of alternatives or strategies for the project's
success. It is beneficial to reduce the project's scope in order to choose the optimal course of
action. Every project must undergo a feasibility study throughout the planning stage, and after the
report is created, it may be used to determine if the project is worthwhile or not. It boosts our self-
confidence and can occasionally be expensive, but it is preferable to know up front if a project will
be successful or not by doing a feasibility study. Companies may decide and arrange all the
elements needed to make company operations successful using a feasibility study. It assists in
identifying logistical and commercial issues as well as potential fixes. It may also result in the
formulation of numerous tactics for allocating our resources—both time and money—to the most
appropriate projects.

Purpose of Feasibility Study:

Please list them in bullet points.
The importance of a feasibility study is predicated on an organization's need to "get it right" before
allocating time, money, and resources to a project. It could produce fresh insights that totally alter
the direction of a project. Making such decisions beforehand is usually preferable to diving right into
a project that won't succeed. The results of the feasibility study always help us and our stakeholders
understand the proposed project. The feasibility study is the second document produced after the
business case while working on a project or developing software, and it aids in the identification of
the elements necessary for the business opportunity given in the project to succeed.

A feasibility report may also be used to investigate potential markets for a target audience. For
instance, doing a feasibility study will assist us determine where we can install the online payment
system. It gives us direction on where to launch our system in areas with a large audience, such
major cities. To determine if our new product will be able to enter the market, we can examine our
current rivals. If our feasibility analysis shows that our business lacks the means to compete, we
can concentrate on developing other items. In this instance, a feasibility assessment keeps us from
making an expensive error that would cripple our idea before it could gain traction. If the feasibility
analysis indicates that the project is likely to fail, we can conserve our resources—both money and
time—for a future opportunity rather than squandering them on ventures with no prospect of
success. A feasibility study's goal is to give a broad picture of the key concerns surrounding a
potential business venture.

Recommendation :
This is how conducting a feasibility study always aids us in completing the project. The fundamental
goal of a feasibility report is to determine if a project is worthwhile. If the report's findings are
unfavorable, we have one more chance to get things right before devoting time and resources to it.
It gives us information on the different project hazards so that we may first reduce them before they
become major issues. Not only does it advise us to discard our project ideas, but it also lists the
reasons why we should abort the project so that we will be aware of them in the future. It assisted
our team in making decisions on the expansion of current services, construction of new facilities,
technique changes, the addition of new goods, etc. when developing insurance business software. I
also advise people to undertake a feasibility study before beginning their projects because it helped
us comprehend our idea when working on it for an insurance firm.

DONE P3

P4 Describe how technical solutions can be compared.

In order to fulfill user needs in the system within the allotted time and money, technical solutions
evaluate the present resources, such as efficiency, performance, legacy systems, and technology.
The implementation of the technological solution in the project can happen either before the project
is begun or after it has been started, similar to the feasibility study of the project. Because a
technical solution is a solution with a good decision that may make the business or project lucrative,
it can be compared to a feasibility study, which is performed to make better decisions. Based on
factors such the abolition of human error, performance, budget, legacy system, performance,
efficiency, etc., we can compare the technological solutions. During the course of a project,
technical solutions consist of designing and putting into practice fixes for any difficulties with
equipment, finances, etc.
I'll demonstrate the technical solution for landlines and mobile phones and compare it to the primary
drives below:
 Performance and efficiency
 Legacy systems upgrade
 Automation
 Elimination of human errors
 Budget/ economic .

Performance and efficiency:

Landline phones are not mobile, and customers can only use them in a single location where there
is a wired connection to the telephone network. Cell phones, on the other hand, are mobile, which
means portable and can be taken from one place to another, and they are functional anywhere the
user can get a signal from a wireless network. When you're away from home and an emergency
occurs, a cell phone may be quite helpful. Modern technology and capacity are found in cell
phones. Landline telephones cannot be used to shoot live photos or movies, but cell phones can. In
terms of style and comfort, cell phones surpass landlines.
Legacy system upgrade :

You will immediately notice a decrease in service fees and call prices, which is one of the most
noticeable advantages. Employees still have access to essential communication tools like phones,
messaging, video conferencing, etc., which aids with company continuity. It also makes it possible
to upgrade your lines with extra capabilities for simpler conferencing and communication.

Legacy system upgrade :

Your ability to immediately reduce service fees and call expenses is one of the most noticeable
advantages. Employees still have access to essential communication tools like phones, sending and
receiving messages, video-clip conversations, etc., which aids with company continuity. Additionally,
it enables you to add features to your lines for simpler conference calls and communication.
Automation :

The both system typically play a message, then ask the caller to either press a button or speak a
response. Depending on the caller’s input the automated phone system may play some information,
route the caller to another prompt or connect the caller with a human operator.
Elimination of human errors :

Human mistake results from an imbalance between what is required by the circumstance, how the
individual interacts, and what the person really accomplishes. It occurs when people intend to act
morally uprightly but end up doing the opposite.

GPS technology on smartphones can pinpoint your precise location or the direction you're trying to
travel.

Budget / economic :

The fact that both landlines and mobile phones are utilized for communication is what makes them comparable. The
cost of a mobile phone plan is often less expensive than a landline plan in most places, especially when long distance
calling plans are taken into account. This is the most popular justification for using a cell phone. Today, we see a lot of
individuals walking around with their mobile phones since they know it's quicker and less expensive.
 DONE P4

M2 Discuss the components of a feasibility report.

Components of Feasibility Report:

A feasibility study evaluates prospective business issue or opportunity solutions and concludes
which of them are viable for future investigation. The key advantages it offers are that it aids in
outlining the project criteria and alternative solutions to the specified issue, need, or opportunity.
After conducting the feasibility study, a report was produced that defines and evaluates several
options or strategies for realizing the project's goals. It is beneficial to reduce the project's scope in
order to choose the optimal course of action. Before the project's actual work begins, a preliminary
research is conducted to determine the project's chances of success. The study analyzes several
solutions to an issue and makes recommendations for the best one to implement. It also includes
thorough data on the financial and operational effect, as well as benefits and drawbacks of both the
existing state and the suggested plan. Every project must undergo a feasibility study throughout the
planning stage, and after the report is created, it may be used to determine if the project is
worthwhile or not.

Perceived objectives are significant aspects in the credibility of the research for possible funders or
other clients since a feasibility study examines the likelihood of project success. There are several
parameters that we must consider when doing the feasibility study.
Below I have described those components of feasibility study:
 1. Introduction .

The planned name and objective of the business, as well as any background information about the
prospective business or project, will be detailed. The knowledge and expertise of the company
investors are also included. When considering whether to do a feasibility study, we had to decide
whether the proposed idea was technically possible, economically viable, and financially successful.
The overall summary of the report we are going to publish must be included in the feasibility study's
introductory section. I conducted a feasibility study for an insurance firm, and as part of the report, we
had to provide background information on the business, including its characteristics and the nations in
which it operates.

2. Business or Project Description.

This section discusses information on the company or project as well as the industry or nature of the
endeavor. We must describe the project's broad scope in this section, as well as how we plan to
conduct a feasibility study for a specific project.

3. Purpose .

It is the key part of a feasibility study, and the researcher must first grasp why it is necessary in order
to get the desired results. The major goal of the feasibility study might be predicated on the
organizational desire to "get it right" before any organization invests resources, cash, and time in a
project. A feasibility study may reveal fresh concepts that might entirely alter the direction of a project.

4. Methodologies
The right technique to undertake or conduct a feasibility study is provided by methodologies. It aids in
choosing the best strategy for gathering data, organizing data, and carrying out the project. We must
use a variety of techniques to gather information and facts about the project in order to conduct a
feasibility study. The many approaches for a feasibility study might include surveys, questionnaires,
interviews, and in-person meetings. We may learn more about the project's scope in a specific place
and for a specific audience by interacting with individuals.

5. Background History

The feasibility study's background history is also regarded as a component. Any project will go more
successfully if its history is gathered. These elements of a feasibility study outline the project's history
and why a feasibility study was necessary for this particular project

6. Intended Audience

These elements pertain to the users of the program once it has been produced. To determine
whether the audience requires this kind of software, we must first do a feasibility study on them. The
success rate of a software launch will be high if the created software makes the work easier for the
target audience.

7. Feasibility Criteria

The principles on which we must build our feasibility research are known as the feasibility criteria.
Technical, social, legal, operational, economic, and timetable considerations are among the
requirements for viability. We need to do research based on those criteria when we complete the
feasibility study in the targeted audience. For instance, in terms of scheduling criteria, we must
determine whether the proposed project will be finished on time or not, and in terms of economic
criteria, we must determine whether the money allotted will be sufficient to complete the program.

8. Outcome

This part is also known as the feasibility study's ultimate outcome. The published report has to be
examined once we do the feasibility study among the intended audience. We can eventually
determine if the project should be begun or not once the system analyst has examined the report.
These elements provide us the feasibility outcome, and after assessing it, we can determine whether
to move on with the project or not.

9. Conclusion and Recommendation

The system analyst and other project stakeholders must communicate with one another and reach a
decision when the feasibility study's findings are published. These elements provide other people an
idea of the project and feasibility study. After the report's conclusion has been reached, we must also
suggest it to other initiatives. We must suggest it to project managers so that we can have another
opportunity to get it right before beginning any project.

10. Evaluation Criteria

11. Review.
We must keep in mind that a feasibility study is more of a style of thinking than it is a formal
procedure. For instance, the procedure I just described is much the same as the one we all follow
when purchasing a car or a home. The feasibility assessment must be documented as the project's
scope expands, especially if significant financial investment is required and/or timely delivery is
critical.
In addition to providing enough information to move on with the project's next phase, the feasibility
study should also be utilized to compare what has been delivered to what was originally requested
when a final project assessment is being prepared.

Studies of feasibility constitute a broad method of planning. To put it simply, it's an excellent task to
implement. I have heard that certain IT professionals, such as those who support the "agile"
technique, believe that feasibility studies are a major waste of time. I must have an excellent used
automobile I wish to sell if that is the case.

DONE M2

1. Feasibility study introduction: A feasibility study evaluates potential solutions to

a problem and suggests the best course of action. It can determine whether to carry out a process.
by a new system that works more effectively than the current one. Three key areas should be looked
at in the feasibility study: market difficulties, organizational and technological needs, and a financial
overview. The study's findings are taken into consideration while deciding whether to move on with
the project or put it on hold. If it does result in a project being authorized, it will be used to determine
the likelihood of the project's success before the actual work on it begins.

2. Different kinds of software inquiry feasibility studies:- A thorough

preliminary examination of all the systems involved was included in the feasibility study.
Therefore, research needs to be done in a fashion that considers the proposed system's operational,
economic, technological, and planning viability.The four primary categories of feasibility studies are as
follows.
2.1. Technical : The technical element investigates whether the project is technically feasible
given the restrictions of time, money, and other resources (i.e., budget, schedule). The system
analyst considers the technological viability in relation to the organizational needs, such as
+ Input device that can enter a lot of data quickly.
+ The type of processing needed by the organization will determine the processing unit to use.
2.2 Operational : This factor establishes the problem's urgency and the acceptance of any
potential solutions. It demonstrates if the system will be used if it is created. People-focused and
social concerns are covered by the operational study, covering internal issues like staffing shortages,
labor complaints, management resistance, organizational disputes, and policies, as well as exterior
ones like social acceptance, legal considerations, and governmental restrictions. It considers social
issues of how organizational changes would impact the working lives of individuals touched by the
system as well as if the present work practices and procedures support a new system.
.