University of Toronto University of Toronto Department of Computer Science Department of Computer Science Today s Menu CSC2106S Requirements Engineering This This Week Week Aims Aims of of the the course course Syllabus Syllabus Readings Readings What are What are Requirements Requirements Prof Steve Easterbrook sme cs toronto edu http www cs toronto edu sme CSC2106S Next Next Week Week Engineering Engineering Context Context Systems Systems Thinking Thinking Role Role of of Modeling Modeling 2000 2004 Steve Easterbrook 1 University of Toronto 2000 2004 Steve Easterbrook University of Toronto Department of Computer Science Definition of RE Not a phase or stage Communication is as important as the analysis Quality means fitness for purpose Cannot say anything about quality unless you understand the purpose Examine the state of the art for research practice in Requirements Engineering Role of RE in software and systems engineering Current techniques notations methods processes and tools used in RE Designers need to know how and where the system will be used Requirements are partly about what is needed Gain practical experience in selected RE techniques Understand the essential nature of RE Breadth of skills needed for RE and the many disciplines on which it draws Contextual factors practicalities and partly about what is possible Gain a basic grounding for research in RE Methodological issues for RE research Current research issues direction of the field Awareness of the literature Need to identify all the stakeholders not just the customer and user 2000 2004 Steve Easterbrook Department of Computer Science Course Objectives Requirements Requirements Engineering Engineering RE RE is is aa set set of of activities activities concerned concerned with with identifying identifying and and communicating communicating the the purpose purpose of of aa software intensive software intensive system system and and the the contexts contexts in in which which itit will will be be used used Hence Hence RE RE acts acts as as the the bridge bridge between between the the real real world world needs needs of of users users customers customers and and other other constituencies constituencies affected affected by by aa software software system system and and the the capabilities capabilities and and opportunities opportunities afforded afforded by by softwaresoftwareintensive intensive technologies technologies 2 3 2000 2004 Steve Easterbrook 4 University of Toronto University of Toronto Department of Computer Science Teaching and Assessment Syllabus 1 x 2 5 hour seminar per week 13 weeks Discussion of weekly reading material Student presentations Plus typically up to 1 hour of lecture material from me Weekly readings plus various background reading Assessments literature survey on a topic of your choice practical project applying 1 or more RE techniques oral presentation on one or other of the above class discussion lead a discussion on weekly reading 2000 2004 Steve Easterbrook Advanced Topics Inconsistency and Uncertainty in RE Use of Formal Methods in RE Research methodology for RE 5 University of Toronto Basic RE activities Planning and Eliciting Requirements Modelling and Analysing Requirements Communicating and Agreeing Requirements Realizing and Evolving Requirements Will be available on the course website 40 40 10 10 Introductory stuff What are Requirements What is Engineering What is a System 1 or 2 papers per week must read before the seminar 2000 2004 Steve Easterbrook What are Requirements Engineering Engineering Engineering Engineering as a profession projects lifecycles design General systems theory Formal foundations of software systems Conceptual foundations of information systems Empirical foundations of human activity systems Observability of systems Stakeholders User Classes System boundaries Goals Scenarios Elicitation techniques What is a System Elicitation Targets What is Engineering Department of Computer Science II Eliciting and Planning Scope for this course Software intensive Systems Separating the Problem from the Solution What Requirements Engineers do 6 University of Toronto Department of Computer Science I Introductory Stuff Department of Computer Science Interviews questionnaires surveys meetings Prototyping Ethnographic techniques Knowledge elicitation techniques Conversation Analysis Text Analysis The Feasibility Study Types of Feasibility Cost benefit analysis Risk Analysis Identifying and managing risk 2000 2004 Steve Easterbrook 7 2000 2004 Steve Easterbrook 8 University of Toronto University of Toronto Department of Computer Science III Modelling Analysing Basics of modelling Notations and their uses Formality and Expressiveness Abstraction and Decomposition Model management and viewpoints Types of Analysis Behaviour Enterprises Information Structures Taxonomies of NFRs Performance Usability Safety Security Reliability Maintainability Software Evolution Laws of evolution Release planning Product families Requirement Reuse Prototyping and Walkthroughs Requirements and Architectures Architectural Patterns and Description Languages Mapping requirements to architectures Architectural Robustness Traceability and Rationale Representing argumentation and rationale Computer supported negotiation Trade off analysis Release planning 10 University of Toronto Department of Computer Science Extensive list of books and papers no one textbook covers the field well this course is research oriented we ll rely on recent papers more than books most of the papers are available electronically feel free to contact researchers directly for more papers info tools etc Managing Inconsistency On the inevitable intertwining of inconsistency and change Learning from inconsistency Feature interaction Living with inconsistency To help navigate the literature http www cs toronto edu sme CSC2106S readings pdf provides a detailed bibliography arranged according to the topics on this course http easyweb easynet co uk iany reviews reviews htm Book reviews by Ian Alexander Managing Change http www rmplace org Baselines and change requests Configuration management and version control Impact Analysis 2000 2004 Steve Easterbrook Negotiation and Prioritization Bibliography Pre and Post traceability Capturing Design Rationale Traceability techniques 2000 2004 Steve Easterbrook Department of Computer Science Effectiveness of Inspection Conducting an Inspection Collaborative Requirements Workshops