Software Processes Flashcards Preview

COMP 3521: Software Engineering > Software Processes > Flashcards

Flashcards in Software Processes Deck (14)
Loading flashcards...
1

Specification

  • Defining what the system should do

2

Design and implementation

  • Defining the organization of the system and implementing the system

3

Validation

  • Checking that the system does what the customer wants

4

Evolution

  • Changing the system in response to changing customer needs

5

Stages of testing

  • Component/development testing
  • System/release testing
  • Customer/user testing

6

Software prototype

  • A prototype is an initial version of a system used to demonstrate concepts and try out design options.

7

Process metric

  • Used to measure the efficiency and effectiveness of various processes

8

Design activities

  • Architectural design
  • Database design
  • Interface design
  • Component selection and design

9

Reducing the costs of rework

  • Change anticipation
  • Change tolerance

10

Benefits of prototyping

  • Improved system usability
  • A closer match to users’ real needs
  • Improved design quality
  • Improved maintainability
  • Reduced development effort

11

Throw-away prototypes

  • It may be impossible to tune the system to meet non-functional requirements.
  • Prototypes are normally undocumented.
  • The prototype structure is usually degraded through rapid change.
  • The prototype probably will not meet normal organizational quality standards.

12

Incremental delivery

  • The development and delivery are broken down into increments, with each increment delivering part of the required functionality.
  • User requirements are prioritized, and the highest priority requirements are included in early increments.

13

Process improvement

  • Way to enhance quality of software
  • Process maturity approach
  • Agile approach

14

Process improvement activities

  • Measure
  • Analysis
  • Change