You are on page 1of 4

Dept.

Name / Institute Department of Computer Science and Engineering / Chitkara University
Name
Institute of Engineering &Technology
Program Name BE (CSE)Computer Science and engineering
Course Code CSL3307
Course Name Software Engineering
Lecture / Tutorial (per 3-0-0 Course Credits 3.0
week)
Course Coordinator Name Er. Poonam Dhiman

1. Scope and Objectives of the Course
1. In this course, students will gain a broad understanding of the discipline of software engineering
and its application to the development and management of software systems.
2. To acquire knowledge of basic software engineering methods and practices, and their appropriate
application.
3. To understand the role of project management including planning, scheduling, risk management,
etc.
4. To impart knowledge of software requirements, software testing approaches (such as unit testing
and integration testing) and quality control and ensuring good quality software using latest tools.

2. Recommended Books

RB1: Software Engineering, A practitioner’s Approach’ by Roger S. Pressman, 6th Edition, McGraw- Hill
International Edition.
RB2: An Integrated Approach to Software Engineering by Pankaj Jalota, third edition

RB3: Software Engineering a Precise approach by Pankaj Jalote,2010,Wiley Publications.

RB4: Software Engineering by K.K Aggarwal and Yogesh Singh,New age Publications

RB5: Software Engineering by Ian Sommerville, sixth Edition, Adison- Wesley Pub. Co.

3. Other readings and relevant websites

S.No. Link of Journals, Magazines, websites, MOOC Course and Research Papers
1. http://nptel.iitm.ac.in/courses/Webcourse-
contents/IIT%20Kharagpur/Soft%20Engg/New_index1.html
2. http://www.csse.monash.edu.au/courseware/cse3308/cse3308_2005/html/lectures.html
3. http://engineeringppt.blogspot.in/2011/12/software-engineering-pressman-ppt.html
4. MOOC course: https://www.udacity.com/course/software-development-process--ud805

Risk Mitigation. Monitoring and RB1 Management (RMMM) plan RB2 41-42 Quality Management :Overview of Quality Management.User Interface Analysis and design. RB1 . Flow Oriented Modeling. Interface analysis and Interface design steps. Designing class based Components . Course Plan Lecture Topics Text Book / Number Reference Book / Other reading material 1-2 Introduction to Software Engineering: The Evolving Role of RB1 Software. RB1 34-35 Software Project Planning: Objective . RB2 25-27 Integration Testing. Metrics for Software Quality. engineering Process.4. Data modeling RB1 Concepts. RB1 RB1 28-29 White-Box Testing Techniques: Basis Path Testing. 17-20 Design Engineering. Earned Value Analysis. Control RB1 Structure Testing: condition and loop testing RB2 30-31 Black -Box Testing Techniques: Equivalence Partitioning and RB1 Boundary Value Analysis RB2 32-33 Project Management & Metrics: The management spectrum. Data RB1 design. Evolutionary Process Models – Incremental Models. 39-40 Risk Management: Software Risks & Risk Strategies. Risk Projection.System Testing. Risk RB1 Identification. TB1 Metrics for process & project. ASD. Software Project Estimation and Decomposition Techniques(LOC. Software Scope and RB1 Resources. what is an agile process. Spiral Model RB1 RB2 6-9 An Agile View of Process: what is agility. Validation Testing . RB1 agile process models: extreme programming(XP).Architectural design. 3-5 The Software Process: SDLC. 21-24 Software Testing Strategies and Tactics: A strategic approach RB1 for Software Testing. RB1 36 Empirical Estimation Models: COCOMO Model.Design Concepts and model. Changing nature of software. Software Testing Strategies: Unit Testing. Project RB1 Scheduling. Software Engineering –Layered RB1 Technology.FP).Requirements Engineering RB1 Tasks: Initiating Requirement. Process Models: The Waterfall Model. Scrum 10-12 Requirements Engineering: SRS. COCOMO Model RB1 II RB2 37-38 Project Scheduling: basic concepts of scheduling. Eliciting RB1 Requirements 13-16 Building Analysis Model: Requirement Analysis. Estimation.

Control Structure 2 Testing. The average of best two will be considered. Evaluation Scheme: Component 2* Sessional Tests (STs)* 40 Component 3** End Term Examination** 60 Total 100 * There are three Sessional Tests (STs) for all theory papers. engineering Process. Integration Testing. Estimation. Black -Box Testing Techniques: Equivalence Partitioning and Boundary 2 Value Analysis Project Management & Metrics: The management spectrum. Software Testing Strategies and Tactics: A strategic approach for 5 Software Testing. 2 Software Project Estimation and Decomposition Techniques(LOC. 4 Architectural design. Project Scheduling. RB1 43-45 Change Management RB1 RB1 5. Eliciting Requirements Building Analysis Model: Requirement Analysis. ASD. Software Scope and Resources. Requirements Engineering Tasks: 3 Initiating Requirement. Monitoring and Management (RMMM) plan . The mandatory requirement of 75% attendance in all theory classes is to be met for being eligible to appear in this component. 2 Earned Value Analysis. Risk Management: Software Risks & Risk Strategies.User Interface Analysis and design. Empirical Estimation Models: COCOMO Model. Data design. ** The End Term Comprehensive examination will be held at the end of semester. Software Testing Strategies: Unit Testing.SDLC 5 Process Models: The Waterfall Model. 2 8% Risk Projection. Software Project Planning: Objective . Metrics for Software Quality. 2 15% Changing nature of software.FP). Design Engineering.System Testing. Evolutionary Process Models – Incremental Models. COCOMO model II 1 10% Project Scheduling: basic concepts of scheduling. Interface analysis and Interface design steps. Scrum Requirements Engineering: SRS. Validation Testing . Data modeling Concepts. agile 4 15% process models: extreme programming(XP). White-Box Testing Techniques: Basis Path Testing. Risk Mitigation. 4 30% Flow Oriented Modeling. Metrics for 2 15% process & project. Spiral Model An Agile View of Process: what is agility. SYLLABUS Contents Lectures Weightage(%age) Introduction to Software Engineering: The Evolving Role of Software. what is an agile process. The Software Process: Software Engineering –Layered Technology.Design Concepts and model. Risk Identification. Designing class based Components .

Rupali Gill Deputy Dean Er. 2 12% Quality Management Change Management 3 This Document is approved by: Designation Name Signature Course Coordinator Er. Jyoti Snehi Program Incharge Er. 2017 Revision No 4 .Overview of Quality Management. Meenu Khurana Date 07th July.