However, they are very closely related.
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. Architecturally Significant Use-Cases 4.
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. This use case describes how a user logs into the Course Registration System. The actors starting this use case are Student, Professor, and Registrar.
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. 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.
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.
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. Logical View 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:Modern Web Design Requirements Gathering The requirements gathering phase of a web design project is critical to the success of any web based project.
The importance of this document grows as the complexity of a site increases. Sample Website Brief 8 8. Design Please provide a short brief on the design direction of the site.
This will help us estimate photography and illustration needs for the site. In terms of the design, we like the following visual references: Microsoft Word - EDIT_Sample Website Brief Author: ichizu Created Date. A design document is a complete high-level solution to the problem presented.
It should be detailed enough that somebody who already understands the problem could go out and code the project without having to make any significant decisions. “Writing effective design documentation (like design itself) is really all about making sure you serve the needs of your audience.” If you are a designer or product planner, you probably create documents of some kind to capture your design decisions and solutions.
Create beautiful designs with your team. Use Canva's drag-and-drop feature and layouts to design, share and print business cards, logos, presentations and more. While we worked to complete the Design Document, Hemingway's copywriter and marketing team worked to collect and refine their final content (text, photography, downloads) so that upon the site's final design approval, we could quickly move forward into the coding stage of the project.