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;
35 Cards in this Set
- Front
- Back
Verification
|
Are we building the system right?
|
|
Validation
|
Are we building the right system?
|
|
Analysis
|
To break down
|
|
Design
|
To build up
|
|
Myers- Briggs
|
Sixteen possible variants
Four dimensions |
|
(I) Introversion Vs. (E) Extroversion
|
Where do you get your energy?
reserved or expressive |
|
(S) Sensing Vs. (N) Intuition
|
How do you take in information?
Detailed and fact or Big picture |
|
(T) Thinking Vs (F) Feeling
|
How do you make decisions?
Analysis or values |
|
(J) Judging Vs. (P) Perceptive
|
How do you deal with time?
Plans or Options |
|
Tuckman's Group Development Model
|
Forming
Storming Norming Performance |
|
(IR) in functional objectives
|
Increase Revenue
|
|
(AC) in functional objectives
|
Avoid Cost
|
|
(IS) in functional objectives
|
Improve Service
|
|
Whats a stakeholder?
|
person, group member or system who affects or can be affected by an orgs actions
|
|
Features
|
An ACTION that yields a RESULT on a OBJECT
|
|
Stakeholders needs
|
It is not possible to meet all stakeholders needs
Prioritization and compromise required |
|
Project Scope
|
Describes what other projects its associated with, and anything else that affected or influenced by this document
|
|
Function vs Constraints
|
Behavioral that the system should support
or Non-functional requirements or attributes |
|
Functional Objective
|
WHAT the system will do ?
WHY they system will do it ? HOW the objective has been met ? |
|
Complete Functional Objective Statement
|
<POSITIVE > The system shall....
<function>, creating <IR AC IS> benefits. Evidence will be measured by <x> improvement in <measurable performance> |
|
Iron Triangle
|
Scope
Schedule Cost |
|
Context Diagram
|
1. Scope- Illustrates the source of problem
2. The externals- Sinks data 3. Data Flow- Control flow into and out of a system |
|
Data flow Diagram
|
Yourdon-DeMarco vs, Gane- Sarrson
Models the essential functions and data of the system Represents data, not action Labeled using noun phrases (no verbs) |
|
Inflows on Context Diagrams
|
triggers or helps process events
|
|
Outflow on Context Diagrams
|
responses to events
|
|
Externals (Terminators)
|
no control over
outside the system |
|
Event Table
|
Trigger-> Source -> Activity -> Response -> Destination
|
|
Bad Context Diagram have
|
Verbs as names
flows between entities No names |
|
Use Case
|
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 |
|
Scenario
|
the sequence of actions required
|
|
Use case
|
Like ping pong
Actor takes a step System responds Actor takes a step System............. |
|
Pre Condition
|
Documents any condition that must be satisfied before the use case can begin
|
|
Post Condition
|
States how the world has changed because of the execution of the use case
|
|
Invariant
|
A condition which is maintained throughout the use case
|
|
Prototype
|
Non working mock up
|