Software Requirements And Design

Front 1

What is the purpose of software design?

Back 1

To enable programmers to implement the requirements by designating the projected parts of the implementation.

Front 2

What are the goals of software design?

Back 2

Sufficiency, Understandability, Modularity, Cohesion, Coupling, Robustness, Flexibility, Reusability, Information hiding, Efficiency, Reliability

Front 3

What makes a design sufficient?

Back 3

It provides the components for an implementation that satisfies the requirements.

Front 4

What makes a design flexible?

Back 4

Designs must be able to anticipate changes in the requirements.

Front 5

What is design modularity?

Back 5

Being divided into separately named and addressable components.

Front 6

What makes software robust?

Back 6

Being able to deal with a wide variety of input.

Front 7

What is software efficiency?

Back 7

It must execute within acceptable time and space requirements.

Front 8

What is cohesion?

Back 8

It is organized so like minded elements are grouped together.

Front 9

What is coupling?

Back 9

Organized to minimize dependence between elements.

Front 10

How is inheritance indicated and how is it implemented?

Back 10

With an open triangle and solid line.

class MyClass extends MyOtherClass{...}

Front 11

How are abstract classes denoted?

Back 11

With italics.

Front 12

What is realization and how is it denoted?

Back 12

It is denoted by an open triangle and dotted line.

class MyClass implements MyInterface {...}

Front 13

What is aggregation and how is it denoted?

Back 13

Indicates the structural inclusion of objects of one class by another. The "has-a" relationship. Denoted by an open diamond with a solid line arrow.

class Company{employee emp;}

Front 14

What is composition and how is it denoted?

Back 14

The aggregated object exists only during the lifetime of the composing object. It is denoted by a closed diamond on a solid line arrow.

class Company
{
class Employee emp;{...}
}

Front 15

What is dependency and how is it denoted?

Back 15

If the class at arrow's end were to change, the dependent class would change as well. Denoted by a dotted arrow.

class MyClass
{
void myFunc(RefClass ref);
}

Front 16

What is the purpose and goal of formal methods in requirements?

Back 16

Formal methods are built on mathematical axioms and can be proven with mathematical correctness.