lOMoARcPSD|29125957
System Analysis Design Assignment
Higher National Diploma (ESOFT Metro Campus)
Studocu is not sponsored or endorsed by any college or university
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
lOMoARcPSD|29125957
Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)
INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Higher National Diploma in Computing
Programme title
Mr. Nuwan Hirantha
Assessor
Internal
Verifier
Unit 34: System Analysis & Design
Unit(s)
Online Auction Website for the fineArts.com
Assignment title
Student’s name
List which assessment
criteria the Assessor has
awarded.
Pass
Merit
Distinction
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria awarded match
those shown in the assignment brief?
Is the Pass/Merit/Distinction grade awarded
justified by the assessor’s comments on the
student work?
Has the work been assessed
accurately?
Is the feedback to the student:
Give details:
• Constructive?
• Linked to relevant assessment
criteria?
• Identifying opportunities for
improved performance?
• Agreeing actions?
Does the assessment decision need
amending?
Y/N
Y/N
Y/N
Y/N
Y/N
Y/N
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:
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
1|Page
lOMoARcPSD|29125957
Assessor signature
Date
Internal
Verifier
signature
Date
Programme Leader
signature (if
required)
Date
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
2|Page
lOMoARcPSD|29125957
Higher Nationals - Summative Assignment Feedback Form
Student Name/ID
Chamika udaminee jayakody
Unit Title
Unit 34: System Analysis & Design
1
Assignment Number
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 P1
M1
D1
Descripts
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.
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
3|Page
lOMoARcPSD|29125957
Pearson Higher Nationals in
Computing
Unit 34: Systems Analysis & Design
Assignment 01
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
4|Page
lOMoARcPSD|29125957
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.
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
5|Page
lOMoARcPSD|29125957
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.
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
6|Page
lOMoARcPSD|29125957
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.
Chamikaudamini@gmail.com
Student’s Signature:
(Provide E-mail ID)
Date:
(Provide Submission Date)
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
7|Page
lOMoARcPSD|29125957
Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number
Chamika udaminee Jayakody GAMA-012831
Unit Number and Title
Unit 4: Systems Analysis & Design
Academic Year
2018/19
Unit Tutor
Online Auction site for the fineArts.com
Assignment Title
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.
Assignment Brief and Guidance:
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
8|Page
lOMoARcPSD|29125957
*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 an 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.
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
9|Page
lOMoARcPSD|29125957
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.
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
10 | P a g e
lOMoARcPSD|29125957
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
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
11 | P a g e
lOMoARcPSD|29125957
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.
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
12 | P a g e
lOMoARcPSD|29125957
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.
M2 Evaluate the relevance of the feasibility criteria on
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
13 | P a g e
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
lOMoARcPSD|29125957
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.
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
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
14 | P a g e
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
lOMoARcPSD|29125957
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.
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
15 | P a g e
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
lOMoARcPSD|29125957
Acknowledgment
I would like to extend my sincere gratitude to all who have given me the opportunity to
complete this report, which I have completed in the third stage of my higher education at the
ESOFT Metro Campus. I would like to express my sincere gratitude to the teachers who
gave me suggestions and encouragement and helped me to understand all the subjects. I
thank my friends who inspired me to resolve some issues while writing this, as well as
fixing. In addition, I am especially grateful to my dear mother, father and brother who
always gave me strength in writing this report. In addition, I would like to take the
opportunity to appreciate all the others who helped me correct the conclusion of this report.
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
16 | P a g e
lOMoARcPSD|29125957
Table of Contents
1. Activity 01
1
1.1.
Traditional system analysis and Agile system analysis methodologies 18
1.2.
Similarities and differences of Traditional and Agile methods
1.3.
what is best method as my opinion 4
2. Activity 02
3
5
2.1.
What is Feasibility Study?
7
2.2.
Explain the impact of Technical, Economic, Cultural, Legal, Operational
6
3. Activity 03
3.1.
5
Tools and Techniques we can use to gather user needs and system need
5
4. Activity 04
4.1.
28
ERD, Prototyping techniques, flow charts for important functionalities,
release plan and tools 28
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
17 | P a g e
lOMoARcPSD|29125957
Figure List
Figure 1-Use case Diagram......................................................................................................28
Figure 2-ER Diagram...............................................................................................................30
Figure 3-Main form..................................................................................................................31
Figure 4-Register form.............................................................................................................31
Figure 5-Categories form.........................................................................................................32
Figure 6-Product Offers Form..................................................................................................32
Figure 7-Product form..............................................................................................................33
Figure 8-Bidding form.............................................................................................................33
Figure 9-Payment form............................................................................................................34
Figure 10-Flowchart.................................................................................................................35
Figure 11-User Feedback.........................................................................................................36
Figure 12-User Feedback.........................................................................................................36
Figure 13-User Feedback.........................................................................................................37
Figure 14-User Feedback.........................................................................................................37
Table list
Table 1-Differences of Traditional and Agile methods................................................................
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
18 | P a g e
lOMoARcPSD|29125957
Activity 01
1.1.
Traditional system ykh y i=
1.2.
analysis methodologies
LO|OO[]|
Traditional Software Development Methodology
The traditional method is a basic development method that takes less
time. In this system the client cannot make any changes during the development period of
the project. At the beginning of the project, the customer's needs and expectations can be
explained. However, again the client can participate in the development of the project only
after this is set up. The traditional method is a very efficient method
Agile system analysis methodologies
The project takes longer to accomplish than the traditional method. But
over time, this methodology gives the client a much better explanation of the project.
Furthermore, in this methodology customer can stay from the beginning to the end of the
project and explain their needs.
Although the agile development method takes longer than the traditional
method, it can deliver the best to the consumer. There are many differences between the
agile development method and the traditional method. Also, there are advantages and
disadvantages of agile development methodology and traditional development methodology.
That is,
 Agile development methodology
Strengths
1) Flexibility is very high.
Agile development methodology takes time, but it is very flexible. That is, the friendliness
between the customer and the company is very high when carrying out a project using this
methodology. Furthermore, the project has the ability to clearly fulfil its needs from start to
finish.
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
19 | P a g e
lOMoARcPSD|29125957
2) Bugs are very rare.
The customer-company friendship is so high that one can get what one wants for the project
without any errors. Also this methodology is very well explained to the customer. It also,
reduces the risk of errors.
3) The output is very high quality.
It takes more time, but this methodology is well explained to the customer. This will
enable the customer to get the project quality as per their requirements. The customer
has the ability to better understand the methodology. Improves quality
Weaknesses
1) Takes longer time
That is, in this fast methodology the customer will have to explain the project well. Also,
since the project has the ability to work with the client from start to finish and change the
project to his liking, this takes more time.
2) The budget cannot be determined until the end of the project.
Since the project can be changed at any time from the beginning to the end according to the
needs of the client, it is not possible to determine the exact budget.
3) Care must be taken for each part of the project.
Since this takes longer than the traditional methodology, special attention has to be paid to
this project.
 Traditional Software Development Methodology
Strengths
1) The project can be completed in a short time.
This can be done using a short period of time in project preparation using this methodology.
That is, at the beginning of the project, the project has to be completed according to the
needs of the client.
2) It is possible to set a definite budget.
Because the project will not take long to complete. Budget can be set a quickly.
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
20 | P a g e
lOMoARcPSD|29125957
Weaknesses
1) The customer cannot change the project at any time.
That is, the customer can change this at the beginning as desired. But this cannot be
changed during the project, as it takes a short time for the project.
2) It is risky and challenging.
This method is risky as it takes a short time for the project. Also, there is no time to explain
to the customer about this methodology and the project. Therefore, there is a challenges in
creating this project.
1.3.
Similarities and differences of Traditional and Agile methods
There are similarities as well as differences between the traditional and agile
development methods.
Differences of Traditional and Agile methods.
Characteristics
Agile method
Traditional method
Organizational structure
Iterative
Linear
Testing
Final stage
Every stage
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
21 | P a g e
lOMoARcPSD|29125957
Clearly defined before
User analysis
Interactive input
Development model
Evolutionary delivery
Life cycle
Involvement of clients
High
Low
implementation
Table 1-Differences of Traditional and Agile methods
[ CITATION
San \l 1033 ]
Similarities of Traditional and Agile methods.
The analytical part and the time management, which are the initial
stages of both traditional and agile development methods, are largely the same. Both
of to these methods have the same goals. That is, the project is done as well as the
customer wants from started to finished. Prepared to do a project using either
traditional or agile methodology but, for that, the same principle are used first. That
best principle was, thoroughly planning the work before starting the project.
As mentioned above, both of these traditional and agile methods have
similarities and differences.
1.4.
what is best method as my opinion
According to the above two traditional and agile methods of similarities and
differences, the agile method is the most efficient and suitable for used. The reason for this
is that the developed system is highly optimized as the customer interaction is very high
when using the accelerated development methodology. The client is involved in every stage
of the development cycle. Therefore, we find that the most important communication chain
exists between the client and the developer until the system is done.
Additionally, the server has the ability make further out of the modifications as
needed during the system develop. Therefore, system development using this methodology
increases customer satisfaction. Also, the start-up cost is lower than the traditional
methodology. In the agile methodology, every part of the developed system is phased out
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
22 | P a g e
lOMoARcPSD|29125957
and tested. Therefore, problems with system development by using this methodology are
minimal.
Activity 02
2.1.
What is Feasibility Study?
Feasibility study is the planning stage before the start of any project. It is a
compilation of information on whether or not we can do a selected the project of our choice.
It helps to identify and assess opportunities and threats in the natural environment, the
resources required for the project and the prospects for success. It is conducted in order to
find answers to the following questions:

Does the company possess the required resources and technology?

Will the company receive a sufficiently high return on its investment?

What are the functional and non-functional requirements?
The Importance of Feasibility Studies and Purpose of it
 Feasibility studies are important for business development.
 If there is a hindrance to the functioning of the business, it can be identified by this
feasibility study.
 It also identifies the amount of funding needed to grow and operate this business.
 Being able to gain some understanding of the success or failure of the business.
[ CITATION cor \l 1033 ]
According to the given scenario,
FineArts.com is an auction service provider. An online web-based system is required
for this process. A feasibility study report should be prepared before setting up this system.
Here we need to cover,

What the client needs.

What the user needs to do through the system.

How the algorithm should work.
There are several different types used in preparing a feasibility report. Feasibility report on
FineArts.com mentioned above according to those types,
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
23 | P a g e
lOMoARcPSD|29125957
Technical Feasibility
The Technical Feasibility study assesses the detail of how you will
deliver a product or service. (Ex: Materials, Labor, Physical Location, Transportation or
Shipping)
Accordingly, by FineArts.com expects an online web-based system.
For that, this technology changes over time. That is, the device we use today will become a
modern device tomorrow. Therefore, new tools must be used to set up the system when using
this method. These include newer computers, barcode scanners, scanners, Internet service
providers, and servers. The technical feasibility study this can find short term funding to set
up this online system.
Economic Feasibility
Economic viability is a cost-benefit analysis of the project examined above, to
assess whether it can be implemented.
[ CITATION
ceo \l 1033 ] FineArts.com auction service system requires a to cover the legal aspects of
the organization, as well as the training required for the new system, as well as the cost of
purchasing equipment with the above technical feasibility. By Economic viability can cover a
short-term way to cover these costs.
Cultural Feasibility
This is called a cultural feasibility study that examines all the environmental
factors that make a project a success. Factors should be well identified so as not to pose any
obstacle to the further development of the project. This project is being implemented in an
internet based environment. Furthermore, there is a distance relationship between the
customer and the client. That is, there is a potential for error because there is no face-to-face
[ CITATION evi1 \l
contact.
1033 ]
Legal Feasibility
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
24 | P a g e
lOMoARcPSD|29125957
Legal feasibility is the study of whether the proposed project meets legal and
ethical requirements. There are a number of factors to consider in a legal feasibility study,
including ethical issues and some social issues.
[ CITATION sli \l 1033 ]
Activity 03
3.1.
Tools and Techniques we can use to gather user needs and system need
 Review of procedural forms
 Interviews
 Questionnaires
 Observation
 Focus groups
 Discovery prototyping
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
25 | P a g e
lOMoARcPSD|29125957
 Joint requirements planning
Interviews
Interviews are critical to understanding and harnessing the goals and expectations of
stakeholders and users in order to create great software. Then we can properly weigh their
inputs. In this discussion, the analyst will prepare a list of questions and ask the interviewer.
Observation
After the system has been thoroughly tested by the user, Identify system bug improvement
requirements. This observation is useful for gaining an understanding of an existing business
process.
Focus groups
A targeted team is one that gathers representatives of the product's users or customers for
further information. Can be collected to refine the needs highlighted.
Discovery Prototyping
Prototyping is a relatively modern technology for assembling needs. In this approach, a
prototype of the basic requirements you use to create an initial version of the solution.
You show this to the client and then give you additional requirements.
User requirements
 A user should be able to register, update or delete their account as required.
 Only registered users can participate in the auction, Therefore the user should
be able to register when required.
 Only registered users can bid on the goods at the auction.
 The user should be able to easily find the items they want at the auction.
System requirements
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
26 | P a g e
lOMoARcPSD|29125957
 The code, image, description and category should be represented when
the client searches for the desired items.
 At the end of the auction, the bidding process must close and the item
must be assigned to the highest bidder.
Use case Diagram
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
27 | P a g e
lOMoARcPSD|29125957
Figure 1-Use case Diagram
User story
To This page is easily accessible to users using any web browser. The user should be
able to buy the desired product at an affordable price by doing this. Any user can register for
this auction. After registering on the system as a registered user, the user can bid at any
time. By requesting a specific user ID and password, users who register here cannot be
fooled. Auctioneers submit their personal information to the system. Also, if a user accesses
a continuous auction service, that user should be able to bid on that auction.
Suitable methodology
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
28 | P a g e
lOMoARcPSD|29125957
Agile methodology is the most suitable methodology to use for system analysis.
The advantages, disadvantages and specialties of this accelerated methodology were given
in relation to the first activity mentioned above. In this methodology there is always a
relationship between the client and the developer. Because of this the system will remain in
a very high state. Start-up costs less. Because the client is always with the developed
system, the client can make changes to the system as he wishes.
Why used the agile methodology?
It is more effective for system development. This method is fast and flexible.
And there is a good connection between the server and the developer in setting up
this methodology. This is useful for system development. In the agile methodology,
every function of the system begins to develop from the smallest partition. So, the
user will get a better understanding of this system. Therefore, this system was user
friendly. This is easy for the customer to use. Also, due to this methodology'
flexibility, it has the ability to activate this system in a short period of time.
Activity 04
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
29 | P a g e
lOMoARcPSD|29125957
4.1. Entity Relationship Diagram
Figure 2-ER Diagram
Prototyping
A prototype is a model version of a product. It's generally an essential part of creating a user
experience, It was usually has the ability to select ideas that meet the needs of the users.
Teams create different models of different reliability to grasp design concepts and test users.
By setting up a prototype we can set up exactly the system we hope to build. That way the
brand can release the right product. Therefore, this prototype can be modified at any time
before system development begins.
Prototyping techniques
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
30 | P a g e
lOMoARcPSD|29125957
Figure 3-Main form
Figure 4-Register form
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
31 | P a g e
lOMoARcPSD|29125957
Figure 5-Categories form
Figure 6-Product Offers Form
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
32 | P a g e
lOMoARcPSD|29125957
Figure 7-Product form
Figure 8-Bidding form
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
33 | P a g e
lOMoARcPSD|29125957
Figure 9-Payment form
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
34 | P a g e
lOMoARcPSD|29125957
Flowchart of the system
Figure 10-Flowchart
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
35 | P a g e
lOMoARcPSD|29125957
User Feedback
Figure 11-User Feedback
Figure 12-User Feedback
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
36 | P a g e
lOMoARcPSD|29125957
Figure 13-User Feedback
Figure 14-User Feedback
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
37 | P a g e
lOMoARcPSD|29125957
Bibliography
(n.d.). Retrieved from slideshare: https://www.slideshare.net/RISHIGUPTA88/legalfeasibility
ceopedia. (n.d.). Retrieved from https://ceopedia.org/index.php/Economic_feasibility
corporatefinanceinstitute. (n.d.). Retrieved from
https://corporatefinanceinstitute.com/resources/knowledge/other/feasibility-study/
evirtualservices. (n.d.). Retrieved from https://www.evirtualservices.com/cultural-feasibility
Kashyap, S. (n.d.). Proofhub. Retrieved from https://www.proofhub.com/articles/traditionalvs-agile-projectmanagement#Difference_between_traditional_and_agile_project_methodology
JKC UDAMINEE JAYAKODY System Analysis Design
HND COM 23
GAM/A-012831
Downloaded by Karthees Sarma Vlog (karthees2002@gmail.com)
38 | P a g e