DOCUMENTATION AND SOURCE CODE CONTROL

The EMA Microsoft Teams folder will be used to store the following files:

·        Functional System Specifications

·        Migration Packages (zip files)

·        Backup Presentation XML files

·        MXS files

·        MIF Files

·        Master Packet Document, PacketLog.xlsx that will list the ‘Packets’ and the environments to which they have been applied

All ‘source code’ will be included in the related FSS. 

Source Code includes the following:

·        Automation Scripts

·        XML Screens

·        MXS files

·        Java Classes (if required)

·        SQL Scripts

1.1      As-Built Documentation Updates

As-built documentation will not be changed after go-live. 

Changes to functionality previously applied to production should be documented appropriate to the level of complexity of the change. Where appropriate, an FSS will be developed, and associated changes will be documented in the FSS. Smaller changes will be documented in a less structured manner. Release notes will refer to the documentation of all included changes. 

For Data Visibility Rework, changes will be documented in the Data Visibility Rework FSS.

The ability for users to enable/disable the screen reader from their user profile was documented in a memo.

The Priority Code change will be documented as part of the go-live process for PFR or TS, which ever goes live first. 

Changes proposed by COT will be documented for review by the COT Change Approval Board (CAB) and EMA and this documentation will be deemed adequate to be associated with the applicable release.

1.2      Roles and Responsibilities