Aurkut - A social Networking website

45,758 views

Published on

A complete project report to Design and Developed a social network website through ASP.NET and C#.

Regards
Abhijeet Kalsi

Published in: Technology, Business
120 Comments
111 Likes
Statistics
Notes
No Downloads
Views
Total views
45,758
On SlideShare
0
From Embeds
0
Number of Embeds
457
Actions
Shares
0
Downloads
48
Comments
120
Likes
111
Embeds 0
No embeds

No notes for slide

Aurkut - A social Networking website

  1. 1. Project Report By Student: Abhijeet Singh KalsiGURU NANAK INSTITUTE OF MANAGEMENT Affiliated to Guru Gobind Singh IndraPrastha University [GGSIPU] 1
  2. 2. ACKNOWLEDGEMENT Exchange of ideas generates the new object to work in a better way whenever aperson is helped and cooperated by others his heart is bound to pay gratitude andobligation to them. To develop a project is not a one-man show. It is essentially acollective work, where every step taken with all precautions and care. Therefore our first duty is to thanks all persons who provided me with basic helpin forming the outline and strategy for my humble effort. We thank Mr. MANOJ SINGHAL, Ducat Training Institute, Noida, who gave usinspiration to do work in this field and gave us her precious time whenever needed,.Thanks may be matter of merely formality but with us it is expression of heartfelt gratitudeto our project supervision. We are highly indebted for her gestures, invaluable suggestionsand boosting confidence to make this successful. The success of this work is mostly dueto her suitable guidance. 2
  3. 3. CERTIFICATE This is to certify that the project entitled “AURKUT, A Social NetworkWebsite“ prepared by Abhijeet Singh Kalsi for the partial fulfillment of therequirements of the MCA degree as a part of Summer Vocation CollegeTraining of Microsoft Dot Net Technologies, through Ducat Training Institute,Noida embodies the work, we all are doing after the 2th semester of ourcourse under due supervision of the supervisor from this college. SIGNATURE: [Mr. Manoj Singhal ] 3
  4. 4. S.No. Contents Page No. Introduction 1.1 Abstract 1.2 Objective 51 1.3 Scope 1.4.3 ) System Requirements 1.4.1) Hardware 1.4.2) Software Project Management 9 2.1 Software Process Model 2.2 Team structure2 2.3 Project Plan 2.3.1 Risk Planning 2.3.2 Project Scheduling Requirement Analysis 13 3.1 ) Rules3 3.2 ) Algorithms Design4 28 4.1 Screen Shots 4.2 C#.NET and ASP.NET Coding / Programming 4
  5. 5. 5
  6. 6. 1.1) ABSTRACT People have used the idea of "social network" loosely for over a century to connotecomplex sets of relationships between members of social systems at all scales, frominterpersonal to international Our project aims at using Microsoft Dot Net Technologies using Visual Studio 2010Professional Edition to make a social Networking Website. In our project we will useASP.NET for the Designing interactive interface or Presentation Logic at Front End andAJAX (Asynchronous JavaScript Xml) to design the website, C# (sharp) for business logicdevelopment and Microsoft SQL 2005 a Database Management System for themanipulation of database of user at Back End.1.2) OBJECTIVE  To have an Attractive and Secure Login page to access.  Make new user account in more user friendly and proper validation of details.  Search Friends easily on entire network.  Send Friend request to other users to make friends.  Add friends to your Friend box to accept request.  Creating a public profile having social, professional and personal information.  Ease of editing of profile anytime you need.  Upload and Share Photographs on network.  Add, Search and shares videos of Youtube.  Send messages to other friends in terms of Scrapbooks. 6
  7. 7.  Reply directly to incoming user scraps  Administration page to keep an eye on user operation.  Easily password recovery processing.1.3) Future SCOPE Of The PROJECT Scope of this project is that we can add a features of User based Communities andLive Chat Server for online user.  User Communities  Online Chat Server  Privacy of user information among other person on network  Games & other Application  A Wall to comment and share information on network. 7
  8. 8. 1.4) Minimum SYSTEM Requirements 1.4.1) SOFTWARE REQUIREMENTS  Compiler – Microsoft Visual Studio 2008 or 2010.  Database: Microsoft SQL Server 2005 or higher.  Operating System –Any platform with internet enable Web Browser.  An IIS (Internet Information Service) install on the OS.  Graphics card - Direct 9X compatible Graphic and Flash Player plugins.  Sound Card – DirectSound compatible sound card. 1.4.2) HARDWARE REQUIREDMENTS  Processor – Pentium4 and above.  Memory - 512MB and above.  Storage – 4 GB Free Hard Drive Space (installed ).  Color Monitor  Keyboard and Mouse  A pair of Speakers.  A Internet Connection. 8
  9. 9. Chapter - 2 9
  10. 10. Project Management Project management includes planning, monitoring and control of people, process, tasksand events that occur during the project development process. It is a very necessary activity for thecomputer based projects. Project management process includes all those activities that run duringthe whole duration of the project. The scope of the project management differs with the persondoing it. A software engineer manages his day to day activities, planning and monitoring of itstechnical tasks. A project manager plans, monitors and controls the work of a team of softwareengineer. Senior manager controls the interface between the business and the softwareprofessionals. Building software being a complex task makes project management very importantpart of software building process.The management spectrum involves the focus on 4 P’s.1.) People:- It is base framework, defining the people management, recruitment, selection, and training2.) Product :- Defining the objectives and scope3.) Process:- Defining the framework for activities4.) Project:- Management of project is the only defined way to manage the complexity of the project.2.1 Software Process Model:-To solve actual problems in a project, a software engineer or a team of engineers must incorporatea strategy that encompasses the process, methods and tools that are focused on the softwarequality. This strategy is called as a process model or a software engineering paradigm. 10
  11. 11. In this project we have used incremental model. Incremental model: - In this model all the basic requirements of the clients are beingstudied and first increment is delivered (also called as core product) and many supplementaryfeatures remain undelivered. Then a plan is developed for the next increment while the firstincrement is under review or evaluation by the user. Then the plan addresses the modification ofthe core product focusing on other requirements of the user. This process is repeated until all therequirements are not fulfilled. This can also be considered in a way that customer has provided allhis requirements and we divide it into phases. In this no integration is required as the newincrement is overwritten on the existing one.2.2 Team Structure:- The team structure is DEMOCRATIC DECENTRALISED (DD). The team comprises of singlemembers:--  ABHIJEET SINGH KALSI Decentralized teams generate better solutions and have greater probability of success whenworking on different problems. DD team structure is best applies to programs with low modularity. Based on the difficulty of the problem to be solved relatively low modularity of the project andhigh volume of the communication required a democratic decentralized team structure is proposed.This software engineering team has no permanent leader. Rather, “task coordinators areappointed for short duration and then replaced by others who may coordinate different tasks.”Problem solving is a group activity. Communication among team members is horizontal.Decentralized team generates more and better solutions than individuals. Therefore such teamshave a greater probability of success when working on difficult problems.2.3) PROJECT PLANSoftware planning involves estimating how much time, effort, money, and resources will berequired to build a specific software system. After the project scope is determined and the problemis decomposed into smaller problems, software managers use historical project data (as well aspersonal experience and intuition) to determine estimates for each. The final estimates aretypically adjusted by taking project complexity and risk into account. The resulting work product iscalled a project management plan. 11
  12. 12. Panning includes:-1. Risk Planning.2. Project Scheduling.2.3.1 Risk Planning:- Risk is an event that delays or destroys the project thus affecting the cost. Planning andmanagement of risks are intended to help a software team to understand and manage theuncertainty during the development process. Thus plans are made not only to understand the riskuncertainty but also to minimize the impact when things go wrong.The steps involved in risk management are: Risk identification Analyzing risk and assessing the damage that it will do Ranking the risk according to probability of occurrence and impact Developing a plan to manage the risks with high probability and high impact The work product of Risk is management is called as Risk Mitigation, Monitoring andManagement Plan (RMMM).Risk Strategies:- Reactive strategies – very common, also known as fire fighting, project team sets resources aside to deal with problems and does nothing until a risk becomes a problem. Proactive strategies - risk management begins long before technical work starts, risks are identified and prioritized by importance, then team builds a plan to avoid risks if they can or minimize them if the risks turn into problems.2.3.2 Project Scheduling:-  Activity that distributes estimated efforts across the planned project duration by allocating the effort to specific software engineering tasks.  Network of software engineering tasks that will enable the job to get accomplished on time.  Done to avoid lateness in project. 12
  13. 13. SCHEDULE IS AS FOLLOWS:-SNO. PROCESS/ PHASE START DATE END DATE 1 Requirement Gathering 26/ June / 2010 30/ June / 2010 2 Requirement analyses 3/ July / 2010 4/ July / 2010 3 Screen design 5/ July / 2010 18/ July / 2010 4 Pseudo code 19/ July / 2010 25/ July / 2010 5 Coding 26/ July / 2010 8/ August / 2010 6 Testing 10/ August / 2010 15/ August / 2010 13
  14. 14. Chapter-3 14
  15. 15. Requirement Analysis This is also known as feasibility study. In this phase, the development team visits thecustomer and studies their system. They investigate the need for possible software automation inthe given system. By the end of the feasibility study, the team furnishes a document that holds thedifferent specific recommendations of what all is to be done for the system. It also includes thepersonnel assignments, costs, project schedule, and target dates. The requirements gatheringprocess is intensified and focused specially on software. To understand the nature of theprogram(s) to be built, the system engineer ("analyst") must understand the information domain forthe software, as well as required function, behavior, performance and interfacing. The essentialpurpose of this phase is to find the need and to define the problem that needs to be solved.Broadly, what all has to be done in the whole project has been documented on the basis ofdetailed study made in this phase. The work product developed by the analysts at the end of analysis phase is SoftwareRequirement Specification Document (SRS). This document is comprised of:-processspecifications, data object specification, control specification. And the system is being designedkeeping in mind all the information gathered in this document._____________________________________________________________3.1) DATA DICTIONARY It is a basic building block. It is an organized listing of data objects/entities (with theirattributes/fields) that are relevant to the system, with precise clear definitions.Entities and their attributes in the project:-3.2) ENTITY RELATIONSHIP DIAGRAM An Entity Relation Diagram (E.R.D) is a graphical tool used to describe and analyze themovement of data through the system-manual or automated-including the Entities, the relationsbetween different entities and the attributes of different relations or attributes are the central tooland the basis from which other components can be developed. While drawing the ERDs, theapproach as given by Yourdon has been followed. The Symbols used in the E.R.D are. SYMBOL MEANING RELATIONS ATTRIBUTES ENTITIES 15
  16. 16. ENTITY RELATIONSHIP DIAGRAM Sex Address Phone Email Lname Userid Name CUSTOMER Fname DOB Image State Country Password City Authenticates Id Password Make Friends ADMINISTRATOR Name Userid Friend Send CUST_FRIENDS ScrapsImage Fname Request Userid Scraps CUST_SCRAPBOOK A Friendid Image Fname 16
  17. 17. A View / Upload Pname CUST_PHOTOS View / Edit Photos Org Degreecareer Year CUST_PROFESSIONAL ColgIndustry Edu. Occupation Aboutme Martial Hobbies Religious URL CUST_SOCIAL Smoke Drink Passion Music Sports Movie 17
  18. 18. 3.3) DATA FLOW DIAGRAM It is a pictorial representation of Business processes (functions/services/activities), alongwith the data flow.  Software process:-Guides how the software is being built.  Business process:-Specific to organization, e.g.:- In this project; issuing ticket, canceling ticket. In this focus is on what data flows and not how the data flows. When all the analysis isbeing made then we develop a diagram to depict the analysis, and following symbols are beingused:- SYMBOL MEANING Process External Entity Data Item Data Store 18
  19. 19. DATA FLOW DIAGRAM0 Levels DFD:- SERVER ADMINISTRATION Provides Authentication Social Networking System Register an Account Developed Profile CLIENT 19
  20. 20. Chapter - 4 20
  21. 21. Design is a meaningful engineering representation of something that has to be built. It cande traced according to a customer’s requirements and at the same time assessed for qualityagainst a set of pre-defined criteria for a “good” design. In the software contexts, design focusesfour major areas of concern: 1. Data 2. Architecture 3. Interfaces 4. ComponentsTRANSLATION OF ANALYSIS MODEL INTO SOFTWARE DESIGN:- Data design - created by transforming the analysis information model (data dictionary and ERD) into data structures required to implement the software Architectural design - defines the relationships among the major structural elements of the software, it is derived from the system specification, the analysis model, and the subsystem interactions defined in the analysis model (DFD). Interface design - describes how the software elements communicate with each other, with other systems, and with human users; the data flow and control flow diagrams provide much the necessary information. Component-level design - created by transforming the structural elements defined by the software architecture into procedural descriptions of software components using information obtained from the PSPEC, CSPEC, and STD.4.1) DATABASE DESIGN:- In this we analyze the work product of requirement analysis, and from that we use datadictionary to design the database. Entities are represented in a tabular form containing the list oftheir attributes. These are in specific the files that are being referred at the time of data flow. Entities (Files) that are being used in the system:- 1) Aurkut_user 2) Cust_professional 3) Cust_social 4) Cust_friends 5) Cust_scrapbook 6) Cust_photos 21
  22. 22. Relational Database Schema’s Aurkut_userFname Lname Sex userid Password Email Dob Phone Address City State Country Image Cust_professional userid edu Degree year Colg occupation industry org career Cust_socialuserid martial religious smoke drink url aboutme passion sports music movie hobbies Cust_friends userid friend request fname image Cust_scrapbook userid friendid scraps fname image Cust_photos userid photo pname 22
  23. 23. Chapter - 5(Screen Shots) 23
  24. 24. Login.aspx 24
  25. 25. Signup.aspx 25
  26. 26. Home.aspx 26
  27. 27. Search.aspx 27
  28. 28. Profile.aspx 28
  29. 29. 29
  30. 30. Edit_Profile.aspx 30
  31. 31. 31
  32. 32. Scrapbook.aspx 32
  33. 33. Friends.aspx 33
  34. 34. Photos.aspx 34
  35. 35. Videos.aspx 35
  36. 36. Recovery.aspx 36
  37. 37. Admin.aspx 37
  38. 38. 38
  39. 39. Developer.aspx 39
  40. 40. Aboutus.htm 40
  41. 41. Chapter – 6(Website Development) Mail me at Abhi_Jeet@Ymail.com Mb: 9971070672 (New Delhi) 41
  42. 42. Chapter – 7 42
  43. 43. Conclusion 43

×