Presentation is loading. Please wait.

Presentation is loading. Please wait.

Tim St. John Masters Computer Engineering Software Engineering Track.

Similar presentations


Presentation on theme: "Tim St. John Masters Computer Engineering Software Engineering Track."— Presentation transcript:

1

2 Tim St. John Masters Computer Engineering Software Engineering Track

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

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

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

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

7 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.

8 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.

9 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.

10 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.

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

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

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

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

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


Download ppt "Tim St. John Masters Computer Engineering Software Engineering Track."

Similar presentations


Ads by Google