SAD Sample

lOMoAR cPSD| 26861203
A-004557-1655226970461-162633-System Analysis Design

(M.A
Network System (ESOFT Metro Campus)
Studocu is not sponsored or endorsed by any college or university

Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)
INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title HND in Computing
Assessor Internal Verifier

Unit 34: System Analysis & Design
Unit(s)
Automated system for E-Solutions Private Limited

Assignment title
Student’s name
List which assessment criteria Pass Merit Distinction
the Assessor has awarded.
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria awarded match

those shown in the assignment brief? Y/N
Is the Pass/Merit/Distinction grade awarded
justified by the assessor’s comments on the Y/N
student work?
Has the work been assessed
accurately? Y/N
Is the feedback to the student:

Give details:
• Constructive? Y/N
• Linked to relevant assessment criteria? Y/N
• Identifying opportunities for Y/N
improved performance?
• Agreeing actions? Y/N
Does the assessment decision need
Y/N
amending?
Assessor signature Date
Internal Verifier signature Date

Programme Leader signature (if required) Date
Confirm action completed

Remedial action taken
Give details:
Assessor signature Date
Internal Verifier
Date
signature
Programme Leader
Date
signature (if required)
1|Page
M.A.M. Akram System Analysis & Design
Higher Nationals - Summative Assignment Feedback Form

Student Name/ID
Unit Title Unit 34: 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 traditional and agile systems analysis methodologies
Pass, Merit & DistinctionP1 M1 D1

Descripts
LO2 Produce a feasibility study for a system for a business-related problem

Pass, Merit & DistinctionP2 M2
Descripts
LO3 Analyse their system using a suitable methodology.

Pass, Merit & DistinctionP3 M3 D2
Descripts
LO4 Design the system to meet user and system requirements.

Pass, Merit & DistinctionP4M4 Descripts
Grade: Assessor Signature: Date:
Resubmission Feedback:
Grade: Assessor Signature: Date:
Internal Verifier’s Comments:
Signature & Date:
* Please note that grade decisions are provisional. They are only confirmed once internal and external moderation has taken place and
grades decisions have been agreed at the assessment board.
2|Page
Pearson Higher Nationals in

Computing
Unit 34: Systems Analysis & Design
Assignment 01
General Guidelines
1. A Cover page or title page – You should always attach a title page to your assignment. Use
previous page as your cover sheet and make sure all the details are accurately filled.
2. Attach this brief as the first section of your assignment.
3. All the assignments should be prepared using a word processing software.
4. All the assignments should be printed on A4 sized papers. Use single side printing.
5. Allow 1” for top, bottom, right margins and 1.25” for the left margin of each page.
Word Processing Rules
1. The font size should be 12 point and should be in the style of Time New Roman.
2. Use 1.5 line spacing. Left justify all paragraphs.
3. Ensure that all the headings are consistent in terms of the font size and font style.
4. Use footer function in the word processor to insert Your Name, Subject, Assignment No,
and Page Number on each page. This is useful if individual sheets become detached for any
reason.
5. Use word processing application spell check and grammar check function to help editing
your assignment.
Important Points:
1. It is strictly prohibited to use textboxes to add texts in the assignments, except for the
compulsory information. eg: Figures, tables of comparison etc. Adding text boxes in the body
except for the before mentioned compulsory information will result in rejection of your
work.
2. Avoid using page borders in your assignment body.
3. Carefully check the hand in date and the instructions given in the assignment. Late
submissions will not be accepted.
4. Ensure that you give yourself enough time to complete the assignment by the due date.
5. Excuses of any nature will not be accepted for failure to hand in the work on time.
6. You must take responsibility for managing your own time effectively.
7. If you are unable to hand in your assignment on time and have valid reasons such as illness,
you may apply (in writing) for an extension.
8. Failure to achieve at least PASS criteria will result in a REFERRAL grade.
9. Non-submission of work without valid reasons will lead to an automatic RE FERRAL. You will
then be asked to complete an alternative assignment.
10. If you use other people’s work or ideas in your assignment, reference them properly using
HARVARD referencing system to avoid plagiarism. You have to provide both in-text citation
and a reference list.
11. 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
Student Declaration
I hereby, declare that I know what plagiarism entails, namely, to use another’s work and to present
it as my own without attributing the sources in the correct form. I further understand what it
means to copy another’s work.
1. I know that plagiarism is a punishable offence because it constitutes theft.

2. I understand the plagiarism and copying policy of 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 attribute the source in the correct
way.
5. I acknowledge that the attachment of this document signed or not, constitutes a binding
agreement between myself and Pearson , UK.
6. I understand that my assignment will not be considered as submitted if this document is not
attached to the assignment.
Student’s Signature: Date:

(Provide E-mail ID) (Provide Submission Date)
Higher National Diploma in Computing

Assignment Brief
Student Name /ID Number
Unit Number and Title Unit 4: Systems Analysis & Design
Academic Year 2021/22
Unit Tutor
Assignment Title Automated system for E-Solutions Private

Limited
Issue Date
Submission Date
IV Name & Date
Submission format
The submission should be in the form of an individual written report written in a concise,
formal business style using single spacing and font size 12. You are required to make use
of headings, paragraphs, and subsections as appropriate, and all work must be
supported with research and referenced Please provide in-test citations, 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 for a business-related problem.
LO3 Analyse their system using a suitable methodology.
LO4 Design the system to meet user and system requirements.

Assignment Brief and Guidance:
*Please note that assignment guidance is for reference only and should be more specific
in detail to meet customized needs.
Assignment brief
Case study
The new automated system is designed to replace the current, manual, error-prone
process of E-Solutions private Limited. The automation of existing process is to reduce
the company’s expenses and enhance the productivity significantly. This transformation
also would support for:
1) Successful teams working
2) Completing projects on time and within budget due to a better understanding of
system requirements and tasks to be completed
3) Starting projects on time through automated project scheduling system.
In the proposed system, the Project director creates a project and a “project profile” for
each project. The creation of the project profile includes identification of project
employee costs, the assignment of tasks to the project, and the assignment of a project
manager. The project profile is consisted of project id, project personnel cost, a list of
tasks assigned, and the project manager. The Project director also creates the teams for
a given project, assigns employees to the teams, and assigns a team leader. The Project
manager is responsible for assigning tasks to various teams working on the projects(s).
The Team Leader assigns tasks to the team members.
Additional functionality includes:

• Produce and update information about different software projects, project teams,
specific team member assignments and team skills.
• Perform function point analysis to identify the personnel cost of the project and
provide information to generate invoices upon completion of project phases.
• Monitor projects and identify completed tasks and ongoing tasks of each project.
Activity 01
Discuss traditional and agile system analysis methodologies used in the industry by
comparing and contrasting the strengths and weaknesses of them. Critically evaluate
two methodologies by referring to the examples to support your answer.
Activity 2
Produce a feasibility report for the scenario given above and assess the importance of
feasibility criteria used for the system investigation. Critically evaluate the strengths and
weaknesses of feasibility study with relevant to the proposed solution.
Activity 3
Analyse and review the system requirements of the proposed solution given in the
scenario using a suitable methodology. Functional and non-functional requirements of
the system should be clearly mentioned. Assessment of the effectiveness and suitability
of the chosen methodology should be provided with proper justifications.
Activity 4
Produce a system design specification for the above scenario and assess the
effectiveness of your design and the methodology used with reference to how it meets
the user requirements.
Your system design specification should include architectural design, interface design,
database design, and program design.
10 | P a g e
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 traditional

and agile systems analysis methodologies.
M1 Compare and contrast the strengths and weaknesses of

the traditional and agile systems analysis methodologies.
LO2 Produce a feasibility study for a system for a business-

related problem.
P2 Produce a feasibility study for a system for a

business related problem.
11 | P a g e
M2 Evaluate the relevance of the feasibility criteria on

the systems investigation for the business related
problem.
LO1 & LO2

D1 Critically evaluate the strengths and weaknesses of the
traditional and agile methodologies and feasibility study.
LO3 Analyse their system using a suitable

Methodology
P3 Review a system using a suitable methodology for a

business-related problem.
M3 Analyse the effectiveness of the methodology used in
providing a solution for a given business context.
12 | P a g e
LO4 Design the system to meet user and system

Requirements
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 & LO4

D2 Justify the choice of the analysis methodology used in
the context of the business problem.
Downloaded by umair faisal Ismalic (umairfaisalislamic@gmail.com)

Acknowledgement
In performing my assignment, I had to take the help and guideline of some respected persons, who
Deserve my greatest thanks. The completion of this assignment gives us much Pleasure. I would
like to Show our gratitude Safran Subject lecture, in ESOFT metro campus, Trincomalee branch for
giving us a good guideline for assignment throughout numerous consultations. I would also like to
expand my deepest gratitude to all those who have directly and indirectly guided me in writing this
assignment.
Thanking you,
M.A.M. AKRAM
HND in Computing and Application Development,
15Batch,
ESOFT Metro Campus Trincomalee
M.A.M. Akram System Analysis & Design 14 | P a g e

Contents
Acknowledgement .......................................................................................................................................... 14
TASK 01 ........................................................................................................................................................... 21
Traditional Software Development Methodology.......................................................................................... 21
The Traditional Waterfall Approach ............................................................................................................... 21
Diagram of Waterfall model ........................................................................................................................... 22
Examples of Waterfall Model ......................................................................................................................... 22
Advantage of waterfall model ........................................................................................................................ 24
Disadvantages of waterfall model .................................................................................................................. 24
When to use the waterfall model ................................................................................................................... 25
Prototyping model .......................................................................................................................................... 26
Steps of the prototyping model...................................................................................................................... 27
Types of prototype models ............................................................................................................................. 27
Advantages of the prototyping model............................................................................................................ 28
Disadvantages of the prototyping model ....................................................................................................... 28
Spiral Model .................................................................................................................................................... 29
When to use Spiral Model? ............................................................................................................................ 30
Each phase of the Spiral Model is divided into four quadrants ..................................................................... 30
Risk Handling in Spiral Model ......................................................................................................................... 31
Advantages of Spiral Model ............................................................................................................................ 31
Disadvantages of Spiral Model ....................................................................................................................... 31
Agile methodology .......................................................................................................................................... 32
4 Values of Agile ............................................................................................................................................. 33
12 Principles of Agile....................................................................................................................................... 34
Why chooses agile? ........................................................................................................................................ 35
Agile methodologies ....................................................................................................................................... 35
Scrum Methodology ....................................................................................................................................... 36
Advantages of agile scrum methodology ....................................................................................................... 37
Advantages of agile scrum methodology ....................................................................................................... 37
different roles in agile scrum methodology ................................................................................................... 38
differences between scrum and agile............................................................................................................. 38
Extreme Programming (XP) ............................................................................................................................ 39
The process and roles of extreme programming ........................................................................................... 41

Principles of extreme programming ............................................................................................................... 42

Extreme programming advantages ................................................................................................................ 42
Extreme programming disadvantages ............................................................................................................ 42
Comparison of Extreme programming vs Scrum ............................................................................................ 43
Adaptive Software Development (ASD).......................................................................................................... 43
The main characteristics of ASD ..................................................................................................................... 44
Advantages of adaptive software development ............................................................................................ 44
Disadvantages of adaptive software development ........................................................................................ 44
Dynamic Software Development Method (DSDM) ........................................................................................ 45
Key principles of the dynamic systems development method....................................................................... 46
Advantages of dynamic systems development method ................................................................................ 46
Disadvantages of the dynamic systems development method ...................................................................... 47
Kanban ............................................................................................................................................................ 47
The five stages of feature driven development.............................................................................................. 48
Advantages of Kanban method ...................................................................................................................... 49
Disadvantages of Kanban method .................................................................................................................. 49
Kanban Practices............................................................................................................................................. 49
TASK 02 ........................................................................................................................................................... 51
Feasibility Study .............................................................................................................................................. 51
Steps in a Feasibility Study.............................................................................................................................. 52
1. Conduct a Preliminary Analysis............................................................................................................... 52
2. Prepare a Projected Income Statement ..................................................................................................... 52
3. Conduct a Market Survey, or Perform Market Research ........................................................................... 52
4. Plan Business Organization and Operations ............................................................................................... 52
5. Prepare an Opening Day Balance Sheet ..................................................................................................... 53
6. Review and Analyze All Data....................................................................................................................... 53
7. Make a Go/No-Go Decision ........................................................................................................................ 53
Contents of a Feasibility Report...................................................................................................................... 53
Best Practices for a Feasibility Study .............................................................................................................. 54
Types of Feasibility Study ............................................................................................................................... 54
1. Technical feasibility................................................................................................................................. 54
2. Financial feasibility.................................................................................................................................. 55
3. Market feasibility .................................................................................................................................... 55
4. Organizational feasibility ........................................................................................................................ 55

1) Technical Feasibility ................................................................................................................................ 55

2) Financial Feasibility ................................................................................................................................. 56
3) Market Feasibility Study ......................................................................................................................... 56
4) Organizational feasibility ........................................................................................................................ 56
5) Economic Feasibility Study...................................................................................................................... 56
6) Operational Feasibility ............................................................................................................................ 57
7) Schedule Feasibility................................................................................................................................. 57
This evaluation is critical for project success; after all, if a project is not completed on time, it will fail. An
organization predicts the amount of time it will take to execute a project when scheduling feasibility.......... 57
6 Elements of a Good Feasibility Study........................................................................................................... 58
1) The project scopes .................................................................................................................................. 58
2) The current analysis ................................................................................................................................ 58
3) The requirements ................................................................................................................................... 58
4) The approach .......................................................................................................................................... 58
5) Evaluation ............................................................................................................................................... 59
6) Review..................................................................................................................................................... 59
Importance of Feasibility Study ...................................................................................................................... 59
key benefits of conducting a feasibility study ................................................................................................. 60
Benefits of a Feasibility Study ......................................................................................................................... 61
What is a feasibility report? ............................................................................................................................ 61
What is the purpose of a feasibility report? ................................................................................................... 61
Important Features of a Basic Feasibility Report ............................................................................................ 62
Introduction .................................................................................................................................................... 62
Background and context ................................................................................................................................. 63
Evaluation criteria ........................................................................................................................................... 63
Evaluation of solutions.................................................................................................................................... 63
Conclusion....................................................................................................................................................... 64
Final recommendation .................................................................................................................................... 64
TASK 03 ........................................................................................................................................................... 65
3. Data Analysis ........................................................................................................................................... 67
4. Data Representation ............................................................................................................................... 67
4.1 Mind Mapping .......................................................................................................................................... 67
5.1 Nominal cluster Technique ....................................................................................................................... 68
5.2 Observation .............................................................................................................................................. 68

5.3 Quality Function Deployment ................................................................................................................... 68
5.4 User Stories ............................................................................................................................................... 68

6. Context Diagram ..................................................................................................................................... 69
7. Protypes .................................................................................................................................................. 69
Identify user and system requirements/ constraints for the system User Requirements ............................. 70
1. User requirements for E-Solutions Private Limited ................................................................................ 70
2. System Requirement for E-Solutions Private Limited............................................................................. 71
2.1 Hardware Requirement for E-Solutions Private Limited .................................................................... 71
Software Requirement for E-Solutions Private Limited.................................................................................. 71
3. Functional Requirement ......................................................................................................................... 72
Non-Functional Requirements........................................................................................................................ 73
Non-Functional Requirements for E-Solutions Private Limited...................................................................... 74
1. Interactive and Good Performance ........................................................................................................ 74
Create user stories for identified for user requirements. .............................................................................. 75
User story for E-Solutions Private Limited ...................................................................................................... 75
Computer function language .......................................................................................................................... 75
Backend Technology ....................................................................................................................................... 58
B Identify and explain the most suitable methodology for the analysis of the system. Answer should cover
features, advantages, and disadvantages of the selected methodology .......................................................... 58
1. Model Driven Analysis ............................................................................................................................ 58
2. Accelerated Analysis ............................................................................................................................... 59
3. Prototype Methodology ......................................................................................................................... 59
Advantages of Prototype Model ..................................................................................................................... 59
Disadvantages of Prototype Model ................................................................................................................ 60
Activity 3.2 ...................................................................................................................................................... 60
Explain how the selected methodology in task 3.1 c) can be used to improve the effectiveness of the analysis
stage .................................................................................................................................................................. 60
Prototyping Methodology for E-Solutions Private Limited ............................................................................. 60
Activity 3.3 ...................................................................................................................................................... 59
Explain reasons to select the methodology in task 3.1 for the given scenario. Provide evidence to support
your ideas and points of view ........................................................................................................................... 59
Reduced time and costs .................................................................................................................................. 59
Improved and increased user involvement .................................................................................................... 59
TASK 04 ........................................................................................................................................................... 61
Activity 4.1 ...................................................................................................................................................... 61
Provide the system specification for the above scenario using the methodology you selected. Documentation
should include ERD, Prototyping techniques, and flow charts for important functionalities, release plan and
tools used .......................................................................................................................................................... 61
Activity 4.2 ...................................................................................................................................................... 62
Explain how the system design can be used to improve the effectiveness of the selected methodology
relevant to the above scenario ......................................................................................................................... 62
Key features of agile methodology ................................................................................................................. 62
Quality............................................................................................................................................................. 62
Visibility........................................................................................................................................................... 63
Early identification and resolution of issues ................................................................................................... 63
Iterative releases, Communication, continuous integration........................................................................... 63
More Enjoyable ............................................................................................................................................... 64
Transparency .................................................................................................................................................. 64
Early and Predictable Delivery ........................................................................................................................ 64
Predictable Costs and Schedule ...................................................................................................................... 64
System design documentation ....................................................................................................................... 65
Architectural design ........................................................................................................................................ 65
The mode of activation ................................................................................................................................... 65
Verification test program ................................................................................................................................ 66
Conduct a survey to collect feedbacks from users and explain the level of satisfaction based on user and
system requirements in the conclusion Feedbacks from Users ........................................................................ 66
Conclusion....................................................................................................................................................... 69
Figure 1 Diagram of Waterfall model................................................................................................ 22

Figure 2 Prototyping model .............................................................................................................. 26
Figure 3 Spiral Model ........................................................................................................................ 29
Figure 4 Agile methodology .............................................................................................................. 32
Figure 5 Scrum Methodology............................................................................................................ 36
Figure 6 Extreme Programming (XP)................................................................................................. 40
Figure 7 Adaptive Software Development (ASD) .............................................................................. 43
Figure 8 Dynamic Software Development Method (DSDM) ............................................................. 45
Figure 9 Kanban ................................................................................................................................ 47
Figure 10 Feasibility Study ................................................................................................................ 51
Figure 11 User case Diagram for E-Solutions Private Limited ........................................................... 73
Figure 12 ER Diagram for E-Solutions Private Limited ...................................................................... 61
Figure 13 Feedback from 01 ............................................................................................................. 66
TASK 01
Traditional Software Development Methodology
Traditional software development approaches are based on the software development lifecycle's
pre- organized phases and stages. The development flow is unidirectional here, with requirements
leading to design, development, testing, and maintenance. Each phase of a traditional technique,
such as the Waterfall model, has precise deliverables and detailed documentation that has gone
through a thorough review process.
List of traditional methodology
a. Waterfall model
b. Prototyping model
c. Spiral model
The Traditional Waterfall Approach
The first Process Model to be introduced was the Waterfall Model. A linear-sequential life cycle
model is another name for it. It is really easy to comprehend and use. Each phase must be finished
before the next can begin in a waterfall model, and the phases do not overlap. The Waterfall model
is the most basic SDLC approach for software development. The waterfall model depicts the
software development process as a sequential flow of events. This indicates that any step of the
development process can start only after the previous one has finished. The phases in this waterfall
model do not overlap.
Diagram of Waterfall model
Figure 1 Diagram of Waterfall model
Examples of Waterfall Model
The Waterfall approach was once used to construct corporate applications such as Customer
Relationship Management (CRM) systems, Human Resource Management Systems (HRMS),
Supply Chain Management Systems, Inventory Management Systems, and Point of Sale (POS)
systems for retail chains, among other things.
Until the year 2000, the waterfall paradigm was widely utilized in software development. Even
after the publication of the Agile Manifesto in 2001, many organizations continued to employ the
Waterfall paradigm into the last decade.Most projects these days use Agile Methodology, some
type of Iterative Model, or one of the other models, depending on the project requirements.
In the past, programs designed using the Waterfall Model, such as CRM systems and supply chain
management systems, took a year or more to complete.
With the advancement of technology, there have been instances where large-scale corporate
systems were constructed over a two- to three-year period but were obsolete by the time they were
finished. This was due to a number of factors.
a. By the time the applications were developed in C, C++ etc, new languages (relatively
speaking) like Java, .Net etc would replace them with web-based functionality.
b. Even if the application was developed using a new technology, factors like more
competitors entering the market, cheaper alternatives becoming available, better
functionality using newer technologies, change in customers requirement etc. increase
the risk of developing an application over several years.
However, there are some areas where Waterfall model was continued to be preferred.
a. Consider a system where human life is on the line, where a system failure could result in
one or more deaths.
b. In some countries, such mishaps could lead to imprisonment for those who are accountable.
c. Consider a system where time and money were secondary considerations and human safety
was first.
In such situations, Waterfall model was the preferred approach.
a. Development of Department of Defense (DOD), military and aircraft programs followed

Waterfall model in many organizations.
b. This is because of the strict standards and requirements that have to be followed.
c. In such industries, the requirements are known well in advance and contracts are very
specific about the deliverable of the project.
d. DOD Agencies typically considered Waterfall model to be compatible with their acquisition
process and rigorous oversight process required by the government.
Having said that, even these industries are being disrupted by the use of Iterative model and Agile
methodology by organizations like Space X and others. Waterfall model was also used in banking,
healthcare, control system for nuclear facilities, space shuttles etc.
Advantage of waterfall model
a. This model is simple and easy to understand and use.
b. It is easy to manage due to the rigidity of the model – each phase has specific deliverables
and areview process.
c. In this model phases are processed and completed one at a time. Phases do not overlap.
d. Waterfall model works well for smaller projects where requirements are clearly defined and
verywell understood.
Disadvantages of waterfall model
a. Once an application is in the testing stage, it is very difficult to go back and change
something that was not well-thought out in the concept stage.
b. No working software is produced until late during the life cycle.
c. High amounts of risk and uncertainty.
d. Not a good model for complex and object-oriented projects.
e. Poor model for long and ongoing projects.
f. Not suitable for the projects where requirements are at a moderate to high risk of changing.
When to use the waterfall model
a. This model is used only when the requirements are very well known, clear and fixed.
b. Product definition is stable.
c. Technology is understood.
d. There are no ambiguous requirements
e. Ample resources with required expertise are available freely
f. The project is short.
During the development of a product, the Waterfall approach involves very little client
engagement. Only when the product has been completed can it be demonstrated to the final users.
If a failure arises after the product has been produced, the cost of resolving the problem is very
significant, because we must update everything from the document to the logic.
Prototyping model
The prototype model requires that before carrying out the development of actual software, a
working prototype of the system should be built. A prototype is a toy implementation of the system.
A prototype usually turns out to be a very crude version of the actual system, possible exhibiting
limited functional capabilities, low reliability, and inefficient performance as compared to actual
software. In many instances, the client only has a general view of what is expected from the
software product. In such a scenario where there is an absence of detailed information regarding the
input to the system, the processing needs, and the output requirement, the prototyping model may
be employe
Figure 2 Prototyping model

Steps of the prototyping model
a. Requirement Gathering and Analyst
b. Quick Decision
c. Build a Prototype
d. Assessment or User Evaluation
e. Prototype Refinement
f. Engineer Product
Types of prototype models
a. Rapid throwaway- This method involves exploring ideas by quickly developing a prototype
basedon preliminary requirements that is then revised through customer feedback. The
name rapid throwaway refers to the fact that each prototype is completely discarded and
may not be a part of the final product.
b. Evolutionary- This approach uses a continuous, working prototype that is refined after each
iteration of customer feedback. Because each prototype is not started from scratch, this
method saves time and effort.
c. Incremental- This technique breaks the concept for the final product into smaller pieces, and
prototypes are created for each one. In the end, these prototypes are merged into the final
product.
d. Extreme- This prototype model is used specifically for web development. All web
prototypes are built in an HTML format with a services layer and are then integrated into
the final product.
Advantages of the prototyping model
a. Reduce the risk of incorrect user requirement
b. Good where requirement is changing/uncommitted
c. Regular visible process aids management
d. Support early product marketing
e. Reduce Maintenance cost.
f. Errors can be detected much earlier as the system is made side by side.
Disadvantages of the prototyping model
a) An unstable/badly implemented prototype often becomes the final product.
b) Require extensive customer collaboration

a. Costs customer money
b. Needs committed customer
c. Difficult to finish if customer withdraw
d. May be too customer specific, no broad market
c) Difficult to know how long the project will last.
d) Easy to fall back into the code and fix without proper requirement analysis, design,
customer evaluation, and feedback.
e) Prototyping tools are expensive.
f) Special tools & techniques are required to build a prototype.
g) It is a time-consuming process.
Spiral Model
The baseline spiral is used to collect the business needs at this phase. This phase is followed by the
identification of system requirements, subsystem requirements, and unit requirements as the
product matures. This phase also includes continual communication between the customer and the
system analyst to understand the system requirements. The product is launched in the identified
market at the end of the spiral.
Figure 3 Spiral Model

When to use Spiral Model?
a. When costs and risk evaluation is important
b. For medium to high-risk projects
c. Long-term project commitment unwise because of potential changes to economic priorities
d. Users are unsure of their needs
e. Requirements are complex
f. New product line
g. Significant changes are expected (research and exploration)
Each phase of the Spiral Model is divided into four quadrants
1. Identifying different options and determining objectives: At the outset of each step,
customers’ requirements are gathered, and objectives are identified, elaborated, and
analyzed. Then, in this quadrant, alternative solutions for the phase are given.
2. Risks must be identified and resolved: In the second quadrant, all viable solutions are
reviewed in order to choose the best one. The risks connected with that solution are then
identified, and the risks are mitigated using the best technique possible. The Prototype is
made at the end of this quadrant for the finest possible solution.
3. Develop the product's next version: The features that have been found are created and tested
in the third quadrant. The next edition of the software is available at the end of the third
quadrant.
4. Review and make plans for the following phase: Customers evaluate the software that has
been built thus far in the fourth quadrant. Finally, the planning for the following step
begins.
Risk Handling in Spiral Model
Any adversity that could jeopardize the effective execution of a software project is referred to be a
risk. The spiral model's most essential aspect is how it handles unforeseen hazards once the project
has begun. The development of a prototype makes such risk resolutions easier. The spiral approach
facilitates risk management by allowing for the creation of a prototype at each stage of software
development. The Prototyping Model also enables risk management, although hazards must be
fully identified before the project's development activity begins. However, in real life, project risk
may arise after development work has begun; in this scenario, the Prototyping Model cannot be
used. The product's features are evaluated and examined in each phase of the Spiral Model, and the
risks at that moment in time are identified and resolved through prototyping. As a result, this
paradigm is far more adaptable than other SDLC models.
Advantages of Spiral Model
a. High amount of risk analysis hence, avoidance of Risk is enhanced.
b. Good for large and mission-critical projects.
c. Strong approval and documentation control.
d. Additional Functionality can be added at a later date.
e. Software is produced early in the software life cycle.
Disadvantages of Spiral Model
a. Can be a costly model to use.
b. Risk analysis requires highly specific expertise.
c. Project’s success is highly dependent on the risk analysis phase.
d. Doesn’t work well for smaller projects.

Agile methodology
The term "agile methodology" refers to a practice that encourages continuous development and
testing throughout the project's software development lifecycle. Unlike the Waterfall paradigm,
both development and testing operations are contemporaneous under the Agile model of software
testing.
Figure 4 Agile methodology

4 Values of Agile
1. Individuals and interactions
In the past, a lot of software teams would concentrate on having the best possible tools or processes
with which to build their software. The Agile Manifesto suggests that while those things are
important, the people behind the processes are even more so. Having the right group of individuals
on your software team is vital to success. The best possible tools in the wrong hands are worthless.
Perhaps even more important is how these individuals communicate with each other. The
interactions between team members are what help them to collaborate and solve any problems that
arise.
2. Working software
Previously, software developers would spend ages creating detailed documentation. That was
before they even started writing a single line of code. And while documentation isn’t a bad thing,
there comes a point when you should focus on providing your customers with working software.
The Agile Manifesto places shipping software to your customers as one of the highest priorities.
You can then gather feedback to help you improve future releases.
3. Customer collaboration
Once upon a time, contracts were king. You would draw up contracts with your customers who
would then detail the finished product. As a result, there was often a contrast between what the
contract said, what the product did, and what the customer actually required. According to the
Agile Manifesto, the focus should be on continuous development. You need to build a feedback
loop with your customers so that you can constantly ensure that your product works for them.
4. Responding to change
The trouble with static roadmaps is that we don’t live in a static world. Needs and requirements are
always shifting, and priorities are always changing. That static roadmap will soon grow
outdated.That’s why the Agile Manifesto suggests that a software team should have the ability to
pivot and change direction whenever they need to, with a flexible roadmap that reflects that.
A dynamic roadmap can change from quarter to quarter, sometimes even month to month, and agile
teams are able to keep up with those changes.
12 Principles of Agile
a. Satisfy the customer through early and continuous delivery of valuable software.
b. Welcome and harness changes for the customer's competitive advantage, even late in
development.
c. Deliver working software frequently, from a couple of weeks to a couple of months, with a
preference for shorter timescales.
d. Have daily collaboration between businesspeople and developers throughout the project.
e. Build projects around motivated individuals. Create the environment and support
developers need and trust them to get the job done.
f. Prioritize face-to-face conversation as the most efficient and effective method of conveying
information to and within a development team.
g. Measure progress by the amount of working software completed.
h. Maintain a constant and sustainable pace of development indefinitely.
i. Enhance agility through continuous attention to technical excellence and good design.
j. Keep it simple. Simplicity—the art of maximizing the amount of work not done—is essential.
k. Recognize that the best architectures, requirements, and designs emerge from self-
organizing teams.
l. Regularly reflect and adapt behavior for continual improvement.
Why chooses agile?
Active project management employs short development cycles known as "sprints," each of which
incorporates and adapts feedback from partners and customers to produce a high-quality end result.
Due to the fast pace of today's business, agile project management has gained popularity. The
approach targets firms that deal with quick market deadlines, shifting goals, increasing share
engagement, and the requirement for flexibility by focusing on continuous evolution and
collaboration. Instead of spending six months producing a product or service that will be outdated
by the time it hits the market, an Agile Project Management business may release a first iteration in
two weeks. Over the next six months, they may continue to produce updated, adaptive versions,
culminating in a more efficient, relevant, and effective final distribution. As a result, Agile Project
Management, which was originally developed for software companies, has found its way into a
wide range of industries, including financial services and transportation.
Agile methodologies
1. Scrum
2. Extreme Programming (XP)
3. Adaptive Software Development (ASD)
4. Dynamic Software Development Method (DSDM)
5. Feature Driven Development (FDD)
6. Kanban
7. Behavior Driven Development (BDD)

Scrum Methodology
Scrum is without a doubt the most popular of the several frameworks that support Agile technique.
Scrum is defined by sprints, or development cycles, and the purpose of maximizing development
time for a software product toward a specific goal, the Product Goal. This Product Goal is a higher-
level value goal, with sprints bringing the scrum team's product closer together. It is most
commonly employed in the management of software product development, but it can also be
applied successfully in a corporate setting. Every day begins with a short 15-minute meeting called
the daily Scrum, which is responsible for synchronizing activities and determining the best
approach to schedule the working day, as well as keeping track of sprint "health" and product
progress.
Figure 5 Scrum Methodology

Advantages of agile scrum methodology
a. Team motivation is good because programmers want to meet the deadline for every sprint
b. Transparency allows the project to be followed by all the members in a team or even
throughout the organization
c. A simple “definition of done” is used for validating requirements
d. Focus on quality is a constant with the scrum method, resulting in fewer mistakes
e. The dynamics of this method allow developers to reorganize priorities, ensuring that sprints
that have not yet been completed get more attention
f. Good sprint planning is prioritised, so that the whole scrum team understands the “why,
what and how” of allocated tasks
Advantages of agile scrum methodology
a. The segmentation of the project and the search for the agility of development can
sometimes lead the team to lose track of the project as a whole, focusing on a single part
b. Every developer role may not be well defined, resulting in some confusion amongst team
members.
different roles in agile scrum methodology
a. Scrum master: The scrum master is the facilitator of the scrum development process. In
additionto holding daily meetings with the scrum team, the scrum master makes certain that
scrum rulesare being enforced and applied as intended. The scrum master’s responsibilities
also include coaching and motivating the team, removing impediments to sprints, and
ensuring that the team has the best possible conditions to meet its goals and produce
deliverable products.
b. Product owner: The product owner represents stakeholders, who are typically customers. To
ensure the scrum team is always delivering value to stakeholders and the business, the
product owner determines product expectations, records changes to the product and
administers a scrumbacklog, a detailed and constantly updated to-do list for the scrum
project. The product owner is also responsible for prioritizing goals for each sprint, based
on their value to stakeholders, such that the most important and deliverable features are
built in each iteration.
c. Scrum team: The scrum team is a self-organized group of three to nine individuals who
have thebusiness, design, analytical and development skills to carry out the actual work,
solve problems and produce deliverable products. Members of the scrum team self-
administer tasks and are jointly responsible for meeting each sprint’s goals
differences between scrum and agile
On the surface, Agile and Scrum appear to be very similar, as both rely on an iterative process,
regular client involvement, and collaborative decision-making. The primary distinction between
Agile and Scrum is that, whereas Agile is a project management philosophy based on a core set of
values or principles, Scrum is a specific Agile technique for project management. There are also
other notable differences between Agile and Scrum.
Agile is a philosophy, whereas Scrum is a type of Agile methodology
a. Scrum is broken down into shorter sprints and smaller deliverables, while in Agile
everything is delivered at the end of the project
b. Agile involves members from various cross-functional teams, while a Scrum project team
includes specific roles, such as the Scrum Master and Product Owner
It’s important to remember that although Scrum is an Agile approach, Agile does not always mean
Scrum—there are many different methodologies that take an Agile approach to project
management.
Extreme Programming (XP)
Kent Beck created this basic Agile development framework, which may be customized to
development businesses of all sizes. The Extreme Programming ("XP") methodology is built on the
concept of finding "the simplest thing that will work" without putting too much emphasis on the
long-term product perspective.
It's a methodology that prioritizes client pleasure over all else and emphasizes qualities like
communication, simplicity, feedback, courage, and respect. This methodology fosters trust by
encouraging developers to accept modifications in customer needs, even if they come late in the
development process.
In XP, teamwork is crucial because when a problem arises, it is resolved by the entire team of
managers, engineers, or consumers, bringing them together to increase conversation and
engagement and break down communication barriers. They all become vital pieces of the same
puzzle, fostering a fertile environment for increased team productivity and efficiency. Extreme
Programming involves testing software from the beginning and collecting feedback to improve
development. XP encourages activities like pair programming, and it's a fantastic engineering style
with a strong testing component.
Figure 6 Extreme Programming (XP)
The five values of XP
1. Communication
Software development is inherently a team sport that relies on communication to transfer

knowledge fromone team member to everyone else on the team. XP stresses the importance of the
appropriate kind of communication – face to face discussion with the aid of a white board or other
drawing mechanism.
2. Simplicity
Simplicity means “what is the simplest thing that will work?” The purpose of this is to avoid waste
and doonly absolutely necessary things such as keep the design of the system as simple as possible
so that it is easier to maintain, support, and revise. Simplicity also means address only the
requirements that you know about; don’t try to predict the future.
3. Feedback
Through constant feedback about their previous efforts, teams can identify areas for improvement
andrevise their practices. Feedback also supports simple design. Your team builds something,
gathers feedback on your design and implementation, and then adjust your product going forward
4. Courage
Kent Beck defined courage as “effective action in the face of fear” (Extreme Programming
Explained P.20). This definition shows a preference for action based on other principles so that the
results aren’t harmful to the team. You need courage to raise organizational issues that reduce your
team’s effectiveness. You need courage to stop doing something that doesn’t work and try
something else. Youneed courage to accept and act on feedback, even when it’s difficult to accept.
5. Respect
The members of your team need to respect each other in order to communicate with each other,
provideand accept feedback that honors your relationship, and to work together to identify simple
designs and solutions
The process and roles of extreme programming
1. Planning, the first stage, is when the customer meets the development team and presents
the requirements in the form of user stories to describe the desired result. The team then
estimates thestories and creates a release plan broken down into iterations needed to cover
the required functionality part after part. If one or more of the stories can’t be estimated, so-
called spikes can be introduced which means that further research is needed.
2. Designing is actually a part of the planning process but can be set apart to emphasize its
importance. It’s related to one of the main XP values that we’ll discuss below — simplicity.
Agood design brings logic and structure to the system and allows to avoid unnecessary
complexities and redundancies.
3. Coding is the phase during which the actual code is created by implementing specific XP
practices such as coding standards, pair programming, continuous integration, and
collective codeownership
4. Testing is the core of extreme programming. It is the regular activity that involves both unit
tests (automated testing to determine if the developed feature works properly) and
acceptance tests (customer testing to verify that the overall system is created according to
the initial requirements).
5. Listening is all about constant communication and feedback. The customers and project
managers are involved to describe the business logic and value that is expected.
Principles of extreme programming
1. Rapid feedback. Team members understand the given feedback and react to it right away.
2. Assumed simplicity. Developers need to focus on the job that is important at the moment
andfollow YAGNI (You Ain’t Gonna Need It) and DRY (Don’t Repeat Yourself) principles.
3. Incremental changes. Small changes made to a product step by step work better than big
onesmade at once.
4. Embracing change. If a client thinks a product needs to be changed, programmers should

support this decision and plan how to implement new requirements.
5. Quality work. A team that works well, makes a valuable product and feels proud of it.
Extreme programming advantages
a) The simplicity of the written code is an advantage since it allows for improvement at any
given time
b) The whole process and the XP development cycle is visible, creating goals for developers
along with relatively rapid results
c) Software development is more agile than when using other methodologies, due to constant
testing
d) Promotes a highly energising way of working
e) XP also contributes to uplifting and maintaining team talent.
Extreme programming disadvantages
a) The extreme focus on code can lead to less importance being paid to design, meaning that it
has to get extra attention later
b) This framework may not work at its best if all the team members are not situated in the
same geographical area
c) In XP projects, a registry of possible errors is not always maintained, and this lack of
monitoring can lead to similar bugs in the future.
Comparison of Extreme programming vs Scrum
Extreme programming is a software development process with the goal of providing high-quality,
valuable software at frequent intervals to please the customer. Scrum is a framework for producing
complicated goods in a sustainable manner, and it may be applied to items other than software.
This is one of the most significant differences between the two.
Adaptive Software Development (ASD)
Rapid Application Development (RAD) was an earlier agile framework that spawned Adaptive
Software Development (ASD) (RAD). It tries to help teams adapt fast and efficiently to shifting
requirements or market needs by allowing them to evolve their products with minimal planning and
continual learning.
Figure 7 Adaptive Software Development (ASD)

The main characteristics of ASD
1. Speculate: This is the initiation phase of the project where it is necessary to establish the
main objectives and goals of the project by understanding the limitations (risk areas) with
which the project operates.
2. Collaborate: This is the phase where most of the development is centered, maintaining co-
ordination between teams that ensures what is learned by one team is communicated to the
rest and does not have to be learned again by other teams from scratch.
3. Learn: The last stage ends with a series of collaboration cycles – the job is to capture what
has been learned, both positive and negative. This stage is critical for the effectiveness of
the project
Advantages of adaptive software development
a. Focused on the end users, which can lead to better and more intuitive products
b. Allows for on-time and even early delivery
c. Encourages more transparency between developers and clients
Disadvantages of adaptive software development
a. Demands extensive user involvement, which can be difficult to facilitate
b. Integrates testing into every stage, which can add to a project’s costs
c. Emphasis on rapid iterating and continuous feedback can lead to scope creep
Dynamic Software Development Method (DSDM)
Dynamic Software Development Method (DSDM) was developed in the year 1994 by a group of
vendors and experts in the field of Software development. DSDM focuses on Software projects that
are characterized by tight budgets and schedules. It focuses on frequent delivery of product cycles,
and development is iterative and incremental. With Dynamic Software Development Method
(DSDM), one can design a roadmap of early and continuous deliveries for the project,
implementing an incremental solution, adapting from the feedback obtained throughout the
process, and checking that the expected benefits are being met.DSDM is an agile model that can
undoubtedly help organizations that are used to working on projects to change their mentality and
way of working to improve their capacity to deliver value and reduce time to market..
Figure 8 Dynamic Software Development Method (DSDM)

Key principles of the dynamic systems development method
a) Focus on the business need: DSDM teams must establish a valid business case and ensure
organizational support throughout the project
b) Deliver on time: Work should be time-boxed and predictable, to build confidence in the
development team.
c) Collaborate: DSDM teams must involve stakeholders throughout the project and empower all
members of the team to make decisions.
d) Quality: To ensure high quality, the level of quality should be agreed with the business at the
start of the project. This is enforced through continuous testing, review, and documentation.
e) Build incrementally from firm foundations: Teams must do enough design work up front
(EDUF) to ensure they know exactly what to build, but not too much to slow development
f) Developer Iteratively: Take feedback from the business and use this to continually improve with
each development iteration. Teams must also recognize that details emerge as the project or
product develops and they must respond to this.
g) Communicate continuously and clearly: Holding daily stand-up sessions, encouraging informal
communication, running workshops and building prototypes are all key DSDM tools.
Communicating through documents is discouraged - instead, documentation must be lean and
timely.
h) Demonstrate control: The project manager and team leader should make their plans and progress
visible to all and focus on successful delivery.
Advantages of dynamic systems development method
a) Projects are delivered on time, whilst still allowing flexibility
b) Progress can be easily understood across the organization
c) Business cases are at the core of the DSDM model, ensuring delivered projects have real
business value

Disadvantages of the dynamic systems development method
a. Large management overhead and costly implementation makes this unsuitable for small
organizations
b. DSDM can be restrictive and inhibit developer creativity. Projects are likely to be completed
exactly as specified, even if more elegant solutions are available.
Kanban
The term "Kanban" is Japanese in origin and refers to the concept of "just in time." In reality, the
Kanban technique is implemented on a board or table (Kanban board), which is divided into columns
and displays each flow inside the software development project. The information in the table changes as
the project progresses, and every time a new task is added, a new "card" is created. This methodology
can also be used in individual company areas like HR, marketing, and others to provide the needed
visibility over all of the team's tasks.
The Kanban technique necessitates communication and openness so that all members of a team are
aware of where a project is in its development and can see its status at any moment. It is best for
processes that undergo minimal modifications and focuses on team capabilities.
Figure 9 Kanban
The five stages of feature driven development
1. Develop an overall model
Here, teams should focus more on the shape and overall scope of the product than the detailed content.
According to Jeff De Luca — FDD’s founding father — the overall model acts as a draft, capturing the
vision of the product but not a lot else. Go into too much feature-heavy detail at an early phase, and you
may miss other opportunities that arise. At this stage, simply focus on capturing on paper who your
target audience is, what context your software will be used in, the necessary content structure and first
thoughts surrounding UX and UI.
2. Build a feature list
Next, teams should use the overall model to identify which features will be required. Remember that in
FDD, ‘features’ are similar to user stories — so think about the development activities which will need
tohappen to bring your product or software to life.
3. Plan by feature
The planning phase is essential in FDD. Here, teams should allocate reasonable estimates to each
feature, assign them to a team member and work out what needs to happen for these deadlines to be
met. For ultimate success, all team members should take part in this process — so everyone is aligned
with the plan of action.
4. Design by feature
Now it’s time to get started! As FDD is an agile practice, teams should design concurrently and
collaboratively.
5. Build by feature
Again, team members should work on their individual build responsibilities at the same time — visual
designers on the UI, programmers on coded components, etc. When everything is ready to be pulled
together, it’s sent to QA for testing. Then, the next feature can be tackled.
Advantages of Kanban method
a) Ability to view all the tasks under a single project (by Completed, In Progress or in testing, for
example) using the simple concept of “Cards”
b) You can limit the number of running tasks (that is, the amount of work, bearing its resolution or
deliverability in mind)
c) Focuses on the duration of a cycle – how long it takes a task to go from backlog to final stage
d) Allows continuous deliveries
e) Probably one of the simplest methodologies to implement outside the “IT world”.
Disadvantages of Kanban method
a) It’s possible for team members to misinterpret the information shown on the Kanban Board,
especially when it is shown as outdated
b) Since there are no timeframes in Kanban, you can face time-related problems, such as delays, at
each and every stage.
Kanban Practices
a) Limit Work in Progress (WIP) – Loss of focus can seriously harm your team’s performance,
so this practice centers around eliminating interruptions by setting limits on the work in
progress. By applying limits to WIP, teams focus on finishing outstanding work before starting
new work. Limiting WIP is critical for the successful implementation of Kanban.
b) Manage flow – By observing and analyzing flow efficiency, you can identify any problem
areas. The main goal of implementing Kanban is to create a smooth workflow by improving the
lead times and avoiding delays. You should always strive to make your process more efficient.
c) Make process policies explicit – The process should be clearly defined, published, and
confirmed for everyone in the team: people won’t feel motivated to be part of something unless
they think it will be useful. When everyone is aware of the explicit policies, each person can
suggest improvements that will improve your performance.
d) Use feedback loops – In order for the positive change to occur, regular meetings are necessary
to provide essential feedback to the entire team. The frequency of these meetings varies, but the
idea is that they are regular, at a fixed time, and that they get straight to the point.
• Improve collaboratively – Kanban requires constant evaluation, analysis, and

improvement.When teams have a shared understanding of the process, they are more
likely to reach a consensus should any problems arise. The Kanban Method suggests
that various models of scientific approach are used to implement continuous,
incremental, and evolutionary changes
TASK 02
Feasibility Study
As the name implies, a feasibility study is used to determine whether a project or proposal is feasible.
It's a determination of the feasibility of a proposed project or plan. A feasibility study is part of any
project's or plan's initial design stage. It is carried out in order to discover objectively the strengths and
weaknesses of a new enterprise or an existing firm. It can assist in identifying and assessing possibilities
and dangers in the natural environment, as well as the resources needed for the project and its chances
of success. It's being done to find out the answers to the following questions.
1. Does the company possess the required resources and technology?
2. Will the company receive a sufficiently high return on its investment?
Figure 10 Feasibility Study

Steps in a Feasibility Study
1. Conduct a Preliminary Analysis
Begin by outlining your project plan. You should focus on an unserved need, a market where the
demand is greater than the supply, and whether the product or service has a distinct advantage. Then
you need to determine if the feasibility factors are too high to clear (i.e., too expensive, unable to
effectively market, etc.).
2. Prepare a Projected Income Statement
This step requires you to work backward. Start with what you expect the income from the project to be
and then what project funding is needed to achieve that goal. This is the foundation of an income
statement. Things to take into account here include what services are required and how much they’ll
cost, any adjustments to revenues, such as reimbursements, etc.
3. Conduct a Market Survey, or Perform Market Research
This step is key to the success of your feasibility study, so make your market analysis as thorough as
possible. It’s so important that if your organization doesn’t have the resources to do a proper one, then it
is advantageous to hire an outside firm to do so. The market research is going to give you the clearest
picture of the revenues and return on investment you can realistically expect from the project. Some
things to consider are the geographic influence on the market, demographics, analyzing competitors, the
value of the market and what your share will be and if the market is open to expansion (that is, response
to your offer).
4. Plan Business Organization and Operations
Once the groundwork of the previous steps has been laid, it’s time to set up the organization and
operations of the planned project to meet its technical, operational, economic and legal feasibility
factors. This is not a superficial, broad-stroke endeavor. It should be thorough and include start-up
costs, fixed investments and operating costs. These costs address things such as equipment,
merchandising methods, real estate, personnel, supply availability, overhead, etc.
5. Prepare an Opening Day Balance Sheet
This includes an estimate of the assets and liabilities, one that should be as accurate as possible. To do
this, create a list that includes items, sources, costs and available financing. Liabilities to consider are
such things as leasing or purchasing of land, buildings and equipment, financing for assets and accounts
receivables.
6. Review and Analyze All Data
All these steps are important, but the review and analysis are especially important to make sure that
everything is as it should be and that nothing requires changing or tweaking. So, take a moment to look
over your work one last time. Reexamine your previous steps, such as the income statement, and
compare it with your expenses and liabilities. Is it still realistic? This is also the time to think about risk,
analyze and manage, and come up with any contingency plans.
7. Make a Go/No-Go Decision
You’re now at the point to make a decision about whether the project is feasible or not. That sounds
simple, but all the previous steps lead to this decision-making moment. A couple of other things to
consider before making that binary choice is whether the commitment is worth the time, effort and
money and is it aligned with the organization’s strategic goals and long-term aspirations.
Contents of a Feasibility Report
1. Executive Summary
2. Description of the Product/Service
3. Technology Considerations
4. Product/ Service Marketplace
5. Identification of the Specific Market
6. Marketing Strategy
7. Organizational Structure
8. Schedule
9. Financial Projections
Best Practices for a Feasibility Study
a) Use project management software like Project Manager to organize your data and work
efficiently and effectively
b) Use templates or any data and technology that gives you leverage
c) Involve the appropriate stakeholders to get their feedback
d) Use market research to further your data collection
e) Do your homework and ask questions to make sure your data is solid
The real effort begins once your project is determined to be realistic. Project Manager assists you in
making more efficient plans. To reduce delays, our online Gantt chart organizes tasks, establishes
deadlines, assigns priorities, and links dependent activities. However, unlike other Gantt tools, we
compute the critical route for you and establish a baseline against which you can assess project variance
once you enter the execution phase.
Types of Feasibility Study
1. Technical feasibility
a. Technical: Hardware and software
b. Existing or new technology
c. Manpower
d. Site analysis
e. Transportation
2. Financial feasibility
a. Initial investment
b. Resources to procure capital: Banks, investors, venture capitalists
c. Return on investment
3. Market feasibility
a. Type of industry
b. Prevailing market
c. Future market growth
d. Competitors and potential customers
e. Projection of sales
4. Organizational feasibility
a. The organizational structure of the business
b. Legal structure of the business or the specific project
c. Management team’s competency, professional skills, and experience
1) Technical Feasibility
The process of determining whether or not your product or service is technically feasible for your
organization is known as technical feasibility. You must plan every aspect of your operations before
launching your offerings, from acquiring your production materials to tracking your sales. You can
identify potential obstacles and solutions to solve them by looking at all of the logistics of this
procedure.
2) Financial Feasibility
The term "financial feasibility" refers to whether or not a project is financially feasible. A cost/benefit
analysis of the project is included in a financial feasibility report. It also estimates the projected return
on investment (ROI) and identifies any potential financial hazards. The purpose of the financial
feasibility study's conclusion is to determine the project's economic benefits.
3) Market Feasibility Study
The market feasibility study is an evaluation of how your team expects the project’s deliverables to
perform in the market. This part of the report includes a market analysis, market competition
breakdown, and sales projections.
4) Organizational feasibility
An operational feasibility study evaluates whether or not your organization is able to complete this
project. This includes staffing requirements, organizational structure, and any applicable legal
requirements. At the end of the operational feasibility study, your team will have a sense of whether or
not you have the resources, skills, and competencies to complete this work.
5) Economic Feasibility Study
The process of analyzing if a new enterprise is worth the cost and time investment is known as
economic feasibility analysis. Cost-benefit analysis is another name for it.
This type of study considers the costs of both building and running the new business. It's a means of
lowering the risk of attempting new ventures. A variety of elements are taken into account, and if they
show that the proposal is cost effective, it is usually adopted.
6) Operational Feasibility
The willingness and ability of management, personnel, customers, suppliers, and others to operate and
support the proposed organization is known as functional feasibility. It relates to the extent to which a
new proposed system is able to solve difficulties.
7) Schedule Feasibility
This evaluation is critical for project success; after all, if a project is not completed on time, it will fail.
An organization predicts the amount of time it will take to execute a project when scheduling
feasibility.
How to Conduct a Feasibility Study
a) To begin, we do a preliminary study of the business case to define what is included and what we
are examining and attempting to find is realistic.
b) Following that, we generate a forecasted income statement. We need to understand the revenue
sources; how are we going to profit from this? Where does the income originate? Additionally,
we must do a market study.
c) We need to find out whether this is a demand for our product. How much demand does this
have? Is there a market for this product or service?
d) Plan your company's structure and operations, which is the fourth step. Specifically, what type
of organization do we need, and what resources do we have? Do we have any specific personnel
needs?
e) We also plan to generate a balance sheet on the first day. What are the income and expenses, and
how can we be confident we'll be able to decide whether we're going to make our ROI?
f) As a result, we plan to go through and examine all of our data before making a final decision on
whether or not to go forward. In other words, are we going to pursue this project or business
opportunity?
6 Elements of a Good Feasibility Study
1) The project scopes
First, the business problem/opportunity has to be addressed clearly. The project scope to be to the point
and clearly defined. Make sure to also define the business components that would be either directly or
indirectly affected, including project participants and end-users.
2) The current analysis
This form of analysis is used to evaluate the current method of implementation like a new product or
system. From this analysis, you can discover the strengths and weaknesses of the current approach.
Conducting a current analysis and identifying the pros and cons of your current system/product can help
you save both money and time.
3) The requirements
You will need to define your requirements depending on the objective of your project. For instance,
how the requirements are specified for a product will be entirely different from the requirements
specified for an information system. How you accurately define your requirements is an important
factor in a feasibility study.
4) The approach
You will next have to choose the recommended solution or course of action to meet your requirements.
You can consider various alternatives and then choose a solution that is the most preferable. Before you
finalize the approach, ask yourself the following questions:
a) Does the approach meet my requirements?
b) Is the approach taken a practical and viable solution?

5) Evaluation
This element will examine the cost-effectiveness of the selected approach and the estimated total cost of
the project. Other alternatives will also be estimated for comparison purposes. After the total cost of the
project has been calculated, an evaluation and cost summary will be prepared to include a return on
investment, cost/benefit analysis, etc.
6) Review
Finally, all the above elements will be assembled into a feasibility study and a formal review will be
conducted. The review will be used to verify the accuracy of the feasibility study and to make a project
decision. At this stage, you can approve, reject or even revise the study for making a decision. If the
feasibility study is approved, make sure that all the involved parties sign the document.
Importance of Feasibility Study
a) Likely to Succeed
The term “feasible” describes an action or event that is likely, probably or possible to happen or
achieve. A feasibility study is the total of the actions you take and the questions you ask to determine
whether an idea, thought or plan is likely to succeed. An effective study can guide you on whether you
should move forward with your idea, refine it, or scrap it altogether and go back to the drawing board.
b) Focused and Specific
Feasibility studies are focused and specific. They start with a single question – asking whether the idea,
event or action is a viable solution – and force you to focus solely on that question to the exclusion of
everything else, drilling down to explore possible outcomes. A feasibility study is not the same as a
business plan. A feasibility study is an investigative tool that might cause you to discount an idea,
whereas a business plan is call to action. You can, in fact, use a feasibility study as a predecessor to be
creating a business plan.
c) The Big Picture
Feasibility studies are important because they force you consider the big picture first and then think in a
top-down fashion. In this way, one or two general starter questions lead to a host of additional, more
detailed questions that become increasingly narrower in focus as you get closer to reaching an ultimate
answer.
For example, asking whether anyone will buy your new-and-improved product and whether it will
generate a profit creates additional questions that force you to consider customer need and possible
competition, and to identify risks that you may face. You must also describe your product and its
benefits, define your target market, and calculate cost along with break-even and profit points.
d) Alternative Opportunities and Solutions
Feasibility studies offer you the chance to “get it right” before committing time, money and business
resources to an idea that may not work in the way you originally planned, causing you to invest even
more to correct flaws, remove limitations, and then simply try again. Feasibility studies may also open
your eyes to new possibilities, opportunities and solutions you might never have otherwise considered.
There are no right or wrong answers to the questions you ask, but an answer you don’t necessarily want
or expect can create new profit potential.
key benefits of conducting a feasibility study
a. Improves project teams’ focus
b. Identifies new opportunities
c. Provides valuable information for a “go/no-go” decision
d. Narrows the business alternatives
e. Identifies a valid reason to undertake the project
f. Enhances the success rate by evaluating multiple parameters
g. Aids decision-making on the project
h. Identifies reasons not to proceed

Benefits of a Feasibility Study
There are several benefits to feasibility studies, including helping project managers discern the pros and
cons of undertaking a project before investing a significant amount of time and capital into it.
Feasibility studies can also provide a company's management team with crucial information that could
prevent them from entering into a risky business venture.
Feasibility studies also help companies with new business development, including determining how it
will operate, potential obstacles, competition, market analysis, and the amount and source of financing
needed to grow the business. Feasibility studies aim for marketing strategies that could help convince
investors and banks that investing in a particular project or business is a wise choice.
What is a feasibility report?
A feasibility study is a document that assesses a set of potential project paths or solutions to see if they
are feasible. A person who writes a feasibility report assesses the feasibility of various options before
making a suggestion for the best option. They then give their company the feasibility study and make
their proposal.
What is the purpose of a feasibility report?
A feasibility report's goal is to assess the viability of various solutions or project paths and select the
best choice. The purpose of a feasibility study is to assist readers understand the viability of various
approaches to a problem or project. Readers can determine whether to follow the report's
recommendation for the optimal method based on the evaluation presented in the report. This in-depth
examination of several ways can assist businesses in making the best judgments possible about projects
and difficulties.
Important Features of a Basic Feasibility Report
Introduction - You must persuade the decision maker to consider any option at all. You must first
persuade them to read your report. Tell them what they will benefit as individuals or as a company as a
result of evaluating your work.
Criteria/Constraints - You must clearly define the criteria for the desired outcomes. You will be able to
make practical and rational decisions as a result of this. In your feasibility report, you have two options
for presenting the criteria. To begin, divide the criteria into separate sections. When you have a lengthy
report and need to go into great detail with your explanation, this is the greatest option. Second, as the
criteria become more relevant, you can incorporate them throughout your report.
It's vital to remember, though, that whatever technique you use, the criteria must be introduced early in
the report. It's also crucial to sketch out the restrictions of your proposed solutions. This demonstrates to
the audience that you recognize and accept the fact that no solution is perfect. This will also ensure that
the audience takes the best decision possible.
Method - It is critical to deliver accurate and timely information. You should list the trustworthy sources
you used and the process by which they were obtained (internet, interview, book, etc.). Your document
will lack credibility if you don't use a reputable research method or use credible sources.
Introduction
The introduction is also an important part of a feasibility report. After the executive summary, write an
introduction that describes the problem or project and the recommended solutions. Your introduction,
like your executive summary, can be generic and quick, as you will give additional specifics later in the
report.
Background and context
Background and context should be included in a feasibility report. This part is crucial for anyone
reading the report to grasp vital context information. If you're addressing different approaches to a
project, for example, you might include the project's history and aims in the background and context
section. Examining several solutions to a problem can reveal where the issue originated and how it
affects the company. It focuses the audience's understanding of the various approaches' possibilities.
Evaluation criteria
This portion of the report helps readers understand how you weighed the pros and cons of various
options and why you made the recommendation. The following are some of the evaluation criteria:
Financial Expenses: Because companies frequently assess a project's financial impact before
moving forward, financial expenses may be one of the elements in a feasibility statement.
Tax Implications: Depending on how the corporation translates taxes into another criterion,
several techniques can be assessed.
Public Opinion: Some projects or challenges may have an impact on the company's overall
perception, thus consider how different approaches in the feasibility report may affect the
company's overall perception.
Environmental Consequences: If the organization emphasizes environmentally friendly

options, the environmental implications of a strategy might be mentioned in the report.
Required Evidence: Different viable ways may require some evidence, so evaluating the
required
evidence together is one of the criteria.
Evaluation of solutions
The evaluation of the Solutions section is a crucial aspect of a feasibility report. This component of a
feasibility report assesses the viability of different solutions and project paths. The evaluation area is
where you can compare different approaches depending on the evaluation criteria. Provides
recommendations on the optimal method by guiding the review process.
Conclusion
In a conclusion section, you might summarize your report and restate your important points. This
section can be brief, with a quick summary of the benefits and drawbacks of each of the ways covered.
This section's objective is to remind your readers how you weighed in on each strategy before making
your ultimate conclusion.
Final recommendation
In the final portion of a feasibility study, you make a straight suggestion for the best course of action.
You can describe whether the solution is practical and why you believe it is the best option in this
short section. The key to crafting the final recommendation part is to state your recommendation and
why it is appropriate.
TASK 03
Activity 3.1
a. Provide suitable tool(s) to collect user and system requirements.
Collecting needs for a project could be a terribly important half. In fact, collect needs process helps to
outline project scope throughout scope management. There is square measure some set of tools and
techniques to collect project needs. It appears sensible to gather all requirements at the beginning
employing a requirement-gathering tool. this could make sure the. project deliverable as wanted.
however essentially, it's more difficult in gift situation why? the rationale is, desires and needs of
project stakeholders’ modification oftentimes. So, it is a responsibility of E-Solutions Private Limited to
confirm capturing all the necessities E-Solutions Private Limited has needs. To do so, to be terribly E-
Solutions Private Limited ought to use applicable demand gathering tools throughout the project agile
whereas grouping life. E-Solutions Private Limited has to be wise within the choice of the
necessities tools. E-Solutions Private Limited would guarantee to not miss any demand within the
project outcome. Because, in the end, E-Solutions Private Limited is chargeable for the success of the
project.
1. Collect Requirements.
Collect Requirements is the process of determining, documenting, and managing stakeholder (users)
needs & requirements to meet project objectives.
Expert Judgment
Experts are the people more knowledgeable in their respective areas. Their knowledge & experience
help to gather most of the specific product/ project requirements. Expert judgment is used to determine
specialized requirements comprising following topics
a. Requirements elicitation
b. Requirements analysis
c. Business analysis
d. Diagramming techniques
e. Facilitation
f. Conflict Management
g. Projects requirements in similar previous projects
2. Data Gathering
Data gathering is a crucial technique for facilitation &/or cluster power. Here, a bunch of individuals
involves working out all project necessities. concepts evolve
through cluster power and facilitate to see necessities. There is square measure many tools, we will use
this method. however, the proper choice depends on the kind of needs or stakeholders together with
alternative complexities.
Below is that the list of tools underneath this method

Questionnaires and Surveys
a. Interviews
b. Focus groups
c. Brain Storming
d. Benchmarking
3. Data Analysis
Business analyst typically uses these techniques. this method is additionally referred as
Document analysis. because the name suggests, E-Solutions Private Limited analyses
existing documents to elicit project necessities. this method utilizes documents like
Business plans
Use cases,
Problem or issue logs
Policies or procedures
Business rules repositories and/ or
Market literature etc., to elicit requirements.
4. Data Representation
It is used, once E-Solutions Private Limited have an outsized variety of stakeholders needs. A similar
set of needs, E-Solutions Private Limited will cluster along below one head. Hence, E-Solutions Private
Limited cut back the quantity of needs to least doable few categories. This broadens the scope of
focusing few classes instead of taking all of them quickly.
Affinity Diagram
4.1 Mind Mapping
Here, E-Solutions Private Limited wear the caps of various stakeholders. attempt to map their minds
and generate ideas. Thus, it’s a way to get an outsized variety of ideas through the method of
backtracking. a awfully helpful technique to spot the requirements of potential customers or finish
users.
5. Interpersonal & Team Skills
5.1 Nominal cluster Technique
This technique is usually wont to order the wants. Here, all stakeholders participate in an exceedingly
group action session. Generate as several ideas through brainstorming. Then rank for every plan
generated. Add up of these ranks from every stakeholder to induce the ultimate ranking of every plan.
These ideas square measure then sorted dead set gather most vital necessities. Higher the rank, higher
the priority
5.2 Observation
Also called employment – shadowing. Here, a possible user or cluster of users is observed for
distinctive necessities. E-commerce sites use this system to identify the patterns of customer’s wants
5.3 Quality Function Deployment
Also called a house of quality. this method is most popular to come up with technical requirements once
stakeholders’ wants square measure notable. Translate voice for stakeholders to spot method
necessities.
5.4 User Stories
Capture user’s experiences to spot totally different wants. Nowadays, social platforms provide several
opportunities to assemble user’s experiences.
Examples square measure Twitter and Facebook etc

6. Context Diagram
Context diagrams exemplify a scope model. They represent a pictorial visualization of various
interactions. Interactions between different users and system. Thus, they depict the steps – customers &
processes take, to result in system outcomes.
7. Protypes
A model of the ultimate product is developed supported stakeholders would like. Now, stakeholders’
area unit asked to grant their feedback on this model. Negative feedbacks are captured to spot any
necessities.
Positive feedbacks area unit preserved because it
is. Thus, paradigm provides the flavors of the ultimate product ahead. during this method, E-Solutions
Private Limited ought to higher use some effective prototyping tools so as to satisfy stakeholders’
wants. Mock and is one among the simplest tools that E-Solutions Private Limited use frequently to
make useful prototypes with single drag-and-drop.
Here is that the general paradigm method step-by step
1. Requirement gathering
2. Quick design
3. Building prototype
4. Engineer product
5. Refining prototype
6. Customer evaluation
Identify user and system requirements/ constraints for the system User Requirements
User necessities suggests that, with reference to any pc computer code, any information or
documentation related to that system consisting of useful requirements describing the top user business
necessities or functions to be happyby the system, together with the input obtainable from the top user
and also the output needed by the top user, however not together with any system design or style
documentation technical specifications, or supply or computer code.
The system needs that the users be equipped with overall net data and the convenience accessing it. The
administrator is anticipated to own a lot of skills with the interface of the school web. The sellers ought
to even have skills of well analyzing and navigating the net usage and be ready to handle customers
WHO might not be therefore acquainted with the net.
1. User requirements for E-Solutions Private Limited
1. Simple Graphical user interface (GUI) for easy navigating through the program
2. Register user details
3. Login features
4. Easy to update profile and items
5. Manage Auctions details
6. Search and view Auctions details (Search functions)
7. Add new Auctions details
8. Categorized the Auctions items
9. Delete and edit Auctions
10. Appealing to the eye through coloration and pictorial presentation
11. System Backup

2. System Requirement for E-Solutions Private Limited
System requirements are the configuration that a system must have in order for a hardware or software
application to run smoothly and efficiently. Failure to meet these requirements can result in installation
problems or performance problems. The former may prevent a device or application from getting
installed, whereas the latter may cause a product to malfunction or perform below expectation or even
to hang or crash.
2.1 Hardware Requirement for E-Solutions Private Limited
A. Processor - Minimum 1 GHz, Recommended 2GHz or more
B. Ethernet connection (LAN) OR a wireless adapter (Wi-Fi)
C. Hard Drive - Minimum 64 GB; Recommended 1 TB
D. Memory (RAM) - Minimum 4 GB; Recommended 8 GB or above
E. Operating Systems
F. Windows - 7 or newer
G. MAC - OS X v10.7 or higher
H. Linux – Ubuntu
Software Requirement for E-Solutions Private Limited
Windows/ android/ Linux/ mac/ chrome or any other operating system.
Mozilla Firefox / Google chrome / opera mini / UC browser or internet explorer.

Software Development tools
A. MySQL database
B. PHP
C. HTML
D. Visual Studio IDE
3. Functional Requirement
Functional needs for the E-Solutions Private Limited on-line auction system is developed to create
positive that the practicalities and functional aspects of the system are met.
Functional Requirements for E-Solutions Private Limited
1. Registration or create account

1.1 System will allow users to create account.
2. Login
2.1 System will allow the user to login.
2.2 System will verify the username and password.
2.3 System will not allow user to login with invalid username or password.
2.4 System will be able to remember username and password.
3. Browsing and database search

3.1 System will allow user to search products that are available for auction.
3.2 System shall display the result.
3.3 System will allow the bidder to bid on desired product.
4. User Auction
4.1 System will allow users to post the ad for product they want to sell.
4.2 System will allow users view their active bids (that are in progress).
4.3 System will allow user to view their expired bids.
4.4 System will allow user to update, search and delete the bids.
5. Purchase History
5.1 System will allow the user to view their purchase history.
5.2 System will allow the user to view their delivery method and location
User case Diagram for E-Solutions Private Limited
Figure 11 User case Diagram for E-Solutions Private Limited
Non-Functional Requirements
Non-Functional Requirement (NFR) specifies the quality attribute of a software system. They
judge the software system based on Responsiveness, Usability, Security, Portability, and other
non-functional standards that are critical to the success of the software system. Example of
non-functional requirement, how fast does the website load? Failing to meet non-functional
requirements can result in systems that fail to satisfy user needs. Non- functional Requirements
allows you to impose constraints or restrictions on the design of the system across the various
agile backlogs. Example, the site should load in 3 seconds when the number of simultaneous
users is above 10000. Description of non-functional requirements is just as critical as a
functional requirement.
Non-Functional Requirements for E-Solutions Private Limited
1. Interactive and Good Performance
The website for E-Solutions Private Limited online auction management system shall have the following
abilities and capabilities
1.1 The responsiveness of the website shall be high, and the website shall behave as per the user
action.
1.2 The user shall be acknowledged in the form of visual changes or feedback on
the site to enhance the interaction
1.3 The response time and throughput time on the site shall be minimal
1.4 Consistency on the website shall be maintained across all the web pages
1.5 The layout of the site shall be kept simple and must be self-explanatory
2. Security
2.1 The website shall offer secure login option to the users to avoid
unauthorized access to the system and the information
2.2 Advanced access control shall be included in the site
2.3 Advanced encryption algorithms must be integrated in the site to avoid
misuse of the data sets.
2.4 Technical controls, such as anti-malware, anti-denial, and intrusion
detection tools shall be integrated with the site.
3. Reliability
3.1 The web site shall provide the users with valid information at all times.
4. Scalability
4.1 Performance test parameter that explores the developmental capacity of a
system by increasing the workload per user or the number of users or the
size of the database at once.
3. Reliability
3.1 The web site shall always provide the users with valid information.
4. Scalability
4.1 Performance test parameter that explores the developmental capacity of a
system by increasing the workload per user or the number of users or the
size of the database at once.
Create user stories for identified for user requirements.
In software development and product management, a user story is an informal, natural language
description of one or more features of a software system. A user story is a tool used in agile software
development to capture a description of a software feature from an end-user perspective. A user story
describes the type of user, what they want and why. A user story helps to create a simplified description
of a requirement.
User story for E-Solutions Private Limited
First, the user needs to understand the purpose of this system, how these webs work when opening a
web browser and typing the finarts.com URL. All the steps should be described in detail to get an
overview and better understanding of the system.
Webserver Webserver roles need to be a communication link between the client side and the server side
and bring the information realized on the server by the web pages. I chose the Apache web server for
Finnards.com because the Apache server is the most popular web server software. It allows a computer
to add websites that can be accessed over the Internet using a web server
Computer function language
Required and knowledge programming languages were selected to implement the development plan. I
believe PHP is the appropriate language for online auctions because PHP is a powerful programming
language for creating dynamic web pages. PHP is basically used as the server page scripting language.
Backend Technology
Backend Technology Then I chose MYSQL because it is a relational database and a very common
database management system that holds all the data in a different table instead of putting all the data in
the same storeroom.
B Identify and explain the most suitable methodology for the analysis of the system. Answer
should cover features, advantages, and disadvantages of the selected methodology.
In IT, systems analysis can include looking at end-user implementation of a software package or
product, looking in-depth at source code to define the methodologies used in building software or taking
feasibility studies and other types of research to support the use and production of a software product,
among other things. Systems analysis professionals are often called upon to look critically at systems,
and redesign or recommend changes as necessary. Inside and outside of the business world, systems
analysts help to evaluate whether a system is viable or efficient within the context of its overall
architecture and help to uncover the options available to the employing business or other party. Systems
analysts are different than systems administrators, who maintain systems day to day, and their roles
generally involve a top- level view of a system to determine its overall effectiveness according to its
design. In order to achieve the objectives of coming up with the E-Solutions Private Limited online
auction management system, the preliminary investigation about the workability of the software is
necessary and need to be carried out first. This will equip me with the relevant materials and knowledge
on how to carry out the implementation
1. Model Driven Analysis
Model Driven Analysis is a software development methodology that saves businesses a significant
amount of time and money and enables them to streamline their operations. With all the parties working
together within a single model, Model Driven Analysis improves coordination between the various
stakeholders, resulting in a more robust software solution with fewer bugs. Model Driven Analysis is
perfect for businesses with a need for complex and error-proof software, such as companies operating in
the high-tech industry. The Benefits of Model Driven Analysis

A. Fewer bugs
B. Error-free code through automation
C. No more separate Excel spreadsheets or Word files
D. Model Driven Analysis creates improved protypes
2. Accelerated Analysis
Accelerated analysis emphasizes the construction of prototypes to quickly identify business and user
needs for a new organization. Because of this it is the most suitable method for system analysis. That
model is very relevant.
3. Prototype Methodology
The prototype methodology is the software development process which allows developers to create only
the prototype of the solution to demonstrate its functionality to the clients and make necessary
modifications before developing the actual application. The best feature of this software development
methodologies is that it solves many issues which often occur in a traditional waterfall model.
Advantages of Prototype Model
a) When a prototype is shown to the clients, they get a clear understanding and complete feel of the
functionality of the software
b) This method significantly reduces the risk of failure, as potential risks can be identified in early
stage and moderation steps can be taken quickly
c) The communication between software development team and the client makes very good and
conducive environment during a project
d) It helps in requirement gathering and requirement analysis when there is lack of requirement
documents
Disadvantages of Prototype Model
a) Prototyping is usually done at the cost of the developer so, it is should be done using minimal
resources otherwise organization’s development cost stretch too much
b) Too much involvement of client is not always favored by the software developer
c) Too many modifications may not be good for the project, as it easily disturbs the workflow of
the entire software development team.
Activity 3.2
Explain how the selected methodology in task 3.1 c) can be used to improve the effectiveness of
the analysis stage.
Prototyping methodology is helping to Addresses the inability of many users to specify their
information needs, and the difficulty of systems analysts to understand the user’s environment, by
providing the user with a tentative system for experimental purposes at the earliest possible time.
Prototyping methodology Improves both user participation in system development and communication
among project stakeholders. Especially useful for resolving unclear objectives, developing, and
validating user requirements, experimenting with or comparing various design solutions or investigating
both performance and the human computer interface. Potential exists for exploiting knowledge gained
in an early iteration as later iterations are developed. So, it helps to easily identify confusing or difficult
functions. Prototyping methodology Encourages innovation and flexible designs. Provides quick
implementation of an incomplete, but functional, application
Prototyping Methodology for E-Solutions Private Limited
At first, I realized what kind of system it was, I collected the user need, I analyzed what the appropriate
methodology was for it, analyzed all the system features, so I could easily choose the right method.
Online auction is not a big project, I need a long time, so I chose the prototype because it helps the
interaction between the software development team and the client create the best and most conducive
environment during a project. I believe the prototype method is appropriate for E-Solutions Private
Limited.
Activity 3.3
Explain reasons to select the methodology in task 3.1 for the given scenario. Provide evidence to
support your ideas and points of view.
The worst-case scenario of any prototype is customers mistaking it for the finished project. Customers
seeing a rough prototype may not understand it is merely a model that needs to be finished or polished.
Prototypes are commonly used in design and development of physical projects when large system
building construction or manufacturing is involved. For projects built on software that have many
changing variables and unknown logistics, prototypes are invaluable. There is a misconception that
prototypes aren’t a viable option for projects facing tight completion deadlines. However, with 3D
printing, making prototypes is comparatively speedy and shouldn’t slow down the project very much.
But for projects demanding trial and error, prototyping is an essential component to guarantee optimum
success.
Reduced time and costs
Prototyping improves the quality of the specifications and requirements provided to customers. With
prototyping, customers can anticipate higher costs, needed changes and potential project hurdles, and
most importantly, potential end result disasters. Strong prototyping can ensure product quality and
savings for years to come.
Improved and increased user involvement
Most customer want to feel like they are involved with the intricate details of their project. Prototyping
requires user involvement and enables them to see and interact with a working model of their project.
With prototypes, customers can give their immediate feedback, request project changes and alter model
specifications. Prototyping most importantly helps eliminate misunderstandings and
miscommunications during the development process.
Nothing makes customers happier than projects that come in under budget. Prototyping improves the
quality of requirements and specifications provided to customers. Needed changes detected later in
development cost exponentially more to implement. With prototyping, you can determine early what
the end user wants with faster and less expensive software.
TASK 04
Activity 4.1
Provide the system specification for the above scenario using the methodology you selected.
Documentation should include ERD, Prototyping techniques, and flow charts for important
functionalities, release plan and tools used
Figure 12 ER Diagram for E-Solutions Private Limited
Need a computer to create the network. This requires a web-based e-network server and webmasters.
Chrome and the JavaScript code for PHP code. We need an XAMPP and Apache server to build us to
configure the local host to test our site. User’s Safety and security reasons. Although safety and security
are real the type of information required by professionals of considerable interest is usually not a barrier
among these factors. What is usually required is a history of offerings for improvement Sales. The
identities of auctioneers and merchants should not be published. Rather it is the non-cooperation of
online retailers is expected to lose.
Activity 4.2
Explain how the system design can be used to improve the effectiveness of the selected
methodology relevant to the above scenario.
Agile software development methodology involves cross functional teams working simultaneously on
various areas like planning, requirements analysis, design, coding, unit testing, and acceptance testing.
Compressing these five sequences of the conventional software development methods, for one three-
week cycle (iterations). At the end of each iteration a working product is available. Agile is a design
framework that was originally used for software development but is now used in other areas where
there is a need to complete large tasks, including project management tasks. It is an alternative to
typical project management frameworks, such as waterfall, which is a linear process. Finearts.com likes
the fact that Agile allows for an iterative and incremental process that adapts well to unknowns. Since
the online auction Finearts.com will be providing is online auctions, Finearts.com wants to break the
project into manageable parts and be able to adjust as new information about the online auctions
becomes available.
Key features of agile methodology
Scrums the most popular way of introducing Agility due to its simplicity and flexibility. Scrum
emphasizes empirical feedback. Team self-management and striving to build properly tested product
increments within short iterations. The benefit includes increased visibility of project goals and how to
achieve them. This clear characteristic of agile projects inevitably contributes toward the even more
significant goal of delivering software on time.
Quality
Testing is integrated throughout the lifecycle, enabling regular inspection of the working product as it
develops. This allows the product owner to make necessary adjustments gives the product team early
sight of any quality issues.

Visibility
Agile development principles encourage ‘user/client’ active involvement throughout the product’s
development process. This provides excellent visibility for key stakeholders, both the project’s progress
and the product itself, which in turn helps to ensure that expectations are effectively managed.
Early identification and resolution of issues
Small incremental releases made visible to the product owner and product team through its
development help to identify any issues early and make it easier to respond to change. The clear
visibility in agile development helps to ensure that any necessary decisions can be taken at the earliest
possible opportunity, while there’s still time to make a material difference to the outcome.
Accommodating change due to volatile requirements (Flexibility / Agility)
In agile development, change is accepted. Instead, the timescale is fixed, and requirements emerge and
evolve as the product is developed. Of course, for this to work, it’s imperative to have an actively
involved stakeholder who understands this concept and makes the necessary trade-off decisions, trading
existing scope for new. Also read our earlier blog on: Top 10 Mobile Application Development Trends.
Iterative releases, Communication, continuous integration
The active involvement of a user representative/product owner, the high visibility of the product and
progress, and the flexibility to change when change is needed, creates better business engagement and
customer satisfaction. This is an important benefit that can create much more positive and enduring
working relationships.
More Enjoyable
The active involvement, cooperation and collaboration make agile development teams a much more
enjoyable place for most people. Instead of big specs, we discuss requirements in workshops. Instead of
lengthy status reports, team collaborates around a task-board discussing progress. Instead of long
project plans and change management committees, there are discussions on what’s right for the product
and project and the team is empowered to make decisions. In my experience this makes it a much more
rewarding approach for everyone. In turn this helps to create highly motivated, high-performance teams
that are highly cooperative.
Transparency
An Agile approach provides a unique opportunity for clients to be involved throughout the project, from
prioritizing features to iteration planning and review sessions to frequent software builds containing
new features. However, this also requires clients to understand that they are seeing a work in progress in
exchange for this added benefit of transparency.
Early and Predictable Delivery
By using time-boxed, fixed schedule Sprints of 1-4 weeks, new features are delivered quickly and
frequently, with a high level of predictability. This also provides the opportunity to release or beta test
the software earlier than planned if there is sufficient business value
Predictable Costs and Schedule
Because each Sprint is a fixed duration, the cost is predictable and limited to the amount of work that
can be performed by the team in the fixed-schedule time box. Combined with the estimates provided to
the client prior to each Sprint, the client can more readily understand the approximate cost of each
feature, which improves decision making about the priority of features and the need for additional
iterations
System design documentation
Design Documents Provides written documentation of design factors and choices made by the designer in
order to meet business and technical requirements. Design documents help implement the design. In many
cases where the designer is not responsible for the implementation, the design documents ensure that the
design is successful. Documents vary from project to project. There are standard document templates that
many consulting firms and resellers use when designing solutions. The following information should be in a
properly documented format.
Architectural design
The card page includes clients and project names The Document Edition record contains the changes made
to the Teacher Registration and Document contacts involve material experts involved in creating the design.
The table of contents is the code of the document sections for quick reference The table list is the code of the
tables included in the document for quick reference The list of figures is the code of the figures included in
the document for quick reference Conceptual design is the documentation of design factors: need,
constraints and assumptions Logical design contains the details of logical management, storage, and
networking the physical design includes details of the selected hardware and the configuration of the
physical and virtual hardware.
The mode of activation
First page, cover page Documentary Version Registration Document Contacts Table of contacts List of
tables in the list of persons Statement of Purpose Project communication is a document of the main project
points of contact Provides the requirements for implementation, access, facilities, hardware, software and
licensing requirements to complete the implementation. implementation Overview Project deliverables
Installation Guide First page, card page Document version registration Document Contacts
Table of contacts List of tables in the list of persons Statement of Purpose The inference statement defines
any assumptions that may be made in the document The installation wizard provides step-by-step
installation instructions to follow when implementing the design

Verification test program
First page, card page Document version registration Document Contacts Table of contacts List of tables
In the list of persons Purpose Report Hypothetical report Success Criteria this is a list of criteria that must be
met to verify the successful implementation of the design Test procedures are a list of test procedures to be
followed, steps to be followed, and expected results. Operating procedures This information can be added to
a single document or split into different documents
Conduct a survey to collect feedbacks from users and explain the level of satisfaction based on user
and system requirements in the conclusion Feedbacks from Users
Figure 13 Feedback from 01



Conclusion
I have some feedback from users for the Finearts.com online auction. From this I have to focus on some and
improve performance and Quickness collection, then I have to choose the right requirement suitable for
Fineart.com auction. Finally make a good online auction for E-Solutions Private Limited
Reference
1. point, T., 2022. Data Structure and Algorithms - Queue. [online] Tutorialspoint.com. Available at:
[Accessed 13 June 2022].
2. Level, I., Manager, I., Tutorial, A., Tests, I., Us, C., Policy, P., Use, T., Us, A., Justus, K., kothari, A.,
Anderson, D., MALEME, N., ruto, m., ghislain, M., Okeke, P., Saab, K., Adhikari, P., kings, C.,
Guide, I., Withanage, I., yousafzai, s., Hussain, M., kwirirai, l., gemeda, T., Moe, N., challa, P.,
PARKS, A., PARKS, A., Student, C., Son, P., kondwani, L. and fakhar, r., 2022. What is Waterfall
model- Examples, advantages, disadvantages & when to use it?. [online] Tryqa.com. Available
at: <https://tryqa.com/what-is-waterfall-model-advantages- disadvantages-and-when-to-use-
it/> [Accessed 14 June 2022].
3. point, j., 2022. Prototype Model (Software Engineering) - javatpoint. [online]

www.javatpoint.com. Available at: <https://www.javatpoint.com/software-engineering-
prototype-model> [Accessed 14 June 2022].
4. point, T., 2022. SDLC - Spiral Model. [online] Tutorialspoint.com. Available at:
<https://www.tutorialspoint.com/sdlc/sdlc_spiral_model.htm> [Accessed 14 June 2022].
5. 99, G., 2022. Agile Methodology: What is Agile Model in Software Testing?. [online] Guru99.
Available at:
<https://www.guru99.com/agile-scrum-extreme-testing.html> [Accessed 14 June 2022].
6. Wrike.com. 2022. Why Use Agile Project Management?. [online] Available at:
<https://www.wrike.com/project-management-guide/faq/why-use-agile-project-management/>
7. Coursera. 2022. [online] Available at: <https://www.coursera.org/articles/scrum-roles-and-

responsibilities> [Accessed 14 June 2022].
8. Asana.com. 2022. [online] Available at: <https://asana.com/resources/feasibility-study>

9. Study, Q., 2022. Operational Feasibility. [online] QS Study. Available at:

<https://qsstudy.com/operational- feasibility/> [Accessed 14 June 2022].
10. simplilearn. 2022. simplilearn. [online] Available at:

<https://www.simplilearn.com/feasibility-study-
article#importance_of_feasibility_study> [Accessed 14 June 2022].
11. flatworldsolutions, B., 2022. 6 Elements of a Good Feasibility Study - Flatworld

Solutions. [online] Blog.flatworldsolutions.com. Available at:
<https://blog.flatworldsolutions.com/6-elements-good- feasibility-study/> [Accessed
14 June 2022].
12. Business, S., 2022. The Importance of a Feasibility Study. [online] Small Business - Chron.com.
Available at:
<https://smallbusiness.chron.com/importance-feasibility-study-69080.html> [Accessed 14 June
2022].

SAD Sample

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAD Sample

Uploaded by

Copyright:

Available Formats

lOMoAR cPSD| 26861203

A-004557-1655226970461-162633-System Analysis Design

Studocu is not sponsored or endorsed by any college or university

Assessor Internal Verifier

Automated system for E-Solutions Private Limited

INTERNAL VERIFIER CHECKLIST

Do the assessment criteria awarded match

Is the feedback to the student:

Assessor signature Date

Internal Verifier signature Date

Confirm action completed

Assessor signature Date

Higher Nationals - Summative Assignment Feedback Form

Assignment Number 1 Assessor

Pass, Merit & DistinctionP1 M1 D1

LO2 Produce a feasibility study for a system for a business-related problem

LO3 Analyse their system using a suitable methodology.

LO4 Design the system to meet user and system requirements.

Grade: Assessor Signature: Date:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

Pearson Higher Nationals in

Word Processing Rules

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

Student’s Signature: Date:

Higher National Diploma in Computing

Unit Number and Title Unit 4: Systems Analysis & Design

Academic Year 2021/22

Assignment Title Automated system for E-Solutions Private

IV Name & Date

Unit Learning Outcomes:

LO2 Produce a feasibility study for a system for a business-related problem.

LO3 Analyse their system using a suitable methodology.

LO4 Design the system to meet user and system requirements.

Assignment Brief and Guidance:

Additional functionality includes:

Grading Criteria Achieved Feedback

LO1 Evaluate the strengths and weaknesses of the

P1 Discuss the strengths and weaknesses of the traditional

M1 Compare and contrast the strengths and weaknesses of

LO2 Produce a feasibility study for a system for a business-

P2 Produce a feasibility study for a system for a

M2 Evaluate the relevance of the feasibility criteria on

LO1 & LO2

LO3 Analyse their system using a suitable

P3 Review a system using a suitable methodology for a

LO4 Design the system to meet user and system

P4 Design a fully functional system to meet user and

M4 Assess the effectiveness of the system design with

LO3 & LO4

Downloaded by umair faisal Ismalic (umairfaisalislamic@gmail.com)

HND in Computing and Application Development,

ESOFT Metro Campus Trincomalee

M.A.M. Akram System Analysis & Design 14 | P a g e

The process and roles of extreme programming ........................................................................................... 41

Principles of extreme programming ............................................................................................................... 42

4. Organizational feasibility ........................................................................................................................ 55

1) Technical Feasibility ................................................................................................................................ 55

5.2 Observation .............................................................................................................................................. 68

5.4 User Stories ............................................................................................................................................... 68

Figure 1 Diagram of Waterfall model................................................................................................ 22

Traditional Software Development Methodology

List of traditional methodology