Life Cycle Plan (LCP)

 Life Cycle Plan (LCP) Data Information Analytics - Managed Online Network Database:DIAMOND Team 01 Samantha Cote Project Manager, Life Cycle PlannerHaiwen Chen Requirements EngineerDanny Diaz Ayon Verification & Validation, Quality Focal PointShijie Ding Software Architect/UML ModelerMeghana Kolasani PrototyperDzung Phan Software Architect/UML Modeler, PrototyperDerek Wang Feasibility AnalystDrew Webb Operational Concept EngineerOctober 21st, 2020Version HistoryDateAuthorVersionChanges madeRationale10/15/20Samantha Cote1.0initialized template for projectadded team members, rolescompleted section 1Initialize the document for further completion10/17/20Samantha Cote1.2completed sections 2 & 3added tables for COCOMO scale drivers and cost driversTo keep the document consistent with our COCOMO estimation10/20/20Samantha Cote1.3Completed sections 4 & 5Maintain consistency with FC Package expectations10/21/20Samantha Cote2.0updated stakeholders to be consistent with other team members’ artifactsTo comply with ARB Presentation Feedback; Final version to be submit for FC PackageTable of Contents TOC \h \u \z Life Cycle Plan (LCP)Version History1Table of Contents2Table of Tables3Table of Figures41. PAGEREF _heading=h.1t3h5sf \h Introduction51.1 PAGEREF _heading=h.4d34og8 \h Purpose of the LCP51.2 PAGEREF _heading=h.2s8eyo1 \h Status of the LCP51.3 PAGEREF _heading=h.17dp8vu \h Assumptions52. PAGEREF _heading=h.3rdcrjn \h Milestones and Products72.1 PAGEREF _heading=h.26in1rg \h Overall Strategy72.2 PAGEREF _heading=h.lnxbz9 \h Phases 72.3 Project Deliverables93. PAGEREF _heading=h.1y810tw \h Responsibilities123.1 PAGEREF _heading=h.4i7ojhp \h Project-specific stakeholder’s responsibilities123.2 PAGEREF _heading=h.2xcytpi \h Responsibilities by Phase123.3 PAGEREF _heading=h.3whwml4 \h Skills154. PAGEREF _heading=h.2bn6wsx \h Approach164.1 PAGEREF _heading=h.qsh70q \h Monitoring and Control164.2 PAGEREF _heading=h.3as4poj \h Methods, Tools and Facilities175. PAGEREF _heading=h.1pxezwc \h Resources18 Table of Tables TOC \h \u \z Table 1: Artifacts Deliverables in Exploration Phase9Table 2: Artifact deliverable in Valuation Phase9Table 3: Artifact deliverable in Foundations Phase10Table 4: Artifact deliverable in Development Phase11Table 5: Stakeholder's Responsibilities in each phase12Table 6: Skills Required for Each Role16Table 7: Methods, Tools and Facilities17Table 8: Modules and Estimated SLOC19Table 9: COCOMO-II Scale Drivers19Table 10: COCOMO-II Cost Drivers for Module 120Table 11: COCOMO-II Cost Drivers for Module 2 22Table 12: COCOMO-II Cost Drivers for Module 324Table 13: COCOMO-II Cost Drivers for Module 426Table of Figures TOC \h \u \z Figure 1: COCOMO Estimation Result with 4 Modules 28Figure 2: Most Likely Estimated Person-Months 29 Introduction1.1 Purpose of the LCPThe purpose of the Life Cycle Plan (LCP) for the DIAMOND project is to plan for each phase of the project’s timeline, monitor the project’s compliance with the Win-Win Negotiations, and adapt if needed to ensure that the project will succeed within its available effort and schedule. The document is currently at the Foundations Commitment (FC) Package state. 1.2 Status of the LCPThe status of the LCP document is currently at Foundations Commitment (FC) Package version 2.0. This is the version that was presented at the ARB FCR presentation and will be submitted as part of the FC Package for the Foundations phase. Major changes from the previous version include:Edits in the list of stakeholders that were provided as feedback at the ARB FCR presentation.Contains content for LCP sections 1-5 as requested for the FC Package.There are no differences between the contents of the LCP and the Win-Win Negotiations. 1.3 AssumptionsThe assumptions are the following:The Client will respond within at most 2-3 days when approvals or answers to team questions are required.There will be no drastic changes to project requirements after win-win negotiation has been completed.The duration of the project lifecycle is 24 weeks; 12 weeks in Fall 2020, 12 weeks in Spring 2021.The Client will deliver sample data, table structures, and forms to the development team early in the fall so that prototypes can align with the client’s desired data structures.The Client will purchase a production Salesforce license at the start of the Spring 2021 semester.5 of the 8 team members will be able to continue on to 577B, allowing us to keep the majority of the team the same.Software Availability: Salesforce will remain available 24/7.The Client will meet regularly with the team to discuss progress and give desired feedback on progress.Team members will complete work and artifacts that align with their project roles by the time that it is due.2. Milestones and Products2.1 Overall StrategyThe overall ICSM strategy for the DIAMOND project is a NCS-Driven process model, due to the fact that the Salesforce platform is a net-centric web service that offers us a development environment and many custom libraries to help the team build out the system. The majority of our early efforts therefore rely on rigorously prototyping both the Salesforce system itself and the libraries we would like to use for other capabilities to ensure that all will be compatible with one another and to ensure that the system will be buildable using these different tools within the schedule and effort that has been allocated for the project.The project also depends on the Schedule As Independent Variable concept, due to the fact that it is being built as part of a university course, and the schedule resources are therefore limited for team members.Our process includes the following milestones:Valuation Commitment Review (VCR)Top Risk PrototypeFoundations Commitment Review (FCR)Prototype Progress PresentationDevelopment Commitment Review (DCR)Re-baselined Development Commitment Review (RDCR)Core Capability Drivethrough (CCD)Transition Readiness Review (TRR)Operational Commitment Review (OCR)2.2 PhasesExploration PhaseDuration: 8/2020 - 9/14/2020Concept: Form teams, meet client, understand basic project scope and requirements, determine stakeholder win conditionsDeliverables: Client Interaction Report, Win Conditions Report, Team Website, Bi-Weekly PackageMilestone: Valuation Commitment Review (VCR)Valuation PhaseDuration: 9/14/2020 - 10/23/2020Concept: Begin prototyping, perform resource estimation, prioritize win conditions, develop initial feasibility evidence, develop operational concept, explore architecture optionsDeliverables: OCD, SSAD, LCP, & FED (FC Package), Top Risk Prototype, Bi-Weekly PackageMilestones: Top Risk Prototype, Foundations Commitment Review (FCR)Foundations PhaseDuration: 10/23/2020 - 2/19/2021Concept: Continue risk-driven prototyping, finalize architecture decisions, further develop the life cycle plan, prepare for developmentDeliverables: Larger prototype, DC Package, Bi-Weekly Package, Re-baselined DC PackageMilestones: Prototype Progress Presentation, Development Commitment Review (DCR), Re-baselined Development Commitment Review (RDCR)Development PhaseDuration: 2/19/2021 - 5/07/2021Concept: Develop the system, integrate, testing, and preparation for transition to operation within the client’s environmentDeliverables: Updated OCD, FED, SSAD, & LCP, CCD Report, TP, SP, ATPR, UM, Bi-Weekly PackageMilestones: Core Capability Drivethrough (CCD), Transition Readiness Review (TRR)Operation PhaseDuration: 5/07/2021 - 5/15/2021Concept: Install the product, execute the transition plan, receive client feedbackDeliverables: Close Out Report, Client Evaluations, Final DeliverablesMilestones: Operational Commitment Review (OCR)2.3 Project DeliverablesProject type: 2-semester NCS-Driven Project2.3.1 Exploration PhaseTable 1: Artifact deliverables in Exploration PhaseArtifactDue dateFormatMediumClient Interaction Report9/14/20202.doc(x), .pdfsoft copyWin Conditions List9/16/2020.doc(x)soft copyTeam Website9/18/2020websitewebsiteProject Planevery other Friday.mpp, .pdfsoft copyProgress Reportevery other Friday.xlssoft copyTrello Board Documentevery other Friday.pdfsoft copyProject Risk and Defect Reportevery other Friday.xlssoft copy2.3.2 Valuation PhaseTable 2: Artifact deliverables in Valuation PhaseArtifactDue dateFormatMediumOCD (FC-Draft)10/12/2020.doc(x), .pdfsoft copyFED (FC-Draft)10/12/2020.doc(x), .pdfsoft copyLCP (FC-Draft)10/12/2020.doc(x), .pdfsoft copySSAD (FC-Draft)10/12/2020.doc(x), .pdfsoft copyTop Risk Prototype9/25/2020codesoft copyTop Risk Prototype Presentation Material9/25/2020.pptxsoft copyOCD (FC-Package)10/23/2020.doc(x), .pdfsoft copyFED (FC-Package)10/23/2020.doc(x), .pdfsoft copyLCP(FC-Package)10/23/2020.doc(x), .pdfsoft copySSAD (FC-Package)10/23/2020.doc(x), .pdfsoft copyProject Planevery other Friday.mpp, .pdfsoft copyProgress Reportevery other Friday.xlssoft copyTrello Board Documentevery other Friday.pdfsoft copyProject Risk and Defect Reportevery other Friday.xlssoft copyTechnical Debt Reportevery other Friday.xlssoft copy2.3.3 Foundations PhaseTable 3: Artifact deliverables in Foundations PhaseArtifactDue dateFormatMediumAcceptance Criteria & Definition of Done10/26/2020.pdfsoft copyTeam Retrospective Analysis10/30/2020.pdfsoft copyPrototype Progress Report11/13/2020.doc(x), .pdfsoft copyOCD (DC-Draft)11/16/2020.doc(x), .pdfsoft copyFED (DC-Draft)11/16/2020.doc(x), .pdfsoft copySSAD (DC-Draft)11/16/2020.doc(x), .pdfsoft copyLCP (DC-Draft)11/16/2020.doc(x), .pdfsoft copyOCD (DC-Package)11/24/2020.doc(x), .pdfsoft copyFED (DC-Package)11/24/2020.doc(x), .pdfsoft copySSAD (DC-Package)11/24/2020.doc(x), .pdfsoft copyLCP (DC-Package)11/24/2020.doc(x), .pdfsoft copyProject Planevery other Friday.mpp, .pdfsoft copyProgress Reportevery other Friday.xlssoft copyTrello Board Documentevery other Friday.pdfsoft copyProject Risk and Defect Reportevery other Friday.xlssoft copyTechnical Debt Reportevery other Friday.xlssoft copy2.3.4 Development PhaseTable 4: Artifact deliverables in Development PhaseArtifactDue dateFormatMediumUpdated OCD2/19/2021.doc(x), .pdfsoft copyUpdated FED2/19/2021.doc(x), .pdfsoft copyUpdated LCP2/19/2021.doc(x), .pdfsoft copyUpdated SSADTBD Spring 2021.doc(x), .pdfsoft copyCCD Report3/13/2021.doc(x), .pdfsoft copyTransition Plan 4/16/2021.doc(x), .pdfsoft copySP4/16/2021.doc(x), .pdfsoft copyATPR4/16/2021.doc(x), .pdfsoft copyUM4/16/2021.doc(x), .pdfsoft copyProject Planevery other Friday.mpp, .pdfsoft copyProgress Reportevery other Friday.xlssoft copyTrello Board Documentevery other Friday.pdfsoft copyProject Risk and Defect Reportevery other Friday.xlssoft copyTechnical Debt Reportevery other Friday.xlssoft copy3. Responsibilities3.1 Project-specific stakeholder’s responsibilitiesThis project does not have any project-specific stakeholders other than the project’s client, users, maintainer, developers, and IIV&V engineer.3.2 Responsibilities by PhaseTable 5: Stakeholder's Responsibilities in each phaseTeam Member / RolePrimary / Secondary ResponsibilityExplorationValuationFoundationsDevelopment- Construction IterationDevelopment- Transition IterationSamantha CoteProject Manager,Life Cycle PlannerPrimary ResponsibilityCoordinate meeting with clientsSecondary ResponsibilityOrganize team meetings and contactPrimary ResponsibilityMaintain a project plan that the team will follow, and coordinate meetings with clientSecondary ResponsibilityReview artifacts and ensure all team assignments are delivered on timePrimary ResponsibilityCoordinate with team members and client, schedule necessary meetings, maintain a project planSecondary ResponsibilityReview artifacts and ensure all team assignments are delivered on timePrimary ResponsibilityCoordinate with team members and client, schedule necessary meetings, maintain a project planSecondary ResponsibilityReview artifacts and ensure all team assignments are delivered on timePrimary ResponsibilityCoordinate with team members and client, schedule transition trainingSecondary ResponsibilityProvide the transition trainingHaiwen ChenRequirements EngineerPrimary ResponsibilityOrganize win conditions and maintain list of stakeholder requirementsSecondary ResponsibilityEnsure all project progress is in line with requirementsPrimary ResponsibilityPrioritize win conditionsSecondary ResponsibilityEnsure all project progress is in line with requirementsPrimary ResponsibilityDirect prototypers to follow top-risk requirementsSecondary ResponsibilityEnsure all project progress is in line with requirementsPrimary ResponsibilityRe-prioritize win conditions if necessarySecondary ResponsibilityEnsure all project progress is in line with requirementsPrimary ResponsibilityEnsure that final system deliverable meets all requirementsSecondary ResponsibilityEnsure all project progress is in line with requirementsDanny Diaz AyonIIV&V, Quality Focal PointPrimary ResponsibilityDetermine best tools to use for team communicationSecondary ResponsibilitySet up a Trello board to track team tasksPrimary ResponsibilityManage Trello board to ensure team is following tasksSecondary ResponsibilityVerify that any progress on different parts of the project are consistent with othersPrimary ResponsibilityManage Trello board to ensure team is following tasksSecondary ResponsibilityVerify that any progress on different parts of the project are consistent with othersPrimary ResponsibilityDetermine best testing strategy and implement a test suiteSecondary ResponsibilityVerify that any progress on different parts of the project are consistent with othersPrimary ResponsibilityFinal verification that system works as specifiedSecondary ResponsibilityVerify that project is consistent across the boardDrew WebbOperational Concept Engineer, DeveloperPrimary ResponsibilityDevelop initial win conditionsSecondary ResponsibilityBegin to outline use cases and benefits of the proposed systemPrimary ResponsibilityDevelop the benefits chain diagram and Operational ConceptSecondary ResponsibilityContribute to top-risk prototypePrimary ResponsibilityContinually update the operational concept as project requirements changeSecondary ResponsibilityContribute to top-risk prototypesPrimary ResponsibilityDevelop system featuresSecondary ResponsibilityEnsure that all development is in line with operational conceptPrimary ResponsibilityContribute to transition planSecondary ResponsibilityHelp with transition trainingMeghana KolasaniPrototyper, DeveloperPrimary ResponsibilityExplore NCS/NDI choicesSecondary ResponsibilityHelp to develop initial win conditionsPrimary ResponsibilityBuild top risk prototypeSecondary ResponsibilityEnsure that prototypes are following project’s top risksPrimary ResponsibilityDevelop further top risk prototypesSecondary ResponsibilityEnsure that prototypes are following project’s top risksPrimary ResponsibilityDevelop system featuresSecondary ResponsibilityEnsure that all development is in line with project requirementsPrimary ResponsibilityContribute to transition planSecondary ResponsibilityHelp with transition trainingDzung PhanPrototyper, DeveloperPrimary ResponsibilityExplore NCS/NDI choicesSecondary ResponsibilityHelp to develop initial win conditionsPrimary ResponsibilityBuild top risk prototypeSecondary ResponsibilityEnsure that prototypes are following project’s top risksPrimary ResponsibilityDevelop further top risk prototypesSecondary ResponsibilityEnsure that prototypes are following project’s top risksPrimary ResponsibilityDevelop system featuresSecondary ResponsibilityEnsure that all development is in line with project requirementsPrimary ResponsibilityContribute to transition planSecondary ResponsibilityHelp with transition trainingShijie DingSystem Architect/UML Modeler,TesterPrimary ResponsibilityExplore system architecture optionsSecondary ResponsibilityIdentify stakeholders, users, etc.Primary ResponsibilityDetermine architecture to prototype, build UML diagramsSecondary ResponsibilityWork with prototypers to ensure prototypes are consistent with the architecture designPrimary ResponsibilityContinue to refine architecture diagramsSecondary ResponsibilityWork with prototypers to ensure prototypes are consistent with the architecture designPrimary ResponsibilityDevelop tests for system featuresSecondary ResponsibilityWork with IIV&V to ensure system components work as intendedPrimary ResponsibilityContribute to transition planSecondary ResponsibilityHelp with transition trainingDerek WangFeasibility Analyst,DeveloperPrimary ResponsibilityAnalyze potential NDI choicesSecondary ResponsibilityHelp to develop initial win conditionsPrimary ResponsibilityAnalyze chosen NDI choices, compute benefit, ROISecondary ResponsibilityWork with prototypers to decide what is top-riskPrimary ResponsibilityAnalyze chosen NDI choices, update benefit, ROI as neededSecondary ResponsibilityWork with prototypers to decide what is top-riskPrimary ResponsibilityDevelop system featuresSecondary ResponsibilityEnsure that all development is in line with project requirementsPrimary ResponsibilityContribute to transition planSecondary ResponsibilityHelp with transition trainingDr. Darin GrayClient/STEM Center DirectorPrimary ResponsibilityMeet with team and give project overviewSecondary ResponsibilityCommunicate desired system functionality to teamPrimary ResponsibilityProvide team with sample data and formsSecondary ResponsibilityMeet with team frequently to give feedback and attend all team presentationsPrimary ResponsibilityProvide team with any updated sample data and forms; prioritize capabilitiesSecondary ResponsibilityMeet with team frequently to give feedback and attend all team presentationsPrimary ResponsibilityMeet with team frequently to give feedback on system developmentSecondary ResponsibilityRe-prioritize system features as necessaryPrimary ResponsibilityPrepare for system transitionSecondary ResponsibilityAttend transition trainingTBD (To be hired by STEM Center)MaintainerPrimary ResponsibilityN/ASecondary ResponsibilityN/APrimary ResponsibilityN/ASecondary ResponsibilityN/APrimary ResponsibilityN/ASecondary ResponsibilityN/APrimary ResponsibilityN/ASecondary ResponsibilityN/APrimary ResponsibilityMeet with team to understand system functionality and get admin accountSecondary ResponsibilityAttend transition training to prepare for the system’s life cycle maintenance.3.3 SkillsTable 6: Skills Required for each RoleTeam membersRoleSkillsSamantha CoteProject Manager, Life Cycle PlannerProject management, organization, communication skills, good time management, good understanding of MS Project and COCOMOIIHaiwen ChenRequirements EngineerOrganization, Negotiation skillsDanny Diaz AyonIIV&V, QFPQuality Management, Testing experience, Trello/JIRADrew WebbOperational Concept Engineer, PrototyperGood understanding of benefit chains and use cases, good organization,JS, XML, Salesforce, HTML, database systemsMeghana KolasaniPrototyperJS, XML, Salesforce, HTML, database systemsDzung PhanPrototyperJS, XML, Salesforce, HTML, database systemsShijie DingSystem Architect/ PrototyperGood understanding of UML diagrams, system architecture. JS, XML, Salesforce, HTML, database systemsDerek WangFeasibility Analystgood organizational skills, good understanding of ROI, risk and risk managementNew MemberDeveloperJS, XML, Salesforce, HTML, database systemsNew Member 2 (Potentially)TesterSalesforce testing capabilities, general software testing methods4. Approach4.1 Monitoring and ControlEach team member is responsible for the artifacts assigned to their role, but we have monitoring and control methods that we use as a team to track project progress, manage risk, identify defects, and plan for the project life cycle. Some of the methods of monitoring and control that our team are using are:Progress Reports: A bi-weekly report that tracks the project size (SLOC), keeps track of the COTS being used, and any new ones that have been recently considered, and tracks the work that has been done for the past two weeks and the work that is planned to get done in the following two weeks.Project Plans: A bi-weekly MS Project Plan (Gantt chart) that outlines what work will be done by which team member over the upcoming two weeks. It outlines how long each task should take and when it should be completed by.Risk & Defect Reports: A bi-weekly report that tracks all risks that the project has and their current P(L) and S(L) values, therefore tracking which are the highest risks for the project at any given time. This document also identifies any defects that the project has and the team’s plan for how to mitigate those defects.Technical Debt Reports: bi-weekly reports that track any technical debt that the team has and how they plan to mitigate that.Trello board: A team Trello board is used for task management to make sure that tasks are assigned to team members and that they get done on time.Software Cost Estimation: COCOMOII Tool. This tools allows us to perform effort estimation for the project so that we can ensure that we have enough team members and schedule time to complete the project’s requirements.Team Meetings: The team meets once a week to discuss what each team member is working on, and so that team members can give each other feedback.4.1.1 Closed Loop Feedback ControlThe team uses a Slack channel to give immediate feedback to each other on documents, prototypes, or other project work. Team members are distributed across different time zones but the Slack channel allows us to give each other immediate feedback on work being done.4.1.2 ReviewsThere are different kinds of reviews across the project’s lifecycle. Team Reviews: The team meets once a week so that each member can demo what they’ve been working on that week. This allows other team members to give immediate feedback and review their work and also ensures that all work being done by different team members is consistent with all other work. Our shared Google Drive also allows all team members to view other team members’ artifacts and give feedback.Review Boards: Throughout the project’s lifecycle, there are many review boards that provide the stakeholders and instructors to provide any feedback and to determine whether or not the project is ready to move on to the next phase. These review boards include:Valuation Commitment ReviewFoundations Commitment ReviewDevelopment Commitment ReviewTransition Readiness ReviewTop Risk Prototype, Prototype Progress, and Core Capability Drivethrough: These are milestones within the project life cycle that allow for stakeholder feedback of project features and developed prototypes. Users can get hands-on experience with the developed features so that if they would like to suggest any changes or improvements, they can do so while there is still time for the development team to change them.4.2 Methods, Tools and FacilitiesTable 7: Methods, Tools and FacilitiesToolsUsageProviderSlackProvides a messaging tool that allows team members to communicate throughout the week and quickly get answers to questions.Open sourceTrelloA task management online platform that allows the team to manage who is doing what task and when.Open sourceGoogle DriveThe team is utilizing a shared drive which serves as a spot where we can store all team artifacts so that anyone on the team can contribute to them.Open sourceSalesforceThe cloud platform that we are using to build our remote data management system; Includes many built-in libraries for data objects, querying, and front-end widgets that are helping us to build out our platform.Client will pay for the prod licenseEinstein OCR APIAn API within Salesforce that allows for Optical Character Recognition. The team uses this to build the OCR Engine, which is one of the project’s desired capabilities.Open source5. ResourcesThis section outlines the use of the COCOMO-II tool for effort estimation for the project. Due to the fact that we are using SAIV (Schedule As Independent Variable), we used COCOMO for effort estimation but not schedule estimation.Estimated 577a Effort: 8 team members at 12hrs/week for 12weeks.Total estimated effort: 1152 hoursEstimated 577b Effort: 6 team members at 12hrs/week for 12 weeksTotal estimated effort: 864 hoursConditions applied for estimating effort cost for DIAMOND:Project schedule is fixed: 12 weeks in Fall 2020 (Exploration, Valuation, Foundation) and 12 Weeks in Spring 2021 (Development, Transition, Operation).Budget for the Salesforce production license will be supplied by the client.Eight members in 577A and 6 members in 577B.There are 4 modules in this project:Salesforce Database - backend object and table storage in the cloud.Data Management Dashboard - Front-end interactive capabilities for the data management system.Query System - System for building and executing custom SQL queries.OCR Engine - System for Optical Character Recognition from a .pdf or .jpegAll modules use a combination of JavaScript, XML, HTML, and CSS.Modules & Estimated SLOCTable 8: Modules and Estimated SLOCNo.Module NameBrief DescriptionSLOC1Salesforce DBbackend object and table storage in the cloud30002Data Management DashboardFront-end interactive capabilities for the data management system15003Query SystemSystem for building and executing custom SQL queries8004OCR EngineSystem for Optical Character Recognition from a .pdf or .jpeg1000Scale DriversThe values for each of the scale drivers and the rationale for choosing those values is shown below:Table 9: COCOMOII Scale DriversScale DriverValueRationalePRECNominalThe team is familiar with database systems, but not in the cloud and not using the Salesforce NCS. Development within the platform is largely unprecedented for the team members.FLEXLowThe team has been given rigorous requirements as to how data input must be done, and what the table schema needs to be, but implementation details of queries is left up to the team.RESLVHighThe team has made it a priority (due to risk-driven ICSM principles) to reduce risk early and eliminate where possible. Trade studies and prototypes have been created for areas of risk within the architecture and team members feel largely comfortable moving forward into development that the large risks have been mitigated.TEAMVHighTeam members, clients, and stakeholders have been highly attentive, cooperative, and prompt with their assignments and expected contributions.PMATNominalThe team is adhering to guidelines from the ICSM principles, using a set of standard processes that are defined. Processes are suited for this specific project. CMM Level 3 - Defined.Cost Drivers (Module 1)Table 10: COCOMOII Cost Drivers for Module1 Cost DriverValueRationaleRELYNominalThough the data being stored in the system is important to the operation of the K-12 STEM Center, Salesforce provides great support for backups and recovery, so any data losses are easily recoverable.DATANominalThe ratio of database size to SLOC of the project is estimated to be more than 10, but less than 100. Data will be stored for participants, parents, programs, and survey data.DOCUNominalSalesforce documentation for the platform itself is plentiful, and the documentation we are writing during development will cover the life-cycle needs of the system without going overboard.CPLXNominalThis project relies heavily on Data Management Operations (Nominal), User Interface Management (High), and Computational Operations (Nominal). It will support complex database queries, and will work on customizing the Salesforce widget library for the front-end. Nominal computational operations will be done in the processing of the data. RUSELowThis system is not intended to be reused for other projects.TIMENominalThe system will be used when STEM Center staff members are entering new data to the system, or querying current data, but otherwise will be mostly idle, simply storing data objects in the cloud, using expectedly <50% of the available execution time.STORVery HighThe STEM Center has years worth of historical program data that they would like to store in the system, and the size of the database will grow each year as new programs begin and new participants join existing programs.PVOLNominalSalesforce releases a major product update with new features and enhancements 3 times a year (in the Spring, Summer, and Winter). They commit to this schedule, and new changes can be expected at these three milestones each year. Browser updates will typically only be once/yr.ACAPVHighOur project’s analysts and designers communicate well and promptly, are very thorough, and follow project requirements when making design decisions.PCAPVHighThough collectively unfamiliar with Salesforce and its development console at the start of the project, the programmers have gained much experience with the platform through prototyping and are feeling very capable with it as we approach the Development phase.PCONNominalWe have 8 members currently working on the project in 577A and it is estimated that ~5 of those will continue on to 577B. It is likely that 1-2 new members will join the team in 577B.APEXNominalThe experience of the project team with cloud data management systems is low, ~6mos. for most team members, however many have experience with database systems and data management systems in general.PEXPLowThe project team has some experience working with SQL databases, but no experience working with the Salesforce platform before, which is the main platform of this system.LTEXHighThe team will be developing the cloud data management system with XML, CSS, and JavaScript, and many team members have lots of experience with those languages and tools. TOOLNominalOur project will be moderately integrated, both frontend and backend will be integrated in the cloud and basic life-cycle tools and documentation for said tools will be available from the Salesforce NCS.SITELowTeammates are distributed internationally (because of COVID), across 5 different time zones, and often have completely opposite waking hours. We do have a Slack messaging system that allows us to retain sufficient communication, however video conferences are limited because there aren’t many times that everyone can make due to time zone issues.SCEDNominalThe schedule is fixed; 12 weeks in fall semester, 12 weeks in spring semester.Cost Drivers (Module 2)Table 11: COCOMOII Cost Drivers for Module 2Cost DriverValueRationaleRELYLowThe front-end will not cause drastic problems if it is temporarily unavailable as it just provides widgets to access tables.DATANominalThe ratio of database size to SLOC of the project is estimated to be more than 10, but less than 100. Data will be stored for participants, parents, programs, and survey data.DOCUNominalSalesforce documentation for the front-end aspects of the platform itself is plentiful, and the documentation we are writing during development will cover the life-cycle needs of the system without going overboard.CPLXLowThis module relies heavily on User Interface Management (High), and Computational Operations (Low). This module will include high levels of interface management, including customizing the Salesforce widget library.RUSELowThis system is not intended to be reused for other projects.TIMENominalThe system will be used when STEM Center staff members are entering new data to the system, or querying current data, but otherwise will be mostly idle, simply storing data objects in the cloud, using expectedly <50% of the available execution time.STORLowThe front-end module does not require much storage at all.PVOLNominalSalesforce releases a major product update with new features and enhancements 3 times a year (in the Spring, Summer, and Winter). They commit to this schedule, and new changes can be expected at these three milestones each year. Browser updates will typically only be once/yr.ACAPVHighOur project’s analysts and designers communicate well and promptly, are very thorough, and follow project requirements when making design decisions.PCAPVHighThough collectively unfamiliar with Salesforce and its development console at the start of the project, the programmers have gained much experience with the platform through prototyping and are feeling very capable with it as we approach the Development phase. We have one prototyper who has gotten very familiar with front-end capabilities in Salesforce.PCONNominalWe have 8 members currently working on the project in 577A and it is estimated that ~5 of those will continue on to 577B. It is likely that 1-2 new members will join the team in 577B.APEXVHighThe experience of the project team with building front-end user interface systems is very high, and the team feels comfortable building the front-end module.PEXPNominalThe project team has experience building front-end UIs but never within the Salesforce platform.LTEXHighThe team will be developing the front-end with XML, CSS, and JavaScript, and many team members have lots of experience with those languages and tools. TOOLNominalOur project will be moderately integrated, both frontend and backend will be integrated in the cloud and basic life-cycle tools and documentation for said tools will be available from the Salesforce NCS.SITELowTeammates are distributed internationally (because of COVID), across 5 different time zones, and often have completely opposite waking hours. We do have a Slack messaging system that allows us to retain sufficient communication, however video conferences are limited because there aren’t many times that everyone can make due to time zone issues.SCEDNominalThe schedule is fixed; 12 weeks in fall semester, 12 weeks in spring semester.Cost Drivers (Module 3)Table 12: COCOMOII Cost Drivers for Module 3Cost DriverValueRationaleRELYLowThe query system going down would have no effect on the stored data itself, so data loss would not occur if the query system went down temporarily.DATANominalThe ratio of database size to SLOC of the project is estimated to be more than 10, but less than 100. Data will be stored for participants, parents, programs, and survey data.DOCUNominalSalesforce documentation for the platform itself is plentiful, however we will be writing the query system from scratch, so Salesforce documentation will not be as helpful here.CPLXNominalThis module relies heavily on Data Management Operations (Nominal), and Computational Operations (Nominal). It will perform complex database queries. Nominal computational operations will be done in the processing of the data. RUSELowThis system is not intended to be reused for other projects.TIMENominalThe system will be used when STEM Center staff members are entering new data to the system, or querying current data, but otherwise will be mostly be idle, simply storing data objects in the cloud, using expectedly <50% of the available execution time.STORLowThis module is very small and will not require much storage at all.PVOLNominalSalesforce releases a major product update with new features and enhancements 3 times a year (in the Spring, Summer, and Winter). They commit to this schedule, and new changes can be expected at these three milestones each year. Browser updates will typically only be once/yr.ACAPVHighOur project’s analysts and designers communicate well and promptly, are very thorough, and follow project requirements when making design decisions.PCAPVHighThough collectively unfamiliar with Salesforce and its development console at the start of the project, the programmers have gained much experience with the platform through prototyping and are feeling very capable with it as we approach the Development phase.PCONNominalWe have 8 members currently working on the project in 577A and it is estimated that ~5 of those will continue on to 577B. It is likely that 1-2 new members will join the team in 577B.APEXVHighThe experience of the project team with database systems and querying databases is very high.PEXPNominalThe project team has lots of experience working with SQL queries but no experience integrating them in Salesforce.LTEXVHighThe team will be developing the queries using SQL, and many team members have lots of experience with SQL.TOOLNominalOur project will be moderately integrated, both frontend and backend will be integrated in the cloud and basic life-cycle tools and documentation for said tools will be available from the Salesforce NCS.SITELowTeammates are distributed internationally (because of COVID), across 5 different time zones, and often have completely opposite waking hours. We do have a Slack messaging system that allows us to retain sufficient communication, however video conferences are limited because there aren’t many times that everyone can make due to time zone issues.SCEDNominalThe schedule is fixed; 12 weeks in fall semester, 12 weeks in spring semester.Cost Drivers (Module 4)Table 13: COCOMOII Cost Drivers for Module 4Cost DriverValueRationaleRELYLowThis module is not essential to project operation and can be seen as a “would like to have” capability. Therefore, if it were ever temporarily unavailable, there wouldn’t be a large effect on the system.DATANominalThe ratio of database size to SLOC of the project is estimated to be more than 10, but less than 100. Data will be stored for participants, parents, programs, and survey data.DOCUHighThe Einstein OCR API offers lots of documentation and samples of its use, so we have a lot we can reference.CPLXLowThough the API itself performs Computational Operations (High), the developers on our team do not have to build out any of that complex functionality ourselves.RUSELowThis system is not intended to be reused for other projects.TIMENominalThe system will be used when STEM Center staff members are entering new data to the system, or querying current data, but otherwise will be mostly idle, simply storing data objects in the cloud, using expectedly <50% of the available execution time.STORLowThe OCR module will not require much storage at all.PVOLNominalSalesforce releases a major product update with new features and enhancements 3 times a year (in the Spring, Summer, and Winter). They commit to this schedule, and new changes can be expected at these three milestones each year. Browser updates will typically only be once/yr.ACAPVHighOur project’s analysts and designers communicate well and promptly, are very thorough, and follow project requirements when making design decisions.PCAPHighThough collectively unfamiliar with the Einstein OCR API when we began this project, the programmers have gained much experience with the API through prototyping and are feeling more comfortable with it.PCONNominalWe have 8 members currently working on the project in 577A and it is estimated that ~5 of those will continue on to 577B. It is likely that 1-2 new members will join the team in 577B.APEXNominalThe experience of the project team with OCR is low, however we have much more experience using other Vision APIs.PEXPNominalThe project team has some experience working with Computer Vision APIs, but not this Salesforce API in particular, so we are less sure of how it interacts with the Salesforce platform.LTEXHighThe team will be developing the OCR system with XML, CSS, and JavaScript, and many team members have lots of experience with those languages and tools. TOOLNominalOur project will be moderately integrated, both frontend and backend will be integrated in the cloud and basic life-cycle tools and documentation for said tools will be available from the Salesforce NCS.SITELowTeammates are distributed internationally (because of COVID), across 5 different time zones, and often have completely opposite waking hours. We do have a Slack messaging system that allows us to retain sufficient communication, however video conferences are limited because there aren’t many times that everyone can make due to time zone issues.SCEDNominalThe schedule is fixed; 12 weeks in fall semester, 12 weeks in spring semester.COCOMO-II Resource Estimation ResultFigure 1: COCOMOII Resource Estimation Result with Four ModulesAnalysisAssuming:12 hrs/week of effort per person10 of the 12 weeks of the spring semester contribute to the Construction Phase (72% of total)100 hrs/person-month for COCOMO Estimates1 577B team member effort = (10 weeks)(12 hrs/week) = 120 hrs1.67(estimated hrs/person-month COCOMO-II) = (1.67)(100 hrs)(0.72) = 120 hrsOne 577B team member effort = 1.67 CII person-monthsIf we only have 5 team members for 577B:5 * 1.67 = 8.35 CII person-monthsIf we have 6 team members for 577B (the expected scenario):6 * 1.67 = 10.02 CII person-monthsFigure 2: Most Likely Estimated Person-MonthsAs can be seen in our estimation, the most-likely estimate for effort for the Construction piece of our project is 10.0 CII person-months, and as identified above, with 6 team members for 577B (the expected scenario), we will meet that estimate. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download