Software Engineering II (SE011)

NTA

STATEMENT ABOUT ACADEMIC HONESTY AND INTEGRITY

GSEI defines academic integrity as the pursuit of scholarly activity in an open, honest and
responsible manner. All students should act with personal integrity, respect other students’
dignity, rights and property, and help create and maintain an environment in which all can
succeed through the fruits of their efforts.

Dishonesty of any kind will not be tolerated in this course. Dishonesty includes, but is not
limited to:

 cheating,

 plagiarizing,

 fabricating information or citations,

 facilitating acts of academic dishonesty by others,

 having unauthorized possession of examinations,

 submitting work of another person or work previously used without informing the
instructor,

 or tampering with the academic work of other students,

 Students who are found to be dishonest will receive academic sanctions and will be
reported to the Head of Department’s office for possible further disciplinary
sanction.
Module name Software Engineering II
Course Name Diploma in Software Engineering
Course Code SE011
Course Length 1 Semester
Aims
Software Engineering II aims to empower the students with the theoretical and practical skills of
software engineering that will enable them to gain understanding of how to develop reliable software
other than programming, including testing, bug finding, verification, and methodologies for
constructing robust code. It emphasizes on modern technology for developing reliable software at
reasonable cost.

Module Instructors Matheus PN Matheus

Credits
Pre-requisites SE010
NQF Level 5
Notion Hours
Method of delivery
Lectures - 4 hours/week for 16 weeks
Tutorials - none,
Labs - 2 hours/week for 16 weeks
Assignments - Total 16 hours of assignments (average 1 hour/week for 16 weeks)
Self-Study - 4 hours/ week for 16 weeks

Objectives
 To help students to develop advanced skills that will enable them to construct software of high
quality – software that is reliable, and that is reasonably easy to understand, modify and
maintain;
 To give students an understanding of how to ensure software quality and reliability through
many different methods that are applied at different stages of software development;
 To give students an understanding of project management skills; and
 To help students to attain skills of how to manage large software systems.

Learning Outcomes
 Author a software requirements specifications document;
 Demonstrate knowledge of requirements modeling;
 Interact with a client to elicit input, and communicate progress;
 Explain how software quality is achieved;
 Demonstrate an understating of software review technique;
 Demonstrate an ability to test different applications;
 Display knowledge of Software Quality Assurance plan;
 Recognize the need for software testing;
  Show an understanding of how software is tested; and
 Demonstrate proficiency in debugging.

Course Rationale
Software Engineering is difficult to teach and to learn in a university environment. Most of
the important lessons of software engineering only apply to large scale software
development, i.e. to systems that are bigger than it is possible for a small group of students
to build in one or two terms. The skills needed to develop such systems have very little to do
with the type of programming that most students learn at University. In fact, software
engineering has very little to do with programming at all. Software Engineering is about the
discipline needed to develop high quality software that can be understood, maintained and
adapted over long periods of time by many different people. ‘Quality’ is a key word here.
The notion of quality for software is different from the notion of quality for other types of
engineered systems (electrical, mechanical, etc), because software is different from physical
systems (during the course we'll examine why). The notion of quality for software is also
different from the notion of quality for programs that students build on programming
courses. An understanding of what software quality really means is central to understanding
what software engineering is all about.

The course attempts to foster an understanding of software quality: what it is, and how to
achieve it. We do this through the use of a team project running throughout the course, in
which teams trade software modules with one another. By attempting to understand,
assess, and modify one another’s programs, students will gain insight into the nature of
software quality, and why an ability to program is not sufficient for the construction of high
quality software.

Assessment
Assessment will be based on a continuous assessment contributing 40% and the final
examination contributing 60%. Continuous assessment will be comprised of:
 2 Tests each contributing 10%
 2 Major assignment contributing 10%

The final examination will be done at the end of the subject teaching. Only candidates with
40% and above in the continuous assessment will be allowed to write the examination.
Candidates obtaining a combined mark between 45% - 49% will be eligible to sit for a
second opportunity supplementary examination in which a mark of less than 50% will be
deemed as fail. Supplementary examination candidates who pass the examination will be
awarded a mark of 50% for the subject, regardless their performance in the examination.
The following is the subject grading:

Grading:

Below 45% - Fail

Below 45% to 49% - Fail (supplementary examination allowed)
50% to 59% - Pass
60% to 69% - Credit
70% to 74% - Merit
75% and above - Distinction

Moderation

All tests and assignments will be internally moderated by a second internal examiner from
the National Software Engineering Academy other than the lecturers teaching the subject.
The final examination will be moderated by an external examiner, who shall be appointed by
the National Software Engineering Academy as a recognized practitioner or expert in the
subject/course, following the college guidelines for the appointment of external
examinations.

Course Content

CHAPTER 1 REQUIREMENTS MODELING: SCENARIOS, INFORMATION, AND

ANALYSIS CLASSES
6.1 Requirements Analysis
6.2 Scenario-Based Modeling
6.3 UML Models That Supplement the Use Case
6.4 Data Modeling Concepts
6.5 Class-Based Modeling

CHAPTER 2 REQUIREMENTS MODELING: FLOW, BEHAVIOR, PATTERNS, AND

WEBAPPS
7.1 Requirements Modeling Strategies
7.2 Flow-Oriented Modeling
7.3 Creating a Behavioral Model
7.4 Patterns for Requirements Modeling
7.5 Requirements Modeling for WebApps

CHAPTER 3 QUALITY CONCEPTS

14.1 What Is Quality?
14.2 Software Quality
14.3 The Software Quality Dilemma
14.4 Achieving Software Quality
Test 5
Assignment 3

CHAPTER 4 REVIEW TECHNIQUES

15.1 Cost Impact of Software Defects
15.2 Defect Amplification and Removal
15.3 Review Metrics and Their Use
15.4 Reviews: A Formality Spectrum
15.5 Informal Reviews
15.6 Formal Technical Reviews

CHAPTER 5 SOFTWARE QUALITY ASSURANCE

16.1 Background Issues
16.2 Elements of Software Quality Assurance
16.3 SQA Tasks, Goals, and Metrics
16.4 Formal Approaches to SQA
16.5 Statistical Software Quality Assurance
16.6 Software Reliability
16.7 The ISO 9000 Quality Standards
16.8 The SQA Plan

CHAPTER 6 SOFTWARE TESTING STRATEGIES

17.1 A Strategic Approach to Software Testing
17.2 Strategic Issues
17.3 Test Strategies for Conventional Software
17.4 Test Strategies for Object-Oriented Software
17.5 Test Strategies for WebApps
17.6 Validation Testing
17.7 System Testing
17.8 The Art of Debugging

Laboratory:

None

Study Materials

Required Book:

Roger S. Pressman, Ph.D., (2010). Software Engineering. (7th edition). New York, NY

10020: The McGraw-Hill Companies.

Recommended Books:

Frederick P. Brooks Jr. (1995) The Mythical Man-Month: Essays on Software Engineering.
Anniversary Edition (2nd Edition) Paperback. 0-201-83595-9.

Michael R. Lyu. Handbook of Software Reliability Engineering. McGraw-Hill (1996).

9780070394001

Websites:

[Link],. (2015). Software Engineering - Free Computer-Science Video Lectures.

Retrieved 9 October 2015, from [Link]
[Link]

OpenCourseWare, M. (2015). Unit 1: Software Engineering | Introduction to Electrical

Engineering and Computer Science I | Electrical Engineering and Computer Science | MIT
OpenCourseWare. [Link]. Retrieved 9 October 2015, from
[Link]
to-electrical-engineering-and-computer-science-i-spring-2011/unit-1-software-engineering/

Authorisation:
This course is authorized for use by:

___________________________________ __________________________

Head of Department Date

ACKNOWLEDGEMENT BY STUDENT

(To be completed by all students doing the course, detached from the course
outline and kept for record purposes in the department)

I, ___________________________________________________________________________,

With student number____________________________________________, herebyacknowledge

that I have received this course outline for Software Engineering I in semester 1
(2014), and that I have acquainted myself with its content, in particular the
statement about academic honesty and integrity. I agree to abide by the Policies
and arrangements spelt out in this course outline.

_____________________________________ _____________

Student Signature Date