ADMAS UNIVERSITY
FACULTY OF INFORMATICS
DEPARTMENT OF COMPUTER SCIENCE
COURSE OUTLINE
Course Title Software Engineering
Course Code CoSc3061
Credit Hours 3
Lecture Hours 3
Laboratory Hours -
Prerequisites -
Program BSc Degree in Computer Science
Academic Year
Instructors’ Name
Course Coordinator
Department Head
Course Description This course provides an introduction to the problems of software
development and maintenance and the processes and methods used to
address them. All phases in the software development life cycle will be
introduced. The course also deals with software project planning, cost
estimation, tracking and control, staffing, risk management, and
software configuration plan. Covers O-O concepts, tools, development
life cycle, problem solving, modeling, analysis, and design, while
utilizing UML (Unified Modeling Language) for O-O modeling. UML
has become the standard notation for modeling O-O systems and is
being embraced by major software developers like Microsoft and
Oracle.
Course Objective At the end of this course, students will be able to:
Explain the basic principles of Software Engineering
Write requirements specification documents
Design a system, component, or process to meet desired needs.
Verify and validate a Software system practice with effective
communication skill.
Describe in detail the theory, concepts and methods pertaining to the
Unified Modeling Language (UML).
Create requirements using use case modeling concepts.
Demonstrate conceptual and technical skills in the analysis, design
and implementation of a software system using Object Oriented
Concepts.
Employ tools and techniques for Object Oriented Software
Engineering,
Demonstrate an ability to adapt and solve problems in software
development activities from specification to testing individually and
as part of a team.
Course Contents
Chapter TOPIC Time
Allotted
1. Introduction to Software Engineering 8hrs.
1.1 The Software and Software Engineering
1.2 The Software Engineering Approach
1.3 Software development life cycle
1.4 Software Processes
1.5 Software Process Concepts
1.6 Characteristics of a Software Process
1.7 Software Process Management and model
1.8 Software design and architecture concepts
2. Planning a Software and software Project Management 8hrs.
2.1 Cost Estimation
2.2 Project Scheduling
2.3 Staffing Personnel Planning
2.4 Software Configuration Management Plans
2.5 Quality Assurance Plans
2.6 Project Monitoring Plans
2.7 Risk Management
3. Software Requirements and Specification (SRS) 6hrs.
3.1 Software Requirements
3.2 Problem Analysis
3.3 Requirements Specification
3.4 Requirement gathering.
3.6 Requirement modeling
4. Object-Oriented Analysis 10hrs.
4.1 Objects and Classes
4.2 System modeling using UML
4.3 Static and Dynamic Modeling Notation
4.3.1 Use Case Diagrams
4.3.2 Class Diagrams
4.3.3 Sequence diagrams
4.3.4 State chart diagrams
4.3.5 Activity diagrams
4.3.6 Component diagram
4.3.7 Deployment diagram
4.3.8 Diagram extensions
4.4 User interface prototyping
4.5 Object Relationships, Inheritance and Polymorphism
4.6 Aggregation and Composition
5. Object Oriented Software Design 8hrs.
5.1 Design Principles and Model
5.2 Module Level Concepts
5.3 Design Notation and Specification
5.4 Structured Design Methodology
5.5 Verification and Metrics
5.6 Module Specifications
5.7 Persistence Models
5.8 Component and Deployment diagrams
6. Software Testing and implementation 8hrs.
6.1 Testing Fundamentals
6.2 Functional Testing
6.3 Structural Testing
6.4 Testing Process
6.5 System implementation
Roles of the Instructor He/she will come to the class regularly on time and deliver the lecture in a well-
organized manner. Besides, at the end of each class he/she gives reading
assignment for the next class. He/she will make sure that a proper assessment is
given. He/she is also responsible to give feedback for each assessment
Roles of the students The success of this course depends on the students` individual and collective
contribution to the class discussions. Students are expected to participate
voluntarily, or will be called upon, to contribute to set exercises and problems.
Students are also expected to read the assigned readings and prepare the cases
before each class so that they could contribute effectively to class discussions.
Students must attempt assignments by their own. Proficiency in this course
comes from individual knowledge and understanding. Copying the works of
others is considered as serious offence and leads to disciplinary actions
Instructional Methods
Lectures Debates and Discussions
Practical classes (Lab sessions) Individual/Group project works
Interactive platforms Presentation & Demonstration
Cooperative Learning Problem Based Learning
Attendance Policy: students should attend a minimum of 80% of the total hours given to the courses
to get the grade they achieved. Otherwise, No Grade (NG).
Assessment Methods Chapters (Topics) to be covered Points
Assessment 1 (Test 1) Chapter 1 & 2 10
Assessment 2 (Test 2) Chapter 3, 4 & 5 10
Assessment 3 Group Project Project work 10
Presentation of Group Project 5
Final Exam All Chapters 65%
Grand total 100%
Text books:
Rajib Mall, Fundamentals Of Software Engineering, Fourth Edition ,2014
References
Ian Sommerville , SOFTWARE ENGINEERING, Ninth Edition,2011.
Martina Seidl, Marion Scholz, Christian Huemer, Gerti Kappel. UML @ Classroom: An
Introduction to Object-Oriented Modeling. Springer International Publishing AG, 2012.
David Kung, Object-Oriented Software Engineering:, 2013
Dianxiang Xu, Modern Software Engineering: Principles and Practices: Writing Clean,
Dependable Code, 2021