Assignment on Software Development Life Cycle

This document is divided into three parts, first describes the different software development life cycles, which will consist of small tasks that need to be completed such as describing two iterative and two sequential software life cycle models. The second explains how to manage risks in the Spiral lifecycle model. The third is to describe, with an example, why a specific lifecycle model was chosen for the development environment and Evaluate the value of applying the Waterfall lifecycle model to a large software development project.

ASSIGNMENT 1 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing
Unit number and title Unit 9: Software Development Life Cycle
Submission date Wednesday, February 2022 Date Received 1st submission
Re-submission Date Date Received 2nd submission
Student Name Lai The Hung Student ID BHBF200052
Class PBIT 17102 Assessor name Ngo Thi Mai Loan
Student declaration
I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that
making a false declaration is a form of malpractice.
Student’s signature
Grading grid
P1 P2 P3 P4 M1 M2 D1 D2

 Summative Feedback:  Resubmission Feedback:
Grade: Assessor Signature: Date:

Signature & Date:
Table of Contents
INTRODUCTION..............................................................................7
P1 Describe two iterative and two sequential software lifecycle models............................7
1. Original Waterfall Model...............................................................................................................8
1.1. What is the waterfall model?..................................................................................................8
1.2. Different Phases of Waterfall Model in Software Engineering................................................9
1.3. When to use SDLC Waterfall Model?......................................................................................9
1.4. Advantages and Disadvantages of waterfall model..............................................................10
2. Prototyping Model.......................................................................................................................10
2.1. What is the prototyping model?...........................................................................................10
2.2. Prototyping Model Phases....................................................................................................11
2.3. When to use SDLC Prototyping Model?................................................................................11
2.4. Advantages and disadvantages of prototyping mode...........................................................12
3. Spiral model.................................................................................................................................13
3.1. What is spiral model?...........................................................................................................13

3.2. Spiral Model Phases..............................................................................................................13
3.3. When to use Spiral Model?...................................................................................................14
3.4. Advantages and disadvantages of spiral model....................................................................14
4. Agile Model..................................................................................................................................15
4.1. What is Agile Model?............................................................................................................15
4.2. Phases of Agile Model...........................................................................................................15
4.3. When to use Agile model:.....................................................................................................16
4.4. Advantages and disadvantages of Agile model.....................................................................16
5. Which method is best for tune source and why?........................................................................17
P2 Explain how risk is managed in the Spiral lifecycle model............................................17
1. Introduction of Risk.....................................................................................................................17
2. Inportance of risk management...................................................................................................17
3. Risk management Process...........................................................................................................18
4. How to manage risk in the Spiral lifecycle model........................................................................18
4.1. Introduction of Spiral lifecycle model...................................................................................18
4.2. Phases of Spiral model..........................................................................................................18
4.3. How to manage risk..............................................................................................................19
P3 Explain the purpose of a feasibility report...................................................................21
1. What is a feasibility report?.........................................................................................................21
2. Purpose of each element in a Basic Feasibility Report.................................................................21
2.1. Introduction of Basic Feasibility Report................................................................................21
2.2. Purpose of four elements.....................................................................................................22

P4 Describe how technical solutions can be compared.....................................................23
1. Introduction of a feasibility study................................................................................................23
2. Technical Feasibility.....................................................................................................................23
2.1. What is Technical Feasibility ?..............................................................................................23
2.2. Can we build it ?...................................................................................................................23
3. Economic Feasibility....................................................................................................................24
3.1. What is Economic Feasibility ?..............................................................................................24
3.2. Should we build it?...............................................................................................................24
4. Organizational Feasibility.............................................................................................................24
4.1. What is Organization Feasibility............................................................................................24
4.2. If we build it, will they come ?..............................................................................................24
5. Discuss whether the project is feasible........................................................................................25
5.1. Analyzing Costs vs. Benefits..................................................................................................25
5.2. Calculating Present Value.....................................................................................................25
5.3. Net Present Value.................................................................................................................26
6. Alternative technical solutions using the alternative matrix........................................................27
6.1. Javascript..............................................................................................................................27
6.2. .Net.......................................................................................................................................27
6.3. Html......................................................................................................................................28
6.4. Css.........................................................................................................................................28
6.5. A summary weighted score table.........................................................................................28

➢ CONCLUSION...............................................................44➢ REFERENCES.................................................................45
INTRODUCTION
In this assignment, I will complete the tasks. The first major task describes the different software development life cycles,
which will consist of small tasks that need to be completed such as describing two iterative and two sequential software life
cycle models. The second explains how to manage risks in the Spiral lifecycle model. The third is to describe, with an
example, why a specific lifecycle model was chosen for the development environment and Evaluate the value of applying
the Waterfall lifecycle model to a large software development project. Next is to explain the importance of the feasibility
study.
Including sections such as: Explaining the purpose of the feasibility report, describing how to compare technical solutions,
discussing the feasibility report components, and assessing the impact of the feasibility criteria for a software survey.
P1 Describe two iterative and two sequential software lifecycle models
 INTRODUCTION OF SOFTWARE DEVELOPMENT LIFE CYCLES
- The software development life cycle is the application of standard business practices to building software applications. It
is usually broken down into six to eight steps: Plan, Require, Design, Build, Document, Test, Implement, Maintain. Some
project managers will combine, break down, or skip steps, depending on the scope of the project. These are the core
ingredients recommended for all software development projects.
- Software Development Life Cycle is a way to measure and improve development. It allows detailed analysis of each step of
the progress. This will help companies maximize efficiency at each stage. Like computing power increased, it places higher
demands on software and developers. Companies must reduce costs, deliver software faster and meet or exceed customer

needs. Software Development Life Cycle helps achieve these goals by identify inefficiencies and higher costs and fix them for
smooth operation.
ite et al(S ., 2021)
Figure oft are e elo ent ife C le
1 S w D v pm L yc
- A number of well-established software development models like Waterfall, Prototype, Spiral, Agile.

1. Original Waterfall Model
1.1 What is the waterfall model?
aterfall ModelW is a se uential odel t at di ides soft are de elo ent into re defined ases a ase ust beq m h v w v pm p - ph . E ch ph m
o leted before t e ne t ase an begin it no o erla bet een t e ases a ase is designed for erfor ingc mp h x ph c w h v p w h ph . E ch ph p m
s e ifi a ti it during t e C ase t as introdu ed in b instonp c c c v y h SDL ph . I w c 1970 y W o eR yc .
at is aterfall Model in C d antages and isad antages(Wh W SDL ? A v D v , 2021)
Figure riginal aterfall Model
2 O W

1.2 Different Phases of Waterfall Model in Software Engineering
Different phases Activities performed in each stage
Requirement Gathering
stage
 During this phase, detailed requirements of the software
system to be developed are gathered from client
Design Stage
 Plan the programming language, for Example Java, PHP, .net
 or database like Oracle, MySQL, etc.
 Or other high-level technical details of the project
Built Stage
 After design stage, it is built stage, that is nothing but coding
the software
Test Stage
 In this phase, you test the software to verify that it is built as
per the specifications given by the client.
Deployment stage  Deploy the application in the respective environment
Maintenance stage
 Once your system is ready to use, you may later require
change the code as per customer request
1.3 When to use SDLC Waterfall Model?
Waterfall Methodology can be used when:
 Requirements are not changing frequently
 Application is not complicated and big
 Project is short
 Requirement is clear
 Environment is stable

 Technology and tools used are not dynamic and is stable
 Resources are available and trained
1.4 Advantages and Disadvantages of waterfall model
Advantages Dis-Advantages
 Before the next phase of development,
each phase must be completed  Error can be fixed only during the phase
 Suited for smaller projects where
requirements are well defined
 It is not desirable for complex project
where requirement changes frequently
 They should perform quality assurance
test (Verification and Validation) before
completing each stage
 Testing period comes quite late in the
developmental process
 Elaborate documentation is done at
every phase of the software’s
development cycle
 Documentation occupies a lot of time
of developers and testers
 Project is completely dependent on
project team with minimum client
intervention
 Clients valuable feedback cannot be
included with ongoing development
phase
 Any changes in software is made during
the process of the development
 Small changes or errors that arise in the
completed software may cause a lot of
problems

2. Prototyping Model
2.1 What is the prototyping model?
Prototyping Model is a software development model in which prototype is built, tested, and reworked until an acceptable
prototype is achieved. It also creates base to produce the final system or software. It works best in scenarios where the
project’s requirements are not known in detail. It is an iterative, trial and error method which takes place between
developer and client..
rotot ing Model in oft are ngineering Met odolog ro ess roa(P yp S w E : h y, P c , App ch, 2021)
Figure rotot ing Model
3 P yp
2.2 Prototyping Model Phases
Prototyping Model has following six SDLC phases as follow:
- Step 1: Requirements gathering and analysis
 A prototyping model starts with requirement analysis. In this phase, the requirements of the system are defined in
detail. During the process, the users of the system are interviewed to know what is their expectation from the system.
- Step 2: Quick design
 The second phase is a preliminary design or a quick design. In this stage, a simple design of the system is created.
However, it is not a complete design. It gives a brief idea of the system to the user. The quick design helps in

developing the prototype.
- Step 3: Build a Prototype
 In this phase, an actual prototype is designed based on the information gathered from quick design. It is a small
working model of the required system.
- Step 4: Initial user evaluation
 In this stage, the proposed system is presented to the client for an initial evaluation. It helps to find out the strength
and weakness of the working model. Comment and suggestion are collected from the customer and provided to the
developer.
- Step 5: Refining prototype
 If the user is not happy with the current prototype, you need to refine the prototype according to the user’s feedback
and suggestions.
 This phase will not over until all the requirements specified by the user are met. Once the user is satisfied with the
developed prototype, a final system is developed based on the approved final prototype.
- Step 6: Implement Product and Maintain
 Once the final system is developed based on the final prototype, it is thoroughly tested and deployed to production.
The system undergoes routine maintenance for minimizing downtime and prevent large-scale failures.
2.3 When to use SDLC Prototyping Model?
Prototype model can be used when:
Prototype model should be used when the desired system needs to have
 a lot of interaction with the end users.
 Typically, online systems, web interfaces have a very high amount of interaction with end users, are best suited for
Prototype model. It might take a while for a system to be built that allows ease of use and needs minimal training for
the end user.
 Prototyping ensures that the end users constantly work with the system and provide a feedback which is incorporated
in the prototype to result in a useable system. They are excellent for designing good human computer interface
systems.

2.4 Advantages and disadvantages of prototyping mode
Advantages:
 Users are actively involved in development. Therefore, errors can be detected in the initial stage of the software
development process.
 Missing functionality can be identified, which helps to reduce the risk of failure as Prototyping is also considered as
a risk reduction activity.
 Helps team member to communicate effectively
 Customer satisfaction exists because the customer can feel the product at a very early stage.
 There will be hardly any chance of software rejection.
 Quicker user feedback helps you to achieve better software development solutions.
 Allows the client to compare if the software code matches the software specification.
 It helps you to find out the missing functionality in the system.
 It also identifies the complex or difficult functions.
 Encourages innovation and flexible designing.
 It is a straightforward model, so it is easy to understand.
 No need for specialized experts to build the model
 The prototype serves as a basis for deriving a system specification.
 The prototype helps to gain a better understanding of the customer’s needs.
 Prototypes can be changed and even discarded.
 A prototype also serves as the basis for operational specifications.
 Prototypes may offer early training for future users of the software system.
- Disadvantages:
 Prototyping is a slow and time taking process.
 The cost of developing a prototype is a total waste as the prototype is ultimately thrown away.
 Prototyping may encourage excessive change requests.
 Some times customers may not be willing to participate in the iteration cycle for the longer time duration.

 There may be far too many variations in software requirements when each time the prototype is evaluated by
the customer.
 Poor documentation because the requirements of the customers are changing.
 It is very difficult for software developers to accommodate all the changes demanded by the clients.
 After seeing an early prototype model, the customers may think that the actual product will be delivered to him
soon.
 The client may lose interest in the final product when he or she is not happy with the initial prototype.
 Developers who want to build prototypes quickly may end up building sub- standard development
solutions.
3. Spiral model
3.1 What is spiral model?
Spiral Model is a risk-driven software development process model. It is a combination of waterfall model and iterative
model. Spiral Model helps to adopt software development elements of multiple process models for the software project
based on unique risk patterns ensuring efficient development process.
(Spiral Model: When to Use? Advantages & Disadvantages, 2021)Figure s iral odel
4 p m
Figure s iral odel
4 p m
Figure s iral odel
4 p m
Figure s iral odel
4 p m
Figure s iral odel
4 p m
Figure s iral odel
4 p m

Figure s iral odel
4 p m
3.2 Spiral Model Phases
Spiral Model Phases Activities performed during phase
Planning
 It includes estimating the cost, schedule and resources for the
iteration. It also involves understanding the system
requirements for continuous communication between the
system analyst and the customer
Risk Analysis
 Identification of potential risk is done while risk mitigation
strategy is planned and finalized
Engineering
 It includes testing, coding and deploying software at the
customer site
Evaluation
 Evaluation of software by the customer. Also, includes
identifying and monitoring risks such as schedule slippage and
cost overrun

3.3 When to use Spiral Model?
➢ A Spiral model in software engineering is used when project is large
➢ When releases are required to be frequent, spiral methodology is used
➢ When creation of a prototype is applicable
➢ When risk and costs evaluation is important
➢ Spiral methodology is useful for medium to high-risk projects
➢ When requirements are unclear and complex, Spiral model in SDLC is useful
➢ When changes may require at any time
➢ When long term project commitment is not feasible due to changes in economic priorities
3.4 Advantages and disadvantages of spiral model
Advantages Disadvantages
 Additional functionality or changes can
be done at a later stage
 Risk of not meeting the schedule or
budget

 Cost estimation becomes easy as the
prototype building is done in small
fragments
 Spiral development works best for large
projects only also demands risk
assessment expertise
 Continuous or repeated development
helps in risk management
 For its smooth operation spiral model
protocol needs to be followed strictly
 Development is fast and features are
added in a systematic way in Spiral
development
 Documentation is more as it has
intermediate phases
 There is always a space for customer
feedback
 Spiral software development is not
advisable for smaller project, it might
cost them a lot
4. Agile Model
4.1 What is Agile Model?
Agile development model is also a type of Incremental model. Software is developed in incremental, rapid cycles. This results in small
incremental releases with each release building on previous functionality. Each release is thoroughly tested to ensure software quality is
maintained. It is used for time critical applications.

e el et al(L v ., 2021)
4.2 Phases of Agile Model
➢ Requirements gathering: In this phase, you must define the requirements. You should explain business opportunities and plan the time and
effort needed to build the project. Based on this information, you can evaluate technical and economic feasibility.
➢ Design the requirements: When you have identified the project, work with stakeholders to define requirements. You can use the user flow
diagram or the high- level UML diagram to show the work of new features and show how it will apply to your existing system.
➢ Construction/ iteration: When the team defines the requirements, the work begins. Designers and developers start working on their project,
which aims to deploy a working product. The product will undergo various stages of improvement, so it includes simple, minimal functionality.
➢ Testing: In this phase, the Quality Assurance team examines the product's performance and looks for the bug.
➢ Deployment: In this phase, the team issues a product for the user's work environment.
➢ Feedback: After releasing the product, the last step is feedback. In this, the team receives feedback about the product and works through the
feedback.
4.3 When to use Agile model
➢ When new changes are needed to be implemented. The freedom agile gives to change is very important. New changes can be implemented at very
little cost because of the frequency of new increments that are produced.
➢ To implement a new feature the developers need to lose only the work of a few days, or even only hours, to roll back and implement it.
➢ Unlike the waterfall model in agile model very limited planning is required to get started with the project. Agile assumes that the end users’ needs
are ever changing in a dynamic business and IT world. Changes can be discussed and features can be newly effected or removed based on feedback.
This effectively gives the customer the finished system they want or need.
➢ Both system developers and stakeholders alike, find they also get more freedom of time and options than if the software was developed in a more
rigid sequential way. Having options gives them the ability to leave important decisions until more or better data or even entire hosting programs
are available; meaning the project can continue to move forward without fear of reaching a sudden standstill.
4.4 Advantages and disadvantages of Agile model
Advantages of Agile model:

 Customer satisfaction by rapid, continuous delivery of useful software.
 People and interactions are emphasized rather than process and tools. Customers, developers and testers constantly
interact with each other.
 Working software is delivered frequently (weeks rather than months).
 Face-to-face conversation is the best form of communication.
 Close, daily cooperation between business people and developers.
 Continuous attention to technical excellence and good design.
 Regular adaptation to changing circumstances.
 Even late changes in requirements are welcomed
Disadvantages of Agile model:
 In case of some software deliverables, especially the large ones, it is difficult to assess the effort required at the
beginning of the software development life cycle.
 There is lack of emphasis on necessary designing and documentation.
 The project can easily get taken off track if the customer representative is not clear what final outcome that they
want.
 Only senior programmers are capable of taking the kind of decisions required during the development process. Hence
it has no place for newbie programmers, unless combined with experienced resources.
5. Which method is best for tune source and why?
- Agile software development is best methodology for tune source because It has many reasons to be suitable for
Tune Source:
➢ Lower Cost
➢ Enables clients to be happier with the end product by making improvements and involving clients with
development decisions throughout the process.

➢ Encourages open communication among team members, and clients.
P2. Explain how risk is managed in the Spiral lifecycle model
1. Introduction of Risk
- Even the most carefully planned project can run into trouble. No matter how well you plan, your project can always
encounter unexpected problems. Team members get sick or quit, resources that you were depending on turn out to be
unavailable, even the weather can throw you for a loop (e.g., a snowstorm). So does that mean that you’re helpless against
unknown problems? No! You can use risk planning to identify potential problems that could cause trouble for your project, analyze
how likely they are to occur, take action to prevent the risks you can avoid, and minimize the ones that you can’t.
- A risk is any uncertain event or condition that might affect your project. Not all risks are negative. Some events (like
finding an easier way to do an activity) or conditions (like lower prices for certain materials) can help your project.
When this happens, we call it an opportunity; but it’s still handled just like a risk.
2. Inportance of risk management
Risk management encompasses three processes: risk assessment, risk evaluation and. risk mitigation Risk management
is the process that allows IT managers to balance the operational and economic costs of protective measures. This
process is not unique to the IT environment; indeed it pervades decision-making in all areas of daily routine work.
Minimizing negative impact on an organization and need for sound basis in decision making are the fundamental
reasons organizations implement a risk management process for their IT systems. sible for the final Effective risk
management must be totally integrated into the System Development Life Cycle. Risk management can be performed in
support of each system development life cycle phase.
- Phase 1—Initiation: Identified risks are used to support the development of the system requirements, including security
requirements, and a security concept.
- Phase 2—Development or Acquisition: The risks identified during this phase can be used to support the security analyses
of the IT system that may lead to architecture and design tradeoffs during system development of operations (strategy)

decision
- Phase 3— The risk management process supports the assessment of the system implementation against its requirements
and within its modeled operational environment. Decisions regarding risks identified must be made prior to system
operation
- Phase 4—Operation or Maintenance: Risk management activities are performed for periodic system reauthorization (or
reaccreditations) or whenever major changes are made to an IT system in its operational, production environment (e.g., new
system interfaces)
-Phase 5—Disposal: Risk management activities are performed for system components that will be disposed of or replaced to
ensure that the hardware and software are properly disposed of, that residual data is appropriately handled, and that system
migration is conducted in a secure and systematic manner
3. Risk management Process
Risk management process involves:
 Identify Organizational Risks: By surveys, interviews, and solicitation of input across divisions and departments of
Probability - The likelihood of risk getting realized.
 Inherent Risk - The nature of the risk event.
 Mitigation Control Effectiveness - The effectiveness of mitigation plans.
4. How to manage risk in the Spiral lifecycle model.
4.1. Introduction of Spiral lifecycle model
Spiral model is one of the most important Software Development Life Cycle models, which provides support for Risk

Handling. In its diagrammatic representation, it looks like a spiral with many loops. The exact number of loops of the
spiral is unknown and can vary from project to project. Each loop of the spiral is called a Phase of the software
development process.
(Spiral Model (Software Engineering) - javatpoint, 2021)
4.2. Phases of Spiral model
Each cycle in the spiral is divided into four parts:
 Objective setting: Each cycle in the spiral starts with the identification of purpose for that cycle, the various
alternatives that are possible for achieving the targets, and the constraints that exists.
is ssess ent and redu tionR k A m c : T e ne t ase in t e le is toh x ph h cyc al ulate t ese arious alternati es based on t e goalsc c h v v h
and onstraints T e fo us of e aluation in t is stage is lo ated on t e ris er e tion for t ec . h c v h c h k p c p h ro e tp j c .
 Development and validation: The next phase is to develop strategies that resolve uncertainties and risks. This
process may include activities such as benchmarking, simulation, and prototyping.

 Planning: Finally, the next step is planned. The project is reviewed, and a choice made whether to continue with a
further period of the spiral. If it is determined to keep, plans are drawn up for the next step of the project.
Figure ases of iral odel
6 Ph Sp m
4.3 How to manage risk
- Risk analysis which involves defining, evaluating and tracking the technological feasibility and handling risks such as cost
overrun and schedule slippage is performed in the second quadrant of the spiral model. After this all possible solutions are
analyzed in order to choose the best possible solutions. The risks involved with that solution will be established later and then
the problem will be overcome with the best available solution. Finally, the prototype at the end of this quadrant is
constructed for the best possible solution. So in short we might conclude that defining possible danger is achieved when
preparing and finalizing risk reduction policy.In the spiral model diagram above, the creation component has been broken
into the four-quadrant. It has provided one complete quadrant for risk assessment and mitigation even though there is no

danger in the context that there may be a danger in the future. It gives the risk reduction a greater focus.
- - Before the start of the spiral, it is common to identify risks and possible measures, the end of each spiral cycle is a review
and assessment of risk. For each spiral, The prototype is gradually being completed. The risk analysis will lead to whether the
project should be continued or stopped….
Figure 7 Risk management
4.3.1 Introduction of Spiral lifecycle model
Risk assessment may be described as defining, evaluating, and measuring the risk levels involved in a scenario, measuring
them to thresholds or expectations and deciding an appropriate level of risk. It analyses the risk and allows the production

to overcome the danger that emerged. The risk assessment is further broken down into three sections given below:
 Identification: Risk identification is the first risk identification tool. We cannot find the right solution, without
defining the possibility. We should know what kinds of danger it is or what kinds of danger will exist in the future so
that we can find the best possible way to address the problem.
 Prioritization: Following risk analysis, we should classify the risk based on meaning, design, or hazard. Before solving
another problem, the problem which is very risky for the program or very important to solve should be resolved
unexpectedly. If we don't consider the danger so in the future it will carry a lot of tech problems.
 Analysis: We should evaluate the defined danger after Risk identification. In order to know the key causes of the
increase in solving it, we should examine thoroughly.
4.3.2 Phases of Spiral model
Risk control is the process by which businesses identify possible risks and intervene to minimize or remove those
hazards. In plain terms, we may conclude that the risk for managing it is controlled. There is no use of risk assessment
without managing risk and there will be various risks arising frequently in the applications.
 Planning: Planning, as we all know, involves preparing before doing something. Planning is the first move that
can be achieved while managing the risk.
 Resolution: We should go on to the second phase which is resolution after good preparation. On the basis of
which we prepare in this phase, we should move forward on the risk assessment or control process.
 Monitoring: Finally, it is monitoring that is the last most critical step in risk management. In this phase, it monitors
and assesses the program risk levels. After risk reduction, we must track the risk of anything to be effective in
solving it.
4.3.3 How to manage risk
P3 Explain the purpose of a feasibility report.
1. What is a feasibility report?
- A feasibility study is a way to evaluate the practicality and desirability of a project. Before a company invests time and

money into a project, they need to know how successful the project will be before investing. Sometimes companies
want to understand input costs, the amount of research that will need to be done, or even the marketability of a
project. With input prices, it is essential that companies understand, (even before they put time and research into the
project), how much it would cost to go through with their product.
- Companies also like to know if they put time into research and go through with their change or promotion of a product,
how the public/people will react to the change. Will people be fighting over the new product or will it fall through? The
purpose of feasibility studies is to provide companies information and analysis on whether or not you or your company
should pursue this course of action.
- Feasibility reports are usually used to sway decision makers towards one direction or the other. Many times there is
only one course of action but, there needs to be a second course of action.
2. Purpose of each element in a Basic Feasibility Report
2.1. Introduction of Basic Feasibility Report
- In its simplest form, a Feasibility Study presents the definition of an issue or opportunity to be studied, analyzes the current
mode of operation, the definition of requirements, the evaluation of alternatives and an the itinerary of action has been
agreed. Therefore, the Feasibility Study preparation activities are of a general nature and can be applied to any type of
project, be it system and software development, acquisition or any other project.
2.2. Purpose of four elements
- Analyzing the feasibility to evaluate the success potential of the project; Therefore, cognitive objectivity is an essential
element of the study's credibility with potential investors and lending institutions. There are four types of feasibility studies -
the separate areas the feasibility study considers, described below.
 Purose of Technical Feasibility
- This review focuses on the technical resources available to the organization. It helps organizations determine whether the
technical resources are meeting their competence and whether the technical team is capable of transforming ideas into
working systems. Technical feasibility is also related to an evaluation of the hardware, software, and other technical
requirements of the proposed system. As an exaggerated example, an organization won't want to try to bring Star Trek's

carriers into their building - for now, this project isn't technically feasible.
 Purpose of Economic Feasibility
- This assessment typically involves a cost/ benefits analysis of the project, helping organizations determine the viability,
cost, and benefits associated with a project before financial resources are allocated. It also serves as an independent
project assessment and enhances project credibility—helping decision-makers determine the positive economic benefits
to the organization that the proposed project will provide.
 Purpose of Schedele Feasibility
- This assessment is the most important for project success; after all, a project will fail if not completed on time. In
scheduling feasibility, an organization estimates how much time the project will take to complete.
- When these areas have all been examined, the feasibility analysis helps identify any constraints the proposed project
may face, including:
 Internal Project Constraints: Technical, Technology, Budget, Resource, etc.
 Internal Corporate Constraints: Financial, Marketing, Export, etc.
 External Constraints: Logistics, Environment, Laws, and Regulations, etc.
 Purpose of Operation Feasibility
- This assessment involves undertaking a study to analyze and determine whether—and how well—the organization’s
needs can be met by completing the project. Operational feasibility studies also examine how a project plan satisfies the
requirements identified in the requirements analysis phase of system development.
P4 Describe how technical solutions can be compared

1. Introduction of a feasibility study
A feasibility study assesses the operational, technical and economic merits of the proposed project. The feasibility study
is intended to be a preliminary review of the facts to see if it is worthy of proceeding to the analysis phase. From the
systems analyst perspective, the feasibility analysis is the primary tool for recommending whether to proceed to the
next phase or to discontinue the project.
2. Technical Feasibility
2.1. What is Technical Feasibility ?
- A large part of determining resources has to do with assessing technical feasibility. It considers the technical
requirements of the proposed project. The technical requirements are then compared to the technical capability of the
organization. The systems project is considered technically feasible if the internal technical capability is sufficient to
support the project requirements.
- The analyst must find out whether current technical resources can be upgraded or added to in a manner that fulfills the
request under consideration. This is where the expertise of system analysts is beneficial, since using their own
experience and their contact with vendors they will be able to answer the question of technical feasibility.
2.2. Can we build it ?
- The essential questions that help in testing the operational feasibility of a system include the following:
 Is the project feasible within the limits of current technology?
 Does the technology exist at all?
 Is it available within given resource constraints?
 Is it a practical proposition?
 Manpower- programmers, testers & debuggers
 Software and hardware
 Are the current technical resources sufficient for the new system?

 Can they be upgraded to provide to provide the level of technology necessary for the new system?
 Do we possess the necessary technical expertise, and is the schedule reasonable?
 Can the technology be easily applied to current problems?
 Does the technology have the capacity to handle the solution?
 Do we currently possess the necessary technology?
3. Economic Feasibility
3.1. What is Economic Feasibility ?
Economic analysis could also be referred to as cost/benefit analysis. It is the most frequently used method for
evaluating the effectiveness of a new system. In economic analysis the procedure is to determine the benefits and
savings that are expected from a candidate system and compare them with costs. If benefits outweigh costs, then the
decision is made to design and implement the system. An entrepreneur must accurately weigh the cost versus
benefits before taking an action.
3.2. Should we build it?
- Questions that may be raised in the economic analysis are:
 Is the system cost effective
 Are the benefits outweigh the costs?
 Cost of doing research for the entire system
 Cost of sales staff time
 Estimated cost of hardware
 Estimated cost of software / software development
 Is the project viable, with limited resources?
 What is the savings from the system?

 Costs for employee study time
 Software / packaging software development costs
 Choose between alternative financing arrangements (hire / lease / purchase)
4. Organizational Feasibility
4.1. What is Organization Feasibility
- Operational feasibility is dependent on human resources available for the project and involves projecting whether the
system will be used if it is developed and implemented.
- Operational feasibility is a measure of how well a proposed system solves the problems, and takes advantage of the
opportunities identified during scope definition and how it satisfies the requirements identified in the requirements
analysis phase of system development.
- Operational feasibility reviews the willingness of the organization to support the proposed system. This is probably the most
difficult of the feasibilities to gauge. In order to determine this feasibility, it is important to understand the management
commitment to the proposed project. If the request was initiated by management, it is likely that there is management
support and the system will be accepted and used. However, it is also important that the employee base will be accepting of
the change.
4.2. If we build it, will they come ?
- The essential questions that help in testing the organizational feasibility of a system include the following:
 Does current mode of operation provide adequate throughput and response time?
 Does current mode provide end users and managers with timely, pertinent, accurate and useful formatted
information?
 Does current mode of operation provide cost-effective information services to the business?
 Could there be a reduction in cost and or an increase in benefits?
 Does current mode of operation offer effective controls to protect against fraud and to guarantee accuracy and
security of data and information?
 Does current mode of operation make maximum use of available resources, including people, time, and flow

of forms?
 Does current mode of operation provide reliable services
 Are the services flexible and expandable?
 Are the current work practices and procedures adequate to support the new system?
 If the system is developed, will it be used?
 Manpower problems
 Labour objections
 Manager resistance
 Organizational conflicts and policies
5. Discuss whether the project is feasible
5.1. Analyzing Costs vs. Benefits
Calculate Return on Investment ( ROI):
ROI = Gain from Investment - Cost of Investment
Cost of Investment
5.2. Calculating Present Value
 if the discount rate is 20%, prevent_value each year is

5.3. Net Present Value
Cash flow
description
year 0 year 1 year 2 year 3 year 4 year 5
Development
cost
$500.000
Operation &
maintenance
cost:
$20.000 $22.000 $24.000 $28.000 $30.000
Discount
factors for 20%:
1 0.83 0.694 0.586 0.482 0.402
Time-adjusted
costs:
$500.000 $16.600 $15.268 $14.064 $13.496 $12.060
Cumulative
time - adjusted
costs over
$500.000 $516.600 $531.868 $545.932 $559.428 $571.488
Benefits
derived from
operation of
new:
$0 $170.000 $200.000 $250.000 $290.000 $300.000
Time - adjusted
benefits
(current of
present)
$0 $141.100 $138.800 $146.500 $139.780 $120.600
Cumulative
time - adjusted
benefits over
$0 $141.100 $279.900 $426.400 $566.180 $686.780
0 1 2 3 4 5
Cumulative life
time - adjusted
costs +
($500.000) ($375.500) ($251.968) ($119.532) $6.752 $115.292

Figure a ba nal sis
8 P y ck A y
 Conclusion, Project can accept and proceed.
6. Alternative technical solutions using the alternative matrix
6.1. Javascript
JavaScript is one of the easiest, versatile and effective languages used to extend functionality in websites. JavaScript
Development Services helps in on-screen visual effects and processing and calculating data on web pages with ease.
The programming language also helps in extended functionality to websites using third party scripts among several
other handy features.
Advantages Disadvantages

 Speed
 Simplicity
 PopularityInteroperability
 Server Load
 Rich Interfaces
 Extended Functionality
 Versatility
 Less Overhead
 Client-side Security
 Browser Support
 Lack of Debugging
 Single Inheritance
 Rendering Stopped
6.2. .Net
- One of the most popular software development frameworks in the market, the .NET Framework props up many of
the applications that we know of today. It is used widely by developers due to how prolific it is and how large the
ecosystem has become. The fact that it is open-source is also why we have noticed that it is quite popular,
particularly among developers with large projects meant for a slew of different platforms.
- T e biggest benefi iaries of t e T Fra e or are businesses t at are in need of a lot of features t at are eanth c h .NE m w k h h m
to address a nu ber of re uired ser i es T esem q v c . h ser i esv c ouldw
Advantages Disadvantages

 Object-Oriented Programming
(OOP)
 Great Caching System
 Visual Studio
 Cross-Platform Development
 Easy to Deploy and Maintain
 Large community
 Licensing cost.
 Vendor lock-in
 Object-Relational Support Issues
 Stability Issues for New Releases
6.3 Html
Hypertext Markup Language (HTML) is the standard markup language for documents designed to be displayed in a web
browser
Advantages Disadvantages
 HTML is widely used.
 Every browser supports HTML Language.  Easy to
learn and use.
 Do not need to purchase any extra software
because it is by default in every window.
 HTML can create only static and plain pages so if
we need dynamic pages then HTML is not useful.
 I need to write a lot of code for making a
simple webpage.
 Security features are not good at HTML.  If we
need to write long code for making a webpage
then it produces some complexity.
6.4 Css
C is a language to reate st le for t e ebsite Cas ading t le eet language t is used to st le and st le ele ents ritten in ar uSS c y h w - c S y Sh . I y y m w m k p
language su as TM t distinguis es t e a earan e of t e ebsite fro t e ain ontent of t e age b ontrolling t e la out, ch H L. I h h pp c h w m h m c h p y c h y ,
olor and fontc , .

Advantages Disadvantages
 CSS saves a lot of time.
 It helps to make consistent and spontaneous
changes.
 It improves the loading speed of the page.
 CSS has the ability to re-position.
 It has better device compatibility.
 There could be cross-browser issues while
using CSS.
 There are multiple levels of CSS such as CSS,
CSS 2, CSS 3. This can create confusion for non-
developers and beginners.
6.5 A summary weighted score table
Feasibility Criteria
score
Weight ASP.net PHP+HTML+CSS+JS JAVA
Technical feasibility 40% 20 90 10
Economic feasibility 40% 60 80 40
Organizational
feasibility
20% 80 80 80
Total Score 100% 140 250 130
 Alternative Weighted Matrix explanation

➢ Technical feasibility
- ASP.net: In entire IT team, there are only 20% of them have been work with this technology before ➔ too lack of
experience
- PHP+HTML+CSS+JS: these are the most popular program project for web-design and webdeveloping. Moreover,
according to a recent research, up to 80% of IT team are professional in HTML+CSS+JS, and the rest are master and
professional in PHP ➔ high experience
- JAVA: this technology has the same problem as ASP.net, only small number have worked with this language.➔ too lack of
experience
➢ Economic feasibility
➢ Economic feasibility
- ASP.net: it takes 200.000$ to develop and 2 years to finish project ➔ cost too much time and money
- PHP+HTML+CSS+JS: it takes 100.000$ to develop and 10 months to finish project. Because we don’t have to spent time and
fee for employee to train as well as monthly training, we can save a lot of time and money. ➔ economical and short finish
time
- JAVA: it takes 300.000$ to develop and 1 year to finish project➔cost too much time and money
➢ Organizational feasibility
➢ The Tune Source project has a high organizational feasibility. They have a good management team, experienced and
highly specialized. They also have good knowledge of their field. The IT department also has experiences with Internet