Requirements Engineering and Software Engineering Lecture Notes, Study notes of Software Engineering

Lecture notes on requirements engineering and software engineering, covering topics such as defect propagation, formal technical reviews, review guidelines, and postmortem evaluations. It includes questions and answers related to software quality control activities, review metrics, and the cost impact of software defects. The notes also touch on improving the efficacy of desk check reviews and the benefits of developing checklists for reviewed products. This resource is valuable for students and professionals in software engineering.

Typology: Study notes

2024/2025

Available from 12/08/2025

cecil27
cecil27 🇺🇸

1.6K documents

1 / 7

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Requirements Engineering -
Software Engineering - Lecture
Notes, Study notes of Software
Engineering
_____ purify software engineering work products, including requirements and design
models, code, and testing data.
1.Analysis matrices
2.Work products
3.Increments
4.Software reviews - correct answerSoftware reviews
_________ _________makes the following argument—an error introduced early in the
software engineering work flow and undetected can and often will be amplified into
multiple errors during design. - correct answerDefect amplification
_____________ _____________is a term used to describe the impact an undiscovered
error has on future development activities or product behavior. - correct answerDefect
propagation
A formal technical review is a class of reviews that includes _____.
1. records and interpretations
2. walkthroughs and inspections
3. product materials and distribution
4. suggestions and derivations - correct answer2. walkthroughs and inspections
According to the review guideline "Conduct meaningful training for all reviewers," the
training should emphasize _____.
1. client-server methodologies
2. process-related issues
3. the human psychological side of reviews
4. system calls - correct answer2. process-related issues
3. the human psychological side of reviews
At the end of a review meeting, the reviewer records and summarizes the problems
raised in the meeting and produces a(n) _______________ _______________
_______________. - correct answerreview issue list
pf3
pf4
pf5

Partial preview of the text

Download Requirements Engineering and Software Engineering Lecture Notes and more Study notes Software Engineering in PDF only on Docsity!

Requirements Engineering -

Software Engineering - Lecture

Notes, Study notes of Software

Engineering

_____ purify software engineering work products, including requirements and design models, code, and testing data. 1.Analysis matrices 2.Work products 3.Increments 4.Software reviews - correct answerSoftware reviews _________ _________makes the following argument—an error introduced early in the software engineering work flow and undetected can and often will be amplified into multiple errors during design. - correct answerDefect amplification _____________ _____________is a term used to describe the impact an undiscovered error has on future development activities or product behavior. - correct answerDefect propagation A formal technical review is a class of reviews that includes _____.

  1. records and interpretations
  2. walkthroughs and inspections
  3. product materials and distribution
  4. suggestions and derivations - correct answer2. walkthroughs and inspections According to the review guideline "Conduct meaningful training for all reviewers," the training should emphasize _____.
  5. client-server methodologies
  6. process-related issues
  7. the human psychological side of reviews
  8. system calls - correct answer2. process-related issues
  9. the human psychological side of reviews At the end of a review meeting, the reviewer records and summarizes the problems raised in the meeting and produces a(n) _______________ _______________ _______________. - correct answerreview issue list

Choose review guidelines that are defined for formal technical reviews.

  1. Set an agenda and maintain it.
  2. Deallocate resources and schedule time for reviews.
  3. Review the product, not the producer.
  4. Take written notes.
  5. Solve every problem that is noted. - correct answer1. Set an agenda and maintain it.
  6. Review the product, not the producer.
  7. Take written notes. Describe a postmortem evaluation.
  8. It is a mechanism that determines elementary processes or steps.
  9. It is a mechanism that determines the structure of a collaboration network and team performance for teams derived from scientific fields.
  10. It is a mechanism that checks if quality control activities are working.
  11. It is a mechanism that determines what went right and what went wrong when software engineering process and practice is applied in a project. - correct answer4. It is a mechanism that determines what went right and what went wrong when software engineering process and practice is applied in a project. During the sprint planning meeting, ___________ ___________ are reviewed and ordered according to priority, before selecting them to include in the next sprint. - correct answeruser stories Identify a statement that holds good for the review guideline: Enunciate the problem areas, but don't attempt to solve every problem noted.
  12. Only a reviewer should solve all the problems that are noted.
  13. A test engineer should know the software features assigned to him, and based on this he should recognize all the impact regions.
  14. A review is not a problem-solving session. The solution of a problem can often be accomplished by the producer alone.
  15. A developer should make a note of problem areas. - correct answer3. A review is not a problem-solving session. The solution of a problem can often be accomplished by the producer alone. Identify a true statement of the review guideline "Review your early reviews."
  16. The very last product to be reviewed should be the review guidelines themselves.
  17. A review is a problem-solving session.
  18. The very first product to be reviewed should be the review guidelines themselves.

1.Effort saved per error = Etesting- Ereviews 2.Effort saved per error = Etesting+ Ereviews 3.Effort saved per error = Ereviews x Etesting 4.Effort saved per error = Ereviews/Etesting - correct answer1.Effort saved per error = Etesting- Ereviews Identify the model that helps to define the level of review formality. 1.The reference model 2.The implementation model 3.The requirements model 4.The development model - correct answer1.The reference model Identify the review metric that requires an effort to review a work product prior to the actual review meeting. 1.Preparation effort 2.Assessment effort 3.Work product effort 4.Rework effort - correct answerPreparation effort Identify the review metrics that are collected for each review conducted. 1.Module name 2.Bug severity 3.Major errors found 4.Minor errors found - correct answerMajor errors found Minor errors found In a review meeting, who informs the project leader that the work product is complete and that a review is required?

  1. Customer
  2. Producer
  3. Team manager
  4. Reviewer - correct answer2. Producer In a software process, the term__________implies a quality problem that is discovered after the software has been released to end users. - correct answerdefect / fault In the context of analyzing metrics, ______________ _____________ represents the errors found per unit of work product reviewed. - correct answererror density In the context of review guidelines, why are resources allocated and time scheduled for formal technical reviews?
  1. Time should be scheduled for the inevitable modifications that will occur as the result of a formal technical review.
  2. Reviews should be allocated to primary and secondary owners for effective results.
  3. Time should be scheduled to write test cases after the build is delivered to the testing team.
  4. For reviews to be effective, they should be scheduled as a task during the software process. - correct answer1. Time should be scheduled for the inevitable modifications that will occur as the result of a formal technical review.
  5. For reviews to be effective, they should be scheduled as a task during the software process. In the context of review metrics and their use, _____ is a measure of the size of a work product that has been reviewed. 1.product review 2.product measure 3.review size 4.work product size - correct answer4.work product size In the context of review metrics and their use, identify the review metric where effort is dedicated to the correction of those errors uncovered during a review. 1.Preparation effort 2.Rework effort 3.Work product effort 4.Assessment effort - correct answer2.Rework effort In the context of the cost impact of software defects, the primary objective of technical reviews is to _____. 1.find errors during the process so that they do not become defects after the release of the software 2.push software with defects when the project deadline approaches and fix the errors later 3.release the software that is more prone to errors 4.identify the error software after it is launched to runtime environment - correct answer1.find errors during the process so that they do not become defects after the release of the software Software reviews are a(n)______________for the software process work flow. - correct answerfilter
  1. Challenges
  2. Performances
  3. Observances - correct answer1. Excellences
  4. Challenges What is the role of a recorder?
  5. To reject records of issues discussed in the meeting
  6. To update latest records on quality management system
  7. To record good activities followed while working on a project
  8. To record all important issues raised during the review - correct answer4. To record all important issues raised during the review When does the formality of a review increase?
  9. When distinct roles are explicitly defined for reviewers
  10. When the moderator takes care of people's issues
  11. When success rate of the test cases is higher than that of failure
  12. When there is a sufficient amount of planning and preparation for the review
  13. When a distinct structure for the review is defined - correct answer1. When distinct roles are explicitly defined for reviewers
  14. When there is a sufficient amount of planning and preparation for the review
  15. When a distinct structure for the review is defined Who evaluates the product for readiness, generates copies of product materials, and distributes them to two or three reviewers for advance preparation?
  16. Developer
  17. Review leader
  18. Business analyst
  19. Project leader - correct answer2. Review leader XP recommends that two people work together at one computer workstation to create code for a story. This is called _____________ ______________. - correct answerpair programming