System Development Methods

CT00046-3-2

People Oriented Methodologies

 Topic & Structure of the Lesson

People Oriented Methodologies:

 Web Information Systems Development Methodology
(WISDM)
 Knowledge Acquisition and Documentation Structuring
(KADS)
 Soft Systems Methodology (SSM)

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 2

 Slide 3 (of 17)

Learning Outcomes

 By the end of this lecture, YOU should be able to :

– Identify and explain the underlying people-based
methodologies

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 3

 Slide 4 (of 17)

Key Terms you must be able to use

If you have mastered this topic, you should be able to use the
following terms correctly in your assignments and exams:
 People Oriented Methodologies and Principles
 Web Information Systems Development Methodology (WISDM)
 Knowledge Acquisition and Documentation Structuring (KADS)
 Soft Systems Methodology (SSM)

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 4

 People Oriented Methodologies

These methodologies are used when;

 Developer trying to make the system mimic the user’s needs and
behaviors.
 The system is going to be used by many types of users (age,
literacy, culture, needs, etc.)
 Widely used in environment involving gaming, robotics, virtual
reality, augmented reality, medicine, animal behaviors, etc.
 Used when:-
 Requirements are not fixed / cannot be fully determined
earlier
 Requirements and scenario is constantly changing.
 Structured methodologies might not be suitable as they
require many facts to be constant.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 5

 People Oriented Methodologies
Facts often considered-

 User’s age  User Emotion

 Users' behavior – Perception, preferences,
– Students, managers, sports emotions, attraction, fear,
athletes, etc. concerns.
 User’s computer literacy  Environment
– Novice, Intermediate, Expert – Private, social, group,
corporate, etc.
 User Physical capabilities
– Body size, level of sight,  Laws and Legislations
– Copyright, Consumer Rights,
hearing, etc. (for Gaming)
etc.
 Users Culture
– Language, texts, colors,
concerns, etc.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 6

 People Oriented Methodologies

General strategies of development in this methods:

 Developers study user behaviors of a system in real-world.

 Capture user's behavior into ‘tasks’ in virtual world.
 Connect / link several tasks to become a complete process.
 Build IS to satisfy the process in real-world.
 Continually update IS system with new and improved tasks (continuous
development).

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 7

 Web Information Systems Development
Methodology (WISDM)

 Idle for building websites and web application which are

very dynamic - incorporates many components, languages
and features.
 WISDM is based on
‘Multiview’
framework

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 8

 WISDM
Multiview Framework

 Multiview looks at a scenario from many view / angle and creates

automated design based on the captured tasks.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 9

 WISDM
Multiview Framework

 Organizational analysis: Mainly focused on relevant situations

characterized by complexity and stakeholder interests.
- Business (strategy)
•What business is the Organization in?
•What are the visions and missions?
- Products and services
•What are the sources of revenue?
•What are the benefits to
the business actors?
- Who are the customers?
- Who are the competitors?

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 10

 WISDM
Multiview Framework

 Information analysis:
– Collect user requirements which can be converted as
functionalities in a new system.
– WISDM uses UML Model to represent the functionalities of the
new system.
– Elements of the analysis model
•Data model
•Flow model
•Class model

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 11

 WISDM
Multiview Framework
 Work design:
– Produce a ‘good fit’ considering people and their needs
together with the computer systems and necessary work
tasks.
– The organization has managements. The management
defines job requirements. These job requirements fit for
employees’ job expectations and job requirements
– The developers design the
system according to the
job expectations and
job requirements - focus on
usability, information quality
and accessibility.
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 12
 WISDM
Multiview Framework

 Technical Design:
– Technical tasks that focus on efficient design based on
the given system specification.
– System is broken down into some subsystems, example:
– The information retrieval subsystem
– The database subsystem
– The control subsystem
– The recovery subsystem
– The monitoring subsystem

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 13

 WISDM
Multiview Framework
 Human Computer Interaction:
– Represents the interaction between technical design and
work design.
– Focus on the ways in which users will interact with the
system (screens, inputs, and outputs, etc.).
– Should be designed to match the technical skill,
experience and expectation
of the customers.
– Concentrate on the user
interface which can be
easily accessible, usable,
flexible, and secured.
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 14
 Knowledge Acquisition and
Documentation Structuring (KADS)

 Structured way of developing knowledge-based systems

(expert systems).
 Its components are:
– A methodology for managing knowledge engineering
projects.
– A knowledge engineering workbench.
– Methodology for performing knowledge elicitation.
 Components in the real world are converted into ‘chunks’ to
be designed and turned into automated functions.
 Uses object-oriented approach for designing and
construction.
 KADS was further developed into CommonKADS.
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 15
 KADS
Development Techniques

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 16

 KADS
Development Techniques

 Context level
 Defines the boundary between the system, or part of a system,
and its environment, showing the entities that interact with it.
 This level is a high-level view of a system.
 Concept level
 Obtaining, processing, and generating information or knowledge.
 Artifact level
 An artifact is one of many kinds of tangible products produced
during the development of software.
 Example of artifacts (e.g., use cases, class diagrams, and other
Unified Modeling Language (UML) models, requirements and
design documents).
 Aimed to describe the function, architecture, and design
of software.
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 17
 Soft Systems Methodology (SSM)

 An organized way of tackling the messy situation in the real

world.
 Based on system thinking, a holistic view of the situation
 Used when:
– Requirements are not clear / cannot be fixed
– Scenario of the system are too complex to be defined.
– Users not sure how the system should behave.
 Soft System - Developer / user not sure of the requirement for
the system (System functionality difficult to be determined)
– Compared to HARD SYSTEMS where most of the requirements
can be determined and fixed.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 18

 Soft Systems Methodology (SSM)

 Soft system
– Organizational problems are ‘messy’ or poorly defined
– Stakeholders interpret problems differently
– Human factors important, – creative, intuitive approach to problem-solving
– Outcomes are learning, better understanding, rather than a ‘solution’
- Focused on improvements to organizational problems.

 Hard System
– Objective reality of systems in the world
– Well-defined problem to be solved
– Technical factors foremost
– Scientific approach to problem-solving
– More traditional way of viewing systems in Computing Science, focused on
computer implementations
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 19
 SSM
Development Path

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 20

 SSM
Development Techniques

 Takes a holistic view of the scenario / situation.

 Draw a ‘Conceptual Design’ of the scenario.
 Root definitions are produced for each system using the
CATWOE criteria. CATWOE is a set of questions that help
complement the Rich Picture of product
 (Client, Actor, Transformation, World-view, Owner,
Environment).
 Conceptual Model produced and compared to the real
world.
 Task to be automated are prioritised using the MoSCoW
technique.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 21

 Question & Answer

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 22

 Discussions

1. Briefly describe the situations that are suitable to adopt

the process-based methodologies.
2. Briefly describe why do we need to study human behavior
when planning and developing a system?

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 23