Cse 3232 Final (2013)

Front 1

Verification

Back 1

Are we building the system right?

Front 2

Validation

Back 2

Are we building the right system?

Front 3

Analysis

Back 3

To break down

Front 4

Design

Back 4

To build up

Front 5

Myers- Briggs

Back 5

Sixteen possible variants
Four dimensions

Front 6

(I) Introversion Vs. (E) Extroversion

Back 6

Where do you get your energy?

reserved or expressive

Front 7

(S) Sensing Vs. (N) Intuition

Back 7

How do you take in information?

Detailed and fact or Big picture

Front 8

(T) Thinking Vs (F) Feeling

Back 8

How do you make decisions?
Analysis or values

Front 9

(J) Judging Vs. (P) Perceptive

Back 9

How do you deal with time?
Plans or Options

Front 10

Tuckman's Group Development Model

Back 10

Forming
Storming
Norming
Performance

Front 11

(IR) in functional objectives

Back 11

Increase Revenue

Front 12

(AC) in functional objectives

Back 12

Avoid Cost

Front 13

(IS) in functional objectives

Back 13

Improve Service

Front 14

Whats a stakeholder?

Back 14

person, group member or system who affects or can be affected by an orgs actions

Front 15

Features

Back 15

An ACTION that yields a RESULT on a OBJECT

Front 16

Stakeholders needs

Back 16

It is not possible to meet all stakeholders needs

Prioritization and compromise required

Front 17

Project Scope

Back 17

Describes what other projects its associated with, and anything else that affected or influenced by this document

Front 18

Function vs Constraints

Back 18

Behavioral that the system should support
or
Non-functional requirements or attributes

Front 19

Functional Objective

Back 19

WHAT the system will do ?
WHY they system will do it ?
HOW the objective has been met ?

Front 20

Complete Functional Objective Statement

Back 20

<POSITIVE > The system shall....
<function>, creating <IR AC IS> benefits.
Evidence will be measured by <x> improvement in <measurable performance>

Front 21

Iron Triangle

Back 21

Scope
Schedule
Cost

Front 22

Context Diagram

Back 22

1. Scope- Illustrates the source of problem
2. The externals- Sinks data
3. Data Flow- Control flow into and out of a system

Front 23

Data flow Diagram

Back 23

Yourdon-DeMarco vs, Gane- Sarrson
Models the essential functions and data of the system
Represents data, not action
Labeled using noun phrases (no verbs)

Front 24

Inflows on Context Diagrams

Back 24

triggers or helps process events

Front 25

Outflow on Context Diagrams

Back 25

responses to events

Front 26

Externals (Terminators)

Back 26

no control over
outside the system

Front 27

Event Table

Back 27

Trigger-> Source -> Activity -> Response -> Destination

Front 28

Bad Context Diagram have

Back 28

Verbs as names
flows between entities
No names

Front 29

Use Case

Back 29

Sequence of actions a system performs that yields an observable result of value to the particular actor

(captures the main functionality from a actors prospective)

Black box

Front 30

Scenario

Back 30

the sequence of actions required

Front 31

Use case

Back 31

Like ping pong
Actor takes a step
System responds
Actor takes a step
System.............

Front 32

Pre Condition

Back 32

Documents any condition that must be satisfied before the use case can begin

Front 33

Post Condition

Back 33

States how the world has changed because of the execution of the use case

Front 34

Invariant

Back 34

A condition which is maintained throughout the use case

Front 35

Prototype

Back 35

Non working mock up