Higher Nationals

Internal verification of assessment decisions – BTEC (RQF)

INTERNAL VERIFICATION – ASSESSMENT DECISIONS

Programme title BITEC Higher National Diploma in Computing

Assessor Internal
Verifier
Unit 7 – Software Development Lifecycles
Unit(s)

Software Development Lifecycles Assignment

Assignment title

Student’s name

List which assessment criteria Pass Merit Distinction

the Assessor has awarded.

INTERNAL VERIFIER CHECKLIST

Do the assessment criteria awarded match

those shown in the assignment brief?
Y/N

Is the Pass/Merit/Distinction grade awarded

justified by the assessor’s comments on the Y/N
student work?

Has the work been assessed

accurately? Y/N

Is the feedback to the student:

Give details:
• Constructive?
Y/N
• Linked to relevant assessment criteria?
Y/N
• Identifying opportunities for improved
Y/N
performance?
• Agreeing actions?
Y/N

Does the assessment decision need

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 1
 amending? Y/N

Assessor signature Date

Internal Verifier signature Date

Programme Leader signature (if required)

Date

Confirm action completed

Remedial action taken

Give details:

Assessor signature Date

Internal Verifier
signature Date

Programme Leader
signature (if required) Date

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 2
Assignment Feedback Form
Student Name/ID

Unit Title Unit 7 – Software Development Lifecycles

Assignment Number Assessor

Date Received
Submission Date 1st submission

Date Received 2nd

Re-submission Date submission
Assessor Feedback:
LO1 Describe different software development lifecycles

Pass, Merit & DistinctionP1 P2 M1 D1

Descripts
LO2 Explain the importance of a feasibility study

Pass, Merit & Distinction P3 P4 M3 D2

Descripts

LO3 Undertake a software development lifecycle

Pass, Merit & DistinctionP5 P6 M3 M4 D3

Descripts
LO4 Discuss the suitability of software behavioural design techniques.

Pass, Merit & DistinctionP7 M5 M6 D4

Descripts

Grade: Assessor Signature: Date:

Resubmission Feedback:

Grade: Assessor Signature: Date:

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 3
Internal Verifier’s Comments:

Signature & Date:

* Please note that grade decisions are provisional. They are only confirmed once internal and external moderation has taken place and grades
decisions have been agreed at the assessment board.

Assignment Feedback

Formative Feedback: Assessor to Student

Action Plan

Summative feedback

Feedback: Student to Assessor

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 4
Assessor Date
signature

Student Date
signature

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 5
Pearson Higher Nationals in

Computing
Unit 7: Software Development Lifecycles
Assignment

General Guidelines

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 6
 1. A Cover page or title page – You should always attach a title page to your assignment. Use
previous page as your cover sheet and make sure all the details are accurately filled.
2. Attach this brief as the first section of your assignment.
3. All the assignments should be prepared using a word processing software.
4. All the assignments should be printed on A4 sized papers. Use single side printing.
5. Allow 1” for top, bottom, right margins and 1.25” for the left margin of each page.

Word Processing Rules

1. The font size should be 12 point, and should be in the style of Time New Roman.
2. Use 1.5 line spacing. Left justify all paragraphs.
3. Ensure that all the headings are consistent in terms of the font size and font style.
4. Use footer function in the word processor to insert Your Name, Subject, Assignment No,
and Page Number on each page. This is useful if individual sheets become detached for any
reason.
5. Use word processing application spell check and grammar check function to help editing your
assignment.

Important Points:

1. It is strictly prohibited to use textboxes to add texts in the assignments, except for the compulsory
information. eg: Figures, tables of comparison etc. Adding text boxes in the body except for the
before mentioned compulsory information will result in rejection of your work.
2. Carefully check the hand in date and the instructions given in the assignment. Late submissions
will not be accepted.
3. Ensure that you give yourself enough time to complete the assignment by the due date.
4. Excuses of any nature will not be accepted for failure to hand in the work on time.
5. You must take responsibility for managing your own time effectively.
6. If you are unable to hand in your assignment on time and have valid reasons such as illness, you
may apply (in writing) for an extension.
7. Failure to achieve at least PASS criteria will result in a REFERRAL grade.
8. Non-submission of work without valid reasons will lead to an automatic RE FERRAL. You will
then be asked to complete an alternative assignment.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 7
9. If you use other people’s work or ideas in your assignment, reference them properly using
HARVARD referencing system to avoid plagiarism. You have to provide both in-text citation
and a reference list.
10. If you are proven to be guilty of plagiarism or any academic misconduct, your grade could be
reduced to A REFERRAL or at worst you could be expelled from the course

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 8
Student Declaration

I hereby, declare that I know what plagiarism entails, namely to use another’s work and to present it as
my own without attributing the sources in the correct form. I further understand what it means to copy
another’s work.

1. I know that plagiarism is a punishable offence because it constitutes theft.

2. I understand the plagiarism and copying policy of Pearson UK.
3. I know what the consequences will be if I plagiarise or copy another’s work in any of the
assignments for this program.
4. I declare therefore that all work presented by me for every aspect of my program, will be my
own, and where I have made use of another’s work, I will attribute the source in the correct way.
5. I acknowledge that the attachment of this document signed or not, constitutes a binding
agreement between myself and Pearson UK.
6. I understand that my assignment will not be considered as submitted if this document is not
attached to the assignment.

Student’s Signature: Date:

(Provide E-mail ID) (Provide Submission Date)

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 9
Higher National Diploma in Business
Assignment Brief
Student Name /ID Number

Unit Number and Title Unit 7: Software Development Lifecycles

Academic Year 2022/23

Unit Tutor

Assignment Title Software Development Lifecycles Assignment

Issue Date

Submission Date

IV Name & Date

Submission format

This assignment consists of section A and section B.

The submission should be in the form of an individual report written in a concise, formal business
style using single spacing (refer to the assignment guidelines for more details). You are required to
make use of headings, paragraphs, and subsections as appropriate, and all work must be supported
with research and referenced using Harvard referencing system. Please provide in-text citation and a
list of references using Harvard referencing system.

The recommended word count is 4,500–5,000 words excluding annexures..

Minimum word count – 4,500
Maximum word count – 5,000

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 10
Unit Learning Outcomes:

By the end of this unit students will be able to:

LO1 Describe different software development lifecycles

LO2 Explain the importance of a feasibility study
LO3 Undertake a software development lifecycle
LO4 Discuss the suitability of software behavioral design techniques.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 11
Assignment Brief and Guidance:

Section A

Case 1: In the wildlife ministry of Sri Lanka intend to develop a wildlife safari system which links
all the details of sanctuaries, wetland, and national parks across Sri Lanka. Through this the
government wants to track all the details of safari drivers and to count local and foreign visitors
entering these premises. The IT department of wildlife ministry have little experience on
developing this kind of system and they have two years to complete this project.

Case 2: “ChangeU” salon needs to have a system to track their bookings and they expect to
provide better customer service through the system. This is not incredibly challenging, and the
development team also has some early experience of this kind of a project. And the main
requirement of the client is to get a high-quality product without considering the budget and time
constraints.

Activity 1

Describe two sequential models and two iterative models you have learned which can be used to
design the systems explained in the 2 given cases. Explain how the risk is managed in each
software lifecycle model identified. Pick one case out of two and select the most suitable SDLC
model along with a discussion elaborating the reasons to select the particular SDLC model.

Which system out of the given two is most suitable to be developed using the waterfall model?
Assess the merits of applying the waterfall model to the system chosen by you.

Section B

Assume yourself as a system analyst assign to analyse and design a software system for an

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 12
organization of your choice. Investigate the business and system requirements using appropriate
tools/ techniques and develop the system design with the findings.

Activity 2

Explain and discuss the purpose and the components of the feasibility report that you have to
develop in order to check the feasibility of the chosen system. Assess the impact of different
feasibility criteria included in your report to investigate the software system.

Suggest , describe and compare two technical solutions for the proposed system and pick the most
suitable one with the justification for the selection.

Activity 3

Undertake the system investigation to identify business and system requirements using appropriate
investigation tools/ techniques and develop the software system specification for the chosen
system.

Evaluate the effectiveness of the system investigation process chosen by you to fulfil the
requirements of the users and analyse the effectiveness of the SDLC followed in order to trace the
system requirements. Discuss two approaches that can be used to improve the quality of the
system in the future.

Activity 4

Analyse the software behavioural tools and techniques that could be used for the proposed system
and discuss suing examples, the most suitable behavioural techniques that could be used for your
system.

Differentiate the finite state machine (FSM) and extended FSM providing an application for each .
Justify how the data driven software can improve the reliability and the effectiveness of the
software system proposed by you.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 13
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 14
Grading Rubric

Grading Criteria Achieved Feedback

LO1 Describe different software development lifecycles

P1 Describe two iterative and two sequential software

lifecycle models.
P2 Explain how risk is managed in software lifecycle
models.
M1 Discuss using an example, why a particular lifecycle
model is selected for a development environment.
D1 Assess the merits of applying the Waterfall lifecycle
model to a large software development project.

LO2 Explain the importance of a feasibility study

P3 Explain the purpose of a feasibility report.

P4 Describe how technical solutions can be compared.

M2 Discuss the components of a feasibility report.

Tharushi Kavishka Software Development Lifecycles Assignment 03 Page

| 15
D2 Assess the impact of different feasibility criteria on a
software investigation.

LO3 Undertake a software development lifecycle

P5 Undertake a software investigation to meet a business need.

P6 Use appropriate software analysis tools/techniques to carry

out a software investigation and create supporting
documentation.

M3 Analyse how software requirements can be traced

throughout the software lifecycle.

M4 Discuss two approaches to improving software quality

D3 Evaluate the process of undertaking a systems investigation

with regard to its effectiveness in improving a software
quality.

LO4 Discuss the suitability of software behavioural design techniques

Tharushi Kavishka Software Development Lifecycles Assignment 03 Page

| 16
P7 Discuss, using examples, the suitability of software
behavioural design techniques

M5 Analyze a range of software behavioural tools

and techniques.

M6 Differentiate between a finite state machine

(FSM) and an extended FSM, providing an
application of use for both

D4 Present justifications of how data-driven software can

improve the reliability and effectiveness of
software

Tharushi Kavishka Software Development Lifecycles Assignment 03 Page

| 17
Table of Contents
Activity 01……………………………………………………………………………………23
Iterative Models: ……………………………………………………………………………..24
Agile Model: …………………………………………………………………………………24
1. Iterative Development: …………………………………………………………………..24
2. Customer
Collaboration…………………………………………………………………..24
3. Adaptability to Change: ………………………………………………………………….24
4. Cross-functional Team
Collaboration…………………………………………………….24
5. Continuous Improvement: ……………………………………………………………….25
6. Timeboxing and Time-to-Market: ……………………………………………………….25
7. Risk Management………………………………………………………………………...25
Big Bang Model………………………………………………………………………………
26
Spiral Model………………………………………………………………………………….26
Sequential Models……………………………………………………………………………27
V- Shaped Model……………………………………………………………………………..28
 Agile Model………………………………………………………………………………29
 Scrum Model: ……………………………………………………………………………29
1. Flexibility………………………………………………………………………………...30
2. Continuous Improvement………………………………………………………………...30
3. Collaboration and Communication: ……………………………………………………..30
4. Early Value Delivery……………………………………………………………………..30
1. Well-Defined Requirements: …………………………………………………………….31
2. Predictability………………………………………………………………………..........31
3. ..Reduced Customer Involvement: ………………………………………………………31
4. Time and Budget Constraints…………………………………………………………….31
Section
B……………………………………………………………………………………...33
 Interviews: ……………………………………………………………………………….34
 Surveys: ………………………………………………………………………………….34
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 18
 Document Analysis:
……………………………………………………………………...34
 Observation:
……………………………………………………………………………...34
 Prototyping……………………………………………………………………………….34
1. Requirement Analysis:
…………………………………………………………………...35
2. System Architecture Design………………………………………………………….…..35
3. Data Design……………………………………………………………………….……...35
4. User Interface Design: …………………………………………………………………...35
5. Algorithm and Functionality Design……………………………………………………..35
6. System Integration
Design…………………………………………………………………………….35
7. System Testing and Quality………………………………………………………………
35
8. Documentation: Prepare detailed…………………………………………………………
35
1. Waterfall
Model…………………………………………………………………………..37
2. Agile Model………………………………………………………………………………37
3. Spiral Model: …………………………………………………………………………….37
4. V-Shaped Model:
………………………………………………………………………...37
1. Flexibility and Adaptability……………………………………………………………....39
2. Early and Continuous User
Empowerment………………………………………….........39
3. Time-to-Market: …………………………………………………………………………39
4. Collaboration and Team Empowerment………………………………………………….39
5. Continuous Improvement: ……………………………………………………………….40
6. Project Complexity……………………………………………………………………….40
7. Customer Requirements and Expectations……………………………………………….40
8. Available Resources and Expertise: ……………………………………………………..40

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 19
9. Time Constraints:
………………………………………………………………………...40
10. Risk Management…………………………………………………...................................40
1. Documentation Emphasis: ……………………………………………………………….42
2. Easy Project Management:
……………………………………………………………….42
3. Client Involvement: ……………………………………………………………………...42
4. Predictability and Stability……………………………………………………………..…
42
5. Regulatory Compliance: …………………………………………………………………42
Activity 2………………………………………………………………………………….
….43
1. Determine Project Viability………………………………………………………………43
2. Assess Technical Feasibility: ……………………………………………………….……
43
3. Evaluate Economic Feasibility……………………………………………………...……43
4. Examine Operational Feasibility: …………………………………………………..……43
5. Consider Schedule Feasibility: ………………………………………………………..…43
6. Address Legal and Ethical Considerations…………………………………………….…43
Describe how technical solutions can be compared…………………………………………44
Functional Requirement: ……………………………………………………………………44
Scalability and Performance…………………………………………………………………44
Integration Capabilities………………………………………………………………………44
Customization and Flexibility: ………………………………………………………………44
Security and Compliance……………………………………………………………………………..44
Cost and Budget………………………………………………………………………………
44
Technical Expertise and Support:
…………………………………………………………….44
Future Proofing and Upgradability………………………………………………………..….44
Discuss the Components of a feasibility report………………………………………………46

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 20
1. Executive Summary: …………………………………………………………………..…
46
2. Introduction: ………………………………………………………………………..……46
3. Project Description: ……………………………………………………………...………46
4. Methodology……………………………………………………………………………..46
5. Technical Feasibility: ……………………………………………………………………46
6. Economic Feasibility: ………………………………………………………………..…..46
7. Operational Feasibility…………………………………………………………………...46
8. Legal and Ethical Considerations……………………………………………………..…47
9. Risk Assessment: ………………………………………………………………..………47
10. Conclusion and Recommendations………………………………………………………47
11. Appendices: …………………………………………………………………………...…47
1. Technical
Feasibility……………………………………………………………………...48
2. Economic Feasibility……………………...……………………………………………...48
3. Operational Feasibility…………………………………………………………………...48
4. Schedule Feasibility…………………………………………………………………..….48
5. Legal and Ethical Feasibility……………………………………………………………..48
Activity 3…………………………………………………………………………………..…
50
1. Identify the Business Need…………………………………………………………….…50
2. Gather Requirements: ……………………………………………………………………50
3. Analyse Existing Systems and Processes…………………………………………………
50
4. Define Project Scope:
…………………………………………………………………….50
5. Research and Evaluate Solutions: ……………………………………………………..…
50
6. Cost-Benefit Analysis…………………………………………………………….………50
7. Technical Assessment: …………………………………………………………..
……….50
8. Risk Analysis: ……………………………………………………………………………
51
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 21
9. Stakeholder Alignment: ……………………………………………….…………………51
10. Develop a Proposal: ………………………………………………………….……..……51
1. Interviews: …………………………………………………………………………….…52
2. Surveys: ………………………………………………………………………………….52
3. Workshops……………………………………………………………………………..…52
4. Observation: Directly………………………………………………………………….…52
5. Prototyping: ……………………………………………………………………………...52
6. Data Analysis…………………………………………………………………………….52
7. Requirements Gathering…………………………………………………………………52
8. SWOT Analysis……………………………………………………………………….…52
9. Cost-Benefit Analysis……………………………………………………………………53
10. Documentation………………………………………………………………………...…53
1. Requirements Elicitation…………………………………………………………………54
2. Requirements Documentation: ………………………………………………………..…54
3. Requirements Management Tools: ………………………………………………………54
4. Design and Development:
………………………………………………………………..54
5. Implementation and
Coding……………………………………………………………....54
6. Testing and Validation……………………………………………………………………
54
7. Change Management: ……………………………………………………………………55
8. Verification and Validation………………………………………………………………55
1. Test-Driven Development (TDD)………………………………………………………..56
2. Continuous Integration and Continuous Delivery (CI/CD)……………………………...56
1. Identification of Requirements and Pain Points……………………………………….....57
2. Analysis of Existing Processes and Workflows………………………………….………57
3. Identification of Functional and Non-Functional Requirements…………………………57
4. and Collaboration Stakeholder Engagement………………………………………….….57
5. Documentation and Communication………………………………………………….….57
Activity 4…………………………………………………………………………………..…
59

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 22
1. Complexity of System Behavior……………………………………………………….…
59
2. Requirements Clarity: ……………………………………………………………………59
3. User-Centric Design…………………………………………………………………...…59
4. Collaboration and Communication: …………………………………………………...…
59
5. Dynamic and Interactive Systems……………………………………………………...…
59
6. Iterative and Agile Development
Approaches…………………………………………....60
1. Requirement Analysis: ………………………………………………………….……..…
61
2. Identifying Deficiencies: …………………………………………………………………
61
3. Gap Analysis:
…………………………………………………………………………….61
4. Process Optimization: ……………………………………………………………………61
5. Risk Identification and Mitigation……………………………………………………..…
61
6. Stakeholder Engagement……………………………………………………………..…..62
1. Use Case Diagrams: ……………………………………………………………..………63
2. Sequence Diagrams: ………………………………………………………………..……63
3. State Diagrams: ………………………………………………………………………..…
63
4. User Story Mapping:
……………………………………………………………………..63
1. Finite State Machine (FSM) Application: …………………………………………….…64
2. Extended Finite State Machine (EFSM)
………………………………………………….64
3. Behavior Modeling with Activity Diagrams……………………………………………..64
4. User Story Mapping: …………………………………………………………………..…
64
5. Event-Driven Design: ……………………………………………………………………64
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 23
Finite State Machine (FSM) Application: ……………………………………………………
65
Transition: User retries login…………………………………………………………………66
1. Accurate Decision-making: ………………………………………………………...……67
2. Personalized User Experience……………………………………………………………67
3. Predictive Analytics: ………………………………………………………………….…67
4. Continuous Improvement: …………………………………………………………….…67
5. Enhanced Automation: ………………………………………………………………………………67
Reference………………………………………………………………….......................................................69

Introduction
The Software Development Life Cycle (SDLC) is a systematic approach used to design,
develop, and deploy software systems. It encompasses a set of phases, activities, and
processes that guide the software development process from conception to completion. In
this context, we will discuss the suitability of different SDLC models for two distinct
projects in the wildlife ministry of Sri Lanka and "ChangeU" salon.

Waterfall, agile, and iterative models can be presented as different SDLC models that offer
different approaches to software development. The selection of an SDLC model depends on
Factors such as project requirements, team experience, project complexity, time constraints,
and budget considerations.

In the following sections, we will analyze and compare various SDLC models to determine
the most suitable model for each case. The merits of applying the selected SDLC model
will be assessed, considering the unique characteristics and requirements of each project.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 24
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 25
Activity 01
Describe two sequential models and two iterative models you have learned which can
be used to design the systems explained in the 2 given cases. Explain how the risk is
managed in each software lifecycle model identified.

Iterative Models:

Agile Model: The Agile model is an iterative and incremental approach to software
development. It emphasizes flexibility, collaboration, and adaptability to change. In
Agile, the development process is divided into small iterations called sprints, typically
lasting from one to four weeks. Each sprint involves a complete cycle of planning,
requirements analysis, design, development, testing, and deployment. The Agile
model promotes continuous feedback and customer involvement throughout the
development process, allowing for adjustments and refinements based on changing
requirements and priorities.

1. Iterative Development: The Agile model breaks down the development process into
iterations or sprints, this ranges from one to four weeks. Each iteration includes a
set of planned activities. That is, it can be termed as requirements gathering,
planning, development, testing, and review. The development team focuses on
delivering a working product incrementally at the end of each iteration.
2. Customer Collaboration: Throughout the Agile development process, there is a
strong focus on engaging the customer or end user. The customer is actively
engaged, providing continuous feedback, clarifying requirements, and
participating in regular review sessions. This collaboration ensures that the
software meets the customer's expectations and enables the team to make
necessary adjustments throughout the development lifecycle.
3. Adaptability to Change: Agile acknowledges that requirements evolve and change
over time. It embraces changes and allows for flexibility in incorporating new
features, enhancements, or adjustments to meet the evolving needs of the
customer or market. By embracing change rather than resisting it, the Agile
model enables teams to respond quickly to new information and make necessary
modifications to deliver a better end product.
4. Cross-functional Team Collaboration: Agile encourages close collaboration among
team members with diverse skill sets, including developers, testers, designers,
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 26
 and stakeholders. The team works together to plan, prioritize, and execute tasks,
fostering effective communication, knowledge sharing, and problem-solving.
This collaboration ensures that everyone has a shared understanding of the
project goals and can contribute their expertise to deliver a successful product.
5. Continuous Improvement: The Agile model promotes continuous improvement
through retrospectives at the end of each iteration. The team reflects on their
work, identifies areas for improvement, and implements changes to enhance
their processes, productivity, and quality. This iterative feedback loop ensures
that the team learns from their experiences and consistently improves their
development practices.
6. Timeboxing and Time-to-Market: Agile employs Timeboxing techniques, where
specific time frames are allocated for each iteration. This time constraint helps
in managing scope, prioritizing work, and ensuring regular delivery of working
software. The Agile model's focus on incremental delivery enables faster time-
to-market, allowing the customer to start realizing value earlier and providing
opportunities for early feedback and validation.
7. Risk Management: Risk management is an integral part of the agile development
process. . Risks are identified, assessed, and addressed at various stages,
ensuring that potential issues are identified early and mitigated effectively. The
iterative nature of Agile allows for frequent risk assessments and course
corrections, minimizing the impact of risks on the project's success

Figure 1 Agile

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 27
 Big Bang Model: An informal and unstructured approach to software development without
defined processes and documentation can be called a Big Bang model. In this model,
development begins instantly with coding and implementation, without extensive planning
or analysis. While it allows for rapid development and quick time-to-market, the Big Bang
model carries high risks due to the absence of comprehensive requirements gathering and
design. The limited control and scalability of the model make it more reasonable for small
projects or prototypes rather than larger, complicated attempts. Stakeholder involvement
and feedback may be limited, and adaptability to changing provisions is possible but needs
careful management. Overall, the Big Bang model is considered a high-risk strategy that is
best suited for projects with time limitations and a tolerance for uncertainty, where the
speed of delivery outweighs the need for extensive planning and control.

Figure 2 big bang

Spiral Model: This Spiral model combines elements of both sequential and iterative
approaches. It focuses on risk management and involves iterative cycles, each representing
a phase of the development lifecycle. The spiral model can be divided into four main
activities namely planning, risk analysis, engineering, and evaluation. Each cycle begins
with risk identification and assessment, followed by prototyping, development, and testing.
Each cycle starts with risk identification and assessment, followed by prototyping,
development, and testing. The Spiral model emphasizes continuous risk management and

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 28
allows for early identification and mitigation of potential issues, making it particularly
suitable for complex and high-risk projects.

Figure 3 Spiral Model

Sequential Models

• Waterfall Model: The Waterfall model follows a traditional and linear sequential
approach, where each phase is completed before moving on to the next. Risk
management in the Waterfall model typically occurs during the early stages of the
project. Identifying, analyzing, and mitigating risks is done during the preliminary
design and requirements gathering phase. The emphasis is on thorough upfront
analysis to minimize risks surfacing in later stages.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 29
Figure 4 Waterfall Model

V-Shaped Model

An extension of the waterfall model is a V-shaped model that emphasizes testing at

each stage. It follows a sequential approach comparable to Waterfall but places a
strong passion on verification and validation. Risk management in the V-shaped
model is intertwined with testing activities. Risks are specified during corresponding
development phases, and confirmation and testing activities are designed to address
those risks. Early defect detection and solution during sampling help manage potential
risks effectively.

These four software lifecycle models offer different approaches to software development,
each with its powers and deficiencies. The choice of model depends on factors such as
project conditions, the level of flexibility needed, customer involvement, risk surveillance
considerations, and the nature of the software being developed.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 30
Two iterative models that can be used are the agile model and the Scrum Model.

• Agile Model: An iterative and incremental approach that promotes flexibility and
adaptability is known as the agile model. It breaks the project into short iterations
or sprints, allowing for continuous feedback, collaboration, and the ability to
respond to changing needs. Risk management in the agile model is an ongoing
process. Risks are constantly specified and assessed throughout the expansion
iteration. The Agile team collaboratively assesses risk, structure comfort
strategies, and adapts to risk promptly, ensuring that chances are addressed on
time.
• Scrum Model: A specific agile framework for managing and developing complex
projects is called Scrum. It follows an iterative approach with short, time-boxed
iterations called sprints. Collaboration, collaboration, and transparency are
emphasized by this scrum model. It consists of specific roles (Product Owner,
Scrum Master, and Development Team), events (Sprint Planning, Daily Stand Up,
Sprint Review, and Sprint Retrospective), and artifacts (Product Backlog, Sprint
Backlog, and Increments). Scrum promotes frequent testing and adaptation,
ordinary contact within the team, and successive delivery of value to the buyer.

Both the Agile model and the Scrum model share similar principles and values, focusing
on iterative, customer collaboration, adaptability to transform, and continuous
improvement. They provide a framework for managing complex projects, fostering
contact and flexibility in providing high-quality software. These iterative models are

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 31
particularly for projects where requirements may evolve, stakeholders' involvement is
important, and the capacity to respond fast to change is esteemed.

Pick one case out of the two and select the most suitable SDLC model for that case.
Provide a discussion elaborating the reasons for selecting the particular SDLC
model.

Reasons for selecting the agile model for "ChangeU" salon:

1. Flexibility: The Agile model offers flexibility and adaptability, allowing for
differences and adjustments to conditions throughout the evolution process.
This is valuable for a salon that may need to refine and enhance its client
service powers based on ongoing feedback and expanding needs.
2. Continuous Improvement: Agile's iterative approach enables frequent delivery of
working software, allowing the salon to constantly improve its strategy based
on client feedback. This aligns with the client's expectation of supplying a high-
quality creation without strict time regulations.
3. Collaboration and Communication: Agile promotes collaboration and close
interaction between the evolution group and the customer. This ensures that the
system meets the customer's expectations and facilitates sufficient
communication for clarifying requirements and resolving problems promptly.
4. Early Value Delivery: Agile's iterative nature enables the delivery of working
elements in each iteration, allowing the salon to start profiting from the
system's abilities early on. This can lead to faster ROI and quicker completion
of the desired client service improvements.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 32
Assessing the merits of applying the waterfall model to the chosen system, it is
important to note that the waterfall model may not be the most suitable choice for
the "ChangeU" salon.

1. Well-Defined Requirements: If the salon's prerequisites are well-defined and

unlikely to modify greatly, the waterfall model's structured and sequential
strategy can ensure a systematic growth.
2. Predictability and Documentation: The waterfall model predictsability as each
phase is finished before shifting to the next. This ensures that the project plan
and deliverables are well-documented, promoting better understanding,
traceability, and project management. For the salon, having a clear and
documented plan may be profitable, especially if there is a need to comply with
specific regulations or if there are strict quality management requirements.
3. Reduced Customer Involvement: In some cases, clients may prefer less
involvement in the development method, particularly when the duration
conditions are well-defined. The waterfall model allows clients to supply inputs
during the initial requirements-gathering phase, and then they can focus on
reviewing the final product. This can be beneficial for the salon if they have
limited resources or if they prefer a hands-off approach to the development
method.
4. Time and Budget Constraints: While the "ChangeU" salon case emphasizes
delivering a high-quality product without considering strict time and budget
regulations, the waterfall model can still be helpful in terms of supply and
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 33
 budget. With well-defined conditions and a sequential method, the waterfall
model enables upfront planning and analysis, which can help organize
resources more efficiently.

However, it's important to consider the potential limits of the waterfall model for the
"ChangeU" salon system. The waterfall model assumes that provisions are stable and
improbable to change awfully throughout the development method. If there is a need for
flexibility, frequent client feedback, or developing provisions, an iterative model like
Agile may be more sensible.

In conclusion, while the waterfall model can offer predictability, documentation, and
reduced client involvement, its sequential nature and limited ability to accommodate
evolutions may not be the best fit for the "ChangeU" salon system. Given the case's
emphasis on delivering high-quality innovation and the potential settlements of client
feedback and continuous improvement, an iterative model like Agile would be a more
suitable selection.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 34
Section B.

Assume yourself as a system analyst assigned to analyze and design a software system
for an organization of your choice. What organization would you choose for this task?

As a system analyst, you have the liberty to choose any organization for this task. Deem
selection is an organization that attracts you or one that you have some knowledge or
experience with. It could be a business, non-profit association, educational society, or any
other type of organization that could profit from a software system.

For this explanation, let's assume that the chosen organization is a retail company that
employs both physical stocks and an online e-commerce platform. This association aims to
enhance its client knowledge by evolving a comprehensive retail management system that
integrates both offline and online sales channels, inventory management, and client
connection management (CRM) functionalities.

Retail requires efficient inventory management, facilitated sales processes, accurate

tracking of client interchanges, and seamless integration between physical and online
stores. Planning a software system that can cater to these specific conditions would greatly
benefit the association in terms of operational efficiency, client satisfaction, and business
growth.

As a system analyst, you would conduct a thorough analysis of the association's current
methods, pain points, and future goals. You would work closely with stakeholders,

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 35
comprising store managers, sales staff, IT teams, and executives, to gather their insights
and provisions.

By selecting a retail association as the focus of your system analysis and design, you can
analyze various aspects such as point-of-sale systems, inventory management, client
loyalty programs, online shopping outlets, and data analytics for business intellect. This
would allow you to create a comprehensive and tailored software system that addresses the
association's specific needs and aligns with its long-term strategic purposes.

Investigate the business and system requirements for the chosen organization. Which
tools or techniques would you use to gather and analyze these requirements?

To investigate the business and system requirements, you can use various tools and
techniques. Here are a few commonly used ones:

 Interviews: Conduct discussions with stakeholders, including managers, workers,

and end-users, to gather their viewpoints on the current system and their
requirements for the new software system.
 Surveys: develop surveys to compile feedback and statements from a broader range
of stakeholders. Interviews can help gather quantitative data and understandings
that can grant to understanding of the association's provisions.
 Document Analysis: Study living documentation, such as business method documents,
user manuals, and system specifications, to gain a deeper understanding of the
association's procedures and identify areas for modification.
 Observation: attend the workflows firsthand to identify pain points, inefficiencies,
and areas where a software system could add value.
 Prototyping: Evolve prototypes or mockups of the software system to gather early
feedback from stakeholders and validate provisions before proceeding with the full
expansion.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 36
Develop the system design based on the findings from the business and system
requirements. How would you go about designing the software system for the chosen
organization?

To design the software system, you would typically follow a systematic approach that
involves several steps:

1. Requirement Analysis: Investigate the gathered business and system provisions in the
element to specify the core functionalities, user roles, data structures, and any
specific technical provisions.
2. System Architecture Design: Specify the overall configuration and ingredients of the
software system, comprising the user interface, database, backend components, and
integration points with external systems if relevant.
3. Data Design: Schedule the database schema, comprising tables, connections, and
constraints, to ensure efficient storage and recovery of data based on the system
provisions.
4. User Interface Design: Develop wireframes or mockups of the user interface to
visually portray how users will interact with the system. Evaluate usability
principles, user feedback, and the association's branding approaches during the
method procedure.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 37
 5. Algorithm and Functionality Design: Specify the algorithms and logic needed to
execute the strategy's core functionalities, taking into statement interpretation,
safety, and scalability facets.
6. System Integration Design: If the software system needs to interact with different
existing systems or APIs, structure the integration facts and protocols to secure
seamless contact and data conversation.
7. System Testing and Quality Assurance: Plan for extensive testing methods, comprising
unit testing, integration testing, and system testing, to ensure the software system
processes correctly and meets the determined provisions.
8. Documentation: Compose detailed system composition documents that outline the
architecture, data configurations, user interface specifications, and any other
relevant technological data. These documents serve as a consideration for creators
during the commission phase and deliver a footing for future system enhancements
and supervision.
By following this organized method procedure, you can ensure that the software system for
the chosen association is well-structured, aligned with provisions, and scheduled to meet
the association's specific needs.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 38
Explain how risk is managed in software lifecycle models

1. Waterfall Model: In the Waterfall model, risk management primarily focuses on

upfront planning and danger designation. Dangers are identified during the initial
requirements-gathering stage and are documented as part of the project plan. Risk
analysis involves assessing the possibility and effect of each determined risk.
Comfort techniques are then devised to address the risks, and contingency plans are
prepared to manage possible cases that may arise. Risk management in the
Waterfall model is commonly carried out during the planning and design phases,
with limited flexibility for differences once the expansion method commences.
2. Agile Model: In the Agile model, risk management is incorporated throughout the
iterative expansion methods. The Agile method underscores constant feedback and
adaptation, allowing for early risk identification and mitigation. Risk management
exercises in Agile comprise regular risk assessments during sprint planning
meetings, where probable risks are determined and prioritized. Agile teams work
collaboratively to address risks by executing risk comfort methods, such as
adjusting emphases, breaking down complex tasks, or completing focused testing.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 39
 The Agile model encourages systematic client involvement, enabling stakeholders
to deliver feedback and address dangers early in the expansion method.
3. Spiral Model: The Spiral model integrates risk management as a core component.
Each cycle of the Spiral model begins with risk analysis and assessment. Risks are
determined, prioritized, and estimated in terms of their potential consequence on the
project. The Spiral model facilitates risk-driven expansion, with iterative cycles
focusing on reducing high-priority risks. Prototyping and testing workouts in each
process help validate and address determined risks. The risk management method in
the Spiral model is iterative, allowing for constant monitoring, evaluation, and
adjustment of risk comfort techniques.
4. V-Shaped Model: In the V-shaped model, risk management is closely tied to the
testing workouts conducted in each phase. The testing phases in the V-shaped
model aim to verify and validate the software against the specified provisions. The
identification of dangers transpires during the corresponding expansion phases, and
testing workouts priority on mitigating those dangers. For example, system testing
aims to specify and rectify probable issues related to system provisions, decreasing
the risk of not meeting the intended functionality. By performing thorough testing
at each phase, the V-shaped model aims to determine and address risks early in the
development lifecycle. Risk management in software lifecycle models affects
proactive designation, analysis, and mitigation of risks. It may include methods
such as risk avoidance, risk transfer, risk reduction, and risk acceptance. The
specific approach to risk management depends on the chosen software lifecycle
model and the association's risk management methods.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 40
Discuss using an example, why a particular lifecycle model is selected for a
development environment.

In this method, the startup aims to create a feature-rich mobile application that delivers a
distinctive benefit to its users. The expansion group consists of skilled creators and
architects, and the project has a tight timeline of three months.

Considering these factors, the agile model would be a suitable choice for the development
environment. Here's why:

1. Flexibility and Adaptability: The Agile model underscores flexibility and adaptability,
which is critical for startups that perform in a dynamic and rapidly developing
demand. It allows for iterative expansion and constant feedback, encouraging the
expansion group to respond to changing provisions, user feedback, and demand
trends. This flexibility is especially advantageous for startups that often face
apprehensions and need to iterate their creation fast.
2. Early and Continuous User Involvement: Startups typically aim to construct
developments that cater to specific user requires and intentions. The Agile model
motivates frequent and direct user involvement throughout the expansion method. It
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 41
 enables the startup to gather early user feedback, validate assumptions, and make
necessary adjustments to meet user expectations. By incorporating user feedback
early on, the expansion group can ensure that the final outcome aligns with user
provisions, improving it chances of success.
3. Time-to-Market: Startups are often employed in highly competitive environments
where time-to-market is critical. The Agile model allows for accumulative
expansion and delivery of working software at the end of each iteration. This means
that the startup can release a minimum viable outcome (MVP) or key
characteristics sooner, authorizing them to enter the demand faster and gain user
traction. This early demand entry delivers possibilities for user investment,
feedback exhibition, and further development enhancements.
4. Collaboration and Team Empowerment: Agile promotes collective teamwork and self-
organizing expansion groups. For startups with a small group, this collective
method fosters better contact, knowledge sharing, and synergy among group
members. It empowers creators, architects, and stakeholders to work closely
together, make convenient conclusions, and adapt to developing provisions
efficiently.
5. Continuous Improvement: Startups often have a culture of experimentation and
constant advancement. The Agile model aligns well with this attitude by delivering
typical possibilities for retrospection and procedure improvement. The expansion
group can regularly evaluate their performance, determine areas for advancement,
and implement essential changes to enhance their expansion exercises and
productivity.
6. Project Complexity: The complexity of the project is a critical deliberation when
choosing a lifecycle model. If the project involves complicated provisions, intricate
interdependencies, or a high level of risk, a sequential model like the Waterfall or
V-shaped model may be more reasonable. These models provide a structured
strategy and allow for detailed planning and documentation, which can help
manage complicated schemes.
7. Customer Requirements and Expectations: The specific requirements and anticipations
of the customer or client can influence the choice of a lifecycle model. Some
customers may have a clear and stable set of requirements, making a sequential
model like Waterfall suitable. On the other hand, customers who importance early
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 42
 and systematic deliverables, alliance, and flexibility may prefer an iterative model
like Agile or the Spiral model.
8. Available Resources and Expertise: The availability of resources and expertise within
the growth group can impact the choice of a lifecycle model. If the group has a high
level of knowledge and expertise in a particular model, it may be more efficient to
employ that model. Additionally, the availability of tools, technologies, and
frameworks that align with a specific model can also affect the choice.
9. Time Constraints: The project timeline is an important factor in selecting a lifecycle
model. Some models, like the Waterfall model, are more suitable for projects with
limited deadlines and limited flexibility for differences. On the other hand, iterative
models like Agile allow for accumulative growth and shorter feedback cycles,
which can be helpful when there are time restrictions or a need for quicker
iterations.
10. Risk Management Approach: The strategy for risk management can vary across
lifecycle models. For example, the Spiral model underscores risk examination and
comfort in each iteration, making it reasonable for projects with high risks. On the
other hand, Agile promotes constant risk assessment and adaption, allowing for
early identification and comfort of risks. The risk management method and the
project's risk profile can impact the selection of a lifecycle model.

In summary, choosing a lifecycle model for a growth environment instructs evaluating

facets such as project complexity, client conditions, available resources, time constraints,
and risk management approach. Each model has its strengths and weaknesses, and the
choice depends on the specific factors of the project and the needs of the stakeholders
implicated.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 43
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 44
Assess the merits of applying the Waterfall lifecycle model to a large software
development project.

1. Documentation Emphasis: The Waterfall model places significant priority on

documentation at each phase. This documentation helps in conserving a
comprehensive record of project prerequisites, strategy judgments, and testing
methods. It aids in knowledge transfer, enhances contact, and facilitates easier
supervision and fortune enhancements.
2. Easy Project Management: The linear nature of the Waterfall model makes it easier to
organize and track improvement, as each phase has distinct access and exit
measures. This allows project managers to have better control over the growth
method and facilitates efficient resource allotment.
3. Client Involvement: The Waterfall model commonly implicates customer or
stakeholder involvement during the provisions conference and design phases. This
ensures that the customer's expectations and provisions are apprehended accurately
upfront, reducing the risk of misunderstandings and scope creep later in the project.
4. Predictability and Stability: The Waterfall model is known for its predictability and
stability. Since each phase is finished before pushing to the next, it decreases the
likelihood of major changes or wonders during later stages of growth. This makes it
reasonable for projects with well-defined prerequisites and where differences are
anticipated to be minimal.
5. Regulatory Compliance: The Waterfall model is often favored in projects that need
strict adherence to regulatory standards and submission. The sequential nature of
the model allows for a comprehensive and methodical strategy to meet regulatory
provisions and ensures proper documentation of methods and judgments.

Despite this excellence, it's crucial to concede that the Waterfall model also has some
limitations. It is less adaptable to differences in provisions, lacks flexibility for feedback
and iterations, and can lead to longer growth processes. It may not be reasonable for
projects where provisions are explosive, customer involvement is important throughout the
growth method, or where a more iterative and collaborative approach is desired Ultimately,
the judgment to apply the Waterfall model to a large software development project should
consider the project's specific characteristics, such as stability of provisions, regulatory
submission needs, customer involvement expectations, and the project team's knowledge
and comfort with the model.
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 45
Activity 2

Explain and discuss the purpose and the components of the feasibility report that you
have to develop in order to check the feasibility of the chosen system. Assess the
impact of different feasibility criteria included in your report to investigate the
software system
1. Determine Project Viability: The feasibility statement helps discern whether the
proposed project is achievable in terms of technological, financial, operational, and
legal aspects. It considers the project's probability of meeting its objectives, addresses
determined needs, and delivers value to the association or stakeholders.
2. Assess Technical Feasibility: The statement of the technology and capacities crucial to
execute the proposed project. It assesses facets such as the availability of technology,
infrastructure, skills, and resources needed for prosperous project execution.
3. Evaluate Economic Feasibility: The economic feasibility analysis focuses on assessing
the monetary viability and cost-effectiveness of the project. It considers facets such as
growth expenses, operational expenses, and the possibility of return on investment,
and the project's contribution to the association's monetary goals.
4. Examine Operational Feasibility: The assesses the expedience and functional feasibility
of the proposed project. It considers how the project aligns with the association's
existing methods, resources, and capacities, and evaluates probable challenges or
effects on functions.
5. Consider Schedule Feasibility: The feasibility statement examines the project timeline
and plan feasibility. It investigates the proposed project's growth, commission, and
delivery timeframes to ensure they align with the association's prerequisites and
regulations.
6. Address Legal and Ethical Considerations: The statement determines any lawful or ethical
importance associated with the project. It evaluates regulatory compliance,
intellectual property rights, privacy troubles, and ethical standards, providing that the
project can be executed within the borders of the law and ethical policies.
By performing a feasibility analysis and readying a feasibility, stakeholders gain a
comprehensive understanding of the project's potential dangers, advantages, and restrictions.
This enables them to make notified conclusions about whether to proceed with the project,
modify the scope or approach, allocate resources actually, and manage anticipations.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 46
Describe how technical solutions can be compared.

Functional Requirements: Assess how well each explanation meets the operating prerequisites
of the project. Consider whether the solutions provide the crucial elements and abilities to
fulfill the desired objectives and user needs.

Scalability and Performance: Assess how the explanations handle scalability and performance
prerequisites. Differentiate if they can handle expected user loads, data volumes, and
transaction rates. Consider facets like reaction time, throughput, and the ability to scale up or
down as needed.

Integration Capabilities: Examine how readily the explanations can integrate with existing
systems, databases, and third-party applications. Evaluate their compatibility with industry
standards, APIs, and data configurations. Assess the effort and complexity required to attain
seamless integration.

Customization and Flexibility: Differentiate the level of customization and flexibility each
explanation offers. Assess whether they can be tailored to fit specific business prerequisites
and methods. Evaluate the ease of configuring, extending, or modifying the explanation to
accommodate future needs.

Security and Compliance: Assess the safety features and criteria delivered by each explanation.
Consider facets like data encryption, access control, audit trails, and submission with
relevant enterprise restrictions or standards. Assess the explanations' capacity to address
safety and privacy troubles.

Cost and Budget: Analogize the expense importance of each explanation, comprising upfront
payments, ongoing supervision fees, licensing fees, and infrastructure prerequisites. Evaluate
the total expense of ownership over the solution's lifecycle and its alignment with the
project's budget.

Technical Expertise and Support: Evaluate the technological expertise and help available for
each explanation. Consider facets like vendor reputation, documentation, training resources,
community help, and the availability of proficient services or advisers if needed.

Future Proofing and Upgradability: Assess how well the explanations can adapt and develop
over time. Consider facets like the vendor's commitment to updates and enhancements, the

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 47
roadmap for future growth, and their path record of invention. Assess the ease of upgrading
to newer versions or migrating to alternative explanations.

By evaluating and comparing these facets, stakeholders can make knowledgeable

conclusions about which technological explanation is most reasonable for their project. It is
important to prioritize the conditions, constraints, and objectives of the project and consider
the long-term implications and strategic fit of each explanation.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 48
Discuss the components of a feasibility report.

1. Executive Summary: This selection delivers an overview of the feasibility statement,

Summarizing the key findings, decisions, and suggestions. It gives decision-makers a
high-level knowledge of the project's feasibility and its potential effect on the
association.
2. Introduction: The introduction puts the context for the feasibility statement, tracing the
goal, scope, and objectives of the investigation. It delivers background data about the
project and its importance, as well as an overview of the statement's configuration.
3. Project Description: This unit explains the proposed project in element, containing its
goals, objectives, and intended results. It outlines the scope of the project, determines
the stakeholders implicated, and describes the rationale behind its initiation.
4. Methodology: The method section presents the strategy taken to perform the feasibility
investigation. It describes the research strategies, data collection techniques, tools,
and resources utilized to gather and investigate relevant data. It also discusses any
assumptions or limitations of the investigation.
5. Technical Feasibility: This element evaluates the project's technological feasibility,
examining the technology prerequisites, infrastructure needs, and availability of
resources. It assesses whether the proposed project can be implemented using existing
or readily available technology and if the essential technological expertise is
available.
6. Economic Feasibility: The monetary feasibility section assesses the economic viability
of the project. It comprises a cost-benefit analysis, evaluating the projected expenses
of growth, implementation, and operation against the expected benefits and returns on
investment. It may also consider facets such as potential revenue generation, expense
savings, and the payback period.
7. Operational Feasibility: This ingredient evaluates the practicality and functional
feasibility of the proposed project. It examines the project's alignment with existing
business methods, organizational capacities, and resources. It assesses potential
functional effects, such as differences in workflows, staff training prerequisites, and
potential disruptions during commission.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 49
 8. Legal and Ethical Considerations: This section the legal and ethical implications of the
project. It complies with relevant laws, regulations, and industry standards. It also
addresses any ethical related to privacy, data, intellectual property rights, or societal.

9. Risk Assessment: The danger assessment element identifies and evaluates probable
dangers and challenges associated with the project. It investigates both internal and
external dangers, such as technological dangers, market risks, resource risks, and
project management risks. It delivers guidance for mitigating and managing these
dangers.
10. Conclusion and Recommendations: This section summarizes the conclusions of the
feasibility investigation and presents decisions based on the assessment of the
project's feasibility. It delivers suggestions on whether to proceed with the project,
modify the scope or approach, or reject the project based on the calculation
performed.
11. Appendices: The feasibility statement may comprise additional data in the appendices
to help the calculation, such as detailed monetary calculations, technological
specifications, sample documentation, or additional investigation data.

Each ingredient of the feasibility statement contributes to a thorough assessment of the

proposed project's feasibility, enabling stakeholders to make informed conclusions about its
viability and potential commission.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 50
Assess the impact of different feasibility criteria on a software investigation.

1. Technical Feasibility: Technological feasibility assesses whether the proposed

software system can be expanded and implemented using available technology,
implements, and infrastructure. If the technological feasibility is low, it may
indicate that the project requires advanced or specialized technology that is not
readily convenient, which can affect the analysis by improving the complexity,
cost, and time required for growth.
2. Economic Feasibility: Monetary feasibility evaluates the economic viability of the
software system. Facets such as growth expenses, functional costs, potential returns
on investment, and cost-benefit calculation are considered. If the monetary
feasibility is low, it may demonstrate that the project's economic resources are
insufficient or that the anticipated advantages do not overshadow the costs. This can
impact the analysis by requiring a reassessment of the project's budget, funding
sources, or possibly earnings generation.
3. Operational Feasibility: Functional feasibility assesses whether the software system
can be integrated into existing business methods and processes effectively. If the
functional feasibility is low, it may indicate that the proposed system would disrupt
or require important differences to existing workflows, leading to resistance from
users or difficulties in adoption. This can consequence the analysis by necessitating
a thorough analysis of the organization's readiness for difference, movement
prerequisites, and potential opposition to the new system.
4. Schedule Feasibility: Plan feasibility evaluates whether the proposed software system
can be expanded and executed within the desired timeframe. If the plan's feasibility
is low, it may demonstrate that the project's timeline is unrealistic or that some
substantial dependencies or restrictions may delay the delivery. This can affect the
analysis by requiring a reassessment of the project's scope, resource allotment, or
prioritization of attributes and functionalities.
5. Legal and Ethical Feasibility: Lawful and ethical feasibility assesses the system's
submission with relevant laws, regulations, and ethical policies. If the lawful and
ethical feasibility is low, it may imply that the proposed system poses dangers
related to data privacy, safety, intellectual property rights, or societal effects. This

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 51
 can affect the analysis by necessitating a thorough investigation of the lawful and
ethical implications, potential lawful barriers, and the need for supplementary
securities or deliberations.

Each feasibility standard has a specific effect on the software analysis and impacts the
decision-making method. The examination of these measures helps determine potential
dangers, challenges, and restrictions associated with the proposed software system,
encouraging stakeholders to make notified conclusions about its feasibility and potential
effect on the association.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 52
Activity 3
Undertake the system investigation to identify business and system requirements
using appropriate investigation tools/ techniques and develop the software system
specification for the chosen system.

1. Identify the Business Need: Begin by comprehending the specific business need or
issue that requires a software explanation. This could be enhancing efficiency,
streamlining methods, enhancing client experience, or addressing any other pain
points within the association.
2. Gather Requirements: Engage with stakeholders, comprising business users,
managers, and IT personnel, to gather detailed prerequisites. Use techniques like
discussions, workshops, surveys, and documentation review to assure a
comprehensive understanding of the needs and anticipations.
3. Analyze Existing Systems and Processes: Assess the existing strategies and methods in
place to determine any gaps or locations for improvement. Understand the
limitations, bottlenecks, and challenges faced by the association, and determine
how a software explanation can address these problems virtually.
4. Define Project Scope: Founded on the gathered prerequisites and investigation, define
the scope of the software analysis. Clearly outline the objectives, deliverables,
constraints, and boundaries of the project. This step benefits in setting realistic
expectations and management stakeholders' prerequisites.
5. Research and Evaluate Solutions: Perform thorough investigation to analyze various
software explanations available in the demand. Evaluate facets such as
functionality, scalability, compatibility, expense, and vendor reputation. Assess
multiple choices and shortlist the ones that best align with the association's
prerequisites.
6. Cost-Benefit Analysis: Conduct an expense-benefit investigation to evaluate the
monetary implications of the proposed software explanation. Consider the initial
investment, ongoing maintenance expenses, potential expense savings, and
anticipated returns on investment. This analysis helps in determining the monetary
feasibility of the software analysis.
7. Technical Assessment: Assess the technological feasibility of the software
explanation. Consider facets such as required infrastructure, compatibility with
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 53
 existing systems, required expertise, and potential integration challenges. Evaluate
whether the association has the necessary technological capabilities and resources
to implement and help the explanation.
8. Risk Analysis: Perform a risk investigation to determine and evaluate potential
dangers associated with the software analysis. This includes technological dangers,
functional risks, safety risks, and project management risks. Expand techniques to
mitigate and organize these risks.
9. Stakeholder Alignment: Engage with stakeholders to ensure their buy-in and help with
the software analysis. Communicate the proposed explanation, its benefits, and
potential effect on the association. Address any troubles or resistance, and seek
consensus on the way forward.
10. Develop a Proposal: Reduce all the conclusions, investigations, and suggestions into a
legal proposal. The proposal should clearly outline the business need, proposed
explanation, estimated expenses, expected advantages, timeline, and
implementation schedule. Present the proposal to key decision-makers for
permission.

By following this software analysis method, associations can gather crucial data, evaluate
potential explanations, and make informed judgments about implementing software
explanations to meet their business needs.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 54
During a software analysis, different assessment tools and strategies can be used to gather
data, evaluate prerequisites, and develop helping documentation. Here are some
commonly used tools and strategies in software investigation:

1. Interviews: Performing consultations with stakeholders, comprising business users,

managers, and IT personnel, supports gathering insights into their needs,
expectations, and pain points. Structured or semi-structured consultations can be
performed to obtain specific data and clarify prerequisites.
2. Surveys: Researches are useful for containing data from a large number of
stakeholders. Online survey tools can be used to develop questionnaires and gather
feedback on specific aspects of the software analysis, such as user preferences,
satisfaction levels, or system prerequisites.
3. Workshops: Workshops implicate interactive sessions with stakeholders to discuss
and brainstorm ideas, identify prerequisites, and address challenges. Strategies like
brainstorming, use case modeling and user story mapping can be operated to
promote collaboration and capture prerequisites.
4. Observation: Directly: following users or workers as they execute their tasks can
deliver beneficial insights into existing methods, pain points, and areas for
modification. This strategy supports understanding the context and identifying
possibilities for software intervention.
5. Prototyping: Construction prototypes or mock-ups of the proposed software
explanation allow stakeholders to visualize and deliver feedback on its
functionality and usability. Rapid prototyping tools or wire framing software can
be used to develop interactive prototypes that emulate key components and user
interchanges.
6. Data Analysis: Investigating existing data, such as client records, transaction logs, or
system logs, can deliver insights into usage patterns, rendition problems, or
bottlenecks. Statistical analysis strategies, data mining, or visualization tools can
be used to derive meaningful understandings from the data.
7. Requirements Gathering: Various strategies can be employed to elicit, document,
and prioritize prerequisites. These comprise use case investigation, user story
growth, prerequisite workshops, and documentation using tools like Microsoft
Excel, JIRA, or specialized prerequisite management software.
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 55
 8. SWOT Analysis: SWOT (Strengths, Weaknesses, Opportunities, and Threats)
investigation is useful for evaluating the internal and external facets that may
result from the software analysis. It supports identifying the project's strengths,
weaknesses, potential opportunities, and potential dangers or threats.
9. Cost-Benefit Analysis: Using spreadsheets or economic investigation tools, a cost-
benefit investigation can be conducted to quantify the expenses and advantages
associated with the software analysis. This analysis supports evaluating the
economic viability and potential return on investment of the proposed explanation.
10. Documentation: Throughout the software analysis, documentation plays a critical
role in capturing and organizing data. Varied documentation strategies can be
used, such as prerequisite documents, use case diagrams, method flowcharts,
system architecture diagrams, and user manuals. Tools like Microsoft Word,
PowerPoint, Visio, or specialized documentation tools can be utilized for
developing and organizing the documentation.

By utilizing these software investigation tools and strategies, critics can gather relevant
data, understand prerequisites, and develop extensive documentation to help the software
analysis. These strategies support ensuring a systematic and well-informed approach to
software investigation and conclusion-making.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 56
Software prerequisites drafting refers to the exercise of inaugurating and maintaining the
traceability of prerequisites throughout the software development lifecycle. It implicates
linking prerequisites to schedule artifacts, implementation ingredients, test cases, and
other relevant deliverables. The primary purpose of prerequisites delineating is to ensure
that all software artifacts are aligned with the established prerequisites and that
modifications to prerequisites are properly tracked and managed. Here is an investigation
of how software prerequisites can be drafted throughout the software lifecycle:

1. Requirements Elicitation: During the initial phases of the software development

lifecycle, prerequisites are compiled from stakeholders through varied strategies
such as consultations, surveys, and workshops. These prerequisites need to be
documented and arranged systematically for efficacious delineation.
2. Requirements Documentation: Prerequisites are generally documented in a
prerequisites specification document, which serves as a baseline for traceability.
Each prerequisite is assigned a unique identifier or tag, making it easier to trace
throughout the lifecycle. The document should include unambiguous statements of
the prerequisites, along with any relevant components or regulations.
3. Requirements Management Tools: Prerequisites managing tools are often operated to
aid in tracing prerequisites. These tools allow for the innovation of requirement
hierarchies, relationships, and organizations. They provide a centralized repository
for storing and managing prerequisites, making it easier to track differences and
updates.
4. Design and Development: Once the prerequisites are established, they perform as the
foundation for the structure and growth phases. Structure artifacts, such as
architectural charts, system models, and prototypes, should be traced back to the
corresponding prerequisites they address. This ensures that the structure aligns
with the intended functionality and regulations specified in the prerequisites.
5. Implementation and Coding: During the coding phase, innovators can trace particular
code ingredients or modules to specific prerequisites. This can be done through
code comments, version control systems, or by maintaining traceability matrices
that link code entities to prerequisites. By doing so, innovators can ensure that the
implemented functionality corresponds to the specified prerequisites.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 57
 6. Testing and Validation: Test issues and test scripts emanate from prerequisites to
confirm that the software meets the intended functionality. Each test case should
be traced back to the prerequisites it aims to validate. This allows for an extensive
test range and ensures that all prerequisites are sufficiently tested.
7. Change Management: Throughout the software lifecycle, prerequisites may be
modified due to developing business needs or stakeholder feedback. Effective
prerequisite tracing facilitates modification management by delivering visibility
into the effect of prerequisite modifications. When a prerequisite is modified,
tracing allows for the identification of associated design ingredients, code
ingredients, and test cases that may need to be updated.
8. Verification and Validation: Prerequisite tracing aids in the confirmation and
assurance method by enabling stakeholders to evaluate whether the software meets
the initial set of prerequisites. Tracing allows for the easy identification of gaps or
inconsistencies between the implemented explanation and the documented
prerequisites, facilitating the solution of any disparities.

By tracing prerequisites throughout the software lifecycle, associations can ensure that the
last software creation aligns with the intended functionality, satisfies stakeholder needs,
and meets quality standards. It enhances transparency, facilitates effective difference
management, and helps the overall success of the software growth method.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 58
1. Test-Driven Development (TDD): Test-driven development is an iterative growth
strategy that emphasizes writing tests before writing the actual code. The method
typically implicates the following steps:
• Write a failing test: Start by writing a test issue that apprehends the desired demeanor
or functionality.
• Write the code: Evolve the minimal part of the regulation required to make the test
pass. This supports focusing on the specific functionality being executed.
• Run the tests: Perform the test suite to confirm that the newly noted regulation passes
the tests.
• Refactor: If important, refactor the regulation to improve its design, maintainability,
and efficiency. This iterative process is repeated throughout the growth method,
allowing for continuous testing and improvement of the software. TDD promotes
better code quality, as it encourages modular, well-structured, and testable code. It
also supports identifying defects early, reducing the overall expense and effort
required for bug fixing.
2. Continuous Integration and Continuous Delivery (CI/CD): Continuous
Integration (CI) and Continuous Delivery (CD) are rehearsals that focus on
automating the method of integrating, testing, and providing software changes. CI
involves regularly merging code changes from multiple creators into a shared
repository and running automated tests to determine integration cases. CD extends
CI by automating the release and deployment process, allowing for the rapid and
frequent delivery of software updates to presentation environments. The advantages
of CI/CD include:
• Early bug detection: By incorporating code differences regularly and running
automated tests, cases can be determined early in the growth method.
• Faster feedback loop: CI/CD facilitates quick feedback on the quality and stability
of the software, allowing for quicker bug fixing and iterations.
• Reliable releases: Automation ensures that each release is sampled, consistent, and
deployable, reducing the danger of instructing new deficiencies.
• Continuous improvement: With CI/CD, growth groups can continuously learn from
feedback and data, leading to iterative modifications in software quality and
rendition.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 59
Enactment of a techniques analysis is a critical step in improving software quality as it
allows for a comprehensive understanding of the existing system, determines areas of
modification, and supports in formulating methods to enhance software quality. Here is an
evaluation of the method of undertaking a systems analysis and its effectiveness in
improving software quality:

1. Identification of Requirements and Pain Points: The techniques analysis method

involves conference prerequisites from stakeholders and identifying pain points or
areas of dissatisfaction with the current technique. This supports understanding the
specific needs and expectations of users and highlights areas that require
modification. By addressing these prerequisites and pain points, software quality
can be enhanced, as the focus is on determining existing cases and conference user
anticipations.
2. Analysis of Existing Processes and Workflows: During the strategy analysis, the
current methods and workflows are investigated to determine bottlenecks,
inefficiencies, or areas where software quality may be compromised. This analysis
helps streamline methods, eradicate redundant steps, and introduce automation
where essential. By optimizing methods, software quality can be improved by
reducing mistakes, enhancing efficiency, and enhancing overall user experience.
3. Identification of Functional and Non-Functional Requirements: The strategies
analysis method implicates determining both functional and non-functional
prerequisites of the software. Functional prerequisites specify the desired features
and functionalities, while non-functional prerequisites focus on facets such as
performance, safety, scalability, and usability. By carefully analyzing and
documenting these prerequisites, the software development group can ensure that
the last product meets the desired quality standards and addresses all necessary
factors.
4. Stakeholder Engagement and Collaboration: Effective stakeholder attention is a
crucial ingredient of the systems analysis method. By affecting stakeholders, such as
business users, managers, and IT personnel, in the analysis method, their insights
and feedback can be incorporated into the improvement initiatives. This
collaboration supports in alignment of software development efforts with
stakeholder expectations, resulting in enhanced software quality.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 60
 5. Documentation and Communication: The systems analysis method implicates
documenting findings, prerequisites, and proposed solutions. Clear and
comprehensive documentation assures that all stakeholders have a shared
understanding of the analysis results and the planned improvements. It also
promotes effective communication between the software development team and
stakeholders, enabling a smooth evolution from analysis to performance. Proper
documentation and contact contribute to the overall effectiveness of the analysis
method and ultimately enhance software quality.

Undertaking a systems analysis is an effective method for improving software quality. By

systematically investigating prerequisites, identifying pain points, optimizing methods,
engaging stakeholders, and documenting findings, organizations can gain beneficial
insights and make informed conclusions to enhance software quality. The analysis method
supports addressing existing cases, aligning software development efforts with stakeholder
expectations, and assuring that the last product meets the desired quality standards.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 61
Activity 4

Discuss the suitability of software behavioral design techniques

1. Complexity of System Behavior: If the software system has a complicated demeanor,

operating behavioral design strategies become critical. Strategies such as Use Case
Diagrams, Sequence Diagrams, and State Diagrams support apprehending and
visualizing complicated system demeanor. These strategies enable the creators to
understand the flow of interactions, events, and states within the system, ensuring
that the desired demeanor is effectively designed and executed.
2. Requirements Clarity: Software behavioral design strategies are extremely beneficial
when prerequisites are well-defined and specific. By using strategies like Use Case
Diagrams, developers can map the system's functionality to user interchanges and
ensure that the system meets the specified prerequisites. Clear prerequisites support
accurately modeling the demeanor of the system and lessening the chances of
misunderstandings or misinterpretations.
3. User-Centric Design: If the software system is user-centric and focuses on delivering
an instinctive and seamless user experience, behavioral design strategies are highly
reasonable. Strategies like User Interaction Diagrams, Storyboards, and Wireframes
assist in apprehending user interactions, workflows, and screen designs. By using
these techniques, creators can design software systems that align with user
anticipations and deliver smooth and committed user knowledge.
4. Collaboration and Communication: Behavioral design strategies promote collaboration
and connection among stakeholders, comprising creators, designers, testers, and
end-users. These strategies provide a common language and visual representation of
the system's behavior, enabling effective connection and assuring that everyone has
a shared understanding of the system's functionality. This enhances collaboration,
lessens misunderstandings, and improves the overall quality of the software system.
5. Dynamic and Interactive Systems: Software systems that require dynamic demeanor,
real-time interchanges, or event-driven reactions can greatly help from behavioral

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 62
 design strategies. Strategies like Sequence Diagrams and State Diagrams support
modeling and knowledge of the dynamic demeanor of the system, capturing the
flow of events and the system's responses to those events. This ensures that the
system behaves as intended in varied methods and supports the desired
functionality.
6. Iterative and Agile Development Approaches: Behavioral structure strategies align well
with iterative and agile development approaches. These strategies allow for the
incremental improvement of the system demeanor, ensuring that the structure
evolves alongside the growth process. As Agile methods emphasize constant
feedback and collaboration, behavioral structure techniques enable creators to
capture, validate, and refine the demeanor of the software system in each iteration.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 63
Undertaking a systems analysis is a crucial step in enhancing software quality as it
implicates thoroughly analyzing the existing system, identifying pain points, and
formulating strategies for modification. The method of systems analysis can have a
significant effect on software quality in the following ways:

1. Requirement Analysis: During the systems analysis, prerequisites are gathered from
stakeholders, comprising end-users and business owners. This investigation
supports understanding the anticipations and needs of the users, ensuring that the
software is designed to meet those prerequisites. By accurately capturing and
investigating the, the sets the foundation for a high-quality software system.
2. Identifying Deficiencies: Systems analysis implicates a detailed assessment of the
current software system, its functionalities, and its performance. This examination
supports identifying deficiencies, such as bugs, performance bottlenecks, safety
vulnerabilities, or usability cases. By uncovering these deficiencies, the analysis
method enables the growth group to address them and enhance the overall quality of
the software system.
3. Gap Analysis: Systems analysis implicates comparing the current system's capacities
with the desired state or industry best training. This gap investigation supports
identifying areas where the software system falls short and where improvements are
needed. By identifying these gaps, the analysis method guides the growth group in
implementing necessary enhancements and aligning the software system with
industry criteria and best exercises.
4. Process Optimization: During the systems analysis, the existing processes, workflows,
and methodologies are assessed. This evaluation supports identifying inefficiencies,
monotonies, or bottlenecks that can affect software quality. By optimizing these
methods, the analysis method ensures smoother workflows, reduced mistakes, and
improved efficiency, coaching to better software quality.
5. Risk Identification and Mitigation: Systems analysis implicates evaluating potential
dangers associated with the software system, such as safety threats, data loss, or
system failures. By identifying these risks, the analysis method enables the growth
Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 64
 group to implement appropriate comfort techniques and preventive criteria. This
proactive approach to risk management significantly contributes to improving
software quality and assuring a robust and secure system.
6. Stakeholder Engagement: Effective stakeholder attention is a critical facet of the
systems analysis method. By implicating stakeholders throughout the analysis, their
insights, feedback, and expectations are captured, assuring that the software system
addresses their needs. This collaborative approach supports improving software
quality by aligning growth efforts with stakeholder anticipations and incorporating
their beneficial input into the system design and commission.

The method of undertaking a systems analysis is highly effective in improving

software quality. It supports determining prerequisites, uncovering deficiencies,
optimizing methods, mitigating risks, and engaging stakeholders. By addressing
these aspects, the analysis method delivers a solid foundation for the development
team to enhance software quality, resulting in a more dependable, secure, and user-
friendly software system.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 65
1. Use Case Diagrams: Using issue diagrams is reasonable for capturing the functional
prerequisites and interchanges between users and the system. For example, in an e-
commerce application, a use issue diagram can depict user efforts such as browsing
products, adding items to the cart, and making a purchase. Use case diagrams are
effective in visualizing user-system interchanges and assuring that all crucial
functionalities are accounted for.
2. Sequence Diagrams: Ordering diagrams are reasonable for modeling the dynamic
demeanor of a system by demonstrating the ordering of interchanges between
objects or ingredients. For example, in a banking system, an ordering diagram can
illustrate the steps implicated in transferring funds from one account to another.
Ordering diagrams support determining the flow of control and data between system
elements, ensuring the desired demeanor is executed correctly.
3. State Diagrams: State charts are reasonable for modeling the demeanor of systems
with distinct states and transitions between them. For example, in a ticket
reservation system, a state chart can represent the various states of a ticket (e.g.,
available, reserved, sold) and the situations for transitioning between states. State
diagrams support visualizing the probable system states and assuring that the system
behaves accurately in different scenarios.
4. User Story Mapping: User tale mapping is reasonable for capturing user prerequisites
and organizing them in a user-centric manner. It implicates developing user tales
and organizing them into a meaningful flow or timeline. User tale mapping supports
understanding the user journey, prioritizing features, and ensuring that the software
system provides value to users logically and cohesively.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 66
1. Finite State Machine (FSM) Application: Evaluate a vending device that dispenses
various products based on user input. An FSM can be used to model the demeanor
of the vending device, where the states represent different stages of the vending
method (e.g., idle, product choice, payment, dispensing), and evolutions represent
the conditions for moving between states (e.g., user input, successful payment). The
FSM can ensure that the vending machine follows a predefined succession of states
and evolutions, ensuring reasonable functionality.
2. Extended Finite State Machine (EFSM) Application: In a web application, an EFSM
can be used to model the demeanor of a user authentication system. The states
depict various user authentication stages (e.g., login, password).
3. Behavior Modeling with Activity Diagrams: Activity diagrams illustrate the flow of
activities, actions, and conclusion points within a system. They support visualizing
the steps involved in completing a task or method. Activity diagrams are useful for
capturing the demeanor of software systems, especially those with complicated
workflows or business methods.
4. User Story Mapping: User tale mapping is a strategy used to prioritize and arrange
user prerequisites. It implicates developing user tales and arranging them into a
coherent flow or timeline. User tale mapping supports understanding the user's
journey, identifying dependencies, and assuring that the software's demeanor aligns
with user needs and priorities.
5. Event-Driven Design: Event-driven structure focuses on modeling the demeanor of a
system based on external occasions and their associated reactions. It involves
determining events that can trigger actions within the system and designing the
system to respond accordingly. Event-driven structure is often used in systems that
need to react to real-time events, such as IoT applications or event-driven
architectures.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 67
Finite State Machine (FSM) Application:

Evaluate a traffic light system with three states: Red, Yellow, and Green. The FSM
model can illustrate the traffic light system as follows:

State: Red

Transition: Timer expires or a command is received

Action: Change state to Yellow

State: Yellow

Transition: Timer expires or a command is received

Action: Change state to Green

State: Green

Transition: Timer expires or a command is received

Action: Change state to Red

In this example, the FSM provides a simple representation of the traffic light
system's behavior, allowing the system to transition between states based on
specified events or conditions.
Extended Finite State Machine (EFSM) Application:

Consider a login authentication system for a web application. The EFSM model can
represent the behavior of the authentication system as follows:
State: Idle

Transition: User submits login credentials

Action: Validate the credentials and change state to Verifying

State: Verifying

Transition: Credentials are valid

Action: Change state to Authenticated and grant access

Transition: Credentials are invalid

Action: Change state to Failed and deny access

Tharushi Kavishka Software Development Lifecycles Assignment 03
Page | 68
 State: Authenticated

Transition: User logs out

Action: Change state to Idle

State: Failed

Transition: User retries login

Action: Change state to Verifying and repeat the authentication process

In this example, the EFSM extends the capabilities of an FSM by including additional
elements such as the ability to handle various results based on the assurance of user
credentials. It allows for more complex demeanor modeling and delivers a more detailed
representation of the authentication system's demeanor.

In summary, while FSMs are beneficial for representing simple systems with distinct
states and evolutions, EFSMs offer added characteristics and flexibility to handle more
complicated demeanor and multiple outcomes. The selection between FSM and EFSM
depends on the specific requirements of the system and the level of element needed to
accurately model its demeanor.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 69
Data-driven software refers to software systems that rely heavily on data for decision-
making, processing, and functionality. Here are some explanations for how data-driven
software can enhance the reliability and convincingness of software:

1. Accurate Decision-making: Data-driven software allows for knowledgeable

conclusion-making based on real-time or historical data. By analyzing and
interpreting data, software systems can make accurate and data-backed conclusions,
reducing the chances of mistakes or biases that may occur with human decision-
making. This enhances the reliability of the software in providing accurate and
constant results.
2. Personalized User Experience: Data-driven software can assemble and investigate user
data to deliver personalized experiences. By understanding user intentions,
demeanor, and patterns, software systems can tailor the user interface, content, and
suggestions to each user's specific needs. This personalization enhances the
effectiveness of the software by providing a customized experience that meets
individual user prerequisites.
3. Predictive Analytics: Data-driven software can influence predictive analytics to predict
future trends, demeanor, or events based on historical data. By analyzing patterns
and correlations, software systems can deliver insights and predictions that enable
assertive decision-making. For example, predictive supervision software can
investigate tools and sensor data to predict when supervision is needed, supporting
to prevention of failures and improving the reliability of the system.
4. Continuous Improvement: Data-driven software can track and investigate rendition
metrics, user feedback, and usage patterns to determine areas for modification. By
monitoring data, software groups can determine bottlenecks, bugs, or usability cases
and take proactive criteria to address them. This iterative modification process
enhances the reliability and convincingness of the software over time.
5. Enhanced Automation: Data-driven software can automate redundant tasks and
methods founded on predefined regulations and data inputs. By automating routine
activities, software systems reduce human error, enhance efficiency, and assure
consistent and reliable performance of tasks. This enhances the overall reliability

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 70
 and convincingness of the software by minimizing manual intervention and
streamlining procedures.

In summary, data-driven software leverages the power of data to enhance conclusion-

making, personalize user knowledge, enable predictive analytics, facilitate continuous
modification, and enhance automation. By relying on data-driven strategies, software
systems can achieve higher reliability and convincingness in providing accurate outcomes,
conference user needs, and optimizing rendition.

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 71
Reference

Tutorials Point (2023). SDLC Overview. [Online] www.tutorialspoint.com. Available at

Accessed: 06 05 2023 https://www.tutorialspoint.com/sdlc/sdlc_overview.htm.

Java point (2011). SDLC - Software Development Life Cycle - java point. [Online]
www.javatpoint.com. Available at: Accessed: 06 01 2023
https://www.javatpoint.com/software-engineering-software-development-life-cycle.

Martin, M. (2019). SDLC (Software Development Life Cycle) Tutorial: What is, Phases,
Model. [Online] Guru99.com. Available at: 06 09 2023
https://www.guru99.com/software- development-life-cycle-tutorial.html.

Investopedia. (n.d.). Feasibility Study. [Online] Available at:

https://www.investopedia.com/terms/f/feasibility- : Accessed: 06 09 2023

WallStreetMojo Editorial Team (2022). Feasibility Study. [Online] WallStreetMojo.

Available at: https://www.wallstreetmojo.com/feasibility-study/. Accessed: 06 10 2023

Java point (2011). Agile Model - java point. [Online] www.javatpoint.com. Available at:

https://www.javatpoint.com/software-engineering-agile-model. Accessed: 06 10 2023

Kumar Pal, S. (2019). Software Engineering | Classical Waterfall Model - GeeksforGeeks.

[Online] GeeksforGeeks. Available at: https://www.geeksforgeeks.org/software-
engineering- classical-waterfall-model/. Accessed: 06 10 2023

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 72
Martin, M. (2019). What is Waterfall Model in SDLC? Advantages & Disadvantages.
[Online] Guru99.com. Available at: https://www.guru99.com/what-is-sdlc-or-waterfall-
model.html. Accessed: 06 11 2023

Sharma, L. (2016). Waterfall Model in Software Development Life Cycle | SDLC. [Online]
Toolsqa.com. Available at: https://www.toolsqa.com/software-testing/waterfall-model/.
Accessed: 06 14 2023

GeeksforGeeks. (2019). Difference between Waterfall model and Incremental model -

GeeksforGeeks. [Online] Available at: https://www.geeksforgeeks.org/difference-
betweenwaterfall-model-and-incremental-model/.Accessed: 06 10 2023

www.cs.odu.edu. (n.d.). Software Development Process Models. [Online] Available at:

https://www.cs.odu.edu/~zeil/cs350/s16/Public/processModels/. Accessed: 06 10 2023

www.roberthalf.co.uk. (2018). 6 basic SDLC methodologies: which one is best? [Online]

Available at: https://www.roberthalf.co.uk/advice/career-development/6-basic-
sdlcmethodologies-which-one-best. Accessed: 06 16 2023

Elprocus (2019). Finite State Machine (FSM): Types, Properties, Diagram, Design and
Applications. [Online] ElProCus - Electronic Projects for Engineering Students. Available
at:
https://www.elprocus.com/finite-state-machine-mealy-state-machine-and-moore-
statemachine/. Accessed: 06 10 2023

GeeksforGeeks. (2020). Software Development Life Cycle (SDLC). [Online] Available at:
https://www.geeksforgeeks.org/software-development-life-cycle-sdlc/. . Accessed: 06 15
2023

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 73
www.tutorialspoint.com. (n.d.). Software Analysis & Design Tools - Tutorials point.
[Online]
Availablehttps://www.tutorialspoint.com/software_engineering/software_analysis_design_t
o ols.htm. Accessed: 06 15 2023

creately.com. (2022). The Easy Guide to UML Activity Diagrams | Creately. [Online] A
https://creately.com/guides/activity-diagram-tutorial/

Tharushi Kavishka Software Development Lifecycles Assignment 03

Page | 74