haramaya universitymameamin.6te.net/.../11/intranet-social-networking-site.docx · web...
TRANSCRIPT
HARAMAYA UNIVERSITY
College of Computing and Informatics
Department of Information TechnologyIndustrial Project I Project Title: - Design And Implementation of HU-Based Social networking site
Submitted by: Awoke Gerem Deggu Dessie Haile Chere
Submitted To: Mrs. Susie
1/11/2013
Haramaya University
Project Title: Design and Implementation of HU based Social Networking Site
2
Abstract HU social network is a social structure that maps out the relationships between individuals.
Social networking sites "make invisible social networks visible" by allowing us to see (with
pictures and links) who our friends' friends are, and who our friends' friends are all in
an easy to use interface. Before user can make an online connection, users need to create a
profile on HU social-networking site. User will be asked to enter a login e-mail id or username
and password.
The Designing and Implementation of HU based Social Networking Site project focuses on
building, developing and maintaining human relations by providing its user to have an active
social life.
To develop this project, we will use the development tools like
Uniform Server(contain My SQL,PHP and Apache Server)
HTML(For User Interface)
Java Script and PHP Programming languages.
Notepad++ Editor
The project will follow the software development life Cycle. These are:-
Analysis phase
Designing phase
Implementation and
Testing
After the completion of our project, some requirements should be fulfill to run the
project. These are: Hardware requirements, software requirements and manpower.
Hardware Requirements:
1. 256 MB Min. RAM
3
2. Intel® Core™2 Duo CPU
3. 40 GB Min. HDD
Software Requirements server side:
1. Windows XP
2. windows Vista
3. Windows 7
Software Requirements clients’ side:
1. Ms-Internet Explorer
2. Mozilla Firefox
3. Google Chrome
4. opera
Manpower requirements:
Three Students or group members can complete this in 6-7 months.
Table of Contents page
4
Abstract......................................................................................................................3
Chapter one................................................................................................................8
1. Introduction......................................................................................................8
1.1 Project background...........................................................................................8
1.2 Statement of the problem.................................................................................9
1.3 Objectives.........................................................................................................9
1.3.1 General objectives......................................................................................9
1.3.2 Specific objectives...................................................................................10
1.4 Significant of the system................................................................................10
1.5 Scope and limitation of the project................................................................11
1.5.1 Scope of the project..................................................................................11
1.5.2 Limitation.................................................................................................11
1.6 Literature review............................................................................................12
1.7 Methodology..................................................................................................13
1.7.1 Introduction..............................................................................................13
1.8 Feasibility analysis.........................................................................................14
1.8.1 Economic Feasibility................................................................................14
1.8.2 Technical Feasibility................................................................................14
1.8.3 Operational Feasibility.............................................................................15
1.8.4 Schedule feasibility..................................................................................15
1.8.5 Legal and contractual feasibility..............................................................16
1.8.6 Political feasibility...................................................................................16
Chapter Two............................................................................................................17
Business Area Analysis......................................................................................17
2. Introduction....................................................................................................17
2.1 Players of existing system..............................................................................17
2.2 Problem of the current system........................................................................18
5
2.2.1 Performance.............................................................................................18
2.2.2 Information (and data)..............................................................................18
2.2.3 Economics................................................................................................18
2.2.4 Control (and Security)..............................................................................19
2.2.5 Efficiency.................................................................................................19
2.2.6 Service......................................................................................................19
2.3 Functional requirements.................................................................................19
2.4 Essential use case modeling...........................................................................21
2.5 Use case..........................................................................................................21
2.5.1 Use case diagram......................................................................................21
2.5.2. Actors......................................................................................................23
2.5.3 Essential use case description..................................................................23
2.6 Essential user interface flow diagram............................................................30
2.7 Essential User Interface Prototyping..............................................................31
2.7.2 Login UI Prototyping...............................................................................31
2.7.3 Change password.....................................................................................32
2.8 Non functional requirements..........................................................................32
Chapter Three..........................................................................................................33
3.1 Introduction.................................................................................................33
3.2 System use case..............................................................................................33
3.2.1 Sequences diagram...................................................................................33
3.3 Activity Diagram Definition..........................................................................38
3.4 Activity diagram.............................................................................................38
3.5 Class Diagram................................................................................................42
3.5.1 Description of Class Diagram..................................................................44
Chapter Four............................................................................................................54
System Design.........................................................................................................54
6
4.1 Introduction....................................................................................................54
4.2 Design goal.....................................................................................................54
4.3 Hardware/Software mapping..........................................................................55
4.3.1 Software...................................................................................................55
4 .3.2Hardware..................................................................................................55
4.4 Access control and security............................................................................56
4.5 Object design..................................................................................................56
4.6 User interface prototype.................................................................................56
4.7 Database Design.............................................................................................58
List of tables.........................................................................................................59
List of figure.........................................................................................................59
List of Abbreviations and Nomenclature.............................................................60
7
Chapter one
1. IntroductionThe communi ty ins ide the Haramaya univers i ty people i s jo in ing
socia l ne twork s i tes l ike MySpace, face book, and other social networks.
Once logged into one of these systems, participants are asked to create a profile
to represent them. Digitally using text, images, video, links, and people
generate a profile that expresses how they see themselves. Participants can
mark other users as 'Friends'. If that other person agrees with the relationship
assertion, a photo of each is d isp layed on the prof i le of the o the r and
make chat wi th f r iends . Thr ough care ful se lec t ion , par t ic ipants
deve lop a 'Friends' list. New social technologies have altered the underlying
architecture of social interaction and information distribution inside in the
university.
1.1 Project backgroundThe title of the project is design and implementing Haramaya University
based social networks.
We try to develop an intranet social network for the campus that can
access only within the campus.
Now a days there are many different types of social networks .but most
of those social networks are caused problem of security. This makes the
campus difficult to exchange ideas. Thus, a new social network site will be
developed for the campus .they can use this system for chatting and transfer file
and sharing information and exchange ideas within their local network or intranet
network.
8
Good for security purpose and to avoid hacker which comes from outside the
campus and also the system will ignore the user registration if the user id is invalid
or incorrect.
1.2 Statement of the problemSince people that are living in the campus are using global social
networks sites in order to share information, uploading image, video, and
text. But when internet connection interrupted, those people cannot
perform those tasks. Because of there is no any means to communicate
with each other in local area network of the campus without internet
access.
There is no any social networking website that provides efficient access and easy
communication in Haramaya University local network.
Using Global social Networking websites, there is an overhead of traffic in
network that making long time to access.
In this intranet network where everyone in the campus wants to connect, so that one can
better coordinate with other any make work easy with enjoyment.
1.3 Objectives
1.3.1 General objectivesDevelop intranet social networking site for Haramaya university
community for the purpose of internal communication.
9
1.3.2 Specific objectivesThe objective of Design and implementation of intranet social networking site is to
connect users that are living in the campus. Social networks rightly defined as “our
connections with others people inside our campus”.
Provide easy to create and share a personal profile for users
Easy search out and contacting potential friends in the intranet network.
Easy to exchange information and data through the intranet site.
HU intranet social networking site is aimed, at developing and maintaining human relation.
This project is an intranet based application that can be accessed throughout the campus helps
users, maintain existing relations and also establish new ones. This is made possible by
messages, pictures and videos. A help option how to use is provided to guide the user. Thus,
allowing you to connect to your personal life. To join this site the user needs to register and then
sign in to start connecting and experiencing a whole campus world.
1.4 Significant of the systemAfter the project is completed the university’s community becomes
beneficiary.
The benefits are:
Reduces the cost that menaces no need internet connection
Reduces time for distribute information inside the university.
Accuracy information is distributed to the people.
Information is secure no venerable for attacker and hacker
10
So the new system will solve the above problem which is not get the
internet connection well and this web application will works locally
without the need of internet connection.
1.5 Scope and limitation of the project
1.5.1 Scope of the project
The social networks are developed for the community for Haramaya
University only.
The Haramaya University uses this system for transfer file and for
communication purpose. Since this system is an intranet system people
inside only accessed.
It is a web-based application
Users can upload images
Registration(login facility)
Help option for better understanding
Users can add friends
Users can communicate with their friends through chat.
1.5.2 Limitation
11
The main limitation of the project is for everyone and thus does not restrict anyone that
are living in the campus and who have the knowledge to use internet from entering to
the site.
Users who are illiterate, disabled or people who can’t use
computer/Internet for different reasons cannot use the system by
themselves
Users must have computer that connected to HU LAN Network rather than use
mobile. Because our site accessed only intranet or in the campus network
During our project progress the computer laboratory will be
occupied by the remaining Bach students or lack of enough
computer access.
1.6 Literature reviewIn this section we will explain the existing social networks. Existing
social networks which available in Haramaya University such as face
book twitter and so on.
But face book and twitter can be connection oriented that means they are
accessed all over the world with internet. This type of social networks is
accessed globally using internet.
We need intranet social network which is accessed only by inside user in
order to share information, share file and communicate inside the campus
without the need to internet connection.
12
1.7 Methodology
1.7.1 Introduction This section demonstrates how the specific objectives of the project will be
achieved. What type of material is required to accomplish our project successfully
and how we can get the information from community.
To successfully complete our project there are some tools to be gate
successful project.
We will use different tools for our project like
Java script
Notepad ++
PHP
Microsoft Visio 2007
Microsoft word 2007
Uniform server
The project will be performed by three students coordinate together to
achieve our aim and works for common objectives
Data collection methodology
I. Direct observation:-by watching what people do in day to day activity in
lack of information flow in the campus when internet connection is not
available.
II. Interviews method: we use interview method in order to gather
information about communication problem in the university when
the connection is terminated. We use this method to collect some
13
information why they need to implements this intranet social
network.
1.8 Feasibility analysisThe feasibility analysis is designed to determine whether or not, given the project
environment, a project will be successful. A feasibility analysis may be conducted
for a project with an emphasis on financial viability, environmental integrity,
cultural acceptability, or political practicability.
1.8.1 Economic FeasibilityEconomic feasibility identifies the financial benefit and cost association with the
development project.
Economic feasibility refers to cost benefit analysis.
When we see our project after completion the university people can use the site to
communicate information internally or create team connection inside the campus.
That means it reduce the cost which use for phone calling and labors which is
distribute the materials inside the offices.
And also the university did not pay any birr for ISP because it is inside the campus.
1.8.2 Technical FeasibilityThe purpose of technical feasibility is to gain an understanding of the organization
ability to construct proposed system. This analysis should include an assessment of
the development group understanding of the possible target hard ware, Soft ware
14
and operating environment to be used as well as a system size, complexity and the
group experience with similar system.
In our project the team uses languages such as HTML, PHP, Notepad++, and CSS
to develop the new system. This all are in technical side.
The technical persons who develop the new system are all the members of the
project.
The project team, to develop the new system, gathers the required information/data
from the universities community who are interested to give information for us.
1.8.3 Operational FeasibilityIts purpose is to gain understanding of the degree to which the proposed system
will likely to solve the business which is inside the university.
After the completion of the project the community inside the university can easily
communicate with each other without physically contact. So it solves some
problem related to communication, information sharing and others.
The community was happy to give information about everything that we want. So
we did not get negative consequences while collecting the information from the
university community.
This indicates that the project is operationally feasible.
1.8.4 Schedule feasibilityThe purpose of assigning schedule feasibility is to know and understanding the
potential time frame and final completion date schedule in order to meet the
expectations and satisfaction of the community .
15
It also indicates the starting date of your project and the final compilation date of
your project.
Schedule is set for the project while we define the specific objectives. The tasks
may not be accomplished during the stated schedule due to many obstacles. We
will try to resist the problem as much as we can and amend the schedule if possible
and finished by the schedule.
1.8.5 Legal and contractual feasibilityWhen the system is developed, it is not violet the rule and regulation of the
government as well as the rule and regulation of the university.
We are developing our project using different software’s that are provided us by
the university and the university purchase with license. Since the university is legal
organization, we expect that no violation of copy right.
1.8.6 Political feasibilityHU intranet social networking site is purposely developing for the interaction of
communities. So there is no impact in political issues.
16
Chapter Two
Business Area Analysis
2. Introduction The chapter will explain the existing social network which is available in
Haramaya University.
It also Explain about the global accessed social networks like face book
and twitter.
Explain about the intranet social networks which are accessed inside the
campus only.
The project social networking site focuses on building developing and
maintaining human relation by providing its user to have an active social
life inside Haramaya University.
This software requirements specification provides a complete description
of all the functions and specifications of the social network site.
The aim of this project is meeting user requirements and efficient
running of the system. This project provides basic networking services
with a friendly touch and the people can access without system busy.
2.1 Players of existing systemPlayers represent external entities that interact with the system.
Users: persons who are directly interacted with the system
17
Administrator: Person, who can allow and deny users and also change the
background of main page of our Social networking site, and so no.
2.2 Problem of the current systemThe problems of existing system are describing using the PIECES
framework. This framework is used to identify the problem within
existing information.
2.2.1 Performance Throughput
The Throughput is low because of the bandwidth which is given for
the campus.
Response time
Since the current system uses global networks that is delay to respond
user requests.
2.2.2 Information (and data)
The user expects the massages from the system and if the
connection is interrupted the user doesn’t get the response.
2.2.3 Economics
Costs
The System doesn’t take that much cost. But some software and
hardware must available for storing of user data.
Profits
18
The existing system used connection or access globally so if no
connection the communication between people is interrupted
2.2.4 Control (and Security)
In security area the campus have its own firewall which is
protect from outsiders. No much more difficult.
2.2.5 Efficiency
When the connection is available the campus community do
exchange file or communicate each other using email or face
book. But when the connection is interrupted the campus used
either human labor or telephone calling so that doesn’t make
efficiency.
2.2.6 Service
It gives an internet access for users who need
information about something.
2.3 Functional requirementsSince we are develop the intranet social networks for Haramaya
University the system will works for the community for the purpose of
sharing or exchange data and used for social life interaction.
It also provides chatting system for inside the university.
19
The main functions are:-
Create account (signup):- Users can create their own account.
Login:-User must login after create account to access their own home
page.
Update profile:-Users can update their own profile picture.
Change password:-Users can modify their password.
Add friends:-User can add friends by searching using the friends email
or their name.
Chatting:-People can make chat with their friends.
Send massage:-People can send massage using this intranet network to
their friends inside the campus only.
Update information:-People can fill their own personal information.
20
Fig. 2.1 functional requirement
2.4 Essential use case modeling An essential use case is a simplified, abstract, generalized use case that captures
the intentions of a user in a technology and implementation independent manner. A
fully documented essential use case is a structured narrative, expressed in the
language of the application domain and of users, comprising a simplified, abstract,
technology-free and implementation-independent description of one task or
interaction.
2.5 Use caseUse cases are all of the functionality of the system that is contained within the
system boundary.
A use case describes the sequence of events of some types of users, called Actors,
using some part of the system functionality to complete a process.
2.5.1 Use case diagramA use case diagram at its simplest is a graphical representation of a user's
interaction with the system and depicting the specifications of a use case. A use
case diagram cans different types of users of a system and the various ways that
they interact with the system.
Lists of use case that we have
Access home page site
User home page
Logout
Profile
Message
Picture
21
22
Fig.2.2 use case diagram.
2.5.2. ActorsAn actor represents a type of users of the system or external systems that the
system interacts with.
Directly or indirectly interact with the system or affected by the system.
The use case diagram identifies the primary elements and process that from the
system.
The primary elements are the “actors” and the processes are called “use cases.”
The use case diagrams show which each use case.
Users
Administrator
2.5.3 Essential use case description
2.5.3.1 Access home page siteUse case name: Access site home page
Priority Essential
Primary actor user
Precondition User is connected to the network
Basic path 1. Web server gets the user requested site
2. The server displays to the user with the site home page
Alternative path N/A
Post condition The user is on the site home pageException path 1. If there is a network failure the
server returns to the wait state.
23
2. If authentication fails prompt the user that he/she typed the wrong password or id. Allow him/her re-enter chances.
Use case
selectuser
2.5.3.2 User Home Page
Use Case Name: User Home PagePriority EssentialPrimary Actor UserPrecondition User is connected to the network and needs to have a valid e-
mail and password
Basic Path1. Web Server verifies the user e-mail and password.
2. After verification the Server displays the user with the User Home Page.
Alternate Path N/A
Post condition The User is on the User Home PageException Path If there is a network failure the Server returns to Site Home Page
requesting to Try Again.
Use Case
access
24
Signup DBSocial network site
Home page
User detail DB
Table 2.1 access home page user description
2.5.3.3 Logout
Use Case Name: Logout
Priority Essential
Primary Actor User
Precondition User is connected to the network and and in the user home page
Basic Path
1. Users select logout option in the the user home page
2. After closing the session the user has successful logout
Alterative path
N/A
Post conditionThe User is on the Site Home Page
Exception Path If there is a network failure the Server returns to the wait state
2.5.3.4 Profile
Use Case Name: Profile
Priority Essential
25
Table 2.2 user home page use case description
Table 2.3 logout page use case
Primary Actor User
Precondition User is connected to the local area network and is in the user Home Page.
Basic Path 1.Select Profile option on User home Page.2.Web server gets Profile form
Alternate Path N/A
Post condition The User is on the Profile Form.Exception Path If there is a connection failure the Server
returns to the wait state.
2.5.3.5 Message
Use Case Name Message
Priority Essential
26
Table2.4 use case description of profile page.
Primary Actor User
Precondition User is connected to the LAN Network and is in the User Home Page
Basic Path 1. Select Message option on User home Page
2. Web server gets Message formAlternate Path N/A
Post condition The User is on the Message form.
Exception Path
.
If there is a network failure the Server returns to the wait state
2.5.3.6 Pictures
Use Case Name: Pictures
Priority Essential
27
Table 2.5 use case description for massages
Primary Actor User
Precondition User is connected to the network and is in the User Home Page
Basic Path 1. Select Photo option in UserHomepages
2. The Server presents the user with the Photo
Alternate Path N/A
Post condition The User is on the Photo Form
Exception Path If there is a connection failure the Server returns to the wait state
2.5.3.7 Friends
Use Case Name: Friends
Priority Essential
28
Table 2.6 use case description for picture
Primary Actor User
Precondition User is connected to the network and is in the User Home Page.
Basic Path 1. Select Photo option in the user homepage
2. The server presents the user with photo form.
Alternative pathN/A
Post condition. The User is on Photo FormException Path If there is a connection failure the Server
returns to the wait state
2.6 Essential user interface flow diagram
29
Campus networking/ intranet networking Data base
Table 2.7 use case description for friends
Add/Edit
Updates
2.7 Essential User Interface PrototypingAn essential UI prototype is a low fidelity model of the UI for our system. It
represents the general ideas behind the UI, but not the exact details. Essential UI
prototypes represent UI requirements in a technology independent manner, just as
essential use case models do for behavioral requirements. An essential UI
30
Users
Home User Account Login Profile
Users
User Account User account Data base
Profile Profile Data Base
Fig 2.3 essential use interface flow
diagram.
Fig 2.4 user update flow diagram
prototype is effectively the initial state the beginning point of the UI prototype for
the system. So, now we don’t need to use technology based prototyping tool in
order to understand and solve the problem.
We just select the UI for sign up as a sample and what user can do on that
interfaces. We take signup interfaces that require first name, last name and soon
from the user.
2.7.1 Create Account User Interface Prototyping
2.7.2 Login UI Prototyping
2.7.3 Change password
31
User First Name
User Last Name
Input fields
Sex
Check box
Date of birth
Drop Down List
E-mail id
Password
Input fields
E-mail id
Input field
Password
Input field
E-mail id
Input field
Fig 2.5 create account prototype
Fig 2.6 Login prototype
2.8 Non functional requirementsThere are some requirements sometimes non functional. Specifically these are
constraints the system must work within. The system must be compatible with
other system in both Netscape and internet explorer web browser.
Hardware: server, enough amount of Hard Disk.
Operating System: windows XP, Windows 7, Vista
Connection: local area network.
Chapter ThreeObject Oriented Analysis
32
E-mail id
Input field
New password
Input field
Confirm password
Input field
Fig 2.7 change password prototype
3.1 IntroductionIn the past two chapter we would discuss the main part of our project the
objectives, scope of the project, statement of the problem, tools and methodology
of the project, all the feasibility study and in the second chapter we would see use
case identification, actor identification and definition, use case diagram, use case
description, essential use case modeling and also in this third chapter we will see
definition and listing of sequences diagram, definition and listing of Activity
diagram ,class modeling ,and class diagram.
This chapter will explain the tables and table attributes of the class diagram.
3.2 System use caseSystem use cases are use cases that bring technological concerns into account. A
use case is a sequence of actions that provide a measurable value to an actor.
Another way to look at it is a use case describes a way in which a real-world actor
interacts with the system.
3.2.1 Sequences diagramA sequence diagram is an interaction diagram that detail show operations are
carried out. What messages are sent and when. Sequence diagrams are
organized according to time.
It represents t h e i n t e r a c t i o n b e t w e e n d i f f e r e n t o b j e c t s i n t h e
s y s t e m . T h e important aspect of a sequence diagram is that it is time-
ordered. This means that the exact sequence of the interactions between the
o b j e c t s i s r e p r e s e n t e d s t e p b y s t e p .
33
34
Fig 3.1 sequences diagram for signup
35 Fig 3.2 sequences diagram for login
36Fig 3.3 sequences diagram for modify password
37
Fig 3.4 sequence diagram for profile page
3.3 Activity Diagram DefinitionThe process flows in the system are captured in the activity diagram. an activity
diagram also consists of activities, actions, transitions, initial and final states, and
guard conditions.
Use case: Access Home page
all visitors first access the home page ,in this page user whom are not create a user
account can create account and user who have an account can login to the profile
page.
Use case: user Home page
After create account users get the profile page and can edit all information that the
user want.
Use case: user profile page
User can upload photo edit there general information.
3.4 Activity diagram
In Unified Modeling Language (UML), an activity diagram is a graphical
representation of an executed set of procedural system activities and considered a
state chart diagram variation. Activity diagrams describe parallel and conditional
activities, use cases and system functions at a detailed level.
38
39
Fig 3.5 activity diagram for signup
40Fig 3.6 activity diagram for login
41Fig 3.7 activity diagram for upload picture
3.5 Class DiagramA class diagram provides an overview of a system by showing its classes,
interfaces, and collaborations and the relationships among them. In the UML
notation, a class is represented as a rectangle divided into several parts: class name,
attributes (fields), operations (methods), and others:
42
43
3.5.1 Description of Class Diagram
Class name: college
Attributes:
Collegeid
- Unique identification character of college.
- It has bigint data type.
- Max-size-10
Collegename:
- It identify name of college.
- It has varchar data type.
- Max-size 50.
Collegelocation:
- It tells us the place of the college.
- It has varchar data type.
- Max-size-50
Class name: Useraccount
Attributes:
Firstname:
- It identify first name of user.
- It has varchar data type.
44
- Max-size 25.
Last-named:
- It identify last name of user.
- It has varchar data type.
- Max-size 25.
Email:
- It tells us the e-mail id of user.
- It has varchar data type.
- Max-size-30
Password:
- It identifies the password of user.
- It has varchar data type.
- Max-size 30.
Comfirmpassword:
- It identifies the password of user.
- It has varchar data type.
- Max-size 30.
Sex:
- It identifies gender of users.
- It has varchar data type.
- Max-size 10.
DOB (Date of Birth):
45
- Date birth of user.
- It has date data type.
Method:
Register ():
- It helps to register user’s full information.
Class name: profile
Attributes:
Firstname:
- Identifies the first name of the user.
- It has varchar data type.
- Max-size 25.
Lastname:
- Identifies the last name of the user.
- It has varchar data type.
- Max-size-25
Email:
- It uniquely identifies the user.
- It has varchar data type.
- Max-size 30.
Status
- Used to specify the status of the user, for instance single, married.
46
- It has varchar data type.
- Max-size 15
College:
- Used to specify the college of the users.
- It has varchar data type.
- Max-size 15
Sex:
- Used to specify the gender of the user.
- It has varchar data type.
- Max-size 10
Qualification:
- Used to specify the education status of the user.
- It has varchar data type.
- Max-size 15
PhoneNo:
- The phone number of the user.
- It has varchar data type.
- Max-size 20
DOB:
- Used to specify the birth date of the user.
- It has date data type.
- Max-size 15
47
Method:
Edit ()
- It used to edit profile
Update ()
- It is used to change profile.
- .
Class name: chat
Attributes:
Chat-id:
- Unique identification chat.
- It has MediumInt data type.
- Max_size-8
User_Id:
- It identifies Id of sender.
- It has mediumInt data type.
- Max-size 8.
To:
- It tells us the receiver.
- It has varchar data type.
48
- Max-size-25
Msg:
- It identifies the instant message.
- It has varchar data type.
- Max-size 1000.
Create_at:
- It identifies the time of the chat is created.
- It has timestamp data type.
- Max-size 10.
Method:
Send ():
- It helps to transfer the instant message.
Class name: Message
Attributes:
message-id:
- Unique identification message.
- It has MediumInt data type.
- Max_size-8
message:
49
- It identifies message it self.
- It has mediumInt data type.
- Max-size 1000.
Create_at:
- It identifies the time of the message is created.
- It has timestamp data type.
- Max-size 10.
Is_read:
- It tells us the message is read or not.
- It has boolean data type.
- Max-size-10
Is_spam:
- It tells us message is real message or not.
- It has boolean data type.
- Max-size 10.
To:
- It tells us the receiver.
- It has varchar data type.
- Max-size-25
Replay:
- It tells us replay the message.
- It has tinyint data type.
- Max-size-1
50
User_Id:
- It identifies Id of sender.
- It has mediumInt data type.
- Max-size 8.
Method:
Send ():
- It helps to transfer the instant message.
Class name: image
Attributes:
Image-id:
- Unique identification of image.
- It has varchar data type.
- Max-size-10
Imagename:
- It identify name of image.
- It has varchar data type.
- Max-size 15.
Imageformat:
- It tells us the extension of images.
- It has varchar data type.
- Max-size-25
51
Uploadimage:
- It identifies the path of the image file.
- It has varchar data type.
Method:
Upload ():
- It helps to upload images.
Delete ()
- It helps to delete uploaded image.
Change ()
- Modify the uploaded image.
Class name: video
Attributes:
Video-id:
- Unique identification of video.
- It has varchar data type.
- Max-size-10
Video name:
- It identify name of Video.
- It has varchar data type.
- Max-size 15.
Video:
52
- It tells us the extension of Video s.
- It has varchar data type.
- Max-size-25
UploadVideo:
- It identifies the path of the Video file.
- It has varchar data type.
Method:
Upload ():
- It helps to upload Videos.
Delete ()
- It helps to delete uploaded Video.
Change ()
- Modify the uploaded Video.
53
Chapter Four
System Design
4.1 Introduction In the first phase of the project or in analysis scope, the functionality, the feasibility, the reason to develop a proposed system and all other feature are showed in detail.
Here in the design phase of the HU intranet social networking site the decomposition of the developed system is explicitly showed, the Hardware software mapping and the architecture for the proposed system is also the part of the design in intranet social networking site.
4.2 Design goalIn this section we will see the different type of class type architecture such as user interface, process/control, business/domain, persistence and system layers and also different type of system modeling techniques that are used for the implementation of the system such as class, state chart, component and deployment modeling. Also some system design techniques such as user interface, training and maintenance design are also to be covered in this design chapter.
The design goals are derived from non-functional requirements that mean non-functional requirement is the description of the feature characteristics and attributes of the system as well as any constraints that may limit the boundary of the proposed solution.
In short non-functional requirement means the necessity of the system (new one) that is not directly related to the functional of the new system. These requirements don’t directly affect the performance of the system but nevertheless important. In most cases the design goal of a system is similar to the non-functional requirement. The access control of the system, hardware software mapping, boundary condition and similar features of the system is shown here. The following are the design goal of the system:
Reliability: the system should be reliable.
54
Fault Tolerance: the system should be fault tolerant to loss of connectivity with the service.
Security: the system should be secure, i.e., not allow other users or unauthorized users to access data that don’t concern with them.
Modification: the system should be modifiable for further modification and enhancement of the application.
4.3 Hardware/Software mapping
4.3.1 SoftwarePHP: PHP, or PHP hypertext processor, is the language in which durable is written. Recently it has received a major upgrade and is now more or less a fully functional object oriented language, with some very power full features.
MYSQL: this is the database software that we will use to store all the information required to keep the web site running. Everything from the user details to product information and a host of other things will be stored in the MYSQL database.
Software at server side:
Windows XP server 2003
Linux
Windows 7
Software at clients’ side:
Ms-Internet Explorer
Mozilla Firefox
Google Chrome
opera
55
4 .3.2HardwareThe system will use the following hardware:
256 MB Min. RAM
Intel® Core™2 Duo CPU
40 GB Min. HDD
4.4 Access control and securityOur HU intranet social network website covers the system like chat, news, messaging and upload picture and video, our web site accessed by different account levels.
The administrator can access the entire module as needed including adding, updating and searching.
The other users also have granted to view and access the module allowed for them like editing their own profile, invite friends and sending messages.
Generally, the system administrator controls all user names, passwords and user activities.
4.5 Object designDuring the object design phase of the HU intranet social network web site is between reusability, portability and efficiency-cost.
Performance: - The performance of the system includes response time, the ability and speed of system while the system is running like for login, registration searching and etc.
Flexibility: - the system is flexible it is easy to configure and tight to get the maximum performance. Therefore, flexibility is higher priority than performance.
4.6 User interface prototypeThe sample user interface of HU intranet social networking site for sin up and validation is the following.
56
Sin up user interface form
Sin up validation
57
Login user interface
4.7 Database DesignThe sample data base design of the HU intranet social network is look like the following.
58
List of tablesTable 2.1 access home page user description
Table 2.2 user home page use case description
Table 2.3 logout page use case
Table2.4 use case description of profile
Table 2.5 use case description for massages
Table 2.6 use case description for picture
Table 2.7 use case description for friends
List of figureFig. 2.1 functional requirement
Fig.2.2 use case diagram
Fig 2.3 essential use interface flow
Fig 2.4 user update flow diagram
59
Fig 2.5 create account prototype
Fig 2.7 change password prototype
Fig 3.1 sequences diagram for signup
Fig 3.2 sequences diagram for login
Fig 3.3 sequences diagram for modify password
Fig 3.4 sequences diagram for profile page
Fig 3.5 activity diagram for signup
Fig 3.6 activity diagram for login
Fig 3.7 activity diagram for upload picture
Fig 3.8 class diagram
List of Abbreviations and NomenclatureHU: Haramaya University
E-mail=Electronic Mail
SQL=Structural Query Language
PHP=Hypertext Preprocessor
HTML=Hyper Text Markup Language
MB=Mega Byte
RAM=Random Access Memory
GB=Gaga Byte
60
HDD=Hard Disk Drive
CPU=Central Processing Unit
MS= Microsoft
LAN =Local Area Network
CSS= Cascading stale shit
N\A= Not applicable
DB=database
UN/PN= Username and Password
UI=user Interface
DOB=date of birth
MSG=Message
Max=Maximum
Fig=Figure
Conclusions
We have included the project in four chapter and each chapters have its own descriptive introduction. All the necessary for project documentation mentioned the above such as, use case diagram with their description, sequence diagram with their definition.
Generally we have included all the content in to three chapters with clear description.
61
62