A project Report of

FRIENDSWORLD.CO.IN
A Dissertation Report Submitted in Partial Fulfillment of the Requirements for the Degree of MASTER OF COMPUTER APPLICATION Submitted by Shashank Shekher Tripathi 1009014027

Under the Supervision of Internal Supervisor Prof.Mr. Shiv Kumar Faculty, Department of MCA IEC College of Engineering & Technology , Greater Noida External Supervisor Mr. Vipul Kumar Project Manager MOSAIC technology A-43,Block-c2nd Floor sector-16 noida

Department of MCA IEC College of Engineering & Technology [Affiliated to Mahamaya Technical University, Noida, U.P.(India)] Plot no:4 , Knowledge Park-I, Greater Noida, Uttar Pradesh, India

IEC-CET

Page 1

IEC College of Engineering & Technology Greater Noida, [Department of MCA] Date : _______________

CERTIFICATE
This is to be certified that the dissertation project report " Friendsworld" is an authenticated work of "Shashank Shekher Tripathi and 1009014027 " and it is not being presented anywhere.

Signature Prof.Shiv Kumar Designation Department of MCA IEC College of Engineering & Technology Greater Noida ,U.P., India

Signature Prof. Shiv Kumar Verma Associate Prof. & Head Department of MCA IEC College of Engineering & Technology Greater Noida , U.P., India

IEC-CET

Page 2

Date : _______________

DECLARATION BY STUDENT
I Shashank Shekher Tripathi S/O Dhirendra Tripathi hereby declare that the

present dissertation project work entitled Friendsworld is a record of an original and authenticated work done by me under the guidance of Prof.Shiv Kumar Varma/Mr. Vipul Kumar. This project work has not performed the basis for the award of any other degree.

Signature Shashank Shekher Tripathi University Roll no.:1009014027 Course : MCA , Semester : VI Session : 2012-13

IEC-CET

Page 3

ACKNOWLEDGEMENT
Many persons have contributed to make this project Friendsworld.co.in a reality. I would especially like to express my appreciation to Mr. Vipul Kumar for his unstinted support, encouragement and his painstakingly and meticulous effort towards developing this software. I acknowledge the help and cooperation received from all the faculty members of Ducat Academy Noida. Several colleagues and students have contributed directly and indirectly to the contents this software, as they had given me numerous ideas. Their criticism gave me the much-needed hints about the areas that needed elaboration and amendments and also to present them with greater clarity. I sincerely express my gratitude to Mr. Vipul Kumar, the present center manager of Ducat Consultancy Ltd Noida, for his support and help in the final preparation of this Report. Finally, I wish to express my sincere thanks to all my family members, especially my Parents for their constant moral support and Encouragement. I would Welcome Constructive Suggestions to improve this software, which can be implemented in my further attempts. Thanking you! Shashank Shekher Tripathi Roll No. 1009014027

IEC-CET

Page 4

CONTENT

Chapter no. 1 2 3 4 5 6 7

Topic Abstract Preface Objective & Scope of the Project The Theoretical Background 4.1 Module of Friendsword.co.in Problem Definition 5.1 Goals That Are Successfully Archieved 5.2 Demrits of Existing System Benefits to User System Analysis 7.1 Project Planning 7.2 Feasibility Analysis 7.3 Function Requirement 7.4 System Planning System Design 8.1 Model View Controller(MVC) 8.2 Software Engineering Paradism 8.3 Input Requirments 8.4 External Interface Requirements 8.5 Design Constraint Methodology Used 9.1 Introduction 9.2 Methodology Adopted System Implementation Platform Used 11.1 Graphical User Interface(GUI) 11.2 Hardware And Software Specification 11.3 Front End And Back End Security System Maintenance 12.1 Maintenance Process Model Life Cycle Of Project 13.1 E-R Diagram Data Flow Diagram 14.1 0-Level DFD 14.2 1-Level DFD Structure Chart Test Reports 16.1 Testing Methodology And Testing Strategies

PAGE NO. 7 8-9 10 11-12 11 13 13 13 14 15-21 16 17-19 20 21 22 22-24 25-27 27 27 29 30 30 30-33 34 35-37 35 36 36-37 39 39 40 40 41-42 41 42 43 44-48 44 Page 5

9 10 11

12 13 14 15 16

IEC-CET

17

18 19 20 21 22

16.2 Type Of Testing Techniques System Security 17.1 User Access Control 17.2 User Authentication 17.3 User Session Management 17.4 Exception Handling Data Dictionary 18.1 Database Design And Table Structure 18.2 Data Structure Screen Shots Conclusion 20.1 Advantage 20.2 Limitation Future Scope 21.1 Future Scope And Dependencies References

46 49-50 50 50 50 50 51-54 54 54 55-70 70 70 70 71-72 72 73

IEC-CET

Page 6

1.ABSTRACT
Friendsworld.co.in is an online community website designed for friends. The main goal of the service is to make your social life, and that of your friends, more active and stimulating. Friendsworld.co.in social network can help you both maintain existing relationships and establish new ones by reaching out to people you have never met before who you interact with is entirely up to you. Before getting to know a forever member, you can even see how theyre connecting to you through the friends network. The main objective of the project is to establish a network among the people residing in all over the world. All the information can be easily accessed and shared among the people. This system provides users to register their various types of profile like social, personal, general, professional. This system provides users to send a scrap message, images, and music files to their friends. User can maintain the scrap book whatever scraps he has send to users. The system provides users to upload the photos so that user can maintain own album. This system provides user to join the communities according to their scenario. This system provides the user to maintain their friend list and user can update their friend list. This system provides user to send invitation to another friend to join the Friendworld.co.in and can add to their friend list for future.

IEC-CET

Page 7

2.Preface
When A Computer Software succeeds-when it meets the needs of the people who use it, when it performs flawlessly over along period of time, when it is easy to modify and even easier to use-it can and does change things for the better. But when software fails-when its users are dissatisfied, when it is error prone, when it is difficult to change and even harder to use-bad things can and do happen. We all want to build software that makes things better, avoiding the bad things that lurk in the shadow of failed efforts. To succeed we need discipline when software is designed and built. Many individuals and companies still develop software haphazardly, even as they build systems to service the most advanced technologies of the day. As a result, the quality of the software that we produce suffers and bad things happen. This project report is intended to serve as a guide to the software developed on FRIENDSWORLD.CO.IN. I have tried to follow the principles and rules as suggested by the software engineers as far as possible, in order to make this software a Successful one. The report starts with a comprehensive introduction to the project undertaken as its very First Section. It includes objectives and scope of the project; about the front-end tool used i.e. ASP.Net with C# and the back-end tool i.e. SQL Server 2005. The second part presents and discusses the theoretical background of the project. The third section encompasses all the problems of the software that includes what is expected from the software, the demands and the requirements of the end-users. The fourth part is the System analysis and design section. This part focuses on requirements analysis and specification, analysis issues, detailed procedures and the database designs. In The fifth section, different approaches to formal IEC-CET Page 8

evaluation and review techniques are explored. The sixth section highlights the methodology adopted for this project. The seventh part suggests the steps required to implement the software on the user machine. The eighth part discusses the hardware and software requirements of the user machines. The ninth part deals with the cost benefit analysis. The tenth section contains the data flow diagrams. The next section is the flowchart part. The next section is for the entity relationship diagram of the project. The thirteenth part explains the methodology used for testing. The fourteenth section is the test report. The fifteenth part is the most important part of the project i.e. the code for the software. The sixteenth part is the user manual section. The seventeenth part is the annexure for the topic that includes some details about the organization, the data dictionary, definitions, acronyms and abbreviations used in the report. The final section is the reference part that contains a list of the books and reports that were referred during the development of the project and the report as well. The emphasis in this report is to document the important concepts and techniques used for the successful development of this project. I do hope fervently that, through this report, the readers will get a real picture of what the project is all about. I also wish that may this software satisfies all the needs and requirements of the organization, for which it is meant.

IEC-CET

Page 9

3.OBJECTIVES & SCOPE OF THE PROJECT

The objective of this software is to completely automate the following processes: 1) The main objective of the project is to establish a network among the people residing in all over the world. All the information can be easily accessed and shared among the people. 2) This system provides users to register their various types of profile like social, personal, general, professional.

3) This system provides users to send a scrap message, images, and music files to their friends. User can maintain the scrap book whatever scraps he has send to users. 4) The system provides users to upload the photos so that user can maintain own album. 5) This system provides user to join the communities according to their scenario. 6) This system provides the user to maintain their friend list and user can update their friend list. 7) This system provides user to send invitation to another friend to join the Friendworld.co.in and can add to their friend list for future.

IEC-CET

Page 10

4.THEORETICAL BACKGROUND
The primary goal of this software is to provide an internet social network service which designed to help users meet new friends and maintain existing relationships. The main goal of the service is to make your social life and that of your friends, more active and stimulating. Friends world social network can help you both maintain existing relationships and establish new ones by reaching out to people you have never met before who you interact With is entirely up to you.

4.1) MODULES OF FRIENDSWORLD

Each Friends world module has different requirements from the others. This section describes the requirements, design, and implementation of each module. This system consists of five modules, which are described below:

1) Scrap Module 2) Security Module 3) Profile Module 4) Friend Invitation Module 5) Registration Module

Scrap Modulethe scrap module provides facility of sending scrap and receiving scraps. Security Modulethe security module requires a user to sign on before accessing certain screens, and manages the sign on process

IEC-CET

Page 11

Profile Modulethe profile module enables user to change his/her profile and friends profile. The module facilitate user to maintain various type of profiles like personal, professional, social. Friend Invitation Modulethe friend invitation module provides feature of sending invitation to his/her friends. Registration Moduleusing Registration module, a new user can get registered by filling registration forms.

IEC-CET

Page 12

5.) PROBLEM DEFINITION 5.1) GOALS THAT ARE SUCCESSFULLY ACHIEVED

Friendsworld.co.in provides User friendly environment. 1) Creating communities, neighborhoods. 2) Sharing emotional or personal feelings with friends or own. 3) Fully customized. 4) Provides the feelings of closeness in spite of being physically separated.

5.2) DEMERITS OF EXISTING SYSTEM

In the current working system the user faces so many problems. Some of them are given below: Earlier there was no such social portal which provided such kind of real interaction in terms of exchanging personal profile, or common platform where one could interact with others. Some of the limitations which were faced earlier are: 1) Feelings of loneliness. 2) Lack of customization 3) One could hardly share emotional feelings with one another.

IEC-CET

Page 13

6.) BENEFITS TO USER

Computer software has become a driving force. It is the engine that drives business decisionmaking. The Application is a working demonstration of how to use blueprints principles in a real application design. This document is an online guide to the design and the implementation of the application Enterprise Applications with web technology. Each release of the application maintains consistent design features such as separating logic and presentation, using web component for control and web pages for presentation, using business components, and so on. High-level design features, this document goes deeper into the implementation details of the current application release. This document is provided as an online-only resource so that it may be continually extended and updated. This document begins with a description of the separate applications that the sample application comprises, describes the modular structure of the FRIENDWORLD.CO.IN application, and provides an in-depth description of several pieces of the modules. Conclusively this software will provide following benefits to its users: 1) Providers the platform to interact to there friends and also fine new friends around the world. 2) Provides a way to be in touch with loved once. 3) Shows the graphically the upcoming birthdays of you friends so now you dont have to remember your friends birthdays. 4) Provides the way to send or receives messages form your friends and family member and makes you connected to others even you are far away from him. 5) Provider some storage space where you can store you memorable memories in the form of photos and videos. 6) You can do instant chat with your friend easily because it is very easy and user friendly. 7) You can also send or receives photographs with text messages.

IEC-CET

Page 14

7.) SYSTEM ANALYSIS

Requirements analysis is a software engineering task that bridges the gap between system level requirements engineering and software design. Requirements engineering activities result in the specification of softwares operational characteristics (function, data and behavior), indicate softwares interface with other system elements, and establish constraints that software must meet. The most commonly used requirements technique is to conduct a meeting or interview. The first meeting between a software engineer (the analyst) and the customer can be likened to the awkwardness of a first date between two adolescents. Neither person knows what to say or ask; both are worried that they do say will be misinterpreted; both are thinking about where it might lead (both likely have radically different expectations here); both want to get the thing over with, but at the same time, both want it to be a success. Gauss and Weinberg suggest that the analyst start by asking CONTEXT-FREE QUESTIONS. That is, a set of questions that will lead to a basic understanding of the problem, the people who want a solution, the nature of the solution that is desired, and the effectiveness of the first encounter itself. The goal of the requirements gathering activity is to collect all relevant information from the customer regarding the product to be developed with a view to clearly understanding the customer requirements and weeding out the incompleteness and inconsistencies in these requirements. The requirements analysis activity is begun by collecting all relevant data regarding the product to be developed from the users of the product and from the customer through interviews and discussions. Data collection is done by taking the copies of the documents involved in its working from the organization.

IEC-CET

Page 15

7.1) PROJECT PLANNING

We were supposed develop a social network web site named as FRIENDSWORLD.CO.IN. Friendworld.co.in is an internet social network service designed to help users meet new friends and maintain existing relationships. Working in team reinstates the team for some common guidelines and standard to be followed by all the team members across all the team. For the optimum use of practical time it is necessary that every session is planned. Planning of this project will include the following things: Topic understanding. Modular break-up of the system. Processor logic for each module. Database requirements.

TOPIC UNDERSTANDING
It is vital to understand the each and every aspect project. So as soon as the project was allocated, we carefully went through the project to identify the requirements of the project. Modular break-up of the system: Identify the various modules in the system. List them in the right hierarchy. Identify their priority of development.

IEC-CET

Page 16

7.2) FESIBILITY ANALYSIS

Feasibility study is conducted to select the best system that meets the performance requirements. This entails an identification, description, and evaluation of the candidate system, and the section of the best system for the job. Many feasibility studies are disillusioning for both user and analyst. First the study often pre-supposes that when feasibility of the documents is being prepared, the analysis is in position to evaluate solutions. Second most studies tend to overlook the confusion inherent in the system development the constraints and the assumed attitudes. If the feasibility study is to serve as decision document, it must answer three key questions: 1) Is there new and better way to do a job that will benefit the user? 2) What are the cost and saving of the alternatives? 3) What is recommended? The most successful system projects are not necessary or most visible in business but rather those that truly need user expectations. More projects failed because of inflated expectations than for any other reasons. There main considerations are involved in feasibility analysis : TECHNICAL ANALYSIS Technical feasibility centers on the current system and to what extent it can support the proposed system, it includes current computer system specifications such as hardware, software etc. it also involves financial considerations to accommodate the technical enhancements. If the budget is serious constraint then the project is judged not feasible.

17

Though the system is developed in the generalized form, which covers all the procedures and operations carried out in any Social networking site. The version used in the system is ASP.Net and MS-SQL Server. The features embedded in the system are latest and according to the need of the client. Such as creating profile, adding friends and other feature that are required for social networking site. The backend used is the latest Microsoft SQL Server version, which also supports to view the database contents, relationship with the connected database including the primary, foreign key. Any up gradations needed can be easily made in the source code, thus decreasing the headache of changing each and every code. If in near future, the latest version of ASP.Net/ MS-SQL Server to be installed then , the source code handling the connection of the database can easily be modified. The codes are easily compatible for the changes, as the latest version doesn't affect the core code. MS-SQL Server can manage large amount of data and is simple and secure. Using

ASP.NET helps us to design the look of our application and its windows. ASP.NET full open database connectivity (ODBC) with MS-SQL Server, Data accessibility, response and output require less time.

COST ANALYSIS
The cost to conduct investigation was negligible, as the centre manager and teachers of centre provided most of information. The cost of essential hardware and software requirement is not very expensive. Moreover hardware like Pentium I PC and software like ASP.NET and MS-SQL Server2005 are easily available in the market.

18

BENEFITS AND SAVINGS

1) Cost of the maintenance of the proposed system is negligible. 2) Money is saved as paper work is minimized. 3) Records are easily entered and retrieved. 4) Time is saved as all the work can be done by a simple mouse click. 5) The proposed system is fully automated and hence easy to use. 6) Since benefits out base the cost, hence our project is economically feasible.

OPERATIONAL FESIBILITY
In this we determine what change will be brought in system, new skills required and other human organization and political aspects. Each user can easily use our site. However it is desirable that the user has the basic knowledge of the computers. Without making any changes in the rules and regulations of the existing system proposed system can easily adopted.

LEGAL FESIBILITY
Our Project does not infringe with known acts, status or any pending legislation. Hence it is legally feasible.

SOCIAL FESIBILITY
Since, the proposed system is inexpensive, easy to use, reduces human errors, fast and simple, hence socially accepted by all organization and institutes being directly affected by it.

19

7.3) FUNCTIONAL REQUIREMENTS

1) Person should have a Valid E mail ID. 2) There must be a net connection and browser to view the web pages of respective site

20

7.4) SYSTEM PLANNING

PROJECT EVALUATION AND REVIEW TECHNIQUE INTRODUCTION

Software project managers take the overall responsibility of steering a project to success. This surely is a very hazy job description. But, it is very difficult to objectively describe the job responsibilities of a project manager.

WORK BREAKDOWN STRUCTURE

Work breakdown structure is used to decompose a given task set recursively into small activities. WBS provides a notation for representing the major tasks needed to be carried out in order to solve a problem. The root of the tree is labeled by the problem name. Each node of the tree is broken down into smaller activities that are made the children of the node. Each activity is recursively decomposed into smaller sub-activities until at the leaf level; the activities require approx. two weeks to develop. If a task is broken down into a large number of very small activities, these can be distributed to a large number of engineers. If the activity ordering permits, the solutions to these can be carried out independently. Thus, it becomes possible to develop the product faster. The following figure represents the WBS of application software:

21

8.) SYSTEM DESIGN 8.1) MODEL VIEW CANTROLLER (MVC)

This software based on concept of the Model View Controller (MVC) design pattern. MVC gives you a nice separation between your data (model), logic/business layer (controller) and display (view). In theory, this allows you to change individual layers without affecting the other layers. You could have a configurable data source (SQL, XML, etc.) or have various controllers depending on the user (admin, anon, etc.) or have various views (console, webform, winform). MVC makes it really easy to implement change which is what programming in the real world is all about. These three objects are known as Model, View and Controller.

VIEW View is the graphical data presentation (outputting) irrespective of the real data processing. View is the responsible for look and feel, some custom formatting, sorting etc. View is completely isolated from actual complex data operations. For example, online product catalog view is completely separated from database connection, query, tables etc. It simply gets final row-data from the model and puts some cosmetics and formatting before displaying it in browser. View provides interface to interact with the system. The beauty of MVC approach is that it supports any kind of view, which is challenging in todays distributed and multi-platform environment. A MVC model can have multiple views, which are controlled by controller. View interface can be of WEB-FORMS, HTML, XML/XSLT, XTML, and WML or can be Windows forms etc.

22

MODEL
The domain-specific representation of the information on which the application operates. Domain logic adds meaning to raw data (e.g., calculating whether today is the user's birthday, or the totals, taxes, and shipping charges for shopping cart items). Many applications use a persistent storage mechanism (such as a database) to store data. MVC does not specifically mention the data access layer because it is understood to be underneath or encapsulated by the Model.

23

CONTROLLER
Controller is responsible for Notice of action. Controller responds to the mouse or keyboard input to command model and view to change. Controllers are associated with views. User interaction triggers the events to change the model, which in turn calls some methods of model to update its state to notify other registered views to refresh their display.

BENEFITS OF MVC DESIGN

Following are the few of the benefits of MVC design pattern.

Since MVC handles the multiple views using the same enterprise model it is easier to maintain, test and upgrade the multiple system. It will be easier to add new clients just by adding their views and controllers. Since the Model is completely decoupled from view it allows lot of flexibilities to design and implement the model considering reusability and modularity. This model also can be extended for further distributed application.

It is possible to have development process in parallel for model, view and controller.

24

8.2) SOFTWARE ENGINEERING PARADIGM

In our project I have used Prototype model. The basic idea here is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements. This prototype is developed based on the currently known requirements. Development of the prototype obviously undergoes design, coding and testing. But each of these phases is not done very formally or thoroughly. By using this prototype, the client can get an "actual feel" of the system, since the interactions with prototype can enable the client to better understand the requirements of the desired system. Prototyping is an attractive idea for complicated and large systems for which there is no manual process or existing system to help determining the requirements. In such situations letting the client "plan" with the prototype provides invaluable and intangible inputs which helps in determining the requirements for the system. It is also an effective method to demonstrate the feasibility of a certain approach. This might be needed for novel systems where it is not clear those constraints can be met or that algorithms can be developed to implement the requirements. The process model of the prototyping approach is shown in the figure below.

25

PROTOTYPING MODEL
The basic reason for little common use of prototyping is the cost involved in this built-ittwice approach. However, some argue that prototyping need not be very costly and can actually reduce the overall development cost. The prototype is usually not complete systems and many of the details are not built in the prototype. The goal is to provide a system with overall functionality. In addition, the cost of testing and writing detailed documents are reduced. These factors help to reduce the cost of developing the prototype. On the other hand, the experience of developing the prototype will very useful for developers when developing the final system. This experience helps to reduce the cost of development of the final system and results in a more reliable and better designed system.

ADVANTAGES OF PROTOTYPING
Users are actively involved in the development. It provides a better system to users, as users have natural tendency to change their mind in specifying requirements and this method of developing systems supports this user tendency. Since in this methodology a working model of the system is provided, the users get a better understanding of the system being developed. Errors can be detected much earlier as the system is mode side by side. Quicker user feedback is available leading to better solutions.

DISADVANTAGES OF PROTOTYPING
Leads to implementing and then repairing way of building systems. Practically, this methodology may increase the complexity of the system as scope of the system may expand beyond original plans.

26

8.3) INPUT REQUIREMENTS 1) FOR LOGIN:

1.1) 1.2) User Email ID which has to be registered in Frindsworld.co.in before Login. Password related to that user Email ID which is used to login.

2) FOR INVITING FRIENDS:

2.1) 2.2) User Email ID which you want to invite. For sending a request for add me as a friend just simply select the user and send request to add me.

3) FOR REQUESTING PASSWORD IF THE PASSWORD ID NOT REMEMBERED:

3.1) Only by confirming the User ID user will automatically receives a mail with their password if they not remember there password.

4) FOR UPDATE YOUR PROFILE:

4.1) Just login with your User ID click on your profile then click on edit and simply edit your profile detail.

OUTPUT REQUIREMENTS
1) Person should have a valid Email ID which is registered in friendsworld.co.in 2) There must be a net connection and browser to view the web pages of respective site.

27

8.4 EXTERNAL INTERFACE REQUIREMENTS

The user interface of software is responsible for all the interactions with the user. Almost every software has a user interface. Many users often judge a software product based on its user interface. An interface that is difficult to use leads to higher level of user errors and ultimately leads to user dissatisfaction. Users become particularly irritated when a system behaves in unexpected ways i.e. issued commands do not carry out actions according to the intuitive expectations of the user. Therefore, sufficient care and attention should be paid to the design of the user interface of any software product. Development of a good user interface usually takes significant portion of the total system development effort. This software is developed keeping in mind the basic characteristics of a good user interface. Some features of this software can be stated as:1) It is very easy to learn. It does not require its users to memorize commands. Neither the users are asked to remember information from one screen to another while performing various tasks using the interface. 2) The time and user effort necessary to initiate and execute different commands is minimal. 3) It is very attractive to use. It catches user attention and fancy. It is a Graphicalbased user interface. 4) The users can seek guidance and online help when they either forget a command or are unaware of some features of the software.

8.6 DESIGN CONSTRAINTS

28

SOFTWARE CONSTRAINTS
The software is to run under Windows Operating System or above versions.

HARDWARE CINSTRAINTS
The software will run on an Intel Workstation with 32 MB RAM, Running on Windows.

29

9) Methodology used
9.1 INTRODUCTION
A software life cycle is the series of identifiable stages that a Software product undergoes during its lifetime. The first stage in the life Cycle of any software product is usually the feasibility study stage. The Subsequent stages are: Requirement analysis and specification, design, coding, testing and maintenance. Each of these stages is called a life cycle Phase. A life cycle model represents all the activities required to make a software product transit through its life cycle phases. It also captures the order in which these activities are to be undertaken. The most strict life cycle model used is the Classical Life Cycle Model. However, in any practical software development work, it is not possible to strictly follow the classical waterfall model from every phase to its preceding phases.

9.2 METHODOLOGY ADOPTED

Structured system analysis techniques had been adopted for the analysis of the algorithm and software development. Structured system design techniques had been adopted for the design of the algorithm and software development. Prototyping model for initial implementation had been used for early testing and module development. Prototyping model had been used for the development of the Graphical User Interface. Incremental Model had been used for the development of the software. Structured development life cycle had been used for this project. PERT chart is the primary Tool used for system planning. Project cost had been estimated as a function of comparing the cost of similar available products, effort estimation on the project, resources acquired for the project and COCOMO Model as the theoretical reference. Test plan was created to form the strategy of testing. This includes the decision of testing techniques, decision of testing tools, and decision of milestones when the testing will commence.

ANALYSIS METHODS

30

Structured system analysis techniques are used for the analysis of algorithm and development.

Background analysis: concept of mining and about the algorithm is learned through research papers on Internet and experts theory.

Fact-finding: facts about the algorithm are collected from the books and Internet. Fact analysis: facts are analyzed through different examples related to algorithm. DFDs and flowchart are used to model the algorithm and logic design.

DESIGN METHODS

Structured design techniques are used to design the software.

An activity of all phases of a project is the walk-through. It is an interchange of ideas among the team members. In design walk-through, the purpose is to recognize as many problems in the software as possible while they are still paper tigers

Activity diagram are used then to define the behavior of mechanism.

Layering has been done to refine the architecture. Initially, two layers are introduced, system layer and application layer.

Demo version is created on these lines of design techniques to demonstrate the feasibility of design methods.

31

CODING METHODS

Event driven programming language ASP.Net had been used for coding the modules and programs.

Structured English and pseudo-codes are used to closely refine the mechanisms using the facility of defined objects.

Various stubs had been used to facilitate incremental coding followed by testing.

The basic philosophy followed at this stage: code one line followed by rigorous testing.

Integrated development environment of .Net had been used for the development of various modules in integrated manner.

Incremental compilation had been used to compile and test on which work was in progress.

Stepwise refinement technique had been used to code the modules.

TESTING METHODS
32

Structured testing tools had been used for testing the programs. Small programs are developed to test the individual modules. Each module is tested by the development of appropriate functionality. Groups of people were assigned to test the software functionality. The same group is responsible to test the reliability of software by using various inputs and techniques, on various parts and functionalities.

The group had done Alpha testing. Software is distributed to doctors and scientist to Beta-test the entire software.

33

10) SYSTEM IMPLEMENTATION

Direct Implementation Method is used to implement the system at the users site. No special Equipment (Hardware Device) is required to install the Software. The only requirement is the user must have an Internet Connection.

11) Platform Used

34

FRIENDSWORLD SPECIFICATION
The system specification is the final work produced by the system and requirements engineer. It serves as the foundation for hardware engineering, software engineering, database engineering and human engineering. Once requirements have been gathered explore each requirements in relationship to others, examine requirements for consistency, omissions and ambiguity.

11.1) GRAPHICAL USER INTERFACE (GUI)

GUI offers a standard look and feel to application, thus reducing development and learning time. Through this a user understands easily. An attractive GUI influence the mind of user. GUI is an application environment that can work with graphical objects.

35

11.2) HARDWARE AND SOFTWARE SPECIFICATIONS HARWARE SPECIFICATIONS

It is recommended that the minimum configuration for clients is as appended below:Suggested Configuration of Windows clients: Microprocessor Ram Hard Disk CD ROM Drive : Pentium-2 class processor, 450 megahertz MHz) : 128 MB of RAM : 2.5 gigabytes (GB) on installation drive, which Includes 500 MB on system drive. : 52 X CD ROM Drive

SOFTWARE SPECIFICATION
Operating System RDBMS Front End : Windows XP,Window 7 : SQL Server 2005 : Microsoft Visual Studio ASP.NET

FRONT END AND BACK END FRONT END

We use rich set of validation controls provided by ASP.NET and where we not achieved this through validation control we implemented JavaScript for all the Client side validations. We usually use lot of client side validation not server side. The form is not submitted until user fills in correct data. It is extremely useful to restrict mistakes by user.

ACTIVER SERVER PAGES (ASP.NET)

36

User friendly GUI Separation of work (designing & coding) Written once run anywhere Middle-Tier Asp.Net APIs

BACK END
We have used SQL Server as the Back End.SQL Server provides efficient/effective solution for major database tech. Large database and space management. Many concurrent database users. High transaction processing requirement High Availability Industry accepted standards Manageable security Portability

SQL-SERVER
Security Performance Scalability Reliability Support RDMS concept

37

12.1) SYSTEM MAINTENANCE

System maintenance denotes any changes made to a software product after it has been delivered to the customer. Maintenance is inevitable for almost any kind of product. However, most products need maintenance due to the wear and tear caused by use. On the other hand, software products do not need maintenance on this count, but need maintenance to correct errors, enhance features, port to new platforms, etc. Software maintenance is becoming an important activity of large number of organizations. This is no surprise, given the rate of hardware obsolescence, the immortality of a software product per se, and the demand of the user community to see the existing software products run on newer platforms, run in newer environments, and/or with enhanced features. When the hardware platform changes and a software product perform some low-level functions, maintenance is necessary. Also, whenever the support environment of a software changes, the software product requires re-work to cope with the newer interface. Thus, every software product continues to evolve after its development through maintenance efforts. Maintenance covers a wide range of activities including correcting, coding and designing errors, updating documentation and test data and upgrading user support. Enhancement means adding, modifying or re-developing the code to support changes in the specifications. It is necessary to keep up with the changing user needs and the operational environment. The software is designed with the view of easy updating to the software. Future advancements can be done easily through the review of product. The software architecture is strong enough to provide enhancement in functionality, performance and reliability. Functions in the software are designed in such away that they dynamically update on addition of new and revised modules.

To append new features in this software, the databases for student details, examination details are sufficient enough for the task. Thus the software is capable enough of being enhanced easily whenever requires by the user.
38

12.1) MAINTENANCE PROCESS MODEL

GATHER CHANGE REQUIREMENTS

ANALYZE CHANGE REQUIREMENTS

DEVISE CODE CHANGE STRATEGIES

APPLY CODE CHANGE STRATEGIES TO THE OLD ONE

UPDATE DOCUMENTS

INTEGRATE AND TEST

13) Life cycle of the project

39

13.1 ENTITY RELATIONSHIP DIAGRAM

14) DATA FLOW DIAGRAM

40

CONTEXT DIAGRAM
The context diagram is the most abstract data flow representation of a system. It represents the entire system as a single bubble. This bubble is labeled according to the main function of the system. The various external entities with which the system interacts and the data flows occurring between the system and the external entities are also represented.

LEVEL 0 DFD

FIRST LEVEL DFD

41

To develop the level 1 DFD, examine the high-level functional requirements. If there are between three to seven high-level functional requirements, then these can be directly represented as bubbles in the level 1 DFD. We can then examine the input data to these functions and the data output by these functions, and represent them approximately in the diagram.

LEVEL 1 DFD

15) STRUCTURE CHART

42

MAIN MENU

SUBMENU

LOGUP GENERAL DETAILS FORM PERSONAL DETAILS FORM PROFESSSINAL DETAILS FORM SOCIAL DETAILS FORM LOGIN USERID PASSWORD SCRAPBOOK SEND SCRAP RECEIVE SCRAP DELETE SCRAP INVITE FRIENDS SEND INVITATION PHOTOS ADD PHOTO ALBUM DELETE PHOTO ALBUM SEND PHOTO ALBUM VIDEOS ADD VIDEOS DELETE VIDEOS SEND VIDEOS

16) Test Report

43

16.1) TESTING METHODOLOGY AND TESTING STRATEGIES

There are following rules that can serve well as testing objectives: Testing is a process of executing a program with the intent of finding an error. A good test case is one that has a high probability of finding an as-yetundiscovered error. A successful test is one that uncovers as-yet-undiscovered error.

TESTING STRATEGIES UNIT TESTING

In unit testing I have testing a single program module in an isolated environment. Testing of the processing procedures is the main focus. Integration Testing Because of interfaces among the system modules, we use integration testing. In other words it ensures that the data moving between the modules is handled as intended.

44

SYSTEM TESTING
During system testing the system is used experimentally to ensure that the software does not fail i.e. it will run according to its specifications and in the way users expect. Special test data are input for the processing and the results examine. A limited number of users try to use it in unforeseen ways. It is preferable to discover any surprise before the organization implements the system and depend upon it. In many organizations persons other than those who wrote the original programs to ensure more complete and unbiased testing and more reliable testing perform testing. Since the user are not familiar to the new system the data screens were designed in such a way that were: Consistent Easy to use Has a fast response time

System testing is the testing of the system against its initial objective. It is done either in a simulated environment or in live environment. TEST REVIEW Test review is the process that ensures that testing is carried out as planned. Test review decides whether or not the program is ready to be shipper out for implementation

45

SECURITY TESTING Security testing attempt to verify that protection mechanism built into a system will, in fact, protect it form penetration mechanisms.

TYPES OF TESTING TECHNIQUES

White box testing Black box testing

WHITE BOX TESTING

White box test focus on the program control structure. Test cases are derived to ensure that all statement in the program has been executed at least once during testing and that all logical condition has been exercised. Basic path testing, a white box testing, makes use of program graph to derive the set of linearly independent test that will ensure coverage. CODING TESTING

Condition testing is tests case design method that exercise the logical conditions contain in a program module. A simple condition is a Boolean variable or a relational expression. BRANCH TESTING

I have used Branch testing that is probably for compound condition, the true and false (in project i.e. null values) for each branch.

46

DATA FLOW TESTING I have used data flow testing due to check the path of program according to the locations of definitions and uses of variables in the program. LOOP TESTING In our project I have use only simple loop. And I have use m pass through the loop where m<n.

BLACK BOX TESTING

Black box testing focuses on the functional requirements of the software. That is, blackbox testing enable the software engineer to derive set of input conditions that will fully exercise all functional requirements for a program. GRAPH-BASE TESTING METHOD I have used graph-based testing method for removing errors associated with relationships. The first step in this testing is to understand the objects that are modeled in software and the relationship that connect these objects. EQUIVALENCE PARTITIONING This testing is used for the following reason: Specific numeric values Range of values Set of related values Boolean condition

47

BOUNDARY VALUE ANALYSIS Boundary value analysis is a test case design technique that complements equivalence partitioning. Rather than selecting any element of equivalence class the selection of test cases at the edges of the class. Rather than focusing solely on the input condition, The point of equivalence partitioning as: An input condition specifies a range boundary by values a and b, test cases should be design with values a and b and just above and just below a and b. An input condition specific a number of values, test cases should be developed that exercise the minimum and maximum number

ACCEPTENCE TESTING When the function test was completed, we involved the user to make sure that the system worked according to the users expectation. Thus the user did the final acceptance test.

48

17.) SYSTEM SECURITY 17.1) USER ACCESS CONTROL

Security comprises user authentication, implying user identification (against defined users) and users authorization indicating actions and permissions within the application. The application will incorporate security for all the modules in a hierarchal form. These levels are required to be identified by the application owners. The users will be classified in groups and each group will b provided access to identify screens and reports. This access will be across different modules. The group authorization right will also define whether they are permitted to view the information only or can modify it as well.

17.2 USER AUTHENTICATION

Every registered user will have a login ID and password. The system administrator, using the functionality provided by login control module, will create new login Ids and maintain existing Ids using the user registration screen. Whenever a new user is registered, a new login ID and password will be created. Users can change their own passwords. The passwords will not be displayed on the screen while they are being entered into the application.

49

USER AUTHORIZATION

For data entry and modification, permissions will be defined for the entry screens. Administrator and Users both will be having different screens and different access rights. Administrator would be able to manage different operations and functions whereas a registered user would be able to access all the features available on the website.

17.3) USER SESSION MANAGEMENT

The USERNAME of the user will be displayed on the next page, and any item needed on the different page will also be maintained using Session management. Browser Session will expire and terminate user session after a certain period of inactivity. The following data will be maintained throughout an active session.

EXCEPTION HANDLING
Validations will be enforced at the UI as well as the business layer of application. If errors occur, appropriate messages will be displayed to the user for taking necessary action. These errors will be handled by the application using Visual Studio Exception Handling.

50

18) Data Dictionary

18.1)DATABASE DESIGN
DATABASE DESIGN AND TABLE STRUCTURE

51

18.2DATA STRUCTURE
FRIEND DETAIL

52

FRIEND INVITATION

IMAGE

MAIL MESSAGE DETAIL

SCRAP DETAIL

53

USER ALBUM

USER GENERAL DETAIL

USER LOGIN DETAIL

USER PERSONAL DETAIL

54

USER PROFESSION DETAIL

19.) Output and Screen shots of software application

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

20.) CONCLUSION

ADVANTAGES
All the procedure in this project is automatic accept the entry of data from the user. The project gives the user-friendly environment, which gives the way of working in more efficient manner.

LIMITATIONS

This system cant provide on line video conferencing. This system not providing chat facility. This system not provides the facility to users so that they can set various types of themes and send interesting themes to their friends.

This system not making scrap in different languages.

71

21) FUTURE SCOPE

This software can be easily upgraded in the future. And also include many more features for existing system.

In future this system will provide online video conferencing bringing people together who are geographically separated.

Friendworld.co.in will provide greater level of customizations suitable to users requirements.

In future user can maintain their play list and any friend of that user can get that play list.

In future there will be privacy policy so that valid user in only permissible to enter anothers profile and cant change their profile.

72

21.1DEPENDENCIES
It doesnt matter how efficiently the application works, if the bandwidth is not sufficient the transaction will take more time then expected. .Net Framework for execution environment and Ado.Net Provides for database connectivity. IIS server is required for the application. Although this software is architecturally independent but following hardware resources are required. For i.e. any IBM compatible PC or any other workstation with mouse support and relevant software

73

22 REFERENCES BOOKS ASP .Net By Peter Norton Mastering ASP.Net TECHMEDIA Learn ASP.Net in 21 days TMH Black book ASP.Net.

LIBRARY MSDN
MSDN Library Visual Studio .Net release The MSDN Library is the essential reference for developers, with more than a gigabyte of technical programming information; including sample code, documentation, technical articles, the Microsoft Developer Knowledge Base, and anything else we might need to develop solutions that implement Microsoft technology.

WEBSITE
www.apollohospital.com www.ducatindia.com www.ministryofhealth.com

74