eFusion

1
eFusion

• By Group 2

2
Purpose eFusion VS eBay

• Current Systems
• eBay, Amazon
• eFusion
• Provide student communities such as the one
  present at F.I.U. with an affordable sale/trade
  system that targets the student population.
• eFusion users will be able to post and buy/trade
  items such as books, computers, and furniture in
  a user-friendly environment.
• Eliminating shipping costs

3
Usability

• Self explanatory, easy to use Graphical User
  Interface.
• User only needs to have minimal computer/internet
  familiarity. Any user meeting these requirements
  will easily use eFusion without the help of the
  users manual.

4
Reliability

• eFusion will work to its required functionality
  and will not be prone to extreme failures because
  the administrators continuous maintenance will
  guarantee its functionality and dependability at
  all times.
• The administrators occupation also includes
  biweekly backups of the systems data.

5
Performance

• eFusion's page transitions should last no longer
  than 30 seconds for a regular 56K modem
  connection.
• Users must be capable of doing several related
  transactions using a minimal number of steps.
• The system must be available at all times except
  during maintenance periods.

6
Interface

• User interface will have a persistent main menu
  that user can access to register, post a product,
  search for a product, etc.
• Simple user-friendly pages that will guide users
  towards their goals.

7
Implementation

• Java Server Pages (JSPs)
• mySQL Database
• JavaScript

8
General Use Case
9
Register Scenario Eduardo Soto

• Gina heard from some friends, that eFusion was a
  good place to find textbooks and many other
  student materials. After browsing through the
  wide variety of things sold at eFusion, she
  decides that she wants to be part of it. She
  goes into the section to register, where she gets
  a form back from the eFusion system. Gina fills
  out the form with all the requested information,
  and then clicks the link/button to submit the
  registration information to the system. She gets
  a message back saying that her social security
  number was missing one digit. Gina then fixes
  the social security number, and clicks the
  link/button to submit the information once again.
  This time everything was fine, and she gets the
  confirmation page, and now Gina is ready to start
  buying and posting her product for sale.

10
Use Case Eduardo Soto

• Use Case Name Register
• Participating Actors User
• Flow of Events
• The user activates the RegisterLink function.
• eFusion brings up the RegistrationForm.
• User fills out their personal information,
  including first name, last name, street address,
  city, state, zip code, date of birth, e-mail
  address, desired username and desired password.
• Upon filling out the information the user calls
  the
• SubmitRegistrationInfo function.
• If there are any problems with the information
  submitted (invalid entries, empty fields,
  username already in use, etc) the
  RegistrationForm will show up on the screen again
  with a small message at the top explaining the
  problem. Else the user will be registered with
  eFusion.
• Entry Conditions User has not registered and
  whishes to useFusion.
• Exit Condition The user has completed eFusion
  registration.

11
Sequence Diagram Eduardo Soto
12
Class Diagram Eduardo Soto
13
Login Scenario Adelein

• Danny is a registered user of eFusion and he
  wants to buy some computer parts. He clicks the
  link/button to log in. Then Danny enters the
  user id and password that he got from
  registering. His user id and password are
  validated by eFusion to make sure that he is
  indeed registered. After validating his login
  information and deciding that he is a registered
  user, eFusion logs Danny into the system.

14
Use Case Adelein

• Use Case Name Login
• Participating Actors User
• Flow of Events
• The User calls the Login function.
• eFusion displays the LoginForm.
• The User enters username and password and submits
  the form.
• eFusion activates the AuthenticateUser function
  and tries to login the User. If information was
  valid then log user into the eFusion, else show
  LoginForm again.
• Entry Conditions The User is not logged into
  eFusion and is registered.
• Exit Conditions The User has been logged into
  the system or the User receives message
  explaining why eFusion could not log User into
  the system.

15
Class Diagram Adelein
16
Sequence Diagram Adelein
17
eFusion ProductSearch

• By Yaima Campos

18
Objectives

• ProductSearch on eFusion
• Sample Scenario
• Use Case Description
• Class Diagram
• Sequence Diagram

19
Scenario ProductSearch eFusion

• Scenario name
• ProductSearch
• Participating actor instances
• Esther User
• Flow of events
• 1. Esther is a student at Florida International
  University who wants to buy a new laptop
  computer. She needs an inexpensive one because
  she plans to use it only for word processing and
  to access the internet.

20
Scenario ProductSearch eFusion

• 2. One of Esthers classmates makes her aware
  about the new eFusion online store.
• 3. Esther visits eFusions home page and clicks
  on the search button to start searching for the
  computer she wants.
• 4. Esther selects buy in the post category and
  computer in the product category.
• 5. Esther clicks on a link to submit her query.
• 6. Esther gets a page with a list of all the
  laptop computers that match the category that she
  specified.

21
Use Case ProductSearch eFusion

• Participating Actor
• User
• Flow of Events
• The User activates the Search function.
• eFusion displays the SearchMenu page.
• User selects a product category (book,
  computer,etc) and indicates the posting category
  (sale/trade).
• eFusion displays the available items under the
  selected category by activating the
  ProductDisplayPage.
• User may now browse the displayed products.

22
Use Case ProductSearch eFusion

• Entry Conditions
• There is no entry condition any user could
  search for products on eFusion.
• Exit Conditions
• User browsed eFusion products.

23
Class Diagram ProductSearch eFusion
24
Sequence Diagram ProductSearch eFusion
25
ProductSearch eFusion

• Thank You

ycampo02_at_fiu.edu
26

• PostProduct

BY Yisell Diaz
27
PostProduct SCENARIO

• Francis is an FIU student who wants to sell her
  old computer monitor.
• She decides to use eFusion to post her monitor
  for sale.
• She immediately logs into eFusions web site, and
  clicks on the PostProduct link.
• A form is displayed on the screen. Francis enters
  a name and a description for her product she
  selects the sale category and uploads a picture
  of her monitor.
• After Francis reviews the information entered,
  she clicks the Submit button to submit her post
  and waits for a confirmation.
• Francis takes a look at her posting summary as
  well as the product Id displayed on the
  confirmation page.

28
PostProduct USE CASE MODEL

• Use Case Name PostProduct
• Participating Actors User
• Flow of Events
• User activates the PostProductLink function on
  the main menu.
• eFusion displays the ProductForm, which allows
  the User to insert a picture of the product,
  assign a name and a category (book,computer,etc),
  as well a description of the product and
  selection of a posting category (sale/trade).
• User fills in required fills of the ProductForm
  and calls the
• SubmitProductButton function.
• 4. eFusion displays PostProductConfirmationPage
  , which displays to the user a product id , and a
  summary of the posted product.

29
PostProduct USE CASE MODEL

• Entry conditions User must be logged in.
• Exit conditions User posted a product
  successfully.

30
PostProduct SEQUENCE DIAGRAM
31
PostProduct CLASS DIAGRAM
32
PostProduct CONCLUSION

• THANK YOU

33
Scenarios Eduardo Quan

• Heather logs into eFusion looking for a new
  laser mouse for her new computer. She finds the
  mouse that she wants, and clicks the link/button
  to buy the product. She gets back a page from
  eFusion that lets her pick the payment method,
  and walks her throughout the payment process.
  After the payment is completed, Heather gets a
  page back confirming the transaction that just
  occurred, and reminding her that if she wants to
  leave feedback later on, she must save the
  product id of the object she just bought.
• Kathy found a book at home that people are using
  for a class that she already took, so she decided
  to log into eFusion to trade this book for
  another one she will need for next semester. She
  searches for the book she will need, hoping that
  this person needs the book she has to offer.
  After reading many postings, Kathy finally finds
  a student named Leah who has the book she wants,
  and will take as a tradeoff the book that Kathy
  has to offer(as stated in Leahs product
  description). Kathy clicks the link/button to
  trade. She gets back a page with Leahs contact
  information, so that she can contact her and
  propose the trade.

34
Use Case Buy

• Buy
• Use Case Name BuyProduct
• Participating Actors User
• Flow of events
• User activates the BuyProduct function.
• eFusion activates the SelectPayment function,
  which displays 2 payment methods for the User,
  credit card or check.
• User selects credit card or check.
• If User selects credit card eFusion calls the
  HandleCreditCard function which redirects user to
  a credit card payment subsite where they enter
  the credit card info. Else if User selects to
  send a check, efusion activates the HandleCheck
  function.
• User activates the ConfirmPurchase function which
  finalizes the transaction.

35
Use Case Trade

• Trade
• Use Case Name TradeProduct
• Participating Actors User
• Flow of events
• The User activates the TradeProduct function.
• eFusion activates the DisplaySellerInfo.
• Entry Conditions User is logged in and has
  selected a product to trade.
• Exit Conditions User has acquired the
  contact information of the seller.

36
Sequence Diagram Eduardo Quan
BUY
lo
37
Sequence Diagram Eduardo Quan
trade
38
Class Diagram Eduardo Quan
39
Scenario Jose

• Julia moved to a different address and wants to
  update her shipping information to reflect the
  new address.
• She logs into eFusion and clicks the edit-profile
  link.
• A form appears with the current user information.
• She changes the shipping address field and clicks
  the save changes button to submit the new
  information.
• After validating the data, eFusion decides that
  the information is correct and the profile is
  updated permanently.

40
Use Case Jose

• Use Case Name EditProfile.
• Participating Actors User
• Flow of Events
• User activates the EditProfileLink function.
• eFusion responds by displaying the UserInfoForm
  with the current users information. The form
  includes the user's name, e-mail address, and
  phone number, city, state, etc.
• The user updates the interested fields and
  activates the SaveChanges function, which updates
  the users profile.
• Entry Conditions
• User is logged-in.
• Exit Conditions
• User successfully completes transaction
• User is notified why the transaction could not be
  completed.

41
Sequence Diagram Jose
42
Class Diagram Jose
43
Scenario (Leave Feedback) Larissa

• Leave Feedback
• Ana wants to leave feedback for another user
  that she bought a book from. Then she gets the
  product id of the book. Ana clicks the
  link/button that activates a field for her to
  input the product id, and after entering the
  product id she presses the link/button to get the
  form to leave feedback. The product id was
  valid, meaning that it existed, and that no
  feedback has been left for that product id.
  After that, eFusion gives back a form to leave
  feedback, and Ana rates the other user involved
  in the transaction. She then clicks the
  link/button to finally submit the feedback.

44
Use Case (Leave Feedback) Larissa

• Use Case Name LeaveFeedBack
• Participating Actors User
• Flow of Events User activates the LeaveFeedback
  function.
• eFusion brings up the LeaveFeedbackForm.
• User has the choice of 'positive',
  'neutral', or 'negative', as well as a
  field to leave a comment about the transaction.
• User activates the SubmitFeedback
  function, which submits feedback.
• Entry Condition User must be logged in.
• Exit Condition User successfully leaves
  feedback.
• Exception Connection to the server is lost,
  in which case the User will be notified.
• Transaction information was not
  properly saved into Users
• feedback
  history, in which case, the ConfirmationPage
  function will display the appropriate
  message.

45
Scenario Larissa

• Check Feedback
• Bob is a registered user of eFusion, but this
  time he just wants to check the feedback for
  Charles, another user that is selling the mp3
  player that he wants. Bob clicks on the
  Charless id and a page with his feedback
  information appears. Now Bob can decide whether
  to buy the mp3 player from Charles or not.

46
Use Case (Check Feedback) Larissa

• Use Case Name CheckFeedBack
• Participating Actor User
• Flow of Events User activates the
  CheckFeedback function.
• eFusion searches the feedback
  information for the specified ID and
  calls the DisplayFeedbackPage.
• Entry Conditions There is no entry
  Conditions.
• Exit Conditions User obtains
  feedback information for specified ID.

47
Sequence Diagram (Check Feedback) Larissa
48
Sequence Diagram (Leave Feedback) Larissa
49
Class Diagram Larissa
50
(No Transcript)