UML Design for an Automated Registration System Denist Oscar • Valendie Alix • Islande Belizaire • James Haralambides. PhD Abstract Architectural and Detailed Design Automated Registration System The design and implementation phases are key, since it is the stage in which an executable software system is actually developed. It is within this stage in which software components and their relationships are identified, all based on the customer’s needs and requirements. Designing a system involves the performance of several different types of activities such as architectural, interface, components and database design. This allows for complete understanding of the system’s principle components and finding additional requirements and functionalities that may be needed or wanted. The architectural designing of a system provides an abstract view of the overall blueprint of the structure of the system. UML diagramming on the other hand provides a much more detailed aspect of a system from different perspectives and in varying degrees of abstraction (can also be referred to as system modeling). It includes a set of graphic notation techniques to create visual models of object-oriented software-intensive systems. Descriptions of these different type of diagrams are shown below: Description of Diagrams: Use Case: This diagram displays the relationship among actors and use cases (specifically the relations that occur between the context and environment of a system). Class Diagram: This diagram models class structure and contents using design elements such as packages and objects. It also shows the relationships such as containment, inheritance, associations and many more. (Displays the organization of a system and structure of data). Interaction Diagram: This diagram contain two sub diagrams: Sequence Diagram: displays the time sequences of objects participating in the interaction (interaction between time and objects). Collaboration Diagram: displays an interaction organized around the objects and their links to one another. The Automated Registration System (A.R.S.) will supply a web-based registration system for its targeted users that are a part of the Barry University community. The main goals of this web interface is to: 1. adequately deliver accurate and up-to-date information in regards to classes, course schedules, and listings in the database, 2. provide a multi-agent based recommendation system that will make suggestions towards the user based on user personal profiles or actions and 3. an information listing providing the user access to their personal information (i.e. Health, finances, grades, enrollment status, etc). Some features of the A.R.S. system includes an adequate search engine (search index capability) which will allow users to quickly and efficiently search for classes and course schedules in the database and provide a suggestive setting which will provide users recommended classes to take, based on the previous classes the user has taken, as well as classes that they will have to take that has high priority. UML Diagramming and Automated Registration System UML Diagramming (Unified Modeling Language) is a design language that holds a huge amount of significance in the software development process of a given system. Unified Modeling Language (UML) is a standardized general-purpose modeling language in the field of object-oriented software engineering. Using UML diagramming is extremely key in the software development process because it allows for developers to be able to completely understand the overall design of a software from a variety of views or perspectives. By successfully utilizing this tool, developers are able to specify, envision and keep track of different types of models incorporated in a software system, including their overall structure and design. The Automated Registration system will act as an information system whose primary purpose is to manage to provide user access to the course registration database, all while maintaining user confidentiality, security, usability and data integrity. This system is designed to accept different types of data and information provided by the user to register for courses. This research project will contain abstract models of the A.R.S., with each model presenting a different view of several processes within this system. UML Diagramming of the Automated Registration System Activity Diagram of Course Registration Generalization Diagram Introduction What is Software Engineering? State Diagram: This diagram models the dynamic behavior of a system and its response to events. Software engineering is an engineering discipline that is concerned with the overall theories, methods, tools and production for professional software development. Through the use of key systematic and organized approaches in the production of software, engineers are able to produce high-quality software within specific organizational and financial constraints. The systematic approach in the production of software involves seven `processes that are fundamental in the sequence of activities that are enacted throughout the overall production of a software product. These seven processes are: Example of a Class Diagram Use Case Diagram Sequence Diagram of Student Search for classes 2. 1. Requirements: Involves the overall definition of the software and presents constraints on its operation. Contains a complete description of the behavior of the software system to be developed. Architecture: Abstract view of the overall blueprint of a software system. Design: Designing and programming process. Implementation: The reduction of the design of the system into code. Testing and Validation: The overall unit testing and checking of the software product to ensure that is meets customer needs. Deployment: The delivery or release of the software system to the customer. Support: Overall modification and on-going maintenance and enhancement of the software product. 3. Example of a Sequence Diagram 7. 4. 6. 5.