Busy. Please wait.

show password
Forgot Password?

Don't have an account?  Sign up 

Username is available taken
show password


Make sure to remember your password. If you forget it there is no way for StudyStack to send you a reset link. You would need to create a new account.
We do not share your email address with others. It is only used to allow you to reset your password. For details read our Privacy Policy and Terms of Service.

Already a StudyStack user? Log In

Reset Password
Enter the associated with your account, and we'll email you a link to reset your password.

Remove Ads
Don't know
remaining cards
To flip the current card, click it or press the Spacebar key.  To move the current card to one of the three colored boxes, click on the box.  You may also press the UP ARROW key to move the card to the "Know" box, the DOWN ARROW key to move the card to the "Don't know" box, or the RIGHT ARROW key to move the card to the Remaining box.  You may also click on the card displayed in any of the three boxes to bring that card back to the center.

Pass complete!

"Know" box contains:
Time elapsed:
restart all cards

Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

  Normal Size     Small Size show me how


Lokapróf 2013 - áherslur: Requirement alanysis

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
Created by: Bjarni