![]() |
Telelogic System Architect (steve huntington) | ![]() |
Topic Title: Future State Topic Summary: Would like to hear from people who have created future state within their SA implementation. Created On: 9-Jan-2008 16:03 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We are new to SA, and are trying to figure out the best way to reparsent future state. Would like to know what people are doing and at what level. Future state within the context of systems or at a more elevated planning or strategy level.
Thanks |
|
![]() |
|
![]() |
|
Future state of what? Are you anticipating changes to business process or data or are you considering your application or technical environments?
|
|
![]() |
|
![]() |
|
The current state of an enterprise architecture is named the As-Is view, and is represented by a single encyclopedia. The next future state is the version expected in the next 1-5 years, is named the To-be view, and represented by another encyclopedia (originally started by copying the As-Is encyclopedia and then modified). The final future state is the version expected in the next 6-10 years, is named the Should-Be view and represented by a third encyclopedia.
|
|
![]() |
|
![]() |
|
Doesn't SA 11.0 incorporate a capability to view as-is, to-be and should-be architecture in one encyclopedia?
|
|
![]() |
|
![]() |
|
I believe that functionaility is coming in future release sometime in 2009.
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.