Resource Management Software Design notes

Procedure

1.       Use case

2.       Class

a)         Concepture Model

3.       Sequence Diagram

a)         Specification

                         i.              Data storage

                       ii.              GUI

                      iii.              Operation between client and server

4.       Class Diagram

a)         List all the classes and relation

Use Cases

1.    Select Item

a)      Client, Project, Resource Allocation, Timeslot, Consultant, Machine, or Room.

b)      Verification Existance (update or display in the lower-right panel)

c)      Verify Modify permission

d)      Display Project-View Graph if is a project.(By initiating the
“Generate Project-View Graph” use case)

 

2.    Add Client

3.    Modify Client

a)      Select Client must first be performed.

4.    Delete Client

a)      Select Client must first be performed.

 

5.    Add Resource

a)      Consultant, Machine, and Room

6.    Modify Resource

7.    Delete Resource

8.    Alternative Courses

 

9.    Add Project

10.Modify Project

11.Delete Project

 

12.Add Resource Allocation

13.Delete Resource Allocation

 

14.Start GUI

a)      Performed First. Provide Logon Screen.

15.Shutdown GUI

 

16.Add User

17.Modify User

18.Delete User

19.Change Password

 

20.Forecast Revenue

 

21.Generate Staffing Report

22.Generate Conflict Report

 

23.Add Timeslot

a)      add a new timeslot to a given resource allocation.

24.Modify Timeslot

25.Delete Timeslot

 

26.Display Project-View Graph

Figure 1: Use Case Diagram Showing Use Cases Only Available To AdminUsers

Figure 2: Use Case Diagram Showing Uses Cases Available to Both AdminUsers and
ProjectLeadUsers

Figure 3: Use Case Diagram Showing Use Cases Available To All Users

Conceptual Model

Conceptual models focus on identifying the domain elements and their attributes. No
operations (methods) are defined on the conceptual model .

entity classes

service classes,

The conceptual model lacks detailed descriptions of important classes related to the graphical user interface
(GUI) and database access.

Figure 4: Conceptual Model

Sequence Diagrams

They are especially useful for determining what methods are needed in a class.

Sequence diagrams come in two forms:

High-level sequence diagrams give an overall picture of the classes needed in the system.

Low-level sequence diagrams show all of the steps (function calls) needed to perform an operation.