SWE214 IntroductiontoSoftwareEngineering SoftwareRequirementsEngineering

1
SWE 214  Introduction to Software Engineering (S
oftware Requirements Engineering)
First Semester 2007 - 2008 (071) King Fahd
University of Petroleum Minerals Information
Computer Science Department
2
Instructor

• Information
• Dr. Sabri A. Mahmoud
• Office 22/148-4 Phone 1117
• Office Hours SMW 900 am 950 am, S 100 pm
  150 pm,
• M 1200 pm 1250 pm (Or by
  appointment)
• E-Mail smasaad_at_kfupm.edu.sa
• Role
• Teaching and Assessment
• Expectation
• Students are encouraged to read the material
  before the class
• Students must always read the covered material
  after the class
• Grades are the responsibility of the student.

3
Course

• Information
• Course SWE 214 Introduction to Software Enginee
  ring  (Software Requirements Engineering)
• Class Time Sec01 SMW 1000 AM 1050 AM Room
  23/014
• Text Book Managing  Software  Requirements  A 
  Use  Case  Approach
• by Dean Leffingwell  Don Widrig, Addison Wes
  ley, 2003. 
• ISBN 0-321-12247-X 
• WebCT http//webcourses.kfupm.edu.sa/

4
Syllabus

• Catalog Course Description
• Study of software engineering process models, requ
  irements engineering process, and system models. 
• Methods, tools, notations, and verification and va
  lidation  techniques for the analysis and specific
  ation of software requirements. 
• Introduction to the principles of project manageme
  nt.
• Students participate in a group project on softwar
  e requirements. 

5
Course Outline

• Introduction Chapters 1-4
• Analyzing the problem Chapter 5
• Understanding User and Stakeholder Needs
  Chapters 8-13
• Defining the System Chapters 14-16
• Managing Scope Chapters 18,19
• Refining the System Definition Chapters 20-24
• Building the Right System Chapters 25, 27-29
• Agile Requirements Methods Chapter 30
• Your Prescription for Requirements Managements
  Chapter 31

6
The course objectives are

• To know and apply appropriate methods, techniques
  and tools to elicit, document and manage
  requirements.
• To be able to define a system that satisfies the
  requirements.
• To learn how to work in teams.

7
Course Learning Outcomes

• Upon  completion  of  the  course,  students 
  will  have the ability  to 
• For Course Objective 1
• Create a vision statement for a system and
  identify stakeholders
• Develop clear, concise, and sufficiently formal
  software requirements specifications based on the
  true needs of users and stakeholders.
• Verify and validate software requirements.
• Prioritize and manage requirements and resolve
  any conflicting requirements.
• For Course Objective 2
• Use appropriate CASE-tools for documenting
  software requirements
• Create a number of different UML models such as
  class model, use-cases, sequence diagram,
  activity diagram, and state charts.
• Apply storyboarding to define software features
• For Course Objective 3
• Be an effective member in software requirement
  team.

8
Grading Policy

• Home works 5
• Major 1 15 (October 22,  2007,  ??00 PM)
  
• Major 2 20 (December  3,  2007, 
  ??00PM) 
• Quizes 15 (22/9/2007, 7/11/2007,
  31/12/2007)
• Final Exam 20
• Lab Work/Project 25
• (distribution will be described in the lab)
• All assignments must be submitted on the due
  date. No late submission is allowed.

9
General Policies

• Attendance will be taken every class. If the numbe
  r of absences exceeds 9 classes, DN grade will be 
  reported. 
• Two late attendances are considered as one absence
  . 
• Official  excuse  for  any  class  absence  must 
  be  presented  within  one  week  after  that 
  class. 
• No make up exams or quizzes will be given. 
• All  grading  issues  must  be  resolved  within 
  a  week  after  the  return  of  graded 
  material. 
• Students  are  expected  to  regularly  check 
  the  course  website  on  WebCT  for  lecture 
  notes,  updates,  announcements,  etc. 
• Participation in the class is strongly encouraged.
   
• Plagiarism, copying and other anti-intellectual be
  havior are prohibited by the university regulation
  s.  Violators will face serious consequences. 

10
Expectation

• This course carries 3-credit hours. On the
  average about 3 hours/week/credit-hour of effort
  is expected from the student.
• The student is expected to interact with the
  instructor on a frequent basis and review the
  difficulties he is facing and get the material
  clarified. Such an effort will bring the student
  back to the flow of course otherwise he will lag
  behind and even the new material will become
  difficult to follow.
• Reading assignments will be given on a regular
  basis. The student is expected to read the
  assigned portions in order to gain the most out
  of the class.

11
Tips to the Students

• In order to do well in this course the following
  points are to be noted and considered in your
  planning
• Your attitude to learn and the effort you put in
  for this course alone will be the primary agents
  that guide you in this course.
• Emphasis is on reasoning and planned regular
  work towards this course and not on memorization.
• Taking notes is important. Once you take a note
  of what you consider to be important bits and
  pieces of information, write it down in your
  notes. On the same day after the class, review
  the relevant material and then prepare detailed
  notes. Such regular recollection, review,
  revision, and documentation will turn out to be
  very important in grasping the material and doing
  well in quizzes and examinations.
• Regular interaction during the class during the
  instructor's office hours is encouraged. There is
  nothing like a silly question. By raising doubts
  and posing questions, you will be helping
  yourself, others in the class, and the instructor
  in steering the coverage towards the weak points.
  So keep one thing in mind during this course
  it is better to raise a doubt or pose a question,
  rather than suppressing it and face difficulties
  later on.

12
Tips to the Students (Cont).

• If you do not follow the instructor's
  pace/language, request him to slow down.
  Likewise, when you do not understand certain
  words or sentences request for an alternative
  explanation.
• Reading, written programming assignments as
  well as quizzes, projects examinations are part
  and parcel of the course. They are expected to
  supplement the coverage in the class/lab. So
  treat them that way instead of facing them just
  as tests for evaluating your performance.
• There is no substitute for a regular (daily)
  preparation for this course. It will be far less
  effective, even if you spend two times more
  effort just before the examination days.
• Good luck and best wishes for a good semester.