Faculty of Engineering andTechnolgy

Deparment of Computer Science

Course Title: Principles of Software Engineering
Code: CS-106
Coordinating Faculty/ Department: Faculty of Engineering and Technology department of
Computer Science
Credits: 04
Pre-requisites : NIL
Lecturer Name and Contact: Mashal Rokhan
+93782220771
[email protected]

GENERAL COURSE INFORMATION

Due to the organizational trends to computerize their businesses and other advancements in the society in
computer science industry it has been recognized that real world systems should be computerized in order to
improve their performance. It has been strongly recommended that the students should be familiarized with
knowledge of basic SW engineering methods and practices, and their appropriate application; Students should
know different kinds of projects/systems and should be able to understand its requirements and hence to prepare
the Software Requirement Specification (SRS) document. The student should understand how to model the
requirements as per the organizational needs and hence should be able to design those modeled requirements
for the proposed system.

COURSE OBJECTIVES
This course aims at introducing to the students about the product that is to be engineered and the process that
provides a framework for the engineering technology. The course facilitates the students to analyze risk in
software design and quality and to plan, design, develop and validate the software project. The course is inteded
to introduce the concepts and methods required for the construction of large software intensive systems. It aims
to develop a broad understanding of the discipline of software engineering. It seeks to complement this with a
detailed knowledge of techniques for the analysis and design of complex software intensive systems. It aims to
set these techniques in an appropriate engineering and management context. It provides a brief account of
associated professional and legal issues.

COURSE LEARNING OUTCOMES

After successful completion of this course, students will be able to:

1. Understand the different categories of software

2. Acquire Analytical skills and Compare software engineering, system engineering, and computer science
3. Leadership skills Critique the different process models used in software project development
4. Acquire collaboration and communication skills and also Analyze the various process models used in
software project development
5. Learn & Understand working in team various categories of Requirements
6. Get technical skills and Apply feasibility study report for software project development
7. Amass creativity skills and interpersonal skills also to Create SRS Document
8. Procure self-management and self-appraisal also to Design the software project of elicited requirements
9. Achieve technical skills and to Design the requirement using class and object diagram
10. Procure Creativity and to How to apply the software engineering lifecycle by demonstrating competence in
communication, planning, analysis, design, construction, and deployment
11. Acquire goals-oriented skills and to Demonstrate an understanding of and apply current theories, models,
and techniques that provide a basis for the software lifecycle
12. Obtain technical skills and to Demonstrate an ability to use the techniques and tools necessary for
engineering practice

LEARNING REFERENCES
Following resources will be used as references during teaching this course:

1. Roger Pressman, Software Engineering: A pracatitioner’s approach Latest Edition

2. Ian Sumerville, Software Engineering: Latest Edition
3. Various Websites

TEACHING METHODS
Following teaching methods will be adopted for the taught course:
1. Leacture:
2. Presentation:
3. Small talk
4. Group discussions

CLASSROOM ETIQUETTE:
Class room courtesy is expected of all students all the time. Following is general guideline for the class room
conduct:

1. Refrain from chatting with fellow students.

2. Arrive on time. If you come late please be courteous to other students
3. Do not get up and walk out halfway through class.
4. Do not cut the instructor off at the class.
5. All cell phones must be turned off during class and examination.
6. Eating is not permitted.
7. Above all please be cognizant of the learning process and purpose of you being in the
8. Class room and extend same respect to other students.

POLICIES / GUIDLINES
Guidelines for Format of Assignments: (General Recommendations)
1. Assignments must be submitted online using Kardan LMS
2. No Assignment will be accepted after the deadline
3. Hard copies of the assignment won’t be accepted
4. Assignments via e-mail won’t be accepted
5. Assignments need to be written by hands also students are obliged to upload the screen shots of the
assignments
6. Copied assignments will lead to the cancellations of the assignments of the respective students
7. Proper references relevant to the assignment must be included in the last page of the assignment
8. Students are also advised to include the table of contents in assignment

Note: All assignments and any work related to this work submitted will be subjected to plagiarism verification
by software.

COURSE SCHEDULE / CONTENTS

Topic
Outcomes
(List the topic
Week Suggested
Topics for Discussion Book Chapter # outcome in
No. Activity
alignment
with course
outcome)
1 Introduction Software engineering Lecture, Understand
FAQs about software engineering by IanSummerville group & clarify
Software chapter no 1 discussion
Types of Software Software engineering: Ethical and
Generic software A practitoner’s professional
Be-spoken software approach chapter 1 The Responsibiliti
Engineering muddiest es
Software Engineering point
Software Engineering vs computer
Science
Software Engineering vs system
engineering
Software Engineering Layers
Professional and ethical responsibilities of
software engineers
Software Crises
Attributes of quality software
2 The Process Softwaare Lecture, Understand,
Software Development Life Cycle Engineering: A group Explain and
Software Engineering: The Layered practitioner’s discussion analyze
Technology approach chapter # 2 One sentence Analytical
Process, Methods and tools summeries skills
A generic view of software engineering
The Software Process
Common Process framework
Framework Activities
Umbrella Activities
3 Software Development Life Cycle oftwaare Engineering: Lecture, Understand,
Different Phases of SDLC A practitioner’s group Learn and
Selecting SDLC for a project approach chapter # 2 discussion,
Process Models Software Engineering: simulations,
Selection criteria of process model for a IanSummerville Team-
project chapter # 4 working
The Build and Fix Process Model
 Topic
Outcomes
(List the topic
Week Suggested
Topics for Discussion Book Chapter # outcome in
No. Activity
alignment
with course
outcome)
Advantages and disadvantages of build
and fix model The
When to use build and fix model muddiest
point
4 The Linear Sequential Process Model Softwaare Lecture, Understand,
Advantages of Linear Sequential Model Engineering: A group Learn and
Disadvantages of Linear Sequential Model practitioner’s discussion,
When to use Linear Sequential Model approach chapter # 2 simulations,
The V-shaped Process Model Software Engineering: Team-
Advantages of V Model IanSummerville working
Disadvantages of V Model chapter # 4
When to use V Model

The
muddiest
point

5 Process Models Softwaare Lecture, Understand,

Prototyping Process Model Engineering: A group Explain and
Types of Prototyping process model practitioner’s discussion, analyze
Advantages of prototyping Model approach chapter # 2 simulations,
Disadvantages of prototyping Model Software Engineering: Analytical
When to use prototyping Model IanSummerville and
Incremental build Model chapter # 4 collaborative
Advantages of Incremental Build Model skills
Disadvantages of Incremental Build One minute
Model paper
When to use Incremental Build Model
6 Process Models Softwaare Understand,
Spiral Process Model Engineering: A and Analyze
Advantages of Spiral Model practitioner’s
Disadvantages of Spiral Model approach chapter # 2 Self-
When to use Spiral Model Software Engineering: organization
IanSummerville
chapter # 4

Process Models Softwaare Lecture, Understand

7 Agile Process Model Engineering: A group and analysis
Advantages of Agile Model practitioner’s discussion,
Disadvantages of Agile Model approach chapter # 2 self-appraisal
When to use Agile Model Software Engineering:
RAD Process model IanSummerville Brain
Advantages of RAD model chapter # 4 storming
Disadvantages of RAD model
When to use RAD model
 Topic
Outcomes
(List the topic
Week Suggested
Topics for Discussion Book Chapter # outcome in
No. Activity
alignment
with course
outcome)
Assignment 1
8 Component based software engineering Softwaare Lecture, Understand,
Who and what in software Engineering Engineering: A group Explain and
Quize 1 practitioner’s discussion, analyze
approach chapter # 2 simulations,
Software Engineering: Analytical
IanSummerville skills
chapter # 4
Opening
question
9 Software Requirements Software Engineering: Lecture, Understand
Functional and Non-Functional IanSummerville group and Learn
Requirements chapter # 6 discussion,
User Requirements audiovisual, Goal-oriented
System Requirements
User Interface Requirements
Domain Requirements One minute
paper
10 Requirement Engineering Process Software Engineering: Lecture, Explain and
Feasibility study IanSummerville group apply
Requirement Elicitation and Analysis chapter # 7 discussion
Requirement Validation Application Leadership
Requirement change management cards skills
11 Requirement Engineering Process Software Engineering: Lecture, Understand,
Requirements gathering process Activities IanSummerville group and apply
Requirement discovery chapter # 7 discussion,
Fact Find Techniques audiovisual Creativity
Assignment 2

The
muddiest
point
12 Requirement Classification and Analysis Software Engineering: Lecture, Understand,
Prioritization and negotiation Requirement IanSummerville group and apply
documentation chapter # 7 discussion,
Creating SRS Document audiovisual Creativity

The
muddiest
point
13 The Analysis Modeling Softwaare Lecture, Design ,
Data Modelling Engineering: A group create and
Functional Modeling practitioner’s discussion, application
Behavior modeling approach chapter # 12 audiovisual
Data Dictionary Technical
Quiz 2 One minute Skills
paper
 Topic
Outcomes
(List the topic
Week Suggested
Topics for Discussion Book Chapter # outcome in
No. Activity
alignment
with course
outcome)
14 Modelling DFD(Data Flow Diagram) Softwaare Lecture, Design and
Purpose of DFD Engineering: A group apply
Elements of DFD practitioner’s discussion,
Guidelines for developing DFD approach chapter # 12 Interpersonal
Context Diagram One- skills
Different Levels in DFD sentence
Example summary
Assignment 3
15 Behavior Modelling Softwaare Lecture, Explain,
State Transition Diagram(STD) Engineering: A group Design and
Elements of State Transition Diagram practitioner’s discussion, apply
Example approach chapter # 12
Use case Diagram Pre and post Team-
Components of use case diagram test working skills
Example
Quiz 3
16 Object Oriented Analysis and Design Softwaare Lecture, Clarify
Class diagram Engineering: A group Design, create
Components of class diagram practitioner’s discussion, and apply
Object diagram approach chapter # 20
Object oriented Analysis an example and 21 Technical
Object oriented design an example One-minute Skills
paper

COURSE ASSESSMENT
TYPE PERCENTAGE RATIONALE
Internal Assessment 25 % Equal weightage is assignments and quizzes and at
Assignments: 10% the same time emphasizing on the importance of
Quizzes: 10% class participation.
Attendance: 5%
External Assessment 75% Students develop an examination sense through
Midterm: 25% midterm examination hence 25% weightage is
Terminal: 50% appropriate. Midterm duly followed by terminal
examination providing 50% weightage which is an
opportunity to improve scores appropriately.
GRADING

MARK RANGE GRADE POINT GRADE EXPECTED RESULT

90 and above 4.0 A At least 25% expected to secure A
grade
80 – 89 3.0 B At least 35% expected to secure B
grade
70 – 79 2.0 C At least 30% expected to secure C
grade
60 – 69 1.0 D At least 7% expected to secure D
grade
59 and below 0.0 F At least 3% expected to secure F
grade

KARDAN UNIVERSITY POLICY ON PLAGIARISM:

All examinations and quizzes will be “closed book” unless otherwise instructed. At the time of examination all
students are requested to clear their desks and are not allowed exchanging any notes or electronic (text)
messages to other students. All cellular phones should be in silent mode and student will not be allowed to use
it during the examination other than medical/family/work emergency. All students are expected to adhere to
these policies and procedures.

CONDUCT AND IMPORTANT POLCIES:

Any student found guilty of a breach of ethics will be referred to Disciplinary Committee of the University.
a) Breach of ethics includes, but is not limited to plagiarism (the copying of other’s ideas and passing them off
as one’s own); copying or other forms of cheating on examinations, papers, and reports; the sale, purchase, or
distribution of term papers It is within an instructor’s discretion to impose a lesser penalty, e.g., “zero” grade
on a given assignment.
b) Course registration is charged by the management. Please approach the management for any queries about
course enrolment. In no circumstances should you approach the lecturers who have no control on this.
c) Make-up exam for midterm and terminal exam is available only for those individuals, who are not able to
attend their regural exams. Provision of supported documents are mandatory for grant of approval to participate
in make-up exams. Those students who miss their regular exam without a genuin reason, will be entitled for
80% of total makeup marks.
Usually make-up exam starts a week after the regular exam finishes.

d) There is no make-up session for the oral presentations and quizzes. If you are absent from the oral
presentation/ quiz without eligible reasons/documents, you will not earn any marks.

e) All examinations and quizzes will be “closed book” unless otherwise instructed. At the time of examination
all students are requested to clear their desks and are not allowed exchanging any notes or electronic (text)
messages to other students. All cellular phones should be in silent mode and student will not be allowed to use
it during the examination other than medical/family/work emergency. All students are expected to adhere to
these policies and procedures.

f) There is no supplementary exam for any failed course. Individuals, who fail the course, must retake the
module.