1. Intro

Question 1

Types of Software

Answer 1

▪ System software
▪ Application software
▪ Distributed systems
▪ Embedded systems
▪ Product-line software
▪ Games
▪ Artificial intelligence systems

Question 2

Successful software will be used and built on for a long time (possibly decades).

Meaning:

Answer 2

➢Software should be built to be adaptable and extensible (maintenance).

Question 3

A software process model defines

Answer 3

how the various software engineering
activities are structured in time

how they depend on each other through
the creation and consumption of artifacts

Question 4

A sequential model (i.e. an extreme version of the “waterfall”) attempts to

Answer 4

identify all or most requirements at the start of the project

create a thorough design as a “blueprint” of the complete system before programming starts

defines a complete project schedule at the beginning of the project

Question 5

What is the problem with the sequential model?

Answer 5

It assumes that nothing will change over the course of the project, it is unrealistic

Question 6

Iterative-Incremental Process Models

Answer 6

Split the project into iterations where each iteration is a mini-project

Has many benefits, like :
Better productivity,
early visible progress,
early user engagement, etc.

Question 6

Iterative-Incremental Process Models

Answer 6

Split the project into iterations where each iteration is a mini-project

Has many benefits, like :
Better productivity,
early visible progress,
early user engagement, etc.

Question 7

Plan-driven Iterative Development

Answer 7

Aspiration for stable structures
Risk management through planning
Defined roles and responsibilities

Question 8

Agile Iterative Development

Answer 8

Acceptance of fluid structures
Gain understanding through
communication and feedback
Risk management through flexibility

Question 9

The Unified Process (UP) was devoloped by?

Answer 9

Ivar Jacobson, Grady Booch and James Rumbaugh in parallel with the Unified Modeling Language (UML); first published in 1999

Question 10

The Unified Process (UP) does ?

Answer 10

Defines a number of roles, workflows, activities and artifacts

Question 11

The UP defines four phases called ?

Answer 11

inception,
elaboration,
construction,
transition

IECT

Question 12

Each phase consists of :

Answer 12

several iterations.

Question 13

Each iteration :

Answer 13

produces an increment.

Question 14

What is included in the Inception phase?

Answer 14

Approximate vision

Business case

Scope

Vague estimates

Question 15

What is included in the Elaboration phase?

Answer 15

Refined vision

Identification of most
requirements and scope

More realistic estimates

Iterative implementation
of core architecture

Resolution of high risks

Question 16

What is included in the Construction phase?

Answer 16

Iterative implementation of lower-risk and
other elements

Preparation for deployment

Question 17

What is included in the Transition phase?

Answer 17

Beta tests

Deployment

Question 18

Time and Effort Distribution in the Unified Process Phases

Answer 18

Inception and Transition typically take
up to 10% each of time and effort

Elaboration typically takes at most
one third of time and effort

Construction typically takes at least
half of time and effort

Question 19

Milestones in the Unified Process Phases

Answer 19

Activities within phases overlap

However, phases are separated by
milestones to judge project feasibility
and progress

Milestones have defined deliverables
and evaluation criteria

Question 20

Inception: Primary Objectives

Answer 20

Establish the project’s software scope and boundary conditions

Identify the critical use cases of the system

Identify (and maybe demonstrate) at least one candidate architecture

Estimate the overall cost and schedule for the entire project

Estimate potential risks (i.e. sources of unpredictability / uncertainty)

Prepare the supporting environment for the project

Question 21

Elaboration: Primary Objectives

Answer 21

Establish baseline architecture addressing the architecturally significant scenarios

Address all architecturally significant risks of the project

Produce an executable architecture and possibly exploratory, throw-away prototypes

Demonstrate that the baseline architecture will support the requirements of the system

Establish the supporting environment for the project

Question 22

During Inception and Elaboration, the project still is

Answer 22

a relatively light-and-fast, low-risk operation.

Question 23

During Construction and Transition, the project becomes

Answer 23

a high-cost, high-risk operation with substantial organizational inertia.

Question 24

Construction: Primary Objectives

Answer 24

Analyze, design, develop and test all required functionality.

Question 25

Transition: Primary Objectives

Answer 25

Beta-testing

Tuning activities such as bug-fixing, enhancement for performance and usability

Executing deployment plans

Question 26

Key Practices of the Unified Process

Answer 26

Build a cohesive core architecture in early iterations

Apply use cases where appropriate

Model visually with the UML