0% found this document useful (0 votes)
219 views

Salman 1

This document contains a lab assignment on use case diagrams for a software design and architecture course. It provides definitions and examples of actors, use cases, include and extend relationships. It then lists 5 exercises asking the student to draw use case diagrams for systems related to tuition payment, tracking college graduates, and car rentals.

Uploaded by

Salman Hafeez
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
219 views

Salman 1

This document contains a lab assignment on use case diagrams for a software design and architecture course. It provides definitions and examples of actors, use cases, include and extend relationships. It then lists 5 exercises asking the student to draw use case diagrams for systems related to tuition payment, tracking college graduates, and car rentals.

Uploaded by

Salman Hafeez
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

Lab Assignment 1

Course:

Software Design and Architecture


Topic:

UML Use Case Diagrams


Name:
Mohammad Salman Hafeez Dr. Aqeel Iqbal

Submitted to: Semester:


6th

Registration no: Date:

5049

4th April, 2013.

Exercises
1. Contrast the following terms:

Actor:
An actor is a role that a user can play in a system. It can be a user or a system that plays a role in the system under construction. Stakeholders may be an actor but every stakeholder is not an actor.

Use case:
A use case is a main task performed by an actor. Use cases represent the complete functionality of a task. B. extends relationship; includes relationship

Extends relationships:

In UML modeling, you can use an extend relationship to specify that one use case (extension) extends the behavior of another use case (base). This type of relationship reveals details about a system or application that are typically hidden in a use case.

Includes relationship:
In UML modeling, an include relationship is a relationship in which one use case (the base use case) includes the functionality of another use case (the inclusion use case). They include relationship supports the reuse of functionality in a use case model.

2. Capture the functionality for a system that accepts a tuition payment from.

3. Extend the use case diagram in exercise #2, To capture


the situation where Employees of the college are not billed for tuition, Their spouses do not get a full Tuition waiver, but pay for only 25 percent of the total tuition.

Use Case Diagram

4. Draw a use-case diagram for a college that would like to


keep track of each Graduate. In order to maintain strong ties to its alumni, the college holds various events. The college needs to keep track of which graduates have attended which events. The college keeps in contact with graduates by mail, email, telephone and Fax to announce each event and keep graduate information up to date. The College would like to be able to produce a report showing the latest information about a graduate and the events the graduate attended.

5 An auto rental company wants to develop an automated


system that would handle car reservations, customer billing, and car auctions. Usually a customer reserves a car, picks it up, and then returns it after a certain period of time. At the time of pick up, the customer has the option to buy or waive collision insurance on the car. When the car is returned, the customer receives a bill and pays the specified amount. In addition to renting out cars, every six months or so, the auto rental company auctions the cars that have accumulated over 20,000 miles. Draw a use case diagram for capturing the requirements of the system to be developed. Include an abstract use case for capturing the common behavior among any two use cases. Extend the diagram to capture corporate billing, where corporate customers are not billed directly; rather the corporations they work for are billed and payments are making sometime later.

You might also like