| |
|
|
|
The chosen architecture facilitates and allows further development and extension of the product without requiring major architectural changes, which was one of the goals of the architecture.
As an example of how the system could further be developed, a number of possible extensions are listed together with a suggestion of which modules would have to be altered or added. To really show how extensible the architecture is, some examples are purely results of wild imagination and are not even marked as extra in the requirements specification [Larsson, 2003].
With little effort a GUI for editing scales could be written. The ConfigurationManager and the TestRunner would have to be expanded. Also an additional GUI component would have to be created.
This would require a new GUI component as well as a new module in the action level. This module would use functionality from ResultManager.
TestRunner would have to be expanded and some additional GUI component, in both the administrator and client parts would have to be written.
It might be useful to let the test results and projects be managed by a general DBMS such as MySQL instead of the built in one.
The ResultProxy would have to be rewritten for saving results into a DBMS. The StorageProxy would have to be rewritten for saving projects and tests into a DBMS.
The administrator and clients could be extended so that an administrator could instruct a number of clients to start a specific project remotely.
The architecture facilitates maintenance by being clear and having well named modules. This helps to quickly get a good picture of the system. Also section 2.2, "Philosophy", on page 8 will further speed up the process of getting familliar with the architecture.
For locating errors, reading of chapters 3, "Use cases" and 4, "Modules and layers" is highly recommended.
 Quadralay Corporation http://www.webworks.com Voice: (512) 719-3399 Fax: (512) 719-3606 sales@webworks.com |
| |
|
|