stonedhesus / fractals Goto Github PK

Before diving further into complex functionality we would want the project to have a predefined architecture. This architecture is designed in accordance to the provided specification, and the engineering decisions of the team, so that it will be suitable later on, and in theory will require few to no modifications.

We would to create an abstract view class which will enable us to easily collate to it the functionality that we want the view to have, i.e. it can either be a menu view, or a view which is linked to some sort of model, against which we check to see what each event which we listen for and intercept modified, etcetera.

Implement a package containing all the required classes and interfaces so as to properly construct, manipulate and utilise complex numbers.

In addition to this implement a series of unit tests which will ensure that the behaviour of the components works in accordance to the specifications, and that the invariants are preserved as long as they were intended to.

The application core design revolves around the state-machine paradigm, in which different views within the application are perceived as states in a DFA automaton, whose transitions map the manner in which we can navigate from one state to the next, if possible.

This issue targets the creation of such a mechanism within the codebase of the current project.

We would want to be able to write mathematical expression naturally, and display them thus, so as to keep track of the functions we are utilising when rendering the fractals.

In order to achieve this, we ought to implement a mathematical expressions input menu, which will contain a series of buttons that will allow the client to select the required mathematical expression and thus ensure proper formatting, and hitherto a correct and natural display of the function.

We would want this menu to be independent of the other application, so that it can easily be collated to any view, or associated with any button we want.

In order to facilitate the documentation of the code, and especially so as to not cram this task towards the end of the development cycle, we would want to commence gradually to fill the README.md file so that it contains relevant information, and that it informs the user in regards to how to manipulate the software. In addition to that, it will be nice to generate a documentation page, which combines the README.md plus the JavaDoc automatically generated documentation for the software!