Save
Busy. Please wait.
Log in with Clever
or
show password
Forgot Password?
Don't have an account?  Sign up 
Sign up using Clever
or
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. Your email address is only used to allow you to reset your password. See 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.
focusNode
Didn't know it?
click below
 
Knew it?
click below
Don't Know
Remaining cards (0)
Know
0:00
edit
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

Software robustness

QuestionAnswer
Robustness 1) Fault tolerant 2) Graceful shutdown 3) Meaningful feedback on errors 4) Recoverable 5) Reliable
How to obtain robust code 1) Program defensively 2) Hide information 3) Reduce Complexity 4) Expect the impossible
Program defensively 1) Require your preconditions to hold 2) Ensure your postconditions hold 3) Defend your gates against intruders 4) Let no spies get out
Hide information 1) Use the language’s build in incapsulation mechanisms 2) or trick the language to hide the information 3) With no walls, defending the gates alone is not very effective 4) Never reveal your weaknesses.
Reduce Complexity 1) Bundle parts of code with high cohesion 2) Decouple bundled parts 3) Be sure that your units are well organized and cooperating 4) Don’t let one unit’s defeat loose the battle
Expect the impossible Remember Murphy’s law . . . Anything that can go wrong will go wrong
Defensive programming 1) Always check the preconditions, trust nobody! 2) Check your postconditions, doubt yourself! 3) Check your invariants, Remember the ACID rules Atomicy Consistency Isolation Durability
The Big V 1) Validation Planning - Validation Reporting 2) User requirements - User Acceptance Testing 3) System requirements - System Testing 4) Technical Architecture - Installation Qualification 5) Detailed Design - Unit&Integration Testing 6) Config,dev
Testing documents 1) Specification of invariants, pre-, and postconditions. 2) Specification of tests to run (perform). 3) Specification of the coverage of the tests. 4) Specification of expected output of the tests.
How to encapsulate 1) Only use public where nescesary according to contract. 2) Use Facade objects. 3) Use Data Transfer Objects and tokens. 4) Be as abstract as possible 5) Don’t promise more than required
Created by: timeakiss
Popular Computers sets

 

 



Voices

Use these flashcards to help memorize information. Look at the large card and try to recall what is on the other side. Then click the card to flip it. If you knew the answer, click the green Know box. Otherwise, click the red Don't know box.

When you've placed seven or more cards in the Don't know box, click "retry" to try those cards again.

If you've accidentally put the card in the wrong box, just click on the card to take it out of the box.

You can also use your keyboard to move the cards as follows:

If you are logged in to your account, this website will remember which cards you know and don't know so that they are in the same box the next time you log in.

When you need a break, try one of the other activities listed below the flashcards like Matching, Snowman, or Hungry Bug. Although it may feel like you're playing a game, your brain is still making more connections with the information to help you out.

To see how well you know the information, try the Quiz or Test activity.

Pass complete!
"Know" box contains:
Time elapsed:
Retries:
restart all cards