Monash University

FIT9130 – Systems Analysis and Design, Semester 1, 2024

Assignment 1 (Groups of 3-4)
Due in Sunday 28 April 2024, 11:55pm, Week 8 (Interviews in Week 9)

You should read this assignment specification carefully. It outlines what you need to do, what
you need to submit and how your submission will be assessed.

1. Assignment Overview
In this assignment, you will produce a Systems Analysis specification (requirements
specification) report for the case described in Section 9 using several UML analysis
techniques. Note that this is a group assessment.
The assessment consists of three main segments:
1. an analysis specification report containing the narrative overview (including all
requirements of the systems);
2. the analysis component which includes the diagrams that represent the narrative;
3. an interview conducted by the tutor based on the analysis specification you submit.
The purpose of the assignment is to simulate proper systems development consulting project
where you, as the systems analyst, will need to identify and elicit user requirements. In
addition to the included case text in Section 9, you can do further requirements gathering of
business processes such as user registration, record a task entry (including text-based diary
entries), social interaction, and generate reports during weekly consultation sessions with
your tutor or through email communications.

2. Assignment Due Dates

Systems Analysis specification – 11.55pm Sunday, Week 8 (28th April, 2024)
Interviews – Based on the interview schedule given to you by your tutor. The
interviews will be scheduled to take place on week 9.

3. Assignment Value
● 25% of your overall grade for FIT9130.

4. Learning Objectives
Successful completion of this assignment will lead to knowledge of and skills in:
● techniques for functional analysis of a business problem;
● communicating an understanding of a business problem, as well as a proposed
solution to a non-technical audience;
● the purpose of, and techniques used to develop, requirements specification for an
information system;
● requirements modelling of data and processes using the following techniques:
 a. Use Case Diagrams
b. A fully developed use case description
c. Domain Class Diagrams
d. Activity Diagrams
e. System Sequence Diagrams
The assignment assesses your understanding of materials covered in Weeks 1-6.

5. Deliverables
The assignment has one deliverable which is the analysis specification report, and this is
assessed in the interview. For the interview, you do not require uploading anything, this is
question and answer session with the tutor to assess your knowledge about the specification
report you uploaded on Moodle. You will submit a complete analysis specification report
containing:
1. The narrative overview - 20 Marks (A sample format is available in the Section 10).
2. Requirements - 20 Marks
3. The following analysis models:
a. a single complete Use Case diagram for the functional areas listed in the case
which should include some <<include>> and <<extend>> scenarios when they
are needed. - 15 Marks.
i. Ensure that you include a use case called “Record a Task Entry.”
b. A fully developed use case description/narrative related to “Record a Task
Entry.” - 10 Marks.
c. a single complete Domain Class Diagram for the functional areas listed in the
case - 15 Marks.
d. an activity diagram for the use case “Record a Task Entry.” - 10 Marks.
e. a system sequence diagram for the activity diagram above in section d - 10
Marks.
The narrative overview should outline your understanding of the business problem based on
the case material provided below. It should also give some idea of the proposed solution. The
narrative overview should not just paraphrase the case study document. Furthermore, the
narrative overview needs to establish your understanding of the scope and nature of the
problem to be solved, as well as any other information necessary for the client to understand
the proposed solution.

6. Assessment Criteria
1. Completed design specification report
1. Narrative overview:
a. Completeness of discussion of project background
b. Completeness of understanding of the scope and nature of the analysis process
2. Diagrams:
a. Quality of the analysis solution and support for the business requirements
 b. Correctness of execution of diagramming technique
3. Quality and professionalism of presentation, including layout, structure and
grammar
A detailed marking criteria is available in the Assignments section on Moodle.

2. Interview
You are required to attend for an interview in week 9 to explain the models to your
tutors depending on your scheduled time.

7. Submission
One student from each group is required to submit an electronic copy of their submissions on
Moodle. The submission link is Turnitin enabled, please read the details given in Sub Section
3 below carefully before you submit the assessment online. Submissions must be in either
Microsoft Word or PDF format.
1. Penalty for Late Submission
Late submissions without an approved extension will be subject to a penalty of 10%
per day. Weekends count as a single day. No submission will be accepted more than
one week late.
2. Turnitin
Turnitin is an online tool to assist students and staff in understanding and supporting
the ethical and appropriate use of materials. Students are required to submit an
electronic version (in .doc format and WITHOUT the cover page) of each submission
through the Moodle site of this unit.
Turnitin generates the initial originality report quickly. However, if you resubmit your
assignment for analysis, there will be a 24-hour delay before a new report is
generated.
You are permitted multiple submissions to Turnitin until the due date of the relevant
assignment. You may want to make improvements based on the report and resubmit it
through the same Turnitin submission link. Each submission will overwrite the
previous submission and only the last submission / originality report will be viewed.
Further details can be found at:
http://vle.monash.edu/supporttraining/learnbytech/turnitin/index-student.
html

8. Plagiarism and Collusion

While general collaboration between students in terms of understanding of modelling
concepts is acceptable, the assignment and the solution contained in it must be entirely your
group’s work.
You must not:
● Use another student’s work as the basis for your own.
● Use another student’s work to help ‘give you ideas.’
● Steal, appropriate or make use of the work of another student without their knowledge.
● Lend your work to another student for any reason.
 ● Borrow work from another student for any reason
● Use the ideas, words or other intellectual property of anyone without proper attribution.
● Leave your work unattended on the student laboratory computers or give your
authcate details to anyone.
Penalties for plagiarism and/or collusion can include formal reprimands, notes being attached
to your student file, failure in the assignment, failure in the unit or even suspension or
exclusion from the university.
See the Unit Guide for more information on plagiarism and cheating, and for links to Faculty
and University policies on this topic.

9. The Case: MyCareConnect (MCC)

You are hired as a business analyst to work for Elderlycare Inc., a not-for-profit organization
run by a charity organization based in Melbourne, Australia. As the business analyst of
Elderlycare Inc., you will design an innovative mobile-based software solution to connect and
manage volunteers for aged care, “MyCareConnect.” The goal of MCC is to provide a
platform to connect nonmedical, in-home caregivers for physically or mentally impaired
seniors.

Elderlycare Inc. thoroughly examines volunteer applicants and accepts government certified
home health aides, nursing assistants, licensed vocational nurses and people with recent
senior caregiving experience. It also checks driving and criminal records. Before starting
work, each service-provider (volunteer applicant) is registered with the Department of Social
Services. Senior citizens, or responsible family members, search for volunteers much in the
way someone might select from a list of qualified and fully vetted Taskers for a job.

Usually, Elderlycare first conduct a face-to-face assessment with the senior citizen who
require aged care (senior citizen, or responsible family member), where the company
determines the needs, preferences and other considerations of the person in need. Senior
citizen users (care receivers) first undergo an initial assessment to determine the types of
services they will likely to use. This is used to tailor search results for each senior citizen
when looking for volunteers. Assume that senior citizens are able to create their own profiles
and family members can be added to their profiles to view their health and well-being.

The mobile app

The mobile app helps to manage the volunteers and acts as a repository for storing the details
of the volunteers, activities they carry, senior citizen details and it also acts as a platform that
shares information of the seniors with their family members. Once the senior member is
registered, the senior or family member can log in at any time to order a volunteer matching
their profile to come over and help them make lunch, bathe and dress, take their medications
on schedule or go for a walk. The volunteers who are registered on the app receives a
notification as soon as they are allocated a task on the mobile app.

User Registration
The system should maintain profiles for the senior citizens, their family member(s) as well as
the volunteers. Each user of the mobile app will need to register. This will allow them to
access the platform from various devices, apps, browsers and other online services that the
user may use. The profile can be minimal but should have options for senior citizen users to
fill out a range of health and demographic information such as age, gender, location, weight,
and height and specify some fitness goals. All users can also add a profile picture. The senior
citizens should be able to enter what they require the volunteer to do for them (tasks).
Task Entries
The core of the CareConnect app is the idea of a task list. For elderly users (senior citizen),
the most common entry added to their diary will be some kind of activity that they need help
such as cleaning, bathing, walking and dressing them. The app needs to support a wide range
of care giving activities. Each type of activity may have a number of different data items
recorded. All will include a date, start time and duration. Some, like walking, will include
distance covered and comments on their health. Other entries the care givers may enter will
be for various health or fitness measurements such as their weight, and in general a comment
on how they are on that day. If the volunteer is cooking a meal for the elders, they can also
add entries for meals that they eat – this would include the date and the type of meal
(breakfast, lunch, etc.). Finally, care givers can also add text-based diary entries and attach
photos or videos of the elder that they look after. This maybe a comment on how they’re
doing, or some other piece of information they’d like to share with their family.
These entries are required to be like posts on other social media sites such as Facebook.
Family members should be able to comment on their elders’ entries.

Social Interaction
Sharing the information with the elders’ families
As with other social media platforms, care giver users should be able to share the information
with their families. The family members will see their elders’ diary entries in their ‘feed,’
allowing them to comment on those entries.

Viewing Progress
Aside from the social aspects of the platform being appealing to end users, many of the
family members will be interested in the data analysis possibilities that the mobile app offers.
They would like the platform to support a range of reports that users can create to track the
elders’ health and wellbeing over time.
Reports may be of simple measures recorded in the users’ diary over time, such as weight or
blood pressure. It may be based on simple calculations, such as the distance covered per
week, how they are feeling etc.

10. The Narrative Overview(20 Marks) Sample Format(Refer to the

Marking Guide for detailed Marking)
Executive summary
This section should:
a. Describe the purpose of this document;
b. Specify the intended readership of this document.

Background about the client

• This section should include information about the company. Not the project.
• Who are the customers, Stakeholders (using the Stakeholders Matrix)
Business scenario
• The problems or the opportunities of the company that has led them to come up with
a new solution. The section should focus on the problems or the opportunities, not the
product to be designed

Scope
• identify the products to be produced;
• explain what the proposed system will do (and will not do, if necessary);
• define relevant benefits, objectives and goals as precisely as possible;
• define any security risks associated with the system;
• be consistent with similar statements in higher-level specifications, if they exist.

Key business requirements – 20 Marks

• If you search on Google for detailed software requirement specification and go to
business requirement section, you will see how different systems analysts have
depicted this. Further, you must have 2 separate sections for functional requirements
and non- functional requirements.
• constraints and limitations on the design
• assumptions made