3.1 Integration Build One

3.2 Integration Build Two

1. Introduction
1. Purpose

   This document describes the plan for integrating the first software components of the C-Registration system into an executable and demonstrable prototype.

2. Scope

The Integration Build applies to the C-Registration prototype and reflects the feature content planned for Release 1 of the C-Registration System, as defined in the E1 Iteration Plan [14]. The resulting architectural prototype will bring together the key architectural components required for Release 1.0.

This document will help form the plans for the prototype integration and will be used as input into the Test Plan [16] for the prototype.

3. Definitions, Acronyms and Abbreviations

See Glossary [4].

4. References

Applicable references are:

1. Course Billing Interface Specification, WC93332, 1985, Wylie College Press.
2. Course Catalog Database Specification, WC93422, 1985, Wylie College Press.
3. Course Registration System Vision Document, WyIT387, V1.0, 1998, Wylie College IT.
4. Course Registration System Glossary, WyIT406, V2.0, 1999, Wylie College IT.
5. Course Registration System Use Case Spec - Close Registration, WyIT403, V2.0, 1999, Wylie College IT.
6. Course Registration System Use Case Spec - Login, WyIT401, V2.0, 1999, Wylie College IT.
7. Course Registration System Use Case Spec - Maintain Professor Info, WyIT407, Version 2.0, 1999, Wylie College IT.
8. Course Registration System Use Case Spec - Register for Courses, WyIT402, Version 2.0, 1999, Wylie College IT.
9. Course Registration System Use Case Spec - Select Courses to Teach, WyIT405, Version 2.0, 1999, Wylie College IT.
10. Course Registration System Use Case Spec - Maintain Student Info, WyIT408, Version 2.0, 1999, Wylie College IT.
11. Course Registration System Use Case Spec - Submit Grades, WyIT409, Version 2.0, 1999, Wylie College IT.
12. Course Registration System Use Case Spec - View Report Card, WyIT410, Version 2.0, 1999, Wylie College IT.
13. Course Registration System Software Development Plan, WyIT418, V1.0, 1999, Wylie College IT.
14. Course Registration System Iteration Plan, Elaboration Iteration #E1, WyIT420, V1.0, 1999, Wylie College IT.
15. Course Registration System Software Architecture Document, WyIT431, V1.0, 1999, Wylie College IT.
16. Course Registration System Test Plan for the Architectural Prototype, WyIT432, V1.0, 1999, Wylie College IT.

2. Subsystems

The elaboration phase will develop the architectural prototype to verify the feasibility and performance of the architecture for Release 1.0. This will include implementing the interfaces to the external subsystems; Finance System and Course Catalog as well as implementing the course registration subsystem.

The main processes which interface with the student and which process the student's registration request will be implemented. Security features, such as the student Logon will be implemented. The Close Registration process will be implemented to initiate the communication with the external Finance System.

Only selected components of the identified subsystems (and processes) will be implemented in the architectural prototype. The intent is to implement the interface and communication mechanisms.

The following table illustrates the subsystems and processes to be implemented for the architectural prototype:

Subsystem	Processes	Components
Course Registration	StudentApplication CourseRegistrationProcess CourseCatalogSystemAccess FinanceSystemAccess CloseRegistrationProcess	TBD
Finance System	FinanceSystem	TBD
Course Catalog	CourseCatalog	TBD

 

3. Builds

The integration (in the iteration) is divided into a number of increments, each resulting in a build, which is integration-tested. The integration of the prototype will be organized as 2 integration builds as described in the following sections.

Build integration includes the following steps:

• Assembling the specified components into the build directories,
• Creating the compile and link command files,
• Compiling & linking the components into executables,
• Initializing the database,
• Transferring the executables, data, and test drivers to the target machines, and
• Running integration tests.

3.1    Integration Build One

The first integration build will enable the following basic functionality:

Integration Build One includes the following Subsystems and Components:

            3.2    Integration Build Two

The second integration build will enable the following basic functionality:

Integration Build Two includes the following Subsystems and Components: