SOFTWARE ENGINEERING PRINCIPLES

Rigor

requires the use of mathematical techniques.

Formality

a higher form of rigor in which precise and unambiguous engineering approaches are use

Separation of Concerns

is an effective divide-and-conquer strategy practiced by software engineers to manage miscellaneous problems related to complexity

Modularity

commonly achieved by grouping together logically related elements, such as statements, procedures, variable declarations, and object attributes, in an increasingly fine-grained level of detail

high cohesion and low coupling

main goal of modularity

high cohesion

implies that each module represents a single part of the problem solution.

Coincidental

Logical

Temporal

Procedural

Communicational

Sequential

Functional

Seven levels of cohesion in the order of increasing strength

Coupling

relates to the relationships between the modules themselves.

None

Data

Stamp

Control

Common

Content

six levels in the order of increasing

strength

Anticipation of change

software products are subject to frequent change either to support new hardware or software requirements or to repair defects. A high maintainability level of the software product is one of the hallmarks of outstanding commercial software

Principle of Generality

can be stated as the intent to look for a more general problem that may be hidden behind it

Incrementality

involves a software-engineering approach in which progressively larger increments of the desired product are developed

Traceability

is concerned with the relationships between requirements, their

sources, and the system design

Design Activity

involved in identifying the components of the software design and their interfaces from the software requirements specification.

Mapping Matrix