These two major leading sources are illustrated in Exhibit 15.9.
Architecture Conceptualization Process. After the organization??™s architectural concepts are in
place, they become a part of the enterprise technological dictionary. This language can be reused
for future projects and business initiatives. But as of now, the mission is to employ these concepts
to provide a business or technological solution. Thus, the architecture conceptualization
process continues through whiteboard strategy sessions, during which modelers, analysts, architects,
developers, and managers are gathered to carve out an architectural direction. The consensus
would set the future technological environment road map and recommend supporting software
assets. This decision process is typically centered on two major action items:
1. Recommend new services and a supporting technological environment based on the conceptual
architecture that has been previously instituted. This process is typically pursued
Architectural
Concepts
Service-Oriented
Logical Design Artifacts
Existing
Technological
Environment
Imperatives
???Yield??™ ???Yield??™
EXHIBIT 15.9 INFLUENCES ON ARCHITECTURAL CONCEPTS
Conceptual Architecture Layers 319
Architectural
Concepts
Service-Oriented
Logical Design
Artifacts
Existing
Technological
Environment
Imperatives
???Yield??™ ???Yield??™
Utilize Existing
Technological
Assets
???Yield??™
Devise New
Technological
Environment
???Yield??™
EXHIBIT 15.
Pages:
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551