1. City of Los Angeles Personnel Department Mobile Application Team 02:Shreya kamani Anushree Sridhar Pattra Thongprasert Abhishek Trigunayat Travis Jones William Everton 1

2. TRR Outline 1. Introduction 2. Demo of Initial Operational Capability - Abhishek and Anushree 3. Test Cases, Procedure and Results - Travis 4. Quality Focal Point - William 5. Support Plan - Anushree 6. Summary of Transition Plan - Pattra 2

3. System Purpose Mobile application that provides Critical information to applicants interested in employment opportunities with City of LA Allow users to subscribe to a specific job The system will send notification via email and/or text message for reminding that the position is open 3

4. Capability goals - Completed! 4

5. Demo of IOC - Creating User Profile 5

6. Demo of IOC - Search by Name / Job ID 6

7. Demo of IOC - Subscribe to a Job 7

8. Demo of IOC - View All Open Jobs 8

9. Demo of IOC - Viewing LA Police Department Jobs 9

10. Test Plan and Cases 10

11. Test Procedures Testing done by team tester Acceptance testing done by client at CCD 11

12. Test Cases USE CASETEST CASE UC01: Create/update user profileTC-05-01: Create/update user profile details UC02: View Open JobsTC-02-01: View current open jobs UC03: Search all jobsTC-01-01/02: Search existing jobs by keyword of job ID UC04: VIew job descriptionsTC-03-01/02: View job descriptions for existing jobs and open jobs UC05: Subscribe for notificationsTC-04-01: Subscribe for notifications UC06: Notification for job openingsTC-06-01: Receive notification for open jobs UC07: Process Neogov RSS feedTC-07-01: Process Neogov RSS Feed UC08: View police department jobsTC-08-01: View LAPD jobs 12

13. Test Results Bugs found: o #1264: unable to return from LAPD site o #1265: user profile refresh o #1266: case-sensitive search o #1292: “Back” button for iOS Concerns: o List results in alphabetical order 13

14. Quality focal point 14

15. Traceability Matrix 15

16. Metrics 16

17. Metrics, cont. 17

18. Metrics, cont. 18

19. Burndown 19

20. Burndown, cont. 20

21. Lessons Learned Benefits of Feedback Sessions The team did not utilize group feedback sessions to share lessons learned. In many agile software development teams, these feedback loops provide a way for the team to learn as a whole and as individuals. Scheduling is Difficult Students have different classes, assignments, and personal lives. Working around each others’ schedules is paramount for cohesive teamwork. Scheduling in advance provides all parties with time to prepare and plan for the next milestone. Communication Every team can stand improvement for better communication. Since the entire team is not collocated in Los Angeles, it is even more important that we have clear discussions regarding tasks and intent. Software Effort is Difficult to Estimate As engineers, we often times underestimate the effort required in a task. Our team has done a good job at evolving their task estimations, which has helped in planning and scheduling. 21

22. Support and Transition Plan 22

23. Support Plan The system has been tested locally by the development team and it is working. Unfortunately we will be unable to test the system on a live environment has it will take time to receive permission to deploy. Deployment and further bug fixes will be the responsibility of the client. We will provide a system admin manual to assist in this process. 23

24. Transition Concerns Development team was notified that the transition on real site at Personnel IT department couldn’t be done as scheduled. The system must be reviewed by City of LA Board before deployment. The review process - unknown period and details Development team will deliver all the final deliverables to clients along with the manual for deployment so that client’s staff would be able to do it after the decision has been decided. 24

25. Transition Strategy Delivery method depends on clients preference (Discuss in TRR ARB session). 1.All deliverables will be made into physical products and deliver to client on the decided date. 1.All deliverables will be uploaded on Team website. Client will be provided with the link to download. Available until 2 nd May 2014. 25

26. Hardware Preparation The decision on installing the existing server or purchase of a new server would depend on the executive board’s decision and policies. Staff would require around 6 to 8 hours to prepare the hardware. If the hardware were existing and being reused the preparation time would be minimal. The IT department will get the necessary approvals for hardware installation from the concerned authorities. 26

27. Software Preparation The packaging of software would be in form of EAR/JAR/WAR (Enterprise Archive, Java Archive, Web Archive) and script files Open source except for the database (DB2) Android IDE and Xcode The IT department will get the necessary approvals for software installation from the concerned authorities. 27

28. Site Preparation DB2 must already be installed on the server If the system will be installed on the existing server, the server needs to be backed up before doing the transition Must have at least one computer that has access to internet and installation server. IT department would be responsible for the security on the site. The server should be protected by a password at all times and only an administrator should have access to it. 28

29. Transition Schedule 29

30. Additional Documents & Activities System Administrator Manual Source Code Baselines including comments in the source files Training o 04/01/14: Overview of server application and mobile app o Upon request - Discuss in TRR ARB session 30

31. Thank You 31