Concept for an e-Transit Reference Enterprise Architecture (2004) / Chapter Skim
Currently Skimming:
Pages 37-41
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 37... ...
TOOLS TO SUPPORT e-TRANSIT REFERENCE ENTERPRISE ARCHITECTURE Tools to support the e-transit reference enterprise architecture can be evaluated for planning and performance. Under the planning factor are sub-factors for the underlying technology of the tool, market share and third-party opinions of the tool, the relative stability of the tool as it evolves, outside investments, and functional modules or third-party add-ons.
|
From page 38... ...
concepts. Several of the object-oriented CASE tools were identified and included in the assessment for use in developing the e-transit reference enterprise architecture.
|
From page 39... ...
processes required to provide the information flows and interfaces required. As discussed in Chapter 3, the National ITS Architecture will therefore be used as a source of information for the development of the e-transit reference enterprise architecture, but is not a tool per se.
|
From page 40... ...
products for creating, visualizing, changing, sharing, and managing visual enterprise models and comes the closest to meeting task requirements. It also has the ability to support the evolution from today to the future vision, which is an important requirement for this effort.
|
From page 41... ...
architecture models. Many developers can work on the architecture models simultaneously.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.