Table of Contents

Part: 1..........................................................................................................................................................2
Introduction.................................................................................................................................................3
SDLC model............................................................................................................................................3
Iterative model.........................................................................................................................................4
Steps in Iterative methods........................................................................................................................5
Spiral model............................................................................................................................................6
Steps of Spiral model...............................................................................................................................6
Pros of Spiral model.................................................................................................................................7
Cons of Spiral model................................................................................................................................7
Management of risk in spiral model........................................................................................................7
Agile model.............................................................................................................................................7
Steps in Agile model................................................................................................................................8
Pros of Agile model.................................................................................................................................8
Cons of Agile model................................................................................................................................9
Sequential model.....................................................................................................................................9
Steps of sequential model........................................................................................................................9
Waterfall model.....................................................................................................................................10
Steps of Waterfall model........................................................................................................................10
Pros of Waterfall model.........................................................................................................................11
Cons of waterfall model........................................................................................................................11
V-model.................................................................................................................................................11
Steps of V-model....................................................................................................................................12
Selection of a model for the development environment.........................................................................14
Merits of applying Waterfall lifecycle model to a large software development project.........................14
Conclusion.................................................................................................................................................16
Part: 2........................................................................................................................................................17
Introduction...............................................................................................................................................17
Feasibility report....................................................................................................................................17
Part: 1
As a part of your responsibility you are required to prepare a report that describes different
software
development cycles. Your report must include the following:
1. Description of predictive and adaptive software development models considering at least two
iterative and two sequential models.
2. The risks involved in each of the models and how the risk can be mitigated /managed in each
model by taking a reference of the spiral model.
Once you have prepared the report you are required to produce documentation that
3. Describe with an example why a particular lifecycle model is selected for a development
environment. You may consider a different development environment with different business
logics, platform, etc., and the applicability of the particular software development model over the
development environment.
4. Assess the merits of applying the waterfall model to a large software development project with
appropriate evidenced researched work with reference to the current context.

Introduction
In this first part of my SDLC assignment, I am going to explain about the software development
lifecycles. Here, I am going to describe some iterative and sequential lifecycle models along with
its definition, steps, diagram, pros and cons. Also, I am going to write about spiral model along
with its definition and management of its risks. Similarly, I am going to select a particular
lifecycle model for a development environment and describe why I chose that particular lifecycle
model. Then, I am going to assess the merits of using waterfall model in a large software
development.
SDLC model
Software Development Lifecycle (SDLC) can be defined as a framework which describes the
activities performed at each stage of a software development project. SDLC is a splitting of a
software development work into distinct phases or stages containing activities with the intent of
better planning and management. SDLC aims to produce a high quality software that meets or
exceeds customer expectations, reaches completion within time and cost effective. Every SDLC
models have various phases which should be followed from the time of initiation to end of the
project. Some of the models are: waterfall model, agile model, spiral model etc. Such models are
beneficial and important to develop an effective software.
There are the two types of the SDLC models:
1. Predictive
Predictive Software Development Lifecycle includes the following models of the
software development:
 Waterfall model
 Prototyping model
 Rapid Application Development (RAD) model
2. Adaptive
Adaptive Software Development Lifecycle includes the following models of the software
development:
 Spiral model
 Agile model
 Dynamic System Development Method (DSDM)

Iterative model
Iterative model is a particular implementation of software development life cycle that focuses on
the initial and simplified implementation which after that progressively gains more complexity
and a boarder feature set until the final system is complete. Such style of model does not attempt
to start with a full specification of requirements.
 Fig: Iterative model
Steps in Iterative methods
The steps involved in iterative methods usually are as follows:

Planning & requirements

In any development project, initial planning is the first step to find any hardware or software
requirements, specification document and prepare for next stages of cycle.
Analysis and design

After planning is done, analysis of the project is done to point out appropriate logics, database
models and so on which will be needed at this stage in project. Similarly, design stage also falls
here. The design is made after analysis of the requirements are done which would help other to
study the structure of the software. Technical requirements will be utilized to meet the needs of
analysis stage and customer in this stage.
Implementation

Actual implementation along with coding processes are done after completing planning and
analysis. Every planning, specification and design formed till here are coded and implemented
into this initial iteration of project.
Testing

After the iteration is coded and implemented, next step is testing where a various test is
performed in order to identify and find any possible bugs present in the project.
Evaluation

Evaluation is performed thoroughly, once all stages are completed. It allows whole team, clients
and other parties to examine the project so that the necessary changes can be made to improve
the whole development project to meet customers need.
The process can be repeated again if needed
Spiral model
Spiral model is the combination of iterative development model and sequential linear
development model with a high emphasis on risk handling. In simple word, it is a model that
works on combined approach of iterative and waterfall model. It is also known as risk driven
software development process model. It is more suitable and effective for large projects rather
than smaller ones as it can undergo infinite iterations and requires more cost along with need of
complex requirements.

Steps of Spiral model

The steps involved in spiral model are as follows:

Identification

Requirements are gathered from the clients in the baseline spiral. In this phase, identification of
the system, sub-system and unit requirements are done. This includes understanding the system
requirements by continuous communication between the customer and the system analyst.
Design

After identifying the requirements, design is done. It helps other to study the structure of the
software. This phase starts with the conceptual design in the baseline spiral and involves
architectural design, logical design of modules, physical product design and the final design in
the subsequent spirals.
Construct or build

Construct phase starts right after accomplishment of identification and design phase. In this
phase, production of actual software product is done at every spiral. In the baseline spiral, when
the product is just thought of and the design is being developed a, POC (Proof of Concept) is
developed in this phase to get customer feedback. This helps to provides a better and clear idea
on requirements and designs. After this, in subsequent models, a product model known as build
is developed with the version number. Then these are sent to obtain feedbacks from the
customers.
Evaluation and risk analysis

In this phase, technical feasibility and risks are identified, monitored and estimated like cost
overrun and schedule slippage. At the end of the first iteration after testing the build, customer
evaluates the software to give a feedback.
Pros of Spiral model
 High and better risk analysis as it helps to avoid any risks.
 It can be used for critical and larger projects.
 Additional functionality could be added later.
 Software is developed at an early stage of lifecycle.

Cons of Spiral model

 It is an expensive model to use.
 It is not appropriate model for smaller projects.
 Success of the project depends on risk analysis phase. To analyze risks, highly skilled
experts are needed.
 Documentation amount is more in this model.

Management of risk in spiral model

In order to manage the risks in the spiral model, risks should be identified and analyzed. Every
possible risks are forecasted along with its solutions. In risk analysis phase, alternative solutions
are made to implement by identifying and studying the possible risks. A prototype is developed
at the end of risk analysis phase. If there occurs ay risk during this, then the best alternative
solutions are suggested and implemented. Even if there is no risk during analysis, with time risks
may arise in near future. To avoid such outcomes, possible risks should be identified thoroughly
within time.
Agile model
Agile model is the combination of iterative and incremental process models that focuses on
adaptability of process and customer satisfaction with rapid delivery of working software project.
This model breaks the product into smaller incremental builds. Such builds are provided in
iterations which usually lasts from one to three weeks. A working product is shown to the
customer and valuable stakeholders at the end of iteration.

Fig: Diagram of Agile model

Steps in Agile model
The steps involved in agile model are as follows:

Planning and requirement analysis

As in any project, planning is firstly done in this model. Goal of this stage is to find the detailed
definition of the system requirements. Every members of the team needs to have a clear idea
about every tasks and requirements that are required to be implemented as per the needs of users.
Similarly, preparation for the upcoming stages are done in this stage.
Design

After the gathering of the requirements, designing phase is initiated by the developers where the
layout of the software is developed which would help others to understand the structure of the
software. Until and unless the proper design of the software is made, further tasks are not
performed.
Development/ Building
This stage starts right after designing the software successfully. Coding are performed in this
stage while keeping previously defined requirements in the mind. By adjusting the software
environment, user interface of program is developed to interact with users.
Testing

After the completion of the development stage, testing is carried out to find any possible bugs or
errors present in the software so that the developers can improve or enhance the software and
available the product in the markets.
Pros of Agile model
 This model is easy to manage and promotes teamwork.
 It is a very realistic approach to software development.
 Required resources are minimum and useful for environments which change steadily.
 Functionality could be developed easily and provides flexibility to the developers.

Cons of Agile model

 This model is not appropriate for the handling of complex dependencies.
 There is more chance of risk related to sustainability and maintenance.
 This model depends upon customer interaction.
 There is minimum documentation generated which increases individual dependency.

Sequential model
In this model, one stage must be finished completely in order to move onto next stage. The
phases are performed sequentially i.e. single (one by one) phase at a time. There is no going
backward to previous stage after finishing that stage as the output of one phase acts as the input
for another or next phase sequentially.

Fig: Diagram of sequential model

Steps of sequential model
The steps involved in sequential models are as follows:

Requirement analysis

In this first stage, every requirement for the software development are analyzed and gathered. So,
this involves what needs to be designed along with its function, purpose and son on.
Specifications of input and final product are studied and marked.
System design

System design is made after studying the requirement specifications from the previous phase. It
helps to specify hardware and software requirements so that the system architecture can be
defined as a whole. Coding to be implemented in next phase are created here.
Implementation

By the help of inputs from system design, the system is divided into small programs known as
units that are integrated to next phase. Each units are developed and tested for its functionality
which is known as unit testing.
Integration and testing

After testing of every unit, all units of implementation phase are integrated into the system. The
designed software is tested to check or find bugs or errors present in the software.
Deployment

After completing the tests, the product is deployed in the customer environment and made
available in the different markets.
Maintenance

In this phase, required modifications are made to the system in order to improve the
performance. Such modifications are performed due to various reasons like requests from
customers, defects found while using the system etc.
Waterfall model
Waterfall model is the earliest and most widely known SDLC approach used for software
development and it is simple to understand as well as use. In this model, development process
moves step by step through different phases like analysis, testing, implementation and so on like
a downward flow of water. Any phase in the development process of this model initiates only if
the previous phase is completed. This model is also known as Linear sequential lifecycle model
because it shows the software development process in a linear sequential flow.
Fig: Diagram of Waterfall model
Steps of Waterfall model
The steps involved in waterfall model are as follows:

Requirement analysis

In this first stage of waterfall model, every requirement needed for the software development are
analyzed and gathered. So, this involves what needs to be designed along with its function,
purpose and son on. Specifications of input and final product are studied and marked.
System design

System design is made after studying the requirement specifications from the previous phase
which helps to specify hardware and software requirements so that the system architecture could
be defined as a whole. Codes to be implemented in next phase are created here usually.
Implementation

By the help of inputs from system design, the system is divided into small programs known as
units that are integrated to next phase. Each units are developed and tested for its functionality
which is known as unit testing.
Integration and testing

After testing of every unit, all units of implementation phase are integrated into the system. The
designed software is tested to check or find bugs or errors present in the software.
Deployment

In this phase, the product is deployed in the customer environment and made available in the
different markets after completing tests.
Maintenance
In this phase, required modifications are made to the system in order to fix issues and improve
the performance. Such modifications are performed due to various reasons like requests from
customers, defects found while using the system etc.
Pros of Waterfall model
 It is simple and easy to understand.
 Stages and activities in this model are well-defined.
 This model is easy to explain to users.
 Phases are processed and completed one at a time so that they would not overlap.

Cons of waterfall model

 It is not a good model for complex projects.
 It can be costly and take more time.
 Going back to previous phase to change something is not possible.
 Less flexibility and has high risks.

V-model
V-model is a SDLC model in which process is executed in a sequential manner in V-shape. It is
also called as Verification and Validation model. It has a testing phase for every corresponding
development stage. So, each step directly linked with testing phase. As it is a sequential model,
the next phase would not be initiated until the previous phase is completed. It is an extension of
waterfall model where there is a corresponding testing phase for all development phases unlike
in waterfall model.

Fig: Diagram of V-model

Steps of V-model
The steps involved in V-model are as follows:
Requirement analysis
In this first phase of V-model, detailed communication is done with the customers in order to
have idea about the requirements and expectations of customers. If the requirements are not met,
then the outcome of the project would not be good and profitable. Hence, the requirements are
understood very well and gathered for further development stages.
System design
After the successful gathering of requirements, the second phase is initiated which is system
design. Here, in this phase, proper design of the system is designed along with the all necessary
hardware and communication setup which will be needed to develop the product.
Architectural design
Architectural design phase is initiated when the system design is completed. In this phase,
previous system design is further broken down in modules with various functionalities. By doing
this, the communication and transfer of data among internal modules and outside world is
understood clearly.
Module design
After architectural designing, module designing occurs in a sequential manner where the system
is further broken down into smaller modules. Then the specification of modules are done as a
detailed design which is also referred as low level design (LLD).
Coding
After requirement analysis and all designing, coding phase comes next. Various programming
standards are used to develop and make the software more effective. The programming unit
begins to code the software while keeping the requirements and previous designs of software in
mind.
Unit testing
The unit test plans that are developed in module design phase are needed in this testing phase.
Those unit test plans are implemented in order to decrease errors or bugs while at code level.
Integration testing
Integration test is carried out after unit testing. In this test, modules are combined and the whole
system is tested as a single. Here, communication of modules are verified among themselves.
This testing is always done on architectural designing phase.
System testing
During this test, whole application of the system is tested on the basis of its functionality, inter-
dependency and communication. Similarly, functional and non-functional requirements are aso
tested of the developed application.
Acceptance testing
This test is done while in user environment which would similar production environment.
Acceptance testing verifies whether the system that has been delivered meets the requirements of
users or not. In case if the delivered system meets the requirements, it is accepted and deployed
in the market places that are ready to be used in real world.
Pros of V-model
 Phases are finished one at a particular time and is disciplined model.
 It is simple and easy to understand as well as use.
 This model is appropriate for the small project that have clear requirements.
 The progress made in the software are accurately tracked in this model.

Cons of V-model

 It is not suitable for large and complex projects.

 This model has high risk and uncertainty.
 Iteration of phases is not supported.
 It is difficult to handle existing or current events.

Selection of a model for the development environment

To select an appropriate model for any development environment is crucial for software
development process. Suitable model should be selected as per the requirement of the project
development. One should have proper and broad knowledge about the software development
models in order to be able to choose a model for a certain project.
According to the given scenario i.e. College Management System, from the study and knowledge
that I have gained by doing research on SDLC models I have selected Agile model as the suitable
one for this project as it is based on iterative and incremental development. This model focuses
more on adaptability of process and customer satisfaction with rapid delivery of working
software project because people and constant interaction are given more importance rather than
tools and process. One of the main reasons why I chose agile model is that a user can see and
understand the results whether he/she is satisfied with it or not. On the other hand, if there is no
defined requirements then it is quite troublesome to calculate the resources and cost of
development. So, this case can be studied properly, understood and handled very carefully to
avoid any unnecessary issues related to requirements. Similarly, our scenario is based on college
management system which have various departments of its own. Unlike some other models,
agile only needs limited planning to initiate. Time to time changes can take place in some
departments according to the new features, needs and requirements. Since the user needs and
requirements can change dynamically, Agile model is an appropriate model for this system in my
opinion because agile provides freedom of time, options and can adapt to changing
circumstances due to which late changes in requirements would not be a big problem. Such
flexibility in model helps to minimize risks, add new effective features as well as remove them
based upon the feedback from users. Ultimately, this provides effective finished system as the
users would want.
For example: based on our scenario, we can use various model for this system. But in my view,
Agile model would probably be the best one in this case. This model is iterative and incremental
in nature which provides flexible adaptability, customer satisfaction and requires less time to
complete the project. First of all, we need to gather all detailed information about the college and
collect all the requirements with proper planning of given system development. Planning is done
by interacting with people and developers involved in this system. Then we need to design a
good and suitable layout for the system by keeping the detailed information and gathered
requirements in mind. After this, necessary coding is performed to build a user interface for
program to interact in user environment. Finally, testing of the developed system is done to
locate any errors or bugs present in that system. If any error is found, the system can be changed
accordingly.
Therefore, considering several advantages and benefits of agile model and the mentioned
example have selected Agile model for the development environment of college management
system.
Merits of applying Waterfall lifecycle model to a large software development project
As discussed previously, Waterfall model most widely known SDLC approach used for software
development and it is simple to understand as well as use. In this model, development process
moves step by step through different phases like analysis, testing, implementation and so on like
a downward flow of water. Any phase in the development process of this model initiates only if
the previous phase is completed. This model is also known as Linear sequential lifecycle model
because it shows the software development process in a linear sequential flow. Though the
waterfall is replaced by agile and other dynamic methods, waterfall does have some advantages.
The merits of applying the Waterfall model to a large software development project are given
below:
Uses clear structure
On comparison with other models, Waterfall model is focused more on a clear and defined set of
steps. It has a simpler and clear structure where development cannot move into next phase until
the previous phase is completed. This would eventually help to prepare a polished project at the
end as the half-completed projects are unlikely to put aside in this model.
Determines end goal early
Waterfall model helps to maintain the main focus on end goal most of the time. Waterfall model
removes the risks of being stuck as we move toward the main goal, if a team have clear schedule
of tasks. Unlike in small projects where goals are clear from the start, large projects have
possibility of getting lost in details during the time of project development. So, Waterfall model
can help to clear and determine the main goal from the time of initiation.
Information is transferred well
Waterfall is a highly methodical approach as it emphasizes a clean transfer of information at each
step. Waterfall prioritizes accessible information so that fresh additions to team can catch up
speed quickly when required, if there occur any personnel changes unexpectedly. So even if the
changes occur in large projects, information are documented throughout the lifecycle of
project[ CITATION Pro17 \l 1033 ].
Simple to use and understand
This model is simpler to understand and use as the work cannot be continued or moved forward
into next phase until the previous phase is completed. Due to this, errors can be fixed at an early
stage which can affect the project during development period. With proper outline and clear
concept waterfall can be handled well even in the larger project.
Concrete schedule
A schedule with deadlines for every stage of development can be set with estimated workload so
that the product can move sequentially without any difficulty in time management and deliver
within an estimated time. Such activity would be beneficial for larger projects to define
milestones and deadlines.
Less financial issues
In any large projects, financial problems may occur time to time due to different reasons:
undefined requirements is one of the main reason. Once the requirements are determined,
allocation of required cost can be done with high accuracy. This can often reduce and remove the
financial risks during the development phase of software.
Departmentalization and managerial control
Waterfall model also facilitates departmentalization which means dividing of works into various
segments in order to perform tasks according to the specializations. Similarly, managerial control
is allowed in the waterfall model based on schedule and deadlines of the particular project.
Therefore, management of tasks can be much convenient and easy to process in this model.
Likewise, there are several advantages of waterfall model due to which it can be used in large
software development projects.

Conclusion
In this current part, I have explained software development lifecycle in detail along with iterative model
and sequential model where I have illustrated diagram of every model in order to have a clear
understanding of its structures. Similarly, I have mentioned pros and cons of each models that I have
discussed. For the development environment, I have selected agile model and explained why I have
chosen that particular model along with example. At last, I have pointed out and explained the merits of
applying the waterfall model to the large projects. With this, I have concluded my first part of my
assignment.
Part: 2
1. You are required to produce a documentation that explains the purpose of the feasibility report

and describe how technical solutions can be compared.

2. Prepare a brief report discussing the components of the feasibility report.

3. Carry out the feasibility study as per the best of your previous research work against the solution

to be developed for the given problem and assess the impact of different feasibility criteria on the

software investigation.

Introduction
In this second part, I am going to explain the feasibility report along with its purpose. After this, I am
going to describe and compare the technical solutions related to the report. The different components of
feasibility report will also be discussed briefly. Then, I am going to assess the impacts of various
feasibility criteria on a software investigation.

Feasibility report and its purpose

A feasibility report is a document which assesses the possible solutions to the business issue or
opportunity, and determines which of those are viable for further analysis. The purpose of the
feasibility report is to present the project limits and define potential solutions to the defined
problem or need [CITATION fes \l 1033 ].
Comparison of Technical solution
Based on different terms, technical solutions can be compared as below:

Budget

Budget is something which carries great importance in any kind of development project. A project is
expected to be completed within the estimated budget. To buy every hardware components and
requirements, manpower requires enough amount of money. If the required amount exceeds the
expected or estimated or allocated amount, various problems are more likely to arise related to it i.e.
there would be insufficient money to invest in the development of project which can cause a major
failure of the project. Therefore, if the budget is allocated properly then the project can run smoothly
without any budget issues.

Performance

Mostly people with the ability to perform well practically are more successful in the real fields. Such
people are given more priority as they can outperform others with less practical knowledge and these
sorts of employees can handle technical issues. As we know, most of the industries announce the
vacancy if they need to recruit the members followed by interviews where the participants are tested
logically and practically in some cases. From such events, participants with better performance skills are
selected and employed so it is safe to say that the performance is important to solve technical problems.

Efficiency

Efficiency means an ability to perform something with minimum amount of the effort. It helps to save
extra effort and time.

Automation (eliminate errors of human)

Automation means the use of electronics and computer-controlled devices to control process. It boosts
the reliability and efficiency. Similarly, automation also improves the productivity as well as quality a
task. So rather than performing time consuming tasks manually, performing those tasks automatically
would be better and it can reduce the chance of errors although such machines can be costly but it
would be worth it to save extra time and give that time to other works which must be done manually.
Therefore, automation can be a better technical solution in comparison.

Legacy system

Technical solutions can be compared by upgrading the previous systems rather than buying or
developing a new system for the same purpose which could cost more as it is the new version of the
same system. So instead of doing that, upgrading that same system would be easier and convenient and
it would not cost high and save the time. Therefore, such legacy system upgrading is necessary to
compare technical solutions.
Components of feasibility report
The various components of feasibility report are discussed below:
Introduction
In the first part of the feasibility report, clear explanation of the project is written so that the one
who reads the report can have a clear understanding of the whole project in detail. Through this
component, people can be aware about the things that are going to be included in the
development of the project. Suppose, someone important person from a college wants to check
feasibility report of a particular software then the first thing that they notice is introduction from
where the concept of the project can be clear.
Purpose
In this second part of feasibility report, main purpose or the reasons to make the particular
software should be mentioned with clear concept. Suppose, a college management system, it is
made to enter and keep records of the information and data of the students, manage the
courses, classes, library, extra curriculum activities, other departments and so on.
Methodologies
In this part of the report, different methods which are used during the project development are
mentioned and how those methods are carried out during the development time are explained.
Suppose, a college management system, to initiate this project firstly out of all the software
development model, a model needs to be chosen that would be the most suitable one for the
system among. Similarly, there can be other different methodologies applied in the system.
These all the methods are explained clearly in this part of report.
Background history
In this part of the report, information about the organization is collected before moving into the
development phase. With the help of this a developer can know the history of the organization
which would assist to make the application according to the needs of the organization and make
it more effective. Suppose, to an effective college management system, a developer may
require the information related to college members and students, initiation of the college,
different available departments of the college and so on.
Document structure
This part of the report holds important documents related to the project and college
management system. So, the documentation should be well maintained and handled well. Such
documents can help to illustrate where the flow of project development is moving towards.
Feasibility criteria
This part of the report includes the various criteria related to the project development. Some are
economic feasibility, technical feasibility criteria and so on. This part mentions whether the
criteria are met or not according to the needs and requirements. Suppose, a college
management system, before developing a software for the college a legal document may be
required to move the project ahead where the software developing party and college would
come to a mutual agreement related to cost to develop the software, time to accomplish the
software and son on.
Outcome
Here, in this part of the report, result of the project are included so that the result can be
compared to the expected outcome of the project. This helps to find whether the outcome of the
project is satisfactory or beyond it. If the result is not satisfactory, improvements can be done by
reviewing the system again.
Potential and feasible solution
This part of the report includes every possible and alternate solution to the errors and problems
that may arise before and after the development of project. This helps to save the time because
in case if there occurs any problem in the project, a solution can be implemented frequently to
solve it before it turns into major problem in the project. Such solutions should be sustainable
and feasible so that the same problems would not occur time to time in a long run.
Evaluation
This part of the project includes the estimation and evaluation of the project. Whether the project
meets the expectations and criteria of it are checked thoroughly here. Each criteria of the project
are evaluated so that the software development can be more efficient.
Suggestion and Conclusion
This is the last part of the feasibility report where recommendations are suggested and
concluded. Suggestions are provided to make and improve the project more. It is like a
feedback which says the system could have been more effective with less errors if this feature
was applied in the system. Finally, the conclusion of the report is done by acknowledging the
whole project.