1. Operational, Services, Performance, and Functionality (OSPF) Architecture View An Executive-Level Enterprise Depiction 24 February 2009
Bruce J. Brown
Director, Architectures
Advanced Technology Group

2. Why a New View?
Current architecture products are fragmented into different views making an understanding of the enterprise difficult to grasp, especially for executives
Typically overview OV-1 and SV-1 are overly simplistic, while other views too microscopic; hence: ”can’t see the forest for the trees”
Desire to show key components of the enterprise and relate to functionality and performance
View facilitates an understanding how subsequent enhancements impact functionality and performance

3. Operational, Services, Performance & Functionality (OSPF) View Example
(As-Is Baseline)
Selection of Core Objects:
- Supports prime functions
- Supports performance features
- Object in Sequence Diagrams
- Arranged in structured format
Core Diagram
(SV-1, SV-4/5, UML/SysML Structure)
Network & Security
Portal Presentation
Services & Business Process
Functionality
(OV-1,UML Use Case)
Data
Stores
Acronyms &
Abbreviations
IM: Instant Messaging
Mail Access
& Routing
Performance
& Features
(SV-7)
2M User Size
2 sec Resp. Time
Biometric Security
.9999 Availability
Sign On
Search Engine
Sessions
Search
Identity
Mangement
Messaging
Service
Scope (AV-1) IM
Segment 1
Warehouse
Service
[Magic DB]
Segment 2
Records Access
Segment 3
What applications support the service?
How well does it work?
What does it do?
Who are the users?
What specific services/components support this functionality?
What specific services/components support this functionality?
What are the key services & components that make it work?
What part of a larger enterprise, if any, does this view cover?

4. Services & Business Process
Operational, Services, Performance & Functionality (OSPF) View
(To-Be Target)
View makes it easier for executive decision-makers to understand how upgrades/changes impact functionality and performance
Upgrades to baseline traceable to
services & components
Functionality
(OV-1,UML Use Case)
Core Diagram
(SV-1, SV-4/5, UML/SysML Structure)
Services & Business Process
Network & Security
Portal Presentation
Data
Stores
Acronyms &
Abbreviations
IM: Instant Messaging
Video
Mail Access
& Routing
Performance
& Features
(SV-7)
2 sec Resp. Time
2M User Size
Biometric Security
.9999 Availability
Sign On
Search Engine
1 sec Resp Time
Sessions
Search IM
Service
Scope (AV-1)
Identity
Managment
Segment 1
Warehouse
Service
[Magic DB] IM
Segment 2
Cache
Segment 3
Video
Service
Records Access
What applications support the service?
How well does it work?
What does it do?
Who are the users?
What specific services/components support this functionality?
What specific services/components support this functionality?
What are the key services & components that make it work?
What part of a larger enterprise, if any, does this view cover?
= New performance, functionality, services and components

5. Sequence Diagram Example (UML; OV-6c; SV-10c)
How does it work?

6. Insertion of Products into Tool*
Sequence Diagrams
OSPF Custom View
“Wiring” Diagrams
AV Custom Views for
Glossary
Acronyms
Requirements
New AV Views
New AV Views
Process Diagrams
Data Models
Standards
* Sparx Systems “Enterprise Architect”

7. “Proof of the Pudding…”
OSPF Diagrams
Sequence Diagrams
OSPF Diagram
Sequence Diagram
Sequence Diagrams

8. Summary
New high-level enterprise view consisting of summarized performance, functionality, and services/systems related by traceability indicators with change/enhancement markers
Can be harmoniously integrated into existing MODAF/DODAF frameworks & toolsets.
Sequence diagrams enhance “the view”
Additional tailored architecture views may be added to further improve understanding and achieve tighter integration with requirements
Purpose: Reusable products; facilitate communications across the team; improved executive-level understanding of the enterprise
Goal: Higher customer acceptance and usability of architecture products