Homework answers / question archive / Assignment 4 Description A company has two systems to access customer data

Assignment 4 Description A company has two systems to access customer data

Computer Science

Share With

---

Assignment 4

1. Description

A company has two systems to access customer data. One is the new developed system and the other one is the old legacy system.

 

The old system accesses the customer data using USB connection to get the customer data from some binary files stored on external disk.

 

The new system accesses the customer data using REST API over HTTPS connection to an external server.

 

You can consider that the two systems have the following APIs.

interface CustomerData {

    void printCustomer(CustomerID id);

    void getCustomer_withUSBConnect(CustomerID id);

}

 

The new system has the following API to access customer data using customer ids

interface CustomerDataOverHttps {

    void printCustomer(CustomerID id);

    void getCustomer_withUSBConnect(CustomerID id);

}

 

You task is to implement a software system that can allow the interface of the old system to be used as the new interface and is able to convert these two interfaces.

 

1. 1. Implementation Details

Your implementation should include the following functionalities:

• Create specific implementation of the given interfaces. (You can create some Mockup objects for customer objects)
• Create concrete implementations and test executions as demonstration of your implementation.

 

Note: In this assignment, you should apply “at least one correct” of the design patterns out of Observer Pattern, Strategy Pattern, Factory Method Pattern, Abstract Factory Method Pattern, Singleton Pattern, Decorator Pattern, State Pattern, Façade Pattern, Adaptor Pattern, Proxy Pattern, Composite Pattern, Command Pattern, Mediator Pattern.

 

We do not mention which one of the design patterns is suitable for this scenario. This would be your task as a software engineer to find it out.

 

Note: The given application scenario can be implemented in different ways and with different implementation details. There is not only one single correct design and implementation for the above application scenario. Each software developer might consider different assumptions and design the software based on them. In this assignment you are free to have your own detail assumptions and implement the details in your own way based on your own ideas. You should document your assumptions very well in your README.md file of your project and consider them in your UML diagrams.

 

2. Tasks
   1. Task 1 - Implementation Description

Provide a description of how you would implement this application considering software design principles. Describe what are your main software design concepts regarding this application.

 

For example, Describe in detail:

• How flexible is your implementation, e.g., how you add or remove in future new drink types?
• How is the simplicity and understandability of your implementation?
• How you avoided duplicated code?

 

In case that you have used any design patterns, describe which design pattern you have applied and why.

 

Write your description in a README.md file, use Markdown format https://spec. commonmark.org/current/ and add the README.md file to the root folder of your project.

 

We recommend writing this description after you finished the other tasks in this assignment.

 

1. 2. Task 2 - UML Class Diagram

Create a class model for your application, containing 5-8 of the most important classes. It should encompass the functionality of the use case application described above. Show only non-obvious and key methods.

 

• 3. Task 3 - Implement your solution in Java
• Provide a zip file that includes your implementation package.

The zip file should include a README.md file that describes how to compile and run your implementation. Create a Zip file from the root of your working directory so that it includes all subdirectories of your project. Remove the binary files before creating the zip files.

• Your zip file should not be larger than 10MB, include only source files of your project but not the binaries that you generated.
• Document your code very well. The best way to write documentation inside your code is to write the code while you are implementing the project and not postpone it to later time.
• Each class should have a description before the implementation
• You should use the Google Java Style Guide (https://google.github.io/styleguide/javaguide.html)
• We should be compiling your solution on a Unix-based operating system like Linux or MacOS. Your project should include a run.sh that can be used to compile and run your project.