Your cart is currently empty!
Submission Information: Please submit on D2L (details near the end of this document). WH A T T H I S A S S I G N M E N T IS A B O U T An image says more than a thousand words: In this assignment, you’ll be visualizing architectures based…
Submission Information: Please submit on D2L (details near the end of this document).
WH A T T H I S A S S I G N M E N T IS A B O U T
An image says more than a thousand words: In this assignment, you’ll be visualizing architectures based on the output of an architecture recovery method of your choice.
From the previous assignments, you should have a good idea and understanding of what the output of architecture recovery looks like and what information it contains.
You have also seen the visualizations coming from two recovery methods and know their strengths and weaknesses.
It is now time for you adapt an existing visualization tool or create your own.
BE F O R E YO U G E T S T A R T ED
In order to produce data for your visualizations, you will need the virtual machine from the previous assignments. You can download the latest version with several updates and fixes here. While the version from Assignment 2 will also produce useful data, the latest one contains some improvements and is recommended.
Note that at this time, we’re not able to offer you a script to upgrade your VM to the latest version. Such a script may or may not become available at a later time.
SE L E C T YO U R VI S U A L I ZA T I O N
Select a visualization. This could be anything you can find, as long as it is:
Examples include:
A list with many examples of free visualization tools can be found here:
https://www.springboard.com/blog/31-free-data-visualization-tools/
CR E A T E O R S E L E CT YO U R DAT A
Select the kind of data you would like to visualize. This has to be data that is
Optionally, you can use the source code of the system and the output of UCC in addition to the data mentioned above.
GUI DE L I N E S
Your visualization should
SE L E C T A P R O G R A M L A N GUAGE AN D W R I T E Y O UR TO O L
You will have to write a tool which will accept one or more files from the output of an architecture recovery run. It will then need to either
Note that your tool may have to consist of two or more components (e.g. a compiled component and a script that runs the first component and submits the converted data to the external visualization).
The final product after running your tool needs to be either
Please note that not all programming languages are acceptable for your tool. Your code and visualization must not be platform-specific and must be able to run within your Ubuntu VM.
These languages will be acceptable:
If you wish to implement your system in a language that is not included above, please contact the instructor and TA.
DE L I V E R AB L E S
Please submit the following files on D2L:
o Describe the input and output of your tool,
o Include at least two examples of the visualizations the tool produces, o Describe how the visualizations relate to the architecture of a system, o Describe how they scale to different system sizes, and
o How they can give a good overview of a system.
o The source code of your tool,
o A compiled version of your tool that is runnable on the CS 578 Ubuntu VM,
o Any external tools and libraries in compiled form, and
o A short file named README_<First Name>_<Last Name>.txt with instructions on how to compile your tool (or stating that no compilation is necessary)
On extraction, the zip file needs to produce a self-contained directory that contains everything required to compile and run your tool. Note that any compilation systems or scripts that rely on downloads (such as Maven) are NOT acceptable.
GR ADI N G
Your visualization will be graded on how well it
Your write-up will be graded on clarity and helpfulness.
Your tool will be graded on code quality (maintainability, readability) and performance.
LA T E S U B M I S S I O N S :