Entrance Announcement
MICTE 2080
2080 Magh 07
User:Ritu Shrestha/Teaching Practice Lesson Plan-9: Difference between revisions
Jump to navigation
Jump to search
(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 |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
__notoc__ | |||
Class: BICTE 4<sup>th</sup> Semester Date: 2024/01/03 | |||
Class: BICTE | |||
Subject: System Analysis and Design | Subject: System Analysis and Design Time: 50 min | ||
Unit: 4 | |||
Unit: 4 Number of Students: 15 | |||
Topic: Requirement Derivation | Topic: Requirement Derivation | ||
1. | |||
== 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 | |||
2. | * To construct steps for requirement derivation in software engineering | ||
== 2. Instructional materials: == | |||
3. | |||
* Daily uses materials | |||
* [https://docs.google.com/presentation/d/1mt0IzYM2_hw0uqSU4kIhkXQz4dV6k9dj/edit#slide=id.p1 PowerPoint presentation slides] | |||
== 3. Teaching Learning Activities: == | |||
* Begin with a real-world scenario that defines requirements in creating successful software. | |||
4. | * Introduce the concept of requirement derivation. | ||
* Discuss the technique of gathering requirements through group discussions. | |||
* Demonstrate how creating prototypes can help in clarifying requirements. | |||
5. | * 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? | ||
Latest revision as of 08:23, 12 January 2024
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:[edit | edit source]
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:[edit | edit source]
- Daily uses materials
- PowerPoint presentation slides
3. Teaching Learning Activities:[edit | edit source]
- Begin with a real-world scenario that defines requirements in creating successful software.
- Introduce the concept of requirement derivation.
- Discuss the technique of gathering requirements through group discussions.
- Demonstrate how creating prototypes can help in clarifying requirements.
- Teach how to document requirements in a clear and concise manner.
- Summarize key points from the lesson.
4. Assessment:[edit | edit source]
- What are the qualities of a good requirement documentation?
- What are the system developer’s challenges for requirement derivation?
5. Evaluation:[edit | edit source]
How can you apply requirement derivation in your future software development projects?