inleverenregisterforumassignment,
projects,
documentation,
resources,
groups,
java3d
Programming and software development becoming more
and more facilitated by interactive and graphical tools.
Apart from speeding up software development, these tools may also
be useful to bridge (to some extent)
the gap between realization and design, by providing appropriate
(graphic) abstractions, such as a class hierarchy diagram.
Rationale
A collection of software development tools may conveniently be called
a Studio. Often the tools in a Studio do nothing more than
providing a graphical user interface to existing utility programs such
as make, or the Orbix command line operations.
Other tools, such as a Class Diagram Tool, contain more
imminent functionality, in this case for displaying classes
and their relations in a graphical way.
The use of distributed object technology and in particular
the specification via CORBA
IDL is encouraged.
See Corba at the VU.
Components
Interface Builder
Class Diagram Tool
Smart Code Editor
Project Manager
Software Documentation Tool
Client/Server Management Tool (for Orbix)
Design
The designer/developer must specify the rationale for
each individual tool, as well as its design
and possibly the patterns or software idioms used to implement it.
The use of the tool must be fully documented, preferably
with an online demo. Otherwise a tutorial on how to use
the tool must be included in the documentation.
See the Guidelines for Documentation.
Comments
Make a selection of what you consider to be useful tools
for hush.
If you think of a tool not in the list, that is OK,
provided you motivate the tool by giving a rationale as well
as some examples.
If you take a more generic approach, be sure to test
the tools for hush programs.
Don't be too generic. Tools is generally a slippery affair.
[.]
-
[up]
[top] -
[I]
[II]
[III]
[IV] -
[1]
[2]
[3]
[4]
[5]
[6]
[7]
[8]
[9]
[10]
[11]
[12] -
[A]
[R]
