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 9
9 CHAPTER 2 Research Approach--Methodology The Transit Enterprise Architecture Planning (TEAP) · Systems Engineering (SE) related to its benefit and role in Framework project consisted of two phases. This chapter a project's success, as well as its relationship to the funding provides a description of the project tasks, including the and project approval process; and methodology used to perform them. · Post-Implementation Analysis (PIA) including goals, approaches, and key issues. Phase I: Development of the TEAP Framework A wiki is a collaborative website where wiki The Phase I research focused on understanding how transit members may edit, review, upload documents, agencies and transportation authorities currently understand, and add their comments. The TEAP wiki is open apply, and use each of the five system development methods for anyone to view, but available only to that compose the TEAP Framework. Building on their meth- members to edit. ods and best practices, the project fused these practices into a coherent framework that showed the connectedness and flow of each development method. As described above, the project objectives involved describing the Framework for several audi- During the interviews and literature search, the research ences including executives, senior managers, practitioners, and team collected examples of performance measures used in program managers. In addition, detailed guidance would also post-implementation analyses, highlighted different method- include a technical audience such as the chief information or ologies and approaches, and developed an annotated bibliog- technology officers and their staff. Further, the means and raphy of relevant transit publications and tools/resources channels used to disseminate the findings and Framework had in the IT industry. The results of the research synthesis are to be collaborative and evolving because the Framework tech- described in Chapter 3. nologies and methods change quickly. A paper report, such as Building on best practices from the transit industry and other this, may be used as a reference once in a while, but it cannot industries, a wiki or collaborative website (see sidebar) was be used as a tool that facilitates community exchange and developed to document the recommendations for the Frame- extensions. To that end, the means of documenting the Frame- work. The resources collected during the synthesis tasks were work was also selected as part of the Phase I effort. inserted into the wiki as a portal to find existing resources that The first part of this phase consisted of gathering informa- explain the multitude of approaches that are available through tion from the literature and interviews on the state of the NTI, APTA, FTA, and other outreach efforts. Another critical practice related to the five framework planning areas: product that was developed for the wiki was a high-level sum- mary of the Framework for executive and senior managers (see · Enterprise Architecture and Enterprise Architecture Plan- Appendix A). This guidance document explains the need to ning (EA/EAP); implement all or part of the Framework, describes the Execu- · Business Case Methodology (BCM) for identifying, justi- tive's role with respect to IT governance, gives details on how to fying, and selecting ITS projects use the enterprise architecture to justify and measure successful · ITS Funding Implementation, focusing on program invest- implementations, and identifies and provides links to a rich set ment strategies and their relationship to IT Governance; of resources that may be used to establish the TEAP Framework.