1. The Database Development Process
MGIS 641
Koç University

2. Learning objectives
Define the following key terms : Information System Architecture (ISA), methodology, business function, business process, functional decomposition & repository
Lists benefits of ISA
describe three components of Zachman framework for ISA
Describe stages of information engineering
Describe major components of an enterprise model
Describe briefly planning matrices used in strategic IS planning
Describe system development life cycle
Explain prototyping approach

3. Introduction The scope of ISs today is the whole organisation
Managers/knowledge workers expect easy access to information
Islands of information retire in favour of cooperative, integrated, interoperable enterprise systems
The goal of enterprise-wide computing presents a significant challenge for ISs management
Problems in controlling & maintaining data stored throughout the organisation
Describe key components to required to develop ISs that support enterprise-wide computing
Concept of ISA - framework
information engineering - formal methodology for developing ISs
Strategic business planning+ Strategic ISs planning
Describe CASE tools & repository

4. A framework for ISA
New home - set of architectural plans before construction
Any large scale endeavour requires early development of a vision/architectural plan
Information Systems Architecture (ISA) : conceptual blueprint/plan that expresses the desired future of an IS
Design/implementation of effective ISs a great challenge
many organisations do not have an ISA
no standard format for an ISA
costly in time & other resources
may seem difficult/counterproductive if conditions change rapidly
ISA creates the context within which managers can make consistent decisions concerning their ISs

5. Benefits of ISA Provides basis for for strategic planning of ISs
basis for communicating with top-management & a context for budget decisions for ISs
unifying concept for the various stakeholders in ISs
help to achieve information integration when ISs are distributed
basis for evaluating technology options (e.g. downsizing, distributed processing)
communicates the overall direction of information technology & a context for a major decision in this area.

6. Overview of the framework
There is no standard means for portraying ISA
Zachman developed a comprehensive framework
not an ISA but a context to develop one
Zachman ISA framework components
data
process
network

7. ISA framework 1 2 3 4 5 6 Data Process Network Business scope Business
List of
entities
important to
business
List of
functions
business
performs
List of locations
in which
business
operates
Business
scope 1
Business
model
Business
entities
& their
relationships
Function &
process
decomposition
Comms. links
between
business
locations 2
Model of
business
data & their
relationships
Distribution
network
ISs
model
Flows
between
apps.
processes 3
Technology
model
Database
design
Configuration
design
Process
specification 4
Technology
definition
Process
specification
Configuration
definition
database
schema
& subschema
definition 5
data &
information
Apps.
programs
System
configuration 6
Information
system

8. ISA framework components
Every IS is visualised as a combination of three components
Data represents what - bill of materials listing the components in a manufacturing system (M.S.)
Process represents how - list of instructions in M.S.
Network represents - where data stored/processed including comms. links - locations where components are manufactured (in M.S.)
Business rules are embedded in the form of logic, constraints & knowledge throughout the columns.
Data column concerns us most. But there is a close interrelationship among data / process / network components

9. Architecture roles & perspective
Each row represents the role/perspective of each individual concerning three components
Each cell contains a representation of a model for a component
any model representation may be used (more than one possible)
Model name
Role/perspective
Role description
Business Scope
Owner
Provides a strategic overview including
business scope/mission & direction
Business model
Architect
develops
business models that describe
the business scope/mission & direction
ISs model
Designer
Develops an IS model that supports the
business
Technology
Builder
Converts
ISs model into a design that
model
conforms to the features/constraints of
the technology
Technology
Contractor
Converts technology models into
definition
statements to generate the actual IS IS
User
Manage
s, uses & operates the completed IS

10. Evolution through the framework
Evolve through the cells from top to bottom
In simple systems one person - many roles
In complex systems - one role many people
Each row is not merely developed by adding extra detail but by transforming it consistently to suit to the person concerned
framework should be used to enforce a discipline in IS development, two simple rules :
Objects within rows are mapped horizontally. each process is mapped to the data it uses & both data & process are mapped to the network locations where they are distributed - ensure integration
Ideally components in each row should be simultaneously developed & one should not proceed to next row before the current row development is completed - avoid inconsistencies > rework.

11. Roles of methodologies & tools
The framework suggests the data model but does not provide the means to to develop these models
One needs a methodology/set of tools to develop architectural representation for each perspective
Methodology : Process/related set of steps to accomplish a stated goal with a set of design objects to support the process
consistent standards & procedures used throughout development process
similar to recipe = a set of instructions + set of ingredient => product
Computer Aided Software Engineering (CASE) tools : S/W tools that provide automated support for some portion of the system development process.( diagramming, screen/report painters, code generation etc.)
Integrated CASE (I- CASE) toolset : S/W tools that provide automated support for all phases of the system development process
CASE tools speed up development, improve quality

12. CASE tools - tasks Diagramming Screen & report painters
Tools for drawing structured diagrams & creating
pictorial specifications
Diagramming
Screen & report painters
Repository & reports
Checking & analysis
Code generator
Maintenance
Tools for prototyping the user interface &
creating system specification
Facility for storing, reporting & querying
all system information
Tools to check the consistency,
completeness & correctness of system
specification
Tools to generate executable code from system specification
Tools to document,
restructure &
analyse
existing systems

13. Information engineering methodology
Information engineering : A methodology that uses a data-orientation to create & maintain ISs.
top down approach
enterprise-wide in scope
data-driven
compatible with the ISA framework introduced

14. Phases of information engineering
Planning
Analysis
Design
Implementation

15. Phases of information engineering - Planning
Identify strategic planning factors
Goals
CSFs
Problem areas
Identify planning objects
Organisational units
Locations
Business functions
Entity types
Develop enterprise model
Functional decomposition
E-R diagram
Planning matrices

16. Phases of information engineering - Analysis
Develop conceptual model (detailed E-R diagram)
Develop process model (data flow diagrams)

17. Phases of information engineering - Design
Design databases (normalised relations)
Design processes
Action diagrams
user interfaces, menus, screens, reports ...

18. Phases of information engineering - Implementation
Build database definitions (tables, indexes ..)
Generate applications (program code, macros ...)

19. Similar phases in DB development & information engineering
Information DB development
Engineering
Planning Enterprise modeling
Analysis Conceptual data modeling & part of logical DB design
Design Parts of both logical & physical DB design
Implementation DB implementation
No similar phase DB maintenance

20. IE methodology
Major strength of IE is its emphasis on strategic planning for ISs.
goal : align IT with business strategies
close cooperation between business & IS managers
Competitive advantage possible if strategic ISs plans are converted into a series of practical ISs projects
3 steps :
develop the planning context, link ISs plans to strategic business plans
Identify the important planning objects (org. units, locations, high-level business functions & entity types) - 1st row in ISA framework (business scope)
Develop an enterprise model - 2nd row in ISA framework (business model)
Functional decomposition diagram high-level functions -> low-level functions
A high-level E-R diagram
A set of planning matrices that link the various components in the sub models

21. PVF & strategic planning factors
1. Goals :
maintain 10% per annum growth rate
maintain 15% before-tax ROI
No layoffs
responsible corporate citizenship
2. Critical Success Factors (CSFs) :(in achieving goals)
high quality products
on-time deliveries
high productivity
3. Problem Areas :
inaccurate sales forecasts
increasing competition
stockouts leading to backorders/lost sales

22. Alignment of Business Goals and IS (CSFs)
Hierarchy of Objectives
Consider a motor car manufaturer
Raise market share to 20% from 10% in 5 years
More frequent choice of new models
Thus reduce time to develop new model 5 to 2 years (designers)
Thus switch over assembly lines in less time, reduce to 3 months from 6 (production department)
Need IS that can produce manufacturing instructions, documents to support tendering, components listings and setup instructions for the assembly lines from drawings.
Critical Success Factors (CSF): Lower level objectives that must be achieved if the top-level objective is to be met

23. Identify Corporate Planning Objects
Organizational units
Organizational locations
Business functions
Entity types – the things we are trying to model
Information (application) systems

24. PVF & planning objects Sales Dept. Business Planning Orders Dept.
Organisational units
Business Functions
Entity Types
Sales Dept.
Orders Dept.
Accounting Dept.
Manufacturing Dept.
Fabrication Dept.
Assembly Dept.
Finishing Dept.
Purchasing Dept.
Receiving / Shipping Dept.
Business Planning
Product Development
Materials Management
Marketing & Sales
Production Operations
Finance & Accounting
Human Resources
CUSTOMER
PRODUCT
VENDOR
RAW MATERIAL
ORDER
WORK CENTRE
WORK ORDER
INVOICE
EQUIPMENT
EMPLOYEE

25. Develop Enterprise Model
Decomposition of business functions
Enterprise data model
Planning matrixes

26. Enterprise Data Model First step in database development
Specifies scope and general content
Overall picture of organizational data, not specific design
Entity-relationship diagram
Descriptions of entity types
Relationships between entities
Business rules

27. Enterprise model Business Planning Materials Management
Market analysis
Sales forecasting
Product Development
Concept analysis
Product design
Marketing & Sales
Marketing research
Order fulfillment
Distribution
Finance & Accounting
Capital budgeting
Accounts receivable
Accounts payable
Materials Management
Materials requirement planning
Purchasing
Receiving
Production Operations
Production scheduling
Fabrication
Assembly
Finishing
Human Resources
Recruiting
Training

28. Example of process decomposition of an order fulfillment function (Pine Valley Furniture)
Decomposition -- breaking large tasks into smaller tasks in a hierarchical structure chart

29. Segment from enterprise data model (Pine Valley Furniture Company) [simplified E-R diagram]
Enterprise data model describes the entities in an organization and the relationship between these entities

30. Pine Valley enterprise data model
mandatory 1
mandatory 1 to many
0 to many :
Places
Bills
CUSTOMER
Fulfills
ORDER
INVOICE
Requests
Ships
PRODUCT
Builds
WORK ORDER
Uses
RAW MATERIAL
WORK
CENTRE
Schedules
Supplies
Works
Assigned
VENDOR
RAW MATERIAL
EQUIPMENT

31. Planning Matrices examples
Function-to-data entity
Location-to-function
Unit-to-function
IS-to-data entity
IS-to-business objective

32. Example business function-to-data entity matrix
Business Planning X X X X
Product Development X X X X
Materials Management X X X X X X
Order Fulfillment X X X X X X X X X
Order Shipment X X X X X X
Sales Summarization X X X X X
Production Operations X X X X X X X
Finance and Accounting X X X X X X X X
Raw Material
Work Center
Work Order
Equipment
Customer
Employee
Product
Invoice
Order
Business
Function (users)
Data Entity
Types

33. Alternative Approaches to Database and IS Development
SDLC
System Development Life cycle
Detailed, well-planned development process
Time-consuming, but comprehensive
Long development cycle
Prototyping
Rapid application development (RAD)
Cursory attempt at conceptual data modeling.
Define database during development of initial prototype.
Repeat implementation and maintenance activities with new prototype versions.

34. Systems Development Life Cycle
Project Identification
and Selection
Project Initiation
and Planning
Analysis
Physical Design
Implementation
Maintenance
Logical Design

35. Systems Development Life Cycle
Project Identification
and Selection
Purpose --preliminary understanding
Deliverable –request for project
Project Initiation
and Planning
Analysis
Logical Design
Physical Design
Database activity –
enterprise modeling
Implementation
Maintenance

36. Systems Development Life Cycle
Project Identification
and Selection
Purpose – state business situation and solution
Deliverable – request for analysis
Project Initiation
and Planning
Analysis
Logical Design
Physical Design
Database activity –
conceptual data modeling
Implementation
Maintenance

37. Systems Development Life Cycle
Project Identification
and Selection
Purpose –thorough analysis
Deliverable – functional system specifications
Project Initiation
and Planning
Analysis
Logical Design
Physical Design
Database activity –
conceptual data modeling
Implementation
Maintenance

38. Systems Development Life Cycle
Project Identification
and Selection
Purpose –information requirements structure
Deliverable – detailed design specifications
Project Initiation
and Planning
Analysis
Logical Design
Physical Design
Database activity –
logical database design
Implementation
Maintenance

39. Systems Development Life Cycle
Purpose –develop technology specs
Deliverable – program/data structures, technology purchases, organization redesigns
Project Identification
and Selection
Project Initiation
and Planning
Analysis
Logical Design
Physical Design
Database activity –
physical database design
Implementation
Maintenance

40. Systems Development Life Cycle
Purpose –programming, testing, training, installation, documenting
Deliverable – operational programs, documentation, training materials
Project Identification
and Selection
Project Initiation
and Planning
Analysis
Logical Design
Physical Design
Database activity –
database implementation
Implementation
Maintenance

41. Systems Development Life Cycle
Project Identification
and Selection
Purpose –monitor, repair, enhance
Deliverable – periodic audits
Project Initiation
and Planning
Analysis
Logical Design
Physical Design
Database activity –
database maintenance
Implementation
Maintenance

42. The prototyping methodology and database development process

43. The prototyping methodology and database development process

44. The prototyping methodology and database development process

45. The prototyping methodology and database development process

46. The prototyping methodology and database development process

47. Managing Projects: People Involved
Systems analysts
Database analysts
Users
Programmers
Database/data administrators
Systems programmers, network administrators, testers, technical writers

48. Gantt Chart
Shows time estimates of tasks

49. PERT chart
Shows dependencies between tasks

50. Database Schema Physical Schema Conceptual Schema External Schema
Physical structures
Conceptual Schema
ER models
External Schema
User Views
Subsets of Conceptual Schema
Can be determined from business-function/data entity matrices
DBA determines schema for different users
This is part of people-management in databases

51. Three-schema database architecture
External schema
Different people have different views of the database…these are the external schema
Internal schema

52. Three-tiered client/server database architecture

53. Preliminary data model
Pine Valley Furniture
Preliminary data model

54. MS Access data model prototype
Pine Valley Furniture
MS Access data model prototype