Specifications include, but are not limited to: The Vendor is responsible for proper system documentation. All system documentation shall be comparable to industry standards and shall be provided in electronic format on CDs or DVDs (two sets) and one bound set of paper copy. The system documentation shall be created using standard tools such as Microsoft Word, Excel, Visio diagrams or Data Designer such as TOAD, ERWIN. The Vendor shall provide current system documentation immediately following selection that shall include, but not be limited to the following: 2.4.1 Data Dictionary- Shall include but not be limited to the following: Table names, Description, layouts with field name, field description, synonyms, primary and foreign keys, field type, field format, compression, and cross references. 2.4.2 High level project plan- Shall include at a high level the proposed vendors plan for implementing this project (e.g. milestones, deliverable, timing). 2.4.3 A conceptual and logical data models and a data dictionary with field descriptions for the proposed system. The State standard data modeling formats are .cdm (Sybase PowerDesigner) and MSWord for conceptual data models, and .pdm (Sybase PowerDesigner), .erx or .xml (CA Erwin), or .mdl (IBM Rational Data Architect) for physical data models. 2.4.4 A detailed Entity Relationship diagram, high-level application data flow charts, high-level application design and information processing functional flow charts shall be provided by the Vendor. For interface and batch jobs order/ sequence of program execution diagram for successful and unsuccessful job completion. Provide detailed security architecture document and diagram.
