The student must design structural and behavioural UML diagrams for distributed system for an application such as multi-player game, a collaboration tool or a transaction system. Structural UML diagram must include class diagram while behavioural diagram can include activity, sequence and use case diagram. The user interfaces must consider interactions between multiple users. Requirements: • The system is required to support multiple, autonomous agents (either human or automated) contending for shared resources and performing real-time updates to a form of shared state. The state of the system is distributed across multiple client or server nodes. – The only centralized service is the one that supports user login, adding or removing the clients or the servers, and other housekeeping tasks.  The system must be robust i.e. – The system should be able to continue operation even when 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 its operation. Since it is difficult to predict how hard designing a new system would be, you may formulate it as a set of “tiers”. The basic tier is fairly easy to complete but for the additional tiers, add more features at both application and system level. For example, your system enhancements could include increasing the level of fault tolerance, decreasing the time to recovery, or adding features to improve scalability, security and QoS. 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 within the boundary of the scope. 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 6th 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. Questions Description Marks Section 1 Week 6 Description of the application. Tiers of the system Overall structure of the implementation. 10 4 5 Section 2 Class diagram Activity diagram Sequence diagram Use-case diagram User Interfaces design 10 10 10 10 10 Section 3 Demonstrate if the design is robust Fault tolerant Minimal recovery time Scalable Secure (Optional) 4 4 4 4 0 Reference style Follow IEEE reference style (should have both in-text citation and reference list) 5 Total 90 Grades Excellent Very Good Good Satisfactory Unsatisfactory Section -1 Relevant application selection Befitting application. Selection Suitable application selection Appropriate application 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

Read less