Data Resources for Information Access

End User Computing

End User ComputingWhere the user does some of the programming

Data Model

Dialog

End User Computing

System Design Sequence

Develop Data Resources Develop Dialog StructureAttach ActionsDevelop Detailed Models

Data Model

Dialog

End User Computing

Data Requirements

Operational DataHistorical DataExternal DataUser Defined Data

Databases

Operational Data Data WarehousesUser Defined Databases

Operational Databases:

contain transaction data to support On-line Transaction Processing (OLTP). These databases contain

• large quantities of data

• one record for each business transaction

• real time data

Data Warehouses and Data Marts

contain summary and historical recordsto support Online Analytical Processing (OLAP).

organized for a specific business unit historical instances summarized as appropriate flexible, read only access

Data Models

Atomic databases (usually relational)Rule models (for expert systems)Image databases Object libraries

Data Extraction Design

Organized for flexibility rather than efficiency

Small enough to fit on user devicesSupports historical data (time

stamped vs real time)Protect corporate master filesReduces concurrency problems for

distributed data

User Defined Databases

User managedNot sharedReside on clients

Data Generation

ExtractionCaptureEntry

Functions of Data Management

InputQuality AssuranceStorageMaintenanceRetrieval

Data Model

Dialog

End User Computing

Dialog Purpose

Produce Output RepresentationsEnable User to Call Operations and

Feed Parameters to ThemAccess Memory AidsProvide Control Mechanisms

Objectives of Good Dialog

Promote man/machine symbiosis.

Identify Problem to be SolvedIdentify Users for the SystemIdentify Functions to be SupportedDesign Dialog

Data Model

Dialog

End User Computing

Program Architecture

The organization of code components

The objective of system architecture is to simplify maintenance by putting code together that will be changed

at the same time

Architectural Philosophies

Requirements DrivenData DrivenDialog DrivenEvent Driven

Traditional Design

Traditional Life Cycle ApproachFormal MethodologiesCASE ToolsPurchased Systems

New ApproachesRADEvolutionary CodeObject Oriented Design

Data Model

Dialog

End User Computing

Business Within a Business

Most firms manage IT as a business within the business, with IT having its own

career pathsjob descriptionspersonality profiles

Aligning IT with the Business

TechnologyExcellence(Systems)

Business Profitability(Applications)

IT

User

End User Systems

Enhance customer decision making toIdentify problems in time to avoid

themDiscover opportunities you would

otherwise miss

End User Computing