1. Architecture Review 10/11/2004
Project Center System
Architecture Review
10/11/2004

2. Introduction
The Project Test Center System is a tool designed to help manage the code development tasks of a large project. Project Center has facilities for
Integrating a series of tools, and accepting new tools as needed by the project.
Supporting control, building, and testing a large code base.
Reporting changes, bugs, and progress against project milestones
Providing an easy to use, integrated GUI to all the tools
Managing security by authenticating users who access the code base

3. Context Diagram

4. Project Center A-Specs
Communication system
shall support transfer of messages in XML format from a source machine to a destination machine when addresses are provided.
shall provide support for multiple clients to connect and communicate with a single server process.
shall use web services for all communications between machines.
shall allow new server tools to register to receive communications from clients.

5. Project Center A-Specs
User Interface
shall provide a login mechanism for the user to enter authentication information.
shall deny access to all components of PC until the user has been authenticated.
shall provide Winforms based UI that supports integrated access within a network domain and across the internet.
shall provide an Asp .Net user interface for project center users that supports integrated access across the internet to the server tools described in this specification.

6. Project Center A-Specs
both the Winform and ASP interfaces shall provide a default home page/user screen from which the user can specify which tool he/she wants to use.
All communications of the User Interfaces to PC tools shall be through XML Messages.
both Winforms and ASP clients shall allow new tools to be registered with and accessed through the GUI.

7. Project Center A-Specs
Security system
shall support role based authentication of users when required given a user name and a password.
shall maintain a persistent store contains ID’s of all users registered, their password and the role assigned.
shall allow administrator access to edit the user information.

8. Project Center A-Specs
Database Store
shall support creation of required databases when PC is installed.
shall use SQL server for storing all persistent data required by PC except for data stored in CVS.
shall provide the capability to export all Project Center data to one or more XML files.

9. Project Center A-Specs
Open Source Tools
shall use CVS for version control of code, build scripts and tests.
shall support check in, check out and creation of new files.
shall collect records of changes made to the CVS code base and package it in a suitable XML format.
shall accept from the user the file and path names of the files to be tested and NUnit options.
shall use NUnit to test the specified files using the options specified by the user.

10. Project Center A-Specs
shall support display of the results generated when NUnit is executed on the file.
shall generate a XML message containing the results of running NUnit.
shall support building of user specified source files incorporating libraries on which it depends using NAnt.
shall generate a XML message containing the results of the build after running NAnt.
shall display results of the build to the user.

11. Project Center A-Specs
Scheduling and Tracking Tools
shall maintain the following schedule information.
Project milestones
Meeting schedules
Review schedules
Integration schedules
shall support adding new schedule information, editing existing information deleting entries.
shall support searching the schedule database based on date, status, project name, and title.

12. Project Center A-Specs
shall provide a GUI display for the Scheduling tool that includes role based access to display, search and edit operations.
shall maintain a store of Requirements information including title, data-time stamps, keywords, requirement number, text descriptions, allocation of derived requirements to client requirements, issues and issue status and priority.
shall support addition and modification of Requirements and Issues.
shall provide a GUI display to the Requirements database that includes role based access to display, search and edit operations..
shall provide list and text views to display requirements data.

13. Project Center A-Specs
shall support searching for a requirement by title fragment, keywords, date-time range or number range.
shall provide a logging facility for tracking bugs, recording the source, current status, date-time of first log and closure, text description, action taken and Responsible Individual (RI).
the user assigned responsibility shall be the user whose test first detected the bug.
shall allow the user to enter a text description for new bugs and a description of action taken for bugs that have been closed.

14. Project Center A-Specs
shall support searching of the bug information database by project name, filename, timestamp, RI and status.
shall provide a GUI display to the Bug Tracker tool that includes role based access to display, search and edit operations.
shall provide a logging facility for tracking all changes to the project code. Every change in the CVS code base must be recorded along with a reason for the change. Every build run by NAnt and test executed by NUnit shall be stored along with a brief description.

15. Project Center A-Specs
shall provide search functions for the change log allowing searches based on date, RI, project and whether the information required is logs of bug reports, CVS changes or build information.
shall provide a GUI display to the Change Log that includes role based access to display, search and edit operations.

16. Project Center A-Specs
Help Subsystem
shall provide help for each individual tool of Project Center
shall integrate all PC help files and provide support for new tool help and project documentation files to be linked to existing help.
shall provide brief tutorials for operating each tool.
shall provide system level help for PCS operations

17. Project Center A-Specs
Alerts and Notices
shall allow role based access to viewing, editing and adding notices.
shall store notices on the server to be delivered when requested by the user.

18. Project Center A-Specs
System Requirements
shall support installation of project center server and client on new Server and client systems.
shall provide the capability to insert new tools defined and acquired during the execution of the project.

19. Project Center A-Specs
Physical Structure
the Project Center System source code shall be composed of modules.
Project Center System builds shall be composed of managed code executables and dynamic-link libraries.
The User Interfaces shall delegate all operations, not directly associated with providing the user interfaces, to server modules, e.g., Communication, Data Management and Security, Scheduling and Tracking, and Open-Source Tool Integration.
All modules shall be provided with manual pages and correct maintenance pages.
Each server module shall be provided with a functional test library for use with NUnit and build scripts for use with NAnt.
Development
The project center development process shall use CVS, NUnit, and NAnt for all development. It shall use the Scheduler, bug tracker, and Change Log as soon as these tools become individually available. Prior to that time the development team shall use a manual process for scheduling, bug tracking, and logging changes.
Development Environment
The Project Center System shall build and operate in the ECS clusters, e.g., 010 Link, 202 Link, 129 Hinds, or CST.
Program Management
The Project Center System shall be developed subject to the conditions specified in the Project Center System Statement of Work, of the latest version.

23. Project Center Messages
All messages sent over the PCS network must be XML encoded.
Basic Message Format
<Message>
<Head>
<SrcAddress>…</SrcAddress>
<DestnAddress>…</DestnAddress>
<Type>…</Type>
</Head>
<Body>
</Body>
</Message>

24. Project Center Messages