Click for next page ( 22


The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement



Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 21
21 with permission to contribute and work together in a loosely file formats, display of graphics, and application of several connected community. The wiki format provides a means of html and Java script functions. All changes are recorded and directly soliciting new and updated guidance from registered ascribed to the user who made the change providing robust users on their questions, recommendations, approaches, and configuration management functionality. practices. The format enables "trusted" writers to contribute The research team populated the site with the TEAP Frame- and share information in a transparent environment on best work Guidance, tools, and a Transit EA/EAP Guidebook. The practices and new methods. Also, using a wiki to store the site lays out the Framework Guidance in a systematic way with project's findings allows for ongoing updating and expanding sections targeting different audiences, from executives and of the content. senior managers to program managers and technical practi- tioners (see Table 4). Target Audience and Wiki Sections There are several open source wiki applications and numer- TEAP Guidebook ous information service providers (ISP) that provide a wiki Guidebook Purpose and Scope "in the cloud." The research team, in order to focus on the content rather than the technology, elected to use an ISP. The The Transit Enterprise Architecture Planning (TEAP) site (http://tcrp-teap.pbworks.com) allows cutting and past- Guidebook differs from the TEAP Framework in that the ing from word processing documents, uploading of different Framework describes general benefits, best practices, and Table 4. TEAP Framework wiki sections. TEAP Framework Wiki Description Audience Guidance for Transit A high-level description of the TEAP Transit Managers Framework, including the purpose and benefits executive and associated with each Framework element and senior their interrelationships. In addition, the managers guidance includes a checklist that enumerates the roles and responsibilities of transit managers with respect to each of the elements. This section includes a self-contained, downloadable version which can be printed and read in hard copy. TEAP Framework A detailed description of each TEAP Program Guidance: Framework element, including: information on managers and Executive Summary the "What, Why and Benefits" of the element; transit EA/EAP "Best Practices" and streamlined approaches; professionals BCM and "Additional Resources" with references, who want to Funding tools, and examples from the IT and transit learn more Project SE industries. about the Post- topics Implementation Transit EAP Guidebook The Transit EAP Guidebook details step-by-step Program how to develop a transit enterprise architecture managers and (as-is and to-be). The Guidebook shows how to transit customize the Reference Enterprise Architecture practitioners for Transit to represent the drivers, business who are processes, information, applications, and tasked with technologies in your organization. The implementing Guidebook is an interactive and extendable an EAP and "space" on the wiki to describe a Reference maintaining Enterprise Architecture for Transit, and to the as-is and include related terms and techniques for to-be implementing a Transit Enterprise Architecture. enterprise It includes models, templates, examples, and architectures benefits associated with each step. State of the Practice A summary of the State of the Practice All Synthesis Results Synthesis related to the five elements of the TEAP Framework. Other Resources How-To Guides All Glossary and Acronym List FAQs About the Project and the Wiki Site Map Improvement Page

OCR for page 21
22 resources for the five system development disciplines, while the Streamlined Process for Developing a TEAP Guidebook describes details related to how to implement Transit Enterprise Architecture a Transit Enterprise Architecture by customizing the Refer- ence Enterprise Architecture for Transit and other resources. A recurring theme during the state of the practice review The Guidebook describes the terms and techniques used was the lack of resources needed to create the enterprise archi- by transit and other architecture experts. The Guidebook tecture. Transit professionals needed a more effective way of may be seen as an evolving process; as more transit agencies collecting and organizing their information without mar- develop architectures, concepts, techniques, and resource shalling their entire IT staff for the effort. Some transit staff materials, the resources and guidance in this section will grow. indicated that they did not even know where to start. Based on The site allows for extensions and conversations among this feedback, the wiki includes a section on how to get started. practitioners as the experience developing TEAP grows in The development of the Reference Enterprise Architecture for the industry. Transit provides building blocks to accelerate development of a high-level TEAP. The streamlined process uses the Reference Enterprise Architecture for Transit to develop templates (which Guidebook Audience and Prerequisites may be populated) and guidelines on how to collect informa- The TEAP Guidebook targets transit staff who understand tion to populate or edit the templates. both the transit enterprise domain and basic organization of The Reference Enterprise Architecture for Transit provides an Enterprise Architecture Process (EAP). (The materials transit agencies with a basic starting point that they can use to presented in the TEAP Framework section on EAP should customize their organization. It contains descriptions of the provide enough background to the reader to understand the business processes, information views, types of transit applica- Guidebook method.) tions, and similar devices and technologies used by the indus- try. It also builds the connections and dependencies between the architecture drivers (goals, measures, standards, regional Guidebook Organization agreements) and the enterprise architecture. The Guidebook is inserted into the "Best Practices" page of The entities and relationships are captured in a metamodel the TEAP Framework, EA/EAP section of the wiki. The Best (see Chapter 5). The metamodel is a way of classifying the enti- Practices page is used as a launch pad into the pages that con- ties in transit and showing how they relate. Similar to a data- stitute the Guidebook. The need to make the material inter- base, the metamodel is the database schema and the reference active and the huge amount of material that is contained in model is the content of each table in the model. these pages makes it efficient to document the material exclu- The streamlined approach describes how to edit or collect/ sively on a website and not compile it into a voluminous populate each layer of the Reference Enterprise Architecture paper document. for Transit using a template or worksheet included with the The Guidebook is divided into two major parts: instruction. Examples from existing agencies are included with the guidance. Suggestions for additional data collection fields Description of the Reference Enterprise Architecture for are included in the discussion. Moreover, the streamlined Transit approach includes a section on purpose that describes exam- Including solutions for different segments of the ples of "what if" scenarios. Additional information about the architecture streamlined approach may be found in Chapter 5. Instructions on augmenting or changing the reference architecture Wiki Site Review and Validation Instructions for customizing the various models in the architecture and changing the relationships between enti- The research team addressed the wiki's usefulness as a tool ties in different models (e.g., measures and information) for the industry at several stages of the project. As a part of the Streamlined process and guidance on applying the Refer- project's validation task, a group of transit professionals, some ence Enterprise Architecture for Transit of whom participated in the research synthesis process and Where do you start? others who did not, were asked to participate in up to three Step by step directions for getting started webinars to discuss the wiki. During the webinars, team mem- How do you drill deeper into the details of your enterprise? bers walked through the site, asking questions and describing the functionality. Participants consistently found the site intu- The Reference Enterprise Architecture for Transit is itive and useful. The results of these workshops were incorpo- described in Chapter 5. The streamlined process is described rated into the latest version of the site. The full report may be in further detail in the following sections. found in Appendix C. Additional improvements to the wiki

OCR for page 21
23 Access Levels As an Administrator, you can rename or delete anything on the workspace. Administrators can add users, change their permission levels, or remove them. Administrators alone have access to the workspace's Settings page and are also the only ones who can change page- and folder-level security settings. Administrators are the only ones who can see Hidden pages or edit Locked pages. Editors are trusted helpers who are highly privileged Writers. They can rename or delete pages, files, and folders. Editors should be highly trusted, since they can delete your data irrevocably. The recommended default for invited users. Writers can edit pages and revert pages to previous versions. They can also upload new files and create new pages. Writers cannot perform any action that cannot be undone. Readers cannot make any modifications at all to a workspace. They can view pages, RSS feeds, and files. They can also see the history of changes that have been made to a page. By default, readers can make comments on a workspace, without being able to edit the workspace itself. This setting can be modified by going to "Settings" and then "Workspace Security" [from http://usermanual.pbworks.com/w/page/11632102/Inviting-Users]. Figure 4. Wiki access levels. were also made based on the pilot results, which are described update and change the wiki and its content. The participants in Chapter 6. unanimously agreed that editors of the wiki should monitor and agree on its content (see Figure 4 for description of user roles and access levels). Vision for Augmenting the Wiki There are two approaches for submitting wiki content and (Guidebook and Reference TEAP Artifacts) changes: through comments or by adding to/changing a wiki The wiki site is critical to presenting the research because it page. Any user may submit a comment at the bottom of most provides a forum for transit professionals to share their expe- wiki pages. Some pages are locked and may be changed only riences with each other and enhance the Guidebook based on by someone with administrator-level access. Other pages may new lessons learned and experiences. During the validation be created and/or changed and documents can be uploaded workshops, participants were asked who should be able to by users with editor- and writer-level access.