Chapter 2: SPE Overview Flashcards

1
Q

Why is SPE Necessary?

A

SPE can detect problems early in the system development cycle by using qualitative analysis

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

What is Fix-it-later approach

A

When bugs are encountered do not fix them right away wait until everything is finished to go back to fix it. Very little modelling and going direct into implementation.

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

Problems with fix-it-later approach?

A
  • Tuning software later does not have the benefits of fixing design issues
  • Can cost exponentially more in the future to fix bugs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the types of software development models?

A
  1. Waterfall method
  2. Iterative Model
  3. Spiral Model
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are systems with high performance requirements?

A
  1. End-user related functions (Reservation systems)
  2. Real-time, critical mission systems (rocketry, airplanes)
  3. Employee support systems (inventory system, CAD systems)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is Software Performance Engineering (SPE)?

A

SPE is a systematic, quantative analysis approach to constructing software systems that meet performance objectives.

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

What are the benefits of starting early in the lifecycle?

A
  1. Increased productivity - don’t throw away bad code
  2. Final design product is of improved quality
  3. Controlled costs of the supporting hardware and software
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is SPE for object-orientated systems?

A

SPE is tightly integrated with UML which is also often used in OOP analysis.

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

What are the stages of SPE process for object-orientated systems

A
  1. Assess Performance Risk
  2. Identify Critical Use Cases
  3. Select Key Performance Scenarios
  4. Establish Performance Objectives
  5. Construct Performance Models
  6. Determine Software Resource Requirements
  7. Add Computer Resource Requirements
  8. Evaluate the Models
  9. Verify and Validate the Models
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is the Simple-Model Strategy?

A
  • Start with the simplest model that identifies issues with the system architecture implementation plans.
  • Used in early stages.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is the Best- and Worse-case Strategy?

A

Use best- and worst-case estimates of resource requirements to establish bounds on expected performance and manage uncertainty in estimates.

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

What is the adapt-to-precision strategy?

A
  • Match the details represented in the models to your knowledge of the software processing details.
  • Used in later stages.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly