Www.ddss.arch.tue.nl 7M822 Software Requirements A Use Case Approach 14 September 2010.

Slides:



Advertisements
Similar presentations
Chapter 7 System Models.
Advertisements

Requirements Engineering Process
UML Use Case Diagram / Use Case Text / Activity Diagram
Bouwkundige Informatiesystemen ADMS 2006 UML part 1 Jan Dijkstra - 25 september 2006 ADMS-BIS.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Requirements Engineering – a brief review by Andy Gillies.
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 ?
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models September 29, 2008.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Overview of Software Requirements
SYSTEMS ANALYSIS AND DESIGN INTRODUCTION 1. Systems Analysis and Design is the process people use to create (automated) information systems Systems Analysis.
SYSTEMS ANALYSIS AND DESIGN INTRODUCTION 1. Systems Analysis and Design is the process people use to create (automated) information systems Systems Analysis.
1 CSC-3324: Chapter 4 Title: What is a requirement? Mandatory reading: Sommerville 6, 7 th ed., Chap.: 7.
7M822 Software Engineering: System Models 14 September 2009.
7M822 Software Requirements Introduction 7 September 2010.
Requirements Engineering
Problem Analysis The goal of problem analysis is to gain a better understanding of the problem being solved before development begins Gain agreement on.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes 1.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 2 Introduction to Requirements Management
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
1 Requirements Analysis and Design Engineering Southern Methodist University CSE 7313.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Feasibility Study.
Requirements Engineering Requirements Elicitation Requirements Analysis Requirements Validation Requirements Management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 Object-oriented and Structured System Models.
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
Software Production ( ) First Semester 2011/2012 Dr. Samer Odeh Hanna (PhD)
Software Requirements and Design Khalid Ishaq
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Chapter 4 Software Requirements
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
Software Engineering, 8th edition. Chapter 7 1 Courtesy: ©Ian Sommerville 2006 March 20 th, 2008 Lecture # 12 Requirements Engineering Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Team Skill 1 - Analyzing the Problem Continued and Product Features and Challenges Sriram Mohan.
Team Skill 1 Analyzing the Problem
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Analyzing the Problem.
1 Requirements Elicitation – 2 Lecture # Requirements Engineering Process Requirements Elicitation Requirements Analysis and Negotiation Requirements.
Requirement Engineering Management Amna Shifia Nisafani Feby Artwodini M. Department of Information Systems Subject : Requirement Engineering.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements (utvalgte foiler fra Kap 6 og 7 i Sommerville)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
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.
IS Development Methodology
CompSci 280 S Introduction to Software Development
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Requirement Management
SNS College of Engineering Coimbatore
Abstract descriptions of systems whose requirements are being analysed
Requirements Engineering
Presentation transcript:

7M822 Software Requirements A Use Case Approach 14 September 2010

7M822 Software Requirements The Rock Problem ?! [Ed Yourdon] 2

7M822 Software systems nature Software systems by their nature are –intangible –abstract –complex –infinitely changeable 3

7M822 Requirements engineering Get a complete description of the problem –feasibility study 4

7M822 Software development Goal –to develop quality software that meets customers’ needs What is this software supposed to do? How, exactly, will we know when the software does exactly that and nothing else? 5

7M822 Software requirement A software requirement is a capability needed by the user to solve a problem to achieve an objective, and is imposed on the system 6

7M822 Problem domain The problem domain is the home of those people (real users, other stakeholders) whose needs must be addressed in order to build the perfect system. 7

7M822 Needs Features Software requirements problem domain solution domain 8

7M822 Stage Relative cost to repair a defect Derived from: Alan Davis, Software Requirements: objects,functions and states; Prentice-Hall, 1993 Requirements time Design Coding Unit test Acceptance test Maintenance

7M822 Functional requirements Find the solution for the user needs by proposing objectives for the system that involves –problem definition –identifying the users –defining the solution system boundary –identifying the constraints 10

7M822 Defining solutions system boundary System InputsOutputs inputs / system / outputs relationship Of concern: 1.Our system 2.Things that interact with our system actor 11

7M822 System boundary Our Solution Users Other Systems System Boundary I/O 12

7M822 System perspective New Solution Users Catalog system System Boundary Library system 13

7M822 Use case approach Lending services User administration Books database Library user Library staff library system 14

7M822 NS Ticket machine – a use case approach Traveler Purchase Ticket Maintenance basic data NS Take ticket Destination 15

7M822 Example Use Cases A simple word processor is required to create new and edit existing documents. Also the ability to print is required. Question? Find the system boundary, actors and use cases 16

7M822 Study matter Ian Sommerville Software Engineering, 6 th edition – Ch.6 Addison Wesley Dean Leffingwell & Don Widrig Managing Software Requirements, 2 nd edition Addison Wesley 17