Summary:

Nicks Bike Rental Shop rents bicycles on Tybee Island in Georgia.Bikes are rented by the hour to customers who must pay by credit card in case the bikes are not returned or returned with damage.The people involved with Nicks Bike Shop are the customers and the staff.For the customers, Nicks need to know their driver's license number and issuing state as identifiers, along with their last name, first name, address, state, zip code, credit card number, CC type, and the CC expiration date.For the staff, Nicks need to know their employee ID, last name, first name, address, state, zip code, and date of hire.There are two main events that occur at Nicks Bike Shop, checking out bikes and checking in bikes.Both of the events are initiated by the customer with the staff responding.The other things Nicks Bike Shop needs to keep track o are the rental agreements and the bike inventory.For each rental agreement, Nicks needs to know which customer rented which bike on what date as identifiers, the check out time, the check-in time, and if there was any damage to the bike at check-in.For the bikes, Nicks need to know the bikes ID number, its description and the cost per hour.A customer may rent many different bikes and a bike may be rental by many different customers, however, a rental agreement is or only one bike rented by one customer. Each rental agreement is completed by a single staff member although a staff member may complete many rental agreements.When a customer checks out a bike, the staff member will record the customer's information and the specific bike they want to rent, then check to see if the customer has ever damaged a bike in the past and check that their credit card is valid. If the customer has ever damaged a bike or if their credit card is not valid, the rental agreement is terminated, otherwise the bike is issued

Deliverables

Open a new Astah model, save the Astah file as yourname and create the Following.

Actors and Attributes:

Within the Actors package/Folder within the Use-Case Model Folder within the Use Case View:

Create the Customer and Staff actors.

Create a generalized Person actor with the Customer and Staff being subtypes of the Person. Organize common attributes within the Person actor and unique attributes within the Customer and Staff actors.

Use Cases and Diagram

Within the Use Cases package/Folder within the Use-Case Model Folder within the Use Case View:

Create Check Out Bike and Check-In Bike use cases.

Create a Use Case Diagram that shows the Customer actor triggering the two use cases and the Staff actor as a receiver actor of the two use cases.

Activity Diagram

Within the Check Out Bike use case:

Create an Activity Diagram For the Check Out Bike use case.