lOMoARcPSD|48216755

SAD assignment

HND in Computing (ESOFT Metro Campus)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by ??? ??? ([email protected])
 lOMoARcPSD|48216755

Higher Na琀椀onals
Internal veri昀椀ca琀椀on of assessment decisions – BTEC (RQF)
INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme 琀椀tle HND in Compu琀椀ng

Assessor Internal Veri昀椀er

Unit 35: System Analysis & Design
Unit(s)

Web based System for “Auto Cars”

Assignment 琀椀tle

Student’s name
List which assessment criteria Pass Merit Dis琀椀nc琀椀on
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/Dis琀椀nc琀椀on grade awarded
jus琀椀昀椀ed 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:
• Construc琀椀ve?
Y/N
• Linked to relevant assessment criteria?
Y/N
• Iden琀椀fying opportuni琀椀es for Y/N
improved performance?
• Agreeing ac琀椀ons?
Y/N
Does the assessment decision need
amending? Y/N

Assessor signature Date

Internal Veri昀椀er signature Date

Programme Leader signature (if required)
Date
Con昀椀rm ac琀椀on completed
Remedial ac琀椀on taken
Give details:

Assessor signature Date

Internal Veri昀椀er
signature Date

1
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Programme Leader
signature (if required) Date

2
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Higher Na琀椀onals - Summa琀椀ve Assignment Feedback Form

Student Name/ID

Unit Title Unit 35: System Analysis & Design

Assignment Number 1 Assessor

Date Received
Submission Date 1st submission
Date Received 2nd
Re-submission Date submission

Assessor Feedback:
LO1 Evaluate the strengths and weaknesses of the tradi琀椀onal and agile systems analysis methodologies
Pass, Merit & Dis琀椀nc琀椀on P1 M1 D1
Descripts

LO2 Produce a feasibility study for a system for system to be developed to solve a business-related
problem
Pass, Merit & Dis琀椀nc琀椀on P2 M2
Descripts

LO3 Assess systems analysis methodologies to e昀昀ec琀椀vely solve business-related problems

Pass, Merit & Dis琀椀nc琀椀on P3 M3 D2

Descripts

LO4 Design the system to meet user and system requirements.

Pass, Merit & Dis琀椀nc琀椀on P4 M4
Descripts

Grade: Assessor Signature: Date:

Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Veri昀椀er’s Comments:

Signature & Date:

* Please note that grade decisions are provisional. They are only con昀椀rmed once internal and external modera琀椀on has taken place
and grades decisions have been agreed at the assessment board.

3
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Pearson Higher Na琀椀onals in

Compu琀椀ng
Unit 35: Systems Analysis & Design
Assignment 01

4
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

General Guidelines

1. A Cover page or 琀椀tle page – You should always a琀琀ach a 琀椀tle page to your assignment.
Use previous page as your cover sheet and make sure all the details are accurately 昀椀lled.
2. A琀琀ach this brief as the 昀椀rst sec琀椀on of your assignment.
3. All the assignments should be prepared using a word processing so昀琀ware.
4. All the assignments should be printed on A4 sized papers. Use single side prin琀椀ng.
5. Allow (Placeholder1)for top, bo琀琀om , right margins and 1.25” for the le昀琀 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. Le昀琀 jus琀椀fy all paragraphs.
3. Ensure that all the headings are consistent in terms of the font size and font style.
4. Use footer func琀椀on 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 applica琀椀on spell check and grammar check func琀椀on to help edi琀椀ng
your assignment.

Important Points:

1. It is strictly prohibited to use textboxes to add texts in the assignments, except for
compulsory informa琀椀on. eg: Figures, tables of comparison etc. Adding text boxes in the
body except for the before men琀椀oned compulsory informa琀椀on will result in rejec琀椀on of
your work.
2. Carefully check the hand in date and the instruc琀椀ons given in the assignment. Late
submissions will not be accepted.
3. Ensure that you give yourself enough 琀椀me 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 琀椀me.
5. You must take responsibility for managing your own 琀椀me e昀昀ec琀椀vely.
6. If you are unable to hand in your assignment on 琀椀me and have valid reasons such as
illness, you may apply (in wri琀椀ng) 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 automa琀椀c RE FERRAL. You
will then be asked to complete an alterna琀椀ve assignment.
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 cita琀椀on 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.

5
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Student Declara琀椀on

I hereby, declare that I know what plagiarism entails, namely, to use another’s work and to
present it as my own without a琀琀ribu琀椀ng 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 o昀昀ence because it cons琀椀tutes the昀琀.

2. I understand the plagiarism and copying policy of Edexcel 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 a琀琀ribute the source in
the correct way.
5. I acknowledge that the a琀琀achment of this document signed or not, cons琀椀tutes a binding
agreement between myself and Pearson , UK.
6. I understand that my assignment will not be considered as submi琀琀ed if this document is
not a琀琀ached to the assignment.

Student’s Signature: Date:

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

6
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Higher Na琀椀onal Diploma in Compu琀椀ng

Assignment Brief
Student Name /ID Number

Unit Number and Title Unit 35: Systems Analysis & Design

Academic Year 2022/23

Unit Tutor

Assignment Title
Issue Date

Submission Date

IV Name & Date

Submission format

The submission should be in the form of an individual wri琀琀en report wri琀琀en in a concise,
formal business style using single spacing and font size 12. You are required to make use of
headings, paragraphs and subsec琀椀ons as appropriate, and all work must be supported with
research and referenced Please provide in-test cita琀椀ons, reference list and bibliography
using Harvard referencing system. Please also provide a bibliography using the Harvard
referencing system.
The recommended word limit is not less than 5000 words, although you will not be
penalised for exceeding the total word limit.

Unit Learning Outcomes:

LO1 Evaluate the strengths and weaknesses of the traditional and agile systems analysis
methodologies.
LO2 Produce a feasibility study for a system to be developed to solve a business-related
problem.
LO3 Assess systems analysis methodologies to e昀昀ec琀椀vely solve business-related problems.
LO4 Design the system to meet user and system requirements.

Assignment Brief and Guidance:

7
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

*Please note that assignment guidance is for reference only and should be more speci昀椀c in
detail to meet customized needs.
Assignment brief
Case study
“Auto Cars” is a taxi service in Sri Lanka which has been in operation for several decades,
serving the customers in city and urban areas. As a result of the increased use of information
technology such as mobile phones and the internet, “Auto Cars” decided to launch a web-
based system that enables customers to reserve vehicles conveniently. This also helps the
company to gain a competitive advantage.
The main system features of the web-based system are required for “Auto Cars” to reserve
taxis for customers are:
a. Customers and drivers can use the online system to register. They will receive an
email with their username and password once they have registered.
b. Customers can book taxis via the website. When they reserve a vehicle, they will
receive an SMS on their phone with the driver's contact information and vehicle
details.
c. Customers can rate drivers based on their experiences with them on trips.
d. In addition, the company employs a phone operator who manually reserves drivers
from the system. This is the same as a customer reserving a driver, except there is no
logged in customer in the application.
e. When the operator makes a taxi reservation, she enters the customer's phone number
into the system, and the customer receives an SMS.
f. The driver closest to the customer must be assigned by the application. When a
customer or the operator reserves a vehicle, the system should display a list of
available drivers. From this list, the customer can then select the best driver.
g. The driver’s location is manually (by the driver) entered into the web-based system
or via the telephone operator. Similarly, when reserving a taxi, the customer's
location is specified (by the customer or through the operator).

Assume that you are the newly appointed system analyst for “Auto Cars” and assigned to
work on this project. Produce a professional report including the answers to the following
tasks.

8
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Ac琀椀vity 01
Discuss and critically evaluate the strengths and weaknesses of the traditional and agile
systems analysis methodologies. Compare the strengths and weaknesses of the two
methodologies by referring to the proposed web system for “Auto Cars”.

Ac琀椀vity 2
Conduct the feasibility study for the web-based system for “Auto Cars” and produce a
feasibility report. Further, evaluate the importance of the feasibility criteria used to
investigate the feasibility of the proposed system.

Ac琀椀vity 3
Review the user and system requirements for the web-based system suggested in the scenario
using a suitable software development methodology and asses the effectiveness of the
methodology selected. Justify the chosen methodology for the web-based system with
relevant examples.

Ac琀椀vity 4
Design a system specification for the web-based system to meet end user system
requirements and assess the effectiveness of your design and the methodology used with
reference to how it meets the user requirements.
Your system design speci昀椀ca琀椀on should include,
 Data Flow diagrams (context diagram, Level 0, level 1 , level 2 DFDs)/ Use case
diagram
 En琀椀ty Rela琀椀onship diagram (ERD)
 Flow charts
 Prototypes to illustrate system interfaces and func琀椀ons.
 Release plan and tools

9
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

10
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Table of Contents
Acknowledgement......................................................................................................11
Ac琀椀vity 01..................................................................................................................12
Key principles of tradi琀椀onal methodologies.........................................................................13
Waterfall methodology:.......................................................................................................16
Here are few agile methodologies explain in follow:............................................................26
Agile vs tradi琀椀onal methodologies.......................................................................................39
Strengths of tradi琀椀onal methodologies................................................................................39
Weaknesses of the tradi琀椀onal methodologies.....................................................................40
Suitable methodologies.......................................................................................................42
Ac琀椀vity 02..................................................................................................................45
What is the feasibility report?..............................................................................................45
Why we need feasibility study report?.................................................................................47
Strengths and weaknesses of feasibility report....................................................................48
Feasibility report of auto car system....................................................................................50
Ac琀椀vity 3....................................................................................................................66
What are the func琀椀onal and non-func琀椀onal requirements?................................................68
Non-func琀椀onal requirements...............................................................................................69
Iden琀椀fying documenta琀椀on produced at the di昀昀erent stages...............................................71
Ac琀椀vity 04..................................................................................................................73
How the design meets user and system requirements.........................................................73
system aligning with user requirements...............................................................................74

Figure 1traditional and sequential project phases..............................................................12

Figure 2waterfall methodology..........................................................................................17
Figure 3prototype model....................................................................................................18
Figure 4spiral model..........................................................................................................20
Figure 5values and principles of agile...............................................................................24
Figure 6process of scrum...................................................................................................27
Figure 7kanban board.........................................................................................................28
Figure 8exterme programming and loops..........................................................................31
Figure 9lean software development...................................................................................34
Figure 10benefits of feasibility report................................................................................47
Figure 11ongoing interview...............................................................................................67
Figure 12use case diagram of the auto car system.............................................................78
Figure 13dfd level 0 diagram of the auto car system.........................................................78
Figure 14entiity related diagram of auto car system..........................................................79

11
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 15flow chart check cab availability........................................................................80

Figure 16flow chart of rating and tip payment...................................................................81
Figure 17flow chart login process......................................................................................82
Figure 18application booting window...............................................................................82
Figure 19login or signup window......................................................................................83
Figure 20destination selecting window..............................................................................83
Figure 21taxi selecting window.........................................................................................84
Figure 22give reviews and tips..........................................................................................84
Figure 23driver login page.................................................................................................85
Figure 24driver dashboard and location of the client.........................................................85
Figure 25selecting payment method and amount...............................................................86
Figure 26driver location and availability update...............................................................86
Figure 27feedback forms of the system.............................................................................87
Figure 28responses for the 1st question.............................................................................89
Figure 29responses for second one....................................................................................89
Figure 30other comments and people who give the feedback...........................................91

Acknowledgement
I would like to express my sincere gratitude to Ms, sithumi geeshya Who was our teacher
regarding this module, for their invaluable guidance, support, and expertise throughout
the completion of this assignment. Their insightful feedback and constructive suggestions
greatly contributed to the quality of the work. I am also thankful to ms, sindhuja and other
teachers for their assistance. This project wouldn't have been possible without the
generous input from these individuals. I extend my thanks to all who have played a role in
shaping this assignment.

12
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Activity 01
What are the traditional methodologies.
Traditional or sequential project management approaches operate in a linear way, with
five typical phases: initiation, planning, execution, monitoring, and closing. This method
involves initial planning, documentation, and prioritizing. Using this method necessitates
defining the scope and establishing project requirements from the outset.

As a result, traditional project management necessitates the employment of a project

manager or a Project Management Office, who has primary responsibility for the project
and is accountable for attaining goals. Once the scope is decided upon and the initiation
phase begins, modifications must be controlled using the change management method.

Figure 1traditional and sequential project phases

When using the traditional methodologies those are best suited for the where the
following conditions are applied.
1. When the requirements are stable: Traditional approaches can be useful when
the project or problem requirements are well-defined and unlikely to change
considerably over time. This is because traditional approaches usually include a
sequential and predictable procedure that works best when the requirements are
steady.

13
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

2. Low risk and project is predictable: Traditional approaches are commonly

utilized in projects with modest hazards that may be readily identified and
handled. Because these approaches require extensive preparation and
documenting up front, they are best suited for projects with known limits and
low uncertainty.
3. Client preferences: Clients or stakeholders may choose conventional
approaches because they are familiar with them or because of regulatory
obligations. Certain sectors, such as aerospace or healthcare, may have severe
requirements requiring the usage of conventional approaches for compliance.
4. Leaner progression: Traditional techniques are useful when activities can be
clearly specified and carried out in a linear order. This means that each part of
the project is contingent on the completion of the preceding phase, with little
overlap or iteration between phases.

Key principles of traditional methodologies.

Traditional approaches often comprise a number of fundamental components that are
required to guide the systematic execution of projects and activities. Here are some of the
fundamental components often present in conventional approaches.

1. Stages: Traditional approaches frequently break down the project lifecycle into
separate phases or stages, each with its own set of activities and deliverables.
These phases are usually consecutive, with one step requiring the completion of
the preceding phase. Phases include start, planning, execution, monitoring and
control, and closing.
2. Detailed planning: Traditional approaches emphasize thorough planning at the
start of a project to establish objectives, scope, timetable, resources, and
deliverables. Detailed project plans, which are frequently recorded in project
charters, work breakdown structures (WBS), and Gantt charts, are developed to
guide project execution and progress.
3. Documenting: Documentation is essential in conventional approaches, with a
focus on establishing and keeping thorough records of project activities, choices,

14
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

and outcomes. Documentation fosters openness, improves communication, and

serves as a reference for future initiatives or audits.
4. Quality management: Quality management is built into conventional
techniques, with a focus on ensuring that deliverables fulfil set standards and
requirements. Quality assurance techniques are used throughout the project's
lifespan to discover and correct flaws or deviations from specifications.
5. Risk management: Traditional techniques involve processes for identifying,
assessing, and mitigating possible risks to project success. Risk management
tasks generally include identifying risks, assessing their possible effect and
likelihood, establishing mitigation methods, and tracking risk throughout the
project.
6. Formal reviews and approvals: Traditional approaches frequently include
formal review and approval processes to validate project deliverables and
milestones. Peer reviews, stakeholder reviews, and management reviews may all
be used to verify project objectives and criteria are met.

When choosing a methodology for a project we have to go with agile or one of

traditional methodology. choosing a methodology is not an easy task. Let’s take
a look at strengths and weaknesses of the choosing traditional methodologies.

strengths
1. Cost effective: Because projects are easier to finish with Traditional
Project Management. That is why they are likely to take less time to
complete and achieve the deadline effectively. Bugs, faults, or
complicated difficulties are unlikely to occur throughout project
conception, design, testing, and execution.
2. Best for remote projects: Larger and more complicated projects have
significant communication challenges due to geographical differences.
Traditional projects are smaller and more manageable, making them ideal
for distant tasks. As a result, projects may be produced by a smaller team
with little communication required to overcome obstacles.
3. Deliver on time: A common issue that many businesses face, regardless
of where they are in the company life cycle, is that they become bogged
down in everyday operations at the expense of business growth efforts. It

15
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

wastes resources, money, and time. Traditional approach projects need

little change since they follow a set sequence. That is why they arrive on
time.
4. Optimized for customer satisfaction: Traditional projects are not overly
sophisticated to suit the client's expectations. Client satisfaction is a top
priority in any project management approach. The entire development
process considers the client's needs. The customer is informed of each
procedure, maintains confidentiality about comments, and prioritizes
each need.
5. Responsible for quality output: Traditional Software Development
Methodology aims to produce high-quality development to generate a
sturdy solution that meets market needs. It is sillier than a fancy
assumption to expect 100% success. Achieving a realistic approach and
refined accuracy requires focused expertise, cooperation, coordination,
and management.

weaknesses
Also there have many weaknesses of choosing a traditional
methodologies for the projects. Let’s dive in to those weaknesses of the
traditional methodologies.

1. Flexibility is limited: Traditional SDLC techniques take a sequential, linear

approach, where each step must be finished before the next can begin. This lack
of flexibility makes it difficult to accept changes in needs, which might result in
delays and cost overruns.
2. Late feedback time: Traditional techniques sometimes entail little client
participation until later stages of development. This can lead to difficulties or
misconceptions being uncovered later in the process, making them more costly
and time-consuming to resolve.
3. Limited chance to change: Traditional approaches are less responsive to
changes in requirements or technological advancements. If the project
requirements change dramatically during development, the resulting solutions
may be obsolete or unsatisfactory.

16
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

4. Difficulty Managing Complex Projects: These approaches may struggle to

manage complicated projects with unpredictable or changing needs. Projects that
use cutting-edge technology or have complex interdependencies may be
especially difficult to complete using standard approaches.

1.

17
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Waterfall methodology:

Other development approaches incorporate a project's end user or customer more than the
waterfall model does. Users are consulted early in the process of gathering and
establishing requirements, and client input is included later. By excluding the customer
from the major part of the waterfall process, the development team may proceed swiftly
through the project ‘stages.

This approach is appropriate for teams and projects that wish to create a project based on
constant or unchanging requirements specified at the start of the project. Waterfall
projects have a high level of process clarity and low to no output variability. Waterfall is
also an excellent option if the project is limited by budget or time. Waterfall model can
easily use when,
1. All the requirements are clear, well known and fixed.
2. There are no ambiguous requirements.
3. When the development environment is stable.
4. The project is short and simple.
5. When The tools, techniques are stable.

Advantages of waterfall model

1. Each steps of waterfall model has their own review process and deliverables.
2. All the requirements, milestones, deadlines and final out comes are fixed and
well documented.
3. Waterfall model require few project management deliverables, these are ensure
that final product is well secured and have quality outcome.
4. In small projects final output can deliver fast.

Disadvantages of waterfall model

1. Waterfall model is not allowed to change the requirements during the process.
2. This model is not allowed go to the previous phase.

18
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

3. Testing under the Waterfall approach is postponed until the conclusion of

project development, which means you find faults and defects too late and have
to spend a lot of time addressing them rather than controlling them early on.
4. Getting stress and pressure because of inflexible deadlines.
5. Do not suitable for complex projects with high risks.

Figure 2waterfall methodology.

Prototype methodology:
The Prototype Model is a software development technique that is suitable for projects
with ambiguous or shifting requirements. It entails developing a preliminary version of
the software product, known as a prototype, that demonstrates the essential features and
capabilities that the clients desire.

The prototype is then evaluated and updated by both consumers and developers until they
are satisfied with the final prototype, which serves as the foundation for the finished
product. The Prototype Model offers several advantages, including more customer
engagement, reduced risks, and improved quality. However, it has certain downsides,
such being time-consuming, expensive, and difficult to document.the main phases of the
prototype model are following,
1. Requirement gathering
2. Quick design.
3. Prototype development.
4. Prototype testing.

19
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

5. Refinement.
 If the desired system need to be interact with the end user prototype is the
best methodology to use.
 When cooperation among several stakeholders, including as developers,
designers, and end users, is critical, the Prototype Model fosters
communication and collaboration through iterative development cycles
and regular feedback loops.
 online systems and web interfaces with a high level of engagement with
end users are best suited for the prototype approach. It may take some
time to develop a system that is user-friendly and requires minimum
training for the end user.
 The Prototype Model facilitates exploration and validation of ideas when
a project involves uncertainty or risk, such as with new technologies or
innovative solutions, allowing for assessment before committing to full-
scale development.

Figure 3prototype model

Advantages of the using prototype model:

1. Very easy to detect errors in system.
2. Find missing functionalities easily.
3. Can reuse in the future for the complex projects.
4. Rich in customer satisfaction and comfort.
5. This method helps to user and developer to understand the system well.
6. Users can involves when system is in the development phase.

20
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Disadvantages of using prototype model:

1. Operation cost is high.
2. There is no strong documentation due to changing customer requirements.
3. Customers ask to deliver actual product soon after seeing the prototype.
4. Maybe increase the complexity of the system.
5. Because prototypes are frequently used to communicate design concepts, there is
a danger of misinterpretation among stakeholders if the prototype does not
accurately reflect the final product.

Spiral methodology:

The Spiral methodology, a Software Development Life Cycle (SDLC) approach, adopts a
systematic and iterative method for software development. Represented diagrammatically
as a spiral with multiple loops, the specific count of loops is indeterminate and varies per
project. Each spiral loop corresponds to a distinct phase in the software development
process.
 The project manager has the flexibility to adjust the precise number of phases
required for product development based on the associated project risks.
 In employing the spiral model for product development, the project manager
assumes a crucial role in dynamically determining the number of phases required.
 Built upon the concept of a spiral, each cycle iteration within the spiral embodies
a full software development cycle, encompassing activities from requirements
gathering and analysis to design, implementation, testing, and maintenance.

There have 5 main phases of the spiral model:

1. Planning phase
2. Risk analysis phase
3. Engineering phase
4. Evaluation phase
5. Planning

21
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 4spiral model

 If the project Is highly uncertain or complex the suitable model is spiral one to
use. Where the requirements are not clear or when there is a need for frequent
releases with continuous improvements.
 A spiral approach is utilized when frequent releases are necessary.
 When it is appropriate to create a prototype
 If modifications are possible with the system.

Advantages of the spiral model:

 In scenarios where projects encounter numerous unknown risks throughout
development, the Spiral Model emerges as an ideal choice, owing to its embedded
risk analysis and mitigation strategies incorporated at each phase.
 This model enables accurate incorporation of change requests in requirements
during later phases.
 The Spiral Model prioritizes risk management, aiming to mitigate the effects of
uncertainty and risk throughout the software development process.
 The Spiral Model facilitates several cycles of the software development process,
potentially leading to enhanced software quality and reliability.

Disadvantages of the spiral model:

 Spiral model is way more complex than other SDLC models.
 This model is not suitable for low budget systems.

22
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

 The successful outcome of the project heavily relies on thorough Risk Analysis.
Without a team of highly experienced experts, attempting to develop a project
using this model is likely to result in failure.
 This model can be more time consuming as it require multiple evaluations and
reviews.

23
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Agile. What is agile methodology?

Agile Software Development is a methodology for software development that prioritizes
flexibility, collaboration, and customer satisfaction. It is founded on the Agile Manifesto,
a collection of principles emphasizing individuals and interactions, functioning software,
customer collaboration, and adaptability to change.
Agile Software Development employs an iterative and incremental approach, prioritizing
the swift and regular delivery of a functional product. It emphasizes close collaboration
between the development team and the customer to guarantee that the product aligns with
their requirements and expectations.

Agile techniques are widely employed in instances when project needs are expected to
change or vary over time, as well as when flexibility, collaboration, and quick delivery
are required. Here are several circumstances where Agile is commonly used:

1. Getting tangible value: Agile prioritises delivering concrete value as quickly as

feasible in a project. Customers can benefit from early delivery of promised
benefits as well as the ability to provide timely feedback and revisions.
2. Agile as mind set: Agile is a cultural transformation that prioritises adaptability,
teamwork, and customer satisfaction. It offers team members more authority and
fosters a collaborative and positive work environment.
3. Quick response to requirement changes: agile provide facility that developers
can adjust quickly to ever changing priorities and objectives.
4. Cross-functional teams: Agile encourages the formation of autonomous,
versatile teams that communicate openly, share information efficiently, and
develop a strong sense of cohesion.

These are the main principles of the agile methodologies:

1. Deliver the final output with zero or minimal errors.
2. Fulfil the customer satisfaction with on-time delivery and achieving customer
requirements.
3. Choose face-to-face communication methods for efficient and effective customer
feedbacks and requirement changes.
4. Sticks into short time period with a quality final delivery.
24
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

5. Accepting change in requirements and deliveries despite nearness to delivery

date.
6. Embracing excellence while estimating and improving the progress.

25
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 5values and principles of agile

26
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Advantages of using agile.

1. Agile software development methodology prioritizes human interactions and

collaboration over reliance on tools and processes.

2. This approach encourages a consistent emphasis on enhancing design and

achieving technical excellence.

3. Agile's iterative development process facilitates improvement through prompt

feedback loops.

4. Accelerates the software development timeline, thereby bolstering customer

confidence and trust.

5. Enables swift adaptability to accommodate evolving requirements.

6. Embraces flexibility and adaptability as fundamental principles.

7. Improves quality and reliability by placing emphasis on quality assurance and

continual enhancement.

8. Boosts team confidence and fosters a collaborative, positive, and supportive

workplace culture.

The disadvantages of using agile methodology listed as follows:

1. Agile development emphasizes less documentation and a greater focus on

writing code.

2. The iterative nature of Agile, driven by continuous customer feedback, makes it

challenging to accurately estimate project timelines, outcomes, and budgets.

27
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

3. Early-stage assessment of the effort needed for project completion is difficult in

Agile software development due to its iterative approach.

4. Depending heavily on customer input can result in misdirection if the team

faces ambiguity.

5. New programmers may find it challenging to adapt to Agile environments

where senior programmers typically make most decisions.

6. While Agile offers flexibility, it also poses risks such as scope creep and a lack
of control over project scope.

7. The fast pace of Agile development, characterized by frequent sprints and tight
deadlines, can lead to mental fatigue and increased pressure on team members,
potentially leading to burnout.

8. Agile's less structured approach compared to other methodologies may result in

oversight and inadequate governance.

Here are few agile methodologies explain in follow:

1. Scrum:

Debating whether Scrum fits into the category of a framework, methodology, or Agile
process, and whether it includes a process within its framework, often leads to
unproductive discussions. Scrum is self-described as a straightforward, lean, and
incomplete framework, which is an adequate characterization. It outlines the essential
practices teams should follow to operate efficiently and effectively while adhering to the

28
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Scrum principles of transparency, inspection, and adaptation. While Scrum may not be
suitable for every team, it's worth giving it a chance to see if it aligns with their needs and
objectives.

Figure 6process of scrum

Scrum is now used by organizations, teams, and project managers across all disciplines.
The framework works well for smaller teams tackling work or projects with changing
deliverables, unknown solutions, and frequent interaction with clients or end-users.
Scrum favors incremental and iterative ways of working to deliver functional products
faster and with more frequency.

What are the advantages of using scrum:

 It helps to finish project quick and efficiently.

 Large projects can divide in to easy manageable portions.
 Scrum ensure the efficient of using money and time.
 Suitable for fast moving projects.
 The project team gets clear vision through scrum meetings.
 Developments can code and test them during the sprint review.

What are the disadvantages of using scrum:

29
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

 Scrum frequently results in scope creep since it lacks a specific end-date.

 Project failure becomes more likely when team members lack strong commitment
or cooperation.
 Implementing the Scrum framework in large teams poses challenges.
 Success with the framework often requires experienced team members.
 Daily meetings can occasionally cause frustration among team members.
 The departure of any team member midway through a project can significantly
harm its progress.
 Achieving quality is difficult until the team undergoes rigorous testing.

Kanban.
Kanban, a widely adopted framework for Agile and DevOps software development,
emphasizes real-time capacity communication and complete transparency of work. Work
items are visually depicted on a Kanban board, enabling team members to readily track
the status of each task at any given moment.

Figure 7kanban board

30
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

What are the benefits of using Kanban.

1. Flexible to plan: A kanban team concentrates solely on work that is currently in

process. When the team finishes a job, they choose the next one from the backlog.
The product owner can reprioritize work in the backlog without upsetting the team
because modifications outside of the existing work items have no effect on the team
2. Short time cycle: Cycle time is an important measure for Kanban teams. Cycle time
is the amount of time it takes for a unit of work to progress through the team's
workflow—from the moment it begins to the moment it is sent. By optimising cycle
time, the team can predict the delivery of future tasks.
3. Lower bottleneck chances: Engaging in multiple tasks simultaneously reduces
efficiency, as it results in more frequent context switching, hindering task completion.
Therefore, a key principle of the kanban methodology is to restrict work in progress
(WIP). By imposing limits on work in progress, kanban helps identify bottlenecks in
the team's workflow caused by distractions, resource constraints, or skill gaps.
4. Continuously delivery: Continuous delivery (CD) refers to the process of frequently
distributing work to clients. Continuous integration (CI) is the automated process of
developing and testing code gradually throughout the day. They constitute a CI/CD
pipeline, which is critical for DevOps teams to deploy software quickly while
maintaining high quality.

Disadvantages of using kanban:

1. Oversimplify the complex tasks: Kanban boards can oversimplify complex tasks,
leading to underestimating time and resources, causing delays. The board's brevity
and visual clarity may not capture nuances of tasks, causing incomplete understanding
and mismanagement. Additionally, teams may prioritize completion over quality and
thoroughness, leading to mismanagement.

2. Limited usage for complex tasks: Kanban boards struggle with complex projects
requiring detailed planning and long-term strategy due to their focus on current tasks
and short-term planning. This can lead to disjointed planning and execution, as the

31
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

board lacks long-term planning tools, hindering effective project management in

complex scenarios.

3. Difficult to track long term projects: Kanban boards are not ideal for tracking long-
term progress and results. They are meant to handle present work and short-term
tasks, but they lack systems for evaluating overall project performance over time. This
constraint can be a substantial disadvantage in businesses requiring long-term data
and patterns, such as pharmaceutical research. Inability to measure long-term
development can result in a lack of strategic oversight and make it difficult to assess
project success or failure over time.

4. Suitable for constantly changing projects: Kanban boards may struggle to adapt to
quickly changing project scopes and objectives. In dynamic circumstances where
duties and objectives change often, such as startups or crisis management scenarios,
the board may be unable to adequately represent real-time changes. The requirement
to regularly update and reorganise the board can become inconvenient, detracting
from its primary aim of improving productivity. This inflexibility might impede the
team's capacity to adapt swiftly to changes, thereby affecting project results and team
agility.

5. Over alliance on tool e昀케ciency: There is a risk of over-reliance on Kanban boards'

effectiveness as a project management tool. Teams may believe that simply deploying
a Kanban board is enough for successful project management, ignoring other crucial
elements like team communication, skill levels, and resource availability. This
overreliance can lead to a false feeling of security, in which the appearance of a
Kanban board is associated with efficient project management, even when other
components of the project are deficient. The notion that the instrument would
automatically increase productivity and efficiency might lead to a disregard for the
need of complete project planning and management methods.

32
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Xp programming:
Extreme Programming (XP) stands as an Agile project management methodology that
prioritizes speed and simplicity through short development cycles and minimal
documentation. Its process structure revolves around five core values, five rules, and 12
XP practices, which we'll delve into later in this article. XP, like other Agile
methodologies, organizes software development into iterative work sprints. These
sprints entail completing and reviewing the framework after each cycle, refining it for
optimal efficiency, and adjusting to evolving requirements. Similar to other Agile
methods, XP allows developers to respond promptly to customer stories and adapt in
real-time. However, it distinguishes itself through its disciplined approach, employing
frequent code reviews and unit testing to facilitate rapid changes. Moreover, XP
emphasizes creativity and collaboration, fostering teamwork throughout all stages of
development.

Figure 8exterme programming and loops

33
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

When to use this method:

Given its focus on software development, extreme programming is primarily utilized by
engineering teams and is effective only in specific contexts. To maximize the benefits of
extreme programming, it's advisable to implement it when:
1. When the team is small: because of methodology have a highly collaborative
nature. It greatly works on small companies.

2. Have an adaptable team that can embrace change: Due to its inherent nature,
extreme programming may frequently necessitate the team to discard previous
efforts. Additionally, certain rules permit team members to implement changes at
any point, which could pose challenges if some members perceive such actions as
personal.

3. Well versed in technical aspects of coding: xp programming is not suitable for

beginners. You have to work and change changes quickly.

4. When project demand high quality requirements: When a project requires

superior quality and reliability, XP's focus on continuous testing, refactoring, and
regular code reviews can play a pivotal role in guaranteeing the excellence of the
product.
5.

34
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Advantages of extreme programming:

 The primary advantage of Extreme Programming is that it helps software
development organisations to save money and time on project implementation.
Time savings are attainable since XP focuses on timely delivery of finished goods.

 Extreme Programming teams save a lot of money since they don't utilise excessive
documentation. They frequently handle difficulties by having team conversations.

 Another advantage of Extreme Programming projects is simplicity. Developers

who opt for this methodology craft code that is exceptionally straightforward and
can be enhanced at any time.

 Extreme Programming contributes increasing employee satisfaction and retention

Disadvantages of using extreme programming:

 Some experts argue that Extreme Programming focuses on code rather than
design. That might be a concern because proper design is critical for software
programmes. It helps them sell in the software business.

 Furthermore, lack of documentation in XP projects may not always be

comprehensive. Inadequate documentation of defects could result in the
recurrence of similar bugs in the future.

 Another drawback of XP is its lack of emphasis on measuring code quality

assurance, potentially resulting in defects within the initial codebase.

The lean so昀琀ware development>

Lean Software Development (LSD) is an agile framework centered on maximizing
development efficiency and resource utilization by minimizing waste and delivering only

35
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

essential features required by the product. The Lean approach, synonymous with the
Minimum Viable Product (MVP) strategy, involves releasing a basic version of the
product to the market, gathering user feedback on preferences, dislikes, and desired
additions, and then iterating the product based on this feedback.

Advantages of using LSD

 A streamlined approach enables the delivery of greater functionality within shorter
timeframes.
 By eliminating unnecessary activities, costs can be minimized.
 Empowering the development team to make decisions can enhance morale and
productivity.

Disadvantages of using LSD

 Its scalability is heavily contingent on the capabilities of the team engaged,
rendering it less scalable compared to other frameworks.
 Strong documentation is pivotal, as failure to adhere to it can lead to
developmental errors.

Figure 9lean software development

36
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

When to use LSD

At times, selecting the appropriate methodology to manage a specific project can be
challenging, a familiar scenario for many software developers. While some programmers
opt for the most convenient approach, others stick to methods they are familiar with.
However, the most effective way to choose the methodology for a software development
project is through thorough analysis of its requirements and alignment with the customer's
needs.
 Resource optimization: When it comes to making the most of development time
and resources, Lean approach may help remove waste and optimise operations,
resulting in more effective resource usage.

 Reduce cost: Lean technique is useful when there is a focus on decreasing waste
by removing non-value-added tasks and optimizing processes.

 Customer centred approach: In projects where the aim is to create a solution

that exactly satisfies customer expectations while minimising features that add no
value, Lean methodology's emphasis on delivering only what is necessary is
extremely advantageous.

 Continuous development: Organisations seeking continuous improvement in

their development processes and products might benefit from the Lean
methodology's emphasis on finding and reducing inefficiencies over time.

Advantages of using LSD method

 A streamlined approach facilitates the delivery of greater functionality within
shorter timeframes.
 By eliminating unnecessary activities, costs can be minimized.
 Empowering the development team to make decisions can also bolster morale.

Disadvantages of using LSD method

 Its scalability relies heavily on the capabilities of the team involved, making it less
scalable than other frameworks.
 Comprehensive documentation is essential, as failure to do so could lead to errors.

37
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Traditional vs agile differences

aspects Traditional methodology Agile methodology

Approach Sequential, plan driven Iterative and adaptive
Requirement Detailed requirement upfront,Embraces changing
often rigid requirement, flexible
Process structure Emphasize documentationValue individuals and
and processes interaction over processes
Delivery Often long developmentShort development cycles,
cycles, with one big release with frequent releases.
Feedback Feedback is gathered at theGathered feedback through
end of the project the development phases.
Flexibility Limited flexibility to adapt toHighly adaptable to changing
changes. requirements.
Team collaboration Work with solid teams. Works with cross-functional
teams
Risk management Risk managed by extensiveRisk managed by
planning upfront continuously monitoring and
adaptation
Customer involvement Limited involvement untilCustomer can involve during
end of the project. development process.
Control Emphasizes control over theEmbraces change and focuses
process and scope on delivering value quickly
documentation Comprehensive Minimal documentation,
documentation focuses on working software

 Approach: traditional methodologies provide stability and predictability, while

Agile methodologies shine in adaptability, customer satisfaction, and risk
mitigation.

 Requirement: traditional methodologies prioritize extensive upfront

documentation, detailed planning, and structured processes, while highlighting
clear requirements, defined roles, and strict change control procedures.
Conversely, Agile methodologies focus on iterative and incremental development,
adaptability to changing requirements, frequent customer involvement.

 Process structure: traditional techniques follow a structured and sequential

process, Agile methodologies encourage flexibility, adaptability, and iterative

38
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

development to produce value progressively and respond effectively to changing

needs.

 Delivery: almost all of traditional methodologies used long development cycle to

finish a single phase while agile is use short time period to finish development
phase.

 Feedback: when using a traditional development methods developers cannot

collect customer feedbacks while the project is finished. But in agile method
developers can collect feedbacks after one development phase is finished.

 Flexibility: if developers choose any traditional method, it’s not a good idea to
change any requirement while development process is running. requirements
cannot change while development is on going with traditional method. But agile is
adaptable to changing requirements. It is very suitable to use project that
requirements are changing.

 Team collaboration: Agile approaches prioritise cross-functional teams,

cooperation, self-organization, and regular customer involvement, resulting in a
highly collaborative and adaptable work environment. Traditional techniques,
although still encouraging cooperation, may include more specialised
responsibilities, hierarchical structures, and official communication channels,
which might have an influence on team collaboration.

 Risk management: Agile approaches provide a more dynamic and flexible

approach to risk management, emphasising continual evaluation, adaptability, and
customer participation. Traditional approaches, while still successful, may rely on
more thorough planning, formal change control procedures, and a predictive
approach to risk management.

 Customer involvement: when the project is develop with agile method customer
can involve with the developers to see the progress and see what happens. But
traditional method cannot involve the customer until project is done.

39
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

 Control: Agile techniques encourage control through self-organization, iterative

planning, transparency, and continuous development. Traditional approaches rely
on formal procedures, hierarchical structures, predictive planning, and formal
reviews to manage project execution.

 Documentation: when traditional methods spend to mush time on docs agile

methods are focus to keep minimal documents and deliver working software
quickly.

The similarities between traditional vs agile methodologies

1. Goal: both methodologies works on deliver to high quality final system that fulfil the
customer’s requirements.
2. Project management: Both methodologies incorporate project management practices
like planning, scheduling, and resource allocation to achieve project success.
3. Project monitoring and control: Both methodologies stress the importance of
monitoring project advancement and managing project tasks to uphold adherence to
timelines, budgets, and quality standards.
4. Customer satisfaction: Both techniques eventually strive to meet client objectives
and expectations by providing software products that suit their demands.

40
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Agile vs traditional methodologies

Strengths of traditional methodologies

 Cost effective: developers are very happy to use traditional methods for the
smaller and sequential projects.it take small time period and fewer developer crew
and resources to complete.
 Suitable for remote projects: traditional projects are always use for small and
easy projects there for this method is highly suitable for remote works.as project
can be developed by small group and don’t require much communication to solve
the hurdles.
 Quick time period: Many companies, regardless of their stage in the business
cycle, often face a common challenge: they become entrenched in daily
operations, neglecting activities essential for business growth. This misuse of
resources—money and time—is detrimental. Traditional methodology projects,
due to their sequential nature, rarely require significant changes, enabling timely
delivery.

 Optimized customer satisfaction: Traditional projects are typically

straightforward in meeting client requirements, with all project management
methodologies placing great importance on client satisfaction. The development
process is conducted under the close observation of client needs, ensuring
transparency and prioritization of their demands. When the customer has a clear
understanding of the software needs, the traditional model, with its sequential
approach and clear requirements from the outset, is the optimal choice to pursue.

 Responsible for the quality output: In traditional approaches, project teams

share responsibility for assuring the quality of outputs. Every person, from project
managers to developers to testers, is critical to ensuring and delivering high-
quality results. Project managers are in charge of the project's overall quality
objectives, defining quality standards and developing systems for monitoring and
controlling quality throughout the project's lifespan.

 Specific training is not required: Traditional project management is a flexible

option since it does not require prior expertise or training to begin tasks. The

41
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

conventional technique is likewise a rigorous paradigm; nevertheless, the precise

deliverables and evaluations facilitate management and development.

Weaknesses of the traditional methodologies

 No space for customer involvement: there is no much space for the customer’s
opinion through every phase. Clients are not involved or see the product until
project is done. If the project is not as the client’s requirement it will be the huge
time and resource waste.
 Lack of coordination: Subcontractors work as independent entities rather than as
a unified team. There is a noticeable lack of attempts to promote unity, mutual
collaboration, and project development commitment. The consequent lack of
cooperation causes development delays and may lead to serious consequences.
 No changes: once the system is on the testing phase it is impossible to do any
changes to the system. If developers want to change anything they have to
implement the system again.

Strengths of agile methodology:

 risk involving and challenging development: Customers and stakeholders are
not always certain of their requirements at the outset, and waterfall Software
Development cannot begin until all necessary data and requirements are collected.
That is why the standard method leaves little room for consumer feedback and a
customised end product. It is also an unsuitable paradigm for complicated, large,
and object-oriented project development
 local optimization: Each individual subcontractor prioritizes their own
contributions and skills, without a collective effort to address issues or challenges.
In the absence of teamwork, there is no collaborative approach to resolve
problems.

 High flexibility of the project: Short cycles and rapid iterations allow you to
quickly adjust your project and match it to the demands of your customers. You
do not have to waste time and money providing a completed project that the client
will reject. This makes the development process more adaptable.

42
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

 High customer satisfaction: Oversee the development process. Since Agile

projects are tightly coordinated with the client, he or she has a significant effect on
the development project. Software is produced on a continuous basis in short
cycles, and user input is always considered.

 Continuous interaction: By keeping everyone talking and involved, including

the client, you don't need lots of complicated paperwork or tools. Everyone on the
team feels important and helps make decisions. This encourages new ideas and
actions that lead to better results.

 Continuous quality assurance: Making sure everything is just right. The testing
team needs to check the product quality right from the start of Agile development.
Because the development happens in quick cycles, testing happens all the time,
helping you make a great final product.

weaknesses of agile methodologies.

 Slow development: If your client's requirements are unclear, the development
process will be delayed. Traditional project management's sequential methodology
makes adjustments difficult. The modifications may disrupt the sequence, and the
next development stage will be delayed until the preceding step is finished.

 Required professional crew: Teams in agile initiatives must continually make

significant decisions. This indicates that the project should only be worked on by
experienced software developers, testers, and managers. This software
development style offers extremely few opportunities for newcomers.
 Difficult to plan at early stages: In Agile development, planning is crucial before
the process begins. Before you begin a project, you need analyse your resources,
form teams, and convey an overarching goal to them.
 Lack of necessary documents: Because tasks are frequently finished just in time
for development using the Agile Method, documentation is less extensive, which
might lead to misunderstandings and challenges down the line.

43
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

conclusion
Transitioning from traditional methodologies like Waterfall to Agile methodologies like
Scrum can present challenges, such as mindset shift, role definitions, documentation
overload, change management, and tooling and infrastructure. Waterfall follows a
sequential, linear approach, while Scrum emphasizes flexibility, iterative development,
and collaboration. Team members accustomed to Waterfall's rigid structure may struggle
to adapt to Scrum's dynamic nature.

Role definitions in Waterfall may be unclear, as Scrum promotes self-organizing teams

and shared responsibilities. Documentation overload in Waterfall may create resistance
among stakeholders who rely on detailed documentation for project oversight. Effective
change management strategies are required to address resistance and ensure buy-in from
all stakeholders.

Tooling and infrastructure in Waterfall projects may require investment in new tools and
infrastructure to support agile practices. This can entail additional costs and technical
challenges during the transition phase.

In conclusion, transitioning from Waterfall to Scrum requires a fundamental shift in

mindset, roles, processes, and tools. Careful planning, clear communication, and ongoing
leadership support are essential to ensure a successful transition and reap the benefits of
Agile methodologies like Scrum.

Suitable methodologies
The Scrum methodology, an agile framework renowned for its iterative development
approach, continuous feedback mechanisms, and adaptive planning strategies, stands as a
beacon of efficiency and efficacy in the realm of project management. With its emphasis
on collaboration, transparency, and flexibility, Scrum emerges as an ideal choice for

44
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

projects grappling with shifting requirements and intricate complexities, much like the
scenario presented by the "Auto Cars" taxi reservation system.
At the heart of Scrum lies the concept of iterative development, epitomized by its
hallmark feature—the Sprint. Spanning typically between 2 to 4 weeks, each Sprint
represents a focused effort aimed at delivering a potentially shippable product increment.
For the "Auto Cars" project, this iterative approach can be harnessed to meticulously craft
and refine specific features of the web-based reservation system. Whether it's
streamlining the customer registration process, enhancing booking functionalities,
optimizing driver assignment mechanisms, or fine-tuning location tracking capabilities,
each Sprint presents an opportunity for tangible progress and improvement.

Integral to the Scrum methodology is the notion of continuous feedback—a dynamic loop
of communication and iteration that permeates every aspect of the project lifecycle.
Through regular Sprint reviews and retrospectives, stakeholders ranging from customers
and developers to operators, converge to provide valuable insights into the system's
functionality, usability, and performance. Armed with this feedback, the "Auto Cars"
team can iteratively enhance and fine-tune the system, ensuring that it not only meets but
exceeds the expectations of its end-users.

Adaptive planning does not works for scrum, empowering teams to navigate the ever-
shifting landscape of requirements and priorities with agility and grace. In the case of the
"Auto Cars" project, where customer needs, market dynamics, and technological
advancements are prone to flux, Scrum serves as a compass, guiding the team through the
turbulent seas of uncertainty. By embracing change as a natural and inevitable part of the
development process, the team can adapt their plans and strategies in real-time, ensuring
the timely delivery of value to stakeholders.

Furthermore, Scrum good at cross-functional collaboration—a synergistic dance of

diverse skill sets and perspectives within self-organizing teams. Comprising software
engineers, UI/UX designers, testers, and system administrators, the "Auto Cars"
development team epitomizes the spirit of collaboration, leveraging their collective
expertise to deliver high-quality solutions that resonate with end-users. Through open
communication, shared goals, and mutual respect, team members unite under the banner
of Scrum, embarking on a journey towards excellence and innovation.
45
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

In conclusion, the Scrum methodology emerges as a beacon of hope and resilience for the
"Auto Cars" taxi reservation system, offering a structured and adaptable approach to
project management. By embracing the principles and practices of Scrum, the project
team can navigate the turbulent waters of development with confidence and clarity,
delivering value incrementally and iteratively. In the crucible of Scrum, the "Auto Cars"
project finds not just a methodology, but a philosophy—a philosophy of collaboration,
innovation, and excellence—that will ultimately pave the way for the successful delivery
of a robust and customer-centric web-based reservation system.

46
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Activity 02

What is the feasibility report?

A feasibility report assesses a range of proposed project paths or solutions to determine
their viability. The individual responsible for preparing the report evaluates the feasibility
of various options and ultimately selects their recommendation for the most suitable
solution. Subsequently, they present the feasibility report to their organization and
advocate for their preferred recommendation. The primary objective of a feasibility report
is to assess the viability of various solutions or project paths and select the most optimal
option. The report dissects different approaches to a problem or project, aiding readers in
comprehending the feasibility of each approach. Based on the evaluation presented in the
report, readers can determine whether to adopt the recommended approach. This
comprehensive analysis of different approaches assists organizations in making informed
decisions regarding projects and problems.
Feasibility criteria denote the particular benchmarks or elements employed to evaluate the
practicality of a proposed project or solution. These criteria usually cover a range of
project facets, including technical, economic, operational, legal, and scheduling aspects.
Here are explanations of typical feasibility criteria:

 Technical feasibility: This criterion assesses if the proposed project can be

executed utilizing current technology, infrastructure, and resources. It evaluates
elements like technical prerequisites, compatibility, and scalability.

 Economic feasibility: Economic feasibility scrutinizes the financial viability of

the project, encompassing cost projections, prospective revenues, return on
investment (ROI), and payback duration. It takes into account aspects such as
initial capital outlay, ongoing operational costs, and potential risks.

 Scheduling feasibility: Scheduling feasibility evaluates the project's time

constraints and deadlines. It scrutinizes elements like project schedules,
milestones, critical path analysis, and resource allocation to ascertain if the project
can meet the intended timeline.

47
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

 Cultural Feasibility: Cultural feasibility refers to the assessment of whether a

proposed project or solution aligns with the cultural values, norms, beliefs, and
practices of the stakeholders involved. It evaluates the compatibility of the project with
the existing organizational culture and the broader societal and cultural context in
which it will operate. Cultural feasibility considers factors such as attitudes towards
change, communication styles, decision-making processes, and organizational
hierarchies.

 Legal feasibility: Legal feasibility assesses if the proposed project conforms to

applicable laws, regulations, and industry norms. It takes into account elements
such as permits, licenses, intellectual property rights, and potential legal risks or
liabilities.

 Operational feasibility: Operational feasibility evaluates the practicality and

effectiveness of a proposed project or solution within an organization's current
operational setting. It examines factors like the organization's resources,
capabilities, and preparedness for project implementation, considering elements
such as the availability of skilled personnel, technological infrastructure, and
necessary support systems for successful execution.

48
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 10benefits of feasibility report

Why we need feasibility study report?

The significance of conducting a feasibility study lies in the organization's aspiration to
ensure accuracy before allocating resources, time, or budget to a project. Such a study
could unveil novel concepts capable of substantially altering the project's scope. It's
preferable to make these assessments beforehand rather than embarking on a project only
to discover its infeasibility later on. Undertaking a feasibility study always proves
advantageous to the project, providing both you and other stakeholders with a
comprehensive understanding of the proposed endeavor. Here some key benefits of
conducting a feasibility study report.
 Helps to improve focus of the team members.
 Identify new opportunities.
 Provide valuable information for decision making.
 Narrow downing business alternatives.
 Identifies a valid reason to undertake the project.
 Identify reasons to not to proceed.

49
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

The commencement of a new business often begins with a feasibility study, a crucial
initial phase. This study entails a thorough assessment to determine the likelihood of
success for a proposed business endeavor. Its primary objective is to furnish business
owners with comprehensive insights, aiding them in making well-informed decisions
regarding their new venture. Below are some of the situations that can occur if this
feasibility report is not done.
 Misallocation of resources: Without a comprehensive grasp of the project's
viability, resources such as time, money, and labour may be allocated arbitrarily,
resulting in inefficiencies and waste.
 Risk increasing: Undertaking projects without conducting a feasibility study
increases the likelihood of encountering unexpected challenges and risks that
could have been anticipated and addressed through thorough analysis.
 Legal and regulatory issues: Projects commenced without adequate feasibility
analysis may violate legal or regulatory mandates, resulting in compliance issues
and potential legal ramifications.
 Lack of stakeholder alignment: Without a feasibility study, stakeholders may
hold divergent expectations and objectives, resulting in misalignment and the
possibility of project setbacks.
 Fail to archive the objectives: Initiating projects without a feasibility study may
ultimately result in failure to accomplish their intended objectives, as crucial
factors determining success or failure were not thoroughly evaluated beforehand.

Strengths and weaknesses of feasibility report.

Starting a business requires a feasibility study to assess the idea's feasibility. This study
identifies strengths and weaknesses of the product, team, and business model, as well as
required resources and prospects for success. It should include historical background,
product description, accounting statements, operations, management, marketing research,
policies, financial data, legal requirements, and tax obligations.
Strengths:
 Market Research for Assessing Demand Potential:Conducting market research
to ascertain the genuine demand for the proposed product or service.
 Competitive Analysis and Industry Benchmarking:Analyzing competitors'
strategies and benchmarking against industry leaders.

50
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

 Resource Assessment for Operational Initiation:Assessing the visibility of all

necessary resources for initiating operations.
 Logistical and Tactical Planning for Operations:Developing a logistical or
tactical blueprint outlining production, storage, delivery, and tracking processes.
 Financial Projections and Capital Estimation for Business Start-
Up:Estimating the initial capital required, including expenses, revenue
projections, and future cash flow analysis.
 Legal Structure Selection for Business Establishmen:Deciding on the
appropriate legal framework for the business.
 Human Resource Requirements and Qualifications Identification :Identifying
the quantity and qualifications of the human resources needed.

Weaknesses
 Lack of practically: The report might not provide practical insights or adequately
tackle real-world challenges, leading to a gap between theoretical analysis and
practical application.
 Complexity and jargon: Excessive complexity or an abundance of technical
terminology within the report could make it challenging for stakeholders to
understand, diminishing its utility as a tool for making informed decisions.
 Limited scope: Feasibility assessments can sometimes focus too narrowly on
specific parts of a company proposal, leaving out other key considerations that
could affect its viability.
 Unrealistic projection: It is likely that the report includes too optimistic
projections or assumptions, which might distort decision-making and lead to
erroneous expectations.

51
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Feasibility report of auto car system

52
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

53
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

54
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

55
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

56
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

57
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

58
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

59
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

60
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

61
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

62
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

63
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

64
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

65
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

66
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Conclusion:

The feasibility study report serves as a critical compass for stakeholders navigating the
uncertain terrain of a potential business venture. Its strengths lie in its comprehensive
nature, offering a deep dive into various aspects of the proposed venture and
empowering decision-makers with invaluable insights. Armed with this information,
stakeholders can make well-informed decisions, identify and mitigate risks, and
maximize the chances of success.

However, the report is not without its weaknesses. There's always a risk of incomplete
assessment, potentially leading to overlooked factors or underestimated risks.
Additionally, the subjective nature of the findings and recommendations could introduce
biases that may compromise the accuracy of the conclusions. Moreover, the technical
complexity of the study may pose challenges for stakeholders in fully grasping and
effectively utilizing the provided information.

In conclusion, while the feasibility study report is a powerful tool, acknowledging its
strengths and weaknesses is crucial for optimizing its utility. By addressing limitations
and leveraging strengths, stakeholders can navigate the complexities of the business
landscape more effectively, ultimately enhancing the likelihood of success for the
envisioned venture.

67
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Activity 3
Investigation methods are systematic techniques used to gather, analyze, and understand
data related to a specific subject, problem, or inquiry. They involve data collection,
observation, experimentation, analysis, and interpretation, essential for research, problem-
solving, informed decision-making, and improvement in various fields. There have many
ways to investigate the auto car system. And we have to use most practical and effective
way to do this. Way to investigate are shown below.
 Questionnaires: A questionnaire serves as a research tool comprising a series of
inquiries or prompts designed to gather information from individuals. Typically, it
includes a combination of closed-ended and open-ended questions. Open-ended
questions allow respondents to provide detailed explanations or opinions. The
concept of research questionnaires dates back to 1838, when the Statistical Society
of London introduced them.
 Interviews: An interview is a formal talk between two or more individuals,
usually with one person, the interviewer, asking questions to gather information,
assess qualifications, or determine a candidate's fitness for a job, admittance, or
other objectives. Interviews are widely utilised in a variety of situations, including
employment, university admissions, media, and research, to acquire insights,
make informed judgements, or connect persons. There have about 8 type of
interviews. They are shown as below,
1. structured interviews
2. unstructured interviews
3. situational interviews
4. behavioural interviews
5. stress interviews
6. technical interviews
7. one-to-one interviews
8. video or phone interviews

68
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 11ongoing interview

 Observation: In sociological research, 'observation' denotes a method wherein

researchers analyse the active behaviours of their participants or subjects. This
approach differs from techniques like interviews or questionnaires as observations
focus on studying subjects' actions rather than their verbal responses.

Observation serves as a primary research method, wherein researchers personally

gather the data or information under study. This stands in contrast to secondary
research methods, where researchers analyse pre-existing data collected prior to
their study.
For the investigation the learner is going to choose questionnaire method. Because this is
the most suitable way to collect data from diverse population in short time period. In a
questionnaire, respondents may feel more at ease sharing candid responses to sensitive
questions, as the anonymity of the format removes the pressure of face-to-face
interaction. When talk about cost, this is the most cost-effective way rather than other
methods to collect data from mass population. The leaner believe that this method can be
effective because more questions can be completed in less time and even a person with
less knowledge can simply provide answers.

69
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

What are the functional and non-functional requirements?

Functional requirements.
These specifications outline the essential features the end user requires the system to
provide. They must be integrated into the system as part of the contract, manifesting as
inputs, operations, and expected outputs. Unlike non-functional requirements, these
directly shape the user's experience with the final product. according to the scenario
functional requirements are,

 User Registration: Customers and drivers should be able to register on the web-
based system. Upon registration, they should receive an email with their username
and password.

 Booking Taxis: Customers should be able to book taxis through the website.
Upon booking, they should receive an SMS with the driver's contact information
and vehicle details.

 Driver Rating: Customers should have the ability to rate drivers based on their
experiences with them during trips.
 Ratings: customers can give ratings about their ride experience.
 Manually reserved the taxi: workers of the auto car company can place book the
taxi.
 Cancel the taxi: both customer and driver have access to cancel the ride.
 Notify by the SMS: when operator place the cab customer will receive the SMS
confirming that.
 Assign the closet driver: automatically assign the nearest available vehicle to the
customer by the app.

70
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Non-functional requirements.
Non-functional requirements pertain to the characteristics of a system that delineate its
general operation and behaviour, as opposed to its specific functionalities. They
commonly encompass attributes like performance, security, reliability, scalability,
usability, and compliance. In contrast to functional requirements that dictate the system's
actions, non-functional requirements outline how the system should perform or behave.
according to the scenario non-functional requirements are,
 Usability: The web-based system should be user-friendly and intuitive for both
customers and drivers.

 Reliability: The system should be highly reliable to ensure that bookings are
accurately processed, and customers receive timely notifications.

 Performance: The system should be able to handle a large volume of concurrent

users without experiencing performance degradation.

 Security: The system should implement robust security measures to protect user
data, login credentials, and transactional information.

Product development is a complex process that relies heavily on technical professionals.

Roles in a software development team specify individuals' tasks, provide efficient work
management, and contribute to overall performance. That is why intelligent managers
should organise their teams with precision and strive for a win-win team
composition.now we talk about auto car system development team and their roles and
responsibilities.

1. Project manager: project Manager is in charge of overseeing the whole

development process and ensuring its effective market launch. Their
responsibilities are broad, including developing and implementing plans, as well
as planning and monitoring product key performance indicators. they often
establish an ambitious aim of meeting business objectives through their goods.

71
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

They do this by keeping a close watch on rivals, extensively analysing the market,
coming up with ideas, and managing price strategies.

2. Product owner: The product owner maximizes a product's value by

understanding client needs, de昀椀ning objec琀椀ves, and uni琀椀ng the team's vision.
They o昀琀en juggle various tasks like business strategy, product design, and project
management, dis琀椀nct from the technical focus of project managers and business
analysts. Product owners priori琀椀ze the product's pro昀椀tability and success.
The primary responsibili琀椀es of product owner are:
 Preparing product road map.
 Maintain the backlog.
 Act like a intermediary between developer team and the clients.
 Evaluate the feedbacks.
 Ensure the maximum satisfaction to the client.

3. Engineering manager: Engineering managers in a software development team

act as conductors, interacting closely with each team member to understand
performance dynamics deeply. Their role extends beyond management to
fostering a supportive work environment where team members feel empowered to
contribute ideas and feedback openly. They also refine the team structure when
new developers join and provide coaching. With a strong technical background,
they select optimal engineering solutions for product development, analyze
potential challenges, and utilize technical tools to mitigate them.

4. Software architect: This specialist leads the internal organization of software,

ensuring alignment with product requirements and available resources. Grounded
in business needs, architects define essential technical and functional tools for
product development. They are not just planners; architects actively participate in
development and craft system designs. With a strategic vision, they plan software
enhancement, extension, and new features, navigating complexities to find
optimal technical solutions that seamlessly align with the product.

72
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

5. Software developers: When discussing pivotal roles in a software development

team, programmers play a crucial role. They are the skilled individuals who bring
code to life, utilizing various programming languages, frameworks, and libraries.
With experience, programmers may hold junior (1-3 years), middle (3-5 years), or
senior (7-10+ years) ranks. Additionally, software engineers specialize as full-
stack, front-end, or back-end developers. Collaborating closely with designers,
testers, and product engineers, they contribute to a seamless workflow, combining
expertise to create exceptional software.

6. Interface designers: UX/UI designers play important roles in software

development teams. While UX and UI are different, they work together fluidly,
needing a combination of creativity and technical expertise. UX designers provide
accessibility and user-friendly features by analysing audience behaviour and
creating an intuitive interface. Meanwhile, UI designers concentrate on visual
features, utilising fonts, colours, and animations to create an appealing interface.
Frequently, the UX/UI designer performs both tasks in the software development
process.

7. Testing crew: In software development, testers play an important role in teams. In

a word, they are in charge of making sure the product works properly. During the
testing step, testers take the manual reins and methodically discover any software
faults, bugs, or other difficulties that may irritate an end user. Following product
testing, they create thorough reports with suggestions for improvement. They also
include following responsibilities,
 Review the test plans.
 Map out the testing strategies.
 Asses and analyse the product specification and requirement.

73
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Identifying documentation produced at the different stages

The project of the auto car has divided into few development phases. Each phase does
their own role and its os very important to to the final output. In every phase of the
development prepare special documentation according to that phase to help the project
move forward and guarantee its successful completion. All the document that prepared in
auto car project are shown below,
 Requirement gathering phase: during this development phase user requirement
document is created. To create this special document data has been collected from
clients by interviewing them, surveys and observations. In this document all the
functional and non-functional requirements, specifications and performance
standards of the auto car system are shown.

 System design phase: in this phase system design specification document is

prepared. In this document system components, data base structure and user
interface details are included.

 Feasibility study: After this study assesses the feasibility of introducing a web-
based reservation system for "Auto Cars" in terms of technological, financial,
operational, schedule, cultural, and legal considerations. An examination of the
needs, constraints, risks, and potential benefits is presented.

 Prototype design stage: during this stage prototype documentation is prepared.

In this document wire frames, designs and sketches are included.

 Development stage: in this stage technical document is prepared by the

developer team. In this document special things about codes, comments are
described.

 Quality assurance and testing: test plan and test case id prepared in this stage.
This document describes what are the expectations they expect while they test the
auto car system and what they actually got and what Is the current status of the
system is.

74
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

 Development stage: this is the stage that auto car system bring to life.
Development guide is the document provide in this stage. Installation instruction
and setup steps are provided.

 Maintenance stage: maintenance manual is the document provide in this stage.

This document shows what are the steps follow when problem is occurred.

 User manual: this is the guide that gives to final user of the auto car system. This
document include almost every thing A to Z user should know. It does not matter
he is stranger or not to this kind of systems. This document is perfect guide to the
system.

Activity 04

How the design meets user and system requirements

Explaining how design fulfils system requirements entails demonstrating how the
proposed design features and capabilities of the system fit the demands and objectives
defined in the system requirements.
1. Identify the system requirements: being by clearly outlining the key
requirements of the system. These requirements should include functional and
non-functional requirements of the auto cars system. If the developers are
identified it clearly they have done great job. It will lead to great final output.

2. Scrum methodology: The Auto Cars project utilized the Scrum framework, an
agile methodology emphasizing iterative development, ongoing feedback, and
flexible planning, in its system design process. Scrum promotes collaboration,
transparency, and adaptability, making it well-suited for complex projects with
evolving requirements.

75
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

3. Functionality demonstration: Provide specific instances or demonstrations of

how the design transforms system requirements into practical functions. This
might include walkthroughs of user interfaces, wireframes, or prototypes that
demonstrate how users interact with the system and complete tasks as required.

4. Client involvement: Scrum encouraged clients to provide feedback on needs and

priorities at all stages of the design process. Consistent sprint reviews and demos
engaged stakeholders and gathered feedback to ensure consistency with project
objectives and user needs. Scrum's iterative structure made it easier to adapt and
improve on a constant basis, which contributed to the Auto Cars project's overall
success.
The development team of the auto car system have chosen to use scrum method because
of the constantly changing requirements of the clients. That is the main reason for the
choose this method. They can produce high quality final project and highly satisfied
customers at end of the projects.

system aligning with user requirements.

 user requirement documentation: to make leading taxi app developers have to
list down what they wants from the taxi app and what are the problems clients
currently suffer and they have to give answers for those questions.developers list
all the things the app must do, like letting users sign up, book a taxi, pay for rides,
rate drivers, and get help if they need it.

 User requirement analysis: Begin by detailing the process for gathering and
analysing user needs. This might include approaches like interviews, surveys,
focus groups, or user observation sessions. analysing the user requirement is most
important to understand the what Is the actually client want to build.

 System design and development: after understanding the user requirements

developing team build the system and test it for better performance and less bugs.
after clear understanding of user requirement, what actually client is wants from
final project they have developed. For instance, users might prioritize features like

76
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

ease of use, quick booking, real-time tracking, secure payments, and driver
ratings.

 User testing and validation: after implement the system before deliver the final
product there have a testing stage. In this stage all the features of the system is
getting tested. All the bugs are getting fixed. This phase ensures system has no
bugs and works perfectly. User acceptance testing (UAT) for a system typically
involves multiple stages and participants to ensure the app meets the requirements
and expectations of its users. For this test actual final system user is participated.

 User training and support: Users are supplied with thorough training materials
and continuous assistance to ensure that they can utilise the auto cars app
properly. Training tools include user manuals that cover all parts of the software,
online tutorials for easy learning, in-app tips for real-time assistance, and
interactive demos for hands-on practice. Training is provided through in-person
workshops, online webinars, and self-paced e-learning courses. Ongoing support
consists of a help desk for user inquiries, a knowledge base for FAQs and
tutorials, and community forums for peer-to-peer support and interaction. This
strategy guarantees that users can learn, utilise, and debug the app with
confidence.

 Feedback and continuous improvement: Feedback mechanisms such as in-app

forms, rating systems, customer support interactions, and surveys gather user
input for analysis. Feedback is regularly reviewed, sentiment analysed, and
quantitatively assessed to prioritize enhancements. Priorities are determined by
impact, user needs, and strategic goals. Agile practices ensure continuous
improvement, with feedback loop closure through transparent communication of
implemented changes to users.

Effectiveness of design artifacts of Auto Cars system

During the design phase of the Auto Cars system, a diverse range of design
artifacts were created to convey design decisions, processes, and interactions.
These artifacts played a crucial role in fostering collaboration, gathering input,
and ensuring alignment among project participants, including development teams,
project managers, and stakeholders.

77
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

 System diagrams: The system architecture diagrams gave a high-level overview

of the Auto Cars system's components and structure. These diagrams effectively
demonstrated the relationships between several modules by emphasising critical
aspects such as driver assignment, booking administration, SMS alerts, and user
authentication. This transparency encouraged talks about scalability and
dependability, as well as helping stakeholders understand the system's underlying
underpinnings.

 Prototypes and wireframes: Prototypes and wireframes were vital in showing

the Auto Cars system's user interface and interactions. These artefacts
demonstrated how the driver selection, SMS alerts, and booking processes
functioned. Stakeholders may provide valuable input on usability, navigation, and
aesthetics by visualising the user experience, resulting in iterative improvements
and modifications.

 Design specification: The design specifications detailed the Auto Cars system's
functional requirements, data structures, and behaviour. They provided
development teams with a detailed guide to help them install features consistently
and properly. These specifications ensured consistency between technical
implementation and stakeholder expectations by describing design decisions and
constraints.

 Alignment to the objective development: All things considered, the Auto Cars
system's design artefacts were critical in integrating development operations with
project goals. They made it feasible for stakeholders to view the completed result.
Identify potential difficulties early on and assign development work in a logical
manner. Because of this alignment, the development lifecycle became more
productive and efficient, resulting in the production of a system that met both user
needs and operational objectives.

Test case of the auto car system

78
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

This table show how the developers are test the system and what are the things
they test and what are the results they got.

Test description test Excepted result status

User registration Give user details User successfullypass
and proceed to registered
register
User login Enter login details User logged in topass
and login system.
Show available cabs Display available Show available pass
taxi nearby taxies near
customer.

Book a taxi Confirm booking Successfully reservepass

with driver details. booking.
Cancel booking Cancel the reserved Remove taxi frompass
taxi if needed booking
View driver details Display driver Display driver pass
profile if needed details with his
reviews
Payment processing Select method and Payment is pass
do payments successful
Assistant help Contact live agent if Agent contacted pass
needed successfully

79
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 12use case diagram of the auto car system

Figure 13dfd level 0 diagram of the auto car system

80
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 14entiity related diagram of auto car system

81
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 15flow chart check cab availability

82
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 16flow chart of rating and tip payment

83
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 17flow chart login process

Figure 18application booting window

84
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 19login or signup window

Figure 20destination selecting window

85
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 21taxi selecting window

Figure 22give reviews and tips

86
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 23driver login page

Figure 24driver dashboard and location of the client

87
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 25selecting payment method and amount

Figure 26driver location and availability update

88
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Feedback form of the autocar system

Figure 27feedback forms of the system

89
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

90
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

These are the responses developer team got

Figure 28responses for the 1st question

Figure 29responses for second one

91
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

92
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Figure 30other comments and people who give the feedback

93
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Reference:

Reaiche, C. and Papavasiliou, S. (2022) The traditional, sequential methodologies,

Management Methods for Complex Projects. Available at:
https://jcu.pressbooks.pub/pmmethods/chapter/traditional-sequential-
methodologies/#:~:text=Traditional%20or%20sequential%20project
%20management,execution%2C%20monitoring%2C%20and%20closure.
(Accessed: 16 April 2024).

11 advantages & 9 disadvantages of Traditional Project Management (2019) WADIC.

Available at: https://wadic.net/traditional-project-management-advantages-
disadvantages/ (Accessed: 17 April 2024).

Lutkevich, B. and Lewis, S. (2022) What is the waterfall model? - definition and guide,
Software Quality. Available at:
https://www.techtarget.com/searchsoftwarequality/definition/waterfall-model
(Accessed: 17 April 2024).

Waterfall model: What is it, when and how to use it? (2023) actiTIME. Available at:
https://www.actitime.com/project-management/what-is-waterfall-model#when-to-
use-the-waterfall-mode (Accessed: 17 April 2024).

GfG (2024) Spiral model - software engineering, GeeksforGeeks. Available at:

https://www.geeksforgeeks.org/software-engineering-spiral-model/ (Accessed: 17
April 2024).

GeeksforGeeks (2024) Agile Software Development - software engineering,

GeeksforGeeks. Available at: https://www.geeksforgeeks.org/software-engineering-
agile-software-development/?ref=lbp (Accessed: 18 April 2024).

Simplilearn (2024) What is Agile: Understanding Agile Methodology and principles in

software development?, Simplilearn.com. Available at:
https://www.simplilearn.com/tutorials/agile-scrum-tutorial/what-is-agile (Accessed:
19 April 2024).

Chandana (2024) Scrum project management: Advantages and disadvantages,

Simplilearn.com. Available at: https://www.simplilearn.com/scrum-project-
management-article (Accessed: 19 April 2024).

Atlassian (no date) Kanban - A brief introduction, Atlassian. Available at:

https://www.atlassian.com/agile/kanban (Accessed: 19 April 2024).

Raymond, D. (2023) Kanban boards: Top 10 cons, disadvantages & limitations,

ProjectManagers.net. Available at: https://projectmanagers.net/kanban-boards-top-
10-cons-disadvantages-limitations/ (Accessed: 19 April 2024).

94
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Kukhnavets, P. (2021) Disadvantages and advantages in extreme programming, Hygger.

Available at: https://hygger.io/blog/disadvantages-and-advantages-of-extreme-
programming/ (Accessed: 19 April 2024).

Lean Software Development (2023) What is Lean Software Development? Available at:
https://www.productplan.com/glossary/lean-software-development/ (Accessed: 19
April 2024).

The secrets of lean software development (no date) mDevelopers. Available at:
https://mdevelopers.com/blog/what-is-lean-software-development (Accessed: 19
April 2024).

(No date) What is a feasibility report? (definition and template) | indeed.com. Available
at: https://www.indeed.com/career-advice/career-development/feasibility-report
(Accessed: 19 April 2024).

Kukhnavets, P. (2021) Agile Strengths and weaknesses, Hygger. Available at:

https://hygger.io/blog/agile-strong-and-weak-points/#agile-model-strengths
(Accessed: 22 April 2024).

Omar (2016) Feasibility Study Pros & cons for Small & Medium Sized Enterprises, SME
Consulting. Available at: https://smecastle.com/2016/01/22/feasibility-study-pros-
cons/ (Accessed: 19 April 2024).

Bhat, A. (2023) Questionnaires: Definition, Advantages & Examples, QuestionPro.

Available at: https://www.questionpro.com/blog/what-is-a-questionnaire/
(Accessed: 21 April 2024).

Puri, G. (2024) What is interview: Meaning, types and formats, Naukri’s Official Blog.
Available at: https://www.naukri.com/blog/what-is-interview/#meaning-of-
interview (Accessed: 21 April 2024).

Sociology (no date) Vaia. Available at: https://www.vaia.com/en-us/explanations/social-

studies/theories-and-methods/observation/ (Accessed: 21 April 2024).

GeeksforGeeks (2024) Functional vs Non Functional Requirements, GeeksforGeeks.

Available at: https://www.geeksforgeeks.org/functional-vs-non-functional-
requirements/#functional-requirements (Accessed: 21 April 2024).

95
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

11 advantages & 9 disadvantages of Traditional Project Management (2019) WADIC.

Available at: https://wadic.net/traditional-project-management-advantages-
disadvantages/ (Accessed: 22 April 2024).

30, T.K.O. et al. (no date) Top 25 back-end web development tools, Digital Acceleration
Company. Available at: https://www.netguru.com/blog/top-back-end-web-
developement-tools#:~:text=Backend%20development%20is%20about
%20server,and%20the%20web%20servers%20themselves. (Accessed: 23 April
2024).

11 key roles in a software development team (2024) Alcor BPO. Available at:
https://alcor-bpo.com/10-key-roles-in-a-software-development-team-who-is-
responsible-for-what/#:~:text=A%20software%20development%20team%20is
%20made%20up%20of%20these%20key,%2C%20and%20team%20%2F%20tech
%20leads. (Accessed: 23 April 2024).

LEARN XAMPP with online courses and programs (no date) edX. Available at:
https://www.edx.org/learn/xampp#:~:text=XAMPP%2C%20which%20stands
%20for%20Cross,and%20Linux%20(LAMP)%20environments. (Accessed: 23
April 2024).

96
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

Grading Criteria Achieved Feedback

LO1 Evaluate the strengths and weaknesses of the

traditional and agile systems analysis methodologies.

P1 Discuss the strengths and weaknesses of the tradi琀椀onal

and agile systems analysis methodologies.

M1 Compare and contrast the strengths and weaknesses of

the tradi琀椀onal and agile systems analysis methodologies with
reference to a speci昀椀c business-related problem.

LO2 Produce a feasibility study for a system to be developed

to solve a business-related problem.

P2 Produce a feasibility study for a system for a

business related problem.

M2 Evaluate the importance of the feasibility criteria in the

97
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

systems investigation for the business related

problem.

LO1 & LO2

D1 Cri琀椀cally evaluate the strengths and weaknesses of
the tradi琀椀onal and agile systems methodologies and
feasibility study in solving a speci昀椀c business-related problem.

LO3 Assess systems analysis methodologies to e昀昀ec琀椀vely

solve business-related problems

P3 Review a system using a suitable methodology for a

business-related problem.

M3 Asses the effectiveness of the methodology used in

providing a solution for a given business context.

LO4 Design a system to meet user and system

Requirements

98
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])

 lOMoARcPSD|48216755

P4 Design a fully functional system to meet user and

system requirements for the business-related
problem.

M4 Assess the effectiveness of the system design, with

reference to the methodology used and how the design
meets user and system requirements.

LO3 & 4
D2 Justify the choice of the methodology used in
the context of the business problem.

99
K.Chanuka nisal System analysis & design

Downloaded by ??? ??? ([email protected])