Tim St. John
Masters Computer Engineering
Software Engineering Track

Software Construction:
Implementation and
Testing the Design
By Mark Christensen
Presented by
Timothy St. John

Software Construction
Fundamentals
1.
Minimizing Complexity.
2.
Anticipating Change.
3.
Constructing for Verification.
4.
Standards in Construction.

Practical Considerations

Construction languages.

Coding.

Construction Testing.

Reuse.

Construction Quality.

Construction model.

Integration.

Current Construction practices

Classical Information System.

Embedded System.

Desktop and local Network Applications.

Internet and Wireless Applications.

Development Environments and
Tool-sets

The Available development and execution environment.
 Support for the Project’s development process.

Resource utilization.

Security.

Access to future capabilities.

Understanding the Scope of the
Construction effort

The requirements that the product must satisfy.

Other requirements that the project must satisfy.

The approach to integrate and deployment.

Contents of the Construction
Plan

A detailed schedule.

A description of methods and procedures.

A staffing and labor expenditure plan.

A list of required resources.

Creating and Using the
Schedule Network

The time span.

Identification of any external conditions or constraints.

The dates by which the individual components are needed.

Cohesion

Coincidental cohesion.

Logical cohesion.

Procedural cohesion.

Temporal cohesion.

Communicational cohesion.

Sequential cohesion.

Functional cohesion.

Coupling

Pathological coupling.

Global-data coupling.

Control coupling.

Data-structure coupling.

Simple-data coupling.

Naming Components

Representative of that routine.

Conflict resolution.

Is reasonably short?

Does it make sense?

Ask someone.


Top down.

Bottom Up.

Flow.
Integration

Any Questions?
Tim St. John tdstjohn@gmail.com