Informatics Development

1
InformaticsDevelopment
2
ISDevelopment
Conception
Total
Development Failure
Analysis
Partial
Project Abandonment
Design
Phases
Construction
Process
Activities
Implementation
Methods
Iterative
Techniques
Toolkit
Requirements
Linear
Maintenance
Tools
Bespoke
Mode
Software
IT Resources
Package
Development Process
Hardware
IT System
Informatics Management Planning
Developer Resources
Communications Technology
Models
Models
Information System
Project-Based
System Documentation
Project Documentation
Informatics Service
Roles
Organisation
Project Management
Project Teams
3
Coverage
All growth depends upon activity. There is no
development physically or intellectually without
effort, and effort means work. Calvin Coolidge
(1872 - 1933)

• Development Process
• Development Toolkit
• Systems Conception
• Systems Analysis
• Systems Design
• Systems Construction
• Systems Implementation
• Systems Maintenance

4
DevelopmentProcess
Conception
Conception
Bespoke
Package
Analysis
Analysis
Adaptation
Design
Design
Implementation
Construction
Linear
Iterative/ Incremental
Construction
Advantages
Implementation
Development
Disadvantages
Disadvantages
Waterfall
Delivery
More difficult
Adaptation
Prototyping
Easier
Advantages
Management
Evolutionary Development
Planning
Planning
Management
Estimation
5
IS Development as a HAS
IS Development
IT Resources
Clients/ Users
Information System
Development Process
Clients
Developer Resources
Human Activity System
Development Information System
6
Development Team
Development Roles
Business Analyst
Systems Analyst
Project Manager
Programmer
Change Manager
7
Development Phases
Development Process
Systems Conception
Clients
Systems Maintenance
Business Case
Costs Benefits Constraints
IS
Systems Analysis
Systems Implementation
Requirements Specification
Users
Users
IS
IS
Requirements
Systems Design
Systems Construction
System Design
System Configuration
Development Information System
8
Forms of Development
Bespoke
Product
Sequencing
Iterative
Linear
Package
9
Bespoke/Package Development
Bespoke
Product
Package
10
Linear Development Process
Linear Development Process
Systems Conception
Systems Analysis
Systems Design
Systems Construction
IS
Systems Implementation
IS
Systems Maintenance
11
Iterative Development Process
Iterative Development Process
Systems Conception
Systems Analysis
Systems Implementation
Systems Design
Systems Construction
12
Summary-Development Process

• Information systems development is the science
  and art of designing and making, with economy and
  elegance, information technology systems that
  support the activity of particular organisations
• The development process can be seen as a human
  activity system. It has key inputs and outputs
  and relies on an information system for effective
  performance
• The development process consists of a number of
  key phases. They are conceived, analysed,
  designed, constructed, implemented and maintained
• These phases may either be expressed as a linear
  sequence or as some form of cycle
• Information systems are built either as bespoke
  products or tailored from software packages

13
DevelopmentToolkit
UML
Low Technology
SSADM
DSDM
Prototyping
Life-Cycle Model
Integration
Techniques
Structured
Object-Oriented
Scenarios
E-R Diagramning
RAD
Core
Use Cases
Documentation Method
Normalisation
Data Analysis
Features
User Involvement
Development Methods
User Centric
Project Management
Data Flow Diagrams
Support
IS Planning
Techniques
Data Dictionaries
Process Analysis
Developer Centric
Multimedia
Process Descriptions
Hypermedia
Object Modelling
User Interface
Tools
Object Analysis
GUI
Web Page
State Transition Diagrams
Application Development
DBMS
KBS
Languages
Environments
Front-End
CAISE
Structured
Object-Oriented
4GL/E
Back-End
14
Methods, Techniques, Tools
Toolkit
Development Toolkit
Methods
Methods
Techniques
Techniques
Tools
Tools
15
Development Methods
Components
Model Development Process
Techniques
Documentation Method
Integration of Process Techniques
16
Method Types
Method Types
Structured
RAD
Object-Oriented
17
Techniques
Techniques
Developer-Centric
User-Centric
18
Developer-Centric Techniques
Techniques
Developer-Centric
Data Analysis
Process Analysis
Object Analysis
User-Centric
19
User-Centric Techniques
Techniques
Developer-Centric
User-Centric
Prototyping
Scenarios
Use Cases
20
Tools
Tools
Interface
Communications
Logic
Transactions
Data
21
CAISE
Development Process
CAISE
Front-End
Integrated
Back-End
Development Information System
22
Summary-Development Toolkit

• A developer's toolkit consists of methods,
  techniques and tools
• Methods constitute frameworks which prescribe,
  sometimes in great detail, the tasks to be
  undertaken in a given development process
• Techniques are particular approaches to
  supporting the processes of systems analysis,
  systems design and systems construction
• Development tools comprise hardware, software,
  data storage and communications technology used
  to construct information systems and to support
  the development process
• The development process has been subject to
  automation through the use of CAISE tools

23
Conception
Tangible
Intangible
Costs
Benefits
Strategic Evaluation
Constructs
ROI
Risk Identification
Investment Appraisal
Developing Business Case
Approaches
Information Economics
Risk Estimation
Benefits Management
Risk Analysis
Risk Assessment
Feasibility Study
24
Process of Systems Conception
Systems Conception
IS Planning
Building a Business Case
Assessing Risk
Feasibility Study
IS Analysis
25
Building a Business Case
Business Case
Costs
Cost-Benefit Analysis
Benefits
26
Tangible/Intangible Costs
Costs
Tangible
Intangible
27
IS Costs
Hardware Costs - computers, printers, storage,
accessories etc. Software Costs - off-the-shelf
packages, bespoke software, development tools
etc. Installation Costs - data entry, data
conversion etc. Environmental costs - wiring,
furniture, air-conditioning etc. Running costs -
electricity, communication costs etc. Maintenance
costs - on hardware and software. Security costs
- risk management and disaster recovery
mechanisms. Networking costs - network hardware,
software and maintenance. Training costs -
frequently under-estimated. Wider organisational
costs - new salary structures, management etc.
28
Life-Cycle Costs
Keen P.G.W. (1991). Shaping the future business
design through IT. Harvard Business School Press.
29
Tangible/Intangible IS Benefits
Benefits
Tangible
Intangible
30
IS Benefits
accuracy increased accuracy of
information quality better quality
information usability more useful
information flexibility ability to use
information more flexibly user satisfaction
increased work satisfaction functionality more
effective working reliability more reliable
service utilisation more information
used relevance more focused information productiv
ity increased levels of working security more
secure information profitability more
money speed getting information quicker volume
more information
31
Cost-Benefit Analysis
Aims
Approaches
Efficiency Gains
Return on Investment
Effectiveness Gains
Payback Period
Strategic Advantage
Information Economics
32
Return on Investment
ROI average (annual net income / annual
investment amount)
33
Payback Period
Payback Investment - cumulative benefit (cash
inflow) Payback Period number of years for this
to reach zero
34
Information Economics
35
Risk Analysis
Risk Analysis
Risk Factors
Risk Identification
Project Size
Risk Estimation
Project Structure
Risk Assessment
Experience with Technology
36
Summary-System Conception

• Conception will follow on from IS planning.
  Conception is the phase in which we develop the
  key business case, analyse risk and assess the
  feasibility of an information system
• Any business case or strategic evaluation of an
  information systems should consider IS costs and
  IS benefits
• It is useful to make the distinction between two
  types of costs/benefits tangible or visible
  costs/benefits and intangible or invisible
  costs/benefits
• Investment in IS can be justified in terms of
  efficiency, effectiveness such as better customer
  relations and strategic advantage
• Appraisal techniques such as payback period
  primarily assess efficiency gain
• Appraisal techniques such as information
  economics are directed at assessing effectiveness
  and strategic advantage
• Risk analysis is the process of identifying
  risks, estimating the likelihood of risks and
  planning for avoiding risks
• A feasibility study is an attempt to determine
  whether an information system is achievable given
  organisational resources and constraints

37
Analysis
Documentary Analysis
Observation
Workshops
Ethnography
Interviews
Prototyping
Techniques
Stakeholder Identification Participation
Functional
Requirements Elicitation
Information Systems
Requirement
Non-Functional
Requirements Specification
Structural Modelling
Behavioural Modelling
Object Modelling
Human Activity Systems
Task Analysis
Job Analysis
Job Satisfaction
Job Requirements
38
Systems Analysis
Systems Analysis
Analysis Human Activity Systems
Analysis Information Systems
Systems Conception
Organisational Analysis
Socio-Technical Systems Analysis
Systems Design
39
Process of Systems Analysis
Information Systems Analysis
Stakeholder
Requirements Elicitation
Requirements Specification
40
Elicitation and Capture
Requirements Capture
Requirements Elicitation
Client
Reality
Producer
User
Producer
Customer
Regulator
41
Elicitation and Specification
Requirements Elicitation
Requirements Specification
Interviews
Structural Modelling
Observation
Behavioural Modelling
Ethnography
Object Modelling
Prototyping
Workshops
Stakeholder Participation
42
Use Case Model
ATM
Cash Withdrawal
Bank System
Bank Customer
Transfer Funds
Deposit Funds
ATM Operator
Administration
43
Specialisation Dimensions
Specialisation Decisions
Specialisation Tasks
44
Summary-System Analysis

• Systems analysis involves two primary and
  inter-related activities - requirements
  elicitation and requirements representation.
• Requirements elicitation is that process devoted
  to the identification of requirements
• Requirements specification is that process
  concerned with the representation of requirements
• A requirement is any desired feature of an
  information technology system
• Requirements may vary depending on the
  stakeholder group. Requirements are not objective
  phenomena. Requirements elicitation involves
  attempting to achieve some inter-subjective
  agreement amongst stakeholder groups about
  requirements
• Requirements are likely to change over time. Part
  of the reason for adaptation of systems is
  because requirements change
• Requirements must be frozen at some point in
  order to construct an information technology
  system - an artefact
• Ideally, requirements will be generated for new
  work systems as well as new technical systems.
  The aim is to achieve an optimal balance between
  both social and technical objectives

45
Design
Input Design
Procedure Design
Process Design
Human Activity System Design
Output Design
Group Design
Logical Design
Data Design
Job Design
Communication Design
IT System Design
Socio-Technical Design
Security Design
Ethics
Hardware Design
Stakeholder Participation
Physical Design
Software Design
Communications Design
Database Design
Interface Design
46
Process of Systems Design
Systems Design
Information Systems Design
Human Activity Systems Design
Systems Analysis
Socio-Technical Systems Design
Systems Construction
47
Interaction IS and HAS
Human Activity System
Information System
48
Data Models for Work Systems
Nurse
Nurse
Group
Patient
Task
Nurse
Task
Patient
Patient
49
ETHICS
Diagnose Human Needs
Diagnose Technical Needs
Set Technical System Objectives
Set Social System Objectives
Set out Technical Solutions
Set out Social Solutions
Feasible Technical Solutions
Feasible Human Solutions
Note any Technical Constraints
Note any Human Constraints
IDEAL Technical Solution
IDEAL Human Solution
Merge Highest Ranking Solutions
Rank Solutions in terms of Technical Objectives
Rank Solutions in terms of Human Objectives
Merge Highest Ranking Solutions
50
Socio-Technical Design
Socio-Technical System (before)
Information System Order clerks fill out order
forms Accounts clerks update customer
ledgers Problems resolved via paper-passing
Human Activity System Orders clerks acounts
clerks Individual working across customer
accounts Problems resolved by two senior clerks
Socio-Technical System (after)
Information System Terminal input of orders Batch
update of a central database Reports output from
system
Human Activity System Small work
groups Specialisation of work around
customers Group resolution of problems
51
IS and HAS Design
Information System Design
Human Activity System Design
Logical Design
Job Design
Group Design
Procedure Design
Physical Design
52
Stakeholder Participation
Benefits
Closer match IS requirements
Closer match IS HAS
Commitment of stakeholders
Involvement
Participation
53
Types of Participation
Types
Consultative Participation
Representative Participation
Concensus Participation
54
Logical Design
Logical Design
Input Design
Output Design
Processing Design
Database Design
Communications Design
Controls and Security Design
55
Physical Design
Physical Design
Hardware Design
Software Design
Telecommunications Design
Database Design
Interface Design
56
HAS Design
HAS Design
Job Design
Team Design
Procedure Design
57
Summary-System Design

• Design is planning the shape of some technical
  artefact to meet the requirements established in
  systems analysis. Also designing the human
  activity system in which the IS will be placed
• Information systems design is a form of
  socio-technical systems design
• We may distinguish between two levels of
  information technology systems design - logical
  design and physical design
• Information systems design benefits from forms
  of stakeholder participation
• Information systems design outputs to systems
  implementation

58
Construction
Bespoke
Module
Integration
Component-Based Development
Coding
Stress
Testing
Tailoring
Package
Building
Configuration Management
Documenting
User Manual
System Manual
Tools
DBMS
Web Tools
Interface Management
Transaction Management
Programming Languages
Data Management
Process Management
Application Development Environments
59
Process of Systems Construction
Systems Construction
Systems Design
Information Technology System Construction
Human Activity System Construction
Information System Construction
Systems Implementation
60
IT System Construction
IT System Construction
Building the Application
Testing the Application
Documenting the Application
61
Building the Application
Building the Application
Building the Interface
Building Business Rules Application Logic
Building the Transaction Layer
Building the Data Management Layer
Construction Approaches
Bespoke
Packages
Software Components
62
Testing the Application
Testing the Application
Unit Testing
System Testing
Volume Testing
Integration Testing
63
Documenting the Application
Documenting the Application
User Manual
System Manual
64
Constructing the HAS
Constructing the HAS
Specifying Jobs/Roles
Specifying Teams
Specifying Procedures
65
Summary-System Construction
66
Implementation
Data Preparation
Hardware Acquisition
User Resistance
Installation
Software Acquisition
User Training
Testing
User Acceptance
Technical Systems Implementation
Social Systems Implementation
User Acquisition
Delivery
67
Process of Systems Implementation
Systems Implementation
Systems Construction
Human Activity System Implementation
Information System Implementation
Socio-Technical System Implementation
Systems Maintenance
68
Implementation
Information System Implementation
Human Activity System Implementation
User acquisition
Software Acquisition
Hardware Acquisition
User Training
User Acceptance
Data Preparation
Installation
Testing
Introduction
69
Types of System Implementation
Implementation Types
Direct Conversion
Parallel Implementation
Hybrid Implementation
70
Technical System Implementation
Technical System Implementation
Software Acquisition
Hardware Acquisition
Data Preparation and Conversion
Installation
Testing
Delivery
71
Social System Implementation
Social System Implementation
User Group Formation
User and Operator Training
User Acceptance
72
Summary-System Implementation

• Systems implementation involves delivering an
  information system into its context of use
• Systems implementation involves both technical
  and social systems implementation
• Technical systems implementation involves
  software acquisition, hardware acquisition, data
  conversion, installation, testing and delivery
• Social systems implementation involves user group
  formation, user training and user acceptance
• After a period of operation a post-implementation
  audit or summative evaluation of the system
  should be conducted

73
Maintenance
Informatics Service
Maintenance Teams
Rejuvenation
Significant Activity
Life-Cycle
Infrastructure
Flexibility Analysis
Inventory
Level of Activity
Legacy Systems
Configuration Management
Domain-Dependent
Maintenance
Information Systems
Corrective
Dialectic
Perfective
Adaptive
Preventative
Adaptation
Use
74
Systems Maintenance
Systems Maintenance
Maintenance Human Activity Systems
Systems Implementation
Maintenance Information Technology Systems
Socio-Technical Systems Maintenance
Systems Conception
75
Reasons for Maintenance
Reasons for Maintenance
Bugs
Process Changes
Requests
Software/Hardware Problems
Environmental Changes
76
Cycle of Maintenance
Information Systems Maintenance
Information Systems Use
77
Types of Maintenance
Types of Maintenance
Perfective
Adaptive
Corrective
Preventative
78
The Process of System Maintenance
Process of Maintenance
Maintenance Teams
Flexibility Analysis
Configuration Management
Rejuvenation
79
Configuration Management
Configuration Management
Development Process
Valid Product
Modified Product
Product Review
CM Controls
Approved Product
Project Repository
Baseline
80
Summary-System Maintenance

• Maintenance is the process of making needed
  changes to the structure of some information
  system
• We may distinguish between corrective,
  perfective, adaptive and preventative maintenance
  of information systems
• Maintenance is a significant activity for most
  organisations
• Maintenance should be planned for and managed by
  informatics services
• Configuration management is an umbrella activity
  applied throughout the development process
  involving Identifying changes to products of the
  development process Controlling the changes made
  to products Ensuring that the changes are
  properly made Reporting the changes to others