ICT284 Systems Analysis and Design

Assignment 1 Marking Rubric

Student Name
Student Number
Date

The assignment will be reviewed as though it was a document forwarded to the Board of
directors in each organisation/business. Consequently, you will need to ensure that your
materials reflect a high professional standard (Remember – in the real world, your job can
depend on this). The marks allocated for the Assignment will be allotted in terms of the
percentages shown in the following table.

Part Criteria Mark

(a) Stakeholders 0-5
(5%) Listed all the stakeholders for the proposed Official-Eze system, and
in each case explained what their interest in the system is.
(b) Functional 0-7
Q1 requirements Listed and described all functional requirements for the Official-Eze
(20%) (7%) system.
(c) FURPS+ 0-8
(8%) Identified and described several non-functional requirements for
OfficialEze. Addressed all of the categories (URPS+): explained
why any of the categories were considered irrelevant.
(a) List (10%) 0-10
The list is presented professionally in a table. Completeness of the
list. Use case names and an informative brief description is
provided. Provided a very specific and accurate as possible
response. Demonstrated an adequate understanding of the concepts,
definitions, and principles of the SDLC.
Q2
(b) Use case 0-10
(20%)
diagram (10%) Diagram drawn using Visio or a similar acceptable tool. Using the
appropriate template for the diagram type.
Diagram is complete and concise. Diagram is clear and readable.
Diagram follows the correct notation and naming conventions and
includes a title and legend. Clearly states assumptions where
information is incomplete.
 0-20
Use case Results are presented professionally in the form of a table with the
Q3 modelling provided headings. Demonstrated an adequate understanding of the
(20%) event decomposition technique. Table is complete and concise.
(20%) Table is clear and readable. Table follows the correct structure and
includes a title. Demonstrated an excellent understanding of all
elements of the scenario,
1

ICT284 Systems Analysis and Design

and a high level of independent thought and critical thinking. Clear

description and illustration of data modelling.
0-20
UML domain Demonstrated an adequate understanding of how to develop a UML
model class domain model class diagram. Diagram drawn using Visio or a
diagram similar acceptable tool. Using the appropriate template for the
Q4 (20%) diagram type. Diagram is complete and concise. Diagram is clear
and readable. Diagram follows the correct notation and naming
(20%) conventions and includes a title and legend. Clearly states
assumptions where information is incomplete. Demonstrated an
excellent understanding of all elements of the scenario, and a high
level of independent thought and critical thinking. Clear description
and illustration of data modelling.
0-10
Clear sense of unity and order, logical transitions (where applicable),
highly effective opening and closing. Overall presentation and
format of the document (Standard Font Size and Colour i.e. Arial/12,
Organisation (10%)
double line spacing, page number, separate sections, aligning
paragraphs). Title page and table of contents. Good technical style,
avoiding excessive jargon.
Correct use of equations, footers and headers.
0-10
Effective choice of words, developing concise standard English
sentences, few language errors, and issues such as grammar,
Professionalism (10%)
spelling, sentence structure, fluency, and punctuation. Full
acknowledgement of the work of others and correctly formatted
reference section. Proofreading completed.
1.

1a)

The stakeholders of the proposed official-Eze system are:

- Volunteers: Referee, scorer. The Official Eze System provides the volunteers with
timely reminders, asks for availability, and provides directions to the competition
thus affecting the Volunteers directly. This makes them stakeholders.
- The managing committee of YBCA: Official Eze automates everything that had to be
done manually before this, making the job much faster and more efficient.
- Australian Bowling Association: The ABA will get a report done by Official Eze which
will make auditing the process a lot easier for them.

1b)

Functional requirements of the Official-Eze account are:

- To collect data from volunteers and maintain a database of said collected data. Data
would include if they have had training in refereeing and or/scoring, government
clearance, and current first-aid certificate.
- Send out text messages a week before a competition.
- Send Reminder messages the day before and the morning of the competition.
- To allow the system User to check through a GPS system for the location of the
competition and the routes to get there.
- Volunteers who can’t come for the match can send the system, notification and the
system will call other volunteers to assign a substitute.
- To keep track of all the various matches that are played throughout the season
- To calendar and Schedule volunteers.

1C) FURPS+
Functional requirements
- Official Eze must maintain the consistency of collected data.
- Official Eze’s data must be portable.
- Access to data should be limited and only authenticated users can access
permissible data.

Usability
- User interface and user experience must be intuitive and easy
- The app shouldn’t crash or be unresponsive, it has to be stable

Reliability
- The system must be accurate with the output it gives
- The system must provide the same results every time the same input is given
ensuring predictability
Performance
- The system should be fast with a fast response time
- The system should be modifiable and able to add new features to it

Supportability
- The system should be able to be installed by users who may not be IT savvy.
- The system should be testable.

2. Question 2

2a)
USE CASE INFORMATION
Ring Alarm The swimmer can set an Alarm for their
goal time for each lap.
Check heart rate The Swimmer can check their heart rate
to see if they are hitting their target heart
rate of 90% or above
Check Oxygen% The Swimmer’s blood oxygen levels help
tell the swimmer if their body requires
more oxygen or not.
Check water temperature The temperature of the water is checked
to see if it’s safe. Extreme temperatures
might lead to hypothermia in open water
swimmers.
Set Stopwatch The stopwatch will allow a swimmer to
measure the amount of time spent
swimming a certain distance.
Check Max-Speed The max speed achieved during a lap
might be important information for a
swimmer
Check Weather Weather information is critical for open
water swimmers as if there is a cyclone
enroute they need to be intimated
beforehand.
Check Swimming distance The distance swam by a swimmer is taken
note for the sake of performance analysis.
Check Calories burnt Athletes need to be in competition
weight, so they have to know how many
calories have been burnt during a session
so they can offset it with their diet.
Check Water Depth The depth the swimmer reaches is noted
by the water as pressure increases as a
swimmer goes down the water.
Call Emergency Services If a swimmer’s heart rate is abnormal
Emergency services is called to the
location of the athlete.
2b)
3.

Event Type of event Use case Brief Actors(only for

Description external
events)
Implement an External Event Manage and The system will Customers
information maintain manage and
System Information maintain the
booking system
along with
maintaining
customer, staff
and session
information
Logging Cave State Event Managing Cave session No External
Usage hours Session times are taken Actors
into account so
that each cave
isn’t used more
than 59 hours
before
maintenance
Inspecting cave State event Checking cave The comfort Customers
between Safety and safety of
sessions the cave are
checked.
Physical
damage,
cleanliness and
hygiene, any
dropped
belongings
from the
previous
session is
noted by the
system along
with technical
checks such as
ropes and
breathing
equipment
Providing Temporal Creation of SCACS makes No External
Adhoc Status Event Report an adhocs Actors
Report status report
on each cave,
noting date last
 serviced,
current usage
hours, next
scheduled
service,
popular
timings, types
of bookings
and plan for
expansion.
Full Daily cave Temporal Inspection of The caves are No external
Inspection Event cave inspected Actors
every day by
service
engineers
before the
sessions start
and after eery
session is
complete

4.