Turn on more accessible mode
Skip to main content
Turn off more accessible mode
Wiki
>
OpenUP (with RACI and Entry_Exit criteria)
Sign In
|
OpenUP (with RACI and Entry_Exit criteria)
This Site
Home
OpenUP (with RACI and Entry_Exit criteria)
>
Wiki Pages
>
Guidance
Guidance
History
|
Incoming Links
Quick Launch
View All Site Content
Contents
Workflow Diagram
Work Breakdown
Activities
Roles
WorkProducts
Guidance
Disciplines
Categories
Recent Changes
WorkProduct - Risk List
WorkProduct - Supporting Requirements Specification
WorkProduct - Test Case
WorkProduct - Test Log
WorkProduct - Test Script
View All Pages
Guidance List
Guidance
Abstract Away Complexity
Actor
Agile Estimation
Analyze the Design
Architectural Mechanism
Architectural View
Architecturally Significant Requirements
Architecture Notebook
Assign Changes to an Iteration
Balance competing priorities to maximize stakeholder value
Business Pattern
Change Requests
Change Set
Coding Standard
Collaborate to align interests and share understanding
Component
Conduct Project Retrospective
Continuous Integration
Core Principles
Daily Meetings
Deploying the Solution
Design
Designing Visually
Detail Use Cases and Scenarios
Determine Architecturally Significant Requirements
Develop the Architecture
Developer Testing
Effective Requirement Reviews
Elaboration Phase
Entity-Control-Boundary Pattern
Evolution of the Use-Case Model
Evolve the Design
Evolve to continuously obtain feedback and improve
Executable Architecture
Find and Outline Actors and Use Cases
Focus on the architecture early to minimize risks and organize development
Implementation
Iteration
Iteration Assessment
Iteration Burndown
Iteration Lifecycle
Iteration Plan
Iteration Planning
Layering
Maintaining Automated Test Suite
Managing Risks
Managing Work Items
Manual Test Script
Metrics
Micro-Increments
Outline the Architecture
Pattern
Phase Milestones
Prioritizing Work Items
Programming Automated Tests
Project Burndown
Project Lifecycle
Project Plan
Promoting Changes
Qualities of Good Requirements
Refactoring
Requirement Attributes
Requirement Pitfalls
Requirements
Requirements Gathering Techniques
Retrospective
Risk
Risk List
Self Organize Work Assignments
Software Architecture
Software Reuse
Staffing a Project
Submitting Change Requests
Supporting Requirements
Supporting Requirements Specification
Test Case
Test Script
Test Suite
Test-first Design
Traceability
Transforming design into implementation
Types of Test
Use Case
Use Case Formats
Use-Case Model
Use-Case Specification
Use-Cases Realizations
Vision
Visual Modeling
Work Items List
Workspace
Writing Good Requirements
Last modified at 2/4/2008 4:51 AM by Administrator