Chapter 26
Frameworks
Learning Objectives
1.
2.
3.
4.
Multiview
Strategic Options Development & Analysis
(SODA)
Capability Maturity Model (CMM)
Euromethod
2
Frameworks

Frameworks provide guidance to the
developer in choosing methods,
techniques, and tools rather than a
prescriptive (methodology-style) stepby-step approach.
3
Multiview 1 – five stages
It is a ‘multi-view’ in the following sense:
As an information systems project develops, it takes on different
perspectives or views: organizational, technical, human-oriented,
economics and so on.
It brings together techniques from multiple methodologies.
It incorporates five different views in five stages:
1.
Analysis of human activity
2.
Analysis of information (sometimes called
information modelling)
3.
Analysis and design of socio-technical aspects
4.
Design of the human–computer interface
5.
Design of technical aspects
4
Multiview 1 – framework
5
Stage 1: Analysis of human
activity


Based on SSM (Mode 1)
Central focus: Search for a particular world view







Form rich pictures of the problem situation
Let rich pictures stimulate discussion between the problem
solver and the problem owner
Extract problem themes from rich pictures
Form root definition
Construct a conceptual model
Compare the completed conceptual model to the
representation of the ‘real world’ in the rich picture
Debate possible changes to improve the problem situation …
6
Stage 2: Analysis of information


Takes as input the root definition/conceptual model
from stage 1
Two main phases:

the development of a functional model:




identify the main function
decompose functions successively (4-5 levels)
provide hierarchical model and DFDs as input into stage 3
the development of an entity model



Extract and name entities from the area of concern
Establish relationships between entities
Construct an entity model and provide it as input to stages 4
and 5
7
Stage 3: Analysis and design of
the socio-technical aspects









Philosophy: people should be allowed to participate in the
analysis and design of the systems that they will be using
Human considerations: job satisfaction, task definition, morale
Consider both social and technical objectives
Specify both social and technical alternatives
Match socio-technical alternatives
Rank in terms of meeting socio/technical objectives
Consider costs/resources/constraints and rank accordingly
Select best socio-technical solution
Define computer task, role set, and people tasks for solution
8
Stage 4: Design of the humancomputer interface



Takes as input the entity model from stage 2, and the
computer tasks, role-set, and people tasks from
stage 3
Philosophy: the ways in which users will interact with
the computer will have an important influence on
whether the users will accept the system
Works on the technical design of the humancomputer interface



batch vs. online facilities
conversations and interactions with particular types of user
necessary inputs and outputs, error checking, minimization
of number of keystrokes
9
Stage 5: Design of the technical
aspects



Takes as input the entity model from stage 2 and the
technical requirements from stage 4
Takes a technical view towards an efficient design of
the system
Final outputs are:






application subsystem (impl. functions in the function chart)
information retrieval subsystem (responds to data enquiries)
database (and db maintenance subsystem)
control subsystem (alerts for user/program/operator errors)
recovery subsystem (repairs system after error detection)
monitoring subsystem (records all system activities)
10
Multiview 1 – outputs
11
Multiview 1 - Concerns
The methodology must help answer the following questions:
1. How is the computer system supposed to further the aims of
the organization installing it?
2. How can it be fitted into the working lives of the people in
the organization that are going to use it?
3. How can the individuals concerned best relate to the machine
in terms of operating it and using the output from it?
4. What information system processing function is the system to
perform?
5. What is the technical specification of a system that will come
close enough to doing the things that have been written
down in the answers to the other four questions?
12
Multiview 1 – framework
13
Multiview 1 – socio-technical
analysis & design outline
14
Multiview 2 – requirements for
the technical specification outline
15
Multiview 2 – interaction of
situation
16
Multiview 2 – framework
17
Multiview v1 to v2 – changes
18
Multiview 2 – T-dominant
prespective
19
Multiview – constructing ISD
methodology
20
Strategic Options Development
and Analysis (SODA)


“SODA is an approach designed to provide
consultants with a set of skills, a framework for
designing problem solving situations and a set
of techniques and tools to help their clients work with
messy problems” [Eden and Ackerman, 2001]
Four perspectives:




individual (tries to make sense of the organization)
nature of organizations (political and power aspects play an
important role in decision making; role negotiation)
consulting practice (role of negotiation in effective problem
solving, managing consensus and commitment)
technology and techniques (used to bring together the first
three elements)
21
SODA – theory and concepts
22
Capability Maturity Model (CMM)


CMM is a framework for evaluating processes used
to develop software projects
Processes are grouped into five levels based on their
‘maturity’

Initial level (“heroic level”):





adhoc (and chaotic) development
success/failure depends on the individuals involved
not sustainable
late and over-budget software delivery
Repeatable level



identifiable policies for managing software development
realistic plans based on performance of previous projects
cost estimates, schedules, project standards
23
Capability Maturity Model (cont…)

Defined level






standard S/E processes documented
well-defined, stable development approach
includes readiness criteria, inputs, standards, procedures,
verification mechanisms, outputs and completion criteria
organization-wide training program for learning process
quality and technical progress monitoring by management
Managed level




quantitative quality and productivity measures
software process db used to collect process-related data
analysis of methodology effectiveness
predictable processes and quick exception handling
24
Capability Maturity Model (cont…)

Optimizing level




proactive and continuous process improvement
ability to identify strengths and weaknesses
assess new technologies and process
innovations
standard activity of planning and managing
process change
25
CMM – five levels
26
27
CMM - structure
28
CMM - KPAs
29
CMM - KPAs
30
Euromethod




Euromethod: part of the IT standardization policy of the EU
Objective: to facilitate cross-border trading by providing a common
understanding of requirements and solutions among users from
different countries
Problem: diversity in approaches, methods and techniques in
information systems used in Europe
Based on experiences with existing methods:





SSADM (from the UK)
Merise (from France)
IE (from the UK/US)
SDM (from the Netherlands)
DAFNE (Italy), MEIN (Spain), Vorgehensmodell (Germany)
31
Euromethod
 Euromethod applies to any information systems adaptation: development or
modification of an information system providing that the initial (or current) state and
the required final state can be defined.
 Euromethod focuses on the understanding, planning and management of the
contractual relationships between customers and suppliers of information systems
adaptations.
 Types of transactions in an IS adaptation
Call for tender
Approval of deliverables
Tender response
Supplier selection
Approval of status
and plans
Contract award
Contract change control
TENDERING
PRODUCTION
Approval of final
deliverables
Contract
completion
COMPLETION 32
Euromethod
 Euromethod includes elements relating to ‘procurement’ rather than
development of information systems
 Its concept is to bridge different methodologies by following three models: the
transaction model, the deliverable model and the strategy model
 The transaction model helps manage customer/supplier interactions
across organizational boundaries
 The deliverable model defines the target domain (data, functions,
architecture) for an information systems adaptation, incl. the goals, the
key roles and responsibilities of the customer and the supplier
 The strategy model assesses the problem situation and selects a
strategy with well defined decision points to get successfully to the final
state of the adaptation.
33
Types of transaction in an IS
adaption
34
An hierarchy of deliverables
35
Euromethod – planning
process
36
Thank
You for Your
Attention
37