User:Ritu Shrestha/Teaching Practice Lesson Plan-9: Difference between revisions

no edit summary
(Created page with "Lesson plan no: 9 Class: BICTE 4th Semester Date: 2024/01/03 Subject: System Analysis and Design Time: 50 min Unit: 4 Number of Students: 15 Topic: Requirement Derivation 1. Specific Objective: At the end of this lesson, students will be able: • To define requirement derivation • To construct steps for requirement derivation in software engineering 2. Instructional materials: • Daily uses materials • PowerPoint presentation slides 3. Te...")
 
No edit summary
Line 1: Line 1:
Lesson plan no: 9
Class: BICTE 4<sup>th</sup> Semester                                              Date: 2024/01/03
 
Class: BICTE 4th Semester Date: 2024/01/03
Subject: System Analysis and Design                               Time: 50 min      
Subject: System Analysis and Design Time: 50 min
 
Unit: 4 Number of Students: 15
Unit: 4                                                                            Number of Students: 15
 
Topic: Requirement Derivation
Topic: Requirement Derivation
 


1. Specific Objective:  
 
 
== 1.    Specific Objective: ==
At the end of this lesson, students will be able:
At the end of this lesson, students will be able:
• To define requirement derivation
 
• To construct steps for requirement derivation in software engineering
*      To define requirement derivation
2. Instructional materials:
*      To construct steps for requirement derivation in software engineering
• Daily uses materials  
 
PowerPoint presentation slides
== 2.    Instructional materials: ==
3. Teaching Learning Activities:
 
• Begin with a real-world scenario that defines requirements in creating successful software.
*      Daily uses materials
• Introduce the concept of requirement derivation.
*      [https://docs.google.com/presentation/d/1mt0IzYM2_hw0uqSU4kIhkXQz4dV6k9dj/edit#slide=id.p1 PowerPoint presentation slides]
• Discuss the technique of gathering requirements through group discussions.
 
• Demonstrate how creating prototypes can help in clarifying requirements.
== 3.    Teaching Learning Activities: ==
• Teach how to document requirements in a clear and concise manner.
 
• Summarize key points from the lesson.
*      Begin with a real-world scenario that defines requirements in creating successful software.
4. Assessment:
*      Introduce the concept of requirement derivation.
• What are the qualities of a good requirement documentation?
*      Discuss the technique of gathering requirements through group discussions.
• What are the system developer’s challenges for requirement derivation?
*      Demonstrate how creating prototypes can help in clarifying requirements.
5. Evaluation:
*      Teach how to document requirements in a clear and concise manner.
*      Summarize key points from the lesson.
 
== 4.    Assessment: ==
 
*      What are the qualities of a good requirement documentation?
*      What are the system developer’s challenges for requirement derivation?
 
== 5.    Evaluation: ==
How can you apply requirement derivation in your future software development projects?
How can you apply requirement derivation in your future software development projects?
283

edits