ii - software processes

Question 1

coherent set of activities for software production

Answer 1

software process

Question 2

process descriptions may also include…

Answer 2

1. products
2. roles
3. pre- and post-conditions

Question 3

[1] discuss, each approach is suitable for different types of software

Answer 3

Boehm and Turner (2003)

Question 4

what are the process models covered?

Answer 4

1. waterfall model
2. incremental development
3. reuse-oriented software engineering

Question 5

fundamental process activities of specification,
development, validation, and evolution and represents them as separate process phases such as requirements specification, software design, implementation, testing, and so on.

Answer 5

waterfall model

Question 6

interleaves the activities of specification,
development, and validation. The system is developed as a series of versions (increments), with each version adding functionality to the previous version.

Answer 6

incremental development

Question 7

This approach is based on the existence of a significant number of reusable components. The system development process focuses on integrating these components into a system rather than developing
them from scratch.

Answer 7

Reuse-oriented software engineering

Question 8

The [1] model is an example of a plan-driven process—in principle, you must plan and schedule all of the process activities before starting work on them.

Answer 8

waterfall

Question 9

enumerate

principal stages of waterfall model

Answer 9

1. requirements analysis and definition
2. system and software design
3. implementation and unit testing
4. integration and system testing
5. operation and maintenance

Question 10

An example of a formal development process, originally developed by IBM; each software increment is formally specified and this specification is transformed into an
implementation

Answer 10

Cleanroom process

Question 11

Description: A sequential software development model that follows distinct phases, producing documentation at each stage.
Key Feature: Consistency with engineering process models, visibility for managers to monitor progress, but inflexible partitioning of the project.

Answer 11

waterfall model

Question 12

Description: Major problem lies in the inflexible partitioning of the project into distinct stages.

Key Challenge: Commitments made early in the process, difficulty in responding to changing customer requirements.

Use Case: Suitable when requirements are well understood and unlikely to change radically during system development.

Answer 12

Waterfall Model Challenges

Question 13

Description: A variant of the waterfall model involving creating a mathematical model of a system specification, refined into executable code using mathematical transformations.

Use Case: Particularly suited for systems with stringent safety, reliability, or security requirements.

Advantage: Simplifies the production of a safety or security case, demonstrating compliance with requirements to customers or regulators.

Answer 13

Formal System Development

Question 14

Description: Typically applied to the development of safety-critical or security-critical systems, requiring specialized expertise.

Consideration: Not generally cost-effective for the majority of systems, but beneficial for projects with stringent safety or security requirements.

Examples: B method (Schneider, 2001; Wordsworth, 1996).

Answer 14

Processes Based on Formal Transformations

Question 15

based on the idea of developing an initial implementation, exposing this to user comment and evolving it through several versions until an adequate system has been developed

Answer 15

incremental development

Question 16

From a management perspective, the incremental approach has two problems

Answer 16

1. process is not visible
2. system structure tends to degrade as new increments are added

Question 17

stages in reuse-oriented process

Answer 17

1. component analysis
2. requirements modification
3. system design with reuse
4. development and integration

Question 18

3 types of software component in reuse-oriented process

Answer 18

1. web services
2. collections of objects developed as package
3. stand-alone software systems

Question 19

Specifications are written on cards.
Executable tests are developed before the actual program.
Evolution may involve substantial system restructuring or refactoring.

Answer 19

extreme programming

Question 20

particularly critical stage of the software process as errors at this stage inevitably lead to later problems in the system design and implementation.

Answer 20

Requirements engineering

Question 21

programs that are used to support software engineering process activities. These tools therefore include design
editors, data dictionaries, compilers, debuggers, system building tools, etc.

Answer 21

Software development tools (sometimes called Computer-Aided Software Engineering or CASE tools)

Question 22

4 main activities in requirements engineering process

Answer 22

1. feasibility study
2. requirements elicitation and analysis
3. requirements specification
4. requierments validation

Question 23

description of the structure of the software to be implemented, the data models and structures used by the system, the interfaces between system components
and, sometimes, the algorithms used.

Answer 23

software design

Question 24

4 activities part of design process for information systems

Answer 24

1. architectural design
2. interface design
3. component design
4. database design

Question 25

• Evolution of structured methods.
• Emphasizes architectural models with abstract and implementation-specific levels.
• Detailed models enable executable system generation.

Answer 25

Model-Driven Development (MDD)

Question 26

• Follows naturally from system design.
• Interleaved stages of design and program development are common.
• Software development tools may generate a skeleton program, allowing developers to focus on component details.

Answer 26

program development

Question 27

system is executed using simulated test data, is the principal validation technique

Answer 27

Program testing

Question 28

stages in testing process

Answer 28

1. development testing
2. system testing
3. acceptance testing

Question 29

acceptance testing is also called [1] where custom systems are developed for a single client and the testing process continues until both agree that the system is acceptable.

Answer 29

alpha testing

Question 30

system is marketed as a software product so [1] testing is used; delivering a system to a number of potential customers who agree to use that system

Answer 30

beta testing

Question 31

2 approaches to reduce costs of rework

Answer 31

1. change avoidance
2. change tolerance

Question 32

2 ways of coping with change and changing system requirements

Answer 32

1. system prototyping
2. incremental delivery

Question 33

initial version of a software system that is used to demonstrate concepts, try out design options, and find out more about the problem and its possible
solutions

Answer 33

prototype

Question 34

A risk-driven software process framework (the spiral model) was proposed by [1]

Answer 34

Boehm (1988)

Question 35

each loop in the spiral is split into 4 sectors…

Answer 35

1. objective setting
2. risk assessment and reduction
3. development and validation
4. planning

Question 36

modern generic process model that is organized into phases (inception, elaboration, construction, and transition) but separates activities (requirements,
analysis, and design, etc.) from these phases.

Answer 36

The Rational Unified Process

Question 37

3 perspective of RUP

Answer 37

1. dynamic perspective
2. static perspective
3. practice perspective

Question 38

shows the phases of the model over time.

Answer 38

dynamic perspective

Question 39

shows the process activities that are enacted.

Answer 39

static perspective

Question 40

good practices to be used during the process.

Answer 40

practice perspective

Question 41

phases of RUP

Answer 41

1. inception
2. elaboration
3. construction
4. transition

Question 42

6 fundamental best practices recommended in RUP

Answer 42

1. develop software iteratively
2. manage requirements
3. use component-based architectures
4. visually model software
5. verify software quality
6. control changes to software

Question 43

standardized modeling language in the field of software engineering that uses graphical notations to create visual models of software systems; help in understanding, visualizing, specifying, constructing, and documenting the artifacts of a software system.

Answer 43

Unified Modeling Language (UML)