代做INFS2037、代写java/python编程语言、代做UML notation、代做C/C++设计

日期：2018-10-30 09:55

INFS2037 Assignment 2

Due date: Friday, 4 November 2018, 11:55 PM

Weighting: 25% of the course total marks.

Submission instructions are at the end of this document.

Instructions:

This assessment item must be conducted in groups. Students must work in the group as published on the

course website. If there are any issues with your group, please let me know early, as it may be very difficult

to resolve problems late in the study period.

Your group will be responsible for designing the implementation of selected use cases of the Mosquito

Tracking system case study. You may refer to the case study document provided for Assignment 1.

You will be creating a suitable object-oriented design including the domain- and persistence layer.

This assignment focuses on developing use case realization at the domain layer of a system. The focus of

this assignment should not be on designing a sophisticated user interface at the expense of addressing the

functional requirements set out in the use cases. Moreover, do not design a database schema for the

persistence layer. However, you do need to show how the domain objects are persisted (i.e. where they

are retrieved from and written to a database.)

You do not need to consider user authentication in your design.

You must ensure that your design is sufficiently complete and detailed so that it can be directly

implemented in code.

All submitted materials must be entirely your own work.

Penalties apply for academic misconduct.

Hand-drawn diagrams are acceptable where appropriate provided that they are legible.

You will receive marks via learnonline within 3-4 weeks.

Answers will be scored based on relevance, completeness, and correctness of your answers.

It is your responsibility to use appropriate document management and collaboration tools if required, and

maintain adequate backup at all times. Hardware and software failure are not usually acceptable reasons

for requesting extensions. Given that the presentations are scheduled in Week 13, it is not possible to ask

for extensions for the presentation aspect of this assignment.

A word of advice: do not allocate individual tasks to individual group members and design/develop in

isolation. This strategy will almost certainly result in outcomes that do not align with each other, resulting

in low marks, possibly even a Fail grade. Rather, collaborate closely with each other to address all four

tasks.

Start this assignment well before the due date. It is unlikely that you will be able to complete the work in

one or two days.

Assignment tasks

This assignment consists of four tasks.

Document all assumptions you make and justify the design decisions.

1. Design Class Diagram

Create a design class diagram for the system implementation, showing the classes, attributes, and

associations. The design shall include all classes comprising the domain layer of the software

implementation, including any controller class(es) and persistence mechanism (i.e. storing and retrieving

relevant information from files and/or databases).

Ensure that the design adheres to the design principles discussed in the course, and that it includes all

classes, attributes, operations, and associations necessary to implement the use cases.

Document all assumptions you make and justify the design decisions.

2. Interaction Diagrams

Create interaction diagrams showing the use case realization for the main success scenarios of the use

cases

UC05 Create Treatment Plan,

UC06 Schedule Treatment Action, and

UC08 Assign Worker.

Use case narratives are given in the Appendix. You may need to extend the use case narratives into

detailed form in order to develop the detailed design.

For each diagram, you can choose to create either a Communication- or a Sequence Diagram. For

consistency it is recommended to use only one of the two diagram styles for this task.

Document all assumptions you make and justify the design decisions.

3. Presentation in class

Prepare a 15 minute Powerpoint presentation describing your design and implementation. Briefly discuss

the main design decisions and design outcomes. Allow 2-3 minutes for questions.

Internal students:

Each group will present their design in the practical class in week 13.

One student per group will record the presentation on their phone and upload the presentation video and

the Powerpoint presentation file to learnonline. Internal students must present in class to receive marks

for this task, and it is recommended that all group members participate in the presentation. It is not

sufficient to record and upload a video.

The presentation schedule will be announced at a later date.

External students:

Please upload your group’s Powerpoint presentation file in PDF format and recording to learnonline.

4. Individual Contributions

Include a summary of the contributions each student has made to this assignment in the design document.

Write one short paragraph per student. This will be used for adjusting marks of individual group members

based on the extent and quality of their contributions to the overall project. Note that this does not imply

that your marks will be determined by only the parts you have contributed to. However, particularly poor

contributions may receive a grade that is different from the overall grade awarded to the group’s

deliverable.

Marking Scheme

Task Weighting

Task 1: Design Class Diagram

Uses correct UML notation, appropriate for Design class diagram

Sufficiently complete to support implementation of each use case

Matches Interaction Diagrams

Responsibilities evident and assigned according to principles

Assumptions documented

30%

Task 2: Interaction Diagrams

Uses correct UML notation

Sufficiently complete to support implementation of each use case

Matches Design Class Diagram

Assumptions documented

40%

Task 3: Presentation in class

Clear and focused presentation

Well laid out presentation aids

Covers all aspects of design and design decisions

Video recorded and uploaded

Ability to answer questions

15%

Quality of Design Document Deliverable

Well laid out design document

Professionally presented

Easily legible when printed on A4 paper

15%

Task 4: Individual contributions

All team members have adequately described their contributions.

If absent, all members may receive the same grade.

Used to

adjust

individual

marks

Submission Instructions

A separate submission area will be created for each group on learnonline.

Please submit only one submission per group. (It is okay to update your submission.)

Do not include any of the assignment specification in your submission nor a cover sheet.

Submit the following three files and adhere to the file format and naming conventions:

1. Design.pdf

A PDF file containing the following 3 sections.

Use the following section headings, in order:

a) Design Class Diagrams: the design class diagram(s) (Task 1)

b) Interaction Diagrams: the interaction diagrams (Task 2)

c) Contributions: a summary of the contributions of each group member (Task 4)

You should create multiple diagrams under each sub-heading if the design does not present well on

a single page.

2. Presentation.pdf

A PDF file containing the presentation slides used in Task 3.

3. Video.mov or Video.mp4

A video recording of the presentation in .mov or .mp4 format. The video must include audio and

show the speaker (and, if possible, the presentation slides).

Appendix A – Use Case Narratives

UC05 Create Treatment Plan

Level: User goal

Primary Actor: Area Coordinator (AC)

Stakeholders and Interests:

Area Coordinator – wants to control Mosquito population in an area; wants to implement correct

treatment plans

Worker – wants to treat sites with minimal effort; wants to receive jobs within area of expertise

Preconditions:

Area Coordinators have been associated with their responsible areas

Workers and their skills have been recorded in the system

Equipment availability has been recorded in the system

Success Guarantee:

Treatment plan has been created and associated with the area

Treatment actions have been scheduled and associated with treatment plan and corresponding sites

Treatment actions have been assigned to workers

Equipment availability has been updated

Workers’ availability has been updated

Workers have been notified of new assignments

Main Success Scenario:

1.AC selects an area and System verifies that AC is responsible for the area.

2.System presents the reported Mosquito sites.

3.AC performs <UC06 Schedule Treatment Action> on a site.

4.AC performs <UC08 Assign Worker> on the treatment action.

Repeat steps 2-4 until sufficient sites have been covered

5.AC finalises the treatment plan.

Alternative Flows:

1a) AC not responsible for selected area

1a.1) System informs AC and repeats step 1

2a) No sites recorded

2a.1) Use Case terminates unsuccessfully

3a) No treatment action available

3a.1) Use case reverts to step 1

4a) No workers available

4a.1) System notifies User and deletes treatment action.

UC05 Schedule Treatment Action

Level: User goal

Primary Actor: Area Coordinator (AC)

Stakeholders and Interests:

Area Coordinator – wants to schedule treatment actions for sites

Preconditions:

Treatment plan has been created

Equipment availability has been recorded in the system

Success Guarantee:

Treatment action has been created and associated with the treatment plan, and required skills and

equipment

Equipment availability has been updated

Main Success Scenario:

1.AC selects a site and date

2.System presents possible treatment actions for the site

3.AC selects treatment action

4.System creates treatment action and updates equipment availability information

Alternative Flows:

2a) No treatment action available

2a.1) Use case aborts unsuccessfully

Notes:

In step 2, treatment actions shall be restricted to actions that are compatible with all the site types

associated with the site. The system shall maintain a set of site types and their compatible

treatment actions.

In step 2, treatment actions shall be restricted to actions where all the required equipment is

available in the area on the given date. The system shall maintain the available quantity of each

equipment type in each area on each day.

UC06 Assign Worker

Level: User goal

Primary Actor: Area Coordinator (AC)

Stakeholders and Interests:

Area Coordinator – wants to assign qualified workers to scheduled treatment actions; wants to

minimise cost of treatment

Worker – wants to receive suitable tasks and complete them with minimal effort

Preconditions:

Treatment action has been created

Workers and skills have been registered in the system

Success Guarantee:

Worker has been associated with the treatment action

Worker has been notified of new assignment

Main Success Scenario:

1.AC selects a treatment action

2.System presents qualified available workers for the action

3.AC selects a worker and system associates worker with treatment action, updates worker’s

availability

4.System notifies the worker that a new assignment is pending

Alternative Flows:

1a) No treatment action available

1a.1) Use case aborts unsuccessfully

2a) No qualified workers available

2a.1) Use case aborts unsuccessfully

Technology Variations:

4a) Notification via portal/phone app, text message, and/or email.

Workers can set their notification preferences in their account settings.

Notes:

In step 2, “qualified” means that the worker possesses all the skills required for the selected

treatment action

In step 2, “available” means that the worker

a) operates in the area containing the treated site, and

b) is available on the day the treatment action is scheduled.

AC’s generally prefer to assign Volunteers rather than Professional workers, as the former are

cheaper than the latter.