Operational, Services, Performance, and Functionality (OSPF) Architecture View An Executive-Level...
-
Upload
timothy-romero -
Category
Documents
-
view
213 -
download
0
Transcript of Operational, Services, Performance, and Functionality (OSPF) Architecture View An Executive-Level...
Operational, Services, Performance, and Functionality
(OSPF) Architecture View
An Executive-Level Enterprise Depiction
24 February 2009Bruce J. Brown
Director, ArchitecturesAdvanced 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)
Performance & Features(SV-7)
• 2M User Size• 2 sec Resp. Time• Biometric Security• .9999 Availability
Functionality(OV-1,UML Use Case)
Search
IM
Records Access
Acronyms & Abbreviations
IM: Instant Messaging
Scope (AV-1)
Segment 1
Segment 2
Segment 3
Core Diagram (SV-1, SV-4/5, UML/SysML Structure)
DataStores
Services & Business Process
Network & Security
Portal Presentation
Mail Access& Routing
Search Engine
MessagingService
WarehouseService
[Magic DB]
Sign On
Sessions
How well
does it work?
What does it do?
Who are the users?
What are the key services &
components that make it work?
What specific services/components
support this functionality?
What specific services/components
support this functionality?
IdentityMangement
What applications support the service?
What part of a larger enterprise, if any, does this view
cover?
Selection of Core Objects:- Supports prime functions- Supports performance features- Object in Sequence Diagrams- Arranged in structured format
Performance & Features(SV-7)
• 2 sec Resp. Time• 2M User Size• Biometric Security• .9999 Availability
Functionality(OV-1,UML Use Case)
Operational, Services, Performance & Functionality (OSPF) View (To-Be Target)
Search
IM
Records Access
Scope (AV-1)
Segment 1
Segment 2
Segment 3
Core Diagram (SV-1, SV-4/5, UML/SysML Structure)
DataStores
Services & Business Process
Network & Security
Portal Presentation
Mail Access& Routing
Search Engine
IMService
WarehouseService
[Magic DB]
Sign On
Sessions
How well
does it work?
What does it do?
Who are the users?
What are the key services &
components that make it work?
What specific services/components
support this functionality?
What specific services/components
support this functionality?
IdentityManagment
VideoService
Video
• 1 sec Resp Time
= New performance, functionality, services and components
Cache
Upgrades to baseline
traceable toservices &
components
What part of a larger enterprise, if any, does this view
cover?
What applications support the service?
View makes it easier for executive decision-makers to understand how upgrades/changes impact functionality and performance
Acronyms & Abbreviations
IM: Instant Messaging
5
Sequence Diagram Example (UML; OV-6c; SV-10c)
How does it work?
6
Insertion of Products into Tool*
OSPF Custom
View
Sequence Diagrams
Standards
New AV Views
Data ModelsNew AV Views
AV Custom Views for
• Glossary• Acronyms• Requirements
“Wiring” Diagrams
Process Diagrams
* Sparx Systems “Enterprise Architect”
7
“Proof of the Pudding…”
Sequence Diagrams
OSPF Diagrams
Sequence Diagrams
Sequence Diagram
OSPF Diagram
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