Sitemap – Roles and Activities

 Report on Configuration Status  Write CM Plan  Confirm Duplicate or Reject…  Review Change Request  Develop Iteration Plan  Develop Measurement Plan  Plan Phases and Iterations  Schedule and Assign Work  Review Requirements  Review Code  Review the Architecture & Design  Project Planning Review  Create Workspaces  Make Changes  Submit Change Request  Update Change Request

Sitemap – Disciplines

 Introduction  Concepts    Requirements  Workflow    Understand the problem    Define the system    Review  Activity Overview  Artifact Overview  Guidelines Overview    Actor    Use-Case    Use-Case Diagram    Use-Case Model    User Interface (General)  Introduction  Concepts    Analysis Mechanisms    Implementation View    Logical View    Software Architecture    Use-Case View  Workflow    Define the Architecture    Grow the Design    Review Architecture & Design  Activity Overview  Artifact Overview  Guidelines Overview    Analysis Class    Design Class    Design…

Read More Read More

The Search Engine

When the Search button is enabled, it indicates that the database has been loaded. Enter your request—see entering a search request—in the Enter query: box. You may have to click in the box first before the cursor appears, and then click the Search button. Upon terminating the search, all resulting documents are listed in the Results box. If no matching…

Read More Read More

Report: Use-Case Model Survey

This report describes the use-case model comprehensively, in terms of how the model is structured into packages and what use cases and actors there are in the model. If you are using packages, the document shows the model structure hierarchically. The report can be used to describe the entire use-case model at different stages: During inception, such as when you…

Read More Read More

Checkpoints: Design Model

Artifacts > Analysis & Design Artifact Set > Design Model > Checkpoints Topics General The objectives of the model are clearly stated and visible. The model is at an appropriate level of detail given the model objectives. The model’s use of modeling constructs is appropriate to the problem at hand. The model is as simple as possible while still achieving…

Read More Read More

Best Practice: Continuously Verify Quality

Software problems are 100 to 1000 times more costly to find and repair after deployment. Verifying and managing quality throughout the project’s lifecycle is essential to achieving the right objectives at the right time. Topics What Do We Mean by Quality Verification Throughout the Lifecycle? It’s important that the quality of all artifacts be assessed at several points in the…

Read More Read More

Best Practice: Manage Change

Managing change is more than just checking-in and checking-out files. It includes management of workspaces, parallel development, integration, and builds. A key challenge when you’re developing software-intensive systems is that you must cope with multiple developers, organized into different teams, possibly at different sites, working together on multiple iterations, releases, products, and platforms. In the absence of disciplined control, the…

Read More Read More

Artifact: Test Class

Artifacts > Test Artifact Set > Test Class The purpose of the test class is to identify the test-specific functionality to facilitate or automate tests. This test-specific functionality should be included in the design model. There are two main types of test-specific classes in a design model: Test classes that are “stubs” for design classes that you need to simulate…

Read More Read More