CSIS 100 Week 7 Lab 5 UML Modeling Background

Csis 100csis 100 Week 7 Lab 5 Uml Modelingbackgroundthe Unified

CSIS 100 CSIS 100 – Week 7 Lab 5: UML Modeling Background: “The Unified Modeling Language, or UML, as it is popularly known by its TLA (three-letter acronym!), is the language that can be used to model systems and make them readable. This essentially means that UML provides the ability to capture the characteristics of a system by using notations. UML provides a wide array of simple, easy to understand notations for documenting systems based on the object-oriented design principles. These notations are called the nine diagrams of UML.” In this exercise, you will be developing the first of the UML diagrams, known as a Use-Case diagram. Before beginning this lab, be sure to read the articles and watch the videos that are in your Reading & Study folder.

In this lab, you are a Systems Analyst working for Liberty University. It is your responsibility to produce a Use Case diagram (complete with Use Case descriptions for each Use Case) for a system that will model an existing system. The system that you choose to model is your decision. Some examples are the systems that you use to apply for admission to the university, the system you use to sign up for classes, the system you use to order textbooks, or another system of which you are familiar. To construct your Use Case diagram, you will use a web-based modeling tool that is found at .

The instructions to use this tool are as follows: 1. Open a web browser and navigate to . You will immediately see a screen like the one below that asks you where you want to save your files. Select “Device” from this screen. 2. The next screen prompts you to either Create a new diagram or Open an existing diagram. Click “Create new diagram”. 3. This opens a new screen. Just click on the “Blank Diagram” and create a blank diagram. This opens your template screen to start diagramming. 4. Click on the down arrow head to the left of the word “General” to collapse the General symbols. 5. Then click on the arrow head next to “UML” to open the UML symbols. 6. Drag in as many Actors and Use case symbols as you need for your Use Case Diagram. 7. When you are ready click on the File-Save As button. The next screen prompts you to give your diagram a name and to select a template for your diagram. a. Name your file using the convention [Your First and Last Name without spaces] followed by “UseCaseDiagram”. b. Once you have named the file, click on the Device icon and it will open your file save as menu.

Tasks : 1. In a three paragraph summary, describe the system you are modeling. Save this summary in a Word document entitled [Your first name + your last name] + “_Lab 6”. 2. Create a Use-Case diagram with a minimum of 3 actors and 5 use cases. 3. Include 1 “extends” relationship in your model. 4. In the same Word document as your system summary, create use case descriptions for each of the use cases you identified. The format of your use case descriptions should be as follows: Use Case Name: Participating Actors: Flow of Events: Alternative Flows: Entry Conditions: Exit Conditions: [For a discussion and example of use case descriptions, be sure to view the articles and videos in your Reading & Study folder.]

Deliverables : Upload your diagram (saved as an xml file) and your Word document containing your summary and use case descriptions to the assignment link in Blackboard by the date specified in your course schedule.

Sample Paper For Above instruction

The system I am modeling is an online course registration system developed for a university. This system enables students to browse available courses, register for classes, and manage their schedules online. It also allows administrators to add, modify, or remove courses from the catalog, oversee student enrollments, and generate reports on registration statistics. The system aims to streamline the registration process, reduce manual paperwork, and improve overall efficiency in managing academic offerings.

The primary actors involved in this system include students, where users select courses and view their schedules; administrative staff, responsible for managing courses and student records; and system administrators, who handle user management and system maintenance. The system facilitates various use cases such as course browsing, registration, deregistration, schedule viewing, and administrative updates. Each actor interacts with the system in specific ways to accomplish these tasks, ensuring a smooth and effective registration process that accommodates both student needs and administrative oversight.

The use case diagram illustrates the interactions between these actors and the system. For example, the "Register for Course" use case extends the "View Schedule" use case, allowing students to add courses to their schedule after viewing available options. The "Manage Courses" use case is primarily extended by administrative staff, providing capabilities for course modification. The diagram includes five use cases: browse courses, register for courses, view schedule, manage courses, and generate reports. The system ensures proper flow of events, with entry conditions such as the user being logged in and having appropriate permissions, and exit conditions like the successful addition or removal of a course from a student’s schedule.

This model aims to provide an effective overview of the course registration process, supporting clear communication among students, staff, and administrators. It encapsulates the essential interactions needed to facilitate efficient enrollment, course management, and administrative reporting, ultimately improving the university's academic operations.

References

• Booch, G., Rumbaugh, J., & Jacobson, I. (2005). The Unified Modeling Language Reference Manual. Addison-Wesley.
• Object Management Group. (2017). UML 2.5 Specification. OMG.
• Cockburn, A. (2000). Writing Effective Use Cases. Addison-Wesley.
• Larman, C. (2004). Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development. Prentice Hall.
• Ambler, S. (2003). The Object Primer. Cambridge University Press.
• Jacobson, I., Christerson, M., Jonsson, P., & Ögren, M. (1992). Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley.
• Fowler, M. (2004). UML Distilled: A Brief Guide to the Standard Object Modeling Language. Addison-Wesley.
• Microsoft. (2018). UML Modeling for Software Development. Microsoft Docs.
• Rosenberg, D., & Stephenson, L. (2007). Use Case Modeling. Software Development Magazine.
• IEEE Software, (2012). UML in Practice: A Case Study. IEEE.