November 21st, 2008 chris
The Test Summary Report summarizes the results of the testing activities and provides an evaluation based on these results.
It is composed of the following 8 sections:
- Test summary report identifier
- Summary
- Variance
- Comprehensive assessment
- Summary of results
- Evaluation
- Summary of activities
- Approvals
Posted in Software Testing
November 21st, 2008 chris
The Test Incident Report documents any event observed during testing that requires further investigation.
It is composed of the following 4 sections:
- Test incident report identifier
- Summary
- Incident description
- Impact
Posted in Software Testing
November 21st, 2008 chris
The Test Log provides a chronological record about relevant details observed during the test execution.
It is composed of the following 3 sections:
- Test log identifier
- Description
- Activity and event entries
Posted in Software Testing
November 21st, 2008 chris
The Test Item Transmittal Report specifies the test items being provided for testing.
It is composed of the following 5 sections:
- Transmittal report identifier
- Transmitted items
- Location
- Status
- Approvals
Posted in Software Testing
November 21st, 2008 chris
The Test Procedure Specification specifies the steps for executing a test case and the process for determining whether the software passed or failed the test.
It is composed of the following 4 sections:
- Test procedure specification identifier
- Purpose
- Special requirements
- Procedure steps
Posted in Software Testing
November 21st, 2008 chris
The test case specification specifies in detail each test case listed in the test design specification.
It is composed of the following 7 sections:
- Test case specification identifier
- Test items
- Input specifications
- Output specifications
- Environmental needs
- Special procedural requirements
- Intercase dependencies
Posted in Software Testing
November 21st, 2008 chris
The Test Design Specification identifies a set of features to be tested and describes a group of test cases that will adequately test those features.
It is composed of the following 5 sections:
- Test design specification identifier
- Features to be tested
- Approach refinements
- Test identification
- Feature pass/fail criteria
Posted in Software Testing
November 13th, 2008 chris
The following are the 44 processes of Project Management:
- Develop Project Charter
- Develop Preliminary Project Scope Statement
- Develop Project Management Plan
- Scope Planning
- Scope Definition
- Create WBS
- Activity Definition
- Activity Sequencing
- Activity Resource Estimating
- Activity Duration Estimating
- Schedule Development
- Cost Estimating
- Cost Budgeting
- Quality Planning
- Human Resource Planning
- Communication Planning
- Risk Management Planning
- Risk Identification
- Qualitative Risk Analysis
- Quantitive Risk Analysis
- Risk Response Planning
- Plan Purchases and Acquisitions
- Plan Contracting
- Direct and Manage Project Execution
- Perform Quality Assurance
- Acquire Project Team
- Develop Project Team
- Information Distribution
- Request Seller Responses
- Select Sellers
- Monitor and Control Project Work
- Integrated Change Control
- Scope Verification
- Scope Control
- Schedule Control
- Cost Control
- Perform Quality Control
- Manage Project Team
- Performance Reporting
- Manage Stakeholders
- Risk Monitoring and Control
- Contract Administration
- Close Project
- Contract Closure
Posted in Project Management
November 13th, 2008 chris
Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Project scope management is primarily concerned with defining and controlling what is and is not included in the project.
The scope project management processes include:
- Scope Planning - creating a project scope management plan that documents how the project scope will be defined, verified, controlled, and how the work breakdown structure (WBS) will be created and defined.
- Scope Definition - developing a detailed project scope statement as the basis for future project decisions.
- Create WBS - subdividing the major project deliverables and project work into smaller, more manageable components.
- Scope Verification - formalizing acceptance of the completed project deliverables.
- Scope Control - controlling changes to the project scope.
Posted in Project Management
November 13th, 2008 chris
The Project Integration Management Knowledge Area includes the processes and activities needed to identify, define, combine, unify, and coordinate the various processes and project management activities within the Project Management Process Groups. In the project management context, integration includes characteristics of unification, consolidation, articulation, and integrative actions that are crucial to project completion, successfully meeting customer and other stakeholder requirements, and managing expectations. Integration, in the context of managing a project, is making choices about where to concentrate resources and effort on any given day, anticipating potential issues, dealing with these issues before they become critical, and coordinating work for the overall project good. The integration effort also involves making trade-offs among competing objectives and alternatives. The project management processes are usually presented as discrete components with well-defined interfaces while, in practice, they overlap and interact in ways that cannot be completely detailed in theory.
The need for integration in project management becomes evident in situations where individual processes interact. For example, a cost estimate neeed for a contingency plan involves integration of the planning processes described in greater detail in the Project Cost Management processes, Project Time Management processes, and Project Risk Management processes. When additional risks associated with various staffing alternatives are identified, then one or more of those processes must be revisited. The project deliverables also need to be integrated with ongoing operations of either the performing organization or the customer’s organization, or with the long-term strategic planning that takes future problems and opportunities into consideration.
Integration is primarily concerned with effectively integrating the processes among the Project Management Process Groups that are required to accomplish project objectives within an organization’s defined procedures.
The integrative project management processes include:
- Develop Project Charter - developing the project charter that formally authorizes a project or a project phase.
- Develop Preliminary Project Scope Statement - developing the preliminary project scope statement that provides a high-level scope narrative.
- Develop Project Management Plan - documenting the actions necessary to define, prepare, integrate, and coordinate all subsidiary plans into a project management plan.
- Direct and Manage Project Execution - executing the work defined in the project management plan to achieve the project’s requirements defined in the project scope statement.
- Monitor and Control Project Work - monitoring and controlling the processes used to initiate, plan, execute, and close a project to meet the performance objectives defined in the project management plan.
- Integrated Change Control - reviewing all change requests, approving changes, and controlling changes to the deliverables and organizational process assets.
- Close Project - finalizing all activities across all of the Project MAnagement Groups to formally close the project or a project phase.
Posted in Project Management