CS4507: Advanced Software Engineering
|
|
- Laura McCoy
- 7 years ago
- Views:
Transcription
1 CS4507: Advanced Software Engineering Lecture 6: Requirements Engineering A O Riordan, 2016 Many of the slides are based on Sommerville (chapter 4)
2 Requirements Engineering (RE) Process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed as far as possible, it should set out what the system should do rather than how it should do it Requirements can range from a high-level statement of a service or of a system constraint to a detailed formal specification Requirements may be part of a contract for the system development Any discussion of a solution is premature until the problem is clearly defined 1 1 S. L. Pleeger, J. M. Atlee (2010) Software Engineering, 4th edition. Pearson 2
3 Case Study: Mentcare In this lecture we ll use examples from the Sommerville textbook, in particular the Mentcare Mental Health Care-Patient Management System case study. Summarized here: The Mentcare is a Mental Health Care-Patient Management System that is intended for use in clinics. It makes use of a centralized database of patient information. The Mentcare has two overall goals: 1. To generate management information that allows health service managers to assess performance against local and government targets. 2. To provide medical staff with timely information to support the treatment of patients. Key features of the system are: 1. Individual care management; 2. Patient monitoring; and 3. Administrative reporting 3
4 Process For Requirements Engineering 1. Elicitation: collecting the user s requirements 2. Analysis: understanding and modelling of desired behaviour 3. Specification: documenting the behaviour of the proposed software system 4. Validation: checking that the specification matches the user s requirements requirements review In practice, RE is iterative in which these activities are interleaved. 4
5 Requirements Elicitation Work with customers to find out about the application domain, the services that the system should provide and the system s operational constraints May involve end-users, managers, engineers and domain experts collectively know as stakeholders Issues stakeholders may not know what they really want or need stakeholders express requirements in their own domain s terminology different stakeholders may have conflicting requirements organisational and political factors at customer org 5
6 Environmental Constraints Requirements may be given to the software engineers have to be established by software engineers Types of systems new software system new software systems in presence of existing (legacy) software applications/systems ("Brownfield development") reengineering of existing system 6
7 Requirements Discovery Methods Interviewing (structured or unstructured) Ethnographic studies/ task analysis observing and analysing how people actually work Knowledge Elicitation techniques Card Sorting, Laddered Grid Prototyping Scenarios User Stories Use Cases In this course we will use Use Cases Storyboards 7
8 Example: Use cases for Mentcare 8
9 User and System Requirements User requirements what the system should do should be understandable by customer usually in English/simple diagrams System requirements detailed descriptions of the system s functions, services and operational constraints system requirements specification (SRS) is a structured collection of information that embodies the requirements of the system Requirements traceability association between a requirement and related requirements, implementations, and verifications 9
10 Example: Mentcare Requirements 10
11 Functional and Non-functional Requirements Functional requirements statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations Non-functional requirements: constraints on the services or functions offered by the system such as security, availability, etc. often apply to the system as a whole rather than individual features or services non-functional requirements may be critical to proper functioning, e.g. in realtime, embedded, and safety-critical systems single non-functional requirement, such as a security requirement, may affect a number functional requirements for different system services 11
12 Example Requirements in Mentcare Product requirement The Mentcare shall be available to all clinics during normal working hours (Mon Fri, ). Downtime within normal working hours shall not exceed five seconds in any one day. Organizational requirement Users of the Mentcare system shall authenticate themselves using their health authority identity card. External requirement The system shall implement patient privacy provisions as set out in HStan priv. 12
13 Goals and Verifiable Requirements Non-functional requirements may be very difficult to state precisely and imprecise requirements may be difficult to verify. If not possible state: Goal A general intention of the user such as ease of use: e.g. The system should be easy to use by medical staff Preferable is a: Verifiable non-functional requirement A statement using some measure that can be objectively tested: e.g. Medical staff shall be able to use all the system functions after four hours of training. After this training, the average number of errors made by experienced users shall not exceed two per hour of system use 13
14 Non-functional Requirements Reliability e.g. MTTF (Mean time to failure) Availability e.g. five nines, i.e % availability (downtime less than 5.26 mins/year) Performance expectations such as response time e.g. processed transactions/second Storage requirements Usability 14
15 Non-functional Requirements continued Robustness to inputs and operating conditions Security confidentiality, integrity, availability Maintainability Constraints on the development process e.g. customer insists on a certain programming language or development method Organisational requirements, organisational policies and procedures External requirements standards compliance, government regulations, legal 15
16 Writing good requirements Precision/Unambiguous should be as precisely stated as possible precision is difficult without making the document difficult to read Complete should include descriptions of all functions and constraints Consistent should be no conflicts or contradictions in the descriptions of the system facilities Requirements confusion functional and non-functional requirements tend to be mixed-up several different requirements may be expressed together Prioritize requirements (essential/desirable/optional) 16
17 Ways of writing a system requirements specification Natural language (NL) written as natural language sentences supplemented by diagrams and tables expressive, intuitive and universal Structured natural language structure text with template; use simple program control structures Graphical notations e.g. UML Formal methods (logic/algebra) 17
18 Example Structured NL Requirement for Insulin Pump Case Study Here is an example structured NL requirement from Sommerville: Insulin Pump/Control Software/SRS/3.3.2 Function Compute insulin dose: safe sugar level. Description Computes the dose of insulin to be delivered when the current measured sugar level is in the safe zone between 3 and 7 units. Inputs Current sugar reading (r2); the previous two readings (r0 and r1). Source Current sugar reading from sensor. Other readings from memory. Outputs CompDose the dose in insulin to be delivered. Destination Main control loop. 18
19 System Requirements Specification (SRS) Requirements documents standards have been designed e.g. IEEE 830 standard 1 Prototype SRS Outline 1 : Table of Contents 1. Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms, and Abbreviations 1.4 References 1.5 Overview 2. General Description 2.1 Product Perspective 2.2 Product Functions 2.3 User Characteristics 2.4 General Constraints 2.5 Assumptions and Dependencies 3. Specific Requirements Appendixes 3.1 Functional Requirements 3.2 Performance Requirements 3.3.Design Constraints 3.4 Attributes Availability Security Maintainability External Interface Requirements 1 IEEE IEEE Guide to Software Requirements Specifications 19
20 Requirements Validation Are the requirements: correct? consistent? unambiguous? complete? necessary? feasible? relevant? measurable/testable? traceable? Validation techniques: Walkthrough: informal review present requirements to team and stakeholders Review: team and stakeholders examine requirements simulation and production of prototypes model checking mathematical proof 20
21 Tool Support CASE tools may have some support for requirements specification Specialized commercial tools: IBM Rational RequisitePro IBM Rational DOORS Borland Caliber 21
Software Requirements. Objectives
Software Requirements cmsc435-1 Objectives To introduce the concepts of user and system requirements To describe functional and non-functional requirements To explain how software requirements may be organized
More informationSoftware Requirements
Software Engineering Software Requirements Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To introduce the concepts of user and system requirements To describe functional and
More informationSoftware Requirements. Descriptions and specifications of a system. Ian Sommerville 2000 Software Engineering, 6th edition.
Software Requirements Descriptions and specifications of a system Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Objectives To introduce the concepts of user and system To describe
More informationSoftware Requirements. Objectives. Topics covered
Software Requirements Sommerville Chapter 6 Objectives To introduce the concepts of user and system requirements To describe functional and non-functional requirements To explain how software requirements
More informationSoftware Requirements
Software Requirements Antinisca Di Marco antinisca.dimarco@univaq.it The present slides are an elaboration of the ones provided by I. Sommerville Objectives To introduce the concepts of user and system
More informationSoftware Requirements. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 6 Slide 1
Software Requirements Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 6 Slide 1 Objectives To introduce the concepts of user and system requirements To describe functional and non-functional
More informationRequirement Engineering
Requirement Engineering Outline Stakeholders Context diagram and interfaces Types of requirements Numbering requirements Scenarios, sequence diagrams Glossary Class diagrams Use cases 1 The process - phases
More informationRequirements Management Practice Description
Requirements Management Practice Description 1. REQUIREMENTS MANAGEMENT (RM) 1.1 Description of the practice TRASYS provide solutions to effectively manage critical issues and reduce risks in project related
More informationSoftware Engineering. Session 3 Main Theme Requirements Definition & Management Processes and Tools Dr. Jean-Claude Franchitti
Software Engineering Session 3 Main Theme Requirements Definition & Management Processes and Tools Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical
More informationRequirements Engineering Process
Software Engineering Requirements Engineering Process Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To describe the principal requirements engineering activities and d their
More informationRequirements Definition and Management Processes
Software Engineering G22.2440-001 Session 1 Sub-Topic 1 Requirements Definition & Management Processes and Tools Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute
More informationWhat is a requirement? Software Requirements. Descriptions and specifications of a system
What is a requirement? Software Requirements Descriptions and specifications of a system May range from a high-level abstract statement of a service or a statement of a system constraint to a detailed
More informationRequirements Engineering for Web Applications
Web Engineering Requirements Engineering for Web Applications Copyright 2013 Ioan Toma & Srdjan Komazec 1 What is the course structure? # Date Title 1 5 th March Web Engineering Introduction and Overview
More informationSoftware Requirements 1
Software Requirements 1 Requirements are descriptions of the services that a software system must provide and the constraints under which it must operate Requirements can range from high-level abstract
More informationCourse Outline. Foundation of Business Analysis Course BA30: 4 days Instructor Led
Foundation of Business Analysis Course BA30: 4 days Instructor Led Prerequisites: No prerequisites - This course is suitable for both beginner and intermediate Business Analysts who would like to increase
More informationSoftware Requirements. Topics covered. Requirements engineering
Software Requirements Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 6 Slide 1 Topics covered Functional and non functional requirements User requirements System requirements Interface
More informationStructure of Presentation. Stages in Teaching Formal Methods. Motivation (1) Motivation (2) The Scope of Formal Methods (1)
Stages in Teaching Formal Methods A. J. Cowling Structure of Presentation Introduction to Issues Motivation for this work. Analysis of the Role of Formal Methods Define their scope; Review their treatment
More informationRequirements Engineering Processes. Feasibility studies. Elicitation and analysis. Problems of requirements analysis
Requirements engineering processes Requirements Engineering Processes The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the.
More informationStory Card Based Agile Software Development
Story Card Based Agile Software Development Chetankumar Patel, and Muthu Ramachandran Leeds Metropolitan University, UK c.patel@leedsmet.ac.uk Abstract The use of story cards for user stories in many Extreme
More informationSoftware Engineering/Courses Description Introduction to Software Engineering Credit Hours: 3 Prerequisite: 0306211(Computer Programming 2).
0305203 0305280 0305301 0305302 Software Engineering/Courses Description Introduction to Software Engineering Prerequisite: 0306211(Computer Programming 2). This course introduces students to the problems
More informationRequirements engineering
Learning Unit 2 Requirements engineering Contents Introduction............................................... 21 2.1 Important concepts........................................ 21 2.1.1 Stakeholders and
More informationSofware Requirements Engineeing
Sofware Requirements Engineeing Three main tasks in RE: 1 Elicit find out what the customers really want. Identify stakeholders, their goals and viewpoints. 2 Document write it down (). Understandable
More informationPartnering for Project Success: Project Manager and Business Analyst Collaboration
Partnering for Project Success: Project Manager and Business Analyst Collaboration By Barbara Carkenord, CBAP, Chris Cartwright, PMP, Robin Grace, CBAP, Larry Goldsmith, PMP, Elizabeth Larson, PMP, CBAP,
More informationTen steps to better requirements management.
White paper June 2009 Ten steps to better requirements management. Dominic Tavassoli, IBM Actionable enterprise architecture management Page 2 Contents 2 Introduction 2 Defining a good requirement 3 Ten
More informationCDC UNIFIED PROCESS PRACTICES GUIDE
Document Purpose The purpose of this document is to provide guidance on the practice of Requirements Management and to describe the practice overview, requirements, best practices, activities, and key
More informationSystem Requirements Specification (SRS) (Subsystem and Version #)
of the (Subsystem and Version #) () (Document Revision Number) Contract (No.) Task (No.) GSA Contract (No.) Prepared for: The United States Department of Agriculture Food & Nutrition Service (FNS)/ Information
More informationRequirements Engineering Processes. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 7 Slide 1
Requirements Engineering Processes Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 7 Slide 1 Objectives To describe the principal requirements engineering activities and their relationships
More informationRequirements Management
REQUIREMENTS By Harold Halbleib Requirements Management Identify, Specify, Track and Control Requirements Using a Standard Process About the author... Harold Halbleib has a degree in Electrical Engineering
More informationSoftware Requirements, Third Edition
j Microsoft Software Requirements, Third Edition Karl Wiegers and Joy Beatty Contents Introduction Acknowledgments xxv xxxi PART I SOFTWARE REQUIREMENTS: WHAT, WHY, AND WHO Chapter 1 The essential software
More informationSoftware Process for QA
Software Process for QA Basic approaches & alternatives CIS 610, W98 / M Young 1/7/98 1 This introduction and overview is intended to provide some basic background on software process (sometimes called
More informationSOFT 423: Software Requirements
SOFT 423: Software Requirements Week 3 Class 1 Finish Elicitation & Start Analysis SOFT 423 Winter 2015 1 Last Class Questionnaires Document Inspection Requirements Stripping Use Cases Scenarios SOFT 423
More informationSOFTWARE REQUIREMENTS
SOFTWARE REQUIREMENTS http://www.tutorialspoint.com/software_engineering/software_requirements.htm Copyright tutorialspoint.com The software requirements are description of features and functionalities
More informationSo You Want To Be a Requirements Analyst? 1
So You Want To Be a Requirements Analyst? 1 Karl E. Wiegers Process Impact www.processimpact.com Be it explicitly or not, someone always performs the role of requirements analyst on a software project.
More informationSoftware Requirements Specification
1 of 7 17.04.98 13:32 Software Requirements Specification The sub-sections : 1. What is a Software Requirements Specification 2. Why is a Software Requirement Specification Required 3. What is Contained
More informationOrganizational Requirements Engineering
Chapter 9, Non-functional Requirements Organizational Requirements Engineering Prof. Dr. Armin B. Cremers Sascha Alda Armin B. Cremers, Sascha Alda Organizational Requirements Engineering 1 Overview of
More informationCS 389 Software Engineering. Lecture 2 Chapter 2 Software Processes. Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
CS 389 Software Engineering Lecture 2 Chapter 2 Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed. Topics covered Software process models Process activities Coping
More informationLecture 9: Requirements Modelling
A little refresher: What are we modelling? Lecture 9: Requirements Modelling Requirements; Systems; Systems Thinking Role of Modelling in RE Why modelling is important Limitations of modelling Brief overview
More informationSoftware Engineering. Software Processes. Based on Software Engineering, 7 th Edition by Ian Sommerville
Software Engineering Software Processes Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To introduce software process models To describe three generic process models and when
More informationUnit 1 Learning Objectives
Fundamentals: Software Engineering Dr. Rami Bahsoon School of Computer Science The University Of Birmingham r.bahsoon@cs.bham.ac.uk www.cs.bham.ac.uk/~rzb Office 112 Y9- Computer Science Unit 1. Introduction
More informationeorgette ullivan Portfolio
Portfolio Experience Designer: Design Research, Interaction and Visual Design georgettes.com georgette@georgettes.com 512-362-8078 Innovating Enterprise IT Management Software Description Create a reference
More informationUsing Use Cases for requirements capture. Pete McBreen. 1998 McBreen.Consulting
Using Use Cases for requirements capture Pete McBreen 1998 McBreen.Consulting petemcbreen@acm.org All rights reserved. You have permission to copy and distribute the document as long as you make no changes
More informationSoftware Engineering. Software Engineering. Software Costs
Software Engineering Software Engineering is the science and art of building significant software systems that are: 1) on time 2) on budget 3) with acceptable performance 4) with correct operation. Ian
More information1.1 The Nature of Software... Object-Oriented Software Engineering Practical Software Development using UML and Java. The Nature of Software...
1.1 The Nature of Software... Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering Software is intangible Hard to understand
More informationSub Code: CP7007 Sub Name: SOFTWARE REQUIREMENTS ENGINEERING Branch / Year: ME CSE / I Year Staff in charge: Dr.M.Senthil Kumar
VALLIAMMAI ENGINEERING COLLEGE S.R.M. Nagar, Kattankulathur DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Sub Code: CP7007 Sub Name: SOFTWARE REQUIREMENTS ENGINEERING Branch / Year: ME CSE / I Year Staff
More informationCREDENTIALS & CERTIFICATIONS 2016
THE COMMUNITY FOR TECHNOLOGY LEADERS www.computer.org CREDENTIALS & CERTIFICATIONS 2016 KEYS TO PROFESSIONAL SUCCESS CONTENTS SWEBOK KNOWLEDGE AREA CERTIFICATES Software Requirements 5 Software Design
More informationSoftware Requirements Specification (SRS)
Software Requirements Specification (SRS) Meeting Scheduler MANISH BANSAL ABHISHEK GOYAL NIKITA PATEL ANURAG MAHAJAN SMARAK BHUYAN - 1 - VERSION RECORD Version record showing the amendments effected to
More informationDraft Requirements Management Plan
BAO111: Core Competencies for the Business Analyst Draft Requirements Management Plan 1.0 INTRODUCTION 1.1 Purpose This document outlines requirements roles and responsibilities, presents a stakeholder
More informationRequirements Analysis Concepts & Principles. Instructor: Dr. Jerry Gao
Requirements Analysis Concepts & Principles Instructor: Dr. Jerry Gao Requirements Analysis Concepts and Principles - Requirements Analysis - Communication Techniques - Initiating the Process - Facilitated
More informationCREDENTIALS & CERTIFICATIONS 2015
THE COMMUNITY FOR TECHNOLOGY LEADERS www.computer.org CREDENTIALS & CERTIFICATIONS 2015 KEYS TO PROFESSIONAL SUCCESS CONTENTS SWEBOK KNOWLEDGE AREA CERTIFICATES Software Requirements 3 Software Design
More informationThe Software Lifecycle. Software Lifecycles
The Software Lifecycle Examining the phases of large-scale software development projects Jeff Stephenson Software Lifecycles Software Engineering vs. Programming What you have done for our past assignments
More informationTo introduce software process models To describe three generic process models and when they may be used
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationLecture 3 Software Development Processes
Lecture 3 Software Development Processes Software Engineering ITCS 3155 Fall 2008 Dr. Jamie Payton Department of Computer Science University of North Carolina at Charlotte September 2, 2008 Lecture Overview
More informationVito Madaio, PMP, TSPM 2015, September, 24th
PMI-PBA Certification Vito Madaio, PMP, TSPM 2015, September, 24th Topics What is Business Analysis Business Analysis Certification PMI-PBA Prep Course Q&A Orientamento alla Business Analysis PBA-Prep
More informationRequirements Engineering
Murali Chemuturi Requirements Engineering and Management for Software Development Projects Foreword by Tom Gilb ^ Springer Contents 1 Introduction to Requirements Engineering and Management... 1 1.1 What
More informationVALLIAMMAI ENGINEERING COLLEGE S.R.M. Nagar, Kattankulathur DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
VALLIAMMAI ENGINEERING COLLEGE S.R.M. Nagar, Kattankulathur DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Sub Code : CP7007 Sub Name: SOFTWARE REQUIREMENTS ENGINEERING Branch / Year : ME CSE / I Year
More informationChapter 1- Introduction. Lecture 1
Chapter 1- Introduction Lecture 1 Topics covered Professional software development What is meant by software engineering. Software engineering ethics A brief introduction to ethical issues that affect
More informationFundamentals of Information Systems, Fifth Edition. Chapter 8 Systems Development
Fundamentals of Information Systems, Fifth Edition Chapter 8 Systems Development Principles and Learning Objectives Effective systems development requires a team effort of stakeholders, users, managers,
More informationCS 6361, SPRING 2010 Advanced Requirements Engineering Web Based Meeting Scheduler- Project Plan
1 W E B B A S E D M E E T I N G S C H E D U L E R S Y S T E M Project Plan Version 4.0 CS 6361 ADVANCED REQUIREMENTS ENGINEERING, SPRING 2010 UNIVERSITY OF TEXAS AT DALLAS R E Q U I R E M E N T S E N G
More informationRequirements engineering and quality attributes
Open Learning Universiteit Unit 2 Learning Unit 2 Requirements engineering and quality attributes Contents Introduction............................................... 21 2.1 Important concepts........................................
More informationThe role of integrated requirements management in software delivery.
Software development White paper October 2007 The role of integrated requirements Jim Heumann, requirements evangelist, IBM Rational 2 Contents 2 Introduction 2 What is integrated requirements management?
More informationRequirements Traceability. Mirka Palo
Requirements Traceability Mirka Palo Seminar Report Department of Computer Science University of Helsinki 30 th October 2003 Table of Contents 1 INTRODUCTION... 1 2 DEFINITION... 1 3 REASONS FOR REQUIREMENTS
More informationNew York University Computer Science Department Courant Institute of Mathematical Sciences
New York University Computer Science Department Courant Institute of Mathematical Sciences Course Title: Software Engineering Course Number: g22.2440-001 Instructor: Jean-Claude Franchitti Session: 4 (Individual)
More informationWeek 3. COM1030. Requirements Elicitation techniques. 1. Researching the business background
Aims of the lecture: 1. Introduce the issue of a systems requirements. 2. Discuss problems in establishing requirements of a system. 3. Consider some practical methods of doing this. 4. Relate the material
More informationBidirectional Tracing of Requirements in Embedded Software Development
Bidirectional Tracing of Requirements in Embedded Software Development Barbara Draxler Fachbereich Informatik Universität Salzburg Abstract Nowadays, the increased complexity of embedded systems applications
More informationTECH. Requirements. Why are requirements important? The Requirements Process REQUIREMENTS ELICITATION AND ANALYSIS. Requirements vs.
CH04 Capturing the Requirements Understanding what the customers and users expect the system to do * The Requirements Process * Types of Requirements * Characteristics of Requirements * How to Express
More informationSoftware Engineering. Introduc)on
Software Engineering Introduc)on Software engineering The economies of ALL developed nations are dependent on software. More and more systems are software controlled Software engineering is concerned with
More informationWhite Paper What Solutions Architects Should Know About The TOGAF ADM
White Paper What Solutions Architects Should Know About The TOGAF ADM WP0015 October 2011 The Open Group Architecture Framework 1 (TOGAF) is the most widely referenced architecture framework currently
More informationSoftware Engineering 10. Teaching introductory and advanced courses in software engineering IAN SOMMERVILLE
Software Engineering 10 Teaching introductory and advanced courses in software engineering IAN SOMMERVILLE 1 Every course is different and what s included depends on the interests of the instructor, the
More informationEstimating Impact of Change
Traceability in Software Engineering Estimating Impact of Change Gøran K. Olsen SINTEF ICT Oslo, Norway Goran.K.Olsen@sintef.no Overview Model Driven Engineering Traceability Traceability Usage Certification
More informationRequirements Analysis that Works!
Requirements that Works! Robert Halligan, FIE Aust Managing Director, Project Performance International Email: rhalligan@ppi- int.com Introduction: Innumerable studies have concluded that requirements
More informationThis alignment chart was designed specifically for the use of Red River College. These alignments have not been verified or endorsed by the IIBA.
Red River College Course Learning Outcome Alignment with BABOK Version 2 This alignment chart was designed specifically for the use of Red River College. These alignments have not been verified or endorsed
More informationCDC UNIFIED PROCESS PRACTICES GUIDE
Document Purpose The purpose of this document is to provide guidance on the practice of Requirements Definition and to describe the practice overview, requirements, best practices, activities, and key
More informationDEVELOPING REQUIREMENTS FOR DATA WAREHOUSE SYSTEMS WITH USE CASES
DEVELOPING REQUIREMENTS FOR DATA WAREHOUSE SYSTEMS WITH USE CASES Robert M. Bruckner Vienna University of Technology bruckner@ifs.tuwien.ac.at Beate List Vienna University of Technology list@ifs.tuwien.ac.at
More information11 Tips to make the requirements definition process more effective and results more usable
1 11 Tips to make the s definition process more effective and results more usable This article discusses what I believe are the key techniques for making s definition process repeatable from project to
More informationRequirements Engineering for Software
Requirements Engineering for Software and Systems Second Edition Phillip A. Laplante CRC Press Taylor & Francis Group Boca Raton London New York CRC Press is an imprint of the Taylor & Francis Croup, an
More informationIn association with: Optimizing Requirements Discovery. We ll be starting shortly
In association with: Optimizing Requirements Discovery You will need to dial into the conference call line provided on your screen to receive audio. Technical difficulties? Please dial: 800-263 263-63176317
More informationSocio technical Systems. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 2 Slide 1
Socio technical Systems Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 2 Slide 1 Objectives To explain what a socio technical system is and the distinction between this and a computer
More informationBuild the Right Software First Time
Build the Right Software First Time are the most misunderstood part of systems development, and yet the most crucial. must be correct if the rest of the development effort is to succeed. This workshop
More informationManage Software Development in LabVIEW with Professional Tools
Manage Software Development in LabVIEW with Professional Tools Introduction For many years, National Instruments LabVIEW software has been known as an easy-to-use development tool for building data acquisition
More informationFamily: Iterative Enhancement Origin: Ivar Jacobson, James Rumbaugh, Grady Booch, 1996 Defines process framework that is adaptable to
Unified Process Family: Iterative Enhancement Origin: Ivar Jacobson, James Rumbaugh, Grady Booch, 1996 Defines process framework that is adaptable to various application domains different organizations
More informationCHAPTER 11 REQUIREMENTS
Lecture Software Engineering CHAPTER 11 REQUIREMENTS Lecture Software Engineering Topics Determining What the Client Needs Overview of the Requirements Workflow Understanding the Domain The Business Model
More informationRequirements Engineering: A Roadmap
Requirements Engineering: A Roadmap Bashar Nuseibeh & Steve Easterbrook Department of Computing Imperial College of Science, Technology & Medicine London SW7 2BZ, UK Email: ban@doc.ic.ac.uk http://www-dse.doc.ic.ac.uk/~ban/
More informationTitle: Topic 3 Software process models (Topic03 Slide 1).
Title: Topic 3 Software process models (Topic03 Slide 1). Topic 3: Lecture Notes (instructions for the lecturer) Author of the topic: Klaus Bothe (Berlin) English version: Katerina Zdravkova, Vangel Ajanovski
More informationSoftware Engineering. Requirements elicitation - Facts finding. Software Engineering Requirements Elicitation Slide 1
Software Engineering Requirements elicitation - Facts finding Software Engineering Requirements Elicitation Slide 1 Chapter Objectives To introduce software the Requirements Engineering Process To describe
More informationHow To Use Gps Navigator On A Mobile Phone
Software Requirements Specification Amazing Lunch Indicator Sarah Geagea 881024-4940 Sheng Zhang 850820-4735 Niclas Sahlin 880314-5658 Faegheh Hasibi 870625-5166 Farhan Hameed 851007-9695 Elmira Rafiyan
More informationLecture 17: Requirements Specifications
Lecture 17: Requirements Specifications Why we need to write specifications Purpose and audience Choosing an appropriate size and formality Desiderata for Specifications Properties of good specifications
More informationSystem Development Life Cycle Guide
TEXAS DEPARTMENT OF INFORMATION RESOURCES System Development Life Cycle Guide Version 1.1 30 MAY 2008 Version History This and other Framework Extension tools are available on Framework Web site. Release
More informationContents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53
Preface xvi Part I Introduction and System Engineering 1 Chapter 1 Introduction 2 1.1 What Is Software Engineering? 2 1.2 Why Software Engineering? 3 1.3 Software Life-Cycle Activities 4 1.3.1 Software
More informationPROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name
More informationSoftware Processes. The software process. Generic software process models. Waterfall model. Waterfall model phases
Software Processes CSC 221 Introduction to Software Engineering software processes extract from Sommerville s chapter 3 slides Alan Dix Coherent sets of activities for specifying, designing, implementing
More informationExamination SUBJECT. Version:
SUBJET Version: 1 Which of the following statements best describes Business nalysis? Business nalysis provides the reasoning for initiating a project. Business nalysis is the strategic part of the project
More informationAssuming the Role of Systems Analyst & Analysis Alternatives
Assuming the Role of Systems Analyst & Analysis Alternatives Nature of Analysis Systems analysis and design is a systematic approach to identifying problems, opportunities, and objectives; analyzing the
More informationRequirements Engineering: Elicitation Techniques
2008:PR003 Requirements Engineering: Elicitation Techniques Sai Ganesh. Gunda Source:http://www.marcocioffi.com/archives/2005/04/requirements-engineering/ MASTER S THESIS Software Engineering, 2008 Department
More informationThe profile of your work on an Agile project will be very different. Agile projects have several things in common:
The Agile Business Analyst IT s all about being Agile? You re working as a Business Analyst in a traditional project environment, specifying the requirements for IT Developers to build. Suddenly everyone
More informationLecture 10 CS5702. Requirements Engineering. Managing change optimising Value - A bit more about Agile RE. Requirements Engineering.
Requirements Engineering Overview Lecture 10 CS5702 Requirements Engineering Semester 1 2009/10 Professor Kevin Ryan 1. Introduction (Week 1) 2. Elicitation of requirements (2 & 3) 3. Standards, Templates
More informationAligning IT investment and Business
IBM Software Group Aligning IT investment and Business The role of requirements management, portfolio management and enterprise architecture Productivity, Governance, Innovation Dr Tariq Aslam 2009 IBM
More informationInvestigation of Adherence Degree of Agile Requirements Engineering Practices in Non-Agile Software Development Organizations
Investigation of Adherence Degree of Agile Requirements Engineering Practices in Non-Agile Software Development Organizations Mennatallah H. Ibrahim Department of Computers and Information Sciences Institute
More information3C05: Unified Software Development Process
3C05: Unified Software Development Process 1 Unit 5: Unified Software Development Process Objectives: Introduce the main concepts of iterative and incremental development Discuss the main USDP phases 2
More informationPOSITIVE TRENDS IN REQUIREMENT ENGINEERING PRACTICES FOR HIGHER SOFTWARE QUALITY
POSITIVE TRENDS IN REQUIREMENT ENGINEERING PRACTICES FOR HIGHER Dr. Rajinder Singh* SOFTWARE QUALITY Abstract : In this competitive world, customer satisfaction is the utmost important thing for any organization
More informationSWEBOK Knowledge Area Jump-Start Document for Requirements Analysis Larry H. Reeker, U.S. National Institute of Standards and Technology
Requirements Analysis 1 SWEBOK Knowledge Area Jump-Start Document for Requirements Analysis Larry H. Reeker, U.S. National Institute of Standards and Technology Purpose and Structure of this Document This
More information