The completed technical specification document is the last review point before development begins. Development may include expenditure of funds for acquisition of software and hardware as well as the assignment of programmers who will begin the development effort. Normally, the requesting unit will not be involved with the process again until acceptance testing begins. It is therefore critical that the requesting unit fully review and commit to the details in the technical specifications. (Any ambiguity or omissions should be resolved with the systems analyst before the requesting unit accepts the document.)

The following templates exist for the creation of a technical specification document and are located in the Development/mudev/ISSDocumentation/ISS_Standards directory of the Miami Development environment in Harvest:

• ERD (Entity Relationship Diagram) required when creating a new database table. (Not started)
  
  
• Point & Click Specification Document used for new point & click query development. (Approved)
  
  
• Technical Specification Document used for new reports and non-interactive processes such as Banner Job Sub, EM, etc. (Approved)
  
  
• Interactive Application Specification Document used for new applications that require user interaction such as web applications (e.g. MyMiami). This document is used to define the overall application and will be used in conjunction with multiple interactive process specification documents (see below). (Approved)
  
  
• Interactive Process Specification Document used to define the individual processes in a new interactive application, such as a single webpage within an web application. Multiple interactive process specification documents may be referenced from an Interactive Application Specifications Document (see above). (Approved)
  
  
• CCS Deliverable Request Form used to request work from CCS (e.g. server set up, networking tasks). (In Progress)

Please send comments and suggestions to the ISS Standards Committee at MCSUASTD@Listserv.muohio.edu.