Education Blog

Concepts: Acceptance Testing

Acceptance testing is the final test action prior to deploying the software. The goal of acceptance testing is to verify that the software is ready and can be used by the end-users to perform those functions and tasks the software was built to do. There are three common strategies for implementing an acceptance test. They are: Formal acceptance Informal acceptance…

Read More Read More

Activity: Plan Phases and Iterations

Purpose To estimate the magnitude of work required to deliver the project To select the optimal schedule that satisfies project constraints During the Inception phase, you should prepare estimates for the work proposed in the project (for a general discussion of software project estimation see [BOE81], [PUT92], and [MCO96]). Software project estimation is based on some complex mathematics, so detailed…

Read More Read More

Best Practice: Develop Iteratively

Best Practice: Develop Iteratively To mitigate risks, develop incrementally in an iterative fashion. Each iteration results in an executable release. Topics What is Iterative Development? A project using iterative development has a lifecycle consisting of several iterations. An iteration incorporates a loosely sequential set of activities in business modeling, requirements, analysis and design, implementation, test, and deployment, in various proportions…

Read More Read More

Activity: Design Test

Purpose To identify and describe the test conditions to be used for testing To identify the specific data necessary for testing To identify the expected results of test For each requirement for test: Analyze application workflows The purpose of this step is to identify and describe the actions and / or steps of the actor when interacting with the system.…

Read More Read More

Phase: Transition

The focus of the Transition Phase is to ensure that software is available for its end users. The Transition Phase can span several iterations, and includes testing the product in preparation for release, and making minor adjustments based on user feedback. At this point in the lifecycle, user feedback should focus mainly on fine tuning the product, configuring, installing and…

Read More Read More

Concepts: Measuring Quality

Measuring Quality Measuring Product Quality Measuring Process Quality The measurement of Quality, whether Product or Process, requires the collection and analysis of information, usually stated in terms of measurements and metrics. Measurements are made primarily to gain control of a project, and therefore be able to manage it. They are also used to evaluate how close or far we are…

Read More Read More

Best Practice: Manage Requirements

Best Practice: Manage Requirements What is Requirements Management? How is Development Driven by Use Cases? Requirements management is a systematic approach to finding, documenting, organizing, and tracking a system’s changing requirements. We define a requirement as “a condition or capability to which the system must conform”. We formally define requirements management as a systematic approach to both: eliciting, organizing, and…

Read More Read More

Introduction to Configuration & Change Management

Introduction Concepts Workflow Activities Artifacts Guidelines Introduction Purpose Relation to Other Disciplines Related Book Content To paraphrase the Software Engineering Institute’s Capability Maturity Model (SEI CMM) ‘Configuration and Change Management controls change to, and maintains the integrity of, a project’s artifacts’. Configuration and Change Control Management (CM and CCM) involves: identifying configuration items, restricting changes to those items, auditing changes…

Read More Read More

Concepts: Software Integration

The term “integration” refers to a software development activity in which separate software components are combined into a whole. Integration is done at several levels and stages of the implementation: Integrating the work of a team working in the same implementation subsystem before releasing the subsystem to system integrators. Integrating subsystems into a complete system. The Unified Process for EDUcation…

Read More Read More

Workflow Detail: Understand Stakeholder Needs

Purpose How to Staff Work Guidelines   The purpose of this workflow detail is to collect and elicit information from the stakeholders of the project in order to understand what their needs really are. The collected stakeholder requests can be regarded as a “wish list” that will be used as primary input to defining the high-level features of our system,…

Read More Read More