LESSON 2. Software process

Question 1

A structured set of activities required
to develop a software system.

Answer 1

Software Process

Question 2

Is an
abstract representation of a process.

Answer 2

Software Process Model

Question 3

It presents a description of a process from
some particular perspective.

Question 4

Defining what the system should do

Answer 4

Specification

Question 5

Defining the organization
of the system and implementing the system

Answer 5

Design and Implementation

Question 6

Checking that it does what the customer
wants

Answer 6

Validation

Question 7

Changing the system in response to changing
customer needs

Answer 7

Evolution

Question 8

Which are the outcomes of a process
activity

Answer 8

Products

Question 9

Which reflect the responsibilities of the people
involved in the process

Answer 9

Roles

Question 10

Which are statements
that are true before and after a process activity has
been enacted or a product produced.

Answer 10

Pre- and post condition

Question 11

Are processes where
all of the process activities are planned in
advance and progress is measured against this
plan.

Answer 11

Plan-driven processes

Question 12

Planning is incremental
and it is easier to change the process to reflect
changing customer requirements.

Answer 12

Agile processes

Question 13

In practice, most practical processes include
elements
of
both
plan-driven and
agile
approaches.

Question 14

There are no right or wrong software processes.

Question 15

There are separate identified phases in the
waterfall model:

Answer 15

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 16

The main drawback of the waterfall model is the
difficulty of accommodating change after the
process is underway.
• In principle, a phase has to be complete before
moving onto the next phase.

Question 17

Inflexible partitioning of the project into distinct
stages makes it difficult to respond to changing
customer requirements.

Is what model problem?

Answer 17

Waterfall model

Question 18

Reuse-Oriented Software
Engineering

Process Stages

Answer 18

1. Component analysis
2. Requirements modification
3. System design with reuse
4. Development and integration

Question 19

One of benefits:

Reusing existing
software components reduces development time
and costs associated with designing,
implementing, and testing new functionality
from scratch.

Answer 19

Time and Cost Savings

Question 20

One of benefits

Reused components have
often been tested and used in multiple contexts,
making them more reliable and less prone to
errors.

Answer 20

Improved Quality

Question 21

Benefits:

Reusing
standardized components promotes consistency
across projects, leading to better maintainability
and easier integration.

Answer 21

Consistency and Standardization:

Question 22

One of benefits:

By leveraging
reusable components and frameworks,
developers can focus more on solving domain-
specific problems rather than reinventing
common functionalities.

Answer 22

Focus on Core Competencies

Question 23

One of problems

Reused components may not
always be compatible with the specific requirements,
platforms, or environments of a new project. Integration
problems can arise due to differences in APIs, data
formats, or dependencies.

Answer 23

Compatibility Issues

Question 24

Problem:

Not all reusable components
are of high quality or well-documented. Using poorly
designed or outdated components can introduce bugs,
security vulnerabilities, or performance issues into the
new system.

Answer 24

Quality and Reliability:

Question 25

One of problems:

Reused components require
ongoing maintenance and support to keep them up-to-
date, compatible with evolving technologies, and
compliant with changing requirements. Neglecting
maintenance can lead to dependency on obsolete or
unsupported components.

Answer 25

Maintenance Burden

Question 26

One of problem:

Reused components may not
perfectly fit the specific needs of a new project, leading
to compromises in functionality or performance.

Answer 26

Lack of Customization

Question 27

One of problems:

Software reuse can
introduce complex dependency relationships between
components, making it challenging to manage
versioning, upgrades, and compatibility across different
projects or modules.

Answer 27

Dependency Management

Question 28

third-
party components or libraries may involve legal
considerations related to intellectual property rights,
licensing agreements, and compliance with open-source
licenses. Failure to properly manage licensing issues can
lead to legal disputes or violations.

Answer 28

Intellectual Property and Licensing

Question 29

One of problem

Reused
components should be well-documented to facilitate
understanding, integration, and customization by other
team members. Inadequate documentation can hinder
knowledge transfer and make it difficult to troubleshoot
or extend reused components.

Answer 29

Documentation and Knowledge Transfer

Question 30

One of problem:

It can lead to a “one-size-fits-all” approach, where
developers prioritize reuse over designing optimal
solutions for specific project requirements. This can
result in overly complex or inefficient systems that are
difficult to maintain or extend.

Answer 30

Over-reliance on Reuse: