The baselines for each phase and reviews necessary to approve the documentation are also defined in the Software Engineering Program. The characteristics of an evolving system are defined and documented in increasing detail at logical transition points, or baselines, of the software development life cycle. At any time in the system life cycle, all previously established baselines, together with any approved changes to these baselines, constitute the formal identification of the system and its components. The type of system being developed will dictate the level of documentation necessary to support that system. The use of the EEIs defined in this volume represent a flexible approach to system documentation.
All systems require some form of documentation.
Software systems that are used nationwide, Agency wide and support major program initiatives require complete documentation and thoughtful consideration of options, life cycle costs and mission needs. EEIs are required for both new system and existing systems. Information managers may want to increase the depth and breadth of these EEIs based on the circumstances of the project. Additional EEIs may have to be developed to meet the specific needs of a given software system or project. Determining Documentation Requirements Criteria for determining the minimum EEI documentation for a specific software system are based on the nature and scope of the information system and its importance to EPA's mission.