In this context, "developing" means creating or updating the document, as well as reconciling a document with the remaining documents to ensure consistency.
Training/learning: Hours spent on training and learning about various tools and languages (e.g., Rational Rose, Microsoft Project, Java, Visual Basic, etc.)
Application research: Hours spent reading and learning about project background, organization, domain, application, etc... (if newcomer on project)
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 meetings: Hours spent in face-to-face meetings with any other team members
Email: Hours spent communicating with other team members via email
Telephone and Other Interactions: Hours spent on team communications via phone, fax, videoconference, etc.
Updates to Operational Concept Description: Hours spent updating the Operational Concept Description document
Updates to System and Software Requirements Definition: Hours spent updating the System and Software Requirements Definition document.
Updates to System and Software Architecture Description: Hours spent updating the System and Software Architecture Description document.
Updates to Life Cycle Plan: Hours spent updating the Life Cycle Plan document.
Updates to Feasibility Rationale Description: Hours spent updating the Feasibility Rationale, e.g., analyzing impacts of changes on schedule, cost,
Updates to Other IOC Document: Hours spent updating the Other IOC Document.
Document Review: Hours spent reading or reviewing document.
Document Inspection: Hours spent on document inspection.
Design Creating or Modification: Hours spent developing or changing the system design, including hours spent developing and updating the System and Software Architecture Description, and the associated model files (e.g., the Rational Rose model) to keep the architecture documentation consistent with the as-built specifications.
Design Review/Inspection: Hours spent reading or reviewing design (includes design meetings and consultations, as well as formal and informal reviews, walkthroughs, and inspections), generating Inspection Reports, ...
Code Generation/Modification: Hours spent actually coding system components
Code Review/Inspection: Hours spent reading code (for any purpose other than isolation of errors) or inspecting other people’s code, generating Inspection Reports, ...
Unit Testing: Hours spent testing individual components of the system (includes writing test drivers, generating regression test package, writing test descriptions, and reporting test results)
Integration Testing: Hours spent writing and executing tests that integrate system components (includes system tests)
Prototyping: Hours spent developing prototypes, e.g., custom coding User-Interface prototypes (including rebaselining the various prototypes)
COTS Assessment: Hours spent assessing various Commerical Of The Shelf (COTS) components for the application
COTS Tailoring: Hours spent tailoring COTS products
COTS Integration: Hours spent integrating COTS products into application including glue code design, development and test
Planning & Control: Hours spent planning, estimating, managing, status reporting, analyzing metrics, adjusting plans, managing or coordinating work, updating the Life Cycle Plan, generating Iteration Plans, generating Iteration Assessment Reports.
Project Review preparation: Hours spent in preparation for internal reviews, Transition Readiness Review, ...
Configuration Management and Quality Assurance: Hours spent performing configuration management and quality assurance functions, including developing Quality Management Plan, Inspection Plan, coordinating tools
Transition Planning, Preparation and Execution: Hours spent developing the transition plan, or executing the transition plan. Including coordinating deliverables with the client, meeting with key personnel for transition strategy and readiness discussions
Training: Hours spent training the users on the application, developing training material
User Documentation: Hours spent developing user documentation, e.g., user's manual, online help
Customer Deliverables: Hours spent coordinating, preparing and packaging customer deliverables (source code files, installation scripts, maintenance package, regression test package, support tools and environment,...)
Test Specification: Hours spent developing the test specification.
Test Case/Procedure Generation: Hours spent generating test case/procedure.
Test Case Review: Hours spent reading or reviewing test case.
Test Case Inspection: Hours spent test case inspection.
Other: Hours spent performing tasks not covered above