Professional Documents
Culture Documents
By
Muzammil Hussain
(09-arid-544)
Umar Farooq
(09-arid-538)
Muhammad Bilal
(09-arid-525)
Supervised by
In this project
We intended to develop a complete database which will maintain all the record and
information of notices, as well as all the notices are updated timely from their relevant
tables.
It will reduce the time of clerical staff to maintain the information of notices and
announcements and the result reduce the effort of student for searching the notices.
Program would have its own user login ID and password. It is necessary for any user to
give proper login and password for accessing the system in order to perform the
functionality.
Administrator will maintain all the information of user(staff and student) in database. He
will add user, update the existing record of the user and can delete the specific record.
Administrator will maintain all the notices and announcements in database. He will add
update and can delete the specific notices.
Administrator can upload notices for user. Notices like attendance, result, timetable,
datasheet and exam can b upload for user.
1.4.5 Assign role to user
Administrator will assign role to the user and that particular user have assign different
roles. Mainly our system has three roles: student, staff and admin.
1.4.6 Logout
User will exit from the system by using the logout option from the application.
Our system will provide reports of the functionality which it provides as:
When a registration form is been filled up a quick review of the data entered is
displayed to the user before storing it so as to prevent any mistake and if the
information is submitted the student get registered.
When any of the tasks is successfully completed a report is generated that describe
that the task has been done.
With the aim to facilitate user as well as to maintain the time saving environment our
system when fully implemented will provide the following features:
1.6.1 Efficient:
Our goal is to provide an easy access of student towards their notice, so as to save the
effective time and efforts. This system will reduce the time of administration to keep the
student and staff notices. It reduces the time and hectic effort of manual finding of notice and
announcements
The interface of the system is user friendly. The data retrieval, insertion, editing and deletion
will be made easy and simple so that the common user can handle database efficiently.
The simple to use data entry form will be provided to facilitate the user to enter the data in
database. The powerful data entry controls have been provided to view, add, modify and
delete the fields of record.
1.6.5 Data security and integrity:
Every user can access the system if he/she have the right to do so. If the username and
password is validated only then the system components can be accessed, viewed and
modified. So, the system is fully secured from the unauthenticated data entry or corrupt usage.
Our aim is to develop install and support the globally acknowledged technologies that also go
with the university institute of information technologys standards of Implementation.
To develop Electronic notice board using oracle 10g with database and form builder. Oracle
Developer Suite is the most complete and integrated development environment, combining
the power of application development and business intelligence tools in a single suite that is
based on the latest industry standards. Most of the multinational and large companies are to
use oracle because the product that can make by this is more secure and reliable language is
used for development is PL/SQL.
CHAPTER 2
REQUIREMENT ANALYSIS
Software Requirement Specification (SRS)
2.1 Introduction
The Electronic notice board is an exciting new innovative way to send information to
visitors, staff and students. Replace paper notice board with an electronic notice board to
speed up the process of communication to an instant. We will implement an electronic notice
board for UIIT, which will be connected to the university management office. He will be able
to display messages or notices on that computer screen by typing them in the software. After
that this message or notice send to the Electronic notice board.
2.2 Purpose
The purpose of electronic notice board to eliminate the paper work from the university
environment, Due to this innovative technology everybody in the university will be
timely updated from important announcements and notices.
The proposed solution of the electronic notice board to reduce the paper work or
workload on the university management. Paper notice board is managed and update is
very difficult task and printing or paper cost is high. When developing, this project will
eliminate the cost of printing or paper that used in notice board.
Functional requirements capture the intended behavior of the system. This behavior may
be expressed as services, tasks or functions the system is required to perform. In product
development, it is useful to distinguish between the baseline functionality necessary for
any system to compete in that product domain, and features that differentiate the system
from competitors products, and from variants in your companys own product
line/family. Features may be additional functionality, or differ from the basic
functionality along some quality attribute (such as performance or memory utilization).
One strategy for quickly penetrating a market, is to produce the core, or stripped down,
basic product, adding features to variants of the product to be released shortly thereafter.
This release strategy is obviously also beneficial in information systems development,
staging core functionality for early releases and adding features over the course of several
subsequent releases.
Add and edit tasks.
Add and edit scheduled tasks.
Add and remove tasks.
Schedule tasks
Display reports of tasks.
ENB project was created to modernize the classic means of communication through the pin and
paperboard based communication to the more efficient and dynamic communication of general
information to the students of the University.
Student and faculty will get the timely information while they are walking around School office
or in Labs. ENB will remind the student about the critical dates for the exams, social events, and
warnings etc. It will positively affect the student behavior towards the academic excellence and
time management. ENB will decrease the rate of late assignments submission and absents among
the students.
ENB will decrease the workload of university management for printing and pasting the
traditional paper based notice boards. ENB system will not require any additional hardware and
it will be developed in the oracle hence low cost of development and implementation. ENB will
bring forth a positive change in the university environment.
The server Machine in which this system will be deployed, have following hardware
specifications
The client machine which can access this system will be have following hardware
specifications
Processor speed is minimum 1GHZ.
Ram minimum 512MB.
Hard disk minimum 20GB.
Operating system windows XP with internet explorer browser.
PROJECT OBJECTIVES
The project ENB aims to develop and implement application software that will
disseminate the academic information in the network environment among the students
and faculty members. The project ENB will open the new powerful channel of
communication between university management and students.
Name
Staff Teacher ID
Signup
Account created
Email ID
Ph#
Designation
ID: ENB-01
Title: Sign up of a staff
Description: If there is any staff member who had not sign up in to the university
Electronic NOTICE Board system, then he/she should have to sign up
first.
Primary Actor: Staff
Preconditions: He/she should have staff member of the University
Post conditions: He/she should have a valid registration number
Main Success 1. Staff selects sign up" from the menu.
Scenario: 2. System displays sign up form.
3. User fills the form.
4. User clicks "Submit" button.
5. System displays a confirmation message.
Extensions: May be User give wrong information then given error.
Frequency of Use: Each User used only first time
Status: Pending Review
Non-functional
requirements:
Name
Student REG#
Signup
Section
Shift
Degree
ID: ENB-02
Title: Sign up of a student
Description: If there is any student who had not sign up in to the university Electronic
NOTICE Board system, then he should have to sign up first.
Primary Actor: User
Preconditions: He should have to be the student of the University
Post conditions: He should have a valid registration number
Main Success 1. Student selects sign up" from the menu.
Scenario: 2. System displays sign up form.
3. Student fills the form.
4. User clicks "Submit" button.
5. System displays a confirmation message.
Extensions: May be User give wrong information then given error.
Frequency of Use: Each User used only first time
Status: Pending Review
Non-functional
requirements:
Priority: Maximum priority
<<include>>
UserName
Validity
Signin Account Opend
User
Invalid
<<include>>
<<extend>>
Passward
ID: ENB-03
Title: Login of a User
Description: A User who is signed up already, log in to his/her Account to see Notice
Board.
Primary Actor: User
Preconditions: He should have sign up
Post conditions: He should have a valid registration number
Main Success 1. User clicks on sign in" button.
Scenario: 2. System displays username and password field.
3. User fills these fields.
4. User clicks "Submit" button.
5. System displays a student detail.
Extensions: May be User give wrong username and password then given error.
Frequency of Use: Each User used every time to see notices
Status: Pending Review
Non-functional
requirements:
Priority: Maximum priority
View Notice Request View Notices
student
ID: ENB-04
Title: Student view notice
Description: A User who is signed up already, log in to his/her Account to see
Notices on the Electronic Notice board(ENB)
Primary Actor: student
Preconditions: He should have sign in .
Post conditions: Student can view the notices on the system.
Main Success 1. User clicks on Notices" button.
Scenario: 2. System displays all the window which shows notices..
3. User select the notice.
5. System displays a detail.of the notice.
Extensions: May be User click on that notice is not available then given error.
Frequency of Use: Each User used every time to see notices
Status: Pending Review
Non-functional
requirements:
Priority: Maximum priority
View Notice request View notices
staff
ID: ENB-05
Title: Staff member view notice
Description: A user who is signed up already, log in to his/her Account to see Notices
on the Electronic Notice board(ENB)
Primary Actor: Staff
Preconditions: He/she should have sign in .
Post conditions: Staff can view the notices on the system.
Main Success 1. User clicks on Notices" button.
Scenario: 2. System displays all the window which shows notices..
3. User select the notice.
5. System displays a detail.of the notice.
Extensions: May be User click on that notice is not available then given error.
Frequency of Use: Each User used every time to see notices
Status: Pending Review
Non-functional
requirements:
Priority: Maximum priority
Post notice request post notices
staff
ID: ENB-06
Title: Staff member post notice
Description: A user who is signed up already, log in to his/her Account to see Notices
on the Electronic Notice board(ENB)
Primary Actor: Staff
Preconditions: He/she should have sign in .
Post conditions: Staff can view the notices on the system.
Main Success 1. User clicks on Post" button.
Scenario: 2. System displays post notice form.
3. User fill the form..
5. System displays a notice that stored in database.
Extensions: May be User put wrong values in form then given error.
Frequency of Use: Staff members used every time to post notices
Status: Pending Review
Non-functional
requirements:
Priority: Maximum priority
staff Edit notice request Edit notices
ID: ENB-07
Title: Staff member Edit notice
Description: A user who is signed up already, log in to his/her Account to see Notices
on the Electronic Notice board(ENB)
Primary Actor: Staff
Preconditions: He/she should have sign in .
Post conditions: Staff can view the notices on the system.
Main Success 1. User clicks on Search" button that notice he/she want edit.
Scenario: 2. System displays the notice.
3. User Edit the Notice
4. Press submit button
5. System displays message Edited successfully
Extensions: May be User put wrong values in form then given error.
Frequency of Use: Staff members used every time to post notices
Status: Pending Review
Non-functional
requirements:
Priority: Maximum priority
Manage Notices
Administrator
ID: ENB-08
Title: Manage Notices
Description: He/she is the person who can manage the data.
Primary Actor: Administrator (male or female)
Preconditions: Any person who is higher by the university
Post conditions: A person who is higher by the university can be entering, deleting and
updating the data from the system
Main Success 1. Administrator first sign in
Scenario: 2. System displays list of notice types.
3. Administrator Manage the notice from that notices list.
4. Administrator clicks "Submit" button.
5. System displays a confirmation message.
Extensions: May be some notices are not available in the list.
Frequency of Use: Most of the time used
Status: Pending Review
Non-functional
requirements:
Priority: Maximum priority
Update Notices
Administrator
ID: ENB-09
Title: Update Notices
Description: He/she is the person who can Update the Notices.
Primary Actor: Administrator (male or female)
Preconditions: Any person who is higher by the university
Post conditions: A person who is higher by the university can be entering, deleting and
updating the data from the system
Main Success 1. Administrator first sign in
Scenario: 2. System displays list of notice types.
3. Administrator filled the notice form that will select.
4. Administrator clicks "Submit" button.
5. System displays a confirmation message.
Extensions: May be Admin put some wrong values system shows error.
Frequency of Use: Most of the time used
Status: Pending Review
Non-functional
requirements:
Priority: Maximum priority
Edit Notices
Administrator
ID: ENB-10
Title: Edit Notices
Description: He/she is the person who can Edit the Notices.
Primary Actor: Administrator (male or female)
Preconditions: Any person who is higher by the university
Post conditions: A person who is higher by the university can be entering, deleting and
updating the data from the system
Main Success 1. Administrator first sign in
Scenario: 2. Admin clicks on Search" button that notice he/she want edit..
3. System displays the notice.
4. Admin Edit the Notice
5. Press submit button
6. System displays message Edited successfully
Extensions: May be some notices are not available in the list.
Frequency of Use: Most of the time used
Status: Pending Review
Non-functional
requirements:
Priority: Maximum priority
Administrator Delete Notices
ID: ENB-11
Title: Delete Notices
Description: He/she is the person who can Delete the Notices.
Primary Actor: Administrator (male or female)
Preconditions: Any person who is higher by the university
Post conditions: A person who is higher by the university can be entering, deleting and
updating the data from the system
Main Success 1. Administrator first sign in
Scenario: 2. Admin clicks on Search" button that notice he/she want Delete.
3. System displays the notice.
4. Admin Delete the Notice
5. Press submit button
6. System displays message Deleted successfully
Extensions: May be some notices are not available in the list.
Frequency of Use: Most of the time used
Status: Pending Review
Non-functional
requirements:
Priority: Maximum priority
Administrator Assign Roles
ID: ENB-12
Title: Assign Roles
Description: He/she is the person who can Assign the Roles to the User.
Primary Actor: Administrator (male or female)
Preconditions: Any person who is higher by the university
Post conditions: A person who is higher by the university can be entering, deleting and
updating the data and assigning the roles from the system
Main Success 1. Administrator first sign in
Scenario: 2. Admin clicks on Roles" button.
3. System displays the all user.
4. Admin Assign the roles to the user.
5. Press submit button
6. System displays a confirmation message.
Extensions: May be user not exist.
Frequency of Use: Most of the time used
Status: Pending Review
Non-functional
requirements:
Priority: Maximum priority
User Logout
ID: ENB-13
Title: Logout
Description: A User after using the services must logout to the system.
Primary Actor: student
Preconditions: He should have sign in .
Post conditions: Then logout to the system.
Main Success 1. User clicks on Logout" button.
Scenario: 2. System displays the sign in window to the user.
Delete
Update
Check register
<<include>>
Signup
<<extend>>
Student
invalid
Password
Login
STAFF
Notices
UserName
Sequence Diagrams:
Login Database
: User
check username/Password
Success/Failure
Success
View Request
View Notices
Responce
Success
Post Request
Post Notices
Insert
Success Responce
Edit Request
Search Notices
Display
Edit
Return
Success
Update Request
Update notice
return
Success
Edit Request
Search Notices
Display
Edit
Return
Success
Delete Request
Search Notices
Display
Delete
Success
Take Input
NO
Validate
Yes
Login
NO
User exist
Yes
View
Notice
NO
is updated
Yes
Record
Updated
Search
record
NO
if found
Yes
Edit
Record
Edit another
record
NO
Search
record
NO
if found
Yes
Record
Deleted
Delete another
record
NO
Session
close
<<device>>
Application server
<<Execuation Envoirnment>>
OS XP <<Device>>
database server
<<Database system>>
<<Process>> after verifying
<<login>> Oracle
authentication the user
user
<<JDBC>>
<<User data>>
Notices
<<view Notices>>
Notice
Component Diagram:
Update
Administrator
Edit
Staff
Database
Delete
Student
Login
Verifying
View
Notices
Class Diagram: