Scribd
Upload
58 views3 pages

Assignment 2 - Object Design-2025

The document outlines the requirements for Assignment 2 of the SWE30003 course at Swinburne University, focusing on the object-oriented design for an Online Electronics Store. Students must provide class lists, UML diagrams, CRC cards, design patterns, and initialization processes, along with typical use scenarios. The assignment is due electronically on May 11, 2025, and must include a signed cover sheet and collaboration documentation from all group members.

Uploaded by

golddroger1234567890
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
58 views3 pages

Assignment 2 - Object Design-2025

The document outlines the requirements for Assignment 2 of the SWE30003 course at Swinburne University, focusing on the object-oriented design for an Online Electronics Store. Students must provide class lists, UML diagrams, CRC cards, design patterns, and initialization processes, along with typical use scenarios. The assignment is due electronically on May 11, 2025, and must include a signed cover sheet and collaboration documentation from all group members.

Uploaded by

golddroger1234567890
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Swinburne University of Technology

School of Science, Computing and Emerging Technologies

SWE30003
Software Architectures and Design

Assignment 2 – Object Design


Semester 1, 2025
Worth 25 marks

Due:
Electronic submission (via Canvas): 11.59pm, Sunday May 11, 2025.

Expectation:

Given the case study (same as in Assignment 1), you are expected to come up with an
(initial) object-oriented design for the Online Electronics Store. More specifically, you are
expected to provide the following information:

A list of classes that define your solution as well as graphical representation of their
inter-relationships (e.g., a basic UML class diagram), following the Responsibility
Driven Design approach. Do not include any method names and/or signatures or
attributes/fields as it would most likely be too premature to come up with this
information for this initial design stage. A brief justification of your choice(s) must
be given.
Note: if your design contains any record or struct-like abstractions, they must be
defined as data-holder classes and included in your class diagram (or similar). But,
note that they are not regarded as “normal classes” as they are more like “data
structure definitions”.

For each of the identified classes, a CRC card that gives a brief description of this
class, all its responsibilities, and for each responsibility, all required collaborators.
Please make sure that you list collaborators on a per-responsibility basis!

An illustration of any Design Patterns or Design Heuristics used in your initial


design, including a brief justification why they were used.
Note: As appropriate, you need to consider the use of any known Design Patterns
and Design Heuristics, and such usage must be appropriately documented.

An illustration of the boot-strap (or initialisation) process of the Online Electronics


Store, i.e., which classes are responsible to create instances of which other class(es)
and in which order.

An illustration of four typical, non-trivial use scenarios as verification of your design


(e.g., how the system determines whether an input given by one of the user is valid
and if so how it is applied to the specific business activities/process).

1
Wrap all the above up in a suitable document structure that contains authorship, a document
overview, any assumptions you made, as well as any used external references. Please attach
your assignment 1 submission as an appendix.

Please use the dedicated discussion forum on Canvas for any further clarifications for
benefits to all, and no individual emails in this regard will be replied to.

Note: The design you come up with for this assignment is to be used as the basis for a
detailed design and implementation in Assignment 3. As such, it is important that every
member of your team fully understands the solution design that you come up with in this
assignment!

Submission details:

Each assignment group is to submit their proposal (design) in electronic form through
Canvas, along with the appropriately signed and completed “Assignment and Project
Cover Sheet” declaration form, which must be signed by all group members. The
assignment must have the form attached as an appendix. Each group is further required to
submit a contribution and collaboration document, signed by all group members, which
1. lists the amount of time spent by each member on each significant part of the
assignment,
2. describes briefly the contributions made by each group member, and
3. provides evidence showing that the assignment is done through true group
collaboration, e.g., discussions and mutual reviews of all major parts of the
assignment, and simple group meeting minutes (time, place, attendees, issues
discussed, decisions made, etc).

Note: For the assignments in this Unit of Study, students are to work in groups of three or
four, i.e., the same groups as in Assignment 1. Permission by the Unit of Study convener is
required to change groups, well before the submission deadline, with a “good” reason.
Extensions to the submission deadline can only be granted for genuine reasons and the Unit
of Study convener must be contacted at least 48 hours prior to the submission deadline.

The electronic submission is through Canvas by the deadline as published in the front of this
assignment specification.

Unless the Unit of Study convener has approved an extension, any late submissions will be
penalised by 10% of the assessment worth for each calendar day or part thereof the
submission is late, up to a maximum of 5 days. After 5 days, a zero result will be recorded
and no feedback may be given on the respective submission.

The Unit of Study convener reserves the right to call in any assignment teams to further
explain their submission if there are doubts about the authorship of the presented solution.

2
Swinburne University of Technology

School of Science, Computing and Emerging Technologies

ASSIGNMENT AND PROJECT COVER SHEET

Subject Code: SWE30003 Unit Title: Software Architectures and Design

Assignment number and title: 2, Object Design Due date: 11:59pm,11th May 2025

Tutorial Day and time: ____________________ Project Group:

Tutor:

To be completed as this is a group assignment


We declare that this is a group assignment and that no part of this submission has been copied
from any other student's work or from any other source except where due acknowledgment is made
explicitly in the text, nor has any part been written for us by another person.

ID Number Name Signature

Marker's comments:

Total Mark:

Extension certification:

This assignment has been given an extension and is now due on

Signature of Convener:

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy