Introduction

Page 1 of 52

An Campus Orkut (3-Tire Arch) is an online community that lets you meet your friends friends. It's where people meet with people online, get to know each other, interact, and share ideas with each other, just like a real community. Campus Orkut (3-Tire Arch) not only allows users to manage and archiving mailing list, but also provides a method for true communication and collaboration with group members. It provides ads for various pages. Sharing of information has become a necessary event for todays world. In this group you can share scraps, messages, photos, etc. you can also share videos. In other groups you cant scrap with others in the group but in this Campus orkut you can scrap to anyone in the group.

Features:

The information of the entire firm will be maintained at a centralized data base any Provide Interactive interface through which a user can interact with different areas Deploy the application on a single system and make is available on all the systems

changes made by the other departs are known to the higher or lower departments instantly. of application easily within the network, thereby reducing the maintenance cost of software.

Page 2 of 52

PURPOSE OF THE SYSTEM

Make own community. Join a community. Share photos and member information Share Photos. Search or browse for communities and friends in the group. Can share scraps. The System provides users to view scraps of friends or friend friends in the group by which the user can send scraps. Send Testimonial to friends and receive Testimonial from friends

Page 3 of 52

System Analysis and Software Requirement Specification

Page 4 of 52

2.1 EXISTING SYSTEM

The examples for the existing system are: 1. Orkut Groups. 2. Facebook Groups. The Existing System doesnt provide video sharing. With the existing system users can scraps and messages to group users only.

Functionalities of Existing system:

Register with group. Create your own Community. Join in a Community. Photos sharing. Message archives. Post Messages. Scraps archives Post scraps. Search or Browse for friends.

Page 5 of 52

Drawbacks of Existing system:

Users cant chat with the friends. Users can not share Testimonial.

2.2 Proposed System

NEED FOR NEW SYSTEM

The existing system has a lot of drawbacks as said earlier. Considering these drawbacks in mind the proposed system is developed. The proposed system is to provide features to share Testimonial and chat with friends.

Functionalities of Proposed System:

Make own community. Join a community. Share photos and member information Share Photos. Search or browse for communities and friends in the group. Can share scraps.

Page 6 of 52

 The System provides users to view scraps of friends or friend friends in the group by which the user can send scraps.
Send Testimonials to friends and receive Testimonials from friends

2.3 Hardware and software Requirements

HARDWARE REQUIREMENTS
PROCESSOR RAM HARD DISK : : : P-III or Above 512MB 40 GB

SOFTWARE REQUIREMENTS

OPERATING SYSTEM DATA BASE PROGRAMMING LANGUAGE TECHNOLOGY SERVER

: : : : :

WINDOWS XP SQLSERVER 2005 C#.NET ASP.NET IIS 6.0

Page 7 of 52

SYSTEM DESIGN

Page 8 of 52

3.1 UML DIAGRAMS:

Use-case diagrams graphically represent system behaviour (use cases). These diagrams present a high level view of how the system is used as viewed from an outsiders (actors) perspective. A use-case diagram may contain all or some of the use cases of a system.

The actors identified in the system are: Administrator

Registered user Anonymous user

Identification of Use cases:

Definition: Use case is a sequence of transactions performed by a system that yields measurable result of values for a particular actor. The use cases are all the ways the system may be used.

Use cases Identified by this system are: login Creating a community Join a community Leave a community Delete a community
Page 9 of 52

 Manage photos Share photos and member info Send scraps

USECASE DIAGRAM

Page 10 of 52

login

Home

uses profilesettings uses

uses uses uses Changeprofile photo uses

uses uses uses

scrapbook

uses uses friend uses

user

Albums uses

uses uses

Testimols

uses

Friend Request

change password

communities

logout

Fig: Overall Use Case Diagram

Page 11 of 52

ACTIVITY DIAGRAMS:
Definition: An Activity diagram is a variation of a special case of a state machine, in which the states are activities representing the performance of operations and the transitions are triggered by the completion of the operations.

. Fig Overall Activity Diagram

Page 12 of 52

The above figure shows the overall activity diagram of the system. It consists of three actors namely member, Non-member and administrator. A Non member can only perform searching operations by viewing information he cant perform the functionalities provided by the system.

SEQUENCE DIAGRAMS:
A sequence diagram is a graphical view of a scenario that shows object interaction in a time based sequence--what happens first, what happens next. Sequence diagrams establish the roles of objects and help provide essential information to determine class responsibilities and interfaces. Purpose: To show the timely ordered object interactions. To provide readability. It is easy to find out the operations that belong to the particular class.

Join a community: User click on the Sign in link and then he has to enter Id & password details are forwarded to the administrator, after validation the user will enter into the groups home page. The user enters into particular group and click on join button. Make own community: User click on the Sign in link and then he has to enter Id & password details are forwarded to the administrator, after validation the user will enter into the groups home page. Manage Photos: User click on the Sign in link and then he has to enter Id & password details are forwarded to the administrator, after validation the user will enter into the groups home page.

Page 13 of 52

: user

joincommUI

joincommCC

database

1: click on sign in

2: enter id & pwd 3: forward 4: get details

5: verify id & pwd

6: enter into user's group

7: enter into particular group

8: click join button 9: forward 10: update database

Fig Sequence diagram for join a community

Page 14 of 52

: user :owncommUI 1: click on sign in 2: enter id & pwd

:owncommCC

:database

3: forward 4: get details

5: verify

6: user logs in 7: enter category of group

8: enter name,description for new group 9: enter user profile 10: forward all 11: invite members 12: forward 13: update

Fig Sequence diagram for create own community

Page 15 of 52

: user

:photosUI 1: click on sign in 2: enter id & pwd 3: forward

:photosCC

:database

4: get details

5: verify 6: user logs in

7: search photos and albums 8: create photos and albums 9: forward 10: update

Fig Sequence diagram for manage photos

Page 16 of 52

:profileUI : user 1: click on sign in 2: enter id & pwd 3: forward

profilecc

:database

4: get details

5: verify 6: user logs in 7: search for files 8: search member info. 9: open/create new files 10: forward 11: update

12: send files 13: forward 14: update

Fig Sequence diagram for Share members information Page 17 of 52

COLLABORATION DIAGRAMS:
A COLLABORATION DIAGRAM is an alternate way to show a scenario. This type of diagram shows object interactions organized around the objects and their links to each other.

1: click on sign in 2: enter id & pwd 7: enter into particular community 8: click join button

: user

joincommuniotyI

6: enter into user's community 3: forward 9: forward 4: get details 10: update database

5: verify id & pwd

joincommunitypCC

database

Fig Collaboration diagram for join a community

Page 18 of 52

1: click on sign in 2: enter id & pwd 7: enter category of group 8: enter name,description for new community 9: enter user profile 11: invite members

: user

:owncommunityUI

6: user logs in 3: forward 10: forward all 12: forward 4: get details 13: update

5: verify

:owncommunityCC

:database

Fig Collaboration diagram for create own community

Page 19 of 52

1: click on sign in 2: enter id & pwd 7: search photos and albums 8: create photos and albums

: user

:photosUI

6: user logs in 5: verify 3: forward 9: forward 4: get details 10: update

:photosCC

:database

Fig Collaboration diagram for manage photos

Page 20 of 52

1: click on sign in 2: enter id & pwd 7: search for profiles 8: search member info. 12: send files

: user 6: user logs in 5: verify 3: forward 10: forward 13: forward 4: get details 11: update 14: update

:profileUI

:profileCC

:database

Fig Collaboration diagram for share member information

Page 21 of 52

3.2 ER diagrams and tables

Page 22 of 52

Entity Relationship Diagram

Registration: Column Name First Name LastName Gender DOB Userid Pwd Email Alt_email Address S_question S_question Country Data Type Varchar(50) Varchar(50) Varchar(50) Datetime Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Registration Constraints Not null Not null Not null Not null Primary Key Not null Not null Not null Not null Not null Not null Not null

Page 23 of 52

Communities: Column Name Userid DataType Varchar(50) Constraints References(Registration userid) C_name C_date C_description Varchar(50) Datetime Varchar(200) Groups Primary Key

Friends:
Column Name idf userid friendid creationtime DataType Bigint Varchar(100) Varchar(100) Datetime Members Constraints Primary Key,

References(Groups g_name)

Page 24 of 52

Scraps:
Column Name Userid friendid scrapsub scraptext scraptime status Data Type Varchar(100) Varchar(100) Varchar(100) Varchar(500) datetime bit Messages Constraints Primary Key References

Photos: Column Name id photoname Userid photocaption status DataType bigint Varchar(100) Varchar(100) Varchar(100) bit Photos Constraints Primary Key,

References(Groups g_name) References(Registration userid)

Files:
Column Name fid G_name Data Type int Varchar(50) Constraints Primary Key References(Groups g_name)

Page 25 of 52

fname Extension fdesc fsize Creator Createdon

Varchar(50) Varchar(50) Varchar(200) int Varchar(50) datetime Files References(Registration userid)

Testimonials:
Column Name id userid friendid Testimonial text status Data Type bigint Varchar(100) Varchar(100) Varchar(500) bit Videos Primary Key Constraints

4.4. DATA DICTONARY:

After carefully understanding the requirements of the client the the entire data storage requirements are divided into tables. The below tables are normalized to avoid any anomalies during the course of data entry.

Page 26 of 52

Page 27 of 52

Page 28 of 52

Page 29 of 52

Page 30 of 52

Code and Implementation

Page 31 of 52

4 Modules:
The Entire Campus orkut project is mainly divided into three modules they are 1. Home 2. Friends 3. Communities
Page 32 of 52

Home: This is Module is further divided into five sub-modules, they are a) Profile Settings b) Maintaining Scraps c) Testimonials d) Profile Display e) Album maintenance Friends: This module is further divided into three sub-modules, they are a) Send Request To friends b) Remove Friends c) Display Friends list Communities: This module is further divided into four sub-modules, they are a) Community Maintenance b) Forums c) Events d) Polls

Page 33 of 52

Testing

Test cases in our system are as follows: Test Case# : 1 Priority(H,L): High

Page 34 of 52

Test Objective: Correct login details. Test Description: Userid and password are checked Requirements Verified: Userid and password are checked in the database Test Environment: Internet Explorer Test setup or Pre-conditions: User initiates any control mechanism like Submit or Go buttons Actions Incorrect login Expected Results A message Invalid userid/password will be displayed and allows the user to reenter the information. Enter into the My Groups Home Page. Correct Login Pass: Yes PrP Problems or issues: Nil Table 6.1 Test Case 1 Conditional Pass: Fail:

Test Case# : 2

Priority(H,L): High

Test Objective: For registration; to let the user enter all the required fields Test Description: All the necessary fields are checked Requirements Verified: All the necessary fields should be entered Test Environment: Internet Explorer Test setup or Pre-conditions: User initiates any control mechanism like Submit or Go

Page 35 of 52

buttons Actions Incomplete Necessary fields Expected Results Red colored * symbols will come against the incomplete fields and the user is allowed to complete those fields and form will not be submitted until that has been done.

Just check and go to sign in page. Completion of all the necessary fields Pass: Yes PrP Problems or issues: Nil Conditional Pass: Fail:

Table: 6.2 Test case 2

6.6 NAVIGATION TESTING:

The job of navigation Testing is To ensure that the mechanisms that allow the WebApp user to travel through the WebApp are all functional and To validate that each navigation semantic unit can be achieved by the appropriate user category.
Page 36 of 52

Navigation links: Internal links within the WebApp, external links to other WebApps and anchors within a specific Web page should be tested to ensure that proper content or functionality is reached when the link is chosen. Redirects: these links come into play when a user requests a nonexistent URL or selects a link whose destination has been changed. We have tested this by accessing the incorrect internal links and the test is completed successfully.

6.7 CONFIGURATION TESTING:

This attempt to uncover errors that are specific to a particular client or server environment. A cross-reference matrix that defines all probable operating systems, browsers, hardware platforms, and communication protocols is created. Tests are then conducted to uncover errors associated with each possible configuration.

6.8 SECURITY TESTING:

It incorporates a series of tests designed to exploit vulnerabilities in the WebApp and its environment. The intent is to demonstrate that a security breach is possible.

6.9 PERFORMANCE TESTING:

It encompasses a series of tests that are designed to assess (1) How the WebApp response time and reliability are affected by increased user traffic, (2)Which WebApp components are responsible for performance degradation and what usage characteristics cause degradation to occur, and (3) How performance degradation impacts overall WebApp objectives and requirements.

Page 37 of 52

2. Output Screens
The system uses a very user-friendly interface developed using extended markup language (XML) and hyper text markup language (HTML). Which most users are acquitted with and is broadly used on the World Wide Web (WWW). The controls are placed on the forms in an easily accessible manner so that user strain is minimized to the maximum extent.

The system also poses a unique format for each type of employee; this ensures that employee is presented with options he has access to. This ensures a great deal of security to the system and to the organization as an employee is not given an option to carryout unauthorized activity.

Login page:

Page 38 of 52

Home page:

Page 39 of 52

Page 40 of 52

Friend List:

Page 41 of 52

Communities Page:

Page 42 of 52

Albums:

Page 43 of 52

Profile Settings:

Page 44 of 52

Send Scrap:

Page 45 of 52

Upload photos:

Page 46 of 52

Create Community:

Page 47 of 52

Community page:

Page 48 of 52

Future enhancements

Page 49 of 52

This project has a huge scope and can be developed further by providing many useful services such as, e-mail services
mobile alerts,

Games Interactive Applications SMS services This project has a wide array of functionalities which can be added to the services listed above.

CONCLUSION
Page 50 of 52

Campus Orkut is a web site which is developed to allow users to share scraps, photos, messages, etc. The present system of groups doesnt provide sharing of videos and scrapping with friends. We provide these facilities which are very much interested to the users working on groups. The main objective of the system is to provide sharing of scraps and Testimonial the member of the groups orkut, Facebook. The system has been tested with sample data covering all possible options and its performance is good and is found to work effectively and efficiently.

Page 51 of 52

BIBLIOGRAPHY

[1] .Dietel, Dietel and Nieto, Internet and World Wide Web-how to program, Student Edition. [2]. Elmasri and Navathe, Fundamentals of Database Systems, 3rd edition, Addison Wesley, Pearson Education, Inc.2000 [3]. Pressman, Software Engineering-A Practitioners Approach, Sixth Edition, McGrawHill International [4]. Wrox, Professional ASP.NET 2.0, Special Edition

WEB REFERENCES
[1]. http://quickstarts.asp.net/QuickStartv20/aspnet/doc/ctrlref/data/gridview.aspx [2]. http://authors.aspalliance.com/aldotnet/examples/perldotnet.aspx [3]. http://www.aspfree.com/ [4]. http://msdn.microsoft.com [5]. http://groups.yahoo.com [6]. http://groups.google.com

Page 52 of 52