Concept for an e-Transit Reference Enterprise Architecture (2004) / Chapter Skim
Currently Skimming:
Pages 5-12
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 5... ...
5CHAPTER 2 SUMMARY OF SYSTEMS ENGINEERING AND ENTERPRISE ARCHITECTURE CONCEPTS This chapter explains the essential relationship between systems engineering procedures, or disciplines, and how they relate to and support the concept of an e-transit reference enterprise architecture. General guidelines for the development of the e-transit reference enterprise architecture and its use by a typical transit agency once it is developed will be explored.
|
From page 6... ...
tive of the planner -- which captures what is important to the enterprise; the context in which the enterprise operates; its mission, goals, and objectives and how and when the enterprise meets them; and its important stakeholders -- to Row 5's detailed representations and descriptions of the data, technologies, and software applications needed for implementing and operating the functions and processes of the business. Each successive row provides more details needed to implement the requirements and constraints from the rows above.
|
From page 7... ...
zation has the characteristics of a good enterprise architecture and that the enterprise architecture is useful for understanding the enterprise and analyzing alternative responses to business changes and emerging technology. The reference architecture will address techniques such as knowledge management, business (re)
|
From page 8... ...
plications and poorly documented processes. The e-transit components of the future enterprise architecture may have substantial impact on the organization's ability to both remain competitive and change.
|
From page 9... ...
• Processes define data (i.e., operational, administrative, engineering, and other)
|
From page 10... ...
(e.g., multiple local transit agencies, trains, ITS, traffic networks, and information providers) using computerized procurement, maintenance, asset management, and delivery systems to provide mobility management to customers.17 The steps found in the overall systems engineering process are as follows: 1.
|
From page 11... ...
• Documenting the relationships between established systems with appropriate metrics, • Describing the linkages between modeled systems, • Documenting established data and process flows, • Modeling established data and process flows, and • Following specialty and traditional engineering procedures for transit and IT that support the goal of the enterprise architecture and its use for communications and planning. Another element that can characterize a good enterprise architecture is the amount of systems engineering effort that is expended on the current, near-term, and future architectures, as shown in Figure 2-8.
|
From page 12... ...
showing the linkage of those systems, and modeling established data and process flows. The key to this process is predicting what will probably be useful and what will probably sit on the shelf unused.
|
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.