Download ware-cj-dissertation.. - Department of Computer Science

Transcript
It can also be seen that the names of actual parameters are shown on the connecting edges
themselves rather than on the source port. Although this does no harm, it is not strictly
correct because it implies that two edges from the same port could have different variable
names, and results in redundancy of information because this is not possible. This can be
seen on Figure 19 with the variable anoise into outs.
It can be concluded from this additional analysis of a separate implementation that
expressions are the source of weakness in the graph representation. They allow a many-tomany mapping between outputs and inputs where the rules to combine the edges terminating
on an input are not defined in graph theory. The theory dictates that the only way to address
this is to expand expressions fully to trees and make them part of the graph, which would
result in clutter. This could perhaps be addressed with hiding or collapsing inner parts of the
expression but is certainly complicated. Therefore, our method of parsing expressions and
connecting the nearest available value is justified for practical purposes.
One final comment is that we have approached the overall problem from the perspective that
the code which is output should be easily understandable and editable by a user. If we
remove this requirement and permit the output of semantically correct but difficult to read
code, the possibility of assigning unique variables for every output becomes apparent. This
would remove the need to match expressions to the ―nearest instance‖ of a given variable,
which in turn would allow a code generation algorithm based on backward chaining/formal
tree traversal.
6.3.5 Non-Functional Considerations
There were no specific tests designed to validate the non-functional requirements given in
section 3.3. Instead we will summarise the system with respect to these here:
25. The system must be delivered, documented, and tested for compliance with the
requirements by the project hand in date of 27 April 2009.
This is an administrative requirement and at the time of writing work is on
schedule to meet this deadline.
26. Code generation must complete quickly to allow rapid adjustment of the diagram
and regeneration of the code by the user. A reasonable average time would one
second for each instrument. For individual opcodes there should be no discernible
delay in generation and display of code.
During execution of the functional test plan, no noticeable delays were
experienced in the generation of code. The only delay seen was when
inserting the first opcode vertex after the application starts – this causes a
freeze of approximately 1 second while presumably the OpcodeVertex
78