The meaning of requirements Vahid Jalali October 2007 Amirkabir university of technology, Department of computer engineering and information technology,

Slides:



Advertisements
Similar presentations
Using the Crosscutting Concepts As conceptual tools when meeting an unfamiliar problem or phenomenon.
Advertisements

ISBN Chapter 3 Describing Syntax and Semantics.
Introduction to Software Engineering Dr. Basem Alkazemi
OASIS Reference Model for Service Oriented Architecture 1.0
Liang, Introduction to Java Programming, Sixth Edition, (c) 2007 Pearson Education, Inc. All rights reserved Chapter 1 Object-Oriented.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
Use-case Modeling.
Chapter 8: Web Ontology Language (OWL) Service-Oriented Computing: Semantics, Processes, Agents – Munindar P. Singh and Michael N. Huhns, Wiley, 2005.
Architecture is More Than Just Meeting Requirements Ron Olaski SE510 Fall 2003.
Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering Vahid Jalali Amirkabir university of technology, Department of computer.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
CSCI 3 Introduction to Computer Science. CSCI 3 Course Description: –An overview of the fundamentals of computer science. Topics covered include number.
1 درس مهندسي نيازمندي استاد دكتر عبداله زاده دانشجو خيرالنسا مرچانت Meaning of Requirement.
Requirements Engineering: A Roadmap Vahid Jalali Fall 2007 Amirkabir university of technology, Department of computer engineering and information technology,
Four Dark Corners of Requirements Engineering
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Dealing.
The Meaning Of Requirements Michael Jackson 07/10/96 By: A. Rasoolzadegan.
Reza Gorgan Mohammadi AmirKabir University of Technology, Department of Computer Engineering & Information Technology, Intelligent.
Software Requirements
Shiva Vafadar 1 آزمايشکاه سيستم های هوشمند ( Requirements Engineering : A Roadmap The Meaning Of Requirements.
Soft. Eng. II, Spr. 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 1 (cont ’d) Title : Client requirements (Review) Mandatory reading: I.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Goal.
SE 555 – Software Requirements & Specifications Introduction
Describing Syntax and Semantics
Dealing with NFRs Vahid Jalali Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory,
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Towards.
Requirement engineering for an online bookstore system
The Software Development Life Cycle: An Overview
Software engineering. What is software engineering? Software engineering is an engineering discipline which is concerned with all aspects of software.
Chapter 7. Statistical Intervals Based on a Single Sample Weiqi Luo ( 骆伟祺 ) School of Software Sun Yat-Sen University : Office.
A GENERIC PROCESS FOR REQUIREMENTS ENGINEERING Chapter 2 1 These slides are prepared by Enas Naffar to be used in Software requirements course - Philadelphia.
Assurance Report on Controls at Service Organizations SAE 3402
Overview of Formal Methods. Topics Introduction and terminology FM and Software Engineering Applications of FM Propositional and Predicate Logic Program.
Constraint Satisfaction Problems (CSPs) CPSC 322 – CSP 1 Poole & Mackworth textbook: Sections § Lecturer: Alan Mackworth September 28, 2012.
Requirements1. Requirements: First Ideas Requirements should state what a system will do but not how it will be done. A basic question in Requirement.
111 Protocols CS 4311 Wirfs Brock et al., Designing Object-Oriented Software, Prentice Hall, (Chapter 8) Meyer, B., Applying design by contract,
ISBN Chapter 3 Describing Semantics -Attribute Grammars -Dynamic Semantics.
1 Identifying System Requirements. 2 Agenda Identifying System Requirements –Stakeholder Needs –Features Project Scope Stakeholder Classifications.
CSC 402 Fall Ambiguity Common signs on escalators in the UK What do they mean? –if I carry two pairs of new shoes I just bought? –if I have no shoes?
IS 325 Notes for Wednesday August 28, Data is the Core of the Enterprise.
Class diagram Used for describing structure and behaviour in the use cases Provide a conceptual model of the system in terms of entities and their relationships.
Semantic web course – Computer Engineering Department – Sharif Univ. of Technology – Fall Knowledge Representation Semantic Web - Fall 2005 Computer.
Artificial Intelligence Lecture 1. Objectives Definition Foundation of AI History of AI Agent Application of AI.
Programming Languages and Design Lecture 3 Semantic Specifications of Programming Languages Instructor: Li Ma Department of Computer Science Texas Southern.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Software Engineering Chapter 10 Formal Specification Ku-Yaw Chang Assistant Professor Department of Computer Science and Information.
MDA & RM-ODP. Why? Warehouses, factories, and supply chains are examples of distributed systems that can be thought of in terms of objects They are all.
Slide 1 A Reference Model for Requirements and Specifications NOTES.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Liang, Introduction to Java Programming, Sixth Edition, (c) 2007 Pearson Education, Inc. All rights reserved Object-Oriented Design.
Business Rules 12 th Meeting Course Name: Business Intelligence Year: 2009.
Chapter 3: Modeling Data in the Organization. Business Rules Statements that define or constrain some aspect of the business Assert business structure.
1 Specification A broad term that means definition Used at different stages of software development for different purposes Generally, a statement of agreement.
CSC3315 (Spring 2009)1 CSC 3315 Languages & Compilers Hamid Harroud School of Science and Engineering, Akhawayn University
Choosing a Formal Method Mike Weissert COSC 481. Outline Introduction Reasons For Choosing Formality Application Characteristics Criteria For A Successful.
1 Software Requirements Descriptions and specifications of a system.
 System Requirement Specification and System Planning.
Political Philosophy: Introduction Political Philosophy can be boiled down to 2 principal questions: Political Philosophy can be boiled down to 2 principal.
COP Introduction to Database Structures
INTRODUCTION The economies of ALL developed nations are dependent on software. More and more systems are software controlled Software engineering is concerned.
Bias.
Chapter 11 Object-Oriented Design
The Systems Engineering Context
Ontology From Wikipedia, the free encyclopedia
Chapter 7: Entity-Relationship Model
(Additional materials)
B (The language of B-Method )
Behavioral goal specialization
Measurement What is it and why do it? 2/23/2019
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Presentation transcript:

The meaning of requirements Vahid Jalali October 2007 Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

A couple of basic questions  What is requirement? A condition over phenomena of the environment  What is specification? Restricted form of requirement Providing enough information for the implementer Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Importance of requirements  Reliance of human beings on computer-based systems  Criticalness and cruciality of these computer-based systems Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Requirements Dos and Does nots  Do not directly concern machine  Concern the environment of the machine Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Shared Phenomena  Common phenomena between machine and environment Controlled by machine Controlled by environment  Used as a bridge between machine and private phenomena Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Affecting private phenomena Machine Shared Phenomena Private Phenomena Direct Indirect Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Optative and Indicative  Describing a requirement Desired condition over the phenomena of the environment Given properties of the environment regarding shared phenomena Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Optative and Indicative (Cont.)  Optative : A customer requirement R expresses a condition over the phenomena of the environment that we wish to make true by installing the machine  Indicative : An environment assertion E expresses a condition over the phenomena of the environment that we know to be true irrespective of the properties and behavior of the machine Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Optative and Indicative (Cont.)  Distinction between optative and indicative Is time independent The environment properties that guaranteed by the environment itself are indicative The environment properties that are to be guaranteed by the machine are optative Is also applicable to description of an agent Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Requirement engineering  Which kind of description to regard, optative or indicative? Actually both of them  Reasons for regarding indicative descriptions in addition to optative ones Understanding the environment Assuring satisfiablity of requirements Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Assuring satisfiablity  A couple of conditions should hold a machine whose behavior satisfies S is installed in the environment Environment has the properties described in E Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Formalism  Elevate the accuracy of descriptions  Computer can be treated as a formal system  Environment on contrast can not  Formalism impels no extra constraints on environment  Formalism can be met through using ground terms in a description Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Ground terms  Have clear and unambiguous meaning  Fix relationship between description and what it describes  Are captured by a tool named designation Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Designation  A designation associates a formal ground term, such as a predicate, with the denoted phenomena, such as an event or entity class or a relationship over events or entities  Appropriately chosen and carefully written designations provide a strong and narrow bridge between the environment and its description in requirements Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Designation (Cont.)  define the scope of a requirement  clarify the meaning of the descriptions  allow these descriptions to be subjected to the test of falsifiability  allow us to reason more reliably about the environment  Convince satisfaction of our specification will guarantee satisfaction of the requirements Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Designation Vs definition  Both underpin an essential discipline in description  Every term used in every description must be either designated or defined  Definition defines new terms on the basis of terms previously designated or previously formally defined Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Designation Vs definition (Cont.)  Definition provides more convenient terminology for saying what we could have said less conveniently Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007

Reference  [1]. M.Jackson, “The meaning of requirements,” Annals of Software Engineering Special Issue on Software Requirements Engineering Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, Requirement engineering course, Fall 2007