Inventory management System

Michael Shaw

Description

Clubs and Societies spend lots of money buying equipment for members to use. Historically it has been a problem to keep track of items. Poor management leads to wasted funds replacing lost or stolen items.

There is a requirement to develop a System that can manage this inventory, the requests for equipment and provide reporting tools that enable the clubs to more efficiently manage their investments. The system should be lightweight and accessible from any location

The Users• Members of the club(Users)

• Users can Search for and View Items• Users can Make a Request for any number of

Items• Users can Report an Item if it is Broken/Faulty

• Club committee members(Manager)

• Managers approve/deny/close Requests, add/edit/remove Items, run reports, report Users etc

• Club Administrator(Admin)

The Users

• Admin adds, remove, suspends User accounts

Admin

Manager

User

Requests

• Made by a User for access to any number of Items

• Approved by a Manager

• Has a life cycle

Pending

Approved

Actioned

Closed

Items

• Represents a Physical object

• Has states and sub states

• Once a Request for items is actioned the Items change state to be Unavailable, in-use

User Actions Diagram

Manager Actions

Admin Actions

Pattern Identification

• Mode View Presenter

– MVC is overkill and a pain in the …

– Not fully modelled in full detail as not a Front end specialist

• Data Access Object

– Hibernate(perhaps?), loosely coupled to queries and statements

• Factory

– Lazy instantiation of requests

Class Diagram

Sequence Diagrams