Application Portfolio Architecture

Some of these articles are large and graphics-intensive. They can take time to download. Please, be patient.

04/01/1998, "The Data Requirements Framework", Database Programming and Design, Moriarty, Terry; Swenson, Jim

Provides an overview of a framework for presenting data requirements in the context of time (current, historical and future) and level of detail (detailed, summary).

06/01/1996, "Architecting for Evolution", Database Programming and Design, Moriarty, Terry

Presents an application portfolio architecture that allows applications that have been architected to share and integrate data co-exist with the unarchitected applications.

11/01/1995, "Avoiding the Trauma", Database Programming and Design, Moriarty, Terry

Provides a number of strategies for migrating to an architected application portfolio.

10/01/1995, "Part of the Whole", Database Programming and Design, Moriarty, Terry

Discusses how the application portfolio needs to be synchronized with the business life cycle by mapping each IT technology into the business functions it supports.

10/01/1992, "Avoiding the Trap", Database Programming and Design, Moriarty, Terry

As part of the change management series, discusses the importance of doing impact analysis across the application portfolio

09/01/1992, "The Winds of Change", Database Programming and Design, Moriarty, Terry

Part of the Change Management Series. Uses a business rule classification scheme to determine whether an impact analysis is complete. Also discusses the need for multi-release impact analysis.

04/01/1992, "Architect for Change", Database Programming and Design, Moriarty, Terry

As part of the change management series, describes the areas of the business from which change is most likely to be initiated. Also discusses how proper allocation of requirements across the three-level architecture can enable flexible applications.

03/01/1992, "Managing Application Evolution", Database Programming and Design, Moriarty, Terry

The initial articles in the change management series, it illustrates how a repository can be used to control application enhancements

09/01/1990, "Planning an Application Architecture", Software Development, Moriarty, Terry

Provides a discussion of the three-level architecture management layers (Information, Business function and Delivery), describing the various ways that the architecture can be used to manage applications.

Last updated on: 12/17/01