Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)
INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title
BTEC Higher National Diploma in Computing
Assessor
Unit(s)
Assignment title
Internal Verifier
Unit 34: System Analysis & Design
Online Auction Website for the fineArts.com
Student’s name
Pass
List which assessment criteria
the Assessor has awarded.
Merit
Distinction
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
student work?
Y/N
Has the work been assessed
accurately?
Y/N
Is the feedback to the student:
Give details:
• Constructive?
• Linked to relevant assessment criteria?
• Identifying opportunities for
improved performance?
• Agreeing actions?
Y/N
Y/N
Y/N
Does the assessment decision need
amending?
Y/N
Y/N
Assessor signature
Date
Internal Verifier signature
Date
Programme Leader signature (if required)
Date
Confirm action completed
Remedial action taken
Give details:
Assessor signature
Date
Internal Verifier
signature
Date
Programme Leader
signature (if required)
Date
P a g e 1 | 48
Higher Nationals - Summative Assignment Feedback Form
Student Name/ID
Unit 34: System Analysis & Design
Unit Title
Assignment Number
1
Assessor
Submission Date
Date Received
1st submission
Re-submission Date
Date Received 2nd
submission
Assessor Feedback:
LO1 Evaluate the strengths and weaknesses of the traditional and agile systems analysis
methodologies
Pass, Merit & Distinction
Descripts
P1
M1
D1
LO2 Produce a feasibility study for a system for a business-related problem
Pass, Merit & Distinction
Descripts
P2
M2
LO3 Analyse their system using a suitable methodology.
Pass, Merit & Distinction
Descripts
P3
M3
D2
LO4 Design the system to meet user and system requirements.
Pass, Merit & Distinction
Descripts
Grade:
P4
M4
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.
P a g e 2 | 48
General Guidelines
1. A cover page or title page should be attached to your assignment. Use page 1 of this
assignment brief as your cover page and make sure all details are accurately filled.
2. The entire assignment brief should be attached as the first section of your assignment.
3. The assignment should be prepared using a word processing software.
4. The assignment should be printed single sided in an A4 sized paper.
5. Allow 1” margin on top, bottom and right sides of the paper and 1.25” on the left side (for
binding).
Word Processing Rules
1. The font size should be 12 point, and should be in the style of Time New Roman.
2. Set line spacing to 1.5. Justify all paragraphs.
3. Ensure that all headings are consistent in terms of size and font style.
4. Use footer function on the word processor to insert your name, unit, assignment no, and
page number on each page. This is useful if individual sheets get detached from the
submission.
5. Use the spell check and grammar check function of the word processing application to review
the use of language on your assignment.
P a g e 3 | 48
Important Points:
1. Carefully check carefully the hand in date and the instructions given with the assignment. Late
submissions will not be accepted.
2. Ensure that sufficient time is spent to complete the assignment by the due date.
3. Do not wait till the last minute to print or bind the assignment. Such excuses will not be
accepted for late submissions.
4. You must be responsible for efficient management of your time.
5. 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.
6. Failure to achieve at least a PASS grade will result in a REFERRAL grade.
7. Non-submission of work without valid reasons will lead to an automatic REFERRAL. You will
then be asked to complete an alternative assignment.
8. If you use other people’s work or ideas in your assignment, it must be properly referenced,
using the HARVARD referencing system, in your text or any bibliography. Otherwise, you’ll be
found guilty of committing plagiarism.
9. If you are caught plagiarising, your grade will be reduced to a REFERRAL or at worst, you could
be excluded from the course.
P a g e 4 | 48
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 Edexcel 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:
(Provide E-mail ID)
Date:
(Provide Submission Date)
P a g e 5 | 48
Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number
Unit Number and Title
Unit 4: Systems Analysis & Design
Academic Year
2018/19
Unit Tutor
Assignment Title
Online Auction site for the fineArts.com
Issue Date
Submission Date
IV Name & Date
Submission format
The submission is in the form of an individual written report. This should be 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 using the Harvard referencing system. Please
also provide a bibliography using the Harvard referencing system. The recommended
word limit is 2,000–2,500 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.
P a g e 6 | 48
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
fineArts.com needs a Online auction system for selling fine art items on the
Internet. The application provides a server side access to catalogue and record
the items on auction. The customer can locally subscribe and participate to the
auction from the web using a web browser.
The main system features are:

Items on auction are characterized by a code, an image, a description, and
a category (i.e. painting, print, silverware, etc.). Each item has an auction
starting date and time, and an end date and time (auction interval).

Items on auction are characterized by a status which specifies the starting
price, the current price, the minimum bid increment, the time remaining
before the end of the auction.

The item features and its status are displayed in a specific item web page.
Items on auction can be added, deleted and modified using an application
local to the server.

A Web site allows users to look at items on auction, navigating among them
using various searching/sorting capabilities, for example, by category, and
through other kinds of search (keyword, cost, auction end date, etc).

The Web site allows users to ask for and receive a user ID and password after
subscribing for the auction by providing personal data.

Bids can be placed only during the auction interval by registered users, and
can only be one or more bid increment higher than the current bid. After
the client has subscribed for the auction he/she can access to a personal
page which takes track of all the items he/she is concurring to buy.

After the auction end time, no more bids can be accepted, and the item is
assigned to the user with highest bid.
P a g e 7 | 48
Activity 01
Activity 1.1
a. Identify and explain traditional and Agile system analysis methodologies
used in the industry.
b. Explain the strengths and weaknesses of the traditional and agile
systems analysis methodologies explained in part (a).
Activity 1.2
a. Explain similarities and differences of strengths and weaknesses
identified in task 1.1.
Activity 1.3
a. Give your opinion as to what extents agree with the similarities and
differences identified in task 1.2. Justify with evidences.
b. Describe transition problems faced by organizations when they move
from traditional approach to agile approach. Justify your answer.
Activity 2
Activity 2.1
a. Discuss the importance and purpose of conducting the feasibility study
on system investigation by considering the given scenario.
b. Produce the feasibility report with suitable recommendations. It should
cover different feasibility criteria including Technical, Economic,
Cultural, Legal, Operational and Schedule.
Activity 2.2
a. Explain the impact of Technical, Economic, Cultural, Legal, Operational
and Schedule criteria for the given scenario. Provide evidences taken
from the scenario.
P a g e 8 | 48
Activity 3
Activity 3.1
a. Provide suitable tool(s) to collect user and system requirements.
b. Identify user and system requirements/ constraints for the system.
c. Create user stories for identified for user requirements.
d. Identify and explain the most suitable methodology for the analysis of
the system. Answer should cover features, advantages and
disadvantages of the selected methodology.
Activity 3.2
a. Explain how the selected methodology in task 3.1 c) can be used to
improve the effectiveness of the analysis stage.
Activity 3.3
a. Explain reasons to select the methodology in task 3.1 c) for the given
scenario. Provide evidences to support your ideas and points of view.
Activity 4
Activity 4.1
a. Provide the system specification for the above scenario using the
methodology you selected. Documentation should include ERD,
Prototyping techniques, flow charts for important functionalities,
release plan and tools used.
Activity 4.2
a. Explain how the system design can be used to improve the effectiveness
of the selected methodology relevant to the above scenario.
b. Conduct a survey to collect feedbacks from users and explain the level
of satisfaction based on user and system requirements in the
conclusion.
P a g e 9 | 48
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 abusinessrelated problem.
P2 Produce a feasibility study for a system for a
business related problem.
M2 Evaluate the relevance of the feasibility criteria on
the systems investigation for the business related
problem.
LO1 & 2
D1 Critically evaluate the strengths and weaknesses of
the traditional and agile systems analysis methodologies,
including the transition problems faced by organisations
that move from the traditional to the agile approach.
P a g e 10 | 48
LO3 Analyse their system using a suitable
Methodology
P3 Analyse a system using a suitable methodology for a
business-related problem.
M3 Evaluate the effectiveness of the analysis in the
context of the methodology used.
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
particular reference to the methodology used and how
the design meets user and system requirements.
LO3 & 4
D2 Justify the choice of the analysis methodology used in
the context of the business problem.
P a g e 11 | 48
Table of Contents
Activity 1 ............................................................................................................................................ 15
Activity 1.1 .......................................................................................................................................... 15
Traditional Software Development Methodology ............................................................................... 15
Agile Software Development Methodology ........................................................................................ 16
Explain the strengths and weaknesses of the traditional and agile systems analysis methodologies
explained in part .............................................................................................................................. 17
Agile model strengths...................................................................................................................... 18
Agile model weaknesses ................................................................................................................. 19
Traditional methodologies ................................................................................................................... 20
Strengths of Traditional Methodology ............................................................................................ 20
Disadvantages of traditional Project Management .......................................................................... 21
Activity 1.2 .......................................................................................................................................... 22
Activity 1.3 .......................................................................................................................................... 24
Traditional method .......................................................................................................................... 24
Why is Agile preferred not traditional approach ............................................................................. 26
Activity 2 ............................................................................................................................................ 28
Activity 2.1 .......................................................................................................................................... 28
What is Feasibility? ......................................................................................................................... 28
Types of Feasibility ......................................................................................................................... 28
Importance of Feasibility Study ...................................................................................................... 29
What is a Feasibility Report? .............................................................................................................. 30
What is a feasibility study?.............................................................................................................. 30
Important Features of a Basic Feasibility Report ............................................................................ 30
Activity 2.2 .......................................................................................................................................... 37
The impacts of different feasibility criteria on a system investigation ................................................ 37
Task 3 ................................................................................................................................................. 39
Task 3.1 ............................................................................................................................................... 39
Provide suitable tool to collect user and system requirements ............................................................ 39
Create user stories for identified for user requirements................................................................... 40
Identify and explain the most suitable methodology for the analysis of the system ....................... 40
Advantages waterfall model ............................................................................................................ 42
Disadvantages waterfall model........................................................................................................ 42
Activity 3.2 .......................................................................................................................................... 44
What is waterfall model............................................................................................................... 44
P a g e 12 | 48
Activity 3.3 .......................................................................................................................................... 44
Activity 4 ............................................................................................................................................ 45
Activity 4.1 .......................................................................................................................................... 45
Explain how the system design can be used to improve the effectiveness of the selected methodology
relevant to the above scenario. ............................................................................................................ 45
Conduct a survey to collect feedbacks from users and explain the level of satisfaction based on user
and system requirements in the conclusion. ........................................................................................ 46
References ........................................................................................................................................... 48
Tables of Figures
Figure 1 lifecycle process in Agile methodologies ........................................................................... 17
Figure 2:- Agile Methodology VS The Traditional Methodology ................................................. 23
Figure 3:- feasibility? ....................................................................................................................... 28
Figure 4:- Doc 01 ............................................................................................................................... 32
Figure 5:- Page 01 .............................................................................................................................. 33
Figure 6:- Page 2 ................................................................................................................................ 34
Figure 7:- Page 3 ................................................................................................................................ 35
Figure 8:- System ............................................................................................................................... 36
Figure 9:- Sequence chart ................................................................................................................. 39
Figure 10:- Waterfall model ............................................................................................................. 41
Figure 11:- Development methods ................................................................................................... 43
Figure 13:- Feedback Form .............................................................................................................. 47
P a g e 13 | 48
Activity 1
Activity 1.1
Traditional Software Development Methodology
One major difference between traditional and fast methods is the sequence of stages
in which the software development project is completed.
The traditional method uses a linear approach, where the stages of the software
development process must be completed sequentially. This means that one stage must be
completed before the next stage can begin.
These stages usually comprise the following:
1. Requirements gathering and documentation
2. System design
3. Code and unit testing
4. System testing
5. User acceptance testing
6. Bug fixes
7. Product delivery
The faster methodology, on the other hand, uses a repetitive and group-based approach. Its
main purpose is to deliver the application quickly with complete and functional
components. Instead of completing software development tasks sequentially, they are
completed within 1 to 4 weeks of spraying. Incomplete functions in Sprint will be
redesigned and added to future speed. This means that different stages of the software
development lifecycle can be reconsidered as needed.
General quick access includes the following steps

Starting projects

Sprint design

DIMOS
P a g e 14 | 48
With the traditional methodology, the details of the entire project are visualized and
defined before the project begins. In contrast, the faster methodology allows for more
flexibility even after the project has started. It is best if the scope of the project cannot be
clearly defined in advance. This means that unplanned software development changes are
faster than traditional methods.
Agile Software Development Methodology
Faster software development is more than just frames like Scrum, Extreme
Programming or Feature-Driven Development (FDD). Faster software development is
more than just applications like dual programming, test-based development, stand-up,
design sessions, and Sprint. Accelerated software development is an umbrella for a set of
frameworks and applications based on the principles and principles set out in the Policy
Statement for Rapid Software Development and the 12 principles behind it. When you
approach software development in some way, it is usually best to live by these values and
principles and use them to find the right thing to do in your particular context. One thing
that sets Agile apart from other software development approaches is the focus on the
people who do the work and how they work together. Solutions evolve through
collaboration between self-organized cross-functional groups. The Agile software
development community focuses on collaboration and the self-organizing team.
That means no managers. That means teams have the ability to figure out how to approach
things on their own. This means that those groups are cross-active. Those teams don’t have
to have a specific role, and when you put the team together, make sure you have the right
skills in the team. There is still room for managers. Managers make sure team members
have or have the right skill sets. Managers provide an environment that allows the team to
succeed. Managers are often reluctant and allow their team to figure out how to deliver
products, but still act when teams try but can’t solve problems. (Anon., n.d.)
P a g e 15 | 48
Figure 1 lifecycle process in Agile methodologies.
At the beginning of the project, the customer shares the initial set of requirements
into user stories. The Scrum Master or Product Owner organizes these user stories
and divides them into different sprints. In general, Sprint contains 3-4 user stories
over the course of four to five weeks, which are approximate numbers, depending on
the complexity of user stories.
Once Sprint is planned, the selected user stories are again divided into tasks so that
the developer can have a clear roadmap to deliver quality output. At the end of each
sprint, the customer will have the opportunity to review and predict the final return
and suggest changes.
Explain the strengths and weaknesses of the traditional and agile systems analysis
methodologies explained in part
Faster strategies are based on faster development cycles and greater distribution of
software pieces and the culmination of constant interaction with the customer. Every new
cycle of software development depends on customer feedback and performance. The
development project is highly flexible and responsive to change due to constant
collaboration with the customer and continuous distribution of software components.
P a g e 16 | 48
Agile model strengths

High flexibility of the project. Short cycles and regular iterations allow you to adapt
your project frequently and adapt it to the needs of the customer at any time. You do
not want to be frustrated if you cannot get the right pitch so invest in a good capo.
This makes the development process extremely flexible.

High customer satisfaction with the development process. As Agile projects are
closely coordinated with the customer, he / she has a strong impact on the
development project. Software pieces are constantly delivered in short cycles and
customer feedback is always taken into consideration.

Constant interaction between stakeholders. When your teams are constantly
interacting with each other and with the client, you avoid producing tons of technical
documentation, processes, and tools. Every member feels an important part of the
team participating in the decision-making process. This stimulates creativity and
initiative and gives better results.

Continuous quality assurance, attention to detail. The test team must ensure the
quality of the product from the earliest stages of rapid development. Since
development takes place in a short cycle, the test continues to work and allows you
to produce a good final product.
P a g e 17 | 48
Agile model weaknesses

Problems with workflow coordination. Several small teams work on their own
software pieces for quick projects. They should always coordinate their work with
each other, inspectors and management. Add to that constant interaction with the
client, you will get tons of communication management to consider before starting
the project. Although many interactions are considered an advantage of Agile
methodology, it can become a weak point due to many factors.

Difficult planning in the early stages. It is essential to plan for rapid development
before starting the process. It is important to evaluate your resources, build teams
and communicate an overall vision to them before starting the project.

Professional teams are very important. Fast projects require teams to constantly make
serious decisions. This means that only experienced software developers, testers and
managers should work on the project. This software development methodology
provides several locations for chickens.

Lack of long-term planning. The lack of a final vision of the project can sometimes
be disorganized. If the customer changes his mind frequently during the process,
your project will be missed. Remember, by the end of the project you will have to
assemble and execute software components that have been modified several times
over the development cycle. Also, there are weak documents because the interaction
with the client was largely verbal. (pavil, 2016)
P a g e 18 | 48
Traditional methodologies
The traditional project management methodology is the complete methodology for
projects that operate continuously in a sequential cycle: start-up, design, execution,
supervision, control and shutdown. It is best suited for projects that can be completed in
one order. The project will be completed successfully on time and on a low budget.
Traditional project management is a universal application that includes advanced methods
used to plan, evaluate and control activities. The purpose of these methods is to achieve the
desired results on time, within the budget and in accordance with the specifications.
Traditional project management is mainly used for projects that change sequentially and
infrequently.
Strengths of Traditional Methodology
1. Cost Effective
Because it is easier to complete projects under traditional project management. That’s why
they take less time to successfully complete the timeline and meet. There are very few
opportunities to encounter errors, bugs or complex issues in project planning, planning,
testing and final implementation. Companies are happy with the traditional methodology
for small and serial projects. They take less time to complete, fewer developers and less
resources. It is also less costly as companies do not need to use high technology and
machinery to complete such projects.
2. It's Sequential
There are sequential patterns that make it easier to follow the traditional methodology. No
further development changes are required for sequential projects. If you stick to the plan
you are developing, there are best opportunities to complete your work within the schedule
and all other criteria. Facilitates sequential management and development. The traditional
model is best suited for small projects where the requirements are clear and
understandable. Each step in the traditional system has a starting and ending point. It is
therefore flexible to share progress with stakeholders and clients. Focusing on
requirements and plans before writing code reduces the risk of errors and delays.
P a g e 19 | 48
Sequential procedures require proper documentation at each stage so that the logic behind
understanding and evaluating the code can be obtained. This sequence creates the right
path for the stakeholder to gain an understanding of a specific stage.
3. Quick Time Around
A standard problem that many companies face is that they are stuck in the trenches of dayto-day operations at the expense of business development activities, no matter where they
are in the business life cycle. It is a waste of resources, money and time. There is no need
to change the traditional methodology when following a series of projects. That is why
they are delivered on time.
4. Responsible for distributable quality
Every Software Development Methodology has the goal to deliver quality development to
create a robust product, efficiently meeting to market’s demands. It is more foolish than a
fancy assumption to achieve 100% results. The realistic approach and refined precision can
be attained through dedicated competency, collaboration, coordination, and management.
Disadvantages of traditional Project Management
1) No customer focus
There is not much room for consumer feedback in every development process. Clients are
not involved and the entire development process is not open until the product is ready. It's a
waste of time if it does not meet the client's needs. It is too late to test marketing
responsibility in the final stages of production. In today's world consumer satisfaction is a
priority. The app development company determines your true position in the market
because of their happiness.
2) Time management
The problem of time management in the traditional system arises from mutual teamwork,
unity and mutual development.
P a g e 20 | 48
3) Lack of intelligence
There is not much room for the use of new ideas in the traditional methodology. The
sequential system has no room for continuous evolution. You can’t do much but follow the
sequence.
4) Lack of coordination
Subcontractors are involved not as a single dynamic group but as individuals. There is no
effort to build unity, mutual team work and commitment to development. Lack of
coordination delays development and can cause serious problems. (Anon., n.d.)
Activity 1.2
Agile Methodology VS The Traditional methodology
The agile isn’t a single tool but instead an approach inspired by the limitations of
conventional application development project management practices. Agile acts as a
remedy to the shortcomings of the waterfall approach. More specifically, agile is a
superior methodology for building software under states of uncertainty.
P a g e 21 | 48
Figure 2:- Agile Methodology VS The Traditional Methodology
P a g e 22 | 48
Benefits of Agile method

Flexible priority

Early and predictable delivery

Predictable Expenditure and Schedules

Improves quality

More transparency
Activity 1.3
In recent years, agile has taken the world of project management and software
development by storm. Everyone seems to be talking about this project management
methodology. The business world is changing rapidly and that’s why businesses are
looking for processes, approaches, and methodologies that could help them run a
business without any glitches. While there are tens of different project management
approaches, but the final choice should be made keeping the nature of the business
and its requirements in mind. Out of all the methods, traditional (Waterfall) and agile
methodologies are often pitted against each other.
Traditional method
Our development methodology consists of seven stages:
1. Define project requirements
2. Make a proposal
3. Development and approval of functional specifications
4. Develop the software and perform the alpha release
5. Perform tests and beta releases to ensure quality
6. Hold the final release
7. Improvements and continued support
P a g e 23 | 48
1. Define project requirements
In the first phase, we collaborate to ensure that we understand how our customers' business
is operating, their objectives and marketing plan. This is how we make sure we fully
understand the needs of the project. Once we understand the challenges and specific needs
of your business, we will define the scope of the project and begin to identify development
approaches and appropriate technologies. This lays the foundation for collaborative success
through efficiency, work management and exceptionally high quality end products.
2. Make a proposal
In the next step, we will use the information gathered in the first step to draft a detailed
proposal. Each proposal contains the following: Our vision for the project as a whole,
including objectives for the final product, a description of the performance of the final
product, all constraints (including work environment, budget and time frame) and other
requirements to be met. Our estimate of the size of the project, the time required and the
expected cost of software development. Our draft plan for the project, including a rough
timeline and a list of all important milestones.
3. Development and approval of functional specifications
The client can suggest changes, corrections or additions to the suggestion list. We always
try to revise the scope of the project as needed before development begins. This is the best
way to avoid unnecessary expenses and stay within the project budget. As a result of our
functional specification document, we engage in a tight back and forth process. It contains
a set of detailed specifications for the final product we are developing. It includes all the
requirements for reliability, functionality and user interface as well as non-functional
features.
4. Perform tests and beta releases to ensure quality
Software development begins with a clear definition of all project requirements and the
architecture of the software. For each project, we identify intermediate distributions shared
with the client on or before defined milestone dates. This allows the client to monitor our
progress. Customers can review each module, element, or system when it is complete and
make sure it fits their goals and path to create the final product that meets their business
P a g e 24 | 48
needs. It is important to review these intermediate distributions carefully as they facilitate
the early detection of any errors or problems.
5. Perform tests and beta releases to ensure quality
Following the release of Alpha, we undergo extensive testing and beta release to ensure
quality. All code in the software is tested for functionality, reliability and compatibility.
Our quality assurance team strives to break away from our standard procedures and ensure
that the final product meets all specifications. If any errors or omissions are found, they
will be rectified immediately in accordance with the requirements of the project.
(Anon., n.d.)
Why is Agile preferred not traditional approach
Many developers and project managers prefer to use the agile methodology for a variety
of reasons. Some of them are discussed below

More flexibility
When making changes to a product or process, the quick methodology is more flexible than
the waterfall method. If team members feel the need to experiment with something
different than what was planned at work, the quick methodology allows them to do so. The
best thing about this methodology is that it focuses more on the product rather than
following a rigid structure.

Transparency
In a quick systematization, everything is external and transparent. Clients and decision
makers are actively involved in the product launch, design, review and testing division. In
the traditional approach, the project manager controls the project while others do not make
major decisions.
P a g e 25 | 48

Scope feedback
In the traditional approach, each process is clearly defined and planned from the beginning
of the project. The project should be completed within the estimated time and budget. So
any major change or feedback that can be pushed to the due date can be avoided. Regular
feedback allows for faster management and helps to provide better feedback. (magreat,
n.d.) The challenges I see most often (some may be duplicates of existing answers, but these
are big enough problems that they are worth repeating):

Assume the goal is to get to a quick approach. You should try to take an approach
that focuses on the benefits and short feedback cycles to meet some of the challenges
in your organization (others will be revealed by following the proper approaches).
You do not have to be fast because all your competitors do it.

Forced activation by leadership without activating organized self-organizing groups.
You definitely want to direct your organization towards quick approaches, but their
role should be to direct. People close to the task must be people who know how to do
it. Individuals involved in central management have the ability to provide air
coverage and find ways for teams to gain the skills and support they need.

Assume the pace is faster to make a better profit. Quick approaches are needed but
not enough. If you want to be a more effective organization, you need to look at your
decision making and portfolio management. Even if you are diligent, you will not be
able to do all the work you need to do. You still have to make tough decisions about
what not to do.

Focus on the uses and tools, you do not know why you are so diligent at first.

You do not know why you are using it.

It is a cultural change; This is always difficult. The key is how far your organization
should go. If it's a hierarchical, Theory-X-style organization that uses steering wheel
control and external motivation, it will be more difficult if you are an employeedriven and instinctively motivated "theory-y" organization.
P a g e 26 | 48
Activity 2
Activity 2.1
What is Feasibility?
The name implies that a project uses feasibility analysis to determine the viability of
an idea, such as ensuring that an idea is legally and technically feasible as well as
economically justified. It tells us whether a project is worth investing in. Sometimes a
project will not work. There can be a number of reasons for this, including the need for
more resources, which not only prevent those resources from performing other functions,
but can also cost a company more than it can recoup by undertaking a non-profit project.
Figure 3:- feasibility?
Types of Feasibility
1. Technical feasibility
This assessment focuses on the technical resources available to the organization. It helps
organizations determine if the technical resource capacity is met and if the technical team
has the ability to actively translate ideas. Technical feasibility includes evaluating the
hardware, software, and other technical requirements of the proposed system.
P a g e 27 | 48
2. Economic Feasibility
This assessment usually involves project cost / benefit analysis and helps organizations
determine the feasibility, cost and benefits associated with a project before allocating
financial resources. It serves as an independent project appraiser and enhances project
credibility to assist decision makers in determining the positive economic benefits to the
organization provided by the proposed project.
3. Legal Feasibility
This assessment examines whether any aspect of the proposed project is lending late in
violation of legal requirements such as zoning laws, data protection laws or social media
laws. Let's say an organization wants to build a new office building at a specific location.
A feasibility study reveals that the ideal location of the organization is not zoned for that
type of business.
Importance of Feasibility Study
The importance of a feasibility study is based on the organizational desire to
“get it right” before presenting resources, time, or budget. A feasibility study can reveal
new ideas that can completely change the scope of a project. It is better to get these criteria
in advance than to know that the project is not operational. Doing a feasibility study is
always beneficial to the project as it gives you and other stakeholders a clear picture of the
proposed project.
The following are some of the key benefits of conducting a feasibility study.

Improves the focus of project teams

Identifies new opportunities

Provides valuable information for the "go / go" decision

Narrow business options

Identifies a valid reason to accept the project

Evaluating multiple parameters increases the success rate

Project decision making assistance
(Simplian, 2020)
P a g e 28 | 48
What is a Feasibility Report?
A feasibility report is evidence that seeks to create some kind of action. Feasibility
reports are created to convince / assist decision makers to choose from the available
options. Remember that it is not just your choice, decision makers can choose many
things. A feasibility report determines whether the task being reviewed can be done with
available resources or how many resources are needed to complete the task. Feasibility is
useful in a variety of situations, such as event planning, financing, or home renovation.
(Anon., n.d.)
What is a feasibility study?
Feasibility study is a method of assessing the practicality and suitability of a project.
Before a company invests time and money in a project, they need to know how successful
the project will be before investing. Sometimes companies need to understand the input
costs, the amount of research that needs to be done, or the marketing potential of a
project. With input pricing, it is essential for companies to understand (even before they
have time and research for the project), how much it will cost to proceed with their
production. Companies also like to spend time researching and promoting their change or
product, and how the public / people respond to change. Are people fighting over a new
product? The purpose of feasibility studies is to provide companies with information and
analysis on whether you or your company should adopt this approach.
(Anon., n.d.)
Important Features of a Basic Feasibility Report
Introduction - You need to convince the decision maker to consider any kind of option.
You need to convince them to read your report first. Tell them what they will gain
personally or as an organization by considering your work.
Criteria / Barriers - You need to map out the criteria for what should be the absolute
benefits. This allows you to make practical and logical decisions. Your feasibility report
can be based on two criteria. First, you can divide the criteria into sections. This is best
done when you have a comprehensive report and should go deeper with the explanation.
P a g e 29 | 48
Second, you can include criteria throughout your report when the criteria apply. However,
it is important to make sure that whichever strategy you choose introduces the criteria at
the beginning of the report. It is also important to map the constraints of the solutions you
have proposed. This will show the audience that you understand and accept that no solution
is perfect. This ensures that the viewer makes a decision for their own good.
Methodology - It is very important to present accurate and relevant facts. Mention the
credible sources you used and how they came to be (internet, interview, book, etc.).
Without a credible research method or credible source, your document itself will not be
reliable.
Overview of Alternative Options - You should emphasize the key elements of every
possible option. Be sure to present them in an easy-to-understand and friendly layout.
Remember that the goal is to allow your audience to make the best decision.
Value Evaluation - This should be the bulk of your report, evaluating options using the
criteria you have created. Add charts, charts, etc. to show that you have studied your
options, and submit statistics showing the reasons why your option loses competition.
Loose Conclusions - You should mention the conclusion you have submitted. How did you
assess the options? What is the best option for your organization?
P a g e 30 | 48
Figure 4:- Doc 01
P a g e 31 | 48
Figure 5:- Page 01
P a g e 32 | 48
Figure 6:- Page 2
P a g e 33 | 48
Figure 7:- Page 3
P a g e 34 | 48
Figure 8:- System
P a g e 35 | 48
Activity 2.2
The impacts of different feasibility criteria on a system investigation
Feasibility study is the analysis of possible solutions to a problem and making
recommendations on the best option. It can determine whether a new system performs a
process more efficiently than the existing one. Feasibility studies should look at three main
areas. - Market issues, - Technical and organizational requirements, - Financial overview.
The results of this study are used to determine whether to proceed with the project or the
table. If it refers to actually approved projects, it will be used to determine the probability
of success of the project - before the actual work of the proposed project begins.

Technical
If the technical aspects are explored, the feasibility of the project is within the limits of
current technology and whether the technology exists at all, or if it is within the limits of
the resources provided (i.e. budget, schedule, ...). Among the requirements of the system
analyst organization in terms of technical feasibility, (i) an input device that can input a
large amount of data at input time (i) can be efficiently manufactured in bulk output. Time
(III) The choice of processing unit depends on the type of processing required by the
organization.

Operational
This feature defines the urgency of the problem and the acceptance of any solution.
Indicates whether the system will be used if it is being developed. Operational studies
include people-oriented and social issues: internal issues such as manpower issues, labor
protests, management resistance, organizational conflicts, and policies; External issues
including social recognition, legal aspects and government regulations. It takes into
account whether current policies and procedures support a new system, and how
institutional change affects the working lives of those affected by the system.
P a g e 36 | 48

Economic
Measuring economic impact has become a powerful and persuasive tool for those seeking
to grasp and witness the potential financial benefits of hosting a major event. Measuring
economic impact not only assesses the economic returns that public sector organizations
receive from their investments, but also shows how events deliver economic benefits allowing event organizers to develop practices that maximize these benefits.
The 'economic impact' of a major event refers to the additional costs generated within a
specific area as a result of staging the event. For many events, the biggest factor
influencing guest spending (and especially accommodation) is local influences; However,
spending by event organizers is another important factor. Economic impact studies
generally seek to verify the net difference in a host economy - in other words, to measure
cash inflows and outflows to confirm net returns.

Social
Social influences cannot happen by accident and must be managed if they are to happen.
The starting point for giving a definite social impact is to describe the distribution
mechanisms of the impact event that clearly articulate the goals and objectives designed for
an event. The reason for measuring social impact can often be directly linked to the goals
and objectives of event fundraisers. It is important to recognize that satisfying a party’s
objectives should not be the only incentive to measure the social impact of events.
Organizers of any event must be willing (directly or indirectly) to understand how their
event affects people's cognition and behavior.
(Anon., n.d.)
P a g e 37 | 48
Task 3
Task 3.1
Provide suitable tool to collect user and system requirements
Sequence diagram shows the interactions between objects over time. It provides
a top to bottom view with message being sent back and forth between the different
objects. The objects can be actors, system or sub packages within a system.
Figure 9:- Sequence chart
P a g e 38 | 48
Create user stories for identified for user requirements
Types of online auctions
There are many different types of online auctions, the most important ones are:
1. English auction
2. Dutch auction
3. Bidding fee auction
4. First-price sealed-bid
5. Second-price sealed-bid
Identify and explain the most suitable methodology for the analysis of the
system.
Software development methods play an important role in software development.
There are many methods used by professional software development companies today.
With each of those there are some pros and cons. The main purpose of these methods is to
provide smooth software development according to project needs.
Software development methodology is a framework used to structure, design and control
the information system development process. These types of development methods focus
on the software development process and not on the technical aspects of proper planning
for software development.
P a g e 39 | 48
Figure 10:- Waterfall model
P a g e 40 | 48
Advantages waterfall model

The waterfall model is a very simple and easy to understand method and that is why
it is really useful for the beginner or novice developer.

The rigidity of the model makes it easy to manage. Furthermore, each stage has a
specific distribution and a single review process

The phases of this model were prepared and completed at once, saving considerable
time

This type of development model is most effectively implemented effectively in small
projects where the requirements are well understood.
Disadvantages waterfall model

This model can only be used when there are high requirements for accuracy

This model does not apply to maintenance type projects

The main drawback of this method is that once an application reaches the test stage,
it cannot go back and edit something.

Software that runs until the end of the cycle cannot be produced

In this model, there is no option to know the final result of the entire project
P a g e 41 | 48
Figure 11:- Development methods
P a g e 42 | 48
Activity 3.2
What is waterfall model
The Waterfall Model is one of the most traditional and widely used software
development methods for software development. This life cycle model is often considered
the classic style of software development. This model explains the software development
process in a linear sequential flow, which means that any stage of the development process
begins only if the previous stage is completed. This development approach does not define
the process of going back to the previous stage to change requirements. (Anon., 2015)
Waterfall Access was the first SDLC model commonly used in software engineering to
ensure project success. Within the “waterfall” approach, the entire process of software
development is divided into separate stages. In this waterfall model, the return of one stage
is usually done in sequence to the next stage.
Activity 3.3
Waterfall Model - Design
The waterfall model is a classical model used in the system development lifecycle to
create a system with a linear and sequential approach. It is called a waterfall because the
pattern gradually develops from one stage to another. This model is divided into different
stages and uses the output of one stage as the input of the next stage. Each stage must be
completed before the next stage begins and the stage does not overlap.
The sequential stages of the waterfall model are: 
Er Requirements Addition and Analysis - All the requirements that can be
developed in the system are captured in this case and the requirements are
documented in a specification document.

Design Systems Design - Requirement specifications from the first stage are studied
at this stage and the system design is prepared. This system design helps to specify
hardware and system requirements and defines the overall system layout.
P a g e 43 | 48

Le Execution - With system design applications, the system is initially developed by
small programs called units, which are integrated with the next stage. Each unit is
developed and tested for its functionality.

Tion Integration and Testing - All units developed during the activation phase are
integrated into a system after each unit is tested. Post-integration The entire system is
checked for any errors and failures.

System deployment - after performing active and non-active tests; The product is
either deployed in the consumer environment or released to the market.

Maintenance - There are several issues that arise in the client environment. Patches
are released to fix those issues. Some better versions will be released to improve the
product. Maintenance is done to make these changes in the customer environment.
(Anon., n.d.)
Activity 4
Activity 4.1
Explain how the system design can be used to improve the effectiveness of
the selected methodology relevant to the above scenario.
One of the most critical stages in software engineering is the emergence and analysis
of requirements. The success of a software project depends on the quality of the
requirements and the associated analysis, as their output contributes to high-level design
and verification decisions. Real-time software systems are event-based and contain
temporary and resource-limited constraints. Natural-language-based specifications and
analyzes are then limited to identifying active and non-active components. Designing an
architecture or testing and verifying these systems requires a broad understanding of
dependencies, concurrent response times, and resource use. Case-based analysis methods
P a g e 44 | 48
provide a way to decompose requirements to understand the above properties of real-time
systems. However, they are not sufficient to support all real estate properties. This article
discusses and evaluates the suitability of certain event-based models in a real-time software
environment, and then suggests an approach called Timed Automata, which builds a
formal vision of when generating chronological specifications.
Conduct a survey to collect feedbacks from users and explain the level of
satisfaction based on user and system requirements in the conclusion.
Satisfied customers are more likely to make a purchase and recommend the site to
their friends and colleagues. A loyal customer is 10 times more likely to place their first
order. If we want to get valuable feedback from your customers, you have to ask them the
right question. The answers will clearly show what works well and the areas where your
activities need to be improved and how urgent they are.
P a g e 45 | 48
Figure 12:- Feedback Form
P a g e 46 | 48
References
Anon., 2015. Top 12 Software Development Methodologies & its Advantages / Disadvantages.
[Online].
Anon., n.d. 11 ADVANTAGES & 9 DISADVANTAGES OF TRADITIONAL PROJECT MANAGEMENT.
[Online]
Available at: https://wadic.net/traditional-project-management-advantages-disadvantages/
Anon., n.d. Asses The Impacts Of Different Feasibility Criteria On A System Investigation. [Online]
Available at: https://www.essay.uk.com/free-essays/information-technology/assess-impactdifferentfeasibility.php#:~:text=Asses%20The%20Impacts%20Of%20Different%20Feasibility%20Criteria%20
On%20A%20System%20Investigation,-1.&text=It%20can%20decide%20whether%20a,organiza
Anon., n.d. Definition of 'Waterfall Model'. [Online]
Available at: https://economictimes.indiatimes.com/definition/waterfall-model
Anon., n.d. Traditional Methodology. [Online]
Available at: https://www.orientsoftware.com/how-we-work/traditional/
Anon., n.d. What is a Feasibility Study/Report. [Online]
Available at: https://courses.lumenlearning.com/alamo-technicalandbusinesswriting/chapter/unit4-b_feasibility-report_readings-2/
Anon., n.d. What is Agile Software Development?. [Online]
Available at: https://www.agilealliance.org/agile101/
magreat, n.d. Why is Agile preferred not traditional approach. [Online].
pavil, 2016. Strong and Weak points of Agile. [Online].
Simplian, 2020. Feasibility Study: Types and Importance in Project Management. [Online]
Available at: https://www.simplilearn.com/feasibility-study-article
P a g e 47 | 48