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


Flashcards for 2nd CEN Exam

analysis focus is on the application domain
design focus on the solution domain
design window time in which design decisions have to be made
Identify Design Goals Additional NFRs, Trade-offs non-functional requirements
Subsystem Decomposition Layers vs Partitions Coherence & Coupling Functional Model
Identify Concurrency Identification of Parallelism (processes, threads) Dynamic Model
Hardware / Software Mapping Identification of NOdes, Special Purpose Systems, Buy vs Build Object Model
Persistent Data Management Storing Persistent Objets, Filesystem vs database Object Model
Global Resource Handling Access Control, ACL vs Capabilities Security Object Model
Software Control monolithic, event driven, concurrent processes Functional Model
Boundary Conditions Initialization, Termination, Failure Non-Functional Requirements
Design Trade offs: Functionality vs Cost vs Efficiency vs Rapid Development v Cost v Backward Compatibility vs Functionality vs Usability Cost vs Robustness Efficiency vs Portability Rapid Development vs Functionality Cost vs Reusability Backward Compatibility vs Readability
Subsystem Collection of classes, associations, operations, events and constraints that are closely interrelated with each other
Service Set of named operations that share a common purpose. (Their origin are use cases from functional model)
Subsystem Interface Set of fully typed UML operations; defined during object design
Application programmer's interface API specification of the subsystem interface in a specific programming language. Should only be used during implementation.
layer subsystem that provides a service to another subsystem with the following restrictions: only depends on services from lower layers; has no knowledge of higher layers.
partition horizontal division of layer into several independent subsystems; weakly coupled subsystem
virtual machine subsystem connected to higher and lower level virtual machines by "provides services for" associations. Abstraction that provides a set of attributes and operations.
High Coherence classes in subsystem perform similar tasks and are related to each other via many associations (good design)
Low coherence lots of miscellaneous and auxiliary classes, almost no associations
High Coupling Changes to one subsystem will have high impact on the other subsystem
Low coupling A change in one subsystem does not affect any other subsystem (good design)
Client / Server one or more servers produce services to instances of subsystems, called clients; End users interact with client.
Peer to Peer "Clients can be servers and servers can be clients."
Repository Subsystems access and modify data from a single data structure.
Model-view-controller model: responsible for application domain knowledge view: responsible for displaying application domain objects to the user controller: responsible for sequence of interactions with the user and notifying views of changes in the model
pipeline chain of processing elements arranged so that the output of one element is the input to the next element
system design activity that reduces the gap between the problem and an existing (virtual) machine
design goals describes the importnat system qualities defines the values against which options are evaluated
subsystem decomposition break down the overall system into manageable parts by using the principles of cohesion and coherence
architectural style pattern of a typical subsystem decomposition
software architecture instance of an architectural style
Created by: ejs09f