CHAPTER ONE

1. Introduction

Now a day, most of the world’s people are having familiarity with computer and computer based
applications. It seems that the digital divide is highly minimized in our planet. Due to this, many
organizations and individuals have got their computer based applications for the purpose of running
their business, getting resources of information system, sharing of files with individuals,
organizations and groups by use of different social networks and web based applications. One of this
which we are considering about is DebreBerhan University Social Networks.

Some of the significant of social network of DebreBerhan University are students can easily share
their resources, knowledge, facilitating friendship among students and teachers. Italso gives timely
information about users and campus’s resource, and most important of all, it increases users’
satisfaction through increased efficiency.

1.1. Background of the organization

DebreBerhan University was established in the year 1998 E.C by the ministry of education. This
university wasbuilt to increase the literacy rate and to perform the capacity of educational
development in the country and ensuring the country ongoing development at the maximum speed.
However; so far, DebreBerhanUniversity has not the ability to use social network except the
traditional social networks. So in order to solve inability to perform different tasks and bridge the
gap of communication in the university, it is necessary to develop a social network system in the
university with rapid communication process.

As far as social network was concerned, with usersor the member of the university were using in
one of the most known network called Face book by the use of web.
 1.2. Statement of the problem

1.2.1. Service related problem

Since most of the campus students are coming from different nations with different languages, there
is a problem of diversity with one another in the campus and these are some of the problems with the
existing system.

1.2.2. Time consumption problem

Since the campus communities are located in different place inside the compound, it takes time to
meet each other for the purpose of sharing of resources and ideas.

1.2.3. Costly way to transfer information

User will lose lots of money to communicate using telephone or mobile phone and communication
will be discontinues if they do not have sufficient credit.

1.2.4. Human power related problem

For transformation of information from office to office, class to class and dorm to dorm in the
campus, human power is needed and this one of the problem there.

1.3. Objectives of the project

1.3.1. General objectives

The overall objective of this project is to provide fastelectronic (online) information transformation
and make strong friendship for the campus community in order to share their idea, resources
especially among officers, students, lecturers and other the campus members.

1.3.2. Specific objective

 To create fast and easier communicationfor the users
 To develop user friendly web based sharing resources: as information
is crucial at this time, users can share the resource and the
information what happened today and what will happen tomorrow.
 To enable users to store their data in a computerized way.
  going from place to place, office to office to perform a specific task. To enable
users online (chat)communication.
 To minimize cost: users can minimize their cost by using the
DebreBerhan university social network rather than using other
communication systems such as telephone communication..
 User can communicate easily via our social network without wastage of their
time: since time is the most fundamental thing, users can accomplish their task
without wasting their time by using this social network rather than

1.4. Significance of the project

The main aim of this social network is to give different online accesses and can be used
byDebreBerhan University to make communication and informationsharing among the society of the
university easily with a minimum amount. The result of this will help for the individual users as well
as the university. And also this project is significant for application developer and other social
network developer to achieve the goal of improving the development of online information system in
the university’s society.

1.5. Scope and Limitations of the project

1.5.1. Scope of the project

The scope of the project that we are going to do will work in every dimension of the world
particularly in Ethiopia especially for those students and workers who are joined in DebreBerhan
University. So the project will focus on the following activities.
 Provide a complete solution for connecting with the friends.

 Help build online communities of people

 Provide productive environment as per user’s reading interest

 To understand how social network works.

 This project will involve all university society in local area network (LAN) connection.

1.5.2. Limitations of the project

The project asks high technical support and maintenance.
Lack of the existing system.
 Users, who are untrained, disabled or people who can’t use computer/Internet for different
reasons and cannot use the system by themselves like speech recognition ora person who has
hearing problem in our campus.

1.6. Feasibility study of the new system

To bring the successful completion of this project goals and objectives the feasibility issues listed
below has determined the project viability or the discipline of planning, organizing, and managing
resources.

1.6.1. Technical Feasibility

So far there is no existing system in the campus and we believe that building this new system with
acceptable through in response time with in accurate performance implemented in DBU as a pioneer
of Social network system project. Because the system is too customized according to DBU
information transferring system there will be no difficulty to build the online communication system,
and also the staff and other concerned bodies has or will have enough experience using this system.

1.6.2. Operational feasibility

The social network system will provide adequate through put at desired time to the user and also
give the needed information in a timely useful formatted way. The system also has security to gives
access privilege providing account for an authorized person. This system provides help description
to the user about how to use the system. And other technical modification on the system is done by
the developers.

1.6.3. Economic feasibility

As cost-benefit analysis showsthat the new system is developed using a very minimum cost and it
gives a lot of benefits such as advancing the services of the system, decreasing the work load of the
users. The project is economically viable since its expected benefits outweigh the expected
cost .The project has a total return on investment of within seven months estimated software life
cycle.
 Items Birr cent Birr cent In birr total
1.paper 200 00 200 00 400
2.pen 20 00 20 00 40
3.USB three 900 00 900
4.CDR-W 40 00 20 00 60
5.CD 30 00 30 00 60
6.laptop 12500 12500 25000
7.print 200 200 400
Total 13890 00 270 26860

Table 1.1: Economic feasibility

1.6.4. Schedule feasibility

According with our time duration, we have listed the activities in accomplishing the project work
with its schedule requirement which are listed on the table below.

Task name Duration Due date

1. project title submission submitted on 28/02/2006 E.C 12 days

2. proposal submission 27/03/2006 E. 1 week

3. requirementspecification 05/04/2006 TO 20/04/2006E.C 15 days

4. design document 22/04/2006E.C 18 days

To10/05/2006E.C

5. implementationOf the 10/06/2006 E.C 115 days

project To05/10/2005E.C
 6. final project submission 20/10/2006 E.C To25/10/2006 6 days
E.C

Table 1.2: Schedule feasibility

Political feasibility
DebreBerhan intranet social networking site is purposely developing for the interaction of
communities especially the university. So there is no impact in political issues.

1.7. Methodology

1.7.1. Data Collection Methodology

Methodology we will use to collect data required information is interview, reading materials and etc.
1.7.1.1. Interview
To gather information, interview method will be conducted with president of the university as well
as some of the university’s society to get general information.

1.7.1.2. Document analysis

So far there is no existing system concerning on our project but during document analysis related
documents and information will be assessed.

1.7.1.3. Practical observation

We will also observe from our past experience in the meantime, our practical observation helps us to
focus on what is currently doing and this can develop data that has been collected by interview as
well as document analysis.

1.8. System Analysis and Design Technique

In this project the team will use object oriented system development methodology (OOSD).This has
two phases.
 1.8.1. Object Oriented Analysis (OOA)
During this phase the team used to model the function of the system (use case modeling), find and
identify the business objects, organize the objects and identify the relationship between them and
finally model the behavior of the objects.

1.8.2. Object Oriented Design (OOD)

During this phase the team uses rational rose software to refine the use case model, and to
reflect the implantation environment, model object interactions and behavior that support the use
case scenario, and finally update object model to reflect the implementation environment.

1.9. Development environment

1.9.1. Uniform Server:

During developing the project to run and execute programming code on browser by using uniform
server local host

1.9.2. Dreamweaver
To write and edit programming code and scripts we use dream viewer text editor.

1.9.3. Microsoft office word 2007/2010

We use Microsoft office word during prepare planning and writing documentation.

1.9.4. Microsoft office Visio 2007,

The developing project has some system analysis and design structure and interface like actors, use
case and the like. These activities are developed by using Microsoft office Visio 2007application.
 1.10. Programming tools

1.10.1. Back End Design tool

PhpMYADMIN, apache software data base system will be used in developing and managing the
back end. Since the data that we will store will be stored in the database, apache software database
system is used as a back end.

1.10.2. Front design End tool

The user interface will be developed using HTML integrated development environment since it
easily designing the front end and connected in to data base realizing rapid application development
with constraints on the hand, and we propose to use rational rose software to design different
diagrams like. Use case, class diagram, and activity diagrams etc.

1.11. Team organization

The project team composed of 5 members, one team leader, one deputy leader, one secretary, and 2
members .Problem solving is group activity. Decision on problem and approach are made by group
agreement, which is much better than individual decision
 CHAPTER TWO

2. DESCRIPTION OF THE EXISTING SYSTEM

2.1. INTRODUCTION

The previous chapter is briefly explained the background of an organization, objectives of the
project both specifically and generally, statement of the problems, feasibility study and methodology
are discussed. In addition to this, Scope and limitations of the project and development environment
programming tool and other tools are mentioned.
This chapter will explain the existing social network which is available in all over the world like face
book and twitter. It also explains about the global accessed social networks like face book and
twitter. It also explains about the intranet social networks which are accessed inside the campus
only.
2.2. Describe the existing system
In this system the existing social network systems are those which are globally used with the internet
connection. So DebreBerhan University is also still using these systems as other their way of
communication concerning social network at online environment. The project social networking site
focuses on building, developing and maintaining human relation by providing its user to have an
active social life inside DebreBerhan University. This software requirements specification provides a
complete description of all the functions and specifications of the social network site.
This project is meeting user requirements and efficient running of the system and it provides basic
networking service with a friendly touch and the people can access this system without any failure
and annoyance.

2.3. Players of existing system

Players represent external entities that interact with the system such as:
Users: persons who are directly interacted with the system.
Administrator: Person, who can allow and deny users and also giving the privileges, revokes
privileges, and so on:
 Student
 Employees and other society in the campus.

2.4. Work flow of the existing system

 The work flow in this existing system is performed starting from the President of university
to the end user. ThePresident, VicePresident, Collage Dean, Department head and other lead
all administrative function such as leading the overall flow of work in the campus.
 The network Administrator, ICT director and ICT worker providing wireless and wired
internet access for all DBU organization members specially network administrator allow and
deny user, give privilege revoke privilege for unauthorized access for the purpose of
communication throughout the world.
 The student must meet to each other or they must meet their lecture through telephone or by
visiting their dorm and the lecturer office in order to gain information.

2.5. Report generating in the existing system

The Administrator generates report daily, weekly and monthly what activities are performed, the
report is manual, it takes time to reach the main office of Information Communication Technology
(ICT). This report includes about ICT, about the employees, about the hardware requirement of the
Lab, and the total condition of the environment. In addition to this, it submits to DebreBerhan
University ICT director to which the office is located, and the office sends the response to the branch
office which is the sender.

The traditional communication generates report in manual so there are many problems faced in the
existing system
 In terms of cost
 In terms of time
 In terms of efficiencies

2.6. Business Rules in the Existing System.

A business rule is effectively an operating principle or polices that we try to specify for both the
traditionalexisting system and the new system must satisfy. It is a principle or a policy in which the
proposed system operates accordingly. It deals with access control issues.

It often pertains to access control issues, operating policies and principles of the organization.

The existing system includes the following operating principles or rules:

 The organization does not functional on Sunday. So our project will solve this problem
because this deals with 24 hour per 7 weeks.
 The user must have mobile phone with recharged account or he/she must meet face to face
to contact with each other.
 the system may not give fast responses to the user our system solve this problem
 The system should work not work 24 hours and 7 days per a week.

Our proposed system includes the following operating principles or rules:

Business Rule1: the user uses the system properly.

Business Rule2: the user creates an account properly.

Business Rule3: the system gives fast responses to the user.

Business Rule4: the system should work 24 hours and 7 days per a week.

Business rule5: the system helps to deliver additional information to the users such as news.

Business rule6: it provides more options to users.

 2.7. Problems in the existing system
2.7.1. Performance
The performance of DebreBerhan University social network with chatting system of internet is slow
because of it accessed globally not locally. While it is used in globally the network traffic is very
busy and users are worrying on this problem.

When we develop the chatting system locally the speed of accessing the system from local server is
very fast comparing with global accesses

2.7.2. Information
Information sharing among community of the university is not used local instant messaging system.

2.7.3. Economy
To share resource, the existing system used traditional way of communication that consumes more
time and money that is the precious resources of the university.

2.7.4. Control
The existing system uses the internet connection to share information online. This makes the systems
of the campus less secure and vulnerable to security threats.

2.7.5. Efficiency
The existing system uses the idea sharing methods using internet and phones that have high
performance but it is more expensive. Using phone is more expensive that can reduce the
organization’s properties. Using internet is expensive and interrupted when internet connection run
out it makes the campus out of information.

2.8. Alternative solutions

This new system solves the problem of disconnection of internet because it works from local
server so that the network traffic will not be affected.
Staffs shares information and messages easily without any involvement messengers

2.9. The proposed system

 2.9.1. Functional requirement
Functional requirements which are observable tasks or processes that must be performed by the
system. For example, functional requirements of our system must usable and more accessible for a
user in the DebreBerhan University intranet. These groups of requirement stress functionality that
the system should support for the user.
Applicant registration: the system should provide the store standard to register to the applicant.
The users can transfer information in easy way.
The users can chat in order to contact their friend online in the campus.
The administrator adds the system feature that is convenient to the user.
Update profile: system can support the user to update their profile as they want to change and
the system allows changing.
Upload and download file: Enable the user to know more about the subject they are taking by
sharing their idea on question form available.
Add friend: the system can support the user to add friend form the member in DebreBerhan
university intranet based social networking by searching their name or user name.

2.9.2. Nonfunctional requirement

These constraints are the user visible aspect of the system. Which includes:

 User Interface and human factors: The developed system provides web application user
interfaces that are compatible with internet explorer browsers. For this reason the user of the
system especially the developers who develop the system is expected to know at least how to
interact with a web application. The users or who navigate the other interface of the system
to access the system is also expected to know basic understanding on how to navigate the
user interface using a web browser.
 Error Performance characteristics or handling and extreme conditions: When the users
of the system interact with the system errors may appear. To control these inaccuracies the
system will generate different messages. Data errors which are entered in to the system may
not be completely avoided but they can be minimized. To do this most of the system
execution buttons will be controlled according to the sequence which the user is expected to
follow. Or this can be done by generating different system responses to the input of the users.
 Backup
 Onlinefilestore
  Quality Issues: To keep the quality of the system when it functions there are basic
considerations determined as requirements for reliability and user requirements.
 Requirement for reliability: Computer with good processing speed, memory and storage
capacity for backup, Local Area Network (LAN) and internet connection.
 User requirement: Technical issues example user friendly types, layout convention and
analysis of the algorithm.
 Security issues: To make the system asset safe, the system will follow a role based security
which means the access level and privilege for each builders of the system is predefined by
the system administrator. The end user of the system most of the time will be asked for
authorization login except if the user or system developer has set its own criteria to access the
system.

CHAPTER THREE

3. ANALYSIS DELIVERABLES OF THE NEW SYSTEM

3.1. Introduction
Model is an abstraction of the real world. It allows us to deal with the complexity current in a
real-world problem by focusing on the essential and interesting features of an application. The
techniques and associated notation used for object oriented analysis and design in incorporated in to
a standard object – oriented language called Unify Modeling Language (UML). An important goal
of requirement modeling is come to an understanding of the useless problem that the new system is
to address. This chapter focuses on developing the requirement and analysis models for the new
system using the UML use case model, sequence diagram, activity diagram and class diagram are
also included.

3.2. USE CASE DIAGRAM

Use case Diagram Describe the functional behavior of the system as seen by the user.
It is a sequence of action that provides a measurable value to an actor another way to look at it is that
a use case describes a way to which a real world to interacts with the system.

An essential use case sometimes called a business the case is simplified, abstract, generalized use
case that captures the intention of the user in a technology and implementation independent manner.

 A use case describes a sequence of action that provides a measurable value to an actor and
draw as a horizontal ellipse.
 An actor is a person, organization, or external system that plays a role in one or more
interactions with the system and draw as stickman figure.

Relationship between actors and use cases exists whenever an actor is involved with an
interaction described by a use case and modeled as a line connecting use cases and actors.
Figure 1Usecase diagram
 3.2.1. Actor description

User: The user of the system without user the system is useless

Admin: Is one who administer the system and who have the privilege to modify the system as new
feature is added to the system.

3.2.2. Use case textual description

Scenarios are valuable for providing context to the elicitation of users‟ requirements. They allow
the requirements engineer to provide a framework for questions about users‟ tasks by permitting
What if?‟ and „how is this done?‟ questions to be asked.
The Descriptions of Use cases and Scenarios of the Proposed System
1. Login Use Case

Name of use case: Login use case

Identification: UC01
Participating actor: user
Precondition:
 User must have user name and password.
 The Log in Window is active.
 Socket connection with server established.
Post condition
 User gets access to the system according to their predefined system privilege and finally
he/she logout or turn off the page.
Flow of events:
1. The user logs to Login form the home page of the DebreBerhan university intranet social
network system.
2. The user insertsusername and password.
3. The user click on Login button.
4. If the username and password is correct the user enter to his/her profile if not the system
display message the username and password you enter is not correct so try again.
Alternative case:
5. User sign up to the system.
 2. Sign Up Use Case

Name of use case: Sign Up use case

Identification: UC02
Participating actor: user
Precondition: Unregistered user

Post condition: user login to Social Network

Flow of events:
1. The user logs to sign up from the home page of the DebreBerhan intranet social network
system.
2. The user fill sign up form with proper manner.
3. The user click on sign up button.
4. The system shows success message if he / she fill the form correctly and registered properly
and message tries again if not correct.
Alternative case:
5. If the registered user exists in the database, the system displays the user name and password
already exists message and if the input data has errors the system display error message and
allow the user to try again.
3. Add friend Case

Name of use case: Add frienduse case

Identification: UC03
Participating actor: user
Precondition:
 The user must be member of DBU Social Network and login to social network.
 The user he/she will added must be member of DBU social network our.
Post condition: Friend request send successfully.
Flow of events:
1. The user logs to his or her profile by her/ his user name
2. The user search friend he / she want to add as friend
3. The user click on Add Friend button
4. The searched friend’s friend displayed for the user
5. The system show him or she requesting message as a message is forwarding to that person.
6. The user click on add friend
Alternate case: none
4. Update profile Use Case

Name of use case: Update profile

Identification: UC04
Participating Actor: user
Precondition: Login to Social Network
Post Condition: Update Profile successfully
Flow of events:
1. The user logs to his account.
2. User click on update profile button on his/ her profile.
3. He / she fill the update form.
4. User click update now button.
5. The system displays message successful if the form is correctly updated.
6. The user click leaves this page.
Alternate case:
7. If the form there is a mistake in the entry the system displays error message and allow
making correction.
5. Send Message Use Case

Name of use case: Send message Use Case

Identification: UC05
Participating Actor: user/Admin
Precondition: Login to Social Network
Post Condition: Message sends successfully
Flow of events:
1. The user logs to his/heraccount.
2. User clicks on Message button on his/ her profile.
3. Use case begins when the user types a message into the message text area of the Mes-
sagePage.
4. The user presses the send button.
5. The client sends the message to the server.
6. Use case ends when the system echo’s the user’s message onto the conversation text area of
their Chat Window.
Alternative Courses of Action:
 In step (step 3 of the Description) the user can choose to delete the message that was typed,
and therefore not send the message
6. Broadcast message to user Use Case

Name of use case: broadcast

Identification: UC06
Participating Actor: admin
Precondition: Login to Social Network
Post Condition: broad cast Message sends successfullyto the system.
Flow of events:
1. The admin logs to his account
2. User click on broadcast message button
3. Admin write the message
4. Admin click send now button.
5. The system displays message successful
6. The admin click leaves this page.
Alternate case:
If there is a mistake in the entry the system displays error message and allow making correction.

7. Control system Use Case

Name of use case: control system

Identification: UC07
Participating Actor: admin
Precondition: Login to Social Network.
Post Condition: Control the system.
Flow of events:
1. The admin logs to his account
2. User click on control button
3. Admin check functionality of the system
4. If there is the error with the system admin will correct it.
5. The system displays message the system is normal
The admin click leaves this page
Exceptions:
1. At the time the user tries to send the message, the other user has already logged off.
Related Use Cases:
1. Initiate Chat Window.
2. Receive Message.
Send Message Use Case
Name of use case: Send Message
Participating Actor: User
Flow of events

Description:
1. Use case begins when the user types a message into the message text area of the
Chat Window corresponding to the intended recipient.
2. The user presses the send button.
3. The client sends the message to the server.
4. Use case ends when the system echos the user’s message onto the conversation text
area of their Chat Window.

Alternative Courses of Action:

1. In step D.2 (step 2 of the Description) the user can choose to delete the message that was
typed, and therefore not send the message.
8. Upload File use Case

Name of use case: upload File Use Case

Identification: UC08
Participating Actor: user
Precondition:
 Login to Social Network
 Select the file
Post Condition: file sent.
Flow of events:
1. The user logs to his/her account
2. User clicks on File button on his/ her profile.
3. Browse the file path and upload it.
4. The user presses the send File button.
5. The user sends the File to the server.
Alternative Courses of Action:
In step (step 3 of the Description) the user can choose to cancel the File that was browsed,
and therefore not send the File.
 9. Logout Use Case

Name of use case: Log out

Identification: UC09
Participating Actor: user
Precondition: No
Post Condition: No
Flow of events: Click on logout button
3.3. Analysis Class Diagram
Class diagram shows the static structure of an object-oriented model the object class, their internal
structure, and the relationships in which they participate. Class diagram represents a detailed view of
a single use case, shows the classes that participate in the use case, and documents the relationship
among the classes. It is a logical model, which evolves into a physical model & finally becomes
functioning information system. Class diagram evolve into code modules, data objects, & other
system components. Class diagrams describe the structure of the system in terms of classes and
objects. Classes are abstractions that specify the attributes and behavior of a set of objects. Objects
are entities that encapsulate state and behavior.

Figure 2analysis class diagram

3.4. Sequence diagrams

Sequence diagram describe behavior as a sequence of messages exchanged among a set of objects.
Sequence diagram which is also known as interaction diagrams are one of the diagrams seed in
UML, for modeling the dynamic aspects of the system. It shows an interaction consisting of a set of
objects and their relationship including message that may be dispatched among them. It emphasizes
the time ordering of messages. A sequence diagram shows an interaction arranged in time sequence.
In particular, it shows the instances participating in the interaction by their “lifelines” and the stimuli
that they exchange arranged in time sequence. It does not show the associations among the objects.
Sequence diagrams are used to display the interaction between users, screens, objects and entities
within the system. It provides a sequential map of message passing between objects over time.

Main Login link Login form Login controller Database

User
Login use Window (UI)
Case# 01

1: customer activates UI ()
Customer
1. Customer activates UI.
2. Select the login link. 2. Select the login link ()
4. Fill user name and
Password
5. Submit.
3: Display the login form ()
System
3. Display the login form.
6. Validate the data
7. Return to step 4. Unless
Follow step 5. 4. Fill user name and password ()
9. Check.
10. Response

5. Submit ()
6. Validate ()

7. Try again ()

8. Step 5 continue ()
9. Check ()

10. Response ()

Figure 3Sequence diagram for login UC#01

 Sign up use Case
Case #2
Main Window Sign up Link Sign up form Sign Up Data Base
: User
UI Controler
1. Activate
2. user Selct Sign up 1.Activate()
Link
3. Sign up form display 2. Select Sign Up Link()
4. User Fill sign up
Form 3. Sign Up form Display()
5. Submit
6. validat data
7.if error try again
message or step 4 4. Fil Sign Up Form()
continue
9.Check 5. Submit() 6.Validate()
10. Responce

7. Try()
8. continue() 9. check()

10. responce()

Figure 4Sequence diagram for signup UC#02

 Add friend use Add Friend Add Friend Add friend Data Base
: User
case Link form Controler
Case# 3
Click Add friend link ()
1. user click Add friend
link 2.Add friend form display
2. Add Friend Form
disply 3. User Serch friend ()
3. user serch friend
4. Send Request
5. Validate the data
4. Send Request()
6. If error message try 5. validate()
Agin messae display
7. Continue
8.Check 6. try Again to Add()
9. Responce
7. Step 4 continue()
8. check()

9. Responce

Figure 5Sequence diagram for Add friend UC#03

 Update profile use
Case# 04 Update profile Update profile Update Profile Data Base
: User
Link() Form () Controler
. Select Update Profile Link

User
1. Selct Update profile Update Profile Form Display ()
Link
user Fill update Profile form ()
2. Update Profile Form
Display
3.Fill Update profile
Form Submit()
4. Submit .Validate()
5. Validate
6. if err try again message
or step 3
7. step 7 continue Try agin To Update ()
8. Check Step 4 Continue()
Check()
9.Edit
1o. Save

Edit()

Save()

Figure 6Sequence diagram for update profile UC#04

 Send Message
Case #05 Message link message form Server Data Base
: Adminstrator : User

Adminstrator
Click message link()
1. Click the message link
2.Message form display
Message Form Display()
3. Send Message
4.Server Request IP To
DB Send Message(Username,message)
5. DB Send IP To Server
6.Server Send Message
7. Send Acknowledgment . Request (username,IP)
To Adiminstrator

Send IP()

Send Message(IP,message)

Send Acknowledgment()

Figure 7Sequence diagram for Send message UC#05

 Send User's
warning U... Message link message form Server Data Base
: Adminstrator : User

Adminstrator
Click message link()
1. Click the message link
2.Message form display
Message Form Display()
3. Send Message
4.Server Request IT To
DB Send Warninge(Username,message)
5. DB Send IP To Server
6.Server Send Message
7. Send Acknowledgment . Request (username,IP)
To Adiminstrator

Send IP()

Send Message(IP,message)

Send Acknowledgment()

Figure 8Sequence diagram for send user warning UC#06

3.5. Activity Diagram
Describe the dynamic behavior of a system, in particular the workflow (essentially a flowchart).

An activity diagram illustrates the dynamic nature of a system by modeling the flow of control from
activity to activity. An activity represents an operation on some class in the system that results in a
change in the state of the system. Typically, activity diagrams are used to model workflow or
business processes and internal operation. Because an activity diagram is a special kind of state chart
diagram, it uses some of the same modeling conventions. Activity diagrams are mainly used as a
flow chart consists of activities performed by the system. But activity diagram are not exactly a flow
chart as they have some additional capabilities. These additional capabilities include branching,
parallel flow etc.
Figure 9Activity diagram for user login
Figure 10Activity diagram for user signup
Figure 11Activity diagram for user Add friend
Figure 12Activity diagram for user update profile
Figure 13Activity diagram for user send message

Figure 14Activity diagram for user Administrator

send message
 CHAPTER FOUR
4. DESIGN DELIVERABLES OF THE NEW SYSTEM

4.1. Introduction
The purpose of designing is to show the direction how the web page is built and to obtain clear and
enough information needed to drive the actual implementation of web page. It is based on
understanding of the model the web page built on system design also focuses on decomposing the
system in to manageable parts.

During system design we concentrate on the process of data structures and software and hard ware
components necessary to implement it.

4.2. Design goals and objectives

The objectives of designing are to model a system with high quality. Implementing of high quality
system depends on the nature of the design created by the designer .If one wants to make changes to
the system after it has been put in to operation depends on the quality of the system design. So if the
system is designed perfectly, it will be easy to make changes to it.

The goal of the system design is to manage complexity by dividing the system in to manageable
pieces.

Some of the goals are listed below.

 Security: The system should be secured from unauthorized user.

 Modifiability: The system should be modifiability to modify different services depending on
the need of the institute.
 Flexibility: The system able to change to suit new condition or situation.
 Efficiency: The system must do what it is supposed to do efficiently without the problem.
 Accessibility
One of best feature of proposed system is its accessibility. Users can access the current information
being everywhere in the campus as well as on internet. To trace some of its best features related with
accessibility
Its accessible without geographical location limitation
It is accessible without time limitation – user can share their idea every time .
Scarce information or the same information accessed by multiple users at the same time.
Workers those who work on the system can make any up on the system being on network.

4.3. Design the class diagram

Diagrams are used to represent the structure of the system in terms of objects, their notes and
nature of relationship between classes. It shows the static features of the actors and do not represent
any particular processing. It is an abstraction of the real environment class of, user and
Administrator.
Figure 15Class diagram design

4.4. Collaboration diagram

A collaboration diagram is an illustration of the relationships and interactions among objects in the
unified modeling language.

9: 9.check ()

6: 6.validate ()
Login form Database

10: 10.response
()
7: 7.try again () 8: 8.step 4 continues () Login
Controller

4: 4.fill user name and password ()

3: 3: Display the login form

5: 5.submit ()
()

2: 2.select login form ()

: User
1: 1: customer activates UI ()

User
Interface (UI)
Figure 16collaboration diagram for login

Sign up
Link
6: 6.Validate() 9: 9. check()
2: 2. Select Sign Up Link()

5: 5. Submit() 8: 8. continue()
Sign Up Data
Controler Base

: User

4: 4. Fil Sign Up Form()

1: 1.Activate() 7: 7. Try()
3: 3. Sign Up form Display() 10: 10. responce()

Main Window
UI Sign up
form

Figure 17collaboration diagram for signup

 Add Friend Link
5: validate()
1: Click Add friend link ()

4: Send Request()
Add friend
Controler
: User

2: 2.Add friend form display

3: User Serch friend () 7: Step 4 continue()

6: try Again to Add()

8: check()

Add Friend form Data

Base
9: Responce

Figure 18collaboration diagram for add friend

 Message
link
1: Click message link()

message
form
2: Message Form Display()
: Adminstrator

Data
Base
3: Send Message(Username,message)

7: Send Acknowledgment() 4: . Request (username,IP)

5: Send IP()

Server
: User 6: Send Message(IP,message)

Figure 19Collaboration diagram for Send message

 Message
link
1: Click message link()

message
form
2: Message Form Display()
: Adminstrator
3: Send Warninge(Username,message)

7: Send Acknowledgment()

4: . Request (username,IP)
Server Data
Base
6: Send Message(IP,message) 5: Send IP()
: User

Figure 20Collaboration diagram for Send Warning to User

 Update profile
Link()
1: . Select Update Profile Link

3: user Fill update Profile form ()

Update profile
Form ()
2: Update Profile Form Display ()
: User

6: Try agin To Update ()

4: Submit() 9: Edit() 10: Save()

5: .Validate()
8: Check()

7: Step 4 Continue()
Update Profile
Data
Controler
Base

Figure 21Collaboration diagram for Update Profile

4.5. State chart diagram

State chart diagram is used to show the sequence of states that an object goes through, the events that
cause the transition from one state to the other and the actions that result from a state change.

Initial state Idle Activate Login Normal exit Verify login

Un normal exit
Fail Evaluation

Final state

Confirm
Login
Complete state

Fig: 22State chart Diagram for User Login

 intial state idle activate normal exit
fill the form send verify
request

un normal exit
Evaluation
leave the page
final state

confirm
request
complete state

Fig 23State Chart Diagram For User Sign up

fill update request normal exit

intial state idle send update edit
request

unnormal exit Evaluate

ignor edit
confirm
update
final state

save

complete state

Fig 24State Chart Diagram for User Update Profile

 Initial state Message Link Click Message Send Verify Message

Un normal exit
Fail Evaluation

Final state

Confirm
Message
Complete state

Fig 25State Chart Diagram for User Send message

4.6. Database design

Database Design is the database structure that will be used as plan to Store and manage the data.
Database se 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. Much thought, as data and reporting requirements become more complex, those same
people will simply and produce the required data by incorrectly adding more columns of tables to the
database.
Figure 26Database design.
 CHAPTER FIVE

5. IMPLEMENTATION DELIVERABLE OF THE NEW SYSTEM

5.1. Introduction
Implementation refers to the Coding of the all documents gathered starting from requirement
analysis to the Design phase. So now the team is in a position of converting all documents gathered
and designed into the code as a system. So that the system will be implemented for the user to be
used for the purpose it developed. To implement it the user must have a server on which the system
will be hosted because this system can run on intranet site with connection availability or on internet
connection as well as the Ethernet system.

5.2. Component diagram

In this Diagram components of the system will be wired showing that there is relation among
components, management of the system, database and operations performed on databases such
security issue. This in some extent shows which component or objects will be accessed by whom
and what type of security infrastructures it is using. The diagram is simulated below.
Figure 27Component diagram

5.3. Deployment diagram

Deployment modeling is used to show the hardware of the system, the software that is installed in
the hardware and also the middleware that is used to connect the disparate machines to one and
other. It also shows how the software and the hardware components work together in order perform
the task.

Database

Figure28Deployment diagram
5.4. User interface design
In this system users will communicate with their friends by using the developed system through the
following user interfaces.

Login: This form appears when the user automatically enters the site address in to the URL, so that the
user can login if he/she had registered in the site, otherwise the user have to register with a valid
identification on the space provided. After registering, the login account will lead the user to the
original homepage.
Figure 29User interface for login and signup.

Home Page: This form appears on the site in which the system deployed is opened and contains some
links as well as some descriptions whichis about your profile whether if you want to upload your
profile picture or no, your address such as birthplace, birthday, and phone number and so on. In the
meantime the system leads the user to other specific pagesin order to access social relationships by
searching friends what he want.

Figure 30User interface for Home.

Profile: this form is a link that can appear when the link is clicked, so that the use can edit his/her
profile whenever he/she wants.
Figure 31User interface design for Edit profile

View and download files: this interface is also a link that used to view the uploaded files and to
download files if necessary.

Figure 32User interface design for view and download file

5.5. Prototype development
Prototype development can be defined it is the sample code of the given project. These are some of
the sample codes that we have done it.

Sample code for login

Sample code for signup
Sample code for order Comment
 CHAPTER SIX
6. CONCLUSION AND RECOMMENDATION

6.1. CONCLUSION
This is a system development project which two phases; the first phase deals with the analysis phase
of the life cycle, and the next phase addresses the Design phase. As the end of the first phase, we
need to review that we have covered in accordance with what we have planned at the beginning. We
began our work by identifying the significance of automated system for the store and the overall
techniques to be used in the development process. This involved defining the system development
methodology, identifying process, and setting the deliverable and scheduled for the project.

The business area Analysis helps the team to truly understand the major functional areas and
processes of the system. Through this we evaluate the existing system weakness and strength.

After that, we performed requirements elicitation to discover user and system requirements. This
phase consisted of drawing the functional as well as non-functional requirements of the system.
Then we have undertaken a major phase in system development process: object oriented Analysis.
Here, we tried to model the new system we proposed using UML diagrams: Use case, sequence, and
activity and class diagrams. Also we designed the new system user interface prototype.
6.2. RECOMMENDATION
The system that we are trying to develop is an electronic communication system that enables users to
share information in real-time as well as uploading different files in to the system. In the meantime
the system will work whenever there is no an internet connection by using the Ethernet system.

Therefore, we suggest the following features need to be incorporated in any further revision and
extension attempt.

- Online video chatting of users and enable them view their friends in online videoin real time.
- Uploading and downloading different multimedia files such as video, games, mp3 files etc.
- The system should develop to add new features like advertisement, onlineviewing
announcement system.
- The system should also develop to block accounts where the user illegally interrupt the
system.
 REFERENCE
1. Ambler, Scott (2001) The Object primer: The application Developers Guide to Object
Oriented and the UML.2nd rev. Ed England: The Cambridge University Press.
2. Bruegge, Bernd (2000) Object oriented Soft ware Engineering Conquering Complex and
Changing System. Upper Saddle River: Prentic Hall.
3. Chopra, R.N (1999) Dictionary of Library Science. New Delhi Anmol Publication
4. http://seminarprojects.com/Thread-project-report-on-online-movie-booking-system
5. http://www.scribd.com/doc/80258611/Online-Ticket-Reservation-System-for-Cinema-Hall
6. http://www.oxicash.in/movie/movie-tickets.aspx
7. http://www.codeforge.com/s/0/online-movie-ticket-booking-in-j2ee
 Appendix

Interview
1. Mention and describe the main challenges in the social network process in DebreBerhan
University.
2. What will be the benefit of Social Network in DebreBerhan University?
3. List the services given byDebreBerhan university
Table of contents
CHAPTER ONE................................................................................................................................................................. 1
1. introduction............................................................................................................................................................ 1
1.1. background of the organization.................................................................................................................. 1
1.2. statement of the problem.............................................................................................................................. 2
1.2.1. service related problem............................................................................................................................. 2
1.2.2. time consumption problem...................................................................................................................... 2
1.2.3. costly way to transfer information........................................................................................................ 2
1.2.4. human power related problem............................................................................................................... 2
1.3. objectives of the project................................................................................................................................. 2
1.3.1. general objectives........................................................................................................................................ 2
1.3.2. specific objective.......................................................................................................................................... 2
1.4. significance of the project............................................................................................................................. 3
1.5. scope and limitations of the project.......................................................................................................... 3
1.5.1. scope of the project..................................................................................................................................... 3
1.5.2. limitations of the project........................................................................................................................... 3
1.6. feasibility study of the new system........................................................................................................... 4
1.6.1. technical feasibility...................................................................................................................................... 4
1.6.2. operational feasibility................................................................................................................................. 4
1.6.3. economic feasibility..................................................................................................................................... 4
1.6.4. schedule feasibility...................................................................................................................................... 5
1.6.5. political feasibility........................................................................................................................................ 6
1.7. methodology....................................................................................................................................................... 6
1.7.1. data collection methodology................................................................................................................... 6
1.7.1.1. interview..................................................................................................................................................... 6
1.7.1.2. document analysis................................................................................................................................... 6
1.7.1.3. practical observation.............................................................................................................................. 6
1.8. system analysis and design technique..................................................................................................... 6
1.8.1. object oriented analysis (ooa)................................................................................................................. 6
1.8.2. object oriented design (ood)................................................................................................................... 7
1.9. development environment........................................................................................................................... 7
1.9.1. uniform server:............................................................................................................................................. 7
1.9.2. dreamweaver................................................................................................................................................. 7
1.9.3. microsoft office word 2007/2010......................................................................................................... 7
1.9.4. microsoft office visio 2007,...................................................................................................................... 7
1.10. programming tools...................................................................................................................................... 7
1.10.1. back end design tool............................................................................................................................... 7
1.10.2. front design end tool.............................................................................................................................. 8
1.11. team organization........................................................................................................................................ 8
CHAPTER TWO............................................................................................................................................................... 9
2. description of the existing system................................................................................................................. 9
2.1. introduction........................................................................................................................................................ 9
2.2. describe the existing system........................................................................................................................ 9
2.3. players of existing system............................................................................................................................. 9
2.4. work flow of the existing system............................................................................................................. 10
2.5. report generating in the existing system............................................................................................. 10
2.6. business rules in the existing system..................................................................................................... 10
2.7. problems in the existing system.............................................................................................................. 11
2.7.1. performance................................................................................................................................................ 11
2.7.2. information.................................................................................................................................................. 11
2.7.3. economy........................................................................................................................................................ 11
2.7.4. control............................................................................................................................................................ 12
2.7.5. efficiency....................................................................................................................................................... 12
2.8. alternative solutions..................................................................................................................................... 12
2.9. the proposed system.................................................................................................................................... 12
2.9.1. functional requirement........................................................................................................................... 12
2.9.2. nonfunctional requirement................................................................................................................... 13
CHAPTER THREE........................................................................................................................................................... 14
3. analysis deliverables of the new system................................................................................................... 14
3.1. introduction..................................................................................................................................................... 14
3.2. use case diagram............................................................................................................................................ 14
3.2.1. actor description........................................................................................................................................ 16
3.2.2. use case textual description.................................................................................................................. 16
3.3. analysis class diagram.................................................................................................................................. 21
3.4. sequence diagrams............................................................................................................................................. 22
3.5. activity diagram.............................................................................................................................................. 28
CHAPTER FOUR........................................................................................................................................................... 35
4. design deliverables of the new system...................................................................................................... 35
4.1. introduction..................................................................................................................................................... 35
4.2. design goals and objectives........................................................................................................................ 35
4.3. design the class diagram............................................................................................................................. 36
4.4. collaboration diagram.................................................................................................................................. 37
4.5. state chart diagram....................................................................................................................................... 43
4.6. database design.............................................................................................................................................. 45
CHAPTER FIVE............................................................................................................................................................. 47
5. implementation deliverable of the new system..................................................................................... 47
5.1. introduction..................................................................................................................................................... 47
5.2. component diagram...................................................................................................................................... 47
5.3. deployment diagram..................................................................................................................................... 48
5.4. user interface design.................................................................................................................................... 49
5.5. prototype development............................................................................................................................... 53
CHAPTER SIX................................................................................................................................................................ 57
6. conclusion and recommendation................................................................................................................. 57
6.1. conclusion......................................................................................................................................................... 57
6.2. recommendation............................................................................................................................................ 58
Reference........................................................................................................................................................................ 59
Appendix60
Figure of Content
figure 1usecase diagram
figure 2analysis class diagram
figure 3sequence diagram for login uc#01
figure 4sequence diagram for signup uc#02
figure 5sequence diagram for add friend uc#03
figure 6sequence diagram for update profile uc#04
figure 7sequence diagram for send message uc#05
figure 8sequence diagram for send user warning uc#06
figure 9activity diagram for user login
figure 10activity diagram for user signup
figure 11activity diagram for user add friend
figure 12activity diagram for user update profile
figure 13activity diagram for user send message
figure 14activity diagram for user administrator send message
figure 15class diagram design
figure 16collaboration diagram for login
figure 17collaboration diagram for signup
figure 18collaboration diagram for add friend
figure 19collaboration diagram for send message
figure 20collaboration diagram for send warning to user
figure 21collaboration diagram for update profile
figure 22state chart diagram for user login
figure 23state chart diagram for user sign up
figure 24state chart diagram for user update profile
figure 25state chart diagram for user send message
figure 26database design.
figure 27component diagram
figure 28deployment diagram
figure 29user interface for login and signup
figure 30user interface for home
figure 31user interface design for edit profile
figure 32user interface design for view and download file