Prof. Sotirios Liaskos
E-mail: liaskos@yorku.ca
Phone #: 416 736 2100 (x33862)
This page contains general information about the course;
nothing more will be posted here throughout the term.
Registered students should use
for current information!
Please follow this link to login to Moolde.
Use your Passport York to Login
ITEC4040
is an introductory course to Requirements Engineering and Management. We first
look at the basic theories and frameworks for understanding system requirements
and the corresponding activities and representations. We examine the early
stages of requirements: establishing project feasibility, performing early goal
analysis, identifying and representing project risks. We then take a thorough,
practical view of requirements elicitation and move into early modeling. We
look at both traditional modeling paradigms, such as Context Diagrams and DFDs,
UML-based such as activity diagrams, as well as modern business process
modeling notations such as BPMN. We also take a thorough look at multi-agent
goal modeling using i*.
At
later stages of the course, we look at more detailed models of software
requirements predominately based on UML (use case diagrams, interaction
diagrams, statecharts) and focus on producing the
requirements specification document. At the same time a variety of topics
pertaining to requirements are covered such as non-functional requirements,
requirements validation and verification, requirements formalization and
analysis, requirements prioritization, and other special topics.
This
section of the course is largely practice-oriented and course meetings
("lectures") rely on students collaboratively working on given
examples. Coursework typically involves one or two exams and a group term
project featuring elicitation and validation sessions with your (real or mocked
by the instructor) client, written deliverables and group presentations.
At the end of the course, students will have a deeper knowledge of issues
pertaining to requirements elicitation, modeling, analysis and documentation,
and will have acquired the necessary toolset to address the challenges that
modern requirements engineering projects pose.
For current details on the course scheduling,
evaluation etc. please refer to the MOODLE page.
Gerald Kotonya
and Ian Sommerville. Requirements engineering : processes and
techniques. Chichester; New York: J. Wiley & Sons, c1998. ISBN:0471972088
Axel van Lamsweerde, Requirements Engineering. Wiley, 2009. ISBN-10: 0470012706
3010/4010 Textbook: John W. Satzinger,
Robert Jackson and Stephen Burd. Systems Analysis
and Design in a Changing World. (4th Edition or later) Course
Technology, 2007. (ISBN: 1-4188-3612-5)
Prerequisites:
General prerequisites; AP/ITEC 3220 3.00 or SC/CSE 3421 3.00. Recommended:
AP/ITEC 4010 3.00. Course credit exclusions: None. Prior TO FALL 2009:
Prerequisites: General prerequisites; AS/AK/ITEC 3220 3.00 or AS/AK/ITEC 3421
3.00 or AS/AK/SC/COSC 3421 3.00 or AS/AK/SC/CSE 3421 3.00. Recommended:
AS/AK/ITEC 4010 3.00. Course credit exclusion: AK/ITEC 4040 3.00..
A typical evaluation scheme is as
follows:
A
typical term is organized as follows:
Week 1. Introduction to Requirements Engineering –
Theories of Requirements
Week 2. Early Requirements Analysis, Goal Analysis,
Feasibility and Risk Analysis.
Week 3. Requirements Elicitation
Techniques
Week 4. Requirements Elicitation Exercise.
Week 5. Early Requirements Modeling (goals): i* goal models, KAOS goal modeling
Week 6. Early Requirements Modeling (process): Activity Diagrams, Business
Process Modeling, DFDs
Week 7. Interim Presentation.
Week 8-10. Detailed Modeling with UML and other formalisms.
Week 11. Non-functional requirements
and requirements authoring.
Week 12. Requirements Prioritization
and Validation.
Week 13. Requirements Validation and
Verification.
Students
are referred to the departmental course pages with official policies and directions regarding exam
deferrals, special accommodations etc.
Please show professionalism
in all your correspondence.
See you in class!! (and Moodle)