You are on page 1of 5

J.

΢ he objectives of Labour
΢ he objectives of teamwork half of the course of the Database is to allow
groups of 3 persons to familiarize themselves with the cycle of database
application (ie, conceptual design, logical design, schema refinement, physical
design and implementation of applications using the database and of the
security mechanisms).
΢ this text, you have the requirements analysis of a hypothetical system of
Social Networking SocialFace, which allows groups of users to "interact" on
the Internet through an application to be installed on their computer. The
groups are invited to model conceptually described the application and then
implement it using commercial relational database Microsoft SQL Server
2008 R2. The implementation of the application should be done with the
programming language JAVA. ΢ the end of the work will be competition which
will be rewarded with the best achievement award from Microsoft Cyprus.
The implementation of the project will be divided into the following two phases:
Yasi A - ΢ chediasi Base (30%)
 Conceptual ΢ chediasi with Frisi ER Diagram of the DDS Toolkit.
 Logic ΢ chediasi ΢ chesiakou ΢ of vehicle (ANSI or TSQL types, constraints,
etc.)
Yasi B - Tlopoiisi Base (70%)
 Tlopoiisi of ΢ chesiakou ΢ vehicle in SQL Server (ie, TSQL-DDL).
 Tlopoiisi Operations (query, import, amendments and reports) in TSQL DML.
 Tlopoiisi ΢ YSTEMS interface (graphical or otherwise) in JAVA to access the
data in the database.
 Yysiki ΢ chediasi to optimize performance.
 Sekmiriosi (as described in Section V of this document)
II Introduction
Shaw Social Networking System SocialFace, is a new social networking
company which will operate in the area of providing advanced services to our
customers / users. After the successful graduation from the University of
Cyprus, SocialFace has decided to offer to your team full implementation of the
database will support the above application. ΢ onsequently will operate both as
the Basis Administrators (DBA - Database Administrator) and as ΢ chediastes
Base and application developers. Part of your duties is to design and implement
the database and interface system which implements the functions as
described later in this document specifications.
III. Data Description
΢ service SocialFace can register as a user first enters in a system
requirements (as outlined below as part of the profile). Shaw system then
verifies the identities of users to access the application (via username /
password). ΢ more, other users can view a user profile and add as a friend.
Therefore beyond the information given by the user in the system must be
stored and information about his social network (who is a friend who! )
D1) Friston Profile
For each user must be kept The identity of the user.
information on their profile. ΢
ygkekrimena for each profile
requires the following information:id
first_name Shaw name.
last_name Shaw name of the user.
name Shaw system must be able to display
full user.
link A link to the profile.
birthday Date of birth.
work A list of employers in user (current
and previous employers).
education A list of institutions that have been
watched by the user.
email The email address of the user.
website A link to the website user.
hometown The city of birth of the user. Shaw
system must make a comprehensive
list of cities from which the user
chooses.
location The city where he lives now by the
user. Shaw system must make a
comprehensive list of cities from
which the user chooses.
quotes A list of favorite sayings of the user.
gender Shaw gender of the user.
interested_in A list of user interest. Shaw system
must make a comprehensive list of
interests from which the user
chooses (the list will then be given
along with other application data)
verified Whether the user has confirmed his
account or not when record (via
electronic mail address).

Obviously not all of the above mentioned elements required. Apart from the identity, name and date
of birth must specify you anymore other than the above is required. Selo note that the above as well
as subsequent descriptions, not the shape of an individual relationship, but may involve multiple
correlated relationships. Set on the final structure of the database will have to identify yourself.
D2) Photo Album
A user can set a photo album. For The identity of the album.
each album should be the
following information: id
from The identity of the user who created
the album.
name The title of the album.
description The description of the album.
location The city in which the photographs
were taken out on the album (using
the list of cities for the system)
link A link to the album.
privacy The privacy settings for the album.
(Explained below)
count The number of photo albums.
comments Like a guest who have several users
on the album.
photos The photos in the album.

΢ imeioste that the system there are four possible arrangements of personal privacy:
 OPEN: ΢ imatodotei that this subject is open for viewing and searching to all
users of the system.
 CLOSED: ΢ imatodotei that this subject is closed to view and search all
users of the system (ie above has access to only the owner).
 FRIEND: ΢ imatodotei that this subject is open for viewing and search
through all the immediate friends of the owner (ie, those who have accepted as
friends and also those who have accepted as a friend).
 NETWORK: ΢ imatodotei that this subject is open for viewing and searching
users from the network owner. Shaw network users a user contain all users who
are more than 3 levels away (friend of a friend of a friend of the user).
Obviously the system must be able to store information about what other
people are friends of a particular user as described in paragraph (7). As in the
profile, the final form of the relationship (the relationship) to have the system
needs to draw you. Generally for all data presented in this calling is the last
comment
D3) Yotografies
For each photo a user need the The identity of the photo.
following information: Id
from The identity of the user who
created the photograph.
source The photo.
height Equal amount of image in
pixels
width Shaw width of the image in
pixels
link A link to the photo.
likes The list of users who like the
photo.

D3) Yotografies
For each photo a user need the The identity of the photo.
following information: Id
from The identity of the user who
created the photograph.
source The photo.
height Equal amount of image in
pixels
width Shaw width of the image in
pixels
link A link to the photo.
likes The list of users who like the
photo.

D4) Video
For each video a user need the The identity of the video.
following information: id
from The identity of the user who
created the video.
message A title for the video.
description A description for the video.
length The duration of the video in
seconds.
comments Like comments have made
various users for video.

D5) ΢ yndesmoi
Each user can store some links that The identity of the
will appear in the profile. For these link.
links we need the following
information: id
from The identity of the
user who created the
link.
link Shaw actual URL of
the link.
name Shaw's name link.
caption The caption of the
link (shown after the
name).
description The description of the
link (shown following
the caption).
message An optional message
from the user link.
D6) ΢ ymvanta
Each user can provide information on an The identity of
event (eg a play or a presentation, the incident.
etc.). Subsequently, other users can indicate
whether or not to participate in this
event.For these events we need the
following information: id
owner The identity of
the user who
created the
incident.
name The title of the
event.
description The description.
start_time The date and
time of the
incident.
end_time The date and
time of the
incident.
location The detailed
location of the
incident.
venue The city of the
event (using the
list of cities

privacy The privacy settings for the event.

D7) Manage friends


A user can search for other users of the system (see functions) and to ask
another user to become his friend. Obviously the system must record these
requests as well as the response to these requests.
When a user accepts a T friendship requests from F, then this should lead to
the inclusion of T in the friends list of F and vice versa (ie, the F to include
friends of T).