1. MAPPS-SCM Software Configuration Management

2. MAPPS-SCM System Services MAPPS Mission Analysis and Payload Planning System Geometry and Trajectory Simulation Service Attitude Generation Service Instrument/Spacecraft Simulation Service Planning and Scheduling Service

3. WINDOWS 7 BUILD MAPPS - SCM ESTEC/SERVER ( CSDE) GIT JENKINS JIRA NEXUS /GIT GIT WINDOWS 7 TEST LINUX CENTOS 6.4 BUILD LINUX CENTOS 6.4 TEST JIRA MAC OS WINDOWS 7 3D TEST VM PM GIT JIRA/JENKINS/GIT/VMs/PMs will be located in the CSDE infrastructure in ESTEC and will be accessible from inside the ESA network only

4. MAPPS-SCM New Versioning System The new versioning system will be simplified. Only one version for each MAPPS components. The main version will be MAPPS_X.Y.Z (build number). The single component will be MAPPS_CCC_X.Y.Z (build number) where CCC is the component name MAPPS_1.2.3 (build 345) MAPPS_AGM_1.2.3 (build 345) MAPPS_GPTR_1.2.3 (build 345) MAPPS_PLM_1.2.3 (build 345) MAPPS_EPS_1.2.3 (build 345) MAPPS_TOOL_1.2.3 (build 345)

5. MAPPS - SCM Internal Structure AGM MAPPS DOCUMENTATION (it includes EPSNG) EPS GPTR MOI OPENIGS PLM CORE DEPENDENCIES 3D visualization

6. MAPPS - SCM Release 1.Source (except for MAPPS tool) 2.Binaries (If applicable) 3.Test report 4.User Manuals In case there is no time to update the user manual because urgent deliveries the information on how to use and configure the new implementation are in the JIRA issue. User Manual will be stored in confluence. 5.Release Note One release note will contain the detail for all components linked to the MAPPS delivery.

7. MAPPS - SCM Software Release Structure MAPPS_1 MAPPS_1_3 MAPPS_1_3_1 MAPPS_1_3_z MAPPS_1_4 MAPPS_1_4_1 MAPPS_1_4_z MAPPS_1_y MAPPS_1_y_1 MAPPS_1_y_z

8. MAPPS - SCM Software Release Structure MAPPS_TOOL_1_2_3 MAPPS_1_2_3 BIN MAPPS_AGM_1_2_3SOURCE MAPPS_EPS_1_2_3 SOURCE BIN MAPPS_PLM_1_2_3 SOURCE BIN ? Test Report MAPPS_TOOL_BIN_XX_1_2_3.zip MAPPS_TOOL_RT_XX_1_2_3.zip MAPPS_EPS_BIN_XX_1_2_3.zip MAPPS_EPS_RT_XX_1_2_3.zip

9. MAPPS - SCM Software Release Binaries Binary directory will contain 2 files: MAPPS_{component}_RT_{platform}_{version}.zip Contains the runtime dependencies of the binary (in the release note will be reported if those have been changed or not respect to the previous release) MAPPS_{component}_BIN_{platform}_{version}.zip Contains the binary. Example: “mapps.exe” or “eps.exe”

10. MAPPS-SCM Issue Types Bug New Feature Task Software Updates Requirements Software Modifications

11. MAPPS-SCM Issue Types Bug New Feature Task Confluence

12. MAPPS-SCM User Issues MAPPS AGM GPTR GPL EPS TOOL USERS DEVELOPERS BugNew Feature Task Software Modification Task

13. MODULES MAPPS AGM SYSTEM MAPPS - SCM Bugs – New Features – Tasks workflow Bug/New Feature Smr Task GPTR SmrTask PLM SmrTask EPS SmrTask TOOL SmrTask

14. MAPPS - SCM Bugs – New Features – Tasks workflow Deferred Assigned FeedbackIn Progress Resolved Closed Open

15. MAPPS - SCM Bugs – New Features – Tasks workflow 1.Open Issue (Users/Developers) a.Issue is assigned to a general “developers” user. b.Issue reach all the developers. c.The issue belong to the MAPPS system and the developers will link the issue to the appropriates modules (one or more). 2.Defer the Issue (Users/Developers) a.Decision need to be taken by SRB. 3.Assign Issue (Developers) a.Issue will be assigned internally by D-TEC. b.The reporter get notified and from now on the assigned developer will be the only one receiving the notifications. 4.Progress Start (Developers) a.Issue related work is in progress. b.The reporter get notified and should actively monitor the issue in case there are feedback to be provided.

16. MAPPS - SCM Bugs – New Features – Tasks workflow 4.Feedback needed (Users/Developers) a.The work on the issue is on hold developer awaiting for feedbacks. 5.Resolve Issue (Developers) a.The work on the issue is finished. b.The issue is re-assigned to the reporter for the testing and closure. 6.Close Issue (Users) a.The user after having successfully tested the implementation close the issue. b.After an issue is closed cannot be reopened. In case bugs are found another bug report shall be opened and linked to the closed issue. This will help to keep all the iterations on the same topic linked together.

17. MAPPS - SCM Smr workflow Open In Progress Resolved Closed

18. MAPPS Monitoring The user can monitor the status of the open issues: 1.Using predefined JIRA filter per mission: MISSION_NAME Open Issue MISSION_NAME Resolved Issue 2.Creating your own filter. 3.MMR -> MAPPS Monthly Report 4.SRN -> Software Release Note