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 Properpro
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.
© Didasko 2021. All rights reserved. 3
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
1.1.Name:
1.2.Goal:
1.3.Pre-condition:
1.4.Post-condition:
1.5.Constraints/Issues/Risks:
1.6.Trigger Event(s):
1.7.Primary Actor:
1.8.Secondary Actor(s):
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.
4 © Didasko 2021. All rights reserved.
Assessment Marking Criteria
Task No.
Total
Criteria (Expectation for HD)
Mark
Marks
No answer or answers are incorrect and/or irrelevant.
0
1
5
Has provided all the required information in the use case template.
Use cases are clear and easy to understand. Has demonstrates
1-5
extensive skills for writing the use case. (1 mark per each correct
use case)
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
1
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.
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
2
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.
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
3
2
5
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.
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
4
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.
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
5
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.
© Didasko 2021. All rights reserved. 5