1. Transition Readiness Review December 4th, 2015
Combat Conflict
Transition Readiness Review
December 4th, 2015

2. TRR Outline OCD Transition objective and strategy Demo Support plan
Test cases
Quality focal point
Transition plan

3. Operational Concept Description (OCD)
PURPOSE OF THE PROJECT-
The project ‘Combat Conflict’ basically deals with helping the Veterans and Civilians to improve their conflict management skills.
STAKEHOLDERS-
Developers
College Students
Adult Learners with military experience
Masters of Business Veterans (MBVs)
Executives of Corporatives
Experiential Learning Center Staff (ELC)

4. INITIATIVES OF THE PROJECT-
Build the new system from scratch
Market the product developed to employees, students and veterans
Training the ELC Staff members by explaining the working of the system
Documentation (Creating the user manual for users to understand the system)
VALUE PROPOSITIONS-
Improve conflict management skills for MBV Students
Resolve conflicts in a team setting
More of collaborative study than competitive study
Improve team setting collaborative skills

5. BENEFIT CHAIN-

6. SYSTEM CAPABILITY DESCRIPTION-
The Combat Conflict System helps veterans and civilians improve their conflict management skills in a team formation.
The target customers of the system includes the Veterans of the Marshall School of Business (MBVs), college students and people enrolled in Marshall Executive Program.
The system provides the veterans and civilians a platform to solve their conflict management skills by experiencing real time scenarios.
The users of the system would like to adopt it as a medium to improve their conflict management skills because the system helps them experience the scenario and makes it interactive by continuous feedback.

7. SYSTEM TRANSFORMATION FROM CURRENT SYSTEM-
There is no existing system for the Combat Conflict System.
SYSTEM OBJECTIVES FOR COMBAT CONFLICT-
The major system objective is to help veterans and civilians to help them improve their conflict management skills.
The other objective is to create a platform to help veterans and civilians realise how other people think about the conflict scenarios by viewing a tabulation feedback. This also makes the system more interactive.

8. ORGANIZATIONAL GOALS-
OG-1: Help the students and veterans of Marshall School improve their conflict management skills.
OG-2: Generate a comparison to judge how differently the civilians and veterans react to a situation.
OG-3: Help students and veterans improve conflict management skills in a team collaboration.
CONSTRAINTS-
CO-1: Zero Monetary Budget: The selected NDI/NCS should be free or no monetary cost.

9. ELEMENT RELATIONSHIP DIAGRAM-

10. BUSINESS WORKFLOW-

11. ORGANIZATIONAL TRANSFORMATIONS-
The need to hire a new system maintainer to take care of the system.
The change in the class structure to help students use the system in a collaborative team fashion.
OPERATIONAL TRANSFORMATIONS-
The veterans will be using an online system in order to improve their conflict management skills.
The Professors of Marshall School and ELC help their students and veterans improve their conflict management skills by the use of an online system which is both interactive and responsive.

12. Transition objective and strategy
Provide client with fully functional and ready to be used system along with manuals.
Dec 7, freeze code and migrate to DigitalOcean
Dec 12, final ops check

13. Demo
Mansi/Jai/Chris - Demo
Feel free to add people into here

14. Individual Test Mansi/Jai/Chris - Demo
Feel free to add people into here

15. Team Test
Mansi/Jai/Chris - Demo
Feel free to add people into here

16. Support Strategies
ELC have a fully functional prototype hosted on their own server, but are free to update the project.
ELC may find a new development team to help create a new feature or make modifications.
ELC may allocate additional funds to hire a consultant for their project
Consultants can help provide new teams answers for questions they may have about the product
Tony
Identify Support Strategy
Identify support lifetime and information about next release or possible development of current evolutionary requirement(s).
Identify Support Environment
Identify minimum hardware, software, and facilities specification for system support.
Identify Support Responsibilities
Identify who will provide system support, required skills, and their scope of responsibilities.

17. Support Environment & Responsibilities
Required items to support Combat Conflict
A web hosting server
Configurations to support WordPress
ELC Staff Responsibilities
Provide guidance for the team exercises using the Training Material
Developer Team Responsibilities
Provide system support to make content changes or add additional features to the product
Understand how to navigate through WordPress using the User Manual
Needs to understand how to use HTML, CSS, JavaScript, PHP, and modify config files
Tony
Identify Support Strategy
Identify support lifetime and information about next release or possible development of current evolutionary requirement(s).
Identify Support Environment
Identify minimum hardware, software, and facilities specification for system support.
Identify Support Responsibilities
Identify who will provide system support, required skills, and their scope of responsibilities.

18. Test Cases, Procedures and Results
Test Case Number
Test Case
Related Win Conditions
Results
[TC-01]
View Feedback
-Database Functional, Database Down, User does not submit individual test
Recording Responses
Individual test results are used in team test
[TC-02]
Generate Summary of Techniques report and send .
-Correct id, incorrect id,
Real Time Feedback/Recording Responses
s are generated correctly, incase of incorrect , also sent to ELC general
[TC-03]
Verify functionality of pre-assignment
-Test correct information, Demographic information required
Demographic Information/ Recording Responses
User can’t continue without entering all demographic info. Tests stored by demographic.
[TC-04]
Team Scenario
-Able to complete scenarios, free form answers, closing browser
Skill Building
Can go through all scenarios and complete system. Closing browser creates a new session.
Lisa

19. Test Case Number Test Case Related Win Condition
Results
[TC-05]
Verify stability of website when there is concurrent access through team exercises.
-All submit successfully, one fails to complete
Real Time Feedback/ Skill Building/ Recording Responses
Can have multiple accesses to both team and individual test.
[TC-06]
Verify multiple browser functionality
-Individual test and team test UX
Works on multiple browsers
[TC-07]
Verify stability of product across different screen sizes & mobile devices
Invalid, ELC to use a specific computer, but still works on different screen sizes. No mobile
[TC-08]
Verify Validation Capabilities
Recording Responses
s which are sent out based on tests/scenarios answered.

20. Quality Focal Point - Requirements Traceability Matrix

21. Quality Focal Point - Technical Debt
Over the course of the project, we have paid back the vast majority of our technical debts. Some examples:
Using the WordPress plugin mechanism rather than custom PHP code
Removing leftover plugins from the NDI evaluation phase to unclutter the Wordpress installation
Hardcoding the ‘id’ in the database
Some technical debts that have not yet been paid back, and are planned to be covered in the future (post-transition)
Transfer of domain management to ELC control
The coordination for this has already begun, and the transfer should occur soon
Adding the feature of highlighting the answer statistics
This could be done by the next team to work on this application, as we ran out of time
Adding additional security measures to the web application
Though there are some measures already in place, additional testing and development could be done by future teams to improve site security
Tyler

22. Summary of Transition Plan
Strategy & Objectives
Preparation
Progress
Schedule
10 min. Summary of Transition Plan (as appropriate)
Nick

23. Transition Strategy & Objectives
“Turn-key” deliverable to client’s organization
Developer to perform the following:
Create and configure virtual server (“droplet”) on client’s Digital Ocean account
Configure DNS settings in support of application/droplet
Install project platform onto this droplet
Configure ELC website to point to Combat Conflict application
Transfer ownership of DNS registration to client
Deliver system snapshot in the form of a deployable installer to client
Deliver training and user manuals to client

24. Transition Strategy & Objectives
Client to perform the following:
Notify development team of remaining changes by cutoff date
Provide domain registrar information to development team to facilitate transfer of combatconflict.com domain ownership

25. Transition Preparation
No hardware or site preparation, as server is virtualized using a third-party hosting service
ALL software preparation will be performed in advance by the development team

26. Completed Transition Objectives
Created and configured virtual server (“droplet”) on client’s Digital Ocean account
Configured DNS settings in support of application/droplet
Performed “dry-run” export of Combat Conflict system to Digital Ocean
Used to test droplet & DNS configuration and resolve remaining issues
Issues Resolved
DNS configured for DigitalOcean hosting
Mail server functionality enabled, DNS updates performed
Issues Remaining
Reverse DNS configuration causing mail to go to spam folder for some services

27. Ongoing Transition Items
Correction of remaining rDNS issues
Week of Nov 30:
Client-run user evaluations
Acceptance Test dry-runs
Transition Readiness Review
Week of Dec 7:
Transfer ownership of “combatconflict.com” domain registration to client’s organization
Delivery of system snapshot, manuals to client

28. Transition Schedule
Dec 5-6: Correct any remaining defects identified during user evaluation and dry-run testing
Dec 7: Code freeze; migrate code base to production server (digitalocean)
Dec 8-9: Acceptance Test sell-runs on production system
Dec 9: Add link to Combat Conflict on ELC main page
Dec 10: Initiate transfer of combatconflict.com DNS registration from developer’s registrar to domain registrar of client’s choosing (requires ~24 hours downtime)
Dec 10: Create backup snapshot of Combat Conflict application as installed on client’s hosting
~Dec 12: Final ops check of system after DNS transfer completed

29. Feedback
20 min. Feedback