Rational software architecture document template

Use-Case View 4. Logical View 5. Process View 6. Deployment View 7. This document provides a comprehensive architectural overview of the system, using a number of different architectural views to depict different aspects of the system.

It is intended to capture and convey the significant architectural decisions which have been made on the system. This document presents the architecture as a series of views; use case view, logical view, process view and deployment view.

There is no separate implementation view described in this document. There are some key requirements and system constraints that have a significant bearing on the architecture. They are:. A description of the use-case view of the software architecture. These use cases are initiated by the student, professor, or the registrar actors.

In addition, interaction with external actors; Course Catalog and Billing System occur. Brief Description:This use case allows a Registrar to close the registration process.

Course offerings that do not have enough students are cancelled. Course offerings must have a minimum of three students in them. The billing system is notified for each student in each course offering that is not cancelled, so the student can be billed for the course offering. The main actor of this use case is the Registrar. The Billing System is an actor involved within this use case. The actors starting this use case are Student, Professor, and Registrar.

Brief Description:This use case allows the registrar to maintain professor information in the registration system. This includes adding, modifying, and deleting professors from the system. The actor of this use case is the Registrar. The actor starting this use case is the Professor. The Course Catalog System is an actor within the use case. Brief Description:This use case allows a student to register for courses in the current semester.

The Billing System is notified of all registration updates. The Course Catalog provides a list of all the course offerings for the current semester. The main actor of this use case is the student.

The student is the actor of this use case. Brief Description:This use case allows a professor to submit student grades for one or more classes completed in the previous semester. The actor in this use case is the Professor. Brief Description:This use case allows the registrar to maintain student information in the registration system.

This includes adding, modifying, and deleting students from the system. The actor for this use case is the Registrar. A description of the logical view of the architecture. Describes the most important classes, their organization in service packages and subsystems, and the organization of these subsystems into layers. Also describes the most important use-case realizations, for example, the dynamic aspects of the architecture.

Class diagrams may be included to illustrate the relationships between architecturally significant classes, subsystems, packages and layers. The logical view of the course registration system is comprised of the 3 main packages: User Interface, Business Services, and Business Objects.

The User Interface Package contains classes for each of the forms that the actors use to communicate with the System. Boundary classes exist to support login, maintaining of schedules, maintaining of professor info, selecting courses, submitting grades, maintaining student info, closing registration, and viewing report cards.

The Business Services Package contains control classes for interfacing with the billing system, controlling student registration, and managing the student evaluation.

The Business Objects Package includes entity classes for the university artifacts i. This application layer has all the boundary classes that represent the application screens that the user sees. This layer depends upon the Process Objects layer; that straddles the separation of the client from mid-tier. The Business Services process layer has all the controller classes that represent the use case managers that drive the application behavior.

This layer represents the client-to-mid-tier border. The Business Services layer depends upon the Process Objects layer; that straddles the separation of the client from mid-tier. Will co ntain the Deployment Mod el. Software Architecture Document 5 pages. Software Architecture Document 6 pages. Software Architecture Document 9 pages. Software Architecture Document Template 13 pages.

Software Design Document Word Template 6 pages. Software Design Document Sample 22 pages. Software Design Document Template 34 pages. Software Design Document 24 pages. Software Design Document 17 pages. Software Design Document 11 pages. System Design Document Template 10 pages. System Design Document Template 8 pages.