Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
29 Cards in this Set
- Front
- Back
Requirements Engineering |
Understanding the problem Describing the problem Agreeing upon the problem Agreeing upon the boundaries of the problem |
|
Two types of UML Diagrams |
Static diagrams Dynamic diagrams show execution |
|
Most often used diagram |
Class diagram: 75% Use-case diagram and communication: 50% |
|
Name 6 static diagrams |
class component deployment interaction overview object package |
|
Name 7 dynamic diagrams |
activity communication composite struture sequence state machine timing use case |
|
Define UML class diagram |
Depicts the static structure of a system |
|
Draw a class diagram |
Publication [isbn :string, publicsher: string] [archive()] <-------- Book [author : string, title: string] [borrow(Client), return()] Journal [name :string] |
|
Draw association class diagram |
[Library] <---- is member of--- [Client] | | [Membership (id)] |
|
Draw composition class diagram |
Lines with dark diamonds. Example: Book class that contains three string attributes (attributes will draw lines with dark diamond to book) |
|
Draw interface class diagram |
Interface has dotted arrows. Example: <<interface>> Financial Data <- - - - - - - - Employee |
|
Name the four modeling techniques |
Entity-relationship modeling Finite state machines Data flow diagrams CRC cards |
|
Define Entity-Relationship modeling |
entity: distinguishable object of some type relationship: association between two or more entities entity type: typeo f a set of entities attribute: type of a set of attribute values attribute value: peice of information describing an entity |
|
Draw an ER-Diagram |
|
|
Define Software Architecture |
Architecture is the fundamental organization of a system embodied in its components, their relationships to each other and to the environment and the principles guiding its design and evolution. |
|
Show where architecture is in the life cycle |
|
|
Why is architecture important? |
1] Architecture is the vehicle for stakeholder communication 2] Architecture manifests the earliest est of design decisions 3] Architecture is a transferable abstraction of a system |
|
Draw the global workflow in architecture design
|
[Context] -------| |--- [Architecture] (backlog) [Requirements] ---^ ^--- [Evaluation results] Know that backlog is the center |
|
fill in |
|
|
List 8 stakeholders |
Architect Requirements engineer Designer Implementor Testor, Ingerator Maintainer Manager Quality Assurance |
|
Name the three design categories (CBS) |
Creational Patterns Structural (static) patterns Behavior (dynamic) patterns |
|
Know the three steps of implicit-invocation |
1. 2. 3. |
|
What is white-box testing? |
To ensure that all statements and conditions have been executed at least once. |
|
What is a "Good" Test? |
Has a high probability of finding an error Is not redundant Neither too simple nor too complex. |
|
Name the 5 design principles |
Abstraction Modularity, coupling and cohesion information hiding limit complexity hierarchical structure |
|
What is cohesion |
The glue that keeps a module together |
|
What is coupling |
the strength of connection between modules |
|
What are the types of cohesion? |
Functional Sequential Communicational Procedural Temporal Logical Coincidental |
|
What are the types of coupling? |
Content coupling Common coupling External coupling Control coupling Stamp coupoling Data coupling |
|
Four information hiding types |
algorithm data structure details of external interface resource allocation policy |