MIS605_Assessment 1_Brief_Written Assessment Page 1 of 5Sample Page
Task Summary
In response to the case study provided, identify the functional and the non-functional requirement for
the required information system and then build a Use Case Diagram and document set of use cases.
Context
System analysis methods and skills are of fundamental importance for a Business Analyst. This
assessment allows you to enhance your system analysis skills by capturing the business and then
functional and non-functional requirement of a system. It helps you in identifying “what” the proposed
system will do and “how”?.
ASSESSMENT 1 BRIEF
Subject Code and Title
MIS605 Systems Analysis and Design
Assessment
Written assessment
Individual/Group
Individual
Length
2000 words +/ 10%
Learning Outcomes
The Subject Learning Outcomes demonstrated by successful
completion of the task below include:
a) Identify, critically evaluate and recommend information
systems solutions for inefficiencies in business processes,
procedures and work practices using data and process
modelling techniques.
b) Formulate, validate and document business requirements
for a medium-scale information system development
project and effectively communicate these requirements to
the stakeholders.
c) Demonstrate the ability to effectively analyse, design and
develop information systems using Unified Modelling
Language (UML) models.
Submission
Due by 11:55pm AEST Sunday end of Module 3.1
Weighting
30%
Total Marks
100 marks
MIS605_Assessment 1_Brief_Written Assessment Page 2 of 5
Instructions
1. Please read the attached MIS605_ Assessment 1_Case Study. Note that every piece of
information provided in the following case serves a purpose.
2. Once you have completed reading the case study. Please answer the following questions:
Question 1 (10 mark).
Identify all the human and non-human actors within the system. Provide brief description against
every actor.
Question 2 (30 marks).
Using the information provided in the case study, build a Use Case Diagram using any diagramming
software.
Note: Please make assumptions where needed.
Question 3 (60 marks).
Document all use cases (use case methods). All use cases identified in the Use Case Diagram in
Question 2 must be elaborated in detail. Please document each use case using the following template:
Use Case Number
Use Case Type
Base/Abstract (Extends or Includes)
Use Case Name
Priority
Actor Involved
Associated Data
Sources
Associated User
Interfaces
Pre-Condition(s)
Post Condition(s)
Detailed
Description
MIS605_Assessment 1_Brief_Written Assessment Page 3 of 5
Normal Course
of Events Using a
Flow Chart
Diagram
Alternate
Course(s)
Word Count and Layout
The total word count for the written assessment should be no more than 2000 words.
Please provide all your answers in a MS word document.
Please note that you are NOT required to copy the questions over to the MS Word document.
Use the question number to indicate which question your answer relates to.
The recommended font size is 12 with 1.5 spacing.
Referencing
It is essential that you use appropriate APA style for citing and referencing if needed. Please see
more information on referencing here http://library.laureate.net.au/research_skills/referencing
Submission Instructions
Please submit the written assessment via the Assessment link within Assessment 1. The Learning
Facilitator will provide feedback via the Grade Centre in the LMS portal. Feedback can be viewed in
My Grades.
MIS605_Assessment 1_Brief_written Assessment Page 4 of 5
Marking Criteria
F
P
C
D
HD
Question 1: Identify all the human
and non-human actors within the
system. Provide brief description
against every actor.
10%
Actors identified are
largely incorrect.
Actors identified are
partially incorrect.
Actors identified are
correct but sufficient
detail is not provided.
Actors identified are
correct and sufficient
detail is provided.
Actors identified are
correct and sufficient
detail is provided. The
student has clear
understanding of
human and non
human actors.
Question 2: Using the information
provided in the case study, build a
Use Case Diagram using any
diagramming software.
30%
UCD does not include
major use cases, many
actors in the UCD are
missing, association of
base and abstract
actors is not given
with the use cases,
extends and includes
are not identified
where required and
not linked to base use
case. The use case
diagram does not sync
in well with the
requirements laid
down in the case
study.
UCD misses some
important use cases,
some actors in the
UCD are missing, some
associations of base
and abstract actors
are not given with the
use cases, extends and
includes are partially
identified (where
required). Extends and
includes and not
appropriately linked to
the base use cases.
The use case diagram
does not fully sync
with the requirements
laid down in the case
study.
UCD has all the use
cases and actors,
some associations of
base and abstract
actors are not given
with the use cases,
extends and includes
are partially identified
(where required).
Extends and includes
are not appropriately
linked to the base use
cases. The use case
diagram largely syncs
with the requirements
laid down in the case
study.
UCD has all the use
cases and actors,
associations of base
and abstract actors
are given with the use
cases, extends and
includes are identified
(where required).
Extends and includes
and not appropriately
linked to the base use
cases. The use case
diagram syncs in
completely with the
requirements laid
down in the case
study.
UCD has all the use
cases and actors,
associations of base
and abstract actors
are given with the use
cases, extends and
includes are identified
(where required).
Extends and includes
and appropriately
linked to the base use
cases. The use case
diagram syncs in
completely with the
requirements laid
down in the case
study.
MIS605_Assessment 1_Brief_written Assessment Page 5 of 5
Marking Criteria
F
P
C
D
HD
Question 3: Document all use cases
(use case methods).
60%
Use case descriptions
are incomplete and do
not sync in with the
given case study.
Use case descriptions
are partially
incomplete and do not
fully sync in with the
given case study.
Use case descriptions
are complete but do
not fully sync in with
the given case study.
Use case descriptions
are complete and are
in sync in with the
given case study.
Use case descriptions
are complete, detailed
and are in sync in with
the given case study.
