GoConqr hat ein neues Design! Sag uns, wie es dir gefällt.

Karteikarten

M363 Unit 2

po_ Englisch 17 Karten

Karten in diesem Stapel (17)

  1. 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.
  2. 2What is wrong with the following requirement: the system should provide acceptable performance under maximum load conditionsThe requirement is ambiguous and unverifiable
  3. 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
  4. 4What are requirements?Requirements are the functions and qualities we want of a product.
  5. 5What are the benefits of documenting requirements within a project?Requirements documentation records decisions.
  6. 6MOSCOWmust haves, should haves, could haves, won't haves
  7. 7What do functional requirements deal with?usability, reliability, maintainability
  8. 8What is one property that a functional requirement should not possess?a statement about quality
  9. 9technical solution requirementrelate to functionality that is needed purely because of the chosen technology i.e. to make the chosen implementation work correctly
  10. 10functional requirementswhat the system should do
  11. 11non-functional requirementsqualities the system should have
  12. 12look and feel requirementsdescribe the overall appearance and behaviour of the product to its users
  13. 13When do cultural requirements usually arise?In different cultures including different corporate cultures
  14. 14What are the three aspects of security from a requirements perspective? (CIA)confidentiality, integrity, availability
  15. 15requirement: the system shall accept a credit card number from a clientfit criteria: a valid credit card number has been stored in the system.
  16. 16functional requirement: the system shall accept a credit card from the clientnon-functional requirement: the credit card should be accepted securely
  17. 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

Informationen

Beschreibung
Karteikarten am M363 Unit 2, erstellt von po_ am 22/06/2014.
Erstellt von
po_
Aufrufe
29
Bewertung

Mehr zu Software Requirements Types and Specification

Feedback

Worum geht es?

Wie gefällt dir das neue Design?

Dein Eindruck