261_review Flashcards
1
Q
Concept of database and database management systems
A
DB=an integrated collection of stored data that is centrally mannaged and controlled. Mgm-system software that manages and controls access tdb
2
Q
What is a relational database system (RDBMS)?
A
a db mgm system that stores data in tables
3
Q
Schema
A
a description of the structure-content-and access controls of a physical data store or database
4
Q
Table
A
2D data structure containing rows and columns alscalled a relation
5
Q
Row
A
portion of table containing data that describes one entity-relationship or object-alscalled tuple or record
6
Q
Column/field
A
a column of a relational database table alscalled an attribute
7
Q
Primary key
A
a key used tuniquely identify a row of a relation db table
8
Q
Foreign key
A
a field value stored in one relational db table that alsexists as a primary key value in another table
9
Q
Representing relationship
A
are represented within a relatikon db by foreign keys
10
Q
Enforcing referential integrity
A
a consistent relational db state in which every foreign key value alsexists as a primary key value
11
Q
Normalization
A
a technique that ensures relational db schema quality by minimizing data redundancy
12
Q
Functional dependency
A
a 1-1 correspondence between 2 field values
13
Q
1NF
A
a relational db table structure that has nrepeating fields or groups of fields
14
Q
2NF
A
a relational db table structure in which every non-key field is functionally dependent on the primary key
15
Q
3NF
A
a relational db table structure in which nnon-key field is functionally dependent on any other non-key field
16
Q
Distributed Databases Architecture
A
organizations typically store data in many different databases-often under the control of many different dmbss
17
Q
Single database server
A
Clients on one or more LANS share a single database locatedn a single computer system
18
Q
Replicated database server
A
Each server stores a separate copy of the needed data. Clients interact with the db server on their own LAN
19
Q
Partitioned database server
A
minimize need for db synchronization by partitioning db contents among multiple db servers
20
Q
Federated database server
A
is commonly used taccess data stored in dbs with incompatible storage models or dbmss.
21
Q
What is UML? What type of modeling is it used for?
A
uml is the accepted standard Omodeling language of the industry.
22
Q
Use case model
A
A collection of models that can be used tcapture system requirements based on use cases with the object-oriented approach
23
Q
The objective of an use case model
A
is tidentify and define all of the elementary business processes that the system must support.
24
Q
Use cases
A
a diagram tshow the various user roles and how these roles use the system
25
Actor
stick figure that represents a user outside the system
26
Automation boundary
the boundary seperating the user/actor from the system
27
<> relationship
adiditional use case that other use cases may need tuse tperform their function-i.e. validate customer
28
Activity Diagram
is an easily understood diagram tdocument the workflows of the business processes (swimlanes)
29
Use activity diagram tdescribe use cases
stick-figure-ovals-lines connecting
30
Understand the notation of an activity diagram
black circle starts flow-oval boxes-black bar indicates repitition-double circle indicates end-swimlane for system-clerkactor-sometimescustomer
31
Know how tconstruct an activity diagram
swimlanes-oval boxes-etc.
32
System Sequence Diagram (SSD)
Contains an actor-the system and twparallel dashed lines below
33
The purpose of a SSD
is used tdescribe the flow of information intand out of the automated sytem.
34
Understand the notation of SSD
input message on solid line inquireOnitem(catalogID-prodID-size)-return value on dashed line -item information
35
Know how tconstruct a SSD
rectangle for loops OR *[another item] description-price-extendedprice on top line. := additem(itemID-quantity)-under the line
36
State Machine Diagram
used tallow analysts tidentify and document which domain objects require status checking
37
The purpose of a state machine diagram
sometimes it is important tknow the status of a problem domain objects-i.e. state of an order
38
Understand the terminologies of state machine diagram
state-transition-pseudostate-destination state-origin state-message event-guard condition-path
39
State
A condition during an object's life when it satisifies some criterion-performs some action-or waits for an event
40
Transition
the movement of an object from one state tanother state
41
Pseudostate
the starting point of a state machine diagram indicated by a black dot
42
Destination sate
for a particular transition-the state twhich an object moves after the completion of the transition
43
Origin sate
for a particular transition-the original state of an object from which the transition occurs
44
Message event
the trigger for a transition which causes the object tleave the origin state
45
Guard-condition
a true/false test tsee whether a transition can fire
46
Path
a sequential set of connected states and transitions
47
What are the composite states?
a state containing other states and transitions (that is a path)
48
Know how tconstruct a state machine diagram
psuedostate black dot starts-oval/square state-arrow path with message fill()-lowMsg().
49
How does an Oprogram work?
consists of a set of program objects that cooperate taccompliswh a result
50
List the models used in the Odesign
component diagram-deployment diagram-design class diagram-interaction diagram-design state machine diagram-package diagrams
51
Oarchitectural design
first step in system design
52
Enterprise-level system
a system that has shared resources among multiple people or groups in an organization
53
Client/server network-based systems
connection is permanent tthe system and values in variables can be passed back and forth and can be remembered by each component in the system. View layer has direct access tfields in system.
54
Internet-based systems
npermenant connection client and server dnot know the state of each other
55
Component Diagram
a type of implementation diagram that shows the overall system architecture and the logical components within it (ports/sockets square diagram)
56
Notation
sockets-ports-conponents-
57
API
application program interface - the set of public methods that is available tthe outside world
58
Two-Layer architecture design
web page code i.e. php and the sub program taccess the data i.e. mysql
59
Three-Layer architecture design
for systrem s that require more complex business logic it is better tadd a layer sthat separate classes exist for botht he domain logic and the data access process.
60
What are web services?
computer programs that provide services tother systems via the internet and are posted in a directory sthat other systems can find and use them.
61
Deployment Diagram
a type of implementation diagram that shows the physical components across different locations (3d rectangle with :server)
62
Purpose of the deployment diagram
shows the placement of various physical nodes across different locations
63
Notation of the deployment diagram
3d rectangle with :server underlined
64
Differences between the domain class diagram and the design class diagram
elaborated attributes and method signatures ie.e ():string/public private
65
Standard stereotypes of design class
is simply a way tcategorize a model element as a certain type. Indicated by guillemets <<>>
66
Entity class
a design identifier for a problem domain class
67
Control class
a class that mediates between boundary classes and entity classes acting as a switchboard between the view layer and domain layer
68
Boundary class
or view class - a class that exists on a systems automation boundary such as an input layer
69
Data access class
a class that is used tretrieve data from a database
70
Design class diagram
standard three cell diagram we used in java
71
Three compartments
stereotype name/attribute list/method list
72
Visibility
denotes wheter other objects can directly access the attribute- the + or - sign for private or public
73
Method signature
a notation that shows all of the infomration needed tinvoke or call the method
74
Overload method
a method with one name but twor more parameter lists
75
Class-level method
a method that is associated with a class instead of with objects of the class
76
Class-level attribute
an attribute that contains the same value for all objects in the system
77
Overridden method
a method in a subclass with inheritance that overrides the moethd in the parent class
78
Abstract class
a class that can never be instantiated (nobjects can be created of this type - i.e. parent class
79
Concrete class
a normal class that can be instantiated (objects can be created)
80
Navigation visibility
a design principle in which one object has a reference tanother object and thus can interact with it
81
CRC card
an index card with lines that partition int3 areas-class name-responsibility-and collaboration classes
82
Purpose of crc card
brainstgorming technique that is quite popular among oodevelopers
83
Process of applying CRC cards in class design
usually done in a brainstorming session.
84
Design principles - Encapsulation and information hiding
principal of objects in which both data and program logic are included within a single self-contained unit
85
Design principles - Coupling
qualitative measure of how closely the classes in a design class diagram are linked
86
Design principles - Cohesion
a qualitative measure of the consistency of functions within a single class
87
Design principles - Protection from variations
principle in which parst of a system that are unlikely tchange are segregated from those that will
88
Design principles - Indirection
principle in which an intermediate class is placed between twclasses tdecouple them but still link them
89
Design principles - Object responsibility
principle in which objects are responsible for carrying out system processing
90
What does the term of use case realization mean?
the process of elaborating the detailed design with interaction diagrams of a particular use case
91
What does the term of design patterns mean? What are the benefits of using design patterns?
standard design techniques and templates that are widely recognized as good practice
92
What is the purpose of using the controller pattern?
designer often define an intermediary class that acts as a buffer between the user interface and the domain classes - we call these classes use case controllers
93
Understand three-layer sequence diagram
more complex systems include classes whose sole responsibility is texecute database sql statements-get the results of the query-provide the infomration tthe domain layer.
94
Components of a sequence diagram
view layer-business layer-data access layer
95
Activation lifeline
a representation of the period in which a method of an object is alive and executing
96
First cut sequence diagram
detailed sequence diagram uses all of the elements that an SSD uses.
97
How does a design sequence diagram differ from a SSD?
difference is that the :System object is replaced by all of the internal objects and messages within the system.
98
What classes are included in first cut sequence diagram?
all the classes needed taccomplish the use case?
99
Explain syntax of a message on a sequence diagram.
message name should reflect the requested service.
100
The assumptions of developing a first cut sequence diagram
perfect technology (not including user login steps)-perfect memory assumption (objects assumed created in memory and available for use case)-perfect solution assumption (assumes nexception conditions)
101
Multilayer sequence diagram
incluses the prevous stuff plus userinterface classes and data access classes
102
Design viewer layer
consists of a single user interface window or more complex multiple windows tenter and view the data
103
Design data layer
keeping the code separate from the viewing layer sthat there is a class acting as 3rd party between view and data
104
Communication Diagram
are useful for showing a different view of the use case - one that emphasizes coupling - easier tchange and rearrange on the fly
105
Differences between a sequence diagram and a communication diagram
lifeline and activation lifeline symbols are not used-alsfocuses more on the objects themselves
106
The notations of a communication diagram
actor-message-objects and a link symbol that sends or receives messages
107
Package Diagram
is simply a high-level diagram that allows designers tassociate classes of related groups
108
Purpose
show related components and dependencies
109
Dependency relationship
a relationship between packages classes or use cases that indicates a change in the independent item will require a corresponding change in the dependant item
110
view layer
view layer(display forms-reports-data fields-capture clicks-rollovers-key entry-accept input-edit and validate input-forward input tdomain layer-start and shut down system)
111
domain layer
create problem domain classes (persistent)-process all business rules with appropriate logic-prepare persistent classes for storage tthe db
112
data access layer
establish and maintain connections tthe db-contain all sql statements-process result sets of sqls intappropriate domain objects-disconnect gracefully from db
113
Design Patterns
patterns exist at various levels of abstraction-may be a class definition or only an approach tsolving a problem
114
Classification of GoF design patterns
basic classification scheme for patterns-creational-structional-behavioral
115
Creational
help assign responsibilities tclasses tinstantiate new objects
116
Structural
provide solutions tmeet the architectural needs of the system-that is the set of classes and the ways they are related- help solve problems associated with indirection
117
Behavioral
provide solutions tproblems that are related tthe way internal system processes execute-for example the iterator pattern solves the problem of how tprocess arrays and lists effectively
118
Adapter
roughly akin ttravel adapters in that it plugs an external class intan existing system
119
Factory
in oop a solution is thave some classes that are factories-these classes instantiate objects from utility classes
120
Singleton
one instance
121
Observer
approach tsolving an important system problem
