Library Management System

[attachment=18000]

COMMON MODELING TECHNIQUES:
To model the context of system.
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.




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


COMMON MODELING TECHNIQUES:
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.