Sequence Diagram.

Sequence Diagram:

Sequence diagram for registration of new customer:

Sequence diagram for customer login request:

Sequence diagram for browser the catlog:

Sequence diagram for creating an order:

Sequence diagram for a cart:

Sequence diagram for payment by customer:

Sequence diagram for deletion of an order:

Continue reading →

Activity Diagram.

Activity Diagram:
Activity for online shopping in customer view:

Activity diagram for online shopping system:

Continue reading →

Usecase Diagram.

Usecase Diagram:
Use case diagram is created to visualize the interaction of our system with the outside world. 

The components of use case diagram are:
Use Case: Scenarios of the system.
Actor: Someone or something who is interacting with the system.
Relationship: Semantic link between use case and actor. The forms of relationship are:
   a. Association.
   b. Dependency.
   c. Generalization.



1) Registration:-

• A user who is not registered will need to enter their details and get an account with the item shop.

Primary Actor: Customer.
Secondary Actor: Manager.
Flow of Events:
Basic Flow   

1. User enters preferred user login name, personal details and password.   
2. System validates name not in use.   
3. On success user is registered with item.   
4. On failure user is prompted to try another name.

Precondition: User not already registered. The user must not be already registered with the system
Post condition: User registered  successfuly
2) Login:
The online shopping customers need to be able to log on to the system                   
Flow of Events:
Basic Flow   

1. User accesses the login page   
2. User enters login name and password   
3. System validates entered data   
4. On success user is taken to item store   
5. On fail user may try again or go to register page

Alternate Flow:
Invalid Name / Password.

• If in the basic flow, the customer enters an invalid name and or password, the system displays an error message. 
• The customer can choose to either return to the beginning of the basic flow or cancel the login, at which the use case ends.

Pre-Conditions
The customer logs on to the system. Now he can browse the system.

3)Create Order

• The use case support searching for an item and browsing the resultant record set. 
• The customer can enter browse criteria and scroll through the results. 
• If they so wish, the user may select an item for addition to their current shopping cart.

Flow of Events
Basic Flow

• The customer can browse the current item catalogue on-line. 
• This should detail both the item details and he stocks details for items. 
• The user should be able to filter the item title, author, and item category.

Select an item    
   a) The user enters some filter criteria such as item title or author. This limits the returned set of books to those that match the supplied filter. Wild cards such as ‘*’ and ‘?’ should be supported.   
   b) The customer can select items by searching   
   c) The system requests the customer to enter the search details. This includes 
- Name of author
- Title of item
- Item category
And any other related information   
   d) The system finds the item or the customer based on his request. On selection the system provides a cart to drop items in.  
   e) The system will return both catalogue and inventory details for the items selected.
Search Unlisted Item.
         If the user cannot find an item in the current category, they should be able to place a special request. This should include details such as Author, Publisher, Title, ISBN and other helpful information.
-The customer enters a request for an item not in the catalogue.
-The system finds for this special order places by customer.
Alternate Flow
    If the search for unlisted item is not successful because of some wrong information regarding the search is provided, the system displays an error message. The customer can re enter the search details or can cancel the search, at which the use case ends.
    If the customer selects an item which is already selected by another customer, the system displays an error message. The customer can list that selection from the inventory and proceed further or can cancel the operation at which the use case ends.
Pre-conditions:
The customer must be logged on to the system before this use case begins.
Post-conditions:
    If the use case was successful, the customer has a list of his selections. Otherwise, the system state is unchanged.
4) Catalogue
A customer will use the catalogue use case to browse the items on sale and make selections.
    The customer can browse the current item catalogue on-line. This should detail both item details and the stock details for items. The user should be able to filter by item title, item category.
Flow of Events:-
Basic Flow
. Display a filtered set of items
. Scroll through list
. Page to next set of results
. Add item to cart
. Get more information on an item

Alternate flow:
None
Pre-conditions:
    The customer has to be logged on to the system before he makes selections by browsing the catalog
Post-conditions:
    If the use case was successful, the user makes selection from the listings in the catalog and adds them to cart. Otherwise, the system state is unchanged.
5. Manage Cart & Payments:-
    This use case allows a user to add an item's title to their on-line shopping cart.
A user first uses the select item use case to find the required item-then this use case to temporarily store the title for later purchase.
Flow of events:
A customer may add a selected title to their shopping cart
Add title to cart:
1) User has searched for and selected a title
2) User highlights the required item in the selection list
3) User presses an 'Add to Cart' button to add the item to their shopping cart
4) The selected title is added to the cart
Pay for order:
    Once a user has created their shopping cart and made their final selection, they may pay for their order and enter shipment details.
1) User selects the 'Pay for Order' menu option.
2) A secure web page allowing the user to enter card details, shipping details and associated information displayed.
3) If the card details are confirmed, the order is completed - an order number and receipt details are displayed to the user.
4) An email confirming their payment details is sent to the user.
5) The payment process is complete.
Remove Item from cart:
Proposed Pre-condition: Cart must have existing items.
. A customer uses this condition to remove a previously added item from his from his shopping cart
. A user removes an item from their shopping cart
. The system asks for confirmation of removal, as once removed an item cannot be retrieved
. The shopping cart will keep track of the current running total and update cart details when an item is removed
5)    View cart:
A customer views the contents of their cart.
The customer confirms the items in the cart and heads for payment.
Pre-condition;-
The user has created their shopping cart
Post-condition
    If the use case was successful, the system accepts the items placed in the cart and creates an order for purchase.
The customer pays for the order in the cart, this is done in highly secure environment. Otherwise, the system state is unchanged.
6)    Order Status:
Brief Description:
    The customer is able to view the states of their order on-line. They enter their order id and retrieve an updated report on status.
Flow of Events:
Basic Flow:
    The customer logs on to the system and verifies his order. If his order hasn't been shipped yet, he can cancel the order, under some circumstances.
7)    Enquire on Order status
    The customer logs on to the system, and then goes to the order status screen. From there have a list of their current orders and
the details of each order, including shipping status and back order status.
. A customer enquires on his order status by a posting a query.
. The system gives response regarding the query posted by customer. This includes the shipping details of his order.
8)    Cancel Order
    The user logs onto the system and locates their orders. An order that has not been shipped and is not yet filled (that is, is on back order) may be cancelled by the user.
. The customer enquires the order status. If the order has not been shipped yet, he cancels his order.
. A system accepts the user request and cancels the order.
Alternate flow: None
Pre-conditions: Order must be shipped
Post-conditions:
    If the use case was successful, the customer is able to view his order status and even cancels the order under some circumstances, if not shipped yet. Otherwise, the system state is unchanged.
9) Inventory
Brief description
    This use case explains that, online shop staff will be continuously updating the db.
Flow of Events
Basic Flow:
    The online shopping staff logs onto the system and updates the db. These include inventory, stock, shipment details.
Alternate Flow: None
Pre-conditions: The bookshop staff must logon to the system
Post-condition: The inventory is updated with the latest details of stock.

Continue reading →

Textual Analysis.

Textual Analysis:
(a)ACTORS
      i. Customer.
     ii. Manager.
    iii. Payment processer.
 
(b)VERBS 
      i. Customer: 
          1. Logs into the system.
          2. Browses/searches for items.
          3. Creates order.
          4. Manages cart.
          5. Pays the bill.
     ii. Manager:
          6. Looks for the validity of customer.
          7. Transactions of payments are performed by the manager.
          8. Order state is managed by the manager.
    iii. Payment processer
          9. Maintains the payments.
         10. Checks the credits.

Continue reading →

Online Shopping Introduction.

Online Shopping Introduction:   
    The current project emphasizes on analysis and design of an Online Shopping System, that serves the customers needs.The Customer’s available activities in the proposed system from logging on to browsing the book store, selecting items and making purchases are described.

    Let us just have an overview of the Online Shopping system:

• Customer gets registered after logging in to the site.
• The manager manages the registration of the customer.
• Manager looks whether the customer is validate or not.
• Customer searches for items in the catalog.
• Customer himself create order in the catalog.
• Inventory depends on the catalog.
• Customer manages the cart.
• Customer pays the bill to the payment processer.
• Credit check is done on the payment processer.
• Customer checks the state of orders from the manager.

Continue reading →

Stimulus Response Diagram.

Stimulus Response Diagram:

• Stimulus Response Diagram emphasizes on describing the life cycle of entire system as a whole.
• The components are:

    a. Start state.
    b. End state.
    c. State.
    d. Transition.

=>	Introduction.
=>	Textual Analysis.
=>	Usecase Diagram.
=>	Activity Diagram.
=>	Interaction Diagram.
=>	Class Diagram.
=>	State Chart Diagram.
=>	Stimulus Response Diagram.

Continue reading →

State Chart Diagram.

State Chart Diagram:

• State chart diagram show a life cycle of a single class.
• The state is a condition where the object may be in.
• The components are:

    a. Start state.
    b. End state.
    c. State.
    d. Transition.

Member:

Librarian:

Library Administrator:

 

=>	Introduction.
=>	Textual Analysis.
=>	Usecase Diagram.
=>	Activity Diagram.
=>	Interaction Diagram.
=>	Class Diagram.
=>	State Chart Diagram.
=>	Stimulus Response Diagram.

Continue reading →

Class Diagram.

Class Diagram:

• Class diagram shows structure of the software system.
• The class diagram shows a set of classes, interfaces and their relationships.
• The components are:

    a. Class
    b. Relationship:

The forms of relationship are:
    1. Association.
    2. Aggregation.
    3. Generalization.
    4. Composition.
    5. Dependency.

=>	Introduction.
=>	Textual Analysis.
=>	Usecase Diagram.
=>	Activity Diagram.
=>	Interaction Diagram.
=>	Class Diagram.
=>	State Chart Diagram.
=>	Stimulus Response Diagram.

Continue reading →

Interaction Diagram.

Interaction Diagram:

• An interaction diagram models the dynamic aspects of the system by showing the relationship among the objects and messages they may dispatch.

• There are two types of interaction diagrams:

    1. Sequence Diagram.
    2. Collaboration Diagram.

1. Sequence Diagram:

• Sequence diagram shows the step to step what mush happen to accomplish a piece of functionality provided by the system. 
• The components are:

       a) Actor.
       b) Object.
       c) Messages.
       d) Lifeline.
       e) Focus of Control.
 

2. Collaboration Diagram:

• Collaboration diagram displays object interactions organized around objects and their links to one another. 
• The components are:

       a) Actor.
       b) Object.
       c) Link.

=>	Introduction.
=>	Textual Analysis.
=>	Usecase Diagram.
=>	Activity Diagram.
=>	Interaction Diagram.
=>	Class Diagram.
=>	State Chart Diagram.
=>	Stimulus Response Diagram.

Continue reading →

Activity Diagram.

Activity Diagram.

• Activity diagram shows the flow of events within our system.

The components are:
    a) Start State.
    b) End State.
    c) Transition.
    d) Decision Box.
    e) Synchronization Bar.
    f) Swim Lane.

=>	Introduction.
=>	Textual Analysis.
=>	Usecase Diagram.
=>	Activity Diagram.
=>	Interaction Diagram.
=>	Class Diagram.
=>	State Chart Diagram.
=>	Stimulus Response Diagram.

Continue reading →

Usecase Diagram.

Usecase Diagram:

• Use case diagram is created to visualize the interaction of our system with the outside world. 
• The components of use case diagram are:

Use Case: Scenarios of the system.
Actor: Someone or something who is interacting with the system.
Relationship: Semantic link between use case and actor. The forms of relationship are:
    a. Association.
    b. Dependency.
    c. Generalization.

1) login:-
Primary Actor: Member
Secondary Actor: Librarian

Description:  

• The person who has membership in the library and can login into the system and use the services.
• All the information about members is maintained by the system.

Flow of Events:

• The member enters into the system by providing the user name and password.
• The catalog sends the details of user to librarian.
• The librarian validates the username and password is valid or not .
• Then librarian verifies the member is from staff or is a student.
• If member is not a student or staff then librarian rejects his request.
• If the member is either from staff or a student then provides with facilites provide to them.
• So that the member can access the books from library when ever She/he requires.

Precondition:-

• The person who is requesting should have membership and should be a staff or student.

Post condition:- NO.

2) View reports:-
Primary actor: member
Secondary actor: catalog

Description:

• The catalog displays the information about books, available, reservations etc and other information’s provided to the members by the catalog.

Precondition: 

• Member should be a valid user and he should logged in

Post condition: No

3) Search and browse:- 
Primary actor: member 
Secondary actor: NO
 
Description:

• The library displays the book in an order according to the subjects and the member can search or browse according to the requirements.

Flow of Events:

• The library assistant maintains the data base about the books that are available in the catalog.
• The user searches the book either by keyword or subject wise wise.
• If the book is found in the list, the user stops the search.

Precondition: 

• catalog has to have the data about the book.

Post condition: 

• member can reserve or take the book.

4) Make and remove reservation:-
Primary actor: Member
Secondary actor: Librarian
Description:

• A member can reserve a book or magazine that is not currently available so that when it is reserved or purchased by library the person is notified and can reserve a book at a particular date or remove the reservation made on a date.

Flow of Events:

• The members who have membership in the library request a book on a particular date.
• The librarian checks the book is currently available or not.
• If the book is available then librarian issues the book to the member on that date.
• If the book is not available currently then librarian reserves the specified book in account of person who requested it.
• When the book is available then librarian notifies the person who requested it and informs to the person.
• If the member wants to remove the reservation he requests the librarian  for that and then the librarian removes the reservation it is update in the catalog.

Precondition: 
A requesting person must be member of library.

Post condition: NO

5) Pay the dues:-
Primary actor: Member
Secondary actor: librarian
 
Description:

• The librarian checks the return date, if it expires S/he calculates the fines for extra dates so the member has to pay the dues.

Flow of Events:

• The librarian calculates the dues depending on the book returned date.
• If the return date exceeds the specified date then librarian calculates the fines based on exceed time then the librarian calculates the fine for extra time according to their norms.
• Then the member pays the fine depending on the calculated dues and hence member can access the other books.

Precondition: 

• The member has to exceed the time limit of retrun date.

Post condition: NO

6) Calculate dues:-
Primary actor: Librarian
Secondary actor: Member
Description:

• The library clerk checks the return date, if it expires S/he calculates the fines for extra dates and accepts from the member.

Flow of Events:

• The member returns the books to the library.
• The librarian receives the books and checks the returned date.
• If the return date does not exceeds the specified date then the takes the books and the member is capable for taking other books.
• If the return date exceeds the specified date then librarian calculates the fines based on exceed time and collects money from the member.
• When the member pays the fine then librarian gives a slip[ specifying that fine is paid and hence member can access the books.

Precondition: 

• The librarian checks for the status of a book.

Post condition: NO

7) Issue or take book:-
Primary actor: Member
Secondary actor: librarian

Description:

• Requesting for issue or take book is taking place between a member and library staff. 
• Member requests for book from the library or the book taken by the member is returned back after the return date has been completed.

Flow of Events:

• Member request a book in the library.
• Librarian checks for membership if book is available issues book to member.
• If book that is requested is not available notifies it to member.
• Librarian records the transaction of book.
• If the member  wants to return the book the  checks for return date of a book and then the returns the book  then the librarian record the transaction of book.

Precondition: 

• The person making the request must be a member of the library.

Post condition: NO.

8) Manages and validate:-
Primary Actor: librarian
Secondary Actor: member

Description:

• The librarian has the access to the information of the member so the librarian validates the member whether he is a genuine user or not and manages the membership and services provided to them.

Flow of Events:

• The librarian has the data of the members
• The member enters into the system by providing the required data
• The librarian validates the member  by comparing the data provides and the date which is stored by them so by that he comes to know the user is valid or not
• Then librarian verifies the member is from staff or is a student according to that he manages the people.

Precondition:-

• The librarian should have the details about the members and membership, reservations etc.

Post condition:- No.

9) Check reservations:-
Primary actor: librarian
Secondary actor: catalog

Description:

• A librarian check the reservation for the  book that is requested by the member if it is available on that date the librarian reserves that book for that date to the particular member so that one other user can access it.

Flow of Events:

• The librarian checks the book in the catalog that is needed by the member is currently available or not on that date.
• If the book is available then librarian issues the book to the member on that date update the catalog.
• If the book is not available currently then librarian reserves the specified book in account of person in the waiting state who requested it.
• When the book is available then librarian notifies the person who requested it and informs to the person.
• So that no other person can reserve or take that book on that particular date.

Precondition: 

• A  member has to make a request of  book on a particular date.

Post condition: NO
   
10) View reports:-
Primary actor: librarian
Secondary actor: catalog

• The catalog displays the information about books available, books needed , reservations made and details of the member  etc to the librarian

Precondition: 

• librarian should be a valid one and have access to the catalog database logged in.

Post condition: NO

11) Update catalog:- 
Primary actor: librarian
Secondary actor: catalog
Description:

• The librarian update the information about books available, books issued books return date, reservations made and details of the member etc in the catalog.

Flow of Events:

• The librarian stores  all the details and update their details if there are any changes  in the catalog.
• The librarian updates  all the  book that are newly available in the catalog.
• The librarian updates  all the  book that are issued in the catalog.
• The librarian updates  all the  book that are to be returend in the catalog.
• The librarian updates  all the  book that are made reservations  in the catalog.
• The librarian updates  all the  book that are not  available in the catalog.
• So that person can use the details provided in catalog and make the acess to the library.

Precondition: 

• There  should be a change in the previous data stored in the catalog .

Post condition: NO

12) Request for the new stock:-
Primary actor: librarian
Secondary actor: library administrator
Flow of Events: 

• The librarian places the order for the book which are not available in the library to the master librarian.

Precondition: 

• The librarian checks whether the books are available or not and whether they are needed or not.

Post condition: NO

13) Manages the librarians:-
Primary actor: library administrator
Secondary actor: librarian
Flow of Events:

• The master librarian supply the orders placed by the librarian.
• The  master librarian provides the permissions to acess the catalog to the librarian according to their norms.

Precondition: 

• The master librarian should have atleast one librarian under him.

Post condition: NO
        

=>	Introduction.
=>	Textual Analysis.
=>	Usecase Diagram.
=>	Activity Diagram.
=>	Interaction Diagram.
=>	Class Diagram.
=>	State Chart Diagram.
=>	Stimulus Response Diagram.

Continue reading →