<Online Notice Board System>

Design Document

Version 1.0
 Revision History

Date Version Description Author

(dd/mm/yyyy)

16-6-2021 1.0 Due to the progressively

inventions of the technology,
everything can be seen with
innovative and latest
features. As there are a lots
of web applications are
developed now with
interesting and very useful
features, there should be a
source where person or
institutes can get or post
there requirements. This
project is to develop a web
application named as “Online
Notice Board System” The
system will contain notice
boards created by
college/university admin.
Admin can send the
notification to the particular
students as well as teachers
regarding any new activity
happening in
college/university campus or
any fest participation, fee
payments, results, libraries
dues, hostel dues, any
workshop/conference
registrations, warnings and
reminders etc.
 Table of Contents

1. Introduction of Design Document

2. Entity Relationship Diagram (ERD)

3. Sequence Diagrams

4. Architecture Design Diagram

5. Class Diagram

6. Database Design

7. Interface Design

8. Test Cases
 1. Introduction of Design Document

Design document is very important in any software or any type of application.

Design document is very helpful to explain about application. A design
document is a way for you to communicate to others especially to your client. A
design is considered good if it fulfill all the requirements. If any point of the
design is not justified then it should be re-considered. A design document
consist of the following components, Entity Relationship Diagram (ERD) is a
graphical representation of data. Sequence diagram shows how objects interact
with each other. Architecture diagram provide a tiered architecture of system.
Class diagram describe the system by showing their classes. Database design is
process of creating a detailed data model of the database. Interface design
describes the most important features of the application as you are visualizing
your application to be in actual development phase and Test case are provide in
detail.

Purposes of the design phase

1.  Developing the document is useful to understand the needs and opportunity of

the customers.

2.  It is useful to identify and evaluate the limit of possible solution and select a
best one’s. which is more accurate

3.  It is useful to represent the business case explain the cost, benefits and risks of
the preference solution against the organization policies objectives and
priorities.
 4.  It is useful to do planning the analysis and the submission of the business case
and outline the risks

5.  It is also useful to search the best resources for development of software.

6.  It is useful to understand and evaluate the needs.

7.  It is useful in guides and controls projects execution

8.  It is useful in implementation of detail strategy.

9.  It is also useful to confirm budget and schedule.

10.   It is also useful to assign the roles and responsibility of the team member of

the project. So that they could ready to face the implementation phase

11.   It is useful to control the project so that it may complete on time and within
budget.

12.   It is also useful to manage risk and issues.

13.   It is also useful to inform the stack holder.

2. Entity Relationship Diagram (ERD)

Registered

NO Yes

Register

Enter User i.d / Password

Login

Teacher Ye Admin
s

Notices Update password Feedback User Update Notice

View Create Sort Modify Delete

Accept Active De-Active

View Create Modify Delete

No

Student
 View Notice Download Notice Sort Notice Feedback

Logout
Name
Update notice Name Upload
notice
I.D
I.D

Admin
Teacher
Manage Delete
account ha notice
Name ve

Read notice
Student
Personal
I.D detail

Addres Mail
Download s
notice
3. Sequence Diagrams:

Student Register Login View / Sort Notice Download Notice Feedback

Enter Details

Get User / Pass

Enter User Password

Authentication

Sort / View Notices

Generate Notice

Download Notices

Generate Notice

User Feed backing

 View / Create / Sort
Teacher Registered Login Modify / Del Notice Feedback
Notice

Enter Details

Get User / Pass

Enter User Password

Authentication

Create/ Sort / View Notices

Generate Notice

Modify/del Notices

Generate Notice

Teacher Feed backing

 Admin Register Login Manage Notice Accept / Reject Update password
Request

Enter Details

Get User / Pass

Enter User Password

Authentication

Insert/update Notices

Action on Notice

User register request

Authority

Give option to user

4. Architecture Design Diagram

Client Server Business Data Layer

Mobile
Browser
Application
Server

Web Web
Browser Server Database
File External
System System
 Application

5. Class Diagram

Admin
#Username: char
#Password: char
Email: char
Mob: int
+aid : int
+addNotice()
+updateNotice
+viewNotice()
+deleteNotice
+acceptRequest()
+activeUser()
+de-activeUser()

Login
-Username : char
-Password : cahr
+login()
+logout()
+register()

Register
-Name : char
Mob : long
-Emali : char
-Dob : char
-College : char
-User name : char
-Password : cahr
+student()
View Notice +teacher()
-nid : int +admin()
Notice : long
-Not_Date : char
-Exp_Date : char
-College : char
+student()
+teacher()
+admin()
6. Database Design

Notice Table

Teacher table
Student Table:
7. Interface Design