Avison

1
Avison FitzgeraldInformation Systems
Development

• Characterisation and Comparison of Methodologies

2
Methodology Definition
3
Methodology suggests
4
Methodology Components
5
Reasons to adopt a methodology

• Implementability
• Low coupling
• Maintainability
• Portability
• Reliability
• Robustness
• Security
• Simplicity
• Testability
• Timeliness
• Visibility

• A better end product
• Acceptability
• Availability
• Cohesiveness
• Compatibility
• Documentation
• Ease of learning
• Economy
• Effectiveness
• Efficiency
• Fast development rate
• Flexibility
• Functionality
• A better development process
• A standardised process

6
Themes (organisational, modelling, engineering
and construction, people )

• Systems approach
• Strategic information systems
• Business process engineering
• Planning approaches
• Stages of growth
• Flexibility
• Project management
• Process modelling
• Data modelling
• Object modelling
• Legacy systems
• Evolutionary development
• Prototyping
• Rapid development
• Method engineering
• Web development

• Participation
• End user development (and client-led)
• Expert systems
• Knowledge management
• Customer orientation
• External development
• Application packages
• Enterprise resource planning
• Outsourcing
• Software
• Software engineering
• Automation
• Component development (and open source)
• Database management

7
Techniques (holistic, data, process,
object-oriented, management, estimation,
organisational, people )

• Rich pictures
• Root definitions
• Conceptual models
• Cognitive mapping
• Entity modelling
• Relational modelling
• Normalization
• Dataflow diagramming
• Decision trees
• Decision tables
• Structured English
• Structure diagrams
• Structured walkthroughs
• Matrices
• Action diagrams

• Entity life cycle
• Object orientation
• UML
• Case-based reasoning
• Risk Analysis
• PERT Charts
• Gantt charts
• Lateral thinking
• Critical success factors
• Scenario planning
• Future analysis
• SWOT
• People techniques
• Stakeholder analysis
• Joint application development (JAD)

8
Tools and toolsets

• Tools
• Project management MS Project
• Groupware GroupSystems Ventura
• Web site development Dreamweaver
• Drawing Microsoft Visio
• Database management system Access

• Toolsets
• Information Engineering Facility
• Select
• Oracle

9
Methodologies (process, blended, object-oriented,
rapid, people, organisational, frameworks )

• STRADIS
• YSM
• JSD
• SSADM
• Merise
• IE
• Welti ERP development
• OOA
• RUP
• RAD JM
• DSDM
• Extreme programming
• WISDM (web development)

• ETHICS
• KADS
• CommonKADS
• SODA
• SSM
• ISAC
• PI
• CMM
• PRINCE
• Renaissance
• Multiview
• Euromethod

10
Yourdon Systems Method (YSM)
11
(No Transcript)
12
Jackson systems development (JSD)
13
JSD structure diagram
14
James Martin IE Four levels
15
Information Engineering (IE)
16
Information Engineering (IE)Data, activity and
interaction
17
Object-oriented analysis (Yourdon OOA)

• Finding class--objects
• Identifying structures
• Identifying subjects
• Defining attributes
• Defining services

18
(No Transcript)
19
Rapid Application Dev.
James Martins RAD (JMRAD)
20
Socio-technical approach (Mumford)
21
KADS

• 1 Organisational model
• 2 Application model
• 3 Task model
• 4 Model of co-operation
• 5 Model of expertise

22
KADS Model of Expertise
Categories of Knowledge

• Domain knowledge
• Inference knowledge
• Task knowledge
• Strategic knowledge

23
(No Transcript)
24
(No Transcript)
25
ISAC
26
A-graph
27
I-graph
28
Why do organisations not adopt a methodology?

• Productivity
• Complexity
• Gilding the lily
• Skills
• Tools
• Not contingent
• One-dimensional approach
• Inflexible
• Invalid or impractical assumptions

• Goal displacement
• Problems of building understanding into methods
• Insufficient focus on social and contextual
  issues
• Difficulties in adopting a methodology
• No improvements

29
Criteria for assessing methodologies

• Rules
• Total coverage
• Understanding the information resource
• Documentation standards
• Separation of logical and physical designs

• Validity of design
• Early change
• Inter-stage communication
• Effective problem analysis
• Planning and control

30
Criteria for assessing methodologies

• Performance evaluation
• Increased productivity
• Improved quality
• Visibility of the product
• Teachable

• Information systems boundary
• Designing for change
• Effective communication
• Simplicity
• Automated development aids

31
Criteria for assessing methodologies

• Consideration of user goals and objectives
• Participation
• Relevance to practitioner
• Relevance to application

• The integration of the technical and the
  non-technical systems
• Scan for opportunity
• Separation of analysis and design

32
Bjørn-Andersen (1984) checklist
33
Comparisons
34
Comparisons
35
(No Transcript)
36
(No Transcript)