How to make lecture break down?

How to make lecture break down?

Today, in this fresh and new post, you can a sample of making the lecture break down for any kind of subject. Here this is a sample of lecture break down of software engineering.

Download Sample File: lecture break downsample

Course Objectives:

This course is designed to teach students the different phases and activities involved in the software development process and Software Models. To understand how to elicit specify and validate requirements and how to create and develop a project plan. To create and analyze design models i.e. ERD, DFD. To learn various quality assurance techniques, including unit testing and functional testing. To apply the appropriate software evolution methods for maintaining, restructuring available software and managing software development.

Description of Course:

Software engineering is a field of study related to all aspects of the software life cycle, covering the problem analysis, design, implementation, modification and maintenance of software. This course is aimed to provide a strong foundation for students to understand software engineering practices and to apply these insights and principles to future software projects.

Text Books:  

  1. Software Engineering, By Ian. Sommerville, 9th Edition, 2010.
  2. Software Engineering: A Practitioner’s Approach, By R. S. Pressman, 8th Edition, 2010.

Pre-requisite:             No Pre-req

Grading Policy:         

There will be an evaluation in shape of Mid Term examination and Final term Examination held once during the whole semester.

Marks Distribution:                           Total Subject Marks: 60

Theory Marks: 60

Mid Term: 18 marks

Quizzes: 4 marks

Presentation    : 3 marks

Project Assignments: 5 marks

Final Term (Theory): 30 marks                    

Assignments and quizzes: Approximately 4 project assignments and 4 quizzes shall be given during the semester. The quizzes shall preferably be unannounced. The duration of each quiz shall be about 20 minutes. No make-ups will be offered for missed quizzes. The graded quizzes shall be returned in the next lecture and the graded assignments shall be returned within a week. The assignments shall clearly reflect the indigenous work of the student. Plagiarism is not allowed which may result in cancellation of an assignment, in addition to reporting the matter to the management for appropriate action.

Mid-Term Examination: A midterm exam of minimum 1-hour duration will be held that will cover all material covered till the midterm.

Attendance Policy: 75% attendance is mandatory; deficient students will not be allowed to appear in the final examination.

Office  Hours:

            Thur : 11:00 – 1:00

            Fri    :  9:30 – 11:00

Week No. Lecture No. Description
Week 1 Lect. 1 Introduction to Software Engineering

·       Professional software development

·        Software engineering ethics

·        Types of Software applications

Lect. 2 Software Development Lifecycle

  • SDLC activities
  • Plan-driven and agile process
Week 2 Lect. 3 Software Process Models

  • Waterfall Model
  • Incremental Model
  • Reuse-oriented Software Engineering
Lect. 4
  • Prototype Model
  • Boehm’s Spiral Model
Week 3 Lect. 5 Rational Unified Process

  • Phases and static workflows
Lect. 6 Agile Software Development

  • Plan-driven and agile development
  • Extreme Programming
Week 4 Lect. 7 Agile Software Development

·       SCRUM

Lect. 8 Requirement Engineering

  • Importance of RE, Role of RE, Cost

·       Functional Requirments

·       Non-Functional Requirments

Week 5 Lect. 9 Requirement Engineering

·       The software requirements document

·       Requirements engineering processes

Lect. 10 System Modeling

  • Functional Modeling and Information Flow

·       Data Flow Diagrams

Week 6 Lect. 11 Interaction Models

  • Use case modeling
Lect. 12 Interaction Models

  • Sequence diagrams
Week 7 Lect. 13 Interaction Models

  • Class diagrams
  • Generalization
  • Aggregation
Lect. 14 Behavioral models

  • Event-driven  modeling
  • State diagrams
Week 8 – 9 Mid Term
Week 10 Lect. 15 Architecture design

  • Architecture and importance
  • Architectural views
  • Architectural patterns
Lect. 16 Application Architectures

  • Transaction processing systems
  • Information Systems
  • Language Processing Systems
Week 11 Lect. 17 Software Quality Assurance

  • Concepts, Challenges
  • Quality control vs. Quality Assurance
  • Verification & Validation
Lect. 18 Software Testing

  • Software Testing Fundamentals
  • Black box
  • White box
Week 12 Lect. 19 Software Testing Levels

  • Development testing
  • Unit testing
  • Component testing
  • Release testing
  • User testing
Lect. 20 Dependability and security

  • Dependability properties
  • Availability and reliability
  • Safety


Week 13 Lect. 21 Process Improvement

  • The process improvement process
  • Process measurement
  • Process analysis
Lect. 22 Process Improvement

  • The CMMI process improvement framework
  • The staged CMMI model
Week 14 Lect. 23 Project management

  • Managing people

·       Motivating people

Lect. 24 Project management

  • Teamwork
  • Case study: Team spirit
  • Case study: Group composition
Week 15 Lect. 25 Risk Management

·       Process of Risk management

·       Project, Product, and Business risks

·       Risk types and examples

Lect. 26 Risk Management

  • Strategies to help manage risk
  • Risk indicators
Week 16 Lect. 27 Software  Re-engineering

·       Software Maintenance

·        A Software Reengineering Process Model

Lect. 28 Reverse Engineering

  • Reverse Engineering to Understand Processing
  • Reverse Engineering to Understand Data
  • Reverse Engineering User Interfaces
Week 17 Lect. 29 Project Presentations & Demos
Lect. 30 Project Presentations & Demos
Week 18 – 19 Final Term