Study Leave Architecture

Talib Hussain Chishti, Hitesh Bhugra

Users
All user

Administrator

Employees

Dean

Supervisor

Faculty Approver

Entities
Course

Leave Request

User

Entity Fields
User

Username(text)

Name (text)

Email Address (text)

Phone no. (integer

Address (Text)

Course

Course ID (integer)

Name (text)

Description (text)

Faculty (integer) Commented [PL1]: Does this reference a constant or

some other table with the faculty? What if they are taking a
. course at another university?
Foreign
Leave Request Commented [PL2]: I think you need more fields for these.
Key What about approval? There’s several levels of approval
User ID (text) that need to be tracked. Some other things you might want
to include: status, letter of recommendation, actual cost,
etc.
 Course ID (integer)

Leave ID

Career Development Plan (text)

Expected Cost(decimal)

Receipt ID(integer)Document Upload

Subject (for subject grid) Commented [PL3]: Should this be referenced in one of
the other CDTs?
subject ID (integer)

Name (text)

Description (text)

Coordinator (text)

Duration(integer)

Process Model : Commented [PL4]: Looks good to me!

Note : For all approved request, news is created

For all denied request, user is sent email

 Reports : Commented [PL5]: I’d also recommend including grids for
these. It’s nice to see a summary in a chart and the details in
No. of Request by department (Pie Chart) the grid.

No. of Request by Department

IT Management

Cost by Department

IT Management
 Department cost by Month
5
4.5
4
3.5
3
2.5
2
1.5
1
0.5
0
Jan Feb Mar Apr

IT Management

Note : All Reports create timely ‘news’ monthly Commented [PL6]: Make sure to plan: what information
is going to be displayed for the news post? Who will be able
to see it?