CSC490 Software Engineering

INSTRUCTOR
Name: Ramzi A. Haraty
Email: rharaty@lau.edu.lb
Office: Nicol 509
Office Hours: MWF: 10:0 – 12:00

CURRENT CATALOG DESCRIPTION

This course presents the techniques for developing reliable, and cost-effective, medium-to-large-scale
with an emphasis on agile development methods appropriate for rapidly-moving projects. Basic
software development infrastructure; requirements elicitation and tracking; prototyping; basic project
management; basic UML; introduction to software architecture; design patterns; testing.

COURSE PREREQUISITE/CO-REQUISITE
CSC375: Database Management Systems.

TEXTBOOK AND REFERENCES

Ian Sommerville. Software Engineering. 10th Edition. International Edition. ISBN-13: 978-
0137035151. Pearson. 2016.

Further Reading and www Links

 http://www.comp.lancs.ac.uk/computing/resources/IanS/SE7/
 S.L. Pfleeger, J.M. Atlee. Software Engineering Theory and Practice. Prentice-Hall.
 L. Maciaszek, B.L. Liong. Practical Software Engineering a Case Study Approach. Addison-
Wesley.
 R. Pressman. Software Engineering. McGraw-Hill.

Other course notes will be provided as needed.

COURSE TYPE

Required Elective Selective Elective

COURSE LEARNING OUTCOMES

A student completing this course should:

 Demonstrate an understanding of the software development life cycle and basic process
models
 Demonstrate an understanding for requirements elicitation, specification, and validation
techniques
 Demonstrate an ability to manage a small size project
 Demonstrate the ability to use CASE and various software tools
 Demonstrate an ability to develop professional documents
 Demonstrate an ability to design medium‐scale programs

COURSE GRADING AND PERFORMANCE CRITERIA

Midterm 30%
Final 30%
Project* 40%

Guidelines for the Grading System:

Grade Quality Points Guidelines over 100

A 4  90
A- 3.67 87 – 89
B+ 3.33 83 – 86
B 3.0 80 – 82
B- 2.67 77 – 79
C+ 2.33 73 – 76
C 2 70 – 72
C- 1.67 67 – 69
D+ 1.33 63 – 66
D 1 60 – 62
F 0  59
P No quality Points
NP No quality Points
U No quality Points
W No quality Points
I No quality Points

*Project: group project extending over the semester to implement some of the methods discussed in
the course on a real-world case study. It will be graded based on effort, technical correctness, and
documentation.

ATTENDANCE POLICY
1. Students are held responsible for all the material presented in the classroom, even during their
absence.
2. Students can miss no more than the equivalent of five weeks of instruction and still receive credit
for that course.
3. Instructors have the right to impose specific attendance regulations in their courses, provided that
the above-stated limit of absences is not exceeded, and the minimum number of absences allowed
is no fewer than the equivalent of two weeks of classroom instruction, after the Drop and Add
period.
4. Instructors will inform the Departments Chairperson and the Guidance Office, of any prolonged
unexplained absence.
5. Students who exceed the allowed number of absences must withdraw from the course; otherwise,
the course grade will be recorded as “F” (NP).
WITHDRAWAL POLICY
“Students wishing to withdraw from one or more courses must follow the withdrawal procedure
provided by the Registrar’s Office. Students withdrawing from courses after the late registration
period and before the withdrawal deadline will receive Ws for all the courses in progress.” It is the
student’s responsibility to drop the course)

Course Evaluation: Completion of the online course evaluations is required.

Students will not be able to access their course grades until they
have completed the course evaluations.

TOPICS COVERED IN THE COURSE

Page 2 of 4
 Lecture / activity Textbook Chap.
Week (Sommerville)
1 Course Introduction and Organization 1
Introduction
2 Software Processes 2
3 Requirements Engineering 4
Group Project – Phase I
4 System Modelling 5
5 Architectural Design 6
6 Architecture Design (continued) 6
Group Project – Phase II
7 Software Testing 8

8 Software Testing (continued) 8

Midterm Exam
10 Project Management 22
11 Project Planning 23
12 Software Evolution 9
Group Project – Phase III 22
13 Project assignment-2 (Design)
14 Basic software project management 5
15 Software process models: evolutionary, component based, 4
incremental, spiral
15 Group Project – Phase IV (Prototype Demo)

POLICY ON CHEATING AND PLAGIARISM

Please refer to the Student Code of Conduct, particularly Appendix B
(http://www.lau.edu.lb/about/governance-policies/policies/student_code_of_conduct.pdf).

Student Code of Conduct - Academic Violations

The following table defines the sanction(s) associated with each violation. In some cases and when the
violation is too general, a range of sanctions is set for the pertinent committee to choose from depending on the

Page 3 of 4
specifics of each case. As for the second offense, the set sanctions apply regardless whether the violation has
taken place in the same course or a different one, within the same semester or not.

Code # Violation First Offense Second

Offense
Cheating
2.2.1 Using material or equipment (including mobile phones, zero on the F on the course
electronic tablets, i-pads, calculators, and other devices) deliverable with with a warning
that is not authorized by the instructor in an examination, a warning
project, or graded assignment
2.2.2 Cheating, copying, collaborating with or aiding another zero on the suspension
Student in a manner not permitted by the instructor on an deliverable with
examination, project, or other graded assignment a warning
2.2.3 Distributing or aiding in the distribution of previous double warning suspension –
exams without authorization of the instructor – suspension expulsion
2.2.4 Stealing, reproducing, or circulating an examination or suspension expulsion
other graded assignment before it has been administered
2.2.5 Impersonating another Student or allowing another suspension expulsion
Student to impersonate one’s self during an examination, for both
presentation, or other graded assignment
2.2.6 Impersonating an assistant, staff member, or faculty suspension – expulsion
member for the purpose of (a) proctoring examinations expulsion
without authorization or permission or (b) obtaining
confidential information regarding coursework or
examinations
2.2.7 Receiving, purchasing or selling a project, paper, or any suspension – expulsion
academic document and presenting it as work other than expulsion
that of the author
2.2.8 Submitting identical papers or coursework for credit in zero on the F on the course
more than one class without the permission of the deliverable with with a warning
instructor a warning
Plagiarism and Copyright Violations
2.2.9 Failing to attribute language or ideas to their original zero on the F on the course
source by not crediting the original author with an deliverable with with a warning
appropriate acknowledgement or citation a warning
2.2.10 Using photocopied or electronic copies of textbooks, warning double warning
compact disks, films, music, online course materials, and
other content beyond the fair use policy within University
Premises
2.2.11 Using copyrighted materials, including in written research warning double warning
reports and papers, without obtaining required
permission, if any, from the rights holder
Unauthorized Sale, Distribution, or Use of Course Materials
2.2.12 Recording any lecture or presentation for personal use or warning double warning
public distribution without the prior consent of the course
instructor. This applies to the unauthorized use of any
medium including but not limited to mobile phones,
electronic tablets, i-pads recorders, films, and other
devices
2.2.13 Selling academic materials by any Student, club, or group. warning double warning
This includes but is not limited to lectures, course
recordings, class notes, and previous exams

Page 4 of 4