Assessment Brief: BIS2002/SBM4201 Systems Analysis and Design
Trimester 1, 2022
Assessment Overview
Assessment Task
Type
Weighting
Length
Due
ULOs Assessed
Assessment 1
Case Study
Covers the following topics:
Systems Development Life Cycle (SDLC), Work Breakdown Structure (WBS), PERT/CPM Chart, NPV, ROI and Payback Period
Group
(Max 3 people)
30%
3000 words
equiv.
Week 5
ULO1
ULO2
ULO3
Assessment 2
Case Study
Covers the following topics:
Use Case Diagram, ER Diagram Class Diagram, Sequence Diagram, Activity Diagram, User and System Interfaces, and System Testing, Deployment, and Maintenance
Individual
30%
2500 words
equiv.
Week 12
ULO1
ULO2
ULO3
ULO4
Assessment 3: Project Design
Every two weeks exercises assess students’ ability to understand theoretical materials
Individual
Invigilated
40%
2500 words
equiv.
Weeks
2, 4, 6, 8, 10
ULO-1
ULO-2
ULO-3
ULO-4
ULO-5
equiv. – equivalent word count based on the Assessment Load Equivalence Guide. It means this assessment is equivalent to the normally expected time requirement for a written submission containing the specified number of words.2
Assessment 1: Case Study
Due date:
Week 5
Group/individual:
Group (Max 3 people)
Word count / Time provided:
3000 words
Weighting:
30%
Unit Learning Outcomes:
ULO-1, ULO-2, ULO-3
Assessment Details:
In this assessment event, you must design an information system for the Comedy Hour Booking System case study provided at the case study section. This assessment covers the following topics:
Systems Development Life Cycle (SDLC), Work Breakdown Structure (WBS), PERT/CPM Chart, NPV, ROI and Payback Period
Case Study Scenario: Comedy Hour Booking System
Organisational Background
Comedy Hour is a comedy club located in Sydney. Founded by two former stage comedians, Bo and Jo, the club grew from a few shows a week, to a fully booked weekly schedule that starts at 6pm until 12pm each night.
Comedy Hour Booking System
Comedy Hour would like to develop an online system for booking shows.
The new online booking system intends allow customers to book for their shows, pay for it using their credit cards, remind them of their booked appointments, and notify them about upcoming events. The system will also send a notification notice to the entertainer and to his/her manager for any booked (or cancelled) shows. The audience can also provide feedback for the performance after the show through the app. The system should also identify loyal customers and reward them with a free show (as a rule of thumb, any customers who have attended 12 shows in one year, or the equivalent of $5000 worth of purchase will be rewarded with one free show).
The customers are required to create an account before booking any ticket for the first time. An email will be sent automatically by the system to confirm membership, where the customer is required to confirm by clicking a confirmation button on the email. Once confirmed, he/she can now book for one to an unlimited number of tickets (depending on the capacity of the show and the number of seats available). Each booking will generate at least two emails, first, the booking confirmation right after the booking, and second, a reminder of the booking 2 days before the event. A member can only cancel/update the booking less than 24 hours before the event. Once the 24 hours was gone, there is no more option to cancel/update, and the member’s credit card payment will be charged whether they come or not. If for whatever reason a show is cancelled, a cancellation email will be sent to the member’s inbox, including a refund of their payment. A copy of the cancelled show email will also be sent to the entertainer and to his/her manager. If members are trying to book a fully booked show, the system provides a option for a stand-by status, and if a seat becomes available, each member will be notified according to their position in the queue and the seating availability status.
The Information collected consists of the customer’s first and last name, residential address, city, zip code, mobile number, and email address. After entering all the information, a unique identification number is created for each customer.
Further, the new online system records the title of the show, the entertainers (classified as main and cast), manager (if any), the date/time, and the price.
Also, the number of tickets sold for each show will also be recorded. Each show will also be identified with a unique identifier.
Each entertainer’s details will be recorded, such as their name, address, telephone, email, genre (example of comedy genre are Dark comedy, Burlesque, Character, Cringe, Deadpan, Improvisational, Musical, Observational, Prop, Sitcom, Ventriloquism), how much they charge per hou
show, and if they are represented by a manager, their manager’s details (name, company name, office address, telephone, mobile, etc).
Each entertainer is managed by only one manager, but a manager manages at least one entertainer up to several entertainers at a time. Each entertainer’s show might fall into just one specific genre and/or several genre categories. An entertainer performs at least one show per night or several shows, depending on the demand.
Since the system will be storing customer details and credit card payments, the form must be WCAG compliant, PCI DSS compliant, TLS certified, among all other web security standards. To prevent data entry mistakes, the should should preferably use automated features such Calendar objects, drop-down lists and the like. The form should reflect the company colour which is black and red for
anding purposes.
Comedy Hour wishes to operate an entirely testable procedure to the whole online system to discover any bug and major issues before the final launch of the system. For example, it should be compatible with all major web
owsers, such as MS Edge, IE, Mozilla Firefox, Google Chrome, and Safari. It must also adjust to different monitor sizes and screens, such as smartphones, tablets, laptops and PCs.
Here’s the project schedule:
Task
Description
Duration (Days)
Predecessor Tasks
A
Determine user requirements
5
-
B
Data collection
7
A
C
Feasibility analysis
8
A
D
System documentation
5
B
E
Management presentation
1
B, C
F
System design
8
D, E
G
Purchase hardware
10
F
H
Write application code
10
F
I
Test system
6
G, H
The company considers different methods to estimate the investments in this project. Table 1 presents the information the accountant provided to the system analyst to calculate Net Present Value (NPV), Payback Period and Return on Investment (ROI).
Yea
No.
Category
0
1
2
3
4
5
1
Value of benefits
$ 9,000.00
$ 9,000.00
$ 9,000.00
$ 9,000.00
$ 9,000.00
2
Development Cost
-$15,000.00
-$700.00
- $850.00
-$770.00
-$750.00
-$730.00
3
Annual expenses
-$ 3,000.00
-$ 3,000.00
-$ 3,000.00
-$ 3,000.00
-$ 3,000.00
4
Net benefit/costs
-$15,000.00
5
Discount facto
XXXXXXXXXX
6
Net present value
-$15,000.00
7
Cumulative NPV
-$15,000.00
Table 1: Five-year investment evaluation
Tasks:
1. Write a
ief description of the project and clearly define the aims and objectives of the report
1. Write the vision of the project (or what the new systems will accomplish)
1. Explain the requirements for the new system (FURPS requirements)
1. Develop a Work Breakdown Structure (WBS) using the details from the project schedule. The WBS should be created using a suitable software (not hand drawn) and follow similar convention below:
1. Develop PERT/CPM chart using a suitable software (not hand drawn) explaining the early and late start for each task. Identify the critical path and the total time to finish the project.
1. Recognize internal and external stakeholders for the new system.
1. Use the information in Table 1, perform financial analysis by calculating the net present value, the payback period, and the return on investment using a discount rate of 6%. The development costs for the project were $15,000. Do a five-year return on investment.
You may need to make some assumption as required. Whenever you make assumptions, please state these clearly.
Assignment Format
Submission: Only through Canvas
Length: 2500 words max (+ or – 10%) equiv
Font size: 12pt (min) Times Roman
Line spacing: 1.5 or double line spacing
Cover sheet: APIC standard coversheet
Referencing: Not required
Marking Criteria and Ru
ic: The assessment will be marked out of 100 and will be weighted 30% of the total unit mark.
Marking Criteria
Not satisfactory
(0-49%) of the criterion mark)
Satisfactory
(50-64%) of the criterion mark
Good
(65-74%) of the criterion mark
Very Good
(75-84%) of the criterion mark
Excellent
(85-100%) of the criterion mark
Introduction
(10%)
Poor introduction with i
elevant details
Introduction is presented
iefly and is missing the report outline
Introduction is generally presented along with the report outline
Introduction is well written, and the report outline is also discussed
Introduction is very well written, and the report outline is also discussed
System vision statement 15%)
Poor development of the system vision statement.
Brief development of the system vision statement.
Good development of the system vision statement.
Well development of the system vision statement.
Excellent development of the system vision statement.
FURPS requirements
(10%)
Poor description of FURPS requirements
Brief description of FURPS requirements
Generally good description of FURPS requirements
Clear description of FURPS requirements
Very good description of FURPS requirements
Work Breakdown Structure (WBS) (15%)
Poor description and did not use a suitable software using the suitable convention recommended
Brief description and used a suitable software using the suitable convention recommended
Generally good description and used a suitable software using the suitable convention recommended
Clear description used a suitable software using the suitable convention recommended
Very good description using a suitable software using the suitable convention recommended
PERT/CPM chart (15%)
Lack of evidence of understanding of PERT/CPM chart with no identification of critical path and the total time to finish the project.
Evidence of basic understanding of PERT/CPM chart with no clear identification of critical path and the total time to finish the project.
Evidence of good understanding and identification of PERT/CPM chart with clear identification of critical path and the total time to finish the project.
Clear understanding and identification of PERT/CPM chart with clear identification of critical path and the total time to finish the project.
Excellent understanding and identification of PERT/CPM chart with clear identification of critical path and the total time to finish the project.
Internal and External stakeholders
(10%)
Poor description of internal