Term
|
Definition
Qualities that the user sees and cares about.
ex. reliability and user friendliness |
|
|
Term
|
Definition
Qualities that concern the developer.
ex. verifiability and reliability |
|
|
Term
|
Definition
| The spec. and software are equivalent. |
|
|
Term
|
Definition
Reliable
The probability of failure is low.
Not buggy |
|
|
Term
|
Definition
How well the product handles exceptional conditions such as hard disk crashes or wrong input.
Deals with problems |
|
|
Term
|
Definition
| Efficiency in terms of time or space. |
|
|
Term
|
Definition
| Do people find it easy to use? |
|
|
Term
|
Definition
| Can the system's properties be verified. |
|
|
Term
|
Definition
| Can the new team of computer programmers maintain this software. |
|
|
Term
|
Definition
| Can we reuse the software in other projects? |
|
|
Term
|
Definition
| Can it be used in different operating systems and hardware platforms. |
|
|
Term
|
Definition
| Can a new team easily understand it and interact with the software components. |
|
|
Term
|
Definition
Can it work with other systems
ex. M$ Word taking a chart from Excel. |
|
|
Term
|
Definition
| Efficiency of the process |
|
|
Term
|
Definition
Can the product be delivered on time.
Scheduling, work estimations, milestones |
|
|
Term
|
Definition
| Are all steps documented clearly? |
|
|
Term
|
Definition
Rigor: Being thorough
Formality: Highest form of rigor |
|
|
Term
|
Definition
Separating the different aspects of a problem by:
Time, Qualities, Views, Parts |
|
|
Term
Modularity
Cohesion
Coupling |
|
Definition
Able to put into simpler pieces
Cohesion: All elements in a module are related strongly.
Coupling: How much a module depends on another. |
|
|
Term
|
Definition
| Ignoring details and looking at the important aspects of something. |
|
|
Term
|
Definition
Ability of software to evolve
Good reusability |
|
|
Term
|
Definition
| Solve the problem behind the apparent problem. Make code more reusable this way. |
|
|
