An Internet forum, or message board, is an online discussion site where people can hold conversations in the form of posted

messages.[1] They differ from chat rooms in that messages are at least temporarily archived. Also, depending on the access level of a user or the forum set-up, a posted message might need to be approved by a moderator before it becomes visible.Forums have a specific set of jargon associated with them; e.g. a single conversation is called a "thread". A forum consists of a tree like directory structure. The top end is "Categories". A forum can be divided into categories for the relevant discussions. Under the categories are sub-forums and these sub-forums can further have more sub-forums. The topics (commonly called threads) come under the lowest level of sub-forums and these are the places under which members can start their discussions orposts. Logically forums are organized into a finite set of generic topics (usually with one main topic) driven and updated by a group known as members, and governed by a group known as moderators.It can also have a graph structure.[8] All message boards will use one of three possible display formats. Each of the three basic message board display formats: Non-Threaded/Semi-Threaded/Fully Threaded, has its own advantages and disadvantages. If messages are not related to one another at all a Non-Threaded format is best. If you have a message topic and multiple replies to that message topic a semi-threaded format is best. If you have a message topic and replies to that message topic, and replies to replies, then a fully threaded format is best. Forums prefer a premise of open and free discussion and often adopt de facto standards. Most common topics on forums include questions, comparisons, polls of opinion as well as debates. It is not uncommon for nonsense or unsocial behavior to sprout as people lose temper, especially if the topic is controversial. Poor understanding of differences in values of the participants is a common problem on forums. Because replies to a topic are often worded aimed at someone's point of view, discussion will usually go slightly off into several directions as people question each others' validity, sources and so on.

2.SYSTEM REQUIREMENTS SOFTWARE REQUIREMENTS: Operating System : Windows XP Server. Web Server Server Script Database Platform : Internet Information Server. : ASP.NET, HTML. : MS Access 2007. : .NET Framework 2.0.

HARDWARE REQUIREMENTS: Processor Type HDD Capacity RAM Capacity Monitor Type Keyboard Mouse Resolution : : : : : : : Intel Pentium IV. 40GB. 512MB DDR RAM. 17 Monitor. 104 Keys. Scroll Mouse. 1024 by 768 pixels.

2.1 SOFTWARE DESCRIPTION: ASP.NET ASP.NET is a Web application framework developed and marketed by Microsoft to allow programmers to build dynamic Web sites, Web applications and Web services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET components to process SOAP messages. Goals of ASP.NET 2.0 Building on ASP.NET 1.1, the developers of ASP.NET 2.0 chose to focus on four goals:
1. Improve the reliability and usability of Web applications . 2. Reduce the number of lines of code you have to write in

common scenarios. 3. Offer user features to personalize Web applications . 4. Provide enhanced design features to generate consistent layouts and design. Development Tools ASP.NET 2.0 and Visual Studio 2005 also change many of the day to day aspects of Web application development. In this section, we will look at several of the areas where features available in ASP.NET 1.x have been heavily modified.The latest release of Visual Studio (Visual Studio 2005) includes several new development tools to help you build Web applications.

IntelliSense Now everywhere! Wizards to auto-generate code for many tasks. Designer support for master pages, themes and skins . Improved code editing features. Visual Studio 2005 includes a light weight Web server . Improved debugging environment .

Debugging applications In ASP is an arduous process, as code is interpreted on the fly. Syntax errors aren't exposed until you run applications. The debugging support is improved in Visual Studio 2005. Visual Studio .NET 2003 provided limited support for edit-and-continue debugging. Visual Studio 2005 improves edit-and-continue debugging and provides more information during the debugging process. For example, an improved implementation of DataTips provides information about variables and expressions as mouse popup windows during the debugging process. Visual Studio 2005 also provides additional features, like advanced debugging with breakpoints on disassembly, registers, addresses (when applicable), and "Just My Code Stepping". 2.3.2 Microsoft Office Access Microsoft Office Access, previously known as Microsoft Access, is a database management system from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical user interface and softwaredevelopment tools. It is a member of the Microsoft Office suite of applications, included in the Professional and higher editions or sold separately. On May 12 2010, the current version of Microsoft Access 2010 was released by Microsoft in Office 2010; Microsoft Office Access 2007 was the prior version.MS Access stores data in its own format based on the Access Jet Database Engine. It can also import or link directly to data stored in other applications and databases. Advantages of MS Access In addition to using its own database storage file, Microsoft Access may also be used as the 'front-end' with other products as the 'back-end' tables, such as Microsoft SQL Server and non-Microsoft products such as Oracle and Sybase. Multiple backend sources can be used by a Microsoft Access Jet Database (accdb and mdb formats). Similarly, some applications will only use the Microsoft Access tables and use another product as a front-end, such as Visual Basic or ASP.NET. Microsoft Access may be only part of the solution in more complex applications, where it may be integrated with other technologies such as Microsoft Excel, Microsoft Outlook or ActiveX Data Objects. Access tables support a variety of standard field types, indices, and referential integrity. Access also includes a query interface, forms to display and enter data, and reports for printing. The underlying Jet database, which contains these objects, is multiuser-aware and handles record-locking and referential integrity including cascading updates and deletes. Repetitive tasks

can be automated through macros with point-and-click options. It is also easy to place a database on a network and have multiple users share and update data without overwriting each other's work. Data is locked at the record level which is significantly different from Excel which locks the entire spreadsheet. Microsoft Access's role in web development prior to version 2010 is limited. User interface features of Access, such as forms and reports, only work in Windows. In versions 2000 through 2003 an Access object type called Data Access Pages created publishable web pages. Data Access Pages are no longer supported. The Microsoft Jet Database Engine, core to Access, can be accessed through technologies such as ODBC or OLE DB. The data (i.e., tables and queries) can be accessed by web-based applications developed in ASP.NET, PHP, or Java. Microsoft offers a runtime version of Microsoft Access 2007 for download. This allows people to create Access solutions and distribute it for use by non-Microsoft Access owners Unlike the regular version of Access, the runtime version allows users to use the Access application but they cannot use its design surfaces. Users can create tables, queries, forms and reports, and connect them together with macros. Advanced users can use VBA to write rich solutions with advanced data manipulation and user control. Access also has report creation features that can work with any data source that Access can "access".The original concept of Access was for end users to be able to "access" data from any source. Other features include: the import and export of data to many formats including Excel, Outlook, ASCII, dBase, Paradox, FoxPro, SQL Server, Oracle, ODBC, etc. One of the benefits of Access from a programmer's perspective is its relative compatibility with SQL (structured query language) queries can be viewed graphically or edited as SQL statements, and SQL statements can be used directly in Macros and VBA Modules to manipulate Access tables. Users can mix and use both VBA and "Macros" for programming forms and logic and offers object-oriented possibilities. VBA can also be included in queries. Development Access stores all database tables, queries, forms, reports, macros, and modules in the Access Jet database as a single file.For query development, Access offers a "Query Designer", a graphical user interface that allows users to build queries without knowledge of the SQL programming language. In the Query Designer, users can "show" the datasources of the query (which can be tables or queries) and select the fields they want returned by clicking and dragging them into the grid. One can set up joins by clicking and dragging fields in tables to fields in other tables. Access allows users to view and

manipulate the SQL code if desired. Any Access table, including linked tables from different data sources, can be used in a query. Access also supports the creation of "pass-through queries". These snippets of SQL code can address external data sources through the use of ODBC connections on the local machine. This enables users to interact with data stored outside the Access program without using linked tables or Jet.Users construct the pass-through queries using the SQL syntax supported by the external data source. When developing reports that are linked to queries placing or moving items in the design view of the report,

3.SYSTEM ANALYSIS: Systems are created to solve problems. One can think of the systems approach as an organized way of dealing with a problem. Inthis dynamic world, the subject System Analysis and Design (SAD),mainly deals with the software development activities. Objectives After going through this lesson, you should be able to: define a system explain the different phases of system development life cycle enumerate the components of system analysis explain the components of system designing

Defining A System A collection of components that work together to realize some objectives forms a system. Basically there are three major components in every system, namely input, processing and output.In a system the different components are connected with each otherand they are interdependent. For example, human body representsa complete natural system. We are also bound by many national systems such as political system, economic system, educational system and so forth. The objective of the system demands that some output is produced as a result of processing the suitable inputs. A well-designed system also includes an additional element referred to as control that provides a feedback to achieve desired objectives of the system. System Life Cycle System life cycle is an organizational process of developing and maintaining systems. It helps in establishing a system project plan, because it gives overall list of processes and sub-processes required fordeveloping a system.System development life cycle means combination of various activities. In other words we can say that various activities put together are referred as system development life cycle. In the System Analysis and Design terminology, the system.

4.FEASIBILITY STUDY: Feasibility studies aim to objectively and rationally uncover the strengths and weaknesses of the existing business or proposed venture, opportunities and threats as presented by the environment, the resources required to carry through, and ultimately the prospects for success.[1][2] In its simplest terms, the two criteria to judge feasibility are cost required and value to be attained.[3] As such, a well-designed feasibility study should provide a historical background of the business or project, description of the product or service, accounting statements, details of the operations and management, marketing research and policies, financial data, legal requirements and tax obligations.[1] Generally, feasibility studies precede technical development and project implementation. Five common factors: TELOS provides five common factors. Technology and system feasibility The assessment is based on an outline design of system requirements in terms of Input, Processes, Output, Fields, Programs, and Procedures. This can be quantified in terms of volumes of data, trends, frequency of updating, etc. in order to estimate whether the new system will perform adequately or not. Technological feasibility is carried out to determine whether the company has the capability, in terms of software, hardware, personnel and expertise, to handle the completion of the project. When writing a feasibility report the following should be taken to consideration: A brief description of the business to assess more possible factor/s which could affect the study. The part of the business being examined The human and economic factor The possible solutions to the problems

At this level, the concern is whether the proposal is both technically and legally feasible (assuming moderate cost). Economic feasibility

Economic analysis is the most frequently used method for evaluating the effectiveness of a new system. More commonly known as cost/benefit analysis, the procedure is to determine the benefits and savings that are expected from a candidate system and compare them with costs. If benefits outweigh costs, then the decision is made to design and implement the system. An entrepreneur must accurately weigh the cost versus benefits before taking an action. Cost-based study: It is important to identify cost and benefit factors, which can be categorized as follows: 1. Development costs; and 2. Operating costs. This is an analysis of the costs to be incurred in the system and the benefits derivable out of the system. Time-based study: This is an analysis of the time required to achieve a return on investments. The future value of a project is also a factor. Legal feasibility Determines whether the proposed system conflicts with legal requirements, e.g. a data processing system must comply with the local Data Protection Acts. Operational feasibility Operational feasibility is a measure of how well a proposed system solves the problems, and takes advantage of the opportunities identified during scope definition and how it satisfies the requirements identified in the requirements analysis phase of system development. Schedule feasibility A project will fail if it takes too long to be completed before it is useful. Typically this means estimating how long the system will take to develop, and if it can be completed in a given time period using some methods like payback period. Schedule feasibility is a measure of how reasonable the project timetable is. Given our technical expertise, are the project deadlines reasonable? Some projects are initiated with specific deadlines. You need to determine whether the deadlines are mandatory or desirable.

6.SYSTEM DESIGN: 6.1 INTRODUCTION: The project Social Networking Site is a web based application that can be accessed throughout the world and provide a variety of ways for users to interact, such as personal profiles, groups, photos, etc. Social- networking sites help users "maintain" existing (and new) offline relationships.The Design Document should be able to adequately serve as training material for new project members, imparting to them enough information and understanding about the project implementation. T he Design Phase provides a complete description the UML Diagram of the Social Networking Site. 6.2 DIAGRAMS DATAFLOW DIAGRAM: A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modeling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated.[2] DFDs can also be used for the visualization of data processing. A DFD shows what kinds of data will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel.

Table 1: User Info Field UserID FirstName LastName JoinedDate Status Passwprd Email Table2: Query Field QueryID Subject Details Tags Raisedby Status Raised on Doc title Table3:Favorite Field UserID QueryID Detail Favorite queryid

Datatype Text Text Text Date Yes or No Text Text

Size 15 15 15 10 10 15 20

Constraints Primary Key

Datatype Text Text Text Text Date Yes or No Date Text

Size 15 15 15 10 10 10 15 20

Constraints ForiegnKey

Datatype Text Text Text Date

Size 15 15 15 20

Constraints ForiegnKey

Table4: Query Followups Field UserID Datatype Text Size 15 Constraints ForiegnKey

QueryID Detail

Text Text

15 10

7.SYSTEM TESTING: System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic. [1] As a rule, system testing takes, as its input, all of the "integrated" software components that have successfully passed integration testing and also the software system itself integrated with any applicable hardware system. The purpose of integration testing is to detect any inconsistencies between the software units that are integrated together or between any of the assemblages and the hardware. System testing is a more limited type of testing; it seeks to detect defects both within the "inter-assemblages" and also within the system as a whole. Software testing can be stated as the process of validating and verifying that a software program/application/product: 1. meets the requirements that guided its design and development; 2. works as expected; and 3. can be implemented with the same characteristics. Software testing, depending on the testing method employed, can be implemented at any time in the development process. However, most of the test effort traditionally occurs after the requirements have been defined and the coding process has been completed. Although in the Agile approaches most of the test effort is, conversely, on-going. As such, the methodology of the test is governed by the software development methodology adopted.

Verification and validation: Verification is intended to check that a product, service, or system (or portion thereof, or set thereof) meets a set of initial design requirements, specifications, and regulations. In the development phase, verification procedures involve performing special tests to model or simulate a portion, or the entirety, of a product, service or system, then performing a review or analysis of the modeling results. Validation is intended to check that development and verification procedures for a product, service, or system result in a product, service, or system that meets initial requirements, specifications, and regulations. Testing Types : WhiteBox Testing WhiteBox testing tests the structure of the software or software component. It checks what going on inside the software.Also Know as clear box Testing,glass box testing or structural testing.Requires knowledge of internal code structure and good programming skills.It tests paths within a unit and also flow between units during integration of units. WhiteBox Test Design Techniques Typically Whitebox Test Design Techniques include: 1. 2. 3. 4. 5. Line Coverage or Statement Coverage Decision Coverage Condition Coverage Multiple Condition Decision Coverage Multiple Condition Coverage

Black Box Testing Blackbox testing tests functional and non-functional characteristics of the software without referring to the internal code of the software.BlackBox testing doesn't requires knowledge of internal code/structure of the system/software.It uses external descriptions of the software like SRS(Software Requirements Specification), Software Design Documents to derive the test cases.

Blackbox Test Design Techniques Typically Blackbox Test Design Techniques include: 1. 2. 3. 4. 5. Testing levels Tests are frequently grouped by where they are added in the software development process, or by the level of specificity of the test. The main levels during the development process as defined by the SWEBOK guide are unit-, integration-, and system testing that are distinguished by the test target without implying a specific process model.[29] Other test levels are classified by the testing objective. Unit testing Unit testing, also known as component testing, refers to tests that verify the functionality of a specific section of code, usually at the function level. In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.These types of tests are usually written by developers as they work on code (white-box style), to ensure that the specific function is working as expected. One function might have multiple tests, to catch corner cases or other branches in the code. Unit testing alone cannot verify the functionality of a piece of software, but rather is used to assure that the building blocks the software uses work independently of each other. Equivalance Partitioning Boundary Value Analysis State Transition Testing Usecase Testing Decision Table Testing

Integration testing Integration testing is any type of software testing that seeks to verify the interfaces between components against a software design. Software components may be integrated in an iterative way or all together ("big bang"). Normally the former is considered a better practice since it allows interface issues to be localised more quickly and fixed.Integration testing works to expose defects in the interfaces and interaction between integrated components (modules). Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system. System testing System testing tests a completely integrated system to verify that it meets its requirements. System integration testing System integration testing verifies that a system is integrated to any external or third-party systems defined in the system requirements.

8.SYSTEM IMPLEMENTATION: System implementation generally benefits from high levels of user involvement and management support. User participation in the design and operation of information systems has several positive results. First, if users are heavily involved in systems design, they move opportunities to mold the system according to their priorities and business requirements, and more opportunities to control the outcome. Second, they are more likely to react positively to the change process. Incorporating user knowledge and expertise leads to better solutions. The relationship between users and information systems specialists has traditionally been a problem area for information systems implementation efforts. Users and information systems specialists tend to have different backgrounds, interests, and priorities. This is referred to as the user-designer communications gap. These differences lead to divergent organizational loyalties, approaches to problem solving, and vocabularies. User Concerns

Will the system deliver the information I need for my work? How quickly can I access the data? How easily can I retrieve the data? How much clerical support will I need to enter data into the system? How will the operation of the system fit into my daily business schedule?
[

Designer Concerns

How much disk storage space will the master file consume? How many lines of program code will it take to perform this function? Now can we cut down on CPU time when we run the system? What are the most efficient ways of storing this data? What database management system should we use? The purpose of System Implementation can be summarized as follows: making the new system available to a prepared set of users (the deployment), and positioning on-going support and maintenance of the system within the Performing Organization (the transition). At a finer level of detail, deploying the system consists of executing all steps necessary to educate the Consumers on the use of the new system, placing the newly developed system into production, confirming that all data required at the start of operations is available and accurate, and validating that business functions that interact with the systemare

functioning properly. Transitioning the system support responsibilities involves changing from a system development to a system support and maintenance mode of operation, with ownership of the new system moving from the Project Team to the Performing Organization. A key difference between System Implementation and all other phases of the lifecycle is that all project activities up to this point have been performed in safe, protected, and secure environments, where project issues that arise have little or no impact on day-to-day business operations. Once the system goes live, however, this is no longer the case. Any miscues at this point will almost certainly translate into direct operational and/or financial impacts on the Performing Organization. It is through the careful planning, execution, and management of System Implementation activities that the Project Team can minimize the likelihood of these occurrences, and determine appropriate contingency plans in the event of a problem. This phase consists of the following processes: Prepare for System Implementation,where all steps needed in advance of actually deploying the application are performed, including preparation of both the production environment and the Consumer communities. Deploy System, where the full deployment plan, initiallydeveloped during System Design and evolved throughoutsubsequent lifecycle phases, is executed and validated. Transition to Performing Organization, where responsibility for and ownership of the application are transitionedfrom the Project Team to the unit in the PerformingOrganization that will provide system support andmaintenance.

The purpose of Prepare for System Implementation is totake all possible steps to ensure that the upcoming systemdeployment and transition occurs smoothly, efficiently, and flawlessly.