1. The document contains a sample exam for a software requirements specification course. It includes 10 multiple choice questions and 10 true/false questions testing concepts from the textbook. 2. Key topics covered in the exam include functional vs non-functional requirements, requirements elicitation techniques like interviews and focus groups, essential analyst skills, defining business requirements, context diagrams, and requirements management best practices. 3. The exam evaluates both conceptual knowledge of requirements engineering as well as practical skills in applying techniques from the textbook.

1. Ahmed Kamel Taha - 13101224
EXAM QUISTIONS
MCQ-TRUE/FALSE
Software requirements specification

2. MCQ:
1. A descriptionof abehaviorthata systemwill exhibitunderspecific conditions. (P.7)
a. Functional requirement
b. Business requirement
c. System requirement
d. Nonfunctional requirement
2. ____________ are particularly valuable for commercial product development, for
which you might have a large and diverse customer base. (P.48)
a. user representatives
b. user classes
c. focus groups
d. elicitation interviews
e. Distribute questionnaires
3. Users who will participate in software _______ should receive one or two days of
education about requirements (P.55)
a. Development
b. Maintenance
c. Requirements
d. Testing
4. According to Implementing requirements engineering good practices, what is the
difficulty of: Define a requirements engineering process (P.58)
a. High
b. Low
c. Medium
d. None of the above
5. Select all Essential analyst skills: (P.65)
a. Listening skills
b. questioning skills
c. Define business requirements
d. Analyze requirements
e. Lead requirements validation
6. Business requirements might come from (P.78)
a. funding sponsors
b. corporate executives
c. marketing managers
d. All the above
7. An_________ showsall of the systemsrelatedtothe systemof interestthatinteract
with one another and the nature of those interactions (P.92)
a. Ecosystem map
b. Feature tree
c. Event list
d. Context diagram

3. 8. _______ is used to discover business, user, functional, and nonfunctional
requirements, along with other types of information. (P.119)
a. Interviews
b. Focus groups
c. Brainstorming
d. Elicitation
9. The cyclic nature of requirements elicitation include: (P.120)
a. Maintenance
b. Validation
c. Interviews
d. None of the above
10. in________ youstudyexistingsystemstodiscoveruserandfunctional requirements
(P.128)
a. User interface analysis
b. System interface analysis
c. Document analysis
d. Observation
True/False:
1. A requirementsbaseline isasetof requirementsthathasbeenreviewedandagreed
uponand servesasthe basisfor furtherdevelopment. (P.39) (T)
2. Customers agreesthatthe requirementswillachieve theirbusinessobjectives.
(P.38) (F)
3. Expertreviewof requirements,particularlythe type of rigorousreview called
inspection,isone of the highest-value software qualitypracticesavailable (P.52) (F)
4. makingthe requirementscome tolife aftertheyare castintothe concrete of code.
(P.53) (F)
5. Each projectteam shouldplanhow itwill handle itsrequirementsdevelopmentand
managementactivities (P.56) (T)
6. The product visionsuccinctlydescribesthe ultimate productthatwill achieve the
businessobjectives. (P.78) (T)
7. requirementisoftendefinedintermsof features,butyoucanalsodefine itinterms
of userstories,use cases,use case flows,orexternal events. (P.89) (F)
8. The stakeholderprofilesdescribedifferentcategoriesof customersandotherkey
stakeholdersforthe project (P.90) (T)
9. Managing scope onan agile project,inwhichdevelopmentisperformedinaseries
of fixabletime box iterations,takesadifferentapproach. (P.98) (F)
10. scrum projectsmake extensiveuse of interviewsasa mechanismtogetdirectuser
involvement. (P.121) (F)