ICS 413 Software Engineering

1
ICS 413Software Engineering
First Semester 2006 - 2007 (061) 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 1100 am 01 pm (S. M. W. )
  Excluding prayer times
• (Or by appointment)
• E-Mail smasaad_at_ccse.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 ICS 413 Software Engineering
• Class Time Sec01 S M W 0110 PM 200 PM Room
  24/174
• Sec02 S M W 1000 AM 1050 AM Room 24/146
• Text Book Software Engineering, by Ian
  Sommerville,
• Seventh Edition, Addison-Wesley, 2004, ISBN
  0-321-21026-3
• WebCT http//webcourses.kfupm.edu.sa/

4
Syllabus

• Catalog Course Description
• The software development process
• Software requirements and specification
• Software design
• Software verification and validation
• Software management
• Software tools.

5
Course Outline

• Introduction Chapters 1, 4
• Requirements Chapters 6-8
• Design Chapters 11, 13, 14, 16, 18
• Verification Chapters 22, 23
• Management Chapters 5, 25-27
• Evolution Chapters 21, 28, 29

6
The objectives of this course are

• To understand the importance of software
  engineering to computer science and the most
  important general approaches to structuring the
  software production process
• To analyse the requirements for a software system
  and produce a software design (including user
  interface) from requirements
• To use formal specification techniques to aid the
  specification process
• To appreciate the benefits and difficulties of
  performing software engineering in a group,
  including the development of requirements and
  design documents and interaction with a client
• To understand how reliability, reusability,
  verification and validation are vital concerns
  for any software engineering effort
• To understand the important issues for managing
  and supporting the software engineering process
  at both the group and individual level

7
Grading Policy

• Assignments 5
• Major 1 (7/10/2006) 15
• Major 2 (18/11/2006) 15
• Major 3 (18/12/2006) 15
• Final Exam 25
• 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.

8
General Policies

• Attendance will be taken every class. If the
  number of absences exceeds 20 of the held class
  DN grade will be reported.
• Submit your own work unless the assignment is
  specifically identified as a collaborative one.
• All assignments are due before the class on the
  due date late assignments will not be graded.
• Participation in the class is strongly encouraged
  and will be considered in the grading.
• No make up exams or quizzes will be given.

9
Methodology

• The course will be three 50-minutes classes a
  week, a total of 45 lectures. It will be used for
  lectures, exams and assignments discussion.
• We will spend enough time for every topic such
  that it will be covered thoroughly. Examples will
  be done in the class. Transparencies will be used
  to save the time of writing. Quizzes, homework
  and programming assignments will be given to
  complement what the student learns in the
  lecture. This material will be available in the
  course web page.
• To do well, the student must study and read the
  material explained in the class before attending
  the next class. This will help the student in
  understanding the material on time and also help
  him in asking related questions immediately. It
  will be better if the student can read the
  material before the class.

10
Course (Cont)

• Attendance is very important. Attendance is taken
  at the beginning of the class.
• By KFUPM regulations 9 unexcused absences will
  result in a DN grade.
• Late attendance is discouraged. Every two late
  attendance is considered one absence. Repeated
  late attendance is not permitted.
• A 0.5 mark will be deducted for every absence
  after the fourth absence.
• Official excuse for any absence of a class must
  be presented not later than a week after that
  class.
• Regular attendance by students is expected and
  required in all courses unexcused absences are
  not permitted. Any student in position of an
  excuse for officially authorized absence must
  present this excuse to the instructor no later
  than one-week following his resumption of class
  attendance. A WF grade should immediately be
  reported to the Dean of Admissions
  Registration, as soon as the student becomes
  eligible, without waiting for the end of the
  semester. - Extract from a memo from vice-rector
  dated September 8, 1996.

11
Course (Cont)

• Students must know and read the regulations.
• No makeup of quizzes or exams will be done. A
  student missing any of these with an official
  excuse, his marks will be adjusted accordingly.
• Cheating is not acceptable at any level,
  (Homework, Quizzes, exams and projects).
  Plagiarism, copying and other anti-intellectual
  behavior are prohibited by the university
  regulations. Violators may have to face serious
  consequences. See the attached clip from the
  university rules in Arabic. Regulations are
  stated on page 31 (copy enclosed).

12
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.

13
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.

14
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.

15
Regulations Regarding Cheating