Test
Tutorial 3
Este test tiene tipos de pregunta que se abren en el reproductor de siempre.
Preguntas del test (24)
1Collecting the requirements provides a basis for [blank_start]validating[blank_end] the system once it is built.
- Avalidating
2The Volere template is organised into 5 main categories:
- Project [blank_start]Drivers[blank_end]
- Project [blank_start]Constraints[blank_end]
- [blank_start]Functional[blank_end] Requirements
- [blank_start]Non-Functional[blank_end] Requirements
- Project [blank_start]Issues[blank_end]- ADrivers
- BConstraints
- CFunctional
- DNon-Functional
- EIssues
3What are the two project drivers?
- AThe stakeholders
- BThe purpose of the project
- CThe end product
- DThe business domain
4'The Product should work in freezing conditions’ is an example of a [blank_start]mandated[blank_end] [blank_start]constraint[blank_end].
- Amandated
- Bconstraint
5Which of the below are part of the Project Constraint section of the Volere template?
- ANaming Conventions and Terminology
- BMandated Constraints
- CFunctional Requirements
- DRelevant Facts and Assumptions
- EStakeholders and project purpose
6The Naming Conventions and Terminology aspect of the Project Constraints refer to the [blank_start]vocabulary[blank_end] of the project. At its most formal, it takes the form of a [blank_start]glossary[blank_end].
- Avocabulary
- Bglossary
7What does this definition describe?
These are external factors that may have an effect on the product but do not necessarily translate into requirements.- ARelevant Facts and Assumptions
- BMandated Constraints
- CNaming Conventions
- DTerminology
8In the Volere template, the 'Functional Requirements' section is made of which 4 of the parts below?
- AThe scope of the work
- BMandated Constraints
- CBusiness Data Model and Data Dictionary
- DNaming conventions and terminology
- EThe scope of the product
- FRelevant Facts and Assumptions
- GFunctional Requirements
9The '[blank_start]scope[blank_end] of the work' defines the [blank_start]boundaries[blank_end] of the business area that will be improved.
- Ascope
- Bboundaries
10The use case diagram represents the [blank_start]scope[blank_end] of the product, which is dependent on the scope of the [blank_start]work[blank_end].
- Ascope
- Bwork
11fit criterion is a [blank_start]precise[blank_end] and [blank_start]testable[blank_end] statement of a requirement. ex: 'Email is received whenever things change'
- Aprecise
- Btestable
12This is how to document Functional Requirements. Place the sections where they should be.
- ADescription
- BRationale
- CFit Criterion
13Non Functional Requirements are [blank_start]qualities[blank_end] that the system should have e.g being secure, fast, usable, maintainable etc. They can be considered as [blank_start]constraints[blank_end] on the functional requirements.
- Aqualities
- Bconstraints
14Which of the below are the 8 classes of non-functional requirements identified by Robertson & Robertson (2006)?
- ALook-and-feel requirements – product’s appearance
- BUsability and humanity requirements – ease of use
- CPerformance requirements – speed, safety + accuracy of product
- DOperational and Environmental requirements –what is the operating environment of system and its considerations
- EMaintainability and Support requirements – expected changes and the time allowed to make them
- FSecurity requirements – security + confidentiality of the product
- GCultural requirements – consider people involved
- HLegal requirements –laws + standards that apply to the product
- IUsability and humanity requirements – consider cultural background of people involved
- JPerformance requirements – security + accuracy of product
15Drag and drop the 8 classes of non-functional requirements identified by Robertson & Robertson (2006)
- Alook-and-feel
- Busability and humanity
- CPerformance
- DOperational and Environmental
- EMaintainability and Support
- FSecurity
- GCultural
- HLegal
16This non-functional requirement is an example of a [blank_start]look-and-feel[blank_end] requirement.
- Alook-and-feel
17This non-functional requirement is an example of a [blank_start]usability and humanity[blank_end] requirement.
- Ausability and humanity
18This non-functional requirement is an example of a [blank_start]performance[blank_end] requirement.
- Aperformance
19This non-functional requirement is an example of a [blank_start]operational and environmental[blank_end] requirement
- Aoperational and environmental
20This non-functional requirement is an example of a [blank_start]maintainability and support[blank_end] requirement
- Amaintainability and support
21This non-functional requirement is an example of a [blank_start]security[blank_end] requirement
- Asecurity
22This non-functional requirement is an example of a [blank_start]cultural[blank_end] requirement
- Acultural
23The list below represents the Project Issues section of the Volere template. Fill in the blanks.
- O[blank_start]pen[blank_end] I[blank_start]ssues[blank_end]: issues that have arisen from the requirements activities, but are not yet resolved
- [blank_start]Off[blank_end]-[blank_start]the[blank_end]-[blank_start]Shelf[blank_end] Solutions: a record of ready-made components that might be used in the project
- N[blank_start]ew[blank_end] P[blank_start]roblems[blank_end]: possible problems caused by the introduction of the product
- T[blank_start]asks[blank_end]: highlights the effort required to deliver the product
- [blank_start]Migration[blank_end] to the New Product: things that need to be done after the product has been installed but before it can work successfully.
- [blank_start]Risks[blank_end]: risks the project is likely to face, together with strategies for coping
- [blank_start]Costs[blank_end]: estimate of the cost or effort
- User D[blank_start]ocumentation[blank_end] and [blank_start]Training[blank_end]: plan for writing the user instructions and documentation.
- [blank_start]Waiting[blank_end] Room: requirements that for some reason cannot be included in the current release of the product
- [blank_start]Ideas[blank_end] for Solutions: design ideas that may become useful- Apen
- Bssues
- COff
- Dthe
- EShelf
- Few
- Groblems
- Hasks
- IMigration
- JRisks
- KCosts
- Locumentation
- MTraining
- NWaiting
- OIdeas
24Fill in the blanks in the Volere template sections:
- Project [blank_start]Drivers[blank_end]: The reasons and motivators of the project
- Product [blank_start]Constraints[blank_end]: restrictions and limitations
- [blank_start]Functional[blank_end] [blank_start]Requirements[blank_end]: functionality of the product
- [blank_start]Non-Functional[blank_end] [blank_start]Requirements[blank_end]: Properties the product must have
- Project [blank_start]Issues[blank_end]: concerns brought to light- ADrivers
- BConstraints
- CFunctional
- DRequirements
- ENon-Functional
- FRequirements
- GIssues
Información
- Descripción
- Software Engineering Test sobre Tutorial 3, creado por Frans k el 02/05/2018.
- Autor
- Frans k
- Idioma
- English
- Visitas
- 3
- Etiquetas
- Valoración
- Aún sin valoraciones Valora este test