socio-organizational issues and stakeholder requirements

Slides:



Advertisements
Similar presentations
Gender and Safe Motherhood
Advertisements

Goals of INFO3315 Learn about the range of techniques to: Understand users Establish requirements Brainstorm alternatives creatively Prototyping alternative.
Chapter 13 socio-organizational issues and stakeholder requirements.
© Colin Potts B1-1 Organizational approaches to requirements Colin Potts Georgia Tech.
Soft Systems Methodology
Introduction to Soft Systems Methodology
Interpersonal skills & Communication Edina Nagy Lajos Kiss Szabolcs Hornyák.
Soft Systems Methodology
Copyright 2009  Develop the project charter: working with stakeholders to create the document that formally authorizes a project—the charter  Develop.
SSM - 1 Soft Systems Methodology SSM Elena Losseva MBA 731 November 12, 2007.
Introduction to Soft Systems Methodology. The Vision SSM Models Use Cases Activity Models Dynamic Models Object Models Programs Databases Business Computing.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Analytical methods for Information Systems Professionals
socio-organizational issues and stakeholder requirements –Part 1
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Analytical methods for IS professionals ISYS3015 Qualitative research methods Data collection.
The Process of Interaction Design
ICS 463: Intro to Human Computer Interaction Design 2. User-Centered Design Dan Suthers.
Introduction to software project management. What is a project? One definition ‘a specific design or plan’ ‘a specific design or plan’ Key elements non-routine.
1 Software project management (intro) An introduction.
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
Facilitating Multi Stakeholder Processes and Social Learning Herman Brouwer/ Karèn Verhoosel Centre for Development Innovation Rich Picture Visit://portals.wi.wur.nl/msp//portals.wi.wur.nl/msp.
Vermelding onderdeel organisatie 1 MKT project 1 & Mens-Machine-Interactie slides chapter 13 Dix et al. Socio-organizational issues and stakeholder requirements.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Requirements Engineering Process – 1
Copyright c 2006 Oxford University Press 1 Chapter 7 Solving Problems and Making Decisions Problem solving is the communication that analyzes the problem.
Customer Focus Module Preview
What is Business Analysis Planning & Monitoring?
Foundation in Business Analysis
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 7 Requirements Engineering Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Chapter 4 Requirements Engineering
IE398 - lecture 10 SSM in detail
S/W Project Management
Requirements Analysis
CB1004 Modelling Business Systems 71 Modelling Business Systems 7 Systems Methods.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
Management Information Systems Foundations of Information Systems Ismiarta Aknuranda Informatika UB.
Software Requirements Engineering: What, Why, Who, When, and How
Chapter 7: A Summary of Tools Focus: This chapter outlines all the customer-driven project management tools and techniques and provides recommendations.
SacProNet An Overview of Project Management Techniques.
Lecture 7: Requirements Engineering
1 chapter 13 socio-organizational issues and stakeholder requirements.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Week 4 (2) 2008IS33 ISD - SSM 1 COMP3470 IS33 People-Centred Information Systems Development Week 4 : Lecture 2 ISD Approaches: Soft Systems Methodology.
Project quality management. Introduction Project quality management includes the process required to ensure that the project satisfies the needs for which.
By Germaine Cheung Hong Kong Computer Institute
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Systems Analyst (Module V) Ashima Wadhwa. The Systems Analyst - A Key Resource Many organizations consider information systems and computer applications.
Techniques In Information Systems Development Methodology.
1 Department of CSE, KLU Chapter 13 socio-organizational issues and stakeholder requirements.
M253 Team Work in Distributed Environments Week (3) By Dr. Dina Tbaishat.
User-centered approaches to interaction design By Haiying Deng Yan Zhu.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
 System Requirement Specification and System Planning.
MANAGEMENT INFORMATION SYSTEM
Software Quality Control and Quality Assurance: Introduction
Monitoring and Evaluation Systems for NARS Organisations in Papua New Guinea Day 3. Session 9. Periodic data collection methods.
Analisis Bisnis.
Public Services Information Management
THE BUSINESS ANALYSIS PROCESS MODEL
SOFT SYSTEMS AND THE META MODEL SEPTEMBER 2018 perspectives abridged
socio-organizational issues and stakeholder requirements
Project Management Process Groups
Why should the public sector want to innovate?
Chapter 5 Understanding Requirements.
User requirements modelling: Motivation
Presentation transcript:

socio-organizational issues and stakeholder requirements O.Love, L.Magwood, O.Byrd, M.Brockman

Organizational Issues They affect the acceptance and relevance of new information and communication systems.

Why Stakeholders Must be Identified Stakeholders must be identified so that information can transfer and to power relationships that cut across organizational structure. Stakeholders also need to know the severity of the situations and how it affects them and their subordinates whether it be positive or negative.

Who are the STAKEHOLDERS? A stake holder is anyone who is effected by the success and failure of the system Four types of stake holders: -primary: actual users of the system -secondary: receive output and provide input -tertiary: no direct involvement but effected by the success and failure -facilitating: involved in development of the system

Helping you understand Stakeholders http://www.youtube.com/watch?v=uKozswXz7q M

So how socio-technology effect business Understanding that socio-technical models affect and are composed of both human and machine elements. The focus of this approach is to describe and document the impact of the introduction of a specific technology into a organization.

Socio-technology cont… Methods vary but most attempt to capture certain common elements The problem being addressed The stakeholders affected Formal and informal work groups Changes Proposed technology External constraints.

CUSTOM Methodology A Socio-technical methodology designed to be practical to use in small organizations. Based on User Skills and Task Match (USTM) Developed to allow design teams to understand fully document user requirements Establishes stakeholder requirements All stakeholders are considered, not jus the end-user

CUSTOM Methodology Cont… Applied at the initial state of design Product Opportunity – Emphasis is on capturing requirements. Forms- Based methodology Providing a set of questions to apply at each of its stages

6 Key Stages 6 key stages to carry out in a CUSTOM analysis: Describe context Identify stakeholders Identify work-groups Identify task Identify needs Consolidate

OSTA OSTA stands for Open System Task Analysis The OSTA has Eight stage model that focus on certain task.

OSTA Stage Model The primary task identified in terms of users’ goals task inputs to system identified external environment into which the system will be introduced is described, including physical, economic and political aspects transformation processes within the system are described in terms of actions performed on or with objects

OSTA Stage Model Part 2 social system is analyzed, considering existing internal and external work-groups and relationships technical system is described in terms of configuration and integration with other systems performance satisfaction criteria are established, indicating social and technical requirements of system new technical system is specified

Soft Systems Methodology Was developed by Checkland There are no assumption of technological solutions but there is an emphasis on understanding situation fully. There are stages to Soft System Methodology

Soft Systems Methodology Stages recognition of problem and initiation of analysis detailed description of problem situation rich picture generate root definitions of system CATWOE conceptual model - identifying transformations compare real world to conceptual model identify necessary changes determine actions to effect changes

Root definitions of system (CATWOE) Clients: those who receive output or benefit from the system Actors: those who perform activities within the system Transformations: the changes that are affected by the system Weltanschauung: (from the German) or World View - how the system is perceived in a particular root definition Owner: those to whom the system belongs, to whom it is answerable and who can authorize changes to it Environment: the world in which the system operates and by which it is influenced

Once Identified… We then identify the transformations and how it is achieved using the conceptual model. Next we return to our real world system. Finally we decide if the changed are necessary and beneficial to the system as a whole.

Participatory Design Participatory design is a philosophy that encompasses the whole design cycle Design in the workplace, design team Users actively collaborate Actively participate Main Characteristics Improve the work environment Collaboration Interactive approach

Participatory Design Cont… Methods to help convey information between the user and designer Brainstorming- All participants are involved Informal Unstructured “On-the-fly” ideas Recorded No judgment

Participatory Design Cont… Storyboarding- can be used as a means of describing the user’s day-to-day activities as well as the potential designs and the impact they will have.

Participatory design continued… Workshops- fill missing knowledge, getting ideas from both users and designers. Allowing everyone to get a more focused view on the design. Pencil and paper exercises- gives everyone a change to walk-through the system using mock designs

Just a little example http://www.youtube.com/watch?v=o-_8d2l_sBE

Ethnography Is based on very detailed recording of the interactions between people and between people and their environment. Special focus on social relationships

Ethnographic tradition Ethnography is based on very detailed recording of the interactions between people and their environments. It has a special focus on social relationships and how they affect the nature of work. The ethnographer does not enter actively into the situation, and does not see things from a particular person’s point of view