UCCD 2213 Software Engineering Principles

Assignment
Part II
1.0 Topic
 Architectural design

2.0 Instruction
i. Evidence of plagiarism or collusion will be taken seriously and University regulations
will be applied fully to such case. You are advised to be familiar with the University’s
definitions of plagiarism and collusion. Any plagiarism or collusion may result in
disciplinary action, in addition to ZERO mark being awarded to all parties involved.
ii. This part has 50 marks and the total of the whole assignment is 100 marks and
contributes 15% of the total grade.
iii. This contains Group Task and Individual Task. Regarding group tasks, all members share
the same marks, but it is open for team leader to claim contribution proportion of every
member.
iv. You MUST submit HARDCOPY and SOFTCOPY of reports. Softcopy is sent by email.
v. The deadline for the submission of PART II is on 18/08/2017, before 12:00PM (Week
11).
Late submission will deduct 10% of assignment grade per day.
vi. Please use Appendix to be the COVER of your report.

3.0 Task to do
Assume that your team is going to develop a Business Information System, such as transaction
processing systems, decision support systems, knowledge management systems, learning
management systems, database management systems, and office information systems, under
Network environment. In this second part of assignment, your team is going to practice to
apply patterns for designing the target business information system.
Target : Architectural design for business information system
Complete the following task:
2.1 Overview of the proposed system (5 marks) (Group task)
2.2 The survey of existing systems (5 marks) (Individual task)
2.3 Functionality of the proposed system (10 marks) (Group task)
2.4 Overview of software/system architecture (10 marks) (Group task)
2.5 Architectural patterns with subsystems (20 marks) (Individual task)

2.1 Overview of the proposed system (Group task)

Propose your target information system. The idea can be from existing systems such as Factory
Inventory System, POS system for a fast food restaurant, or Food Ordering System for a
restaurant. However, please assume that your system must run under Network (Inter- or
Intra-net). Moreover, the size of your system is medium so that you can practice to apply
architectural patterns to design subsystems. In this section, 1.1, provide a context diagram
you have learned from ADIS (Context diagram) or OOSAD (Class diagram) course. Then you
need to briefly describe this context diagram. The length of this section is at least ONE page.

Marking: All members share the same marks of this section.

2.2 The survey of the existing systems (Literature review) (Individual task)

In this section, each member MUST survey at least one existing application. You can find it via
Internet. The survey must cover the brief description of every existing application (You are not
allowed to copy and paste any text via Internet. You should understand the existing
application/system and write the introduction of it according to your understanding). You
MUST try to make the comparison with the existing application and the proposed application,
including the strength and the weakness.

Marking: Individual of members can have his/her own marks of this section.
2.3 Functionality of the proposed system (Group task)

Prepare a table to list ALL functions of your proposed system. The format or structure of a
function’s description is not limited. You can write functions as “traditional functional
requirements”, or “user stories”. All members discuss and come out the proposed user/system
requirements.
Marking: All members share the same marks of this section.

2.4 Overview of software/system architecture (Group task)

In this section, you must prepare a block diagram to represent the overview of software or
system architecture for your proposed system. If you are familiar with UML modeling, UML
diagrams are allowable to represent the architectural design of the proposed system. You can
refer to lecture note of Unit 5 to find the example of an architecture, or you can find out more via
Internet.
Marking: All members share the same marks of this section.

2.5 Architectural patterns with subsystems (Individual task)

For this section, practice to divide you proposed system into several subsystems. The
subsystems in this section must be consistent with your proposed software/system
architecture. For each subsystem, individual member needs to prepare the followings:
 The brief description.
 Suggest the most suitable architectural pattern learned from the lesson to design the
corresponding subsystem. You also need to provide reasons of your selection.
 Refer to the selected architectural pattern to provide software architecture for the
corresponding subsystem.
 Describe components in software architecture of the corresponding subsystem.

Marking: Individual member is given marks based on the contribution.

Appendix

UCCD 2213 Software Engineering Principles

Assignment
Part II

Architectural Design Exercise

(Place name of the proposed APP here)

Student ID Name Tutorial No. Signature Marks

MAY 2018