User:Ritu Shrestha/Teaching Practice Lesson Plan-17

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

Subject: System Analysis and Design                               Time: 50 min      

Unit: 4                                                                            Number of Students: 15

Topic: Reflection on Unit 4      

1.    Specific Objective:

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

•      To reflect on Requirement Derivation, Allocation, Flow Down, and Traceability.
•      To analyze the importance of preparing requirement statements and selecting appropriate verification methods.

2.    Instructional materials:

•     Daily uses materials

3.    Teaching Learning Activities:

•      Explain that the focus of this lesson is on reflecting on what they have learned and discussing its practical implications.
•      Discuss each subtopic of Unit 4:

·        Requirements Derivation Methods

·        Requirements Derivation and Allocation Across Entity Boundaries

·        Requirements Allocation

·        Requirements Traceability

·        Preparing the Requirement Statement

·        Selection of Requirement Verification Methods

•      Provide guiding questions for discussion:

·        What are the main requirement derivation methods we discussed? How do they differ?

·        How can requirement traceability enhance project management and development processes?

·        What challenges might arise when preparing requirement statements?

·        How do we select appropriate requirement verification methods based on project needs?

•      Wrap-up with the emphasizing the importance of understanding requirement derivation, allocation, flow down, and traceability in software engineering.
•      Address any remaining questions or concerns.

4.    Assessment:

•      Identify at least two challenges that may arise when preparing requirement statements.
•      Compare and contrast different requirement derivation methods in terms of their effectiveness and applicability.

5.    Evaluation:

Propose a requirement verification plan for a hypothetical software project, considering project needs and constraints.