CIS 788.12I:
Software Component Engineering

Description

Component-based software from client's, implementer's, and designer's perspectives; container components; data representation; reasoning about the behavior of component-based software.

Level and Credits

• UG 3 (three one-hour lectures)

Prerequisites

• Graduate standing in CIS, or permission of the instructor

Quarters Offered

• TBD

General Information, Exclusions, etc.

• Not open to students who have taken CIS 321 at OSU when it was taught using C++.
• C++ is used.

Objectives

• Master using C++ class templates and classes, and related RESOLVE/C++ principles for clients, to write layered implementations of operations;
• Master using simple techniques to test layered implementations of operations, including developing and carrying out simple specification-based test plans;
• Master using simple techniques to debug layered implementations of operations;
• Be familiar with using the Array, Binary_Tree, List, Partial Map, Queue, Record, Sequence, Set, and Stack templates to write layered implementations of operations;
• Be familiar with using basic C++ control structures and statements, RESOLVE/C++ class templates and classes, and related RESOLVE/C++ principles for clients and implementers, to write bodies of component realizations with layered data representations;
• Be familiar with reading code that uses dynamic storage management (new and delete) and pointers to create simple "raw C++" data representations;
• Be familiar with using loop invariants to reason about loop behavior
• Be familiar with using basic algorithm analysis techniques and notations to analyze and express execution time of operations whose implementations involve straight-line code and simple loops;
• Be familiar with using simple formal logic assertions involving mathematical set models to understand and reason about an operation's behavior;
• Be familiar with using simple techniques to test implementations of class templates that define new types, including developing and carrying out simple specification-based test plans;
• Be familiar with using simple techniques to debug implementations of class templates that define new types;
• Be exposed to using data representation conventions ("representation invariants") and correspondences ("abstraction relations") to reason about correctness of data representations;
• Be exposed to writing programs using dynamic storage management and pointers to create simple "raw C++" data representations;
• Be exposed to writing simple formal logic assertions involving mathematical set models to describe an operation's behavior;
• Be exposed to using the RESOLVE/C++ principles for interface designers to guide the choice of mathematical model and operation behavior of a new software component.

Texts

• Weide, B.W., Software Component Engineering, OSU Reprographics, 1998.

Topics

Representative Lab Assignments

Grading Plan

Important Note: A passing grade on the final exam is required in order to receive a passing grade for the course.