Exam 2 Software Process Flashcards

1
Q

A general term describing the over-arching process of developing software.

A

Software Process

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

What are the five elements of the Software Process?

A
Requirements Gathering
Design
Implementation
Testing 
Maintenance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the primary object-oriented methodology?

A

The unified process

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

an adaptive methodology for software construction

A

Unified Process

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

The 5 phases of the unified process

A
requirements workflow
analysis workflow
design workflow
implementation workflow
test workflow
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is meant by a phase of the Unified Process?

A

A phase is a series of smaller steps in a larger process

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

Who is responsible for the correctness of a product?

A

SQA Group (Software Quality Assurance)

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

What are CASE tools used for?

A

Software tools that assist software engineering teams in developing and maintaining software.

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

Name the 7 types of Team Organizations

A
Democratic Teams
Classical Chief Programmer Teams
Modified Chief Programmer Teams
Modern Hierarchical Programming Teams
Synchronize and Stabilize Teams
Agile Process Teams
Open-Source Teams
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Democratic Teams

A

Strengths
High-quality code
good with hard problems

Weakness
senior members may resent appraisals
cannot be externally imposed

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

Classical Chief Programmer Teams

A

Strength
Major success of The New York Times project

Weakness
Impractical

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

Modified Chief Programmer Teams

A

Strength
Many Successes

Weakness
No successes on a large scale

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

Modern Hierarchical Programming Teams

A

Team Manager structure eliminates the need for a chief programmer
scales up
supports decentralization when needed

Weakness
Problems can arise unless areas of responsibility of the team manager and the team leader are clearly delineated

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

Synchronize-and-stabilize teams

A

Strength
Encourages creativity
Ensures that a huge number of developers can work toward a common goal

Weakness
No evidence so far that this method can be utilized out side of microsoft

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

Agile Process Teams

A

Strengths
Programmers do not tes their own code
Knowledge is not lost if one programmer leaves
Less-experienced programmers can learn from others

Weakness
Still too little evidence regarding efficacy

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

Pair Programming Advantages and Disadvantages

A

Strengths
Team members benefit from each others experience
Programs have fewer bugs

Weaknesses
requires large blocks of uninterrupted time
does not work for shy or overbearing programmers

17
Q

Walkthrough vs Testing

A

Walkthrough takes less time and has few steps