Sixteen Week Plan
Department of Computer Science
Faculty of Computing & Information Technology
Hafiz Hayat Campus, University of Gujrat
Title Software Engineering
Code CS-321
Credit hours 3.0
Prerequisite
Category Core -Computer Science
Course Description --
Aim:
Application of software engineering practices to the development of software where professionalism, quality, schedule,
and cost are important in producing a range of software projects.
Objectives:
To understand the importance and need of software engineering in producing a software.
To discuss different software development models, appropriate for the development and maintenance of software
Aims & Objectives
products
To introduce the basic project management concepts for the development of a high-quality product
To impart comprehensive knowledge regarding software development lifecycle
To demonstrate, with justification, an appropriate set of tools to support the development of a range of software projects
Hands on Training for Project Management tools such as Gantt Chart, Critical Path Method.
Extract and analyze software requirements
Develop some basic level of software Architecture/Design
Able to understand and draw different UML Diagrams
Learning Outcomes Prepare SRS by applying practices and principles in each phase of software development lifecycle
Apply different testing and debugging techniques
Students will be able to select and apply appropriate Design Patterns
Understand quality, Project management and testing
Roger S. Pressman, “Software Engineer: A Practitioner’s Approach”, 7th/e, M c Graw-Hill, 2001, ISB: 0072496681
Text Book
Reference Book Ian Sommerville, “Software Engineer”, 9 edition, ISBN-13: 978-0-13-703515-1 ISBN-10: 0-13-703515-2
Grading Breakup and Policy Assignment(s): 10%
Quizzes: 5%
Project: 10%
Midterm Examination: 25%
Final Examination: 50%
Recommendations
for Learning
Activities
Week Source
Lecture # TOPICS (Mention Assignments,
(Book, Chapter No)
Test, Case Study,
Projects, Lab Work or
Reading Assignments)
Introduction, The Nature of Software, Software Engineering VS Computer Science, [TB1: Ch. 1] [TB1: Ch. 1]
01
Characteruistics of Software, Types of Software , Application Software Types
01
The Software Process, Software Engineering Practice, S/W process Framework, [TB1: Ch. 1] [TB1: Ch. 1]
02
Umbrealla Activities of Software
03
Software Development LIFE CYCLE, Process FLOW
02
04
Introduction to Software Process Model: Water fall model, [TB1: Ch. 2] [TB2: Ch. 2]
05
Incremental development, Reuse-oriented software engineering Evolutionary Model, [TB1: Ch. 2] [TB2: Ch. 2]
03
Spiral Model, Prototype [TB1: Ch. 2] [TB2: Ch. 2] Assignment-1
06
The Rational Unified Process
Introduction to Agile Development, [TB1: Ch. 3] [TB2: Ch. 3]
07
Plan Driven Development VS Agile Development, Types
04
Principles that Guide Practice: Principles for Communication, Principles for Planning,
08 [TB1: Ch. 4] Quiz 1
Principles for Modeling, Principles for Construction, Principles for Deployment
Introduction to Requirement Engineering, Functional requirements and non-functional Project Proposal
09 [TB1: Ch. 5] [TB2: Ch. 4]
requirement, Announced
05
Requirement Specification, Structured Specification, Requirement Elicitation and [TB1: Ch. 5] [TB2: Ch. 4]
10
analysis
Requirements Elicitations Techniques: Observation, Questionaries, Interviewing, [TB1: Ch. 5] [TB2: Ch. 4]
11
Scenarios, introspection.
06 Project Scheduling: GANTT chart
Handouts
12 LAB Session: Microsoft Project (Project Scheduling and Tasks, Tasks Dependencies and
Resources Allocation)
07 Introduction to Unified Modeling Language. What IS UML? Structural Modeling, [TB1: Ch. 6] [TB2: Ch. 5]
13 Quiz 2
Behavioral Modeling, Architectural Modeling
14 Use Case Dependencies. Analysis Use Case Diagram, Include, extend and Generalization [TB1: Ch. 6] [TB2: Ch. 5]
Relationships, Use case description, how to write Use case Description?
Class Diagrams, Generalization, Aggregation, Behavioral Models, Data-driven modeling, [TB1: Ch. 6] [TB2: Ch. 5]
15 Assignment 2
Event-driven modeling
08
16
Practices of USE CASE and Class Diagrams [TB1: Ch. 6] [TB2: Ch. 5]
Mid Term Exam
Sequence Diagram, Drawing Sequence Diagram in UML, the use of condition and loop in [TB1: Ch. 6] [TB2: Ch. 5]
17
sequence diagram ,
09 Collaboration Diagram, Drawing Collaboration Diagram in UML, The difference between se-
18
[TB1: Ch. 6] [TB2: Ch. 5]
quence and collaboration diagram
Advanced Behavioral Modeling: Introduction to Activity and State chart diagram, Drawing
19 Activity and State chart diagram in UML, The usage of these two diagrams and difference of
[TB1: Ch. 6] [TB2: Ch. 5]
10 these two diagrams
Architectural Modeling: Introduction to Component, Package, and Deployment diagrams. [TB1: Ch. 6] [TB2: Ch. 5]
20
Drawing Component, Package, and Deployment diagrams in UML.
What is the Software Requirement Specification? Different chapters involved in SRS, SRS
Template for SRS. Handouts Template and
21
SRS as Term
11 Project
Design patterns, Creational Design Patterns, Structural Design Patterns, Behavioral [TB1: Ch. 17] [TB2: Ch. 7]
22
Design Patterns, Implementation issues, Reusability
Introduction to Software Testing, Development testing, Unit testing, Choosing unit test [TB1: Ch. 17] [TB2: Ch. 8]
23 Quiz 3
cases, Component testing, System testing,
12
24
Types of Software Testing , Object Oriented Testing Strategy, WebApp Testing [TB1: Ch. 20]
Alpha testing, beta testing, Stress testing, acceptance testing. The concept of stubs and [TB1: Ch. 20]
25
drivers in incremental testing.
13 Introduction to Software Pricing, Plan Driven Development, Project Plan, The Planning [TB1: Ch. 23] [TB2: Ch.
26 Process, Project scheduling, Schedule representation 23]
14 27 Process-Based Estimation, Estimation with Use-Cases, The COCOMO II model [TB1: Ch. 26] [TB2: Ch.
23]
Estimation for OO Projects-I, OO Projects-II, and Agile Projects. [TB1: Ch. 26] [TB2: Ch.
28 23] Assignment 3
Introduction to Software Quality, Software standards, The ISO 9001 standards [TB1: Ch. 14] [TB2: Ch.
29 framework, Reviews and inspections, The review process, Program Inspections 24]
15
Discussion about Software Quality Assurance and the importance of the SQA team. How Handouts
30
can we effectively present our group project's SRS to the class?
31 Project Presentation (SRS)
16
32 Project Presentation (SRS)
Final Exam
