Fichas
M363 Unit 2
Fichas del conjunto (17)
- 1Where and when does the requirements engineering process take place in an iterative and incremental process?Early in the software development process. But in both iterative and incremental processes the requirements are revisited again and again.
- 2What is wrong with the following requirement: the system should provide acceptable performance under maximum load conditionsThe requirement is ambiguous and unverifiable
- 3What is wrong with the following requirement: If the system fails in production there should be minimal loss of data.It is ambiguous and unverifiable
- 4What are requirements?Requirements are the functions and qualities we want of a product.
- 5What are the benefits of documenting requirements within a project?Requirements documentation records decisions.
- 6MOSCOWmust haves, should haves, could haves, won't haves
- 7What do functional requirements deal with?usability, reliability, maintainability
- 8What is one property that a functional requirement should not possess?a statement about quality
- 9technical solution requirementrelate to functionality that is needed purely because of the chosen technology i.e. to make the chosen implementation work correctly
- 10functional requirementswhat the system should do
- 11non-functional requirementsqualities the system should have
- 12look and feel requirementsdescribe the overall appearance and behaviour of the product to its users
- 13When do cultural requirements usually arise?In different cultures including different corporate cultures
- 14What are the three aspects of security from a requirements perspective? (CIA)confidentiality, integrity, availability
- 15requirement: the system shall accept a credit card number from a clientfit criteria: a valid credit card number has been stored in the system.
- 16functional requirement: the system shall accept a credit card from the clientnon-functional requirement: the credit card should be accepted securely
- 17non-functional requirement: the credit card should be accepted securelyfit criteria: the credit card number should be revealed to a third party in less than 0.0001% of the time
Información
- Descripción
- Fichas sobre M363 Unit 2, creado por po_ el 22/06/2014.
- Creado por
- po_
- Visitas
- 29
- Valoración
Más sobre Software Requirements Types and Specification