SWE 311 Principles of Software Engineering - PowerPoint PPT Presentation

1 / 13
About This Presentation
Title:

SWE 311 Principles of Software Engineering

Description:

Plagiarism, copying and other anti-intellectual behavior are prohibited by the ... Violators will face serious consequences. Expectation. This course carries 3 ... – PowerPoint PPT presentation

Number of Views:97
Avg rating:3.0/5.0
Slides: 14
Provided by: scie370
Category:

less

Transcript and Presenter's Notes

Title: SWE 311 Principles of Software Engineering


1
SWE 311Principles of Software 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_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 SWE 311Principles of Software
    Engineering
  • Class Time Sec01 SMW 1100 AM 1150 AM Room
    24/273
  • Text Book Software Engineering, A Practitioner
    Approach, 6th ed.,
  • by Roger Pressman McGraw Hill, 2005.
  • ISBN 007-123840-9
  • 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 Chapter 1
  • Processes Chapters 2, 3
  • Requirements Chapter 7
  • Analysis Chapter 8
  • Design Chapters 9-12
  • Testing Chapters 13, 14
  • Management Chapters 21, 24

6
The course objectives are
  • To learn different software processes for
    producing software products.
  • To learn the complete software life cycle and
    understand its major activities such as software
    requirement, analysis, design, testing, and
    implementation.
  • To learn how to work in teams.

7
Laboratory Objectives
  • Provide students with the opportunity to
  • Undertake a significant software engineering
    project.
  • Implement a sound development process, covering
    all phases.
  • Work in teams. The leader position is rotated
    among members of the same team at different
    phases of the project.
  • Learn a number of Software Engineering tools
    during the lifecycle of the project.

8
Course Learning Outcomes
  • For Course Objective 1
  • 1. Select an appropriate and effective software
    process for a given project
  • For Course Objective 2
  • 2. Develop clear, concise, and sufficiently
    formal software requirements specification (SRS)
    based on the true needs of users and other
    stakeholders
  • 3. Apply design principles and architectures in
    designing software
  • 4. Create a number of different UML models such
    as class model, use-cases, sequence diagram,
    activity diagram, and state charts
  • 5. Apply a variety of testing techniques in
    software development
  • For Course Objective 3
  • 6. Develop a project plan for software
    development project and apply management
    techniques and work as a team leader and a member
    of a team.

9
Grading Policy
  • Home works 5
  • Major 1 15 (October 20,  2007,  ??00 PM)
  • Major 2 20 (December  1,  2007, 
    ??00PM) 
  • Quizes 15 (24/9/2007, 5/11/2007,
    29/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.

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

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

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

13
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.
Write a Comment
User Comments (0)
About PowerShow.com