APT will need a generic architecture to support a set of tools which
must work together. This design will need to support inter-operability
between sets of tools. If a tool is not present or avail- able the
architecture should gracefully support this. Tools may be available
locally or on remote servers. It is expected that the infrastructure
will need to support connecting to legacy systems, web pages, local
applications, etc. Communication may be asychronous or synchronous. It
is expected that this infrastructure should be designed such that it
will be capable of supporting any HST PI tool. This includes, but is
not limited to, Phase 1, Phase 2, and Archival Research,. Cur- rently
there are three projects, RPS2, SEA, and Starview 2, which have
infrastructures which may be used/extended to support APT A new
architecture may be developed as a blend from the different
projects. It is hoped that the APT architecture doesn't need to be
designed from scratch, but can use existing architectures. In
designing a system with an MVC architecture (data model, view,
controller), this team will design the control and event handling
mechanisms including the objects needed to support this design. This
team will be responsible for providing the following deliver- ables in
the following order:
· A timeline schedule for this task
· A requirements document
· Hold a requirements review
· A design document using a UML tool.
· Hold a design review
· An updated timeline schedule for implemenation/test