636-530-7776
Legend: RUP Notation
Workflow > Detail > Artifact

Artifact: Business Operations Plan

The Business Operations Plan describes the how the business is managed and produces its products or services. The plan may represent the current situation or describe a future state.

More detail: Purpose - Audience - Template

Click the icons for definition

Business Strategist
Software Architect
Information Architect
Subject Matter Expert
Project Manager
Requirements Analyst
Stakeholder
Business Concept (from Business Strategy)Business Use Case Model (from Business Strategy)User Research ReportBusiness Operations Plan (from Business Strategy)
Find Actors and Use Cases
Manage Dependencies
Glossary (from Environment)
Use Case Modeling Guidelines
Supplementary SpecificationUse Case (sketch)Requirements AttributesUse Case ModelActor Catalog
Software ArchitectPrioritize Use CasesSoftware Architecture Document (updated)
Requirements Analyst Define System Wide Attributes

Purpose

The Business Operations Plan is a composite artifact that contains:

If this artifact contains the operational vision for the future of the business, then it will also contain a summary of changes required and an action plan to achieve that vision. Particular attention should be paid to the impact of growth on operations and mechanisms that will help the business grow.

Audience

The following roles use the Business Operations Plan:

  • The key stakeholders use it to manage the business and to prepare for organizational changes.
  • The Role: Business Process Analyst and Role: Business Designers use it to create a coherent explanation of the business.
  • The Role: Business Strategists and others use it to find cost-saving and business improvement opportunities.
  • All roles involved in analyzing, designing, and implementing the software use it to understand the business operations and the context in which the application will be used.