Introduction to Requirements Management

Slides:



Advertisements
Similar presentations
Lecture 5: Requirements Engineering
Advertisements

NEES Project Management Workshop June 16 June 18 1 Segment 2.
Redesigning the Organization with Information Systems Soetam Rizky.
Software Requirements
Introduction to Requirements (Chapters 1-3 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
1 Chapter 5: The F1ive Steps in Problem Analysis The five steps in problem analysis. Team Skill 1.
7M822 Software Engineering Introduction 7 September 2010.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
1 CSC-3324: Chapter 4 Title: What is a requirement? Mandatory reading: Sommerville 6, 7 th ed., Chap.: 7.
SE 555 – Software Requirements & Specifications Introduction
Mastering OOA/OOD with UML. Contents Introduction Requirements Overview OOAOOD.
Project Documentation and its use in Testing JTALKS.
Bite sized training sessions: Business And Functional Requirements.
RUP Requirements RUP Artifacts and Deliverables
Chapter 2 Introduction to Requirements Management
1 SYS366 Week 10, Lecture 3 Systems Requirements Gathering: Identifying Operating Requirements.
UNIVERSITI TENAGA NASIONAL “Generates Professionals” CHAPTER 4 : Part 1 INTRODUCTION TO SOFTWARE DEVELOPMENT: SYSTEM ANALYSIS & DESIGN.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Software System Engineering: A tutorial
Software Design: An Introduction by David Budgen Presented by Shane Marcus EEL 6883 – Spring 2007 Presented by Shane Marcus EEL 6883 – Spring 2007.
Chapter 4 Requirements engineering Chapter 4 – Requirements Engineering Lecture 1 1.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Chapter 11 Analysis Concepts and Principles
Lecture 7: Requirements Engineering
1 Requirements Management - General concepts - Noureddine Abbadeni King Saud University College of Computer and Information Sciences Based on “Software.
Smart BA Distance Learning Programme Module 3: Functional Requirements.
1 Identifying System Requirements. 2 Agenda Identifying System Requirements –Stakeholder Needs –Features Project Scope Stakeholder Classifications.
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
Software Acquisition and Project Management Lesson I: Introduction.
Project – A Quick Tutorial Krishna Sainath Meda. PROJECT  A task assigned to a set of people or teams to be completed within a time frame  Any project.
Software Production Chapter 2: Identifying Software Development Activities.
Team Skill 2 Understanding User and Stakeholder Needs The Challenge of Requirements Elicitation (8)
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
Week 1. The goal of software development To develop quality software – on time on budget – that meets customers’ need However, our customer are quite.
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
Software Engineering REQUIREMENT ENGINEERING. Software Engineering Phases.
SAM-101 Standards and Evaluation. SAM-102 On security evaluations Users of secure systems need assurance that products they use are secure Users can:
Computer Software & its Types Instructor : Adnan Iqbal Course : Introduction to Computer.
Lecture 4: Requirements Engineering COSI 120b, Principles of Software Engineering.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Requirements Analysis
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Chapter 4 – Requirements Engineering Lecture 1 The hardest part of the software task is arriving at a complete and consistent specification, and much of.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Knowledge Engineering. Review- Expert System 3 Knowledge Engineering The process of building an expert system: 1.The knowledge engineer establishes a.
Software. Introduction n A computer can’t do anything without a program of instructions. n A program is a set of instructions a computer carries out.
1 Software Requirements Engineering (CS 708) Dr. Ghulam Ahmad Farrukh.
Introduction to Software Requirement Engineering Nisa’ul Hafidhoh Teknik Informatika
 System Requirement Specification and System Planning.
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.
Requirements Introduction Emerson Murphy-Hill. Scope of Software Project Failures WHY PROJECTS FAIL % 1. Incomplete Requirements Lack of user involvement12.4.
Software Requirements Engineering (CS 708)
Chapter 5 – Requirements Engineering
SYSTEM ANALYSIS AND DESIGN
Software Requirements
Software Engineering (CSI 321)
Software Requirements analysis & specifications
UNIT II.
Requirements Engineering Introduction
Software Engineering Furqan Rustam.
CS385T Software Engineering Dr.Doaa Sami
Software Engineering Lecture #3
Lecture # 7 System Requirements
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Requirements gathering
Presentation transcript:

Introduction to Requirements Management

What is a Software Requirement? A software capability needed by the user to solve a problem to achieve an objective A software capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed documentation

What is Requirements Management? A systematic approach to eliciting, organizing, and documenting the requirements of the system, and a process that establishes and maintains agreement between the customer and the project team on the changing requirements of the system.

Requirements Management Tasks Eliciting requirements from the users and other stakeholders Organizing the requirements Documenting the requirements

Types of Software Applications Information systems developed for use within a company Software developed and sold as commercial products Software that runs on computers embedded in other devices

Questions Regarding Potential Requirements Is this a need or a requirement? Is this a nice-to-have or a must-have? Is this a statement of the problem or a statement of the solution? Is this a goal of the system or a contractual requirement? Do we have to program in a particular language? Is there disagreement whether this is a requirement?

Moving from the Problem Domain to the Solution Domain Stakeholder needs Features of the system Software requirements