book academia on-line case study
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

book academia on-line case study

on

  • 294 views

 

Statistics

Views

Total Views
294
Views on SlideShare
294
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

book academia on-line case study Document Transcript

  • 1. Version 1 Individual Report – Project Two Student Name: SID: Assessment Item No.: 5 Assessment Title: UML modelling for the BookAcademia-On-Line case study @Coventry University Page 1
  • 2. Version 1 1. Use case Diagram (produced using a CASE Tool) The above picture shows the use case diagram for BookAcademia-On-Line. This use case diagram explains the behaviour between the actor or the users of BookAcademia-On-Line. The actors or user in this diagram are the customers, sales and bank validation system. An end result is achieved through the actors or user. Actors are not necessary human, but in this case the customers are human but the sales and bank validation are necessary not humans. @Coventry University Page 2
  • 3. Version 1 2. Use case Description (for each of the use cases) The table below gives more details about the use case diagram and also explains more about the process of the actor achieving an end result. The tables below can be called dependency table, this shows all the process and possible problems the actor might encounter during the flow of event. The table also shows how all this events depends on each other Title Actors Brief description Pre-condition Flow of event Post condition alternative scenario @Coventry University Credit card /debit card details Customer Customer saves bank details on account for any transaction Customer goes on website and saves bank details when creating profile Brings out bank card and stores account number and other details on card onto the profile on website Bank details verify by website and bank Wrong bank details Page 3
  • 4. Version 1 Title Actors Brief description Pre-condition Flow of event Post condition Alternative scenario Title Actors Brief description Pre-condition Flow of event Post condition Alternative scenario @Coventry University Search for product Customers Customers can search for product they want to buy Customer clicks on the search icon on website Customer visits website and search for product Browse through website to look for product Cannot find product or item Browse website Customers Allows customer to view range of product they have Open websites on any computer device connected to the internet Turn on device and go on internet to visit the website and browse website View different product on website Website not loading or visited the wrong website Page 4
  • 5. Version 1 Title Actors Brief description Pre-condition Flow of event Post condition Alternative scenario Title Actors Brief description Pre-condition Flow of event Post condition Alternative scenario @Coventry University Add to shopping cart Customer Allows customers to buy multiple product at once View items or product they will like to buy View items and add to shopping chart View items Unable to add to shopping chart Place order Customer Item ready to be delivered Selects products to order Add product to shopping cart and place order Item ready to be delivered after payment Order not successful Page 5
  • 6. Version 1 Title Actors Brief description Pre-condition Flow of event Post condition Alternative scenario Title Actors Brief description Pre-condition Flow of event Post condition Alternative scenario @Coventry University Creating wish list Visitors Visitors not registered to the website can creating list of product they will like to buy for latter Visitors visit website Visitors visit website, view products and add them any product they like into wish list Wish list created for later purchased Unable to create wish list Updates order sales Sends order to the warehouse for delivery Looks at order list and check for availability Look at order, sends order to warehouse and arrange for delivery Item packed and ready for delivery Delivery time delayed Page 6
  • 7. Version 1 Title Actors Brief description Pre-condition Flow of event Post condition Alternative scenario Title Actors Brief description Pre-condition Flow of event Post condition Alternative scenario @Coventry University Banking validation system customer Verify and accept customer payment Enter account details Input account details during registration and order for product and money gets taking out of customers account Enter bank details Incorrect account details Check out Customers Verify and order complete Select product and pay Select product to shopping cart, place order and pay for product Shows order details Order not successful Page 7
  • 8. Version 1 3. Class Diagram (produced using a CASE Tool) After presenting the case study in a case diagram and a case description for each use case identified in the case diagram, the final step was to present it in a class diagram which shares the same common structure and behaviour. Presenting the case study in a class diagram enable us to see the attributes and operations of each class which means what each class depends on to be able to function. In conclusion, I have really enjoyed doing this task because I have being able to gain more experience in using the rational rose software and also the starUML. @Coventry University Page 8