Final Flashcards

(57 cards)

1
Q

Lava Flow Project

A

Code that has been worked on for many years

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

Phases of Software

A

1) Specification
2) Development
3) Validation
4) Evolution

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

Difference between software engineering and computer science

A

Theory vs practicality

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

Difference between systems and software engineering

A

Systems engineer are in changed with resources.

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

Connection refuse

A

no service at port

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

Connection time out

A

firewall

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

Waterfall

A

used for a large systems project

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

Incremental development

A

Outline description

Reduced cost of changing specs

Easier testing

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

COTS

A

Commercial-off-the-shelf

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

Stakeholder

A

anyone who has interest in the outcome/system

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

Design Activities(4)

A

Architectural design

Interface design

Component design

Database design

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

Verification

A

testing code

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

Validation

A

working in the way we want it to work

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

Testing-DEV

A

Testing each component

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

System testing

A

Testing a system as a whole

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

Acceptance testing

A

Testing customer data

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

Demarcation

A

line between evolution and development is increasing irrelevant

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

Change avoidance

A

Avoidance process that includes activities that can anticipate possible changes(prototypes)

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

change tolerance

A

Tolerance able to accommodate changes with least cost

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

Functional

A

specific tasks that need to be solved

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

Non-function

A

not exactly mentioned

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

Boehm’s spiral model

A

First theoretical model that water model users can work

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

RUP

A

Rational Unified Process -

Inception

Elaboration

Construction

Transition

24
Q

Agile

A

Individual and interactions over processes and tools.

Working software over comprehensive documentation

25
Principles of agile
Customer involvement Incremental delivery People not process Change
26
Problems with agile
Difficult to keep the interest of customers Small or mid size teams Prioritizing changes to multiple stakeholders Simplicity requires more work Contractual
27
Extreme Programming
Regression testing & test driven Full time customer engagement Pair Programming - one typing and one watching Collective ownership - ownership of just part vs whole
28
SRCUM - Product owner
Voice of customers Ranks and prioritize product
29
Scrum master
Servent-leader Buffer between team and customers Scrum process
30
Scrum tasks to complete
Product backlog
31
Mini tasks that user needs done
User stories
32
type of quick srcum meeting
Stand up meeting
33
What I did...
What i did yesterday, what im going to do today
34
Main job of scrum master
Shield development team from external distractions
35
Scrum Benefits
Broken down into set of manageable chunks Unstable requirements do not hold up progress
36
Brownfield system
interact with an existing system
37
Greenfield System
newly created
38
Scaling up
applying agile processing to larger teams
39
Scaling out:
applying agile processing to non-software development teams
40
Ethnography is effective for understanding existing processes, but cannot identify new features that should be added. (TRUE OR FALSE)
TRUE
41
Requirements Checking
``` Valid Consistent Complete Real Verifiable ```
42
Ethnography
Living with in the environment to learn
43
System perspectives(
Context models Process models: boarder model Use case Sequence diagrams
44
Generalization
Bottom up
45
Specialization
Top down
46
Which of the following is not a system characteristics
``` Performance Security Safety Availability Maintainability ```
47
4+1 model of architecture
``` Logical view Process view Development view Physical view Related use cases ```
48
Types of application types
``` Model view controler Layer Repository Client server Pipe and filter ```
49
Syntax Analyzer
grammer
50
Semantic analyzer
meaning
51
Observer
listener and delegation
52
Iterator
accessing elements in collections
53
GNU General Public License
Must make that software open source
54
GNU Lesser
DONT CHANGE link to open source components
55
Berkley
Can be concealed and private
56
Fake Object
Doesn't verify user input
57
Mock Object
Verify user input