click below
click below
Normal Size Small Size show me how
Þarfagreining
Lokapróf 2013 - áherslur: Requirement alanysis
Question | Answer |
---|---|
Communicating with stakeholders of the project | Requires the document to be written in a non-technical language, regular users / managers / developers must all be able to understand the report |
What is the purpose of Requirement analysis | state *what* the system should do, communicate with stakeholders of the project and use as input to later stages of the development process |
Contents of a requirement analysis report | Almenn lýsing, kröfulisti, forgangsröðun, listi yfir use case, use case diagram og hlutverk. |
What is a requirement? | Vel útfærð mælanleg yfirlýsing sem hægt er að sannreyna s.s: "Notandi skal geta leigt bók". |
Functional requirements | •Implemented featuers (the user should be able to rent a book) •Rules (a user may not borrow more than 3 books simultaneously) |
Non_functional requirements | •Extensibility/scalability •Portability, reusability •Performance, hardware concerns •Cost savings •Trainings needs, etc... |
A requirement list will often look like this | •A number; incrementing number •Name/description: short description of the requirement •Use case numner(s): a list of use cases which have to do with this requirement •Priority: how important this requirement is: Status: approved/not |