Information engineering (ie)

Today, many organizations have evolved from a structured analysis approach to an information engineering approach.

Information engineering is a data-centered, but process-sensitive technique that is applied to he organization as a whole (or a significant part, such as a division), rather than on an ad-hoc, project-by-project basis (as in structured analysis). The basic concept of information engineering is that information systems should he engineered like other products. Information engineering books typically use a pyramid framework to depict information systems building blocks and system development phases. The phases are:

1. Information strategy planning (ISP) applies systems analysis methods to examine the business as a whole to define an overall plan and architecture for subsequent information systems development. No actual information systems or computer applications are developed.

Instead, the project team studies the business mission and goals and defines an information systems architecture and plan to optimally align information systems to help the organization achieve its business goals.

2. Based on the strategic plan, business areas are carved out and prioritized. A business area is a collection of cross-organizational business processes that should be highly integrated to achieve the information strategy plan (and business mission). A business area analysis (BAA) uses systems analysis methods to study the business area and define the business requirements for a highly streamlined and integrated set of information systems and computer applications to support that business area.

3. Based on the business area requirements analysis, information system applications are carved out and prioritized. These applications become projects to which other systems analysis and design methods are applied to develop production systems. These methods may include some combination of structured analysis and design, prototyping, and object-oriented analysis and design. Information engineering is said to be a data-centered paradigm because it emphasizes the study and definition of DATA requirements before those of PROCESS, INTERFACE, or GEOGRAPHY requirements. This is consistent with the contemporary belief that information is a corporate resource that should be planned and managed. Since information is a product of data,

data must be planned first! Data models are drawn first. In addition to data models, information engineers also draw process models similar to those drawn in structured analysis.

Although information engineering has gradually replaced structured analysis and design as the most widely practiced Strategy for Systems analysis, information engineering actually integrates all the process models of structured analysis with its data models. That should make sense, since we know that an information system must include both DATA and PROCESS building blocks. Information engineering was the first formal Strategy for synchronizing those building blocks!

Information engineering was also the first widely practiced strategy that considered GEOGRAPHY building blocks through application of tools that plan and document the distribution of data and processes to locations.

PROTOTYPING (P)

Another strategy for Systems analysis is prototyping. Prototyping is an engineering technique used to develop partial but functional versions of a System or applications. When extended to system design and construction, a prototype can evolve into the final, implemented system.

Two flavors of prototyping are applicable to systems analysis:

- Feasibility prototyping is used to test the feasibility of a specific technology that might be applied to the business problem. For example, we might use Microsoft Access to build a quick-but-incomplete prototype of the feasibility of moving a mainframe application to a PC-based environment.

- Discovery prototyping (sometimes called requirements prototyping) is used to discover the users business requirements by having them react to a quick-and-dirty implementation of those requirements. For example, we might again use Microsoft Access to create sample forms and reports to solicit user responses as to whether those forms and reports truly represent business requirements. (Note: In discovery prototyping, we try to discourage users from worrying about the style and format of the prototypes; that can be changed during system design!)

In response to the faster pace of the economy in general, prototyping has become a preferred technique for accelerating systems development. Many system developers extend the prototyping techniques to perform what they call rapid application development. Unfortunately, some developers are using prototyping to replace model-driven strategies, only to learn what true engineers have known for years-you cannot prototype without some degree of more formal

design models.

 

2. Make a written translation of the text below.

JOINT APPLICATION DEVELOPMENT (JAD)

As previously described, modern structured analysis and information engineering both emphasize model-driven development. Prototyping places emphasis on construction of the working prototypes. Joint application development (JAD) complements both of these techniques by emphasizing participative development among system owners, users, designers, and builders. Joint application development (JAD) uses highly organized and intensive workshops to bring together system owners, users, analysts, designers, and builders to jointly define and design systems. Synonyms include joint application design and joint requirements planning.

A JAD-trained Systems analyst usually plays the role of facilitator for a workshop that will typically run from three to five full working days. This workshop may replace months of traditional interviews and follow-up meetings. JAD provides a working environment in which to accelerate methodology activities and deliverables. It promotes enhanced system owner and user participation in system development. But it also requires a facilitator with superior mediation and negotiation skills to ensure that all parties receive appropriate opportunities to contribute to the system's development.