Washera Broadview College

Department of Computer Science

Industrial project on
Washera Broadview College Online Notice Board system
Group Member’s
Name ID NO
1. Bekalu Tsegaw CSE/048/10
2. Dagnachew Kumie CSE/103/10
3. Beza Adamu CSE/050/10
4. Kassahun Yeshanew CSE/061/10
5. Simegnish Sewnet CSE/077/10
6. Getnet Bitew CSE/095/10

Advisor:Mr.Yazachew Enyew(BSC)
2013 E.C
Debre Markos, Ethiopia
 CERTIFICATE
I certify that this BSc industrial project entitled << Washera Broadview College Online Notice
Board system >> by:

Name Signature

Bekalu Tsegaw
Dagnachew Kumie
Beza Adamu
Getnet Bitew
Kassahun Yeshanew
Simegnsh Sewnet

is approved by me for submission. I certify further that, to the best of my knowledge, the report
represents work carried out by the students.
____________________ ____________________
Date Mr.Yazachew Enyew
Examining committee members’ Signature

1.

2.

3.

It is approved that this project has been written in compliance with the formatting rules laid
down by the university.
 DECLARATION

This is to declare that this project work is done under the supervision of Mr.Yazachew Enyew,
and having the title << Washera Broadview College Online Notice Board system >>is
contribution of:
1. Bekalu Tsegaw CSE/048/10
2. Dagnachew Kumie CSE/103/10
3. Beza Adamu CSE/050/10
4. Kassahun Yeshanew CSE/061/10
5. Simegnish Sewnet CSE/077/10
6. Getnet Bitew CSE/095/10

No part of the project work has been reproduced illegally (copy and paste) which can be
considered as plagiarism. All referenced part has been used to argue the idea and have been cited
properly. The project team will be responsible and liable for any consequence if violation of this
declaration is proven.
Date: __________________
Group members:
Full name Signature
1. Bekalu Tsegaw ______________________________________
2. Dagnachew Kumie ______________________________________
3. Beza Adamu ______________________________________
4. Kassahun Yeshanew ______________________________________
5. Simegnish Sewnet ______________________________________
6. Getnet Bitew _______________________________________
 ACKNOLEDGEMENT
Any accomplishment requires the blessing of the God. This work is not any different to that. So
the first thanks goes to God!!! Secondly, Advisor Instructor Yazachew Enyew who gave
sounding advice help us guide this project in the right direction, in which he enforce us to have a
massive knowledge about the project to easily familiarize with the concept of project
development.
Thirdly, the project team would like to thank s to Washera Broadview college Stuff members and
teachers
Especially Mr.Zelalem(MSC) for their full willingness of interview, interest in answering to
project team numerous questions, telling how existing system work to better know the system.
Finally we would like to forward our special thanks to computer science Students for their guide
to develop our project.

Contents
CERTIFICATE.............................................................................................................................................................................. I
DECLARATION.......................................................................................................................................................................... II
ACKNOLEDGEMENT.............................................................................................................................................................. III
ACRONFYMS AND ABBREVIATION....................................................................................................................................VI
ABSTRACT................................................................................................................................................................................ VII
CHAPTER ONE............................................................................................................................................................................ 9
1.1 INTRODUCTION.................................................................................................................................................................... 9
1.2 ORGANAIZATION BACKGROUND.................................................................................................................................10
1.4 STATEMENT OF THE PROBLEM...................................................................................................................................11
1.5 TEAM COMPOSITION....................................................................................................................................................... 11
1.6 OBJECTIVE OF THE PROJECT.......................................................................................................................................12
1.6.1 GENERAL OBJECTIVE...................................................................................................................................................12
1.6.2 SPECIFIC OBJECTIVE.................................................................................................................................................... 12
1.7 FEASIBILITY OF THE PROJECT.....................................................................................................................................13
1.7.1 OPERATIONAL FEASIBILITY.......................................................................................................................................13
1.7.3 ECONOMICAL FEASIBILITY........................................................................................................................................14
1.7.4 LEGAL FEASIBILITY...................................................................................................................................................... 14
1.7.5 TECHNICAL FEASIBILITY............................................................................................................................................14
1.8 SCOPE OF THE PROJECT AND LIMITATION OF THE PROJECT..........................................................................15
1.8.1 SCOPE OF THE PROJECT.............................................................................................................................................15
1.8.2 LIMITATION OF THE PROJECT..................................................................................................................................15
1.9 SIGNIFICANCE OF THE PROJECT................................................................................................................................15
1.10 TARGET BENEFICIARIES OF THE PROJECT............................................................................................................16
1.11 METHODOLOGY FOR THE PROJECT........................................................................................................................16
1.11.1 DATA COLLECTION METHODOLOGY....................................................................................................................16
1.11.2 SYSTEM ANALYSIS AND DESIGN METHODOLOGY............................................................................................17
1.11.3 CASE TOOL....................................................................................................................................................................17

1.11.5 Testing procedures..................................................................................................................18

1.13. COST SCHEDULE............................................................................................................................................................. 19
1.13.1 HARDWARE COST......................................................................................................................................................... 19

Total..................................................................................................................................................19
11,012 birr.........................................................................................................................................19
CHAPTER 2................................................................................................................................................................................. 20
DESCRPITION OF THE EXISTING SYSTEM.......................................................................................................................20
2.1 INTRODUCTION OF THE EXISTING SYSTEM.............................................................................................................20
2.6.1. TO ELIMINATE WASTAGE OF TIME AND ENERGY..............................................................................................23
2.6.2.TO AVOID DUPLICATION AND OVERLAPPING......................................................................................................23
2.6.3. TO ENSURE DUE ATTENTION OF STUDENT TO EACH AND EVERY NOTICE................................................23
2.7 REQUIREMENT ANALYSIS OF NEW SYSTEM............................................................................................................24
2.7.1 FUNCTIONAL REQUIREMENTS...................................................................................................................................24
2.7.2 NON-FUNCTIONAL REQUIREMENTS.........................................................................................................................25
CHAPTER 3................................................................................................................................................................................. 26
ANALYSIS OF THE NEW SYSTEM........................................................................................................................................26
3.1 INTRODUCTION.................................................................................................................................................................. 26
3.2 DESIGN & STEPS.................................................................................................................................................................27
3.3 USE CASE DIAGRAM........................................................................................................................................................29
TABLE REGISTRATION USECASE DESCRPITION...........................................................................................................32
TABLE: CHANGE PASSWORD USECASE DESCRPITION................................................................................................33
TABLE: VIEW NOTICES USECASE DESCRPITION...........................................................................................................34
TABLE: UPDATE NOTICE USECASE DESCRPITION........................................................................................................37
TABLE: UPDATE PROFILE USECASE DESCRPITION......................................................................................................38

3.5 Activity Diagram.........................................................................................................................38

3.7 DATA FLOW DIAGRAM:..................................................................................................................................................48

3.8 User Interface Design......................................................................................................................48

3.10.1 DESIGN PROCESS..........................................................................................................................................................51
3.11 DEPLOYMENT DIAGRAMS............................................................................................................................................52

4.3 Logic model Design.........................................................................................................................57

List of Figure
Figure 1 Physical Notice Board.................................................................................................................22
Figure 2 Notice Protocol Form..................................................................................................................22
Figure 3 Notice Protocol Sample...............................................................................................................23
Figure 4 Usecase Diagram.........................................................................................................................30
Figure 5 Login Usecase activity Diagram..................................................................................................39
Figure 6 Create Account Activity Diagram..............................................................................................39
Figure 7 Update Profile activity Diagram..................................................................................................40
Figure 8 View Notice activity Diagram.....................................................................................................40
Figure 9 Create Notice Usecase activity Diagram.....................................................................................41
Figure 10 Update Notice Usecase activity Diagram..................................................................................41
Figure 11 Delete Notice Usecase activity Diagram...................................................................................42
Figure 12 Feedback Usecase activity Diagram..........................................................................................42
Figure 13 Update Password Usecase activity Diagram..............................................................................43
Figure 14 Login Sequence Diagram..........................................................................................................44
Figure 15 View Notice Sequence Diagram................................................................................................45
Figure 16 Create Account Sequence Diagram...........................................................................................45
Figure 17 Create Notice Sequence Diagram..............................................................................................45
Figure 18 Delete Notice Sequence Diagram..............................................................................................46
Figure 19 Update Notice Sequence Diagram.............................................................................................46
Figure 20 Update password sequence diagram..........................................................................................47
Figure 21 feedback Sequence Diagram.....................................................................................................47
Figure 22 Data flow Diagram....................................................................................................................48
Figure 23 User Interface Design...............................................................................................................49
Figure 24 Component Diagram.................................................................................................................50
Figure 25 Sample Database Design...........................................................................................................52
Figure 26 Deployment diagram.................................................................................................................53
Figure 27 Class Diagram...........................................................................................................................56

ACRONFYMS AND ABBREVIATION

Admin: Administrator
CSS: Cascaded style sheet
DB: Database
DBMS: Database Management System
ID: Identification number
HTML: Hyper Text Markup Language
HTTP: Hyper Text Transfer Protocol
MySQL: My Standard Query Language
OOD: Object oriented design
OS: Operating system
OTP: One Time password
SQL: Structured Query Languge
UC: Use Case.
UI: User Interface
UML: Unified Modeling Language.
 WBVC: Washera Broadview College

Abstract

This project aims to develop online Notice Board system for Washera Broadview College. The
Notice Board system is web-based system that can be accessed through out the internet and can
be accessed by registered users to view notices . In the system Special Privileged user will only
publish notices. The system also report number of visitors and notify specific person
privately .The existing system uses only post on physical board, however it’s difficult to share
Notices from college to multiuser environment. This online Notice Board system is simplified
the publishers time, cost and also it will automate the accessibility of notices.

An online notice board is a place where people can leave any types of messages and
notifications announce events or provide any information. Notice board online it can be placed
on digital devices such computers, tabs, mobile phones etc. This online notice board project is
very helpful for all type of users like existing users and new users. So admin can leave and erase
notification for other people to read and see. The main aim of this online notice board project is
make information much easier in a paperless community as the community tends to interact with
the online notice board facility as an project, Online notice board admin can send the notification
to the particular students, results, any new activity happen in college for this work online notice
board project is make all work much easier and understandable to all.
 CHAPTER ONE
1.1 INTRODUCTION
A Notice Board is a traditional tool for the dissemination of information in academic campuses.
A traditional Notice board is made of a wooden frame with a soft central square of cork for
pinning the papers of information for the students .In any College there is a lot of on wall notice
boards placed on different location where by people with their announcements type on a sheet of
paper and place it on the notice boards for other people to read when passing through those
notice boards. Thus there is a lot of accumulation of papers due to carelessness of people who
place them and no one who is responsible for removing it. And hence there is a lot of strain on
the people who having announcements in hand by making sure that the announcements are
placed everywhere, all these comes because the software is not used in this context.

The Online Notice Board System is intended for washera colleges where information and file
sharing on regular basis plays vital role in the performance. The proposed system will act as an
online notice board which will make use of the modern communication methodologies and
techniques for information flow. The system is planned to consist of various useful features for
the said purpose. The proposed system aims to create a platform for issuing notice, sharing
information and files between the members of the institution. Different users shall have different
level of access to the content. In the context of Washera College, there shall be four users of the
system:-system – administrator, student, teachers and guest. The administrator shall be able to
issue notice, upload files, and view students’ activities on the system. With the diversity of
technologies available, finding the most convenient server software and programming language
to develop a website is always an area of concern. Even more, implementing an online notice
board requires more than just a fast accessible website, but also, one that supports concurrent
views, and changes to the notice board seamlessly.
1.2 Organaization Background
Washera Broadview college is one of the colleges which have served its customers in Debre
Markos town. The college is found in Debre Markos town and it was established in 1996 E.C.
When the college was established it consists around four departments such as Low,Accounting
,Secretary and Marketing. At that time the college starts the work with 91 employees which
perform different activities within the college. Starting from 1996 the college have started to
accept students in the above four departments and start delivering the courses in each
departments according to the students need of educational profession and it have started to
graduate students from their departments according to their result .
The college gives courses to students by categorizing the level of study starting from level one
up to level four. The levels are categorized according to the number of courses which should be
taken within the department that means numbers of courses to be taken by level one students are
very different from a student who take level four in number as well as by the contents of the
course. So students who need to study level two programs stay one years of study in the college
and students who need to study level four stay three years of study in the college.
In 2010 the number of departments has been raised to eight departments by adding four
departments by degree which are Business and Technology it includes Computer
Science,Information Technology,Accounting and Management . Now a day in the college
distinct departments which have their own staffs which accepts students as the students interest
and the organization now have 32 employees who performs different activities within the
organization and the organization now have different offices such as departments offices, college
dean office, human resource management office, Registrar office and other offices.

1.2.1 Mission
Washera Broadview College have a mission Based on New education policy and carriclum give
quality education and training to contrbute ethical and enterprener man power.

1.2.2 Vision
Washera Broadview college have a vision In Amhara Region upto all over Ethiopia Look
Enough and sopesticated citizens with using sience and technology look qualified manpower in
every economic subsystem and make free from poverity and also look prosperity ethiopia.

1.3 Background of the project

Notice Board System is a system that used to notify users for different tasks there are many types
of notices like auction , vacancy , advertisement , urgent and more. The main purpose of notice is
to notify users to do some action in the organization. This notice board system simplify notice
owner work load and customers can view notices easily by using internet in everywhere. Now a
day every thing is in internet most medias target is advertisement the major task of notice also
advertisement so the organization can boost their business by using this notice system.
In this system the admin can post notice for specified user and also can send for particular users
by using their privilege. To view notices unless public notice they need register in the system and
then login before access the notice. When users register on the system by default their privilege
is user and then system administrator can assign new privilege for registered users and also can
register new users in the system. to login the system simply fill email and password field and
submit the login form.

1.4 Statement of the Problem

In today’s world, everything is digitalized and paper is being used less and less every day. How
often has it happened that we miss some important notice because we have to go to a wall and
read the notice there? The proposed system is such a system. In the college or institutions there
are many problems, distinguish is between rumor and true information. In case of an Online
Notice Board students will have access to important announcements while walking around
anywhere or not having in the campus and have the benefit of being reminded several times a
day.

To develop a web application that will help us receiving the notices from the college, anywhere,
anytime. Earlier there was problem that notices were posted on notice board.If there is holiday
on the next day, nobody will be able to read it and also The following are some problems in the
current system.

 Lack of Security (When College want to announce someone securly that

is deficult)
 Data is not easily accessible based on securiy.
 Cost in terms of time was high.
 When Users Want to view Botice Remotly that is Defficult.
 High vernelable to damage by anonymus before Deadline of notice then targeted user
may not read.
 Notice may damage by wind or rain.

1.5 Team Composition

S.No Name ID NO. Email Address Responsibilities

bekalutsegaw@gmail.com -V/group Coordinator

1. Bekalu Tsegaw CSE/048/10 -Testing
-Designer

-Data gathering
2. Dagnachew Kumie CSE/103/10 kumieebe@gmail.com -Designer
-

Beza Adamu CSE/050/10 - -Data gathering

3.

4. Kassahun Yeshanew CSE/061/10 - -Data gathering

5. Simegnsh Sewnet CSE/077/10 - -Designer

6 Getnet Bitew CSE/095/10 Designer

Project Advisor: Mr. Yazachew Enyew(BSC)

Table 1.5Project Team composition

1.6 Objective of the project

1.6.1 General Objective

The general objective of our project is to develop Web based Notice Boardsystem For
Washera Broadview College .

1.6.2 Specific objective

Our specific objective regarding to our project is that
 To design registration form.
 To register users.
 To view users
 To create user account.
 To develop a user friendly interface.
 To Create Delete and Update Notice
  To Update Users Profile
 To Delete Users using Admin Account
 To View Notice
 To Search Notices.

1.7 Feasibility of the project

The main objective of feasibility study is to analyze the Technical, Operational Economical and
legal feasibility for adding new modules and debugging old running system. All system is
feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study
portion of the preliminary investigation.
 Technical Feasibility
 Schedule feasibility
 Operation Feasibility
 Economical Feasibility
 Legal feasibility

1.7.1 Operational feasibility

Operational feasibility refers to does the proposed system meet the organization’s operating
requirements. Operational feasibility aspects of the project are to be taken as an important part
of the project implementation. Some of the important issues raised are to test the operational
feasibility of a project includes the following: -
 Is there sufficient support for the management from the users?
 Is the system used and work properly if it is being developed and implemented?
Is there any resistance from the user that undermines the possible application benefits?
So the new system is operationally feasible because the system works properly the tasks
required.
1.7.2 Schedule feasibility
Time
March 10-

March 30-
March 01-

April 17-
March 25

May 20 -

Activities
April 15

May 17

May 23

Jun 20-
Jun 26

Project Proposal

Requirement Analysis

Design

Implementation & Coding

Testing
project Defense

1.7.3 Economical feasibility

In the economical feasibility, the development cost in creating the system is evaluated against
the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the
costs.
The system is economically feasible. It does not require any addition hardware or software.
Since the interface for this system is developed using the existing resources and technologies.
Organization manager gives some what the required information’s about what their work seems
like.

1.7.4 Legal feasibility

Legal feasibility refers to does the proposed system does have any controversial issues, does it
have any considerations which oppose the government and institutional rules and regulations. i.e.
 Assessment of legal and institutional framework
 Does the system take the legal risks resulted from it.
 Determines whether the proposed system conflicts with legal requirements

The new developed system is legally feasible because there is no any action that contradicts
government policy and strategy. It is not against government rather it support it.

1.7.5 Technical feasibility

The technical issue usually raised during the feasibility stage of the investigation includes the
following:
 Can a system be supported with the existing technology or not?
 Is the project possible with current technology?
 What technical risk is there?
 Does the necessary technology exist to do what is suggested?
 Do the proposed equipment’s have the technical capacity to hold the data required to use
the new system?
 Is the proposed system providing adequate response to inquiries, regardless of the
number or location of users?
 Can the system be upgraded if developed?
 Are there technical guarantees of accuracy, reliability, ease of access and data security?
 So the project developed is technically feasible because the system is supported by existing
technology and no technology is required to apply the system, there are technical guarantees for
the system and it provides adequate response to queries made by users.

1.8 Scope of the project and limitation of the project

The proposed system will have the following scope and limitation.

1.8.1 Scope of the project

Our project is going to implement in Washera Broadview College online Notice Board and the
system boundary includes Targeted College Announcements view by Registered Users and
Public Notices View by Any registered or UN registered User in the system

Generally, our project scope include

 The system enables students to view Announcements

 Teachers and Stuff Members can view their individual Notices
 Public Notices can View By Unregisted users.
 Users Should register in the system to view Unpublic notices
 The administrator has an authority to Post, Delete and Update Notices.

1.8.2 Limitation of the project

1. There is a lack of security to verify users authenticate by using phone number OTP(one
time password).
2. Anyone can register in the system then there maybe scammers treat the system or they
may create fake account.
3. There is a lack of responsiveity.
4. When users want to delete account they can not delete and restore it.
5. System haven’t Responsive languge. Example. Can not convert to amharic
6. There is a lack of security to verify users using their email address by sending Email
confirmation.

1.9 Significance of the project

The system:

 Post Urgent notices for Students.

  Notice stuff Members and to Call new Employers.
 Vacancy and census can post on page
 Registered Members can view Notices.
 Reduce the manual work, time and cost to be consumed.
 Reduce more cost spending on papers and some other materials needed for the whole
entire system.
 Improving accuracy of file management system.
 Provide online access for student notices
 Users Can view How much Time remind for notice
 System provide How many Users view Notices for System admin

1.10 Target beneficiaries of the project

Users
 Save Money: users can view notices remotely by using internet then they can save
noney from extra transport cost.
 Save Time: users can save time by using this system because they do not need to go in
the organization physical notice board, simply access the system using internet and
save their time.
 Save energy: users they don’t need to loose energy to view notice simply access the
system in anywhere using internet.

Organaization/College
 Save Money: when college want to notify their customer they need post many notice
for specific notice but when use this system they can save money from extra paper
cost.
 Save time: the organization can save time by publish notices in this system simply
post notice in the office using internet no need get out to publish notice.
 Save from work load & complexity: This system design using many automation
algorithms then simply system admin can record and publish notices and accessible In
any where.

1.11 Methodology for the project

1.11.1 Data collection Methodology

The data collection instruments used to gather accurate information about the existing system
and the requirements for the new system. Interviews were administered to Stakeholders like
College Dean Mr. Zelalem(MSC).
To get a precise data, the team member has used the following data collection techniques.
Those are: -
 A. Interview: - to get the basic information and background information about the existing
management system, the team members has interviewed the Dean Mr Zelalem about the
services that are given to them, and the problems associated with that environment.
B. Direct observation: even though interview is very important to gather information,
direct observation is simple and we project team members physically observe information
about how the current system works.
C. Existing document: To get more information about the project we use earlier documents
that help us to develop the project also we check the current Physical notice board
system. During the analysis of documents, we give a special consideration to those
documents which can bring more features to the project.
D. Quastionaries: To Get more information about the currecnt system and to implement in
new system we use some quastionaries for washera college stuff memebers like registrar
Lingerew shitaye and department head Temesgen Lake.

1.11.2 System analysis and design Methodology

Here for the analysis of our project we have selected object oriented system analysis and design
method specifically UML (Unified Modeling Language) model. We have selected this because
of the following advantages:-
 To simplify the design and implementation of complex program.
 To make it easier for teams of designers and programmers to work in a single software
project.
 To enable a high degree of reusability of designs and of software codes.
 To decrease the cost of software maintenance.
 Increase reusability.
 Reduce maintenance burden.
 Increased consistency among analysis, design and programming activities.
 Improved communication among users, analysis, design and programming.

1.11.3 Case tool

While developing the project starts from the documentation to the implementation we use the
following case tools:
Activities Tools

Documentation MS word 2007,2010

Design for UML standard design edraw max

Editing Paint, Macro media flash 8,Adobe.Photoshop.CS4

Script languages PHP, JavaScript, CSS, HTML,SQL

Web server Apache Wamp server

Data base Server MYSQL database

Table 1.1 Tools used in the project

1.11.5 Testing procedures

The Notice Board System will be tested using the following system testing procedures.
Unit Testing: - Each module will be test separately and often performed by the coder himself
simultaneously along with the coding of the module. The purpose is to exercise the different
parts of the module’s code to detect coding errors.
Integration Testing: -The modules will be gradually integrated into subsystems, which are then
integrated to eventually to the entire system. Integration testing will be done to detect design
errors by focusing on testing the interconnection between modules.
System Testing: - After the system is put together, it will be performed. The system will be
tested against the system requirement to see whether the entire requirements meet and whether
the system performs as specified by the requirement.
Acceptance Testing: - will be carried out by the customer to ensure that the delivered product
meets the requirement and works as the customer expected. It includes
Alpha testing – conducted by users to ensure they accept the system with sample data.
Beta testing – conducted by users with real data, not test data.

1.12 Risk and contingencies

During the development of the project there may be different problems that we may face. These
are:
 Time management problem: all group mambers have a lack of time to meet,descuss and
work together then we devide tasks of project for each member and then we meet every
important meetings.
 There is a lack of internet and computer in college then we ask adviser yazachew and he
help us by by giving his computer to use internet.
 There was a problem to find necessary software to download or to find in case of lack of
internet and then we find some software like edraw max from our classmate friends.
1.13. Cost schedule

1.13.1 Hardware cost

No Material Amount Price per unit Total price

1 A4 size paper 1 Destin 100 Birr 100Birr

2 Pen 3 8 Birr 24Birr

3 Flash disk 1 240 Birr 240Birr

4. For Print 100 sheet 1 Birr 100Birr

5 CD 6 8 Birr 48 Birr

6 HP Laptop 1 12,500 Birr 10,500 Birr

Total 11,012 birr

Table 1.3Hardware cost in the project

1.13.2 Software cost

No Material Price per unit

1 Microsoft office 2007 Free

2 Microsoft office 2010 Free

3 EdrawMax Free

4 Wamp server Free

5 Sublime Free

Total 00.00 Birr

Table 1.4 Software cost in the project

 Chapter 2
DESCRPITION OF THE EXISTING SYSTEM
2.1 Introduction of the Existing System
The existing notice board made from wood and chipwood also they used roof to prevent from
rain and there is another notice board made from metal both physical notice boards are
traditional and when notices expired no one care about expired notices to remove it.
Currently our college has manual system of putting notices on notice board. It’s outdated now.
As nobody has a time to stand in rush in order to read the notices on notice board. The
limitations of the existing system are following:
2.1.1.Order of Data: Notice can get out of order in traditional notice board system. If someone
accidentally puts some data in the wrong place, it can lead to lost data. Automated notice
management systems allow users to quickly check whether information already exists
somewhere in the system, which helps avoid problems like redundant data.
2.1.2.Complexity: Automated system is less complex than manual system of handling notices,
which can make it easier for untrained people to access and manipulate data. Anyone having the
basic knowledge of mobiles can work on the automated system.
2.1.3. Inconsistency of data: There will be an unavailability for future use, since notice might
get misplaced during manual notices management. So notice won’t be preserved properly for
future use.
2.1.4. Damage: Manual notices stack are vulnerable to damage, destruction and theft in ways
that digital databases are not. A company may back up its digital data both on site and at offsite
locations ,ensuring its security if the office building suffered a fire or similar disaster. A manual
database, however, may only exist in one place without any copies. As a result, a manual
database would be very vulnerable to a fire or other natural disaster. In addition, while access
time in a manual database system, information must be found by hand rather than electronically.
While a digital database will typically allow users to search the entire database for specific
information in seconds ,someone looking for information in a manual system may have to spend
hours searching for a particular piece of data.
2.1.5. Editing and Communication Manual notices do not allow users to easily edit data or
information. Manual notices often cannot be edited directly, forcing users to make new copies.
To circulate notice on paper, users must require peons and other staff. Online Notice Board allow
users to edit information fields directly, and because data is stored digitally, it is already in a
form that can be easily transmitted.

2.2 Players In the Existing System

Actors in the existing system are
1 Registrar: College registrar have their own responsiblity to call students for registration and
also may announce the start date and deadline of student registration.
2 Department: department head also have their own responsiblity my be announce program
schedule for students and teachers.
3 Dean : the college dean have their own responsiblity to post vacancy in the current notice
board system.
4 Student: students only view notice in the existing system they don’t have action requirement on
the notice board system.

2.3 Major functions in the Existing System

There are 2 functions in the existing system
1 Notice authoriser post notice: Either Registrar ,Dean or department may create post for their
target audeince.
2 Notice audence take action based on the notice: students may be actors to view notice.

2.4 Business Rule in the Existing System

The Existing System Have The following Business rule
1. Notice Owner Have A protocol that used to record the index of every notice
2. Notice Must be have Published Date
3. In the notice It must have signature or seal of the notice authoriser
4. Noticce should post on notice board

2.5 Forms and Other Documents of the Existing System

2.5.1 Physical Notice Board

Figure 1 Physical Notice Board

2.5.2 Notice Protocol Form

Figure 2 Notice Protocol Form

2.5.3 Notice Protocol Sample

Figure 3 Notice Protocol Sample

2.6 Proposed System

After looking the current system and identifying all the problems occurred during over all
activities of the college,We recommended by our teachers to develop Notice board system to our
college and then we decide to develop it Our new proposed system will solve the problem and
limitation of the current system seen above. After developing the new system it is fully flagged
online at anytime, anywhere. The proposed system will use the major functionality of the
existing system and able to advance in accordance with speed, performance and efficiency with
respect to current system using new technologies. Proposed System will be able to do the
following:

2.6.1. To eliminate wastage of time and energy

Online Notice Board application will be able to save lot of paper and time. It directs both teacher
and pupil’s energy and attention to one thing at a time by placing proper persons at their proper
places at the proper time. Everything will be instantaneous.

2.6.2.To avoid duplication and overlapping

This application will help to remove the duplicity of notices. Only one person, who is admin can
post the notice. No one else would be able to do. So student and staff will be given correct
information all the time.

2.6.3. To ensure due attention of student to each and every notice

Online Notice Board application ensures that everyone has kind attention to every notice and
updates going on in college. There will be a buzz at each and every notice to drive the attention
of student to check it once. In this way, students will be well informed about their college
activities.
2.6.4. To bring system into college life It would be dire need of all colleges as it’s easy and
shortcut method to inform all the students. In the absence of proper notification system will make
it very difficult to inform students at right time.
2.6.5. Searching a particular Notice This application allows you search the notice very easily
through title of notice. If anyone forgets about the notice details, he can search it out very easily.
2.6.6. Free Service It gives free service to notify all the students. There will be no cost of
sending notification to all. Just have the good system implemented in college and that too free of
cost.
2.6.7. Prevent Crowd in College As you can see, there is always a crowd at notice board. As
notice board is one, and people to see notice are more. With this application there will be no
more crowd. Everyone will be well informed even at their homes. So they are free to do there
other work.
2.6.8. Automatically Updated Dashboard The dashboard of notice is automatically updated
when a new message arrives. The user can himself refresh the dashboard to see any new notice.
2.6.9. Anytime Anywhere Service With this application, notices will be delivered anytime and
at any place. There is no restriction of time to send a notice.
2.6.10. Keeping Notices at one place This application allow you to have notices in one place
only. If there is an attachment with that, all will be placed in a separate folder dedicated to that
application. So there will be no here and there of notices.

2.7 Requirement Analysis of New System

The purpose of requirement is used to prepare requirement specification before starting the
actual design. This enables the project team to have a clear idea about the structure and content
of the information system. This project is concerned within the functional requirements and non-
functional requirements.

2.7.1 Functional Requirements

Functional requirement explains and describes what things are performed by the system.
Describe user tasks that the system needs to support. Generally it’s the interaction between the
system and the users or functionality we are going to get from this system. Functional
requirements also capture the intended behavior of the system. This behavior may be expressed
as services.

 Updating: The admin will update information and users can update their password
and profile information.
 Privacy: Registered users can view their individual notice after login into their
account.
  Authorization: The system provides enough privilege to access and update the
recourses.
 Sorting: Users sort notices based on time or other periority.
 Registering: Users can register using their email once.
 Searching: users can search notices.
 Delete: System adminstrator can Delete either user accounts or Notices.

In our Proposed system they are some actors particiate on the system .
 Administrator: System administrator post notices for registered users and
gust users or for specified user like teachers,or other stuff members.
 Dean: College Dean Can post notice Either for specific user or for public.
 Registrar: Registrar there is their own privlage to post notice either for
specific user or for public.
 Department: Department Head also can post notice for specific user or for
public/
 Student: Students can registr and have the privlage to view notice.

2.7.2 Non-Functional Requirements

Non-Functional requirement explains and describes the user visible aspects of the system.
Constraints on the services or functions offered by the system are constraints of timing, the
development process; standards, etc. are things we have to focus on developing new systems to
achieve its functionality.
Non-functional requirements are requirements which specify criteria that can be used to judge
the operation of a system. This is contrasted with functional requirements that specify behavior
or functions.
 User Interface: This works as an interface between the user and the system by properly
guiding the user how to use it and perform operations. Any sort of training is not required for
using the system. It is important that the system is easy to learn. The input device is given to
keyboard and the output is viewed on the monitor.

 Performance is the ability of system to response quickly and optimal workload. Is how fast
(speed) of operation of a system. How much the system can accomplish within a specified
amount of time. time taken to do what is asked or response giving time and how quickly the
system reacts to a user input
 Error Handling: Our system handles the errors in a very efficient manner. It can tolerate to
wrong inputs and prompts the users to correct the inputs. It gives notifications as and when
required, guiding the users to properly utilize it.
 Security and Access permissions: Users of the system must be identified, authenticated and
authorized before having access to the system’s services. Users will have their own password
and username through which they could gain access to. When the users of the system interact
 with the system errors may appear. To control these inaccuracies the system will generate
different messages. When users of the system input wrong username or password, the system
responses failure message which tells them that either username or password is not correct.
 Availability: all data in the system will be available all the time if the internet is available
and the system contains redendent server to protect the down time of the system . So Users
can view Notices in every time (24 hours available per day).
 Response time: average reponse time of this system shall be less than 25 seconds.
 Capacity: The system accommodate allows concurent user to use.
 Efficiency: The system uses less time to retrive. Insert and modifying data.
 Easy to learn:The system can be learned with in 30 minutes who can read and write english.
 Maintainablity:the system is easy to modify and to add functionality without affecting the
general frame work of the system.
 Operating system: the system can be deployed in Windows OS or Linux OS.
 Accuracy: proposed system will be better due to reduction of error. All operation can be done
correctly and it ensures that whatever information is coming from the data base is accurate.

CHAPTER 3
ANALYSIS OF THE NEW SYSTEM
3.1 Introduction
System design is the process and focuses on decomposing the system into manageable parts.
During requirements analysis, we concentrated on the purpose and the functionality of the
system design. During system design, we focus on the processes, data structures, and software
and hardware components necessary to implement it. The challenge of system design is that
many conflicting criteria and constraints need to be met when decomposing the system. The
analysis model describes the system completely from the actors’ point of view and serves as the
basis of communication between the client and the developers. The analysis model, however,
does not contain information about the internal structure of the logical, its hardware
configuration, or, more generally, how the system should be realized. System design results in
the following products:
• List of design goals, describing the qualities of the system that developers should
optimize.
• Webpage architecture, describing the subsystem decomposition in terms of subsystem
responsibilities, dependencies among subsystems, subsystem mapping to hardware, and
major policy decisions such as control flow, access control, and data storage.

3.2 Design & steps

A design approach is general philosophies that may or may not include a guide for specific
methods .Some is to guide the overall goal of the design. Other approaches are to guide the
tendencies of the designer. A combination of approaches may be used if they don’t conflict.
Function Oriented Design Approach is partitioning of a design into subsystems and modules,
with each one handling one or more functions. Contrast with object-oriented design, data-
structure-oriented design .This application project uses function oriented design approach. Every
module and sub modules are made based on their functionality. These modules are designed and
implemented separately and then they are integrated together to form the desired application.

This web application contains Six types of user:

1. Admin
2. Dean
3. Registrar
4. Finance Management
5. Research and community Service
6. Club representatives
7. Department
8. Library
9. Student

Both the user are having different works. User has to check the notices and work on these
notices. Admin has a different work such as Add Notice, Delete Notice, and Update Notice Etc.
The working of both user and admin are described below:
3.2.1. User: The working procedure of user is described below:
3.2.1.1. Registering a User: The first step in this web application is to get the users registered to
the website. For this, user will provide all the necessary details such as Name, Email, ID No. etc.
and press the register button. After that, all the information along with registration id is stored on
Web Server and the user gets registered.
3.2.1.2.User Login: After registering, the user is allowed to log in. Username and password after
validating at client side, is sent to server side to authentication. After authentication response is
sent by the server to client, and then user gets logged in.
3.2.1.3. Viewing the Notices: At the first time, when you are using this application for the first
time, it will fetch all the notices from server. In all the other case, all previous notices are fetched
from application’s own database stored inside client mobile. It then checks for new notices from
the server. If there are new notices on the server, it will fetch all those notices.

3.2.1.5 Feedback: User can give feedback for College about their service
3.2.1.6 Searching a Notice: The user is able to search the notice in list view depending on the
title of the notice. It helps user to get the desired notice instantly.
3.2.1.5. Reset Password: This application also has the facility to reset the password. If one user
has forgot his password, he/she can rest the password by giving his username or email address.
The user will be given a page in which he can set his new password. Forgotten password will be
updated with the new one on the server.
3.2.2 Admin: The working of admin is described following:
3.2.2.1 Add Notice: Being an admin, the most important work is to add the notice on the online
notice board. Since the right of adding notice to the web application is only at the admin, hence it
is very important to be sincere in performing this work. Any type of small mistake can create
some big issues.
3.2.2.2 Delete Notice: An admin can perform too many work on this web application and delete
notice is one of them. If a notice is useless i.e. the time has been passed for that notice then the
admin can delete that notice.
3.2.2.3 Update Notice: Updating the notice is not a primary work of admin but sometimes as per
the requirements it is important to update any notice.
3.2.2.4 Create User Account: System adminstrator have a previlage to create user account
3.2.2.5 Update Profile: System Adminstrator can modify their profile information

3.3 Use Case Diagram

Use Case represents interaction between a user (human or machine) and the system.
Use case components:-
 Actor: is a person, or external system that plays a role in one or more interaction with the

system .
 Use case: describes a sequence of actions that provides something of measurable value to
an actor.

 System boundary: indicates the scope of the system project. Anything within the box
represent functionalities in side in scope.
Figure 4 Usecase Diagram

Use case name LOGIN

Identifier UC1

Description 1. To authenticate the any system user, system request

login action and thenthey can access their privlage.
Actor System Admin,Registrar,Library,Department.Dean,Research
and Community Service,Club Represenatatives,Finance and
Student

Pre-condition The user should have an account.

Post-condition The authenticated user gets the appropriate page.

User gets access to the system according to their predefined
system privilege and

Finally the user can logout or turn off the page.

Step1: Select the login link

Flow of event step Step2: The system displays the login form
Step3: Fill Email and password
Step4: system validates Email and password.
Step5: The system displays the appropriate page.

Alternative flow If user Email and password are incorrect

Return Back to step 2 in flow event

3.4 Usecase Descrpition

Table: Usecase descrpition of login

Use case name Register/Create Account

Identifier UC2

Description 1. Users Can create account by Entering valid

information
2. Users can update their account
3. System admin can add new account for users with
previlage

Actor System Admin and Student

Pre-condition Users should enter valid information to create accont.

System admin should have to enter a valid user name and
password in order to create, update and delete user account.

Post-condition You update, create and delete user account successfully

message will be displayed.
Finally page will redirect to login page.
For Users

Flow of event step 1 click Create account link from home page

2 System display registration page

3 users enter valid information

4 submit form

5 Display Registration Successfull information

For admin

1.Login to admin control panel

2. Select Add User Link

3. Registration form Display

4, Admin Enter User valid information

5 Submit form

6 Display successfull Information

Alternative flow Confirmation/rejection message will be displayed.

Table Registration usecase descrpition

Use case name Change Pssword

Identifier UC3

Description Users or Admin Can change Password after login their

account
Actor System Admin,Registrar,Library,Department.Dean,Research
and Community Service,Club Represenatatives,Finance and
Student

Pre-condition Users Should Login Firest.

Post-condition After Chanege password it should display Show message

Password change Successfully

Step1: Login
Flow of event step Step2: Click Chanege password
Step3: Enter New Password
Step4: Submit New Password
Step5: Show “Password Changed Successfully.” Message

Alternative flow Forget password option

Return bake to step 2 in flow event

Table: Change password Usecase Descrpition

Use case name View Notice

Identifier UC4

Description Users After Login in their account Can view Notices unless
puplic Notice
Actor System Admin,Registrar,Library,Department.Dean,Research
and Community Service,Club Represenatatives,Finance and
Student

Pre-condition The user should have an account and Login Firest unless
puplic Notice

Post-condition User gets access to the system according to their predefined

system privilege and

Finally the user can logout or turn off the page.

Step1: Login To account

Flow of event step Step2: Click Notices
Step3: System Display List of Notices with Approprate
Information

Alternative flow Users can view Puplic Notices Without Login

Table: View Notices Usecase Descrpition

Use case name Create Notice

Identifier UC5

Description System Admin,Registrar,Library,Department.Dean,Research

and Community Service,Club Represenatatives and Finance
Can Create Notice After Login System
Actor System Admin,Registrar,Library,Department.Dean,Research
and Community Service,Club Represenatatives and Finance

Pre-condition Users Should Login Firest.

Post-condition System Should Display Message “Notice Created

Successfully”

Step1: Login To Dashboard

Flow of event step Step2: Click Create Notice Link
 Step3: System Display Notice Form
Step4: Enter Valid Notice Information And Submit
Step5: System Should Display Message “Notice Submited
Successfully”

Alternative flow The Only Option to create option Is the above Step

Table Create Notice Usecase Descrpition

Use case name Feedback

Identifier UC6

Description Users Can Give Feedback about Notices by Submiting

Feedback Form
Actor Students

Pre-condition Users Should Login Firest.

Post-condition After Submiting Freedback the system Should Display

Feedback submited Successsfully

Finally the user can logout or turn off the page.

Step1: User Login in their Account

Flow of event step Step2: Click View Notices
Step3: Below the page Give Feedback Link click it
Step4: System Diplay Feedback Form.
Step5: User Fill Feedback form and Submit
Step 6: System Display Feedback Submited Successfully.

Alternative flow The above Option is only way to give feedback

Table: Feedback Usecase descrpition

 Use case name Delete Notice

Identifier UC7

Description System Admin,Registrar,Library,Department.Dean,Research

and Community Service,Club Represenatatives and Finance
Can Delete Notice After Login in the System Dashboard
Actor System Admin,Registrar,Library,Department.Dean,Research
and Community Service,Club Represenatatives and Finance

Pre-condition Users Should Login Firest.

Post-condition The authenticated user gets the appropriate page.

User gets access to the system according to their predefined
system privilege and System
Admin,Registrar,Library,Department.Dean,Research and
Community Service,Club Represenatatives and Finance can
Delete Notice

Finally Session User can logout or turn off the page.

Step1: Login To Dashboard

Flow of event step Step2: Click Notices Link
Step3: Select Notice
Step4: Click Delete .
Step5: System Disply Notice Deleted Succesfull Message.

Alternative flow The above option is the only way to delete notices

Table: Delete Notice Usecase Descrpition

Use case name Update Notice

Identifier UC8

Description System Admin,Registrar,Library,Department.Dean,Research

and Community Service,Club Represenatatives and Finance
Can Update Notice Information After login to Dashboard.
Actor System Admin,Registrar,Library,Department.Dean,Research
and Community Service,Club Represenatatives and Finance

Pre-condition Users Should Login Firest.

Post-condition The authenticated user gets the appropriate page.

User gets access to the system according to their predefined
 system privilege and System
Admin,Registrar,Library,Department.Dean,Research and
Community Service,Club Represenatatives and Finance can
Update Notice

Finally the user can logout or turn off the page.

Step1: Login to Dashboard

Flow of event step Step2: Select Notices Link
Step3: Select Specific Notice.
Step4: Click Update Link
Step5: Display Notice Deleted Successfully Message

Alternative flow The Above Option is The Only way To update Notices

Table: Update Notice Usecase Descrpition

Use case name Update Profile

Identifier UC9

Description System Admin,Registrar,Library,Department.Dean,Research

and Community Service,Club Represenatatives , Finance and
Student Can Edit their Profile Information after Login in their
account
Actor System Admin,Registrar,Library,Department.Dean,Research
and Community Service,Club Represenatatives and Finance

Pre-condition Users Should Login Firest.

Post-condition The authenticated user gets the appropriate page.

User gets access to the system according to their predefined
system users can edit their profile picture

Finally the user can logout or turn off the page.


Flow of event step
Step1: Login User Home Page
Step2: Edit Profile link
Step3: Edit Form.
Step4: Fill the form and submit
Step5: ”Profile Updated” Message Display

Alternative flow The Above Option is The Only way To update Profile.

Table: Update profile usecase Descrpition

3.5 Activity Diagram

An activity diagram visually presents a series of actions or flow of control in a system similar to
a flowchart or a data flow diagram. Activity diagrams are often used in business process
modeling. They can also describe the steps in a use case diagram. Activities modeled can be
sequential and concurrent. In both cases an activity diagram will have a beginning and an end.
An activity diagrams have activity nodes and activity edges.
 Activity node: which are placeholders for one or more steps within an activity.
 Activity edge: which are connections between activity nodes.
Activity nodes has different control nodes (which coordinates flow among other activity nodes).
 An initial node: is where the flow of control starts when an activity is invoked.
 A final node: is control node at which one or more flows within the given activity stop.
The following are Washera Broadview College Notice Board System Activity Diagram
Figure 5 Login Usecase activity Diagram

Figure 6 Create Account Activity Diagram

Figure 7 Update Profile activity Diagram

Figure 8 View Notice activity Diagram

Figure 9 Create Notice Usecase activity Diagram

Figure 10 Update Notice Usecase activity Diagram

Figure 11 Delete Notice Usecase activity Diagram

Figure 12 Feedback Usecase activity Diagram

Figure 13 Update Password Usecase activity Diagram

3.6 Sequence Diagram

The sequence diagram is used primarily to show the interactions between objects in the
sequential order that those interactions occur. However, an organization's business staff can find
sequence diagrams useful to communicate how the business currently works by showing how
various business objects interact. Besides documenting an organization's current affairs, a
business-level sequence diagram can be used as a requirements document to communicate
requirements for a future system implementation. During the requirements phase of a project,
analysts can take use cases to the next level by providing a more formal level of refinement.
When that occurs, use cases are often refined into one or more sequence diagrams.

The main purpose of a sequence diagram is to define event sequences that result in some desired
outcome. The focus is less on messages themselves and more on the order in which messages
occur; nevertheless, most sequence diagrams will communicate what messages are sent between
a system's objects as well as the order in which they occur.
Figure 14 Login Sequence Diagram
Figure 15 View Notice Sequence Diagram

Figure 16 Create Account Sequence Diagram

Figure 17 Create Notice Sequence Diagram

Figure 18 Delete Notice Sequence Diagram

Figure 19 Update Notice Sequence Diagram

Figure 20 Update password sequence diagram

Figure 21 feedback Sequence Diagram

3.7 Data Flow Diagram:

Figure 22 Data flow Diagram

3.8 User Interface Design

User Interface (UI) Design focuses on anticipating what users might need to do and ensuring that the
interface has elements that are easy to access, understand, and use to facilitate that Automation of
Wahera Broadview College Notice Board. The goal of user interface design is to make the user's
interaction as simple and efficient as possible, in terms of accomplishing user goals.
Figure 23 User Interface Design

3.9 Component diagram

Component diagram is a special kind of diagram in UML. The purpose is also different from all
other diagrams discussed so far. It does not describe the functionality of the system but it
describes the components used to make those functionalities.

So from that point component diagrams are used to visualize the physical components in a
system. These components are libraries, packages, files etc.

Component diagrams can also be described as a static implementation view of a system. Static
implementation represents the organization of the components at a particular moment.

A single component diagram cannot represent the entire system but a collection of diagrams are
used to represent the whole.

So the purpose of the component diagram can be summarized as:

 Visualize the components of a system.

 Construct executables by using forward and reverse engineering.
 Describe the organization and relationships of the component
Figure 24 Component Diagram

3.10 Database Design

Database design is the process of producing a detailed data model of a database. This logical data
model contains all the needed logical and physical design choices and physical storage
parameters needed to generate a design in a data definition language, which can then be used to
create a database. A fully attributed data model contains detailed attributes for each entity. The
term database design can be used to describe many different parts of the design of an overall
database system. Principally, and most correctly, it can be thought of as the logical design of the
base data structures used to store the data. In the relational model these are the tables and views.
In an object database the entities and relationships map directly to object classes and named
relationships. However ,the term database design could also be used to apply to the overall
process of designing, not just the base data structures, but also the forms and queries used as part
of the overall database application within the database management system (DBMS).The process
of doing database design generally consists of a number of steps which will be carried out by the
database designer Usually, the designer must:
• Determine the relationships between the different data elements.
• Superimpose a logical structure upon the data on the basis of these relationships.

3.10.1 Design process

1. Determine the purpose of the database - This helps prepare for the remaining steps.
2. Find and organize the information required - Gather all of the types of information to record in
the database, such as product name and order number.
3. Divide the information into tables - Divide information items into major entities or subjects,
such as Products or Orders. Each subject then becomes a table.
4. Turn information items into columns - Decide what information needs to be stored in each
table. Each item becomes a field, and is displayed as a column in the table. For example, an
Employee stable might include fields such as Last Name and Hire Date.
5.Specify primary keys - Choose each table’s primary key. The primary key is a column, or a set
of columns, that is used to uniquely identify each row. An example might be Student ID.
6. Set up the table relationships - Look at each table and decide how the data in one table is
related to the data in other tables. Add fields to tables or create new tables to clarify the
relationships, as necessary.
7. Refine the design - Analyze the design for errors. Create tables and add a few records of
sample data. Check if results come from the tables as expected. Make adjustments to the design,
as needed.
8. Apply the normalization rules - Apply the data normalization rules to see if tables are
structured correctly. Make adjustments to the tables
Figure 25 Sample Database Design

3.11 Deployment diagrams

Deployment diagrams are used for describing the hardware components where software
components are deployed. Component diagrams and deployment diagrams are closely related.
Component diagrams are used to describe the components and deployment diagrams shows how
they are deployed in hardware.UML is mainly designed to focus on software artifacts of a
system. But these two diagrams are special diagrams used to focus on software components and
hardware components. So most of the UML diagrams are used to handle logical components but
deployment diagrams are made to focus on hardware topology of a system. Deployment
diagrams are used by the System engineers.
The purpose of deployment diagrams can be described as:
 Visualize hardware topology of a system.
 Describe the hardware components used to deploy software components.
Figure 26 Deployment diagram
3.12 Data Dictionary

Data Dictionary is a graphical tool for outlining a program’s metadata.The tool assists in
establishing items,such as variables that will be contained within aprogram. Data dictionaries
contain the heading of data item ,data type format number of bytes for storage ,size of
display,descrpition example and validation.

 Data item: The name of a particular fild uded in the program(player ID,Firest_Name).
 Data Type:The fild will be recognised by the system(intiger,string or boolean)
 Format: The way data will be displayed by the system(DD/MM/YYY).
 Number of byte for storage: Means size of data to store in memory.
 Size for display: Amount of ram required to display the data.
 Descrpition: Store information about the purpose of data.
 Example: sample data for each data.
 Validation: Rules applied to data items to ensure correct data entered.

Data item Data Format Number Size for Descrpition Example Validation
Type of byte display
for
storage

ID int - 1 ID Number 1 Auto

of a user increament

First String -------- 30 >2 Firest Abe Can not use

Name Name of numbers
User and special
characters

Last String -------- 30 >2 Last name Kebe Can not use
Name a user numbers
and special
characters

Password String ------ 25 >6 User ****** Password

Password should
greater
than 6
 chars

3.12Class diagram

Class diagram is static model that shows the classes and the relationships among classes that
remain constant over the time. Class is the main building block of class diagram, which stores
and manages information in the system. In the phase of conceptual class modeling we just create
or classes ad their interrelationship.
Figure 27 Class Diagram

CHAPTER FOUR
DESIGN DELIVERABLES OF THE NEW SYSTEM
4.1 Introduction
System design is the transformation of the analysis model into a system design model. Up to now
we were in the problem domain. System design is the first part to get into the solution domain in
a software development. This chapter focuses on transforming the analysis model into the design
model that takes into account the non-functional requirements and constraints described in the
problem statement and requirement analysis sections discussed earlier.
The purpose of designing is to show the direction how the system is built and to obtain clear and
enough information needed to drive the actual implementation of the system. It is based on
understanding of the model the software built on. The objectives of design are to model the
system with high quality. Implementing of high quality system depend on the nature of design
created by the designer. If one wants to change to the system after it has been put in to operation
depends on the quality of the system design. So if the system is design effetely, it will be easy to
make changes to it.
The objectives of design are to model the system with high quality. The design goals are derived
from non-functional requirements that means non-functional requirement is the description of the
feature characteristics and attribute of the system as well as any constraints that may limit the
boundary of the proposed solution.
4.2 Design Goals
Design goals describe the qualities of the system that the developers should consider.
 Reliability: WBVC Notice Bord system should be reliable.
 Fault Tolerance :The system should be fault tolerant to loss of connectivity with the
service.
 Security: The system should be secured, i.e., not allow other users or unauthorized users to
access data that has no the right to access it.
 Modifiability: Notice Board system should be modifiable for further modification and
enhancement of the application.
 Performance: - The system should respond fast with high throughput, i.e. it should perform
the task quickly possible such as allocating private public and users Notice, viewing users
information etc.
 Cost: The system should be developed with minimum cost possible. washera college they
loose extra cost in physical notice like papers,printer and so many for notice but if they
invest once for this project they can save extra cost then we recommended to invest for our
project.
 End User Criteria: - The system should have simple and understandable graphical user
Interface such as forms and buttons, which have descriptive names. It should give reliable
response for each user request at least before the session expires. All the interfaces, forms
and buttons are written or designed in a simple language or common language so that the
user can access it without any difficult.

4.3 Logic model Design

Logic model is an algorithm or pseudo code for a process. The following are
sample pseudo codes.
Login to the system
Login ()

Display login page

User enters Email and Password

If “login” button is clicked

{
 Open Washera database

Open Users table

If “username” is matched and password is “matched”

Display Users Home Page

Else

Display Error Message

Close table

Close database

Viewing Notice

View Private Notice ()

User log into the system

If “My Notice” is clicked

Open database

Open result table

If “result” is exist

Display Session User Notices

Close table

Close database

End function

Admin Create Notice

Create Notice ()

Admin log into the system Dashboard

Users click “Create Notice” link

Display Create Notice Form

Enter Notice Form

If “Post” button clicked

Open database

Insert data into selected Notice table

If inserted

Display “Notice Created Successfully”

Close database

Else if invalid data

Display error message

End function}

References
To do the system starting from the requirement analysis to the implementation the team members were
used the following materials:

Youtube channels
 Roha tech show
 Ethio programming
 Coding caffe
 Edurica
 Tutorials point
 Websites
 https://www.tutorialspoint.com
 https://www.javatpoint.com
 https://www.youtube.com
 https://www.ethioprogramming.com
 https://www.w3schools.com
 https://www.phptpoint.com
 https://www.google.com