Great Deal! Get Instant $10 FREE in Account on First Order + 10% Cashback on Every Order Order Now

Assessment Details and Submission Guidelines Unit Code MN611 – T1 2018 Unit Title System Architecture Assessment Type Individual Assignment Assessment Title Assignment1: UML diagrams to illustrate the...

1 answer below »

Assessment Details and Submission Guidelines

Unit Code

MN611 – T1 2018

Unit Title

System Architecture

Assessment Type

Individual Assignment

Assessment Title

Assignment1: UML diagrams to illustrate the system architecture

Purpose of the assessment (with ULO Mapping)

This assignment assesses the following Unit Learning Outcomes; students should be able to demonstrate their achievements in them.

c. Analyse and model system functionality and behaviour.

d. Compare and contrast different approaches to system analysis and design, such as object-oriented, agile, and service oriented techniques

e. Analyse and model the functional and non-functional requirements of a software system

f. Design and deploy functional solutions, such as initiating, analysing and implementing system plans


15% of the total assessments

Total Marks

Word limit

Not applicable

Due Date

Week 7, Friday, 11.55 PM

Submission Guidelines

· All work must be submitted on Moodle by the due date along with a completed Assignment Cover Page.

· The assignment must be in MS Word format, 1.5 spacing, 11-pt Calibri (Body) font and 2 cm margins on all four sides of your page with appropriate section headings.

· Reference sources must be cited in the text of the report and listed appropriately at the end in a reference list using IEEE referencing style.


If an extension of time to submit work is required, a Special Consideration Application must be submitted directly through AMS. You must submit this application within three working days of the assessment due date. Further information is available at:

Academic Misconduct

Academic Misconduct is a serious offence. Depending on the seriousness of the case, penalties can vary from a written warning or zero marks to exclusion from the course or rescinding the degree. Students should make themselves familiar with the full policy and procedure available at: For further information, please refer to the Academic Integrity Section in your Unit Description.

Assignment 1 Specifications


The student must design structural and behavioural UML diagrams for distributed system for an application such as multi-player game or a collaboration tool or a transaction system.

Structural UML diagram must be a class diagram while behavioural diagram can be an activity, sequence and use case diagram. The user interfaces will have to consider interactions between multiple users.


• The system must support multiple, autonomous agents (either human or automated) contending for shared resources and performing real-time updates to some form of shared state.

• The state of the system should be distributed across multiple client or server nodes. – The only centralized service should be one that supports users logging on, adding or removing clients or servers, and other housekeeping tasks.

• The system should be robust

– The system should be able to continue operation even if one of the participant nodes crashes.

– It should be possible to recover the state of a node following a crash, so that it can resume operation.

Since it is difficult to predict just how hard designing a new system will be, you should formulate as a set of “tiers,” where the basic tier is something you’re sure you can complete, and the additional tiers add more features, at both the application and the system level. For example, your system enhancements could include increasing the level of fault tolerance, decreasing the time to recovery, or adding features to increase scalability, security and QoS.

Important, but secondary considerations include:

• How interesting is the application: is it a fun game, a useful tool, or a solution to a real-world problem?

• How nice is the application’s appearance: does it have a nice interface or a compelling visual display?

· The architecture should be well designed, in terms of the overall architecture and the detailed realization.

Some of the application Ideas are as follows but are not limited to.

The following list of projects is intended to spark your imagination. Feel free to come up with something totally different. Contact the lecturer if you are uncertain of the suitability of your ideas.

1. Shared document editing, in the style of Google docs. The system should support real-time editing and viewing by multiple participants. Multiple replicas would be maintained for fault tolerance. Caching and/or copy migration would be useful to minimize application response time.

2. A simulated life game, in the style of The Sims or Farmville. The state of the system would be partitioned spatially, with replication for fault tolerance.

3. A multi-player real-time game, based on shooting, hunting for treasure, etc. There are many possibilities here.

4. An airline reservation system. Each airline would maintain its own collection of servers, with enough state replication to enable automatic fail-over. It would be possible to book travel that involves multiple airlines.

During the 6 th week lab, students should submit and explain the proposal.

This should include:

• A description of the application.

• The overall structure of the implementation.

• How you intend to implement your system as a series of tiers.

• A schedule for how you plan to carry your design and implementation.

Marking criteria:

For example, your system enhancements could include increasing the level of fault tolerance, decreasing the time to recovery, or adding features to increase scalability, security and QoS.




Section 1

Week 6

Description of the application.

Tiers of the system

Overall structure of the implementation.




Section 2

Class diagram

Activity diagram

Sequence diagram

Use-case diagram

User Interfaces design






Section 3

Demonstrate if the design is robust

Fault tolerant

Minimal recovery time








Reference style

Follow IEEE reference style (should have both in-text citation and reference list)






Very Good




Section -1


application selection




Suitable application selection



Not relevant application.

Section 2

Precise UML diagram representation

Accurate UML diagram representation

Exact UML diagram representation

Correct UML diagram representation

UML diagrams do not satisfy the requirements.

Section 3

Design that satisfies all requirements of distributed architecture

Design that satisfies partial

Requirements of distributed design

Design that satisfies some

Requirements of distributed design

Design that satisfies few

Requirements of distributed design

Design that does not considers features of distributed design

IEEE Reference style

Clear styles with excellent source of references.

Clear referencing style

Generally good referencing style

Sometimes clear referencing style

Lacks consistency with many errors

Answered Same Day Apr 21, 2020 MN611


Ahmedali answered on May 01 2020
137 Votes
Airline Booking System
Airline Booking System
Airline Booking System        System Analysis & Design Document        4/30/2018            
Table of Contents
Introduction    2
Purpose    2
Approaches to System Development    2
System Requirements, Functionality, & Behavior    3
Functional Requirements    3
Non-Functional Requirements    4
System Availability    4
System Scalability    4
System Usability    4
System Performance    4
System Security    4
System Reliability    5
System Maintenance    5
User Requirements    5
System Design & Architecture    6
Class diagram    6
Use case diagram    6
Activity diagram    8
User interface diagram    9
System Testing & Risk Management    11
References    13
The document is a System Analysis & Design document for an Airline Booking System. The system will allow the users to search and book the flights through an online application that will be provided to them. Online bookings are being used by the users from all across the world and therefore, it is necessary to offer these functionalities to the users. The analysis phase of the project covers the selection of the system development approach. As a part of this phase, the business case will be analyzed and the system functionalities and requirements will be highlighted in the areas of functional, non-functional, and user aspects. The system behavior will also be assessed. The design phase of the project covers the designing of the system through system architecture, class diagram, activity diagram, use case diagram, and user interface screens.
The purpose of the document is to cover and discuss the analysis and design details of the airline booking system.
Approaches to System Development
There are numerous system development approaches that have been defined. These approaches differ in terms of the development methodology and process that is suggested and the handling of the various requirements and resources. The development approach is selected on the basis of system factors and desired properties and attributes.
The methodology that has been suggested for airline booking system is agile methodology for system development. It is a methodology that comes in the category of adaptive methodologies and provides a value-based approach for all the development activities. Under this methodology, all the requirements that are associated with the airline booking system will be defined in the form of user stories and will be put in a product backlog [1]. There will be iterations that will be executed and a sub-set of the overall set of requirements will be obtained and targeted in each cycle. The iterations will be termed as sprints and the requirement set for each sprint will be stored in sprint backlog. There will be small teams for the project activities and the teams will acquire the requirements from sprint backlog and proceed with the design and development tasks [2]. There will be a daily meeting that will be organized by the Project Manager and the progress and issues will be discussed during the same. The end of a sprint will have a feedback process in which the user acceptance testing will be ca
ied out. The comments and feedback from the users will be incorporated in the next sprint until the final airline booking system will be developed [3].
This approach has been recommended as it meets the cu
ent requirements of a flexible and scalable system. It will allow the development team to update the system easily and make changes as per the user expectations at any stage of the project. The system will be adaptable to changes and user environments which will enhance the user engagement and satisfaction levels [4].
System Requirements, Functionality, & Behavio
Functional Requirements
· The system shall allow the four user types viz. super admin, system user, employee, and passenger to login and logout from the system.
· The system shall allow every user to manage its account and change password when desired.
· The super admin shall be allowed to manage the users by modifying the user account details, confirm bookings, add or delete users.
· The super admin shall be allowed to view and modify the airlines details and information on the...

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here