Cs 2450

Front 1

Requirements Engineering

Back 1

Understanding the problem

Describing the problem

Agreeing upon the problem

Agreeing upon the boundaries of the problem

Front 2

Two types of UML Diagrams

Back 2

Static diagrams

Dynamic diagrams show execution

Front 3

Most often used diagram

Back 3

Class diagram: 75%

Use-case diagram and communication: 50%

Front 4

Name 6 static diagrams

Back 4

class

component

deployment

interaction overview

object

package

Front 5

Name 7 dynamic diagrams

Back 5

activity

communication

composite struture

sequence

state machine

timing

use case

Front 6

Define UML class diagram

Back 6

Depicts the static structure of a system

Front 7

Draw a class diagram

Back 7

Publication [isbn :string, publicsher: string] [archive()] <-------- Book [author : string, title: string] [borrow(Client), return()] Journal [name :string]

Front 8

Draw association class diagram

Back 8

[Library] <---- is member of--- [Client]

|

|

[Membership (id)]

Front 9

Draw composition class diagram

Back 9

Lines with dark diamonds. Example: Book class that contains three string attributes (attributes will draw lines with dark diamond to book)

Front 10

Draw interface class diagram

Back 10

Interface has dotted arrows. Example: <<interface>> Financial Data <- - - - - - - - Employee

Front 11

Name the four modeling techniques

Back 11

Entity-relationship modeling

Finite state machines

Data flow diagrams

CRC cards

Front 12

Define Entity-Relationship modeling

Back 12

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

Front 13

Draw an ER-Diagram

Back 13

Front 14

Define Software Architecture

Back 14

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.

Front 15

Show where architecture is in the life cycle

Back 15

Front 16

Why is architecture important?

Back 16

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

Front 17

Draw the global workflow in architecture design

Back 17

[Context] -------| |--- [Architecture]

(backlog)

[Requirements] ---^ ^--- [Evaluation results]

Know that backlog is the center

Front 18

fill in

Back 18

Front 19

List 8 stakeholders

Back 19

Architect

Requirements engineer

Designer

Implementor

Testor, Ingerator

Maintainer

Manager

Quality Assurance

Front 20

Name the three design categories (CBS)

Back 20

Creational Patterns

Structural (static) patterns

Behavior (dynamic) patterns

Front 21

Know the three steps of implicit-invocation

Back 21

1.

2.

3.

Front 22

What is white-box testing?

Back 22

To ensure that all statements and conditions have been executed at least once.

Front 23

What is a "Good" Test?

Back 23

Has a high probability of finding an error

Is not redundant

Neither too simple nor too complex.

Front 24

Name the 5 design principles

Back 24

Abstraction

Modularity, coupling and cohesion

information hiding

limit complexity

hierarchical structure

Front 25

What is cohesion

Back 25

The glue that keeps a module together

Front 26

What is coupling

Back 26

the strength of connection between modules

Front 27

What are the types of cohesion?

Back 27

Functional

Sequential

Communicational

Procedural

Temporal

Logical

Coincidental

Front 28

What are the types of coupling?

Back 28

Content coupling

Common coupling

External coupling

Control coupling

Stamp coupoling

Data coupling

Front 29

Four information hiding types

Back 29

algorithm

data structure

details of external interface

resource allocation policy