54-1547092378635-Unit 34 SAD - Assignment 2018.11.13
54-1547092378635-Unit 34 SAD - Assignment 2018.11.13
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 Pass Merit Distinction
criteria the Assessor has
awarded.
INTERNAL VERIFIER CHECKLIST
Assessor Feedback:
LO1 Evaluate the strengths and weaknesses of the traditional and agile systems analysis
methodologies
Pass, Merit & Distinction P1 M1 D1
Descripts
Resubmission Feedback:
* 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.
Pearson Higher Nationals in
Computing
Unit 34: Systems Analysis & Design
Assignment 01
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).
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.
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.
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.
Issue Date
Submission 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.
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.
*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.
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.
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.
Grading Criteria Achieved Feedback
LO3 & 4
D2 Justify the choice of the analysis methodology used in
the context of the business problem.