Cycle Life Plan (LCP)
Thai Students Association Website (THSA)
Team #12
Amrit Pal Singh Dhwanit Purohit Niket Ashesh Ishita Gupta Kushboo Bindlish Kunal Jain Wison Lei
Project Manager Prototyping Engineer Requirements Engineer Operational Concept Engineer System Architect Asst. Shaper & UML Modeler IIV & V, SRE
LCP_LCO_F07a_T12_V1.0
Version Date: 10/17/2007
Life Cycle Plan (LCP)
Version no 1.0
10/17/2007
LCP_LCO_F07a_T12_V1.0
ii
Version Date: 10/17/2007
Life Cycle Plan (LCP)
Version no 1.0
Version History
Date 08/20/0 5 Author Kunal Jain Versio n 1.0 Changes made Filled in information in all sections from LCP template in 577a web site Rationale Initial draft for use with LeanMBASE v1.9
LCP_LCO_F07a_T12_V1.0
iii
Version Date: 10/17/2007
Life Cycle Plan (LCP)
Version no 1.0
Table of Contents
Life Cycle Plan (LCP)......................................................................................................................i
....................................................................................................................................................................i
Version History...............................................................................................................................iii Table of Contents............................................................................................................................iv Table of Tables...............................................................................................................................vi Table of Figures.............................................................................................................................vii
A.1. Introduction.........................................................................................................................................................1 A.1.1 Status of the LCP Document.......................................................................................................................1 A.1.2 Assumptions................................................................................................................................................1 A.1.3 References...................................................................................................................................................1 A.2. Milestones and Products.....................................................................................................................................3 A.2.1 Overall Strategy..........................................................................................................................................3 A.2.2 Phases..........................................................................................................................................................4 A.2.3 Project Deliverables....................................................................................................................................4 A.3. Responsibilities...................................................................................................................................................7 A.3.1 Overall Summary........................................................................................................................................7 A.3.2 By Phase / Stage..........................................................................................................................................8 A.4. Approach...........................................................................................................................................................11 A.4.1 Monitoring and Control.............................................................................................................................11 A.4.2 Methods, Tools and Facilities...................................................................................................................13 The following table shows the tools, methods and facilities that are being used to develop the project: ........13 ...........................................................................................................................................................................13 A.5. Resources..........................................................................................................................................................14 B. Platform...............................................................................................................................................................18
LCP_LCO_F07a_T12_V1.0
iv
Version Date: 10/17/2007
Life Cycle Plan (LCP)
Version no 1.0
C.Personnel..............................................................................................................................................................21 D.Project..................................................................................................................................................................23 E.Schedule Compression.........................................................................................................................................23 ..................................................................................................................................................................................24 A.6. Appendix...........................................................................................................................................................28
6.1 Glossary of Terms....................................................................................................................28
LCP_LCO_F07a_T12_V1.0
v
Version Date: 10/17/2007
Life Cycle Plan (LCP)
Version 1.0
Table of Tables
Table 1: Artifact deliverable in Engineering Stage..........................................................................4 Table 2: Artifact deliverable in Production Stage............................................................................6 Table 3: Stakeholder responsibilities during software life cycle.....................................................7 Table 4: Stakeholder responsibilities during each phase.................................................................8 Table 5: Authorized Stakeholder Representatives...........................................................................9
LCP_LCO_F07a_T12_V1.0
vi
Version Date: 10/17/07
Life Cycle Plan (LCP)
Version 1.0
Table of Figures
LCP_LCO_F07a_T12_V1.0
vii
Version Date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
A.1.
Introduction
A.1.1 Status of the LCP Document
The purpose of the Life Cycle Plan (LCP) for the Thai Students Association Website is to monitor and control the progress of the project in order to maximize productivity of people and resource throughout the system's life cycle. The current document is version 1.0. Currently, the contents of the document do not deviate from any of the Win-Win negotiated agreements and does not have any major risks that have to be resolved.
A.1.2 Assumptions
The assumptions are the following: 1. There will not be major requirement changes after Win-Win negotiation agreements. 2. The developer team is not changeable during the semester. 3. The total time for system development is 24 weeks (12 weeks in 577a and 12 weeks in 577b). 4. Team members do not have major time clashes on all delivery dates. 5. Only the administrator will have the rights to allow the students to access the THSA website.
A.1.3 References
Distributed Assessment of Risk Tool (DART) http://greenbay.usc.edu:8080/dart/appManager?event=HOMEPAGE LeanMBASE Version 1.9 Templates for FRD http://greenbay.usc.edu/csci577/fall2007/site/guidelines/LeanMBASE_v1.9_templates_for_FRD. doc Schedules for the CS 577a semester http://greenbay.usc.edu/csci577/fall2007/site/schedule/index.html MS Project Plan Elements: http://greenbay.usc.edu/processelements/pages/introduction.html Fall 2006 Team Websites: Team 3: http://greenbay.usc.edu/csci577/fall2006/projects/team3/
LCP_LCO_F07a_T12_V1.0
1
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
Team 15: http://greenbay.usc.edu/csci577/fall2006/projects/team15/
LCP_LCO_F07a_T12_V1.0
2
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
A.2.
Milestones and Products
A.2.1 Overall Strategy
Overall strategy for developing Thai Students Association Website is schedule as Independent Variable (SAIV). This is done as time is a major factor in this project. The Process Model which the project follows is the "Spiral Model" which is driven by success critical stakeholders. The project can have anyone of the following approaches: Custom COTS- Based Currently we are using the COTS- based approach as the clients requirements are met by the COTS product i.e. DRUPAL. The documentation is done keeping the COTS product in mind. The Process Model will include the 3 key milestones: Life Cycle Objective (LCO) Life Cycle Architecture (LCA) Initial Operational Capability (IOC) We have scheduled to complete and deliver this project in 24 weeks. It is divided into 2 stages: the Inception & Elaboration stage (Engineering Stage) and Construction & Transition (Production Stage) stage. LCO and LCA are done at the end of 577a term and IOC will be done at the end of 577b term. Engineering stage: Inception phase (LCO) o Development of the LCO Package. o End slightly after LCO ARB Review. Elaboration phase (LCA) o Revise and improve artifacts and deliverables (LCA package). o End slightly after LCA ARB Review. Production stage: Construction phase (IOC) o Re-baseline LCA using a Win-Win negotiation. o Testing and Development of software. o End after Transition Readiness Review. Transition phase (IOC) o Deliver software to client site using the Win-Win negotiation. o End after Release Readiness Review.
LCP_LCO_F07a_T12_V1.0
3
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
A.2.2 Phases
The following link provides contains the MS Project Plan. http://greenbay.usc.edu/csci577/fall2007/projects/team12/PR/week5_mpp_F07a_T12.m pp It shows the tasks which are being done in the Inception and the Elaboration Phase. It also lists the tasks which we need to complete throughout the life cycle of the project. The details of tasks which are provided on the MS Project are assumed to be moderate. The level of details and the granularity will increase as we go along the life cycle.
A.2.3 Project Deliverables
.2.3.1 Engineering Stage
Table 1: Artifact deliverable in Engineering Stage
Artifact Inception phase OCD Early Section Prototype IV & V (Evaluation of Early OCD) Wiki Win-Win Report LCO Core IV & V (Evaluation of Initial Prototype) IV & V Problems (AAR Summary to LCO Core Level) LCO Draft LCO-Draft SSAD Team Project Roles IV & V Problems (LCO Draft) Respond to IV & V Evaluation of LC Core AAR for SSRD &
LCP_LCO_F07a_T12_V1.0
Due date 9/24/2007 10/05/2007 10/05/2007 10/8/2007 10/10/2007 10/12/2007 10/15/2007 10/17/2007 10/19/2007 10/19/2007 10/22/2007 10/22/2007 10/22/2007 4
Format .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf
Medium
Softcopy on Team Website Softcopy on Team Website
Softcopy on Team Website Softcopy on Team Website
Softcopy on Team Website
Softcopy on Team Website Softcopy on Team Website Softcopy on Team Website Softcopy on Team Website Softcopy on Team Website Softcopy on Team Website
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
Business case analysis for FRD at LCO Draft LCO ARBs LCO Package QFP (Quality Management Plan- Part I) Configuration Management IV & V (Evaluation of LCO Draft SSAD) Elaboration phase QFP (Evaluation of LCO Package) Respond to V&V Evaluation of LCO Package SRE (Updated Wiki Win-Win Report) IIV & V (LCO Draft) LCA Package QFP (Quality Management Plan- Part II) QFP (Evaluation of LCA Package) SRE (AAR for SSRD and ROI Analysis of FRD at LCA Draft) IIV&V (Evaluation of LCA Draft) LCA ARB Project Archiving Respond to V&V Evaluation of LCA Draft
10/26/2007 10/29/2007 10/29/2007 10/31/2007 10/24/2007
.doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf
Softcopy on Team Website Softcopy on Team Website Softcopy on Team Website
Softcopy on Team Website Softcopy on Team Website
11/05/2007 11/12/2007 11/14/2007 10/22/2007 12/10/2007 11/16/2007 12/17/2007 12/03/2007
.doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf
Softcopy on Team Website
Softcopy on Team Website
Softcopy on Team Website
Softcopy on Team Website Softcopy on Team Website Softcopy on Team Website
Softcopy on Team Website
Softcopy on Team Website
12/03/2007
.doc, .pdf .doc, .pdf .doc, .pdf .doc, .pdf
Softcopy on Team Website
12/12/2007 12/10/2007
Softcopy on Team Website Softcopy on Team Website Softcopy on Team Website
LCP_LCO_F07a_T12_V1.0
5
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
.2.3.2 Production Stage
The schedule for 577b term is not announced yet, the following criteria: due date, format, and medium, will be updated as soon as we find out.
Table 2: Artifact deliverable in Production Stage
Artifact Construction phase Updated LCA Package Iteration Plans Iteration Assessment Report Release Description Quality Management Plan Test Plan and Cases Test Procedure and Results Peer Review Plan Peer Review Reports Transition phase Source Code Load Modules Installation Scripts Software Development Files Client-side deliverables User Manual Training Plan Transition Plan Support Plan Training materials Regression Test Package Tools and Procedures Version Description Document Facilities, Equipment, and Data
Due date TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD
Format TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD
Medium TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD
LCP_LCO_F07a_T12_V1.0
6
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
A.3.
Responsibilities
A.3.1 Overall Summary
Table 3: Stakeholder responsibilities during software life cycle
Role
User (Members of the Thai Student Association)
Inception
Reviewing the prototype of the THSA website and giving their feed back on it. Providing the requirements. Negotiating on the Win-Win conditions. Participating in weekly meetings. Reviewing the LCO package giving his feedback. Noting down the client's requirements. Negotiating on the Win-Win conditions. Developing the LCO. Actively participate in ARB. Developing prototype.
Elaboration
Providing feedback after reviewing prototype of the THSA Website. Match their requirements, if any with the prototype. Evaluate the prototype and match the requirements. Review and give their feedback on the design & prototype. Participate in the ARB. Monitor the progress. Determine risks and making strategies in mitigating them. Getting better understanding of the client's requirements and the architecture. Enhancing the prototype. Providing document and prototype for the LCO ARB. Review the prototype. Provide developers their feedback on the prototype. Giving their opinion on the LCA ARB. Provide some test case.
Construction
Reviewing the website and providing the developers with their feedback. Testing & evaluating the website.
Transition
Testing & checking the website in the operational phase. Providing feedback to the maintainer.
Client (Thai Students Association)
Review the website and check its performance. Provide the admin support. Give feedback to the developers and monitor the progress. Attend the ARB. Start coding the website. Developing the test cases. Ensuring the website is uploaded at the scheduled time.
Assisting the developers in transition to the proposed system and in its installation. Acceptance of the website and checking its reliability and performance. Provide details of the website to the maintainer & administrator. Review the website finally and provide help to user in case needed.
Developer (Team 12)
Maintainer (Thai Students Association)
Checking the LCO and monitoring the project deliverables. Provide feedback to the developers.
Providing feedback on the developed design or prototype. Monitoring the progress and test the product.
Provide development support for the website. Learn how to maintain website.
LCP_LCO_F07a_T12_V1.0
7
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
A.3.2 By Phase / Stage
Table 4: Stakeholder responsibilities during each phase
Team Member / Role
Amrit Pal Singh Project Manger
Inception
Primary Responsibility Risk Analysis, FRD, COTS Assessment, Progress Report Secondary Responsibility LCP, Win-Win Report Primary Responsibility LCP, Develop life cycle process model, UML modeler Secondary Responsibility OCD Primary Responsibility SSRD, Win-Win Report Secondary Responsibility Inspection, OCD Primary Responsibility Design SSAD, Choosing COTS product, UML modeler Secondary Responsibility SSRD Primary Responsibility OCD documentation, Risk Management Secondary Responsibility SSAD
Primary / Secondary Responsibility Elaboration Construction
Primary Responsibility FRD, Progress Report, Risk Management Secondary Responsibility LCP, Win-Win Report Primary Responsibility LCP, Quality Assurance, Design testing plan Secondary Responsibility OCD, inspection Primary Responsibility Win-Win Report, SSRD, FRD Secondary Responsibility Inspection, OCD Primary Responsibility Redefine SSAD, Risk Management, UML modeler, COTS analysis Secondary Responsibility SSRD Primary Responsibility Updating OCD, Check scope of increment Secondary Responsibility SSAD Primary Responsibility Implementation, ROI analysis, COTS assessment Secondary Responsibility Making Test Cases Primary Responsibility Redefine Plans, Plan next stage. Secondary Responsibility Implementing Test Cases Primary Responsibility Review Secondary Responsibility Testing Primary Responsibility Implementation, Testing COTS Secondary Responsibility Integration Primary Responsibility Review Secondary Responsibility Testing
Transition
Primary Responsibility ROI analysis, Deployment Secondary Responsibility Testing
Kunal Jain: UML Modeler & Assistant Shaper
Primary Responsibility Maintenance Support Secondary Responsibility Testing
Niket Ashesh: System Software Requirement Analyst
Primary Responsibility Maintenance Secondary Responsibility Testing Primary Responsibility COTS checking, Development Support Secondary Responsibility Testing Primary Responsibility Maintenance Secondary Responsibility Testing
Kushboo Bindlish : System Architect/ Programmer
Ishita Gupta:
Operational Concept Engineer
LCP_LCO_F07a_T12_V1.0
8
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
Dhwanit Purohit:
Prototyping Manager
Wilson Lie: IIV & V, SRE
Poonchana Thitametakul Customer/ Client
Primary Responsibility Developing initial prototype Secondary Responsibility FRD Primary Responsibility Evaluation of Early OCD, WinWin Report & Prototype. Verify and Validate the various documents. Secondary Responsibility Monitor quality the & progress of project. Primary Responsibility Providing requirements, Win-Win Negotiation, Evaluate Prototype Secondary Responsibility Monitor progress of project
Primary Responsibility Enhancing the prototype Secondary Responsibility FRD Primary Responsibility Evaluation of WinWin Report, Prototype and LCO. Verify and Validate Secondary Responsibility Monitor the quality & progress of project. Primary Responsibility Review LCA document, Evaluate prototype. Secondary Responsibility Monitor project progress.
Primary Responsibility Developing, Review Secondary Responsibility Testing Primary Responsibility Developing, Review Secondary Responsibility Testing
Primary Responsibility Maintenance Support Secondary Responsibility Testing Primary Responsibility Maintenance Support Secondary Responsibility Testing
Primary Responsibility Check the artifacts of 577a. Test the website. Provide feedback. Secondary Responsibility Provide administrative support and test cases.
Primary Responsibility Learn how to support the website and accept the website. Secondary Responsibility Know the various functionalities provided by the website.
Table 5: Authorized Stakeholder Representatives
Stakeholders
Amrit Pal Singh Dhwanit Purohit Niket Ashesh Ishita Gupta Kushboo Bindlish Kunal Jain Wilson Lei
Poonchana Thitametakul
Category
Developer
Organization
University of Southern California
THSA Community members
IV & V Client/ Customer User
University of Southern California Thai Student Association Thai Student Association
LCP_LCO_F07a_T12_V1.0
9
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
TBD
Maintainer
California Science Center
LCP_LCO_F07a_T12_V1.0
10
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
A.4.
Approach
A.4.1 Monitoring and Control
To check if the project is on track and meeting its appropriate quality monitoring and control has to be done for the Thai Student Association Website. Each team member is responsible for keeping the quality of the product being made. The strategies for monitoring and control used in this project are the following: Weekly Progress Report Helps in keeping track of the status of the project. Weekly Effort Report Hours put in by each individual every week. Regular Team Meeting This is held regularly in between the developers after the class to keep track of the plan & issues which are in the project. USC COCOMO Tool The tool helps the team in estimating the person hours. Weekly Client Meeting Reports This report informs all the key stake holders about the various topics discussed in the meeting. IV & V Interaction The team is in constant contact with IV& V. We are getting good amount of support and feedback from our IV&V member. In case of any mistake in document our IV&V informs us about it and we can improve it accordingly. Weekly Microsoft Project Schedule Allocation of resources is done. It helps us plan in advance of the critical issues and also the milestones which the team has achieved. DART Tool Risks are identified. Helps in mitigating them before they occur. This helps us sticking to the deadlines which we have made. Client Interactions Constantly updating the client of the progress of the project in every 2 weeks. This helps the client better understand the requirements and helps him in clearing his doubts.
LCP_LCO_F07a_T12_V1.0
11
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
.4.1.1 Closed Loop Feedback Control
The closed loop feedback control helps to plan more efficiently. Iterative calculations of project schedule and effort can be done through it. A balance of workload is made among the team members. Team members can split the tasks and responsibilities amongst themselves. The responsibilities are distributed according to the skills and preferences of each member. If problems occur they can be efficiently rescheduled and resolved at an early stage.
.4.1.2 Reviews
Reviews are constantly done by the key stakeholders. Through the review process the stake holders are able to check the status of the artifact and its transition into the next phase of the life cycle. Peer review and the quality management review are done to check the quality of the software being made. The Architecture Review Board (ARB) meetings are held at the completion of each phase of the life cycle. The meetings helps the key stakeholders identify the progress made through that phase of life cycle. The Independent Verification and Validation member (IV &V) is monitoring the documents being made like Early OCD, Initial Prototype etc. This helps the team to get another opinion on the document, the good features in it, its errors and the critical concerns.
.4.1.3 Status Reporting
The status reporting of the project is done is following ways: Weekly Progress Report: This is created by the Project Manager along with the LCP. The weekly progress report has the following sections: o Plan Summary- This contains the summary of the effort hours put in by the team. o Progress- The tasks which the team completed and the activities which were taken care off. o Top Risks- Top risks which were faced by the team and the plans which are made to mitigate those risks. o Defects- The number of defects which were made & removed by the team. o Effort Charts- Two charts displaying the cumulative project effort and project progress for that particular week. Project Plan: This contains the plan which the team is going the follow the coming week. It has all the tasks done with their dates and duration in it also showing the milestones achieved. This plan is weekly updated and is on the team website. The link for it is: http://greenbay.usc.edu/csci577/fall2007/projects/team12/ Weekly Effort Report: The effort report contains the number of hours that each individual has put in the project. The link to the report can be found at:
LCP_LCO_F07a_T12_V1.0
12
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
http://greenbay.usc.edu/iCard/authentication/ulogin.php? &SERVICE=CSEiCard&URL=http://greenbay.usc.edu/iCard/pages/student.login.php
A.4.2 Methods, Tools and Facilities
The following table shows the tools, methods and facilities that are being used to develop the project:
Table 6: Tools being used in the project
Tools Microsoft Word 2003 Microsoft Project 2007 Microsoft PowerPoint 2003 Internet Explorer and Mozilla Firefox Twiki Win-Win IBM Rational Software Molder Macromedia Dream Weaver USC COCOMO II DART Tool Adobe Acrobat 6.0
Usage Construct documents for all artifacts such as LCO package, LCA package, and other documentation Create Gantt charts for Progress reports and LCP Create presentation for client meeting and ARB reviews For downloading the course material and medium for communication among stakeholders. Brain storming of the Win- Win conditions and felicitate creation of Win-Win report. Create UML, sequence diagram and other diagrams for SSAD Develop team website. Involve in the create of the system using PHP For making the cost and schedule specifications Projecting the THSA project risks Documentation dissemination.
LCP_LCO_F07a_T12_V1.0
13
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
A.5.
Resources
COCOMO II tool is used the effort estimate for THSA Website project. This is used to ensure that the project is feasible for a team of 7 students (6 development team members + 1 IV&V). This section gives rationale for the values used in the estimation. The following are conditions for cost estimation of THSA Website: 1. Project schedule is 24 weeks, 12 weeks each in 577a and 577b. 2. Development team consists of 7 members. 3. There are 3 modules in the project, which are the following: Module 1: User Interface Module 2: Database Module 3: COTS DRUPAL 4. Since the development is part of the coursework in CS577a there is no cost for development. 5. The Development model is post architecture. Table 7: COCOMOII Scale Driver Scale Driver Value PREC NOMINAL Rationale There are existing social networking sites like Facebook etc which can be referenced. The team does not have experience with development of a social networking site but can reference various sites. The application has to be developed using technologies suggested by the client. Certain constraints are not flexible like the size of the database, schedule etc. 2-3 risks items are critical which need to be mitigated as the maintainers are expected to be nontechnical.
The team conducts regular meetings among itself and with the client for smooth operation of the project.
FLEX
NOMINAL
RESL
NOMINAL
TEAM
HIGH
PMAT
NOMINAL
Development team follows LeanMBASE guideline, which is CMM level 2 maturity level.
LCP_LCO_F07a_T12_V1.0
14
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
Table 8: COCOMOII Cost Driver A. Product
LCP_LCO_F07a_T12_V1.0
15
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
Driver RELY
Value VLo
Module Number Module 1
Rationale The website is a social networking site and if it is down, no financial loss will be incurred. The only effect would be on the communication for a short period of time which can be easily recovered. The D/P will be between 10 and 100. The database is supposed to be for 500 students which will also include JPEG pictures. The program SLOC to store an extract the data will also be substantial. Thus, the ratio is expected to be between 10 and 100. Excessive documentation is required for each lifecycle for smooth development of the project. The work of each cycle would be dependent on the documentation done for the previous cycle as there are 7 members in the team and documentation allows easy reference. The product complexity is very low. The control operations are very low as the coding will be done using simple scripts, data management operations will be low since there will be moderately complex DB queries and User interface management operations will be low due to use of simple graphic GUI builders. The weighted average results in Low. The user interface designed may be reused in later projects. The database of the system should be reliable to some extent as it is the information fed by the students. The loss of information can be recovered but the leak of information can result in disclosure of some important student information The D/P will be between 10 and 100. The database is supposed to be for 500 students which will also include JPEG pictures. The program SLOC to store an extract the data will also be substantial. Thus, the ratio is expected to be between 10 and 100. Excessive documentation is required for each lifecycle for smooth development of the project. The work of each cycle would be dependent on the documentation done for the previous cycle as there are 7 members in the team and documentation allows easy reference.
DATA
Nom
Module 1
DOCU1
VHi
Module 1
CPLX
Lo
Module 1
RUSE RELY
Nom Lo
Module 1 Module 2
DATA
Nom
Module 2
DOCU2
VHi
Module 2
1 2
This driver is in a different order in the questionnaire than in the driver table (which is where it is positioned).
LCP_LCO_F07a_T12_V1.0
16
Version date: 10/17/07
Life Cycle Plan (LCP)
Version no 1.0
CPLX
Lo
Module 2
The product complexity is very low. The control operations are very low as the coding will be done using simple scripts, data management operations will be low since there will be moderately complex DB queries and User interface management operations will be low due to use of simple graphic GUI bui...