Version History Date Author Changes made Rationale Preethi Ramesh 1.0 Add risks and program model Initial draft of Feasibility Evidence Description (FED) Rakesh Mathur 1.1 Added more risks and identified NDI risks Updated FED Rakesh Mathur 1.2 Added another NDI evaluation Salesforce.com was added Rakesh Mathur 1.3 Added Business Case Analysis Completing the document Preethi Ramesh 1.4 Edited the ROI table Made the ARB meeting 3 3 on
Risk Assessment Table 5: Risk Assessment Risks Risk Exposure Potential Magnitude Risk Mitigation Probability of Loss Risk Exposure Rationale Use of LDAP for authentication and authorization of users 7 6 42 Develop a prototype for the suspected feature Use of DB2 as the back-end database for the system 9 5 45 Training needs to be taken by Developers to be able to use DB2 with ASP.NET framework. Need to be able to give privileges to an ‘administrator’ or a of administrators who can add/delete investigators from the system. High Operational clarity needed 9 5 45 Clarify ‘Administrator’ Role with Dept. of Public Safety personnel Interoperability of ASP.NET Application with DB2 8 6 48 Learn about how ASP.NET interoperates with DB2 and how data can be passed between the application and the database.
Version History Date Author Version Changes made Rationale 09/26/13 Vaibhav Dey, Shreyas Devaraj 1.0 First Draft of the Life Cycle Plan To initiate the Life Planning process and discuss the skills required. 10/12/13 Arijit Dey, Shreyas Devaraj 1.1 Modification done to Section 2, Section 3.1, 4, 5. First Revision before FC Package. 10/20/13 Arijit Dey, Shreyas Devaraj 1.2 Modification done to Section 3.1, 4, 5. First Revision after FC Package which includes the review responses of the stakeholders from ARB session. Mathur,
Required- ASP.Net, C# Gaurav Mathur Builder UML designer Current-JAVA, C++,MySQL Required-C# Preethi Ramesh Feasibility Analyst Requirement Engineer Current-ASP.Net, C# Divya Nalam Operational Concept Engineer UML designer Current-C/C++, Python Required- ASP.Net, C# Rakesh Mathur Validation and Verification of COTS Interoperability Current- ASP.Net, C#, JavaScript SKILLS REQUIRED FOR TEAM MEMBERS IN CSCI 577B C# ASP.NET MYSQL SERVER 2008 DB2
Table of Contents Operational Concept Description (OCD) 1 Version History 2 of Tables 4 Table of Figures 5 1. Introduction 6 1.1. Purpose of the OCD 6 1.2. Status of the OCD 6 2. Shared Vision 7 2.1. Overview of the system 7 2.2. Benefits chain diagram 8 2.3. System Boundary and Environment 9 3. System Transformation 10 3.1. Information on Current System 10 3.1.1. Infrastructure 10 3.1.2. Artifacts 10 3.1.3. Current Business Work-flow 11 3.2. System Objectives, Constraints and Priorities 12 3.2.1. Capability Goals 12 3.2.2. Organizational Goals 12 3.2.3. Constraints 12 3.3. Proposed New Operational Concept 14 3.4. Organizational and Operational Implications 16
2. Shared Vision 2.1. Overview of the system 1: The Program Model Assumption: The new system will be accepted by the staff of the City of Los Angeles Stakeholders Initiatives Value Propositions Beneficiaries Developers Management and of City of LA IT department of the City of LA Develop the web based system for reference letters processing Provide training to the City staff to use the new system Maintain the web based system Advertise the new system Reduce the labor involved in processing references letters Expedite application process Reduce administrative costs (postal) Decrease paper work Applicants Background investigators Managers/ Background Investigation Supervisor Supporting Staff Costs Benefits Time spent by client in giving inputs to development team, evaluating prototypes and training staff. Reduced costs (postal charges avoided) Reduced time in sending reference requests and receiving responses Reduced effort for due to avoiding paper work and for managers due to electronic assignment of investigators