Concepts: Logical View

To provide a basis for understanding the structure and organization of the design of the system, an architectural view called the Logical View is used in the Analysis & Design workflow. There is only one logical view of the system, which illustrates the key use-case realizations, subsystems, packages and classes that encompass architecturally significant behavior. The logical view is refined…

Read More Read More

Artifact: Implementation Model Document

The Word template can be bought through a template package. Case studies and reports are freely available in the table below. Word Template Case Study Report — Purpose The purpose of the Implementation Model Document is to define the order in which the components and subsystems should be implemented, which builds to create when integrating the system, and how they…

Read More Read More

Guidelines: Requirements – Use Case

Use Case A use-case instance is a sequence of actions a system performs that yields an observable result of value to a particular actor. A use case defines a set of use-case instances. There are several key words in this definition: Use-case instance. The sequence referred to in the definition is really a specific flow of events through the system,…

Read More Read More

Role: Any Role

Roles and Activities > Any Role Any role identified in the Unified Process for EDUcation can, given access privileges, ‘check-in’ and ‘check-out’ any product-related artifact for maintenance in the configuration control system. Any role may also submit change requests and make updates to the change requests for which they are the owner.

Introduction to Test

Introduction Concepts Workflow Activities Artifacts Guidelines Purpose Relation to Other Disciplines Related Book Content The Test discipline acts in many respects as a service provider to the other disciplines. Testing focuses primarily on the evaluation or assessment of product quality realized through a number of core practices: Finding and documenting defects in software quality. Generally advising about perceived software quality.…

Read More Read More

An Educative Process Modeling Tool

Process Modeler ProcessEdit is a tool that enables easy drawing of process models based on the UPEDU process elements. ProcessEdit has been developed at the Software Engineering Lab at the École Polytechnique de Montréal. We are grateful to Mathieu Lavallée, Michael Sokol and Noureddine Kerzazi for their involvement in this project. Please forward any comments to upedu@polymtl.ca To access the…

Read More Read More

Milestone: Initial Operational Capability

Overview > Lifecycle > Construction > Milestone At the Initial Operational Capability Milestone, the product is ready to be handed over to the Transition Team. All functionality has been developed and all alpha testing (if any) has been completed. In addition to the software, a user manual has been developed, and there is a description of the current release. Evaluation…

Read More Read More

Phase: Elaboration

The goal of the elaboration phase is to baseline the architecture of the system to provide a stable basis for the bulk of the design and implementation effort in the construction phase. The architecture evolves out of a consideration of the most significant requirements (those that have a great impact on the architecture of the system) and an assessment of…

Read More Read More

Concepts: Prototypes

Prototypes are used in a directed way to reduce risk. Prototypes can reduce uncertainty surrounding: The business viability of a product being developed The stability or performance of key technology Project commitment or funding: building a small proof-of-concept prototype The understanding of requirements The look and feel of the product, its usability. A prototype can help to build support for…

Read More Read More

Concepts: Use-Case View

To provide a basis for planning the technical contents of iterations, an architectural view called the use-case view is used. There is only one use-case view of the system, which illustrates the use cases and scenarios that encompass architecturally significant behavior, classes, or technical risks. The use-case view is refined and considered initially in each iteration. The use-case view shows…

Read More Read More