TCMS Design Deliverables


The first column denotes the time for completion of the goals for the individual areas of functionality. The goals for that time period are in the row, divided by area of functionality. Interfaces between components regarding data being stored or displayed need the following state information: table, field, data type, static (or dynamic), defined list or value, (dependant field). dynamic and dependant field are reserved for future functionality. All components should have a common interface that returns the version, timestamp when it was built, and 255 char string for miscellaneous data.

Time Schema Data Storage Data Entry Query Reports Logging UI Notes
1 week Design component infrastructure Design component infrastructure Design component infrastructure Design component infrastructure Design component infrastructure Design component infrastructure Design component infrastructure Should be designed with re-usability, modularity, and distributed functionality in mind. A design review follows. See Figure 1.
1 week Design interface between schema and data storage Design interface between data storage and data entry Design interface between data entry and data storage Design one-way interface for sending strings and severity level (int) Design interface between UI and data entry Interface/protocol should be consistent between all components, fully documented in headers/IDL, and behavioral graphs. See this graph. Review.
2 weeks Done. Done. Done. Design interface between query and data storage Design interface between UI and query Fully documented headers/IDL, and behavioral graphs. See this graph. Review.
1 week Done. Done. Done. Done. Design interface between reports and query Done. Done. Final Review before implementation.