THE UNIVERSITY OF LAHORE
Course Outline
Session 2016-17
Software Requirement Engineering
SCU 3 Credit(s)Weekly tuition pattern 2 session lecture (90 min)
Pre Requisit Introduction to Software Engineering
Teaching Team Dr. Ahmad Salman KhanAssistant Professor, University of Lahore
1-Course Description
Requirements engineering is a critical and fundamental part of software development process. Requirements engineering discipline covers a vast range of activities including requirements elicitation, requirements analysis, requirements documentation, requirements validation and requirements management. Success of software development project is depended on the enactment of requirements engineering phase. It is the phase where system stakeholders make decision regarding scope, features, functionality and constrains on the system to be developed.
This courses presents an overview of the fundamentals of requirements engineering and discusses in detail the processes and practices important to elicit requirements, techniques for requirements analysis, guidelines/methods for requirement specification development, system modeling perspectives, techniques for requirements validation and critical issues of requirements management.
2-Objectives
The goal of this course is to:
1. Provide student with detailed body of knowledge in the area of requirements engineering
2. Describe different phases of requirements engineering
3. Prepare and train students for eliciting, analyzing and managing requirements in industrial setting
3-Outcomes
At the successful completion of this course students should be able to: 1. Understand the key knowledge area of requirements engineering 2. Understand different phases of requirements engineering
3. Apply requirements engineering practices in industrial setting
4-Course Structure
1. Presentation by lecturer
2. Class Activities, assignments, quiz 3. Project
4. Exams
5-
Course Duration
This course will be held twice a week having a session of 90 minutes duration The course will be held for 16 weeks.
The course will be delivered in a classroom environment.
7-
Text and Other Resources
7.1 Text
1. Book1: Software Requirements by Karl E Weigers
2. Book2: Requirements Engineering: Processes and Techniques by Gorald Kotonya and Ian Sommerville
7.2 Other Resources
1. Book3: Requirements Engineering: From System Goals to UML Models to Software Specifications by Axel Van Lamsweerde
8-
Course Outline
Wee k
Topics, sub topics Literature
1 Introduction
Introduction to requirements engineering, FAQs about requirements, RE cost, requirements document, users of requirements document, relationship between requirements and design, system stakeholders, business requirements, user requirement, system requirement, functional requirement, non functional requirement, feature, sign off, requirements risks, Benefits from a High-Quality Requirements Process,
Book2 CH1 Book 1
2 Requirement Engineering Processes
Introduction, inputs/outputs of RE process, Process models, coarse grain, fine grain, role action, entity relationship, RE process activities, overview of requirements elicitation, requirements analysis, requirements documentation, requirements validation, Requirements Management, Project scope and vision, Goal modeling
Book2 CH 2 Book 3 CH7
3 Requirements Elicitation
Introduction, user classes, Establishing business requirements, Requirements sources, discovering sources, discovering stakeholders, onion model, system beneficiaries, interfacing stakeholders, negative stakeholders, sponsor and champion, managing stakeholders, analyzing influences, prioritizing stakeholders
Book1 CH6
4 Requirements Elicitation Techniques
Interview, steps for conducting interviews, scenarios, workshops, Focus groups, Questionnaires, use cases, ethnography, prototyping, throwaway prototype, evolutionary prototype, Planning elicitation, preparing for elicitation, performing elicitation activities, followup
after elicitation, classifying customer input, finding missing requirements
5 Understanding user requirements
Use cases and user stories, use cases and usage scenarios, identifying usecases, exploring use cases, validating use cases, usecases and functional requirements, benefits of usage centric requirements
Book1 CH 8
6 Documenting requirements
The requirements specification, labeling requirements, dealing with incompleteness, user interface and SRS, SRS template, Requirements specification and agile projects, writing excellent requirements, characteristics of excellent requirements, complete, correct, feasible, unambiguous, verifiable, traceable, guidelines for writing
requirements
Book1 CH10,11,App C
7 Software quality attributes
Introduction, exploring quality attributes, definition quality attributes, external quality attributes, internal quality attributes, quality attributes tradeoffs, constraints, goals and non functional requirements, Metrics for measuring non-functional requirements
Book1 CH12
8 Mid Term
9 Requirements Analysis, Prioritization
setting up priorities, prioritization techniques, in or out, pairwise comparison, 100 dollar test, Analysis of the Information Collected in the Elicitation and Gathering, Enumerating Requirements,
Requirements Completeness, Requirements feasibility, Forming requirements clusters, duplicate requirements, inconsistent
requirements, requirements prioritization rules, Dominant factor first, Most linked first, First come first served, Quickest (or the smallest) first, Highest benefit, Lowest cost, Tardiest first, Penalty, Most urgent first
Book1 CH16
10 Requirements Validation
Requirements Validation Objectives, difference between
requirements analysis and requirements validation, Validation inputs and outputs, Requirements reviews, Review checklists, Prototyping for validation, Requirements testing, Test case definition,
Requirements test form
Book1 CH17
11 Requirements Management
Major requirements management activities, change control, version control, requirements status tracking, requirements tracing, The Requirements Baseline, Requirements Management Procedures, Version control mechanism, Requirement Attributes for requirements management, Requirement Statuses, Managing Scope Creep, Change-Control Policy, The Change Control Board (CCB)
Book1 CH31
12 Requirements Traceability
forward to requirements, backward from requirements, forward from requirements, backward to requirements, Traceability links, Types of traceability relationships, Requirements Traceability Matrix,
Cardinality between system elements, Two way traceability matrix, Requirements Traceability Procedure, Requirements Management Tools
13 Modeling the Requirements-1
Representation Technique for System external interfaces, context diagram, use case diagram, data flow diagrams, Sequence diagram, representation techniques for business process flow, Swimlane diagrams/ Activity diagram, Representation Technique for data definitions and data object relationships, Class diagrams, entity-relationship diagram
14 Modelling the Requirements-2
Generalization, aggregation, composition, Object-Oriented Static Modeling of the Banking System, Problem Description, Steps in Object-Oriented Analysis, Identification of Objects and Classes, Possible Objects in the ATM Domain, Entity Classes in the Banking System, Relationships between classes, Static Model for Problem Domain, System and object states, Complex logic, User interfaces, dialog map
15 Requirements Engineering Tools Book1 CH30
16 Final term exam
9-
Assessment Criteria
No. Assessment Percentage
1. Mid Exam 25%
2. Final Exam 45% 3. Quiz/Internal Assessment 10% 4. Term Project 20%
Total 100%
10-
Attendance Requirements
You are expected to attend all lectures, seminars, tutorials, or any other classroom activity. Where you fail to attend classes, you cannot expect the lecturer to brief you on what you have missed. You are responsible for your attendance, not the academic staff. Attendance at tutorials and lab sessions will be strictly monitored, and failure to attend will be taken into account.
11-
Submission and Collection of Assignment
All assignments should be handed in at the beginning of the class sessions when they are due. All assignments may be handed back during scheduled classes.
12-
General Information
Students are required to be familiar with the university code Conduct, and to abide by its terms and conditions.
12.1 Copying of Copyright Material by Student
A condition of acceptance as a student is the obligation to abide by the
University’s policy on the copying of copyright material. This obligation covers photocopying of any material using the University’s photocopying machines, and the recording off air, and making subsequent copies, of radio or television
broadcasts, and photocopying textbooks. Students who flagrantly disregard University policy and copyright requirements will be liable to disciplinary action under the Code of Conduct.
12.2 Academic Misconduct
Please refer to the Code of Conduct for definitions and penalties for Academic Misconduct, plagiarism, collusion, and other specific acts of academic dishonesty. Academic honesty is crucial to a student's credibility and self-esteem, and
ultimately reflects the values and morals of the University as a whole. A student may work together with one or a group of students discussing assignment content, identifying relevant references, and debating issues relevant to the subject. Academic investigation is not limited to the views and opinions of one individual, but is built by forming opinion based on past and present work in the field. It is legitimate and appropriate to synthesize the work of others, provided that such work is clearly and accurately referenced. Plagiarism occurs when the work (including such things as text, figures, ideas, or conceptual structure, whether verbatim or not) created by another person or persons is used and presented as one’s own creation, unless the source of each quotation or piece of borrowed material is acknowledged with an appropriate citation. Encouraging or assisting another person to commit plagiarism is a form of improper collusion and may attract the same penalties. To prevent Academic Misconduct occurring, students are expected to familiarize themselves with the University policy, the Subject Outline statements, and specific assignment guidelines. Students should also seek advice from Subject Leaders on acceptable academic conduct.
12.3 Guidelines to Avoid Plagiarism
Whenever you copy more than a few words from any source, you must
acknowledge that source by putting the quote in quotation marks and providing the name of the author. Full details must be provided in your bibliography. If you copy a diagram, statistical table, map, etc., you must acknowledge the source. The recommended way is to show this under the diagram. If you quote any statistics in your text, the source should be acknowledged. Again full details must be provided in your bibliography. Whenever you use the ideas of any other author you should acknowledge those, using the APA (American Psychological Association) style of referencing.
Students are encouraged to co-operate, but collusion is a form of cheating. Students may use any sources (acknowledged of course) other than the assignments of fellow students. Unless your Subject Leader informs you
otherwise, the following guideline should be used: Students may work together in obtaining references, discussing the content of the references and discussing the assignment, but when they write, they must write alone.
12.4 Referencing For Written Work
Referencing is necessary to acknowledge others' ideas, avoid plagiarism, and allow readers to access those others’ ideas. Referencing should:
1. Acknowledge others' ideas 2. Allow readers to find the source 3. be consistent in format and
4. Acknowledge the source of the referencing format
To attain these qualities, the school recommends use of either the Harvard or American Psychological Association style of referencing, both of which use the author/date.
12.5 Referencing Standards
APA style referencing
Approval
Designed by,Dr Ahmad Salman Khan
Assistant Professor Computer Science
Approved by,
Dr. Nadeem Ahmad
