Control and Monitoring: Hours spent planning, estimating, managing, status reporting, adjusting plans, managing or coordinating work
Client Interaction: Hours spent interacting with client during meetings, or using other forms of communication (e.g., email, phone, etc...) to understand and define the application, evaluate the various prototypes, etc...
Team Interaction: Hours spent in face-to-face meetings with any other team members
Project Web Site: Hours spent preparing and maintaining the project web site and posting deliverables on the web site
Architecture Review Board: Hours spent in preparation for the Architecture Review Board and the actual review time.
Installation and Administration: Hours spent preparing software and equipment for developing the prototype or software system. Include time spent in administrative matters such as reservations for conference rooms and setting up meeting times.
Configuration Management: Hours spent on product element identification, configuration change management, project library management and configuration status management.
Custom Toolsmithing: Hours spent developing custom tools for the project.
COTS Initial Filtering (Assessment): Hours spent reading and learning about organization, domain, application, etc. and evaluating and selecting various Commerical Of The Shelf (COTS) components for the application
"Developing" means creating or updating the document, as part of the iterative cycle as well as ensuring consistency between the various documents.
Prototyping for Requirements: Hours spent building the prototype for requirements
Modeling for Operational Concept Description: Hours spent building the Operational Conceptual model
Documenting of Operational Concept Description: Hours spent creating or updating the Operational Concept Description document
Modeling for System and Software Requirements Definition: Hours spent building System and Software Requirements model
Documenting System and Software Requirements Definition: Hours spent creating or updating the System and Software Requirements Definition document.
Documenting of System and Software Architecture Description: Hours spent creating or updating the System and Software Architecture Description document, and creating or updating the various model files (e.g., the Rational Rose model to keep it in sync with the rest of the documentation)
COTS Final Selection (Evaluation): Hours spent finally evaluating and selecting of the COTS products and establishing a standard version for the COTS product to be used.
COTS Tailoring: Hours spent in tailoring the finally selected COTS products to the application.
COTS Glue Code Development: Hours spent developing, and testing glue code integrating the COTS products and the application
Feasibility Rationale Description: Hours spent creating or updating the Feasibility Rationale, e.g., analyzing several alternative implementations and/or comparing their impact on schedule, cost and ease of operation
Test Planning: Hours spent developing the system test plan to prescribe the scope, approach, resource and schedule of test activities
Inspections and Peer Reviews: Hours spent doing inspections and peer review on documents and code