CSIS 100 Week 7 Lab 5 UML Modeling Background The Unif

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 of 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.

Paper For Above instruction

The purpose of this assignment is to develop a comprehensive understanding of UML (Unified Modeling Language) and its application in system modeling through the creation of a Use-Case diagram and detailed use case descriptions. This exercise serves as a foundational activity in systems analysis and design, allowing students to illustrate system functionalities, identify critical actors, and document the interactions within a particular system. By engaging in this project, students will also gain practical experience with a web-based UML modeling tool, fostering skills necessary for professional system documentation and analysis.

The first step involves selecting an existing system to model. This can be any familiar system such as the university admission process, class registration, textbook ordering system, or another relevant system. The choice of system should allow the student to clearly identify multiple actors and key functionalities. For example, if a student selects the university registration system, the primary actors might include students, registration staff, and administrators, with use cases like “Register for Classes,” “Drop Classes,” “View Schedule,” “Update Student Info,” and “Check Enrollment Status.” The system summary should thoroughly describe the chosen system, its purpose, primary users, and main functionalities, solidifying the foundational understanding necessary for accurate modeling.

Next, students will utilize a web-based UML diagramming tool to create their Use-Case diagram. This involves opening the tool, creating a new blank diagram, and properly using UML symbols to add actors and use case ovals. Special attention must be paid to including at least three actors and five use cases, with one use case demonstrating an “extends” relationship—indicating optional or conditional functionality that extends the behavior of a primary use case. The diagram should clearly illustrate the interactions between actors and use cases, visually representing the system’s operational scope. Proper labeling and diagram organization are essential for clarity and professionalism.

Finally, students will develop detailed use case descriptions for each identified use case, following a prescribed format. These descriptions should include the use case name, participating actors, a step-by-step flow of events, alternative flows when applicable, entry conditions that must be met before the use case can initiate, and exit conditions that signify successful completion. The descriptions serve to elaborate on the diagram, providing comprehensive narrative details that specify how system interactions occur. These documents, along with the UML diagram, will be submitted as the final deliverables, demonstrating the student's understanding of UML concepts and their ability to model real-world systems accurately and effectively.

References

• Ambler, S. (2004). The Object Primer: Agile Model Driven Development with UML 2.0. Cambridge University Press.