Beruflich Dokumente
Kultur Dokumente
ACTORS
· Registered User
· Borrower
· Librarian
· Student
· Staff
USE CASES
· Login
· Browse
· Search
· Article Printing
· Manage Browser
· Manage Items
· Manage Titles
· Assure Identity Of Browser
· Manage Suppliers Data
· Make Reservation
· Remove Reservation
· Check Out Item
· Return Item
FUNCTIONAL REQUIREMENTS
· Identify the actors that surround the system by considering which require
help from the system to perform their tasks; which groups are needed to
execute the system’s function, which groups are needed to interact with
external hardware or other software system and which systems are
needed to perform secondary functions for administration and
maintenance.
· Organize actors that are similar to one another in a generalization /
specification hierarchy. (Registered User—Borrower, Librarian)
· Where it aids understandability, provide a stereotype for each such actor.
· Populate the use case diagram with these actors and specify the paths of
communication for each actor to the system’s Use Cases.
CLASS DIAGRAM (Checkout Item)
CLASS NAMES:
· UIAgent
· Borrower
· Title
· Item
· CheckoutItemForm
· CheckoutItemFormContorller
· Staff
· Student
UIAgent class:
Operations:
· main()
Borrower class:
Operations:
· checkout()
Title class:
Operations:
· getmatching()
· getitems()
Item class:
Operations:
· setStatus()
CheckoutItemForm Class:
Operations:
· specifycriteria()
· search()
· selecttitle()
· selectitem()
· checkout()
CheckoutItemFormController Class:
Operations:
· search()
· getItem()
· checkout()
Student Class:
Staff Class:
FUNCTIONAL REQUIREMENTS:
· Each class has some responsibilities to be performed.
· Based on responsibilities that each class has, its attributes and
Operations are identified.
· Depending on the type of attributes and operations their visibility is
chosen.
· Depending on the Class its multiplicity is decided (i.e. how many other
classes are related to it).
· Based on the functionality messages are given to relate classes
· Only a Registered User can Access the Library Management System
· Librarian & Borrower are the Registered Users
· The Library system has to maintain all the relevant information about
books, Student Information.
· The Borrower(Student, Faculty) has to search the Books/Journals and
can make Reservation from the given list.
· The Librarian has to check for the Item status.
· The Library system has to send the status of the book.
· The Item class updates the relevant information of Books or Journals
(Set Status).
To model a collaboration.
· Identify the Mechanism would like to model. A mechanism represents
some function or behavior of the part of the system you are modeling that
results from the interaction of a society of classes, interfaces and other
things.
· For each mechanism identify the classes, interfaces and other
collaborations that participate in this collaboration that participate. Identify
the relationships among all there things as well.
· Use scenario to work through there things. A long the way, you’ll discover
parts of your model that were missing and parts that were just plain
semantically.
· Because sure to populate there elements with their contents. For classes,
start with getting a good balance of responsibilities, then; overtime turn
there into concrete attribute and operations.
SEQUENCE DIAGRAM (Checkout Item)
OBJECTS:
· Borrower
· UIAgent
· CheckoutItemForm
· CheckoutItemFormcontroller
· Item
· Title
MESSAGES:
· Specify Criteria
· Search
· Get matching
· Select title
· Get item
· Select item
· Checkout
· Set status
.
FUNCTIONAL REQUIREMENTS
· UIAgent
· Validator
· Form
· FormController
FUNCTIONAL REQUIREMENTS
· Logged in
· Specify criteria
· Make reservation.
· Checkout Item.
FUNCTIONAL REQUIREMENTS
FUNCTIONAL REQUIREMENTS
To model an Operation.
· Collect the abstractions that are involved in this operation. This
operation parameters the attributes of the enclosing class, and enter
certain neighboring classes.
· Identify the preconditions at the operation’s initial state and the post
conditions at the operations final state.
· Beginning at the operation’s initial state, specify the activities and
actions that take place over time and render then in the activity
diagram as either activity states or action states.
· Use branching as necessary to specify conditional paths and iteration.
(Verify Password)
· Only if an active class owns this operation, Use joining and forking as
necessary to specify parallel flows of control.