Analysis of Combined Design Patterns
$30-45 USD
着払い
This project is fairly **easy**; all it requires is a diagram and some interpreting of code and explaining what it does.
This project provides a working implementation of the design patterns I have investigated so far. Instead of implementation I need to show the significance in analyzing existing code.
The code provided with this lab implements a relatively straightforward computer network with the following functionality:
• It allows any kind of device to be connected or disconnected dynamically.
• It allows any device to communicate with any other device over the network by sending messages in one of three ways:
• *unicast*: from one device directly to another.
• *general multicast*: from one device to all others.
• *filtered multicast*: from one device to all others of a certain type.
## Deliverables
**I have attached a zipped file that includes all of the source files that you would possibly need!
Part 1: Analysis of Architecture**
Draw an architectural diagram that depicts the structure of the implementation in terms of (1) what its interfaces and classes are, and (2) how they interconnect. The format is of your own choice. Do not indicate implementation details like variables and methods.
**Part 2: Analysis of Execution**
The **Lab6Tester** class demonstrates the functionality of this system in this order:
1. It **creates** a **network**.
2. It **connects** two **basic lamps** to the **network**.
3. It **toggles** one **basic lamp** **on** and **off** by **unicasting** directly to it.
4. It **toggles** all **basic lamps** on and off by **multicasting** to every basic lamp only.
5. It **toggles** everything on and off by **multicasting** to everyone.
6. It **disconnects** the two **basic lamps** from the **network**.
The task is to explain in sufficient detail the sequence of events with enough detail to indicate the high-level processes that are occurring that the code executes when each of these demonstrations occurs.
In other words, trace the execution (1) from the tester, (2) through everything that it executes, and (3) back to the tester.
Do not list code verbatim or regurgitate psuedocode from the actual implementation.
The format is of your own choice. However, be sure that, given such a description, any reasonably capable programmer could actually implement it. (At the college sophmore level)
**Part 3: Analysis of Implementation**
For each block of code immediately following the tag <COMMENT>, describe with a customary level of commenting detail what the block does, why, and how.
## Platform
**Submission:**
Part 1: please submit your architectural diagram on paper and please scan it and post it.
Part 2: please submit a document with your narration.
Part 3: please submit **ONLY** the source files that require Commenting.
プロジェクトID: #3367707
