Software Requirements

Engineering
Lecture 0 - Introduction
Welcome！

u Welcome to the course Software Requirements Engineering

u In this lecture we will:
u Discuss some key administrative issues.
u Describe what we’re going to do in this course
u Give a brief introduction about the software requirements
Teaching Staff

u Dr. Wanru Gao (Kelly) 高琬茹

u Email : iewrgao@zzu.edu.cn
u You can also send me message through DingTalk

u If you have any questions regarding this course and cannot find the answer
everywhere
u Use the discussion group in DingTalk
u For personal issues, please send Kelly an email with [IP] in subject line.
Schedule

u Lectures are held

every Tuesday through
DingTalk, from 10.10
to 11.50.
u Lab sessions will be
scheduled when
needed
Objectives

The Objective of this course is to introduce software requirements and to discuss

the processes involved in discovering and documenting these requirements.
After taking this course, you should obtain the following knowledge:
1. Understand the importance of requirement engineering in software
engineering
2. Understand the different type of requirements and how to document them
3. Understand the principal requirements engineering activities and the
relationships between them
4. Understand the necessity of requirements management
Course Outline

u Week 1: Introduction to Software Requirements

u Week 2: Software Engineering and Requirement Engineering
u Week 3: Types of Requirement
u Week 4: Software Requirements Elicitation
u Week 5: Software Requirements Elicitation: case study
u Week 6: Software Requirements Analysis
u Week 7: Software Requirements Documentation
u Week 8: Software Requirements Documentation 2
Course Outline

u Week 9: Requirements Validation

u Week 10: Requirements Management
u Week 11: Requirements Modeling Techniques
u Week 12: Requirements Modeling: Scenario-Based Methods
u Week 13: Requirements Modeling: Class-Based Methods
u Week 14: Requirements Modeling: Behavior-Based Methods
u Week 15: Case Study
u Week 16: Summary
Assessment

u There are three different types of assessment

u Examination: 70% (replaced assignment)
u Assignment & Quizzes: 10%
u Practical: 20%
Textbook/ References

u Textbook :
u Software
Requirement
Engineering, Karl
Wiegers and Joy
Beatty
u Software Engineering:
Ian Sommerville

u Lecture Slides: The

lecture notes are
available before the
lecture.
Academic Honesty

u Assignment work helps to develop your understanding and ability to apply

techniques.
u The best way to avoid the need to plagiarize is to start preparing your
assignments early. Don’t let your work get on top of you.

DOs and DON’Ts

• DO your own work.
• DON’T copy others’ work.
• DON’T let others to copy your work.
• DO feel free to discuss problems with your friends.
• DO seek help from lecturer when stuck.
• DO start your assignments early.
 IF YOU DON’T
DO THE WORK
YOU WON’T
HAVE THE KNOWLEDGE
AND YOU WON’T
PASS THE COURSE
The Course on One Slide

u By the end of this course you should be able to answer the following
questions:
Ø What is SRE?
Ø Why SRs are important?
Ø How to write a formal SR document?
u But all of these base on:
Ø You do all the work yourself
Ø You keep up with the viewings and readings
Ø You attend the lectures
Ø You take the opportunity to practice