BTS330: Business Requirements Analysis using OO Lecture 5: The Importance of Stakeholders.

Slides:



Advertisements
Similar presentations
3.05 Employee Marketing-information to develop a marketing plan
Advertisements

Workbook 1: Crafting Your Value Proposition Workbook Template
Chapter 5 Buying business services. Program The increasing importance of services Differences between goods and services A classification of services.
Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 1998 by Carnegie Mellon.
Lecture 2: Businesses and Business Processes  archaic : purposeful activity : BUSYNESSBUSYNESS  usually commercial or mercantile activity engaged in.
1 Chapter 5: The F1ive Steps in Problem Analysis The five steps in problem analysis. Team Skill 1.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Project Management Quality Management* Dr. Khalid S. Husain * 07/16/96
CHAPTER 9: LEARNING OUTCOMES
socio-organizational issues and stakeholder requirements
Waniwatining Astuti, M.T.I
Framework Project Concept Source – PMBOK®– 2008 Edition Project Management Professional Project Management Professional (P M P)
Chistyakova Nataly O.. Project stakeholders The client is the principal party interested in the carrying out of a project and in its successful outcome.
International Organization for Standardization AIMS MANAGEMENT CONSULTANTS Vijay Garg ,
Voice of the Customer (Part of the Project Preparation Phase)
Problem Analysis The goal of problem analysis is to gain a better understanding of the problem being solved before development begins Gain agreement on.
SYS366 Week 3, Lecture 2 Introduction to Requirements Gathering:
Project Management Lecture 5+6 MS Saba Sahar.
Project Management An Overview John Mulhall MIICM; LIB International Credit & Process Management Professional.
Project Management Fundamentals Project Organization and Integration
A description of the different project roles and responsibilities within an organization Next © 2009 IT Project & Portfolio Office I The University of.
Project Identification and Selection
1 Module 14 Managerial Accounting for MBAs. 2 Financial Accounting Defined as the preparation of financial statements and other data for parties external.
1 BTS330 Vision & Scope. 2 IT Projects What defines project success? On time Within budget Delivers what the clients want The reality Less than 20% of.
1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.
1 SYS366 Week 10, Lecture 3 Systems Requirements Gathering: Identifying Operating Requirements.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Quality Control Project Management Unit Credit Value : 4 Essential
INTRODUCTION TO PROJECT MANAGEMENT. WHAT IS A PROJECT? “A planned undertaking of related activities to reach an objective that has a beginning and an.
Software Requirements Engineering: What, Why, Who, When, and How
Lecture: The Importance of Stakeholders.  Objective of the requirements capture and analysis phases is to understand business processes and develop requirements.
STRATEGIC HR CHOICES. STRATEGIC HR CHOICES: COMPENSATION  Internal vs. external equity  Fixed vs. variable pay  Performance vs. membership  Job vs.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Chapter CHAPTER EIGHT OVERVIEW SECTION 8.1 – OPERATIONS MANAGEMENT Operations Management Fundamentals OM in Business IT’s Role in OM Competitive.
1 BTS330 Introduction to Stakeholders & Business Areas.
The Enterprise Project Management (EPM) Professional March 28th, 2007 Brendan Giles, BSc., PMP, MOS, MCP (EPM) The Key to Successful Adoption of Enterprise.
1 Identifying System Requirements. 2 Agenda Identifying System Requirements –Stakeholder Needs –Features Project Scope Stakeholder Classifications.
Business Driven Technology Unit 5 Transforming Organizations Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution.
1 SYS366 Week 4, Lecture 2 Requirements Part 4: Constraints, The Problem Statement.
1 BTS330 Lecture: Businesses and Business Processes.
Software Requirements and Design Khalid Ishaq
1 SYS366 Lecture Requirements Gathering: Stakeholders.
By Germaine Cheung Hong Kong Computer Institute
BTS330: Business Requirements Analysis using OO Lecture 6: Systems.
1 Team Skill 1 - Analyzing the Problem Continued and Product Features and Challenges Sriram Mohan.
Requirements Management with Use Cases Module 3: Analyze the Problem Requirements Management with Use Cases Module 3: Analyze the Problem.
Lecture: The Importance of Stakeholders SYS366. Identifying Requirements Objective of the requirements capture and analysis phases is to understand business.
Problem Analysis 1. What is Problem Analysis?  The process of understanding real-world problems and user needs and proposing solutions to meet those.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
1 CP586 © Peter Lo 2003 Multimedia Communication Multimedia Development Team.
Environment Lecture 2. Environment definition Organizations are open systems with input and output. Environment is all that surrounds the organization.
Software Project Management Lecture 3. What is Project Management?  Project management is “the application of knowledge, skills, tools and techniques.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Analyzing the Problem.
BTS330: Business Requirements Analysis using OO Lecture 5: The Importance of Stakeholders.
Slide 1 Software Construction Software Construction Lecture 3.
Range of different businesses. Unit Overview: On completion of this unit you should: 1. Know the range of different businesses and their ownership 2.
1 BTS330 Week 4 - Lecture 1 Businesses and Business Processes.
CMMI Certification - By Global Certification Consultancy.
Crafting Your Offer & Market Value Proposition By Ed Downes.
1 Team Skill 1 Analyzing the Problem … Part 1: 5 steps in Problem Analysis Based on “Software Requirements Management, A use case approach”, by Leffingwell.
Requirement Elicitation Nisa’ul Hafidhoh Teknik Informatika
Lecture 2: Business Use Cases and Actors - How to identify them
Architecture Components
Chapter 4 Systems Planning and Selection
Team Charter Project Name: Executive Sponsor: Project Purpose:
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 1 Mumtaz Ali Rajput +92 – 301-
Why should the public sector want to innovate?
ISO 9001.
Kenya’s Journey towards Optimal Medical Devices Management
Presentation transcript:

BTS330: Business Requirements Analysis using OO Lecture 5: The Importance of Stakeholders

Identifying Requirements  Objective of the requirements capture and analysis phases is to understand business processes and develop requirements for the new system

Who is a Stakeholder?  “ An individual who is materially affected by the outcome of the system or the project (s) producing the system” *  Or the people who suffer from the problem being addressed * * Use Case Modeling by Bittner and Spence, p. 51.

Categories of Stakeholders  Five primary categories –Users –Sponsors –Developers –Authorities –Customers

User Stakeholders  Those who actually use the system  Technology Adopters –Interested in using all of the features of the system; in pushing it to the limit of its capabilities  Standard Users –Not interested in using all of the features of the system. Rather they want a system that allows them to perform their business processes simply and in the same way that they are used to performing them

Standard Users  Those in day-to-day business operations –use and change information  Those using queries –view calculated/collected information  Management –use reports, statistics –demand controls  Executives –strategic issues

Non-human users –Mechanical devices that the system must interact with –Other business areas –Other systems

Sponsor Stakeholders  Indirect users  Or those actually paying for the development of the system  Or those affected only by the business outcomes that the system influences

Sponsor Stakeholders  Business Managers, investors  Department heads  “champions”

Developer Stakeholders  Those involved in the production and maintenance

Authority Stakeholders  Those who are expert in a particular aspect of the problem or solution domain –Ministries –Technical experts –Domain experts

Customer Stakeholders  Those doing business with the company

Questions to Ask to Determine Stakeholders:  Who will be affected by the success or failure of the new solution?  Who are the users of the system?  Who is the economic buyer for the system?  Who is the sponsor of the development? * * Use Case Modeling, by Bittner & Spence, page 63.

Questions to Ask to Determine Stakeholders:  Who else will be affected by the outputs that the system produces?  Who will evaluate and sign off on the system when it is delivered and deployed?  Are there any other internal or external users of the system whose needs must be addressed? * * Use Case Modeling, by Bittner & Spence, page 63.

Questions to Ask to Determine Stakeholders:  Are there any regulatory bodies or standards organizations to which the system must comply?  Who will develop the system?  Who will install and maintain the new system?  Who will support and supply training for the new system?  Who will test and certify the new system? * * Use Case Modeling, by Bittner & Spence, pages

Questions to Ask to Determine Stakeholders:  Who will sell and market the new system?  Is there anyone else?  Okay, Is there anyone else? * * Use Case Modeling, by Bittner & Spence, page 64.

More Reasons to Involve Stakeholders and Users  “…you must understand the economic, technological, political, and business environment into which the system will be introduced and how that environment will be changed by the new system.” * * Use Case Modeling by Bittner and Spence, page. 15.

Stakeholders & Users are the ones who can tell you the economic, technological, political, and business environment into which the system will be introduced and how that environment will be changed by the new system.