Structural and Behavioural Modelling – Global Homework Experts

Assessment 2
Structural and Behavioural Modelling
CSE2SDX Information System Development
2 © Didasko 2021. All rights reserved.
Before you begin
Objectives
This is an individual assignment. Students are not permitted to work in a group when writing this
assignment.
Copying and Plagiarism
This is an individual assignment. Students are not permitted to work in a group when writing this
assignment. Plagiarism is the submission of another person’s work in a manner that gives the
impression that the work is their own. La Trobe University treats plagiarism seriously. When detected,
penalties are strictly imposed.
Further information can be found on http://www.latrobe.edu.au/students/academicintegrity/explanation/plagiarism
Submission Guidelines
Your assignment submission should be typed, not written/drawn by hand.
Submit the electronic copy of your assignment through the subject LMS.
Submission after the deadline will incur a penalty of 5% of the available assignment mark per day
capped at 5 days. No assignment will be accepted after 5 days. If you have encountered difficulties
that lead to late submission or no submission, you should apply for special consideration.

© Didasko 2021. All rights reserved. 3
Background
Properprop is an Australian real estate company involved in a variety of real estate investments
and activities. The company has a large number of customers who require a range of different real
estate related services.
One of the main subsystems of the organisation’s information system is the “Sales Management”
subsystem. This subsystem is used by Properprop sales managers and agents to identify trends,
opportunities for selling properties and to automate the data collection process for sales agents.
Based on an initial requirement gathering process, the following requirements have been identified
for the “Sales Management” subsystem:
Sales Data:
Properprop stakeholders want to record and save all the sale data, including the sale type
(private, auction), type of the property, sale date and time, amount of sale, buyer and
seller names and sale documents.
Contact management:
Properprop stakeholders want to record and save all buyer and seller contact details, call
history, activity tracking, and contact history.
Opportunity management:
Properprop stakeholders want to record and save potential buyer goals and objectives in
purchasing a property, including the type of the properties that the buyer is looking for,
their budget, their preference of location, and their contact details.
Productivity and time management:
Properprop managers and agents want to manage their daily work schedule by organizing
meetings with potential buyers and sellers through calendar invites, task scheduling, and
document management.
Analytics:
Properprop stakeholders want to be able to visualize sales data in dashboards, graphs,
and charts by filtering sales data such as overall sales and sales per agent for different
periods.

4 © Didasko 2021. All rights reserved.
Tasks
Task 1 – Use Case Analysis [5 marks]
You need to develop five Use Cases, one Use Case per requirement of the Sales Management
subsystem as listed in the scenario. When documenting each Use Case use “Use Case Template”
as outlined below. All up you should have 5 use cases.
1. Use Case Template

order now
1.1. Name:
<short descriptive verb-phrase naming the use case>
Goal:
<a few sentences describing the goal of the use case from the perspective of the
user>
Pre-condition:
<the state the system must be in before the use case can begin.
Post-condition:
<the state the system must be in after the use case has completed.
Constraints/Issues/Risks:
<any items that may place a burden on the use case completion.
Trigger Event(s):
<the external event or internal timer-events that stimulate the use case.>
Primary Actor:
1.2.
1.3.
1.4.
1.5.
1.6.
1.7.

<the key actor involved in the use case. Typically, this individual is the source of the
event that stimulates the use case into action>

1.8. Secondary Actor(s):
<other actors that play a part in the use case>

Task 2 – Use Case Diagram [5 marks]
Create a Use Case diagram for the ‘Sales Management Subsystem’. Make sure you identify
dependency (include & extend) relationships where applicable. [5 marks]
Task 3 – Class Diagram [5 marks]
Create a complete Class Diagram for the ‘Sales Management Subsystem’ with associations and
multiplicity information. In your class diagram you need to define any relationship that can be
described by aggregation/composition and/or generalisation/specialisation.
Submission
When you have completed the tasks, submit your answer via the Upload link on the LMS.
You should submit Tasks 1, 2, and 3 in a single Word document called
xxx_cse2sdx_assessment2.docx (where xxx is your student number) with clearly labelled
headings for each task.

© Didasko 2021. All rights reserved. 5
Assessment Marking Criteria

Task No. Total
Marks
Criteria (Expectation for HD) Mark
1 5 No answer or answers are incorrect and/or irrelevant. 0
Has provided all the required information in the use case template.
Use cases are clear and easy to understand. Has demonstrates
extensive skills for writing the use case. (1 mark per each correct
use case)
1-5
2 5 No answer or answers are incorrect and/or irrelevant. 0
Use case diagram covers some of the desired features mentioned
in the requirements document but don’t provide a clear
understanding of the information system functionality. The use case
does not represent the main functions of the system and it has
some syntactic errors. Most of the elements that are needed are not
present.
1
Use case diagram covers some of the desired features mentioned
in the requirements document but do not provide a clear
understanding of the information system functionality. The use case
represents the main functions of the system, but it is not clear and
easy to understand. Use cases have some syntactic errors. Some
of the elements that are needed are present.
2
Use case diagram covers some of the desired features mentioned
in the requirements document but they provide a clear
understanding of the information system functionality. The use case
accurately represents the main functions of the system including the
appropriate actors. Use case is clear and easy to understand
however there are some minor syntactic errors. Some of the
elements that are needed are present, and the level of detail is
acceptable.
3
Use case diagram covers most of the desired features mentioned in
the requirements document and provide a clear understanding of
the information system functionality. The use case accurately
represents the main functions of the system including the
appropriate actors. Use case is clear and easy to understand with
some minor syntactic errors. Most of the elements that are needed
are present, and the level of detail is acceptable.
4
Use case diagram covers all the desired features mentioned in the
requirements document and provide a clear understanding of the
information system functionality. The use case accurately
represents the main functions of the system including the
appropriate actors. Use case is clear and easy to understand
without syntactic errors. Class diagram uses UML correctly to depict
the classes in the right format. All the elements that are needed are
present, and the level of detail is acceptable. Has demonstrated
extensive skills for drawing the use case diagram.
5

6 © Didasko 2019. All rights reserved.

3 5 No answer or answers are incorrect and/or irrelevant. 0
The class diagram has been prepared but it has some errors. The
class diagram demonstrates some of the associations and
multiplicity information but there are some errors. Some of the
elements that are needed are present, and the level of detail is
acceptable.
2
The class diagram has been prepared but it has some errors. The
class diagram demonstrates some of associations and multiplicity
information correctly and clearly. Some of the elements that are
needed are present, and the level of detail is acceptable.
3.5
The Class diagram has been prepared demonstrates all the
associations and multiplicity information as expected. The class
diagram is clear and easy to understand and without syntactic
errors. All the elements that are needed are present, and the level
of detail is acceptable.
5