SOFTWARE ENGINEERING Semester 7
Course Code BCS755C CIE Marks 50
Teaching Hours/Week (L:T:P: [Link]
SEE Marks 50
S)
Total Hours of Pedagogy 50 Total Marks 100
Credits 04 Exam Hours 3
Examination type (SEE) Theory
Course objectives:
To understand foundational principles and the evolving nature of software engineering.
- To learn various software process models and their practical applications.
- To acquire skills in gathering, modeling, and validating software requirements.
- To apply Agile methodologies and understand core software engineering practices.
- To build a foundation for software design, testing, and quality assurance.
Teaching-Learning Process
These are sample Strategies, which teachers can use to accelerate the attainment of the
various course outcomes.
1. Lecturer method (L) needs not to be only a traditional lecture method, but alternative
effective teaching methods could be adopted to attain the outcomes.
2. Use of Video/Animation to explain functioning of various concepts.
3. Encourage collaborative (Group Learning) Learning in the class.
4. Ask at least three HOT (Higher order Thinking) questions in the class, which promotes
critical thinking.
5. Adopt Problem Based Learning (PBL), which fosters students’ Analytical skills, develop
design thinking skills such as the ability to design, evaluate, generalize, and analyze
information rather than simply recall it.
6. Introduce Topics in manifold representations.
7. Show the different ways to solve the same problem with different circuits/logic and
encourage the students to come up with their own creative ways to solve them.
8. Discuss how every concept can be applied to the real world - and when that's possible, it
helps improve the students' understanding
9. Use any of these methods: Chalk and board, Active Learning, Case Studies
Module-1
Software and Software Engineering: The nature of Software, The unique nature of WebApps,
Software Engineering, The software Process, Software Engineering Practice, Software Myths.
Process Models: A generic process model, Process assessment and improvement, Prescriptive process
models: Waterfall model, Incremental process models, Evolutionary process models, Concurrent
models, Specialized process models. Unified Process , Personal and Team process models
Textbook 1: Chapter 1: 1.1 to 1.6, Chapter 2: 2.1 to 2.5
Module-2
1
Understanding Requirements: Requirements Engineering, Establishing the ground work, Eliciting
Requirements, Developing use cases, Building the requirements model, Negotiating Requirements,
Validating Requirements.
Requirements Modeling Scenarios, Information and Analysis classes: Requirement Analysis,
Scenario based modeling, UML models that supplement the Use Case, Data modeling Concepts, Class-
Based Modeling.
Requirement Modeling Strategies : Flow oriented Modeling , Behavioral Modeling.
Textbook 1: Chapter 5: 5.1 to 5.7, Chapter 6: 6.1 to 6.5, Chapter 7: 7.1 to 7.3
Module-3
Agile Development: What is Agility?, Agility and the cost of change. What is an agile Process?, Extreme
Programming (XP), Other Agile Process Models, A tool set for Agile process .
Principles that guide practice: Software Engineering Knowledge, Core principles, Principles that guide
each framework activity.
Textbook 1: Chapter 3: 3.1 to 3.6, Chapter 4: 4.1 to 4.3
Module-4
Software Design: Design within the context of software engineering, Design process and quality, Design
concepts: abstraction, modularity, architecture, patterns.
Architectural Design: Architectural styles and patterns, reference architectures, component-level
design, designing class-based components, conducting component-level design, design for reuse.
Textbook 1:Chapter 8: 8.1–8.6, Chapter 9: 9.1–9.5
Module-5
Software Testing: Introduction to software testing, Strategic approach, Test strategies for conventional
and object-oriented software, Validation testing, System testing, White-box and Black-box testing, Basis
Path Testing, Control structure testing.
Software Quality: Concepts of quality, Software quality assurance, Reviews, Software reliability and
metrics.
Textbook 1: Chapter 14: Sections 14.1 to 14.5,Chapter 15: Sections 15.1 to 15.5, Chapter 19:
Sections 19.1 to 19.5
Course outcome
At the end of the course, the student will be able to :
1. Explain the software nature, engineering practices, myths, and software process models.
2. Apply requirements engineering, elicitation, modeling, and validation in software development.
3. Demonstrate agile principles, practices, and tools for software development agility.
4. Apply design concepts, process, and architecture for quality software development.
5. Explain software testing strategies and quality assurance for reliable software.
2
Assessment Details (both CIE and SEE)
The weightage of Continuous Internal Evaluation (CIE) is 50% and for Semester End Exam (SEE) is
50%. The minimum passing mark for the CIE is 40% of the maximum marks (20 marks out of 50)
and for the SEE minimum passing mark is 35% of the maximum marks (18 out of 50 marks). A
student shall be deemed to have satisfied the academic requirements and earned the credits allotted
to each subject/ course if the student secures a minimum of 40% (40 marks out of 100) in the sum
total of the CIE (Continuous Internal Evaluation) and SEE (Semester End Examination) taken
together.
Continuous Internal Evaluation:
● For the Assignment component of the CIE, there are 25 marks and for the Internal Assessment
Test component, there are 25 marks.
● The first test will be administered after 40-50% of the syllabus has been covered, and the second
test will be administered after 85-90% of the syllabus has been covered
● Any two assignment methods mentioned in the 22OB2.4, if an assignment is project-based
then only one assignment for the course shall be planned. The teacher should not conduct two
assignments at the end of the semester if two assignments are planned.
● For the course, CIE marks will be based on a scaled-down sum of two tests and other methods
of assessment.
Internal Assessment Test question paper is designed to attain the different levels of Bloom’s taxonomy
as per the outcome defined for the course.
Semester-End Examination:
Theory SEE will be conducted by University as per the scheduled timetable, with common question papers for
the course (duration 03 hours).
1. The question paper will have ten questions. Each question is set for 20 marks.
2. There will be 2 questions from each module. Each of the two questions under a module (with a maximum
of 3 sub-questions), should have a mix of topics under that module.
3. The students have to answer 5 full questions, selecting one full question from each module.
4. Marks scored shall be proportionally reduced to 50 marks.
Suggested Learning Resources:
Textbook
Roger S. Pressman: Software Engineering – A Practitioner’s Approach, 7th Edition, Tata McGraw Hill, 2010.
Web links and Video Lectures (e-Resources):
[Link]
Activity-Based Learning (Suggested Activities in Class)/Practical-Based learning
● Course project (Group of two students): Simulation that covers all the phases of SDLC -
25 marks
