User:Ritu Shrestha/Teaching Practice Lesson Plan-14

Class: BICTE 4^th Semester                                              Date: 2024/02/02

Subject: System Analysis and Design                               Time: 50 min      

Unit: 4                                                                            Number of Students: 15

Topic: Software Requirements Specification

1.    Specific Objective:

At the end of this lesson, students will be able:

•     To understand the significance of a Software Requirements Specification (SRS) document in the software development lifecycle
•     To identify its key components
•     To demonstrate the ability to create a basic SRS document.

2.    Instructional materials:

•     Daily uses materials
•     SRS document

3.    Teaching Learning Activities:

•     Engage the class in a discussion by asking questions like:

o   What do you understand by software requirements?

o   Why is it important to document software requirements?

o   Have you ever encountered any issues due to unclear or incomplete requirements in a project?

•     Define and discuss the importance of Software Requirements Specification (SRS).
•     Outline the essential components of an SRS document.
•     Divide the class into three groups and instruct each group to create a basic SRS document for an online food ordering project.
•     Circulate among the groups to offer guidance and answer questions.
•     Convene the groups to present their SRS document.
•     Address any remaining questions or concerns.

4.    Assessment:

•     Provide examples of scenarios where a well-defined SRS can prevent misunderstandings and project failures.
•     What is the purpose of SRS?

5.    Evaluation:

Report on any recent advancements or best practices in SRS documentation methodologies.