INTERNATIONAL SCHOOL OF MANAGEMENT & TE

ASSIGNMENT COVER SHEET

STUDENT DETAILS

Student ID Reg No.

Family Name Given Name

Enrolment Year Section

Semester Email

UNIT DETAILS
Unit Title Unit Code

Assessor Name Issued Date

Assignment
Title

Assignment No Submission Date

Qualification Campus
 STUDENT ASSESSMENT SUBMISSION AND DECLARATION

When submitting evidence for assessment, each student must sign a declaration
confirming that the work is their own.

Student Name Assessor Name

Issue Date Submission Date

Programme

Unit Name

Assignment Title

Plagiarism

Plagiarism is a particular form of cheating. Plagiarism must be avoided at all costs

and students who break the rules, however innocently, may be penalized. It is your
responsibility to ensure that you understand correct referencing practices. As a
university level student, you are expected to use appropriate references throughout
and keep carefully detailed notes of all your sources of materials for material you
have used in your work, including any material downloaded from the Internet. Please
consult the relevant unit lecturer or your course tutor if you need any further advice.

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.

Pearson Education 2018

Higher Education Qualifications
Table of Contents
Scenario...............................................................................................................................5

Objective..............................................................................................................................6

LO1 Describe different Software Development Life Cycles........................................10

Executive Summary...................................................................................................10

SDLC.........................................................................................................................11

Benefits of using SDLC.............................................................................................11

Phases of SDLC.........................................................................................................11

Agile Model:..............................................................................................................12

Phases of Agile Model:..............................................................................................12

Advantages................................................................................................................13

Disadvantages............................................................................................................13

Spiral Model:.............................................................................................................14

Phases of Spiral Model:.............................................................................................14

Advantages................................................................................................................14

Disadvantages:...........................................................................................................15

Waterfall Model:........................................................................................................15

Phases of Waterfall Model:.......................................................................................15

Advantages................................................................................................................16

Disadvantages............................................................................................................16

V-Model:....................................................................................................................17

Verification Phase of V-Model:.................................................................................18

Validation Phase of V-Model:...................................................................................18

Advantages:...............................................................................................................19

Disadvantages:...........................................................................................................19
 Risk Management......................................................................................................20

Types of Risk.............................................................................................................20

The Agile Model's Major Risk Sources.....................................................................20

How can risk be mitigated in Agile Model?..............................................................21

Why Agile Model is best suited for our scenario?........................................................22

Merits of applying the Waterfall lifecycle model to a large software development

project........................................................................................................................23

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

Executive Summary...................................................................................................26

Feasibility Study........................................................................................................27

Feasibility Report.......................................................................................................27

Purpose of Feasibility Study......................................................................................27

Types of Feasibility Study.........................................................................................28

References..........................................................................................................................51
Scenario
As per the scenario I am hired as the System Analyst for Apex Educational
Institute(AEI). AEI is a predominantly operating educational institution in Nepal and is
offering education to many national and international students. It is one of the leading
research and academic institutes with nearly 4000 students, 75 faculty members and 40
non-teaching staffs across 4 departments (IT, Business, Hospitality Management &
ACCA) and 7 centers and is seeking an enhanced solution that automates various
academic and administrative activities. The institution is building a new Office
Management Solution. AEI has a small systems development team which in the past has
been solely responsible for all development work. The CEO of the AEI feels that the
Research & Development team has not been outward looking and wants a fresh approach
for the proposed system. The in-house team will work alongside analysts and developers
from my team who will lead the project. As the System Analyst I am responsible for
managing the project including analysis and design stage of the new system. My first task
as an Analyst is to update the in-house team on the developments in new methodologies
used to analyze systems as most of the in-house teams use a more traditional approach
and very few are aware of the agile methodologies which are increasing in popularity.
Objective
 International SchoolSubmitted
of Management
to: and
Technology (ISMT)
Mr. Rahul Kumar

Submitted By:

Kaushal Upadhya

2nd Semester Section B

Report on

Software Development Life Cycle

Table of Contents for LO1

LO1....................................................................................................................................10

Executive Summary...........................................................................................................10

SDLC.................................................................................................................................11

Benefits of Using SDLC....................................................................................................11

SDLC Phases.....................................................................................................................11

Agile Model.......................................................................................................................12

Phases of Agile Model.......................................................................................................12

Advantages of Agile Model...............................................................................................13

Disadvantages of Agile Model..........................................................................................13

Spiral Model......................................................................................................................14

Phases of Spiral Model......................................................................................................14

Advantages of Spiral Model..............................................................................................14

Disadvantages of Spiral Model..........................................................................................15

Waterfall Model.................................................................................................................15

Phases Of Waterfall Model................................................................................................15

Advantages Of WaterfallModel.........................................................................................16

Disadvantages Of WaterfallModel....................................................................................16

V-Model.............................................................................................................................17

Verification Phase V-Model..............................................................................................18

Validation Phase V-Model................................................................................................18

Advantages Of V-Model....................................................................................................19

Disadvantages Of V-Model...............................................................................................19

Risk Management..............................................................................................................20

Types Of Risk....................................................................................................................20
Risks Associated to Agile Model......................................................................................20

Risk Mitigation in Agile Model.........................................................................................21

Agile Model for Scenario..................................................................................................22

Merits Of Applying Waterfall Model to Large Projects....................................................23

LO1 Describe different Software Development Life Cycles
Executive Summary
SDLC
("What Is SDLC? Understand the Software Development Life Cycle", 2021) defines Software
Development Life Cycle (SDLC) as a methodology for developing high-quality software
that includes well documented processes.

SDLC is a well-structured flow of phases that enables a company to easily manufacture

high-quality software that has been thoroughly reviewed and is ready for production.

Benefits of using SDLC

 It shows why project planning, organizing, and budgeting are essential.
 It is an effective method for project management and monitoring.
 It aids in the reduction of project risk as well as the project administration
process.
 Helps during client interactions.

Phases of SDLC
The SDLC process is divided into five stages, which we will go through briefly below:

 Requirement Analysis: Requirement analysis is the initial phase of the Software

Development Life Cycle. The goal of this phase is to understand the client’s
requirements and to document them properly. The focus of requirement analysis
is on determining what the system requires. It is most crucial phase in Software
 Development Life Cycle. The output of requirement analysis is Software
Requirement Specification (SRS).
 Design: It is the first step to move from the problem towards the solution. It is the
most creative phase in Software Development Life Cycle. The goal of this phase
is to transform the requirement specification into structure. Software Design
Document(SDD) is the end result of this phase.
 Coding/Implementation: In this step, a programming language is used to convert
the SDD into code. This phase's output is software code.
 Testing: This is the most important phase since testing effectively would result in
higher-quality software products, satisfied customers, lower maintenance costs,
and more accurate and consistent performance.
 Maintenance: This process begins after the product has been delivered. This step
is where any errors or changes that need to be made are enforced.

Agile Model:
("Agile Model (Software Engineering) - javatpoint", 2021) says a software development
strategy focused on iterative development refers to as an "agile process model”. Agile
methods divide projects into smaller variations, or bits, and avoid long-term planning. At
the start of the planning process, the project scope and specifications are defined.

In the Agile method model, each iteration is thought of as a short time "frame" that lasts
between one and four weeks. The division of the whole project into smaller sections
helps to reduce overall project risk and implementation time requirements.

Phases of Agile Model:

 Requirements - Define the iteration's specifications based on the product
backlog, project schedule, and input from customers and clients.
 Development - Create applications based on specifications that have been
specified.
 Testing - Internal and external preparation, documentation production, and QA
(Quality Assurance) testing
 Delivery - Implement the working iteration into development and produce it.
  Feedback - Consider consumer and stakeholder input and incorporate it into the
next iteration's specifications.

Figure: Agile Model

Advantages
 Production on a regular basis and face-to-face communication with customers.
 Project that is both efficient and meets client’s needs.
 Changes can be made at any time, which cuts down on overall production time.

Disadvantages
 Due to a lack of structured documentation, there is inconsistency, and important
decisions made at various stages may be misinterpreted by different team
members at any moment.
 Maintenance of the completed project will become problematic due to a lack of
detailed reports after the project is completed and the developers are assigned to
another project.

Spiral Model:
("Spiral Model (Software Engineering) - javatpoint", 2021) defines Spiral Model as an
evolutionary software process model that combines the iterative aspect of prototyping
with the linear sequential model's controlled and systematic elements.

Phases of Spiral Model:

Phases of the Spiral Model are divided into four quadrants which are discussed below:

 Objectives determination and identify alternative solutions: At the start of

each stage, customers' requirements are gathered, and goals are defined,
elaborated, and evaluated. This quadrant then suggests alternative solutions for
the phase.
 Identify and resolve Risks: All potential solutions are evaluated in the second
quadrant in order to determine the appropriate one. The risks associated with the
method are then defined, and the risks are mitigated using the suitable methods
available. The Prototype is constructed at the end of this quadrant for the best
possible solution.
 Develop next version of the Product: The features that have been defined are
established and tested in the third quadrant. The next iteration of the program is
available at the end of the third quadrant.
 Review and plan for the next Phase: Customers test the functionality that has
been created so far in the fourth quadrant. Finally, the preparation for the next
step begins.

Advantages
 Due to the risk identification and risk management at each point, the Spiral Model
is the ideal planning model to pursue for projects with many unknown threats that
arise as the development progresses.
 In large and complex programs, the Spiral Model is suitable.
 Using this model, change requests in the Requirements at a later stage may be
implemented effectively.
Disadvantages:
 The Spiral Model is much more complicated than other SDLC models, and it is
too costly for small projects.
 Time estimation is difficult since the number of steps is uncertain at the start of a
project.

Figure: Spiral Model

Waterfall Model:
("What is Waterfall Model? Definition of Waterfall Model, Waterfall Model Meaning - The

Economic Times", 2021) defines waterfall model as a traditional system development life
cycle model that uses a linear and sequential approach to model a system. The model is
called a waterfall because it progresses gradually from one step to the next in a
downward direction.

Phases of Waterfall Model:

The phases of the waterfall model are briefed below:

 Requirement Gathering and analysis: This process captures all potential

specifications for the framework to be implemented and documents them in a
requirement specification document.
  System Design: This process examines the first phase's criteria requirements and
prepares the system design. This system design assists in determining the overall
system configuration as well as identifying hardware and system specifications.
 Implementations: The framework is designed in small programs called units,
which are then implemented in the next step, using inputs from the system design.
Unit Testing refers to the process of developing and testing each unit for its
functionality.
 Deployment of System: The product is deployed into the market after functional
and non-functional testing is completed.
 Maintenance: Patches are issued to address problems that can arise in the client
system. In order to improve the product, newer versions are released.
Maintenance is carried out in order to bring about these changes in the product.

Advantages
 Simple and straightforward to understand and apply. Because of the model's
rigidity, it's simple to handle.
 Phases are processed and completed one at a time.
 For projects with well-defined requirements, this method works effectively.

Disadvantages
 Only until the end of the life cycle will functional software be produced.
 There is a great deal of risk and confusion in this model.
 Not ideal for projects with a moderate to high chance of alteration in
specifications. As a result, this process model has a high level of risk and
instability.
 Figure: Waterfall Model

V-Model:
("SDLC - V-Model - Tutorialspoint", 2021) says
V-model is an SDLC model in which
processes are carried out in a V-shape in a sequential order. Verification and Validation
Model is another term for it.

The V-Model is based on the association of a testing process with each corresponding
development step, and it is an extension of the waterfall model. This ensures that each
step of the production cycle has a testing phase that is directly linked to it. This is a very
disciplined model, and the next step begins only after the previous one has been
completed.

Verification: It includes a static analysis method (review) that is performed without

running code. It's the method of evaluating the product development cycle to see if the
specifications are met.

Validation: It involves the use of complex analysis methods (functional and non-
functional), as well as code execution for checking. Validation is the method of
classifying software after it has been developed to decide if it meets the expectations and
specifications of the consumer.
Verification Phase of V-Model:
 Business requirement analysis: This is the first step in understanding the
customer's product specifications. This step involves extensive communication in
order to fully comprehend the customer's needs and specifications.
 System Design: Through reviewing the consumer specifications guide, system
developers evaluate and interpret the proposed system's business.
 Architecture Design: During this process, architectural requirements are
identified and designed. Typically, more than one technical solution is proposed,
and the final decision is made based on technical and financial viability. This is
also referred to as High Level Design (HLD).
 Module Design: This process specifies the comprehensive internal specification
for all system modules. It is also known as Low Level Design (LLD).
 Coding Phase: In the Coding process, the actual coding of the system modules
built in the Design phase is completed. Based on the framework and architectural
specifications, the best programming language is chosen. Before the final project
is installed into the repository, the project is subjected to various code tests and is
optimized for maximum output.

Validation Phase of V-Model:

 Unit Testing: During this validation process, unit tests created during the module
design phase are run on the code. Unit testing is code-level testing that assists in
the early detection of bugs.
 Integration Testing: Integration testing is associated with the architectural
design phase. Integration checks are used to ensure that internal components
inside the system can coexist and communicate with one another.
 System Testing: System testing is directly associated with the system design
phase. System tests examine the whole system's functionality as well as the
system's interaction with other systems.
 Acceptance Testing: Acceptance testing is associated with the business
requirement analysis phase and involves testing the product in user environment.
Acceptance checks reveal some inconsistencies with other systems in the user's
 environment. It also detects non-functional problems in the current user
environment, such as load and efficiency issues.

Advantages:
 It's ideal for smaller projects with well-defined specifications.
 Because of the model's robustness, it's simple to handle. There are clear outputs
and a review process for each phase.

Disadvantages:
 For diverse and object-oriented programs, this is not a suitable model. There are
also significant threats and instability.
 It's difficult to go back and adjust a function while a program is in the testing
stage.
 Until late in the development cycle, no working software is made.

Figure: V-Model
Risk Management
("The Project Risk Management Process | 5 Tips for Success", 2021) says the practice of
recognizing, evaluating, and preventing or minimizing risks to a project that have the
potential to affect the desired outcomes is referred to as risk management.

Types of Risk
Regardless of the project's specifics, there are various sorts of risks that arise frequently.
These are some of the most common categories of risk:

 Cost: The possibility of events that have an impact on the budget,

particularly those that cause the project to run over budget. In addition to
external causes, cost estimates errors are a common source of risk.
 Schedule: The risk of unanticipated scheduling issues, such as
circumstances delaying the project. Scope creep is a common cause of
project delays and schedule challenges.
 Performance: The risk of occurrences causing the project to deliver
results that do not match the project specifications.

There are a variety of potential dangers that can arise depending on the specifics of the
project. Project managers, for example, may need to plan for risks related to
implementation, training, and testing.

The Agile Model's Major Risk Sources

Despite its claims about risk management, agile development lacks any clear
recommendations for dealing with these threats. As a result, numerous risk sources will
be unchecked. The major sources of risk in agile development are as follows:

 Very large software system: Since the resulting increments would be rather
large, the basic risk management in agile development is insufficient for big,
sophisticated software systems. This would lengthen the period between
increments, requiring a greater cost to deal with any modifications or defects that
were identified.
  Large development team: It is not appropriate for big teams because
coordinating communication among team members would be significantly more
complex.
 High reliance on human factor: It is completely reliant on the development
team's experience and ability to properly interact with clients. Failure is
unavoidable if the project fails to achieve these conditions.
 Inappropriate customer representative: Another risk factor is the selection of
an effective customer representative. In fact, this component has the same impact
on the development process as team members.
 Distributed development environment: This methodology is not appropriate for
building software projects in a decentralized environment since it involves close
face-to-face communication between the development team. Otherwise, other
forms of communication, such as video conferencing, should be used on a daily
basis.
 Scope creep: Another significant risk issue is project scope, which occurs as a
result of the methodology's minimum planning, which causes developers to
become sidetracked from the project's major goals. As a result, the project will
grow in size, get more complex, and eventually overrun.

How can risk be mitigated in Agile Model?

 Transparency – Disclose everything we are working on so we can spot threats
early.
 Collaborative planning – Utilize the accumulated knowledge of the entire team
to identify further hazards.
 Customer involvement – By engaging with the client throughout the
development process, the client is able to address any new requirements and
customize the product to their specific specifications.
Why Agile Model is best suited for our scenario?
The system will be developed using Agile Model Methodology which is lenient when
compared to other models mentioned above. As per the requirements the system must
include Attendance, Record Management, and Accounting functions. Using this
methodology we can regularly involve with the client and change the design as per their
requirements. Agile model offers the luxury of being able to work flexibly and if the
systems requires something innovative in the design, an Agile software development
technique is best suited to projects of this nature. Agile places a higher value on features
and speed to market than strictly adhering to a budget.

As the project manager we can track team productivity and product delivery using the
Agile Method by using lean estimates approaches and emphasizing the delivery of
working software. This activity emphasizes teamwork and ensures that activities are
coordinated and synchronized. Agile Methodology ensures that teams focus on the most
critical aspects of the project first—features that will result in working software that adds
value to the company, however these features may change over the course of the project.
We can track team productivity and product delivery using the Agile Method by using
lean estimation approaches and emphasizing the delivery of working software.

Agile will produce more features in a shorter period of time and also gives the team more
flexibility throughout the process so that they can take advantage of opportunities as the
project unfolds.
Merits of applying the Waterfall lifecycle model to a large software development
project.
In software development businesses, waterfall development is still a popular method of
operating. When building a project, the waterfall process is rather simple and
expectations are clear if the requirements are put out with strict regulations and standards.
This model is better suited to organizations/projects with precise procedures that must be
maintained. Testers and developers can work on writing code and test cases. They don't
have to wait for instructions from clients because the product specifications are
established in advance. Waterfall may be more appropriate if the features are fully
specified and must interface with known or existing products. It will provide a more
predictable outcome if the project timeline and budget is set and cannot be changed.

Because the product requirements are specified and approved before development begins,
there is a commitment to deliver a defined set of features, making the final product more
predictable.

The model has been attributed to plenty of problems. Commonly acknowledged issues
include the inability to cope with change and the fact that flaws are frequently found too
late in the software development process. However, many of the problems mentioned in
literature are based on beliefs and experiences, and not on empirical evidence. Many of
the issues raised in the research, however, are based on individual beliefs and experiences
rather than factual data.
International School of Management and

Technology

(ISMT)

Feasibility Study

Research on feasibility study

Kaushal Upadhya

Date: 03/06/2021
Table of Contents for LO2

LO2....................................................................................................................................26

Executive Summary...........................................................................................................26

Feasibility Study................................................................................................................27

Feasibility Report...............................................................................................................27

Purpose of Feasibility Study..............................................................................................27

Types of Feasibility Study.................................................................................................28

LO2 Explain the importance of a feasibility study
Executive Summary
Feasibility Study
("(PDF) Feasibility Studies and Important Aspect of Project Management", 2021) defines
feasibility study as a technique for predicting the outcome of an investigation or
evaluation of a proposed system, as well as potential profit. Feasibility studies are crucial
in establishing the viability of a proposed project.

Feasibility Report
("Feasibility report Template - feasibility report Introduction - « Full » version - project
identification stage - Intro Page « Full « - IT-Enabled Projects - NPMS - Real Property - PSPC",

2021) says a feasibility report is a document that evaluates various solutions to a business

problem or opportunity, determining which are viable for additional research.

Purpose of Feasibility Study

A feasibility study may uncover innovative ideas that totally alter the scope of a project.
It's preferable to make these decisions ahead of time rather than rushing into a project
only to discover that it won't work. A feasibility study is usually advantageous to a
project since it provides us and other stakeholders with a clear picture of what is being
proposed.
Some purposes of conducting feasibility study are mentioned below:

 Enhances the focus of development team and seeks for new opportunities.
 Provides essential information for making a "go" or "no-go" assessment.
 Minimizes the number of business alternatives and establishes a convincing
argument for pursuing the project.
 Increases the success rate by considering several elements.
 Assists in project decision-making and illustrates arguments not to continue if the
project is due to fail.

Types of Feasibility Study

The five types or categories of feasibility study are as follows:

 Technical Feasibility: The technological resources accessible to the organization

are the emphasis of this assessment. It aids companies in determining whether
technical resources are sufficient for the job and whether the technical team is
capable of putting concepts into operational systems. The proposed system's
hardware, software, and other technical needs are also evaluated for technical
viability.

 Economic feasibility: Before allocating financial resources, companies use this

evaluation to examine the viability, cost, and advantages of a project. It also aids
decision-makers in determining the proposed project's positive economic
advantages to the company.
 Logical Feasibility: The purpose of a legal feasibility study is to determine if the
proposed plan or system is in violation of national or international legal standards.
It looks into if any component of the planned project is in violation of any
regulations, such as zoning rules, data protection legislation, or social media
regulations.
 Operational Feasibility: This evaluation entails doing research to evaluate if —
and to what extent — the project can meet the organization's needs. Operational
 feasibility studies also look at how a project plan meets the criteria specified
during the system development requirements analysis phase.
 Scheduling Feasibility: If a project is not completed within the specified time
range, it may be considered unsuccessful. Here, we may estimate how long it will
take to perform certain project tasks. The scheduling feasibility study plays a
significant part in completing the project on time.

References
https://www.professionalqa.com/iterative-model#:~:text=Iterative%20Model%20is
%20too%20a,the%20final%20system%20is%20complete.

https://www.javatpoint.com/software-engineering-agile-model

https://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm

https://www.researchgate.net/publication/317713058_Feasibility_Studies_and_Importan
t_Aspect_of_Project_Management