Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

Software Engineering > 10 Overview > Flashcards

10 Overview Flashcards

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
Q

Selects right version of each artifact for a product

A

Build Tool

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

A human fucked up

A

Fault

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

Observed result of a fuck-up

28
Q

Amount of fuck-up

29
Q

General term for fuck-up

30
Q

Formal review

A

Inspection

31
Q

Informal review

A

Walkthrough / Code Review

32
Q

Coupling between modules should be

33
Q

Cohesion inside modules should be

34
Q

Data Coupling

A

Every arg is simple or a structure for which all elements are used by module

35
Q

Hiding implementation details from being seen outside the module

A

Information Hiding

36
Q

Parts of software project management plan

A

Work to do, resources to use, money to pay

37
Q

Resources

A

People, hardware, software

38
Q

Project Functions

A

Project management, QC, etc

39
Q

Activities / Tasks result in

A

Work Products

40
Q

Date a work product is completed

41
Q

Workflow

A

Work you do/activities

42
Q

Coupling

A

Interaction between modules

43
Q

Cohesiveness

A

How well a module works internally

44
Q

Artifact

A

Component of project

45
Q

Miller’s Law

A

Humans can only focus on 7 pieces of info

46
Q

Iteration

47
Q

Incrementation

A

Piece-by-piece addition

48
Q

Software Process

A

LCM + Methodology, way we make software

49
Q

UML

A

Graphic representation of software

50
Q

Model

A

Set of UML diagrams

51
Q

Workbench

A

CASE tool for 1-2 workflows

52
Q

Environment

A

CASE tool for all workflows

53
Q

Fault

A

A human fucked up

54
Q

Error

A

The amount of fuck-up

55
Q

Failure

A

Observed result of a fuck-up

56
Q

Defect

A

All-inclusive term for fuckiness

57
Q

Information Hiding

A

Hiding implementation details from being seen outside the module

58
Q

Milestone

A

Date a work product is completed

59
Q

5 Basic Metrics

A

Cost, Duration, Effort, Quality, Size

60
Q

Non-execution testing

A

Code reviews

61
Q

Modularity types

A

Objects, methods, procedures, functions

62
Q

3 work categories

A

Project functions, activities > tasks

63
Q

Unified Process

A

A flavor of Agile

64
Q

RUP phases

A

Inception (Reqs), Elaboration (Analysis/Design), Construction (Implementation), Transition (delivery)

65
Q

FURPS

A

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