Responsibilities Responsibilities by Phase Table : Stakeholder's responsibilities Name: Vaibhav Mathur Role: Project Manager Exploration Schedule Meetings, Assign Tasks Valuation Plan Project Meeting, Manage Client Interaction, record Project Progress Foundations Coordinating Meetings with team members and clients. Development- Construction Iteration Track project development progress, Manage client interaction and satisfaction. Development- Transition Iteration Launch final system developed, Manage client interaction and satisfaction, Deliver final project artifacts. Name: Arijit Dey Role: Requirements Engineer/Builder Exploration Understanding Requirements, Life Cycle Planning Valuation Update Life Cycle Plan, Identify Milestones, Identify the features to be implemented Foundations Maintaining the Life Cycle Plan and keeping it updated. Development- Construction Iteration Check whether requirements are properly implemented; Implement the main functions of the system, maintaining Project Website. Development- Transition Iteration System deployment, Deliver final project artifacts. Name: Divya Nalam Role: Operational Concept Engineer/ System Architect Exploration Building the Operational Concept Design Report. Valuation Establishing New Operational Concept and Identify the alternative. Foundations Implement necessary changes to the OCD and Identify the operational concepts to be developed. Development- Construction Iteration Identify Objectives, constraints & priorities, Explore alternatives, Update OCD. Development- Transition Iteration Tailor components, Define the technology dependent architecture, Assess System Architecture.
Skills Table 2: Stakeholder’s Skills Team members Role Skills Vaibhav Mathur Project Manager Life Cycle Planner Current- ASP.Net, C#, Javascript Arijit Dey Requirements Engineer Prototyper Current- JAVA, Oracle 10g, Visual Basic, HTML, UML. Required- C#, MySQL Shreyas Devaraj Life Cycle Planner Project Manager Current- JAVA, MySQL, JavaScript 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 System Architect Current-C/C++, Python Required- ASP.Net, C# Rakesh Mathur Validation and Verification of COTS Interoperability Tester Current- ASP.Net, C#, JavaScript Note: - None of the team members are planning to continue to take up CSCI 577B. SKILLS REQUIRED FOR TEAM MEMBERS IN CSCI 577B C# ASP.NET DB2 UML BUGZILLA WINBOOK ROLES REQUIRED FOR TEAM MEMBERS IN CSCI 577B Project Manager Life cycle planner Builder Operational Concept Engineer Quality Focal Point IIV & V Tester
Table 8: COCOMOII Cost Drivers of Module - 3 - Investigator Module Cost Driver Value Rationale RELY NOMINAL If the system fails, it will cause inconvenience to the references and background investigators. But the system can be recovered within certain period of time. DATA LOW The ratio of bytes in the testing database to SLOC in the program is approximately less than 1000 because the database will store all information of candidate’s reference, references’ response which contains lot of data and candidates assigned to investigators. DOCU NOMINAL Because the development process follows ICSM, the document for life-cycle needs is normal. CPLX HIGH Few modules like authentication using LDAP, implementing manager module, investigator module requires complex programming. RUSE NOMINAL The system is used by every department of the background verification organization and also used by the references. TIME HIGH The percentage of available execution time expected to be used by the system and subsystem consuming the execution time resource is about 70% because this system is performing the database operation whenever any process is executed. STOR NOMINAL The percentage of available storage expected to be used by the system and subsystem is about 70% because the most of the candidates’ data is stored in the database. And this is used in every database operation. PVOL LOW Major changes of the platform, i.e. ASP.net, DB2 and web browsers are approximately every year. ACAP HIGH The analysts have good ability to analyze, design and communicate among others. PCAP HIGH Programmers are capable, efficient and thorough. Although some of the team members lack knowledge about ASP.net and DB2. PCON LOW Our team has 6 members and most of them do not plan to continue in CSCI577B. APEX NOMINAL The average experience of the team members for this online application is about one year. LTEX LOW The development team plans to develop this web-based application with ASP.net, C# and DB2 language to query information from the database. The tools for programming are Microsoft Visual Studio. Therefore, the language and tool experience is low because only a few team members have at least one year experience with these languages and tools and rest are trying to learn. PLEX LOW Most of the team members are inexperienced with ASP.net
1 Email Generation Automated Email generation to references HIGH 3 2 Reference Letter Reference Letter Completion HIGH 3 3 Review Reference Review HIGH 3 6.1.3 Capabilities not to be tested Almost all the capabilities of our system need to be tested. There does not exist any such capability which need not be tested.