Busy. Please wait.
or

show password
Forgot Password?

Don't have an account?  Sign up 
or

Username is available taken
show password

why


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
Know
remaining cards
Save
0:01
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:
Retries:
restart all cards




share
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 des toolbox

Software design

QuestionAnswer
System design identifying large chunks of work that could be assigned to individual teams.
Object design specifying the boundaries between objects.
Component Reusable encapsulated well defined software. Cannot stand alone.
Subsystem Encapsulated well defined stand-alone software. Might or might not be an application by itself.
Application An end-usable piece of software.
System design strategies 1) Layered (high cohesion) 2) Use case based (low coupling) 3) Mixed or balanced FE - use cases BE - layered
Toolbox 1) Logical data model 2) Use case model 3) Communication model 4) Verification strategy
Logical data model 1) What should be persisted 2) Only entities 3) No implementation details
System operation contracts The interface is the code based operation contract Use strong typing. Make inline documentation (JavaDoc) have documentation close to code - easier to update. generates written code contracts. ETOs
Verification We have JUnit for the backend. That is put in a singleton format in the suit run on the system. All these tests are running on the contract, that is running on the backend.
Communicational model MVC + contract, contract + unit test, setup with bridge, system operation contract (interface + documentation), DTOs ETOs, Remote interface
Use case model 1) Use case diagram 2) Detailed Used Case 3) System Sequence diagram 4) System operational contracts
Created by: timeakiss