Chapter 2 Flashcards

1
Q

Define

Work Product

A

The programs, documents, and data produced by engineering activities and tasks included in the process.

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

Define

Software Engineering

A

The establishment and use of sound engineering principles in order to obtain economically software that is reliable and works efficiently on real machines.

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

List

Different Process Flow Organizations

A

Linear
Iterative
Evolutionary
Parallel

Each one contains actions that can happen and the order they can happen in.

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

List

Umbrella Activities

Within the Task Framework

A

Software project tracking and control
Risk management
Software quality assurance
Technical reviews
Measurement
Software configuration management
Reusability management
Work product prep and production

Within the Task Framework

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

List

Components of Polya essense of practice

Overview, not just for software

A

Understand the Problem
Plan the Solution
Carry Out the Plan
Examine the Result

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

List

Questions to ask to Understand the Problem

Ask yourself these.

A

Who has stake in the solution?
What are the unknowns?
Can the problem be compartmentalized?
Can it be represented graphically?

Questions to ask to Understand the Problem

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

List

Questions to Plan the Solution

Ask yourself these.

A

Have you seen similar problems before?
Have similar problems been solved?
Can subproblems be defined?
Can you represent a solution in a manner that leads to effective implementation?

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

List

Questions to Carry out the Plan

Ask yourself these.

A

Does the solution conform to the plan?
Is each component provably correct?

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

List

Questions to Examine the Result

Ask yourself these.

A

Is it possible to test each component part of the solution?
Has the software been validated against all stakeholder requests?

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

Define

Elicitation

A

An action associated with the communication activity

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

Define

Task Set

A

Defines the actual work that needs to be done to accomplish the objectives of a software engineering action.

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

Define

Prescriptive Process Models

A

Define a predefined set of process elements and a predictable process workflow. Strive for structure and order in software development.

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

Define

Unified Process Model

A

Suggests a process flow that is iterative and incremental, providing the evolutionary feel that is essential in modern software development.

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

Define

Unified Modeling Language

A

Developed to support UP. Contains a robust notation for the modeling and development of object-oriented systems and has become industry standard for modeling software of all types.

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

Define

Inception phase of UP

A

Where customer communication and planning takes place.

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

Define

Elaboration phase of UP

A

Encompasses planning and modeling of generic process model. Creates architectural baseline that includes use case model, analysis model, design model, implementation model, and deployment model.

17
Q

Define

Construction phase of UP

A

identical to construction phase of generic process model. Unit tests are designed and implemented for each component, integration activities are conducted, and suite of acceptance tests derived.

18
Q

Define

Transition phase of UP

A

Encompasses later stages of generic construction and first part of generic deployment (delivery and feedback). Beta testing stage.

19
Q

Define

Production phase of UP

A

Coincides with deployment activity in generic process. Usage monitored, support provided, defect reports and requests for change submitted and evaluated.

20
Q

List

Five phases of Unified Process Model

A

Inception
Elaboration
Construction
Transition
Production

21
Q

List

Some task sets inside of Umbrella activities

A

Work tasks
Work Products
Quality assurance points
Project milestones

22
Q

The lists to create when you first define a task set

A

List of tasks to be accomplished
List of works to be produced
List of quality assurance filters to be applied

23
Q

List

Pros of Waterfall Model

A

Easy to Understand and Plan
Works for well-understood small projects
Analysis and Testing are straightforward

24
Q

List

Cons of Waterfall Method

A

Does not accomodate change well
Testing occurs late in the process
Customer approval at end
Prof recommends not using it

25
Q

List

Pros of Prototyping Model

A

Reduced impact of required changes
Customer involved early and often
Works well for small projects
Reduced likelihood of product rejection

26
Q

List

Cons of Prototyping Model

A

Customer involvement may cause delays
Temptation to ship a prototype
Hard to plan and manage
Might make quick decisions that get stuck

Need to make rules clear with stakeholders at beginning.

27
Q

ListDefine

Pros of Spiral Process Model

A

Continuous customer involvment
Development risks are managed
Suitable for large, complex projects
Works well for extensible projects

28
Q

List

Cons of Spiral Process

A

Risk analysis failures can doom the project
May be hard to manage
Requires an expert development team

29
Q

List

Pros of Unified Process Model

A

Utilizes best of Agile
Quality documentation emphasized
Accepts requirement changes

Works well for maintenance projects

30
Q

List

Cons of UP model

A

Use cases not always precise
Tricky software increment integration
Overlapping phases can cause problems
Requires expert development team