Unformatted text preview:

University of Toronto Department of Computer Science Department of Computer Science University of Toronto Today s Menu CSC2106S Requirements Engineering This This Week Week Aims Aims of of the the course course Syllabus Syllabus Readings Readings What What are 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 of Modeling Role of Modeling 2000 2004 Steve Easterbrook 1 University of Toronto 2000 2004 Steve Easterbrook Department of Computer Science University of Toronto 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 the the purpose purpose 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 by by softwaresoftwareintensive intensive technologies technologies 2 3 2000 2004 Steve Easterbrook 4 1 Department of Computer Science University of Toronto University of Toronto Teaching and Assessment ARISE Video conferencing 1 x 3 hour seminar per week 13 weeks Discussion of weekly reading material Student presentations Plus typically up to 1 hour of lecture material from me ARISE is a collaborative venture IBM Toronto Lab and the Universities of Waterloo Toronto and York See http www softwareresearch ca for details Weekly readings Challenges Interaction Laptops and instant messaging during the class 1 or 2 papers per week must read before the seminar Community building Will be available on the course website Name tags exchange bios photos web addresses plus various background reading Assessments 40 40 10 10 Department of Computer Science ARISE research questions How to collect archive and index the classes 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 Communications from the instructor syllabus assignments lecture notes Postings to a Wiki or similar online discussion tool Audio Video of the seminars Instant messaging during the seminars Emails What would you give your consent to 2000 2004 Steve Easterbrook 5 2000 2004 Steve Easterbrook Department of Computer Science University of Toronto University of Toronto Syllabus Introductory stuff Basic RE activities What is Engineering Inconsistency and Uncertainty in RE Use of Formal Methods in RE Research methodology for RE 7 Engineering Engineering Engineering Engineering as a profession projects lifecycles design What is a System Advanced Topics 2000 2004 Steve Easterbrook What are Requirements Scope for this course Software intensive Systems Separating the Problem from the Solution What Requirements Engineers do Planning and Eliciting Requirements Modelling and Analysing Requirements Communicating and Agreeing Requirements Realizing and Evolving Requirements Department of Computer Science I Introductory Stuff What are Requirements What is Engineering What is a System 6 General systems theory Formal foundations of software systems Conceptual foundations of information systems Empirical foundations of human activity systems Observability of systems 2000 2004 Steve Easterbrook 8 2 Department of Computer Science University of Toronto II Eliciting and Planning Stakeholders User Classes System boundaries Goals Scenarios Interviews questionnaires surveys meetings Prototyping Ethnographic techniques Knowledge elicitation techniques Conversation Analysis Text Analysis Notations and their uses Formality and Expressiveness Abstraction and Decomposition Model management and viewpoints Types of Analysis The Feasibility Study Behaviour Activities and Interactions States and Transitions Concurrency Quality Requirements Enterprises Business rules and organisational structures Goals tasks and responsibilities Soft Systems analysis Information Structures Taxonomies of NFRs Performance Usability Safety Security Reliability Maintainability Entities and Relationships Classes and Objects Domain Ontologies Types of Feasibility Cost benefit analysis Basics of modelling Elicitation techniques III Modelling Analysing Elicitation Targets Department of Computer Science University of Toronto Risk Analysis Identifying and managing risk 2000 2004 Steve Easterbrook 9 2000 2004 Steve Easterbrook Department of Computer Science University of Toronto Validation Refutable descriptions Role of contracts and procurement Role of organisational politics Documenting Requirements Properties of a good specification Documentation standards Specification languages Making requirements testable Prototyping and Walkthroughs V Realizing and Evolving Reviews and Inspections Effectiveness of Inspection Conducting an Inspection Collaborative Requirements Workshops Software Evolution Negotiation and Prioritization Representing argumentation and rationale Computer supported negotiation Trade off analysis Release planning Laws of evolution


View Full Document
Loading Unlocking...
Login

Join to view CSC 2106S Syllabus and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view CSC 2106S Syllabus and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?