Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

Software Engineering > 10 Overview > Flashcards

10 Overview Flashcards

(65 cards)

Start Studying
1
Q

Work you do / Activities

A

Workflow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What “quality” is

A

Meeting specs (not necessarily good)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How intertwined things are

A

Coupling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

How well things work together

A

Cohesiveness

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Lifecycle model phases

A

Requirements, Analysis, Design, Implementation (Test)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Requirements changing during process

A

Moving target problem

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Component of project

A

Artifact

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Humans can only focus on 7 pieces of info

A

Miller’s Law

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Repeating

A

Iteration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Improves quality of features

A

Iteration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Piece-by-piece additions

A

Incrementation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Adds functionality

A

Incrementation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Way we make software; LCM + methodology

A

Software Process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Major OO methodology

A

Unified Process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

How to graphically represent software

A

Unified Modeling Language

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Set of UML diagrams representing software aspects

A

Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Requirements workflow

A

Client needs, deadlines, constraints

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Analysis workflow

A

Analyze and refine requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Design workflow

A

Translate requirements into steps

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

CASE for 1-2 workflows

A

Workbench

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

CASE for all workflows

A

Environment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Set of versions of each artifact in current build

A

Configuration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Helps with dev and maintenance problems

A

Configuration Control Tools

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Configuration of all artifacts in “default” product

A

Baseline

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Selects right version of each artifact for a product
Build Tool
26
A human fucked up
Fault
27
Observed result of a fuck-up
Failure
28
Amount of fuck-up
Error
29
General term for fuck-up
Defect
30
Formal review
Inspection
31
Informal review
Walkthrough / Code Review
32
Coupling between modules should be
Low
33
Cohesion inside modules should be
High
34
Data Coupling
Every arg is simple or a structure for which all elements are used by module
35
Hiding implementation details from being seen outside the module
Information Hiding
36
Parts of software project management plan
Work to do, resources to use, money to pay
37
Resources
People, hardware, software
38
Project Functions
Project management, QC, etc
39
Activities / Tasks result in
Work Products
40
Date a work product is completed
Milestone
41
Workflow
Work you do/activities
42
Coupling
Interaction between modules
43
Cohesiveness
How well a module works internally
44
Artifact
Component of project
45
Miller's Law
Humans can only focus on 7 pieces of info
46
Iteration
Repeating
47
Incrementation
Piece-by-piece addition
48
Software Process
LCM + Methodology, way we make software
49
UML
Graphic representation of software
50
Model
Set of UML diagrams
51
Workbench
CASE tool for 1-2 workflows
52
Environment
CASE tool for all workflows
53
Fault
A human fucked up
54
Error
The amount of fuck-up
55
Failure
Observed result of a fuck-up
56
Defect
All-inclusive term for fuckiness
57
Information Hiding
Hiding implementation details from being seen outside the module
58
Milestone
Date a work product is completed
59
5 Basic Metrics
Cost, Duration, Effort, Quality, Size
60
Non-execution testing
Code reviews
61
Modularity types
Objects, methods, procedures, functions
62
3 work categories
Project functions, activities > tasks
63
Unified Process
A flavor of Agile
64
RUP phases
Inception (Reqs), Elaboration (Analysis/Design), Construction (Implementation), Transition (delivery)
65
FURPS
Functional, Usability, Reliability, Performance, Supportability

Software Engineering (7 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions