Project Photo Share)

8/3/2019 Project Photo Share)

1/58

Online Photo Sharing System

INTRODUCTION

PG Department of Computer Applications, Marian College Kuttikkanam1


2/58


1.1 Description of system

The aim of the system is to allow users to upload, organize,

share and modify (crop and resize) their photos. The advantage is that

once they upload photos to the server they can access it from anywhere

else. They can modify their photo at server even if the computer the user

is using does not have a photo editing software. Organize means group

photos into an efficient manner. Like what we do in our computer if we

have a huge pool of photos, we will group them and put each group in a

separate folder, so it will be efficient to retrieve photos than to search for

Munnar tour photos in the whole pool of photos.

Users can upload photos until they reach their limit (e.g.: 100MB/Month).

Users can organize their photos by tagging them, grouping then into sets

(a group of photos) and collection (a group of sets).

Users can share the photos with the registered users of the system and

also with people from outside.

Users can create their own group or join in others group(s).

Users can create, view and share slideshows.

Users can set the visibility of the photo such as to public (to all), private

(only to the user himself) etc.

Users and nonusers can post comment on photos.

Users can modify their photos uploaded at the server itself through the

browser.



3/58


1.2 Why we need such a system?

Finding a picture out of your collection is a tough task, especially if your

collection is huge.

Once you upload photos to the server you can access it from

anywhere.

User can modify their photo at server even if the computer the user

is using does not have a photo editing software.

Sharing pictures with your friends or other people is hard and

inefficient with current mechanisms (blogs, mailing etc.), as they are

not meant for this purpose.

People can get together, share their photos and make comment on

each others photos. Such a system is necessary because many

group based systems such as blogs are reluctant in uploading

pictures to their server



4/58


ABOUT THE

ORGANIZATION



5/58


4G Technologies

4G Technologies is a Software Development and Services

Company established in the year2008 headquartered at Pali, India. The

company is directed by a group of youngsters. Over the years, they have

built up the organization based on enduring principles which has a clearfocus on Customer Satisfaction. 4G Technologies is committed to be a

world class service provider in Custom Software Development using

technologies .Net and Java. As the fountain head of most significant

pursuit of human mind 4G Technologies believes, only a leader can

transform you into a leader. 4G Career Development Centre is an initiative

that enables individuals to benefit from 4G Technologies expertise in the

space and become industry ready IT professionals. 4G Career

Development Centre offers a complete spectrum of quality training

programs in Microsoft Technologies, Open Source Technologies, Internet

Programming, Multimedia, and Administration.



6/58


SYSTEM ANALYSIS



7/58


3.1 Existing System

People are currently using mechanisms that are not intended for this

purpose. Following are some of such popular mechanisms and their

drawbacks.

Using Internet mail systems:

The limitations of this system are,

We can share photos only if we have the email-id of person(s) with

whom we want to share it. This puts a restriction on the number of

persons we share our picture i.e. the pool of viewers of our picture is

finite (e.g. all my contacts in the mailing system) and not infinite

(e.g. all the people who searches for pictures with a tag Morning)

Organizing is difficult: In mailing systems we send and receive

pictures either as attachments or as pictures embedded in mail

body. Both of them are difficult to organize.

Searching for pictures in a mail system is hard. Replying is the only

way to make comments on pictures. Creating and sharingslideshows are also impossible

Blogs:

Many dont allow uploading pictures especially that of large size.



8/58


Organizing, searching will be difficult though commenting can be

emulated with postings.

Running your own Website:

Website author will have to do all the hard work. The author may not

be able to provide more complicated and advanced features like

slideshow mechanism, easy to use organizer. Hosting Services can

be expensive.

3.2 Proposed System

The proposed system will avoid almost all of the drawback that

are with the existing mechanisms mentioned above and is introducing new

features that are not available in them. The proposed system will allow

users to upload, organize, share and modify (crop and resize) their photos.

The advantage is that once they upload photos to the server they can

access it from anywhere else.

The main advantages of the proposed system are,

Easy and flexible ways for sharing pictures:

Users can share pictures between other users and nonmembers (who

are not registered with the system and so do not have an account in the

application).And more than one ways are available for sharing in the form

of Slideshows, Sharing pictures in groups, and through public searching

mechanism.

Easy way to organize pictures:

Organizing picture in the system will be so easy. User can organize

his picture with as much ease as we organize files in windows. Users will

be allowed to create two types of virtual containers (like folders) named



9/58


Set a container for a group of pictures and Collection a container for a

group of Sets. Moving pictures between the containers will also be easy.

Good Searching Mechanism:

This will allow users and nonmembers to search in the whole pool of

pictures present in the system. Owners of picture can also decide his all

pictures or specific pictures to be private, thereby hiding then from others

even in searches.

Group Mechanism:

Users (especially those with a common interest e.g. those who love

landscape photography) can create groups, put their pictures in the group

thereby sharing them with the members of that group and will be able to

comment on each others pictures.

3.3 Software Requirement Specification (SRS)

3.3.1 The Problem to be solved

Finding a picture out of a collection is a tough task, especially if the

collection is huge. So the process of organizing them has become so

tedious. And also these pictures can eat up the secondary storage very

quickly. If we are putting the pictures in our computer it can be accessed

from that computer only. The solution we have to make must solve the

above problem and it also will contain some additional features such as

group facility, online picture modifications (only cropping and resizing).

3.3.2 Customer requirements



10/58


An easy to use administration interface: An interface for

managing the different settings (e.g. monthly upload limit for a user,

maximum number of collections that can be made by user etc).

Resource usage by users should be well bound by the

above specified settings: Resources (hard disk space and bandwidth

usage) of the system are not unlimited, they definitely have a limit, and

because of this we cannot allow users to use unlimited amount of

resources. So we should put limits on their usage e.g. the maximum

upload limit for a user per month is 100MB.

Advertising mechanism should be there in order to make

money: System should be capable of showing advertisements, so that

money can be earned after hosting the system.

3.3.3 User requirements

A simple and easy to use interface: The interface has to be

simple and the internal complicacies of the system must be hidden from

the users. Theinterface has to be an easy to use one e.g. we cannot ask

the user to enter two coordinates to crop the picture, we have to give

them an interface with which they can select the portion to crop with the

mouse itself.

Users privacy should be preserved:There should be option to

make all or specific pictures of a user private. Private pictures can only be

viewed by the owner of the picture only.

Security: The users account and pictures have to be protected

from intruders.

3.3.4 Functional Requirements



11/58


The following are the functions that the system has to perform,

Upload photos to the server.

Allow Users can organize their photos by tagging them, grouping then

into sets (a group of photos) and collection (a group of sets).

Allow Users to share the photos with the registered users of the system

and also with people from outside.

Allow Users to create their own group or join in others group(s).

Allow Users to create, view and share slideshows.

Allow Users to set the visibility of the photo such as to public (to all),

private (only to the user himself).

Allow Users and nonusers to post comment on photos. Allow Users to

modify their photos uploaded at the server itself through the browser.

3.3.4 System Requirements

One of the main advantages that this system should have is it

should adapt to both large scale (above 25,000 users) implementations

and small scale (1000 to 15,000) implementations.

HARDWARE REQUIREMENTS

Processor :Intel pentium2 or Higher

RAM :1GB or higher

HD :20 GB or more

Mouse :Any standard mouse

Keyboard :Any standard Keyboard

SOFTWARE REQUIREMENTS



12/58


Front end :ASP.NET

Server side scripting :C#

Back end :SQL Server 2005

Operating system :Windows 7/XP

IDE :Visual Studio2008

3.3.5 Platform Specifications

The design tools that were used to make this software is ASP.NET which is

part of the .NET Framework, and when coding ASP.NET applications we

have access to classes in the .NET Framework.

The language used for developing this software is C# which is one of the

languages used in the Microsoft .NET Framework. The Microsoft .NET

Framework is a library of objects that create or draw things on the

computer. C# is a modern, type safe programming language, object

oriented language that enables programmers to quickly and easily build

solutions for the Microsoft .NET platform.

Here we are using SQL Server 2008 as Back End. The SQL Server is a state

of the art information management environment. It is a repository for very

large amount of data, and gives users rapid access to that data. SQL

Server allows for sharing of data between applications, the information is

stored in one place and used by many systems. There are many significant

features that, to become SQL Server to the top of the growing information

management vendor community.

CSS and HTML used to design the webpages.

JavaScript is used for client side scripting.

The documentation used in developing this software is Microsoft Office

2007.



13/58


3.3.7 Constraints

Secondary Storage: We will be storing the pictures on Hard Disks,space available in them are limited. So we cannot feel like having

unlimited storage. We have to make sure that the available space is not

getting consumed very quickly by putting limits on users (e.g. Maximum

number of pictures they can have in a Set etc.).

Bandwidth: Users are connected to the server via communication

network, we must fairly distribute this communication lines bandwidth

usage among users.

Processor Cycles: Even the high performing processors will start to

respond slowly when the number of users increases and their number of

requests also increases. Our system should utilize the processor cycles to

the full without overloading it.

3.4 Feasibility Analysis

A feasibility study is a preliminary study undertaken before the real work

of a project starts to ascertain the likelihood of the project's success. It is

an analysis of possible alternative solutions to a problem and a

recommendation on the best alternative.

The development of a computer-based system is more likely to be

plagued by the scarcity of resourced bad difficulty delivery data. A

feasibility study is not warranted system in which economic justification is

obvious, technical risk, low, few legal problems are expected, and no

reasonable alternative exits.



14/58


Three essential consideration are involved in the feasibility analysis

Technical feasibility

Economic feasibility

Operational feasibility

Technical Feasibility: This involves questions such as whether the

technology needed for the system exists, how difficult it will be to build,

and whether the firm has enough experience using that technology. All the

technologies needed for this system is currently available, such as

multiple quad core based servers and high end windows server operating

systems.

Economical Feasibility: The spending that has to make is for the Server

machine. Advertisements can also be allowed on the system to make

profit.

Operational Feasibility: People are inherently resistant to change.

Computers have been known to facility changes. An estimate should be

made to know the reaction of the user is likely to have towards the new

system. As this is a very necessary system, people will use it. And it will be

able to achieve all its requirements. The users of the system dont need

thorough training on the system. All they are expected to know to operate

the system is the basic net surfing knowledge. It has a user-friendly

interface.

3.5. Data Flow Diagrams(DFD)

With DFD analysis can be carried out to precisely the level

of detail required. The technique exploits a method called top-down

expansion to conduct the analysis in a targeted way. The transformation of

data from input to output, through processed, may be described logically



15/58


an independently of physical components associated with the system.

These are known as the logical data flow diagrams. The physical data flow

diagrams show the actual implements and movement of data between

people, departments and workstations.

Initially a context diagram is drawn, which is a simple

representation of the entire system under investigation. This is followed by

a level 1 diagram; which provides an overview of the major functional

areas of the system.

The level 1 diagram identifies the major processes at a high

level and any of these processes can then be analyzed further - giving rise

to a corresponding level 2 process diagram. This process of more detailed

analysis can then continue through level 3, 4 and so on. However, most

investigations will stop at level 2 and it is very unusual to go beyond a

level 3 diagram.

A DFD is a graphical tool used in the structured analysis and

design techniques to describe and analyze the movement of data through

the system, including the process, data stores and data flows.

3.5.2 Context Level

3.5.3 Level 1



16/58



Users

User

Manag

ement

1

Login Request

View

2

Upload

3

Organi

zer

4

Admini

stratio

n

10

Slidesh

ow

5Authenticated

User Information

Slideshow table

Slideshow table

User Information

Slideshow

Application Settings

Slideshow requests

Us

ers

Nonmembers

Slideshow

Slide

RequSlidesho

w

Search

9

Search

Requests

Results

Results

Requests

Tags table

Modific

ation

6

Picture to

modify

Picture.Xml

Modification

information

Mail

7

Groups

8

User information

Group Name

Group

Information

Authenticated User

Result pictures


17/58


3.5.4 Level 2

Login and Session Management Process in detail



18/58


View Process in detail

Upload Process in detail



19/58


Organize Process in detail

Modification Process in detail



20/58


Mail Process in detail

Groups Process in detail



21/58


SYSTEM DESIGN

4.1 Input Design



22/58


Inputdesign is a part of overall system design. The input

design is the link between the information system and the user. The

activity of putting data into the computer for processing can be achieved

by inspecting the computer to read data from a written or printed

document or it can occur by having people keying the data directly into

the system. Since this application is a web based one, there will be the

bottleneck of slow network connections. The main objectives of input

design for this system are

Reduce the time delay for getting validation by doing it at the

Client itself.

Make the input process an easy one for the user. It should be flexible e.g. do not make user to upload files one

by one only or in a limited groups only, say only ten pictures

at a time. Allow them to upload as many as from the single

form itself.

The design of input should be in such a way that it should play

a role in restricting incorrect data getting into the system.

.

The samples of Webpage layout are given in the appendix.



23/58


4.2 Output Design

The output design is used to communicate with the user.Computer output is the most important and direct information source to

the user. Output generally refers to the results and information that are

generated by the system. Efficient, intelligible output design should

improve the systems relationship with the user and help in decision

making. In this Web application we dont have any reports. Our output is a

group of forms that will show pictures in different ways such as

slideshows, search results, and viewing a single picture in different sizes

available. While designing output the following things are considered.

It should easy for the user to understand

Try to accommodate everything in the 1024*768

screen, dont make the user scroll to the right and left.

The output should reach the client without much delay

i.e. we should sent only the appropriate sized pictures to

the client. Sending a big sized picture and showing it

with a reduced size at the client is not a good thing.

The samples of Output WebPages are given in the appendix.



24/58


4.3 Table Design

1. User Table

Primary key: UID

Field Type Size Description

UserName varchar 50 User Name

Password varchar 50 Users password

Count Integer 32Number of successive failed

attempts that happened recently.

NextAllowedTi

medatetime NA

Time until which the account is

blocked

HomeDirPath varchar 20Folder Path where all the users

stuff will be placed.

Email varchar 50 Email id of user

NextAllowedTi

medatetime NA

Time until which the account is

blocked

UID Integer 32 Unique ID for each user



25/58


2. Group Table

Primary key: GroupID


GroupID Integer 32 Groups ID

GroupName varchar 50 Groups Name

GroupPath varchar 20Folder Path where Groups XML

files will be located.

Type varchar 12

Specifies the type of the groupwhich can be

1.Public(anyone can join)

2.Restricted(only those invited by

the admin of the group can join)

3. Tags Table

Primary key: Tag


Tag Varchar 50 The tag itself.

ImgPaths Varchar(MAX)

Upto

2GB

String that contains path to all the

pictures that have this

particular tag.

4. Slideshow Table

Primary key: sildeshowID



26/58



SlideshowID Integer 32 Slideshows ID

username varchar 50 Name of user who created theslideshow.

setpath varchar 101

Path to the set.xml, in which paths

to all the pictures in the slideshow

can be located.

Collection Varchar 50

Name of the Collection in which all

the pictures in the slideshow can

be located.

SetName Varchar 50

Name of the Set in which all the

pictures in the slideshow can be

located.

4.4 Process Design



27/58


There are 10 modules in this system they are,

1. User Management : This module handles all the actions that are

related to user management such as,

Add a new user

Delete a user

Edit users profile

Login and session management

2. View: Viewing is the main function of the system, so I have grouped

the different types of viewing mechanisms into one module. The

main actions of this module is to generate and show the user(s) the

following things,

A users Home Page View

Groups Home Page

Set and Collection View

Individual Photo View

3. Upload : The only function this module does is to upload picture

files from users computer to the server

4. Organizer: This module allows the user to organize their pictures

that they have uploaded onto the server. The functions of this

module are,

Allow users to create and delete Collections.



28/58


Allow users to create and delete Sets within

Collections.

Allow users to move pictures from one set to another.

Allow Users to Delete a picture or a group of pictures.

5. Slideshow : This module performs the slideshow related operation,

they are,

Create a slideshow

Show a slideshow

6. Modification :This module allows user to modify the picture at the

server, two types of modification options this system gives is,

Crop a picture

Resize a picture

7. Mail: Mail module allows users of the system to communicate with

each another by sending messages. The main functions of this

module are,

Compose Mails

View Inbox

View sent mails

Contact management

8. Group: Users of the system can create groups, so that the group

members can put pictures to this group which then can be shared



29/58


by all other members of that group and they can comment on those

pictures. This module does all the group management activities,

Create a new group

Delete a Group

Add a user to a group

Quit a user from a group

9. Search: This module allows users and nonusers to search and find

pictures with a keyword called tag. A picture can have zero or

more tags associated with it. When the user searches for a tag, all

pictures that have the particular tag attached will be listed.

10. Administration: All setting that will affect all the users in the

system (e.g. users monthly upload limits, number of pictures that

they can have in a set etc.).



30/58


TESTING

&

IMPLEMENTATION

5.1 Testing

System testing is a critical element of quality assurance and

represents the ultimate review of analysis, design and coding. Test case

design focuses on a set of techniques for the creation of test case that

meet overall testing objective. When a system is developed it is hoped



31/58


that it performs properly. The main purpose of testing an information

system is to find the errors and correct them. The scope of system testing

should include both manual and computerized operations. System testing

is comprehensive evaluation of the programs, manual procedures,

computer operations and controls.

System testing is the process of checking whether the

developed system is working according to the objective and requirement.

All testing is to be conducted in accordance to the test conditions specified

earlier. This will ensure that the test coverage meets the requirements and

the testing is done in a systematic manner

Testing process

The strategy for system testing integrates system test cases

and design techniques into a well-planned series of steps that result in the

successful construction of the software. The testing must co-operate with

test planning, test case design, test execution and the resultant data

collection and evaluation. A strategy for software testing must

accommodate low level test and the necessary to verify that a small code

segment has correctly implemented as well as high level test that validate

major system functions against user requirements. Software testing is a

critical element of software quality assurance and represents the ultimate

review of specification design and coding. A series of testing is performed

for the proposed system before the system is ready for acceptance testing

TEST CASE DESIGN



32/58


More important, test methods provide a mechanism that can

help to ensure the completeness of tests and provide the highest

likelihood for uncovering error in software. Any engineered product can be

tested in one of two ways:

BLACK BOX TESTING

Black box testing focuses on functional requirements of the

software. That is, black box testing enables the software engineer to

derive sets of input conditions that will fully exercise functional

requirements for a program. It is a complementary approach that is likely

to uncover different class of errors than white box methods. Black box

testing attempts to find errors in the following categories.

Incorrect or missing functions.

Interface errors.

Errors in data structure or the external data base

access.

Performance errors.

Initialization and termination errors.

When computer software is concerned, black box testing alludes to tests

that are conducted at the software interface. Although they are designed

to uncover errors, black box tests are used to demonstrate that software

functions are operational, inputs are properly accepted and the output is

correctly produced and the integrity of external information is maintained.

Black box testing examines some functional aspect of a system with little

regard for the internal logic structure of the software.

The Black box testing methods is applied to this system is

applied to PhotoShare online photo sharing system. This testing was



33/58


done thoroughly and errors were found in the part of coding. They were

corrected.

WHITE BOX TESTING

White Box testing ,sometimes called glass box testing,

is that internal operations perfom according to specifications and all

internal components have been adequately exercised.

This testing:

Guarantee that all independent paths within a module have

been exercised at least once.

Exercise all logical decisions on their true and false sides.

Execute all loops at their boundaries and within their

operational bounds.

Exercise internal data structures to assure validity.

This testing method is applied to this system by executing the every loop

at the boundary and all the logical conditions are tested on their both

sides and every module is executed at least once.

The testing steps are

Unit testing

Integration testing

Validation testing

Output testing

User acceptance testing

Unit Testing



34/58


Unit testing focuses verification efforts on the smallest unit of

software design, the module. This is known as module testing. The

modules are tested separately. This testing is carried out during the

programming stage itself. In this testing step each module of the total of

10 modules in the system is found to be working satisfactory as regard to

the expected output from the module.

Integration Testing

Data can be lost across an interface. One module can have

an adverse effort on another. Sub functions, when combined may not

produce the desired major functions. Integration testing is a systematic

testing for constructing the program structure, while at the same time

conducting test to uncover errors within the interface. the objective is to

take unit tested modules and build a program structure. All the modules

are combined and tested as a whole. Here connection is difficult because

the vast expense of the entire program complicate the isolation of cause.

Validation Testing

After integration testing the software is completelyassembled as a package, interfacing errors have been uncovered and

corrected, and then test of software is conducted i.e. validation test

succeeds when software function in a manner that can be reasonably

expected by the client. Software validation is achieved through a series of

Black Box testing, which confirms with the requirements .Black Box testing

is conducted at software interfaces. This test through is designed to

uncover errors interfaces, is also used to demonstrates that software

functions are operational ,input is properly accepted ,output are produced

correctly. I made sure that the system solves the problem and it satisfies

all the customer requirements, user requirements and functional

requirements.



35/58


Output Testing

In this stage of testing we make sure that the outputs are

displayed properly. Checked whether the different types of views are

displaying properly and made sure that they all satisfy the output design

requirements specified in the output design section.

User Acceptance Testing

User acceptance of the system is the key factor for the success

of any system. Here we are not aiming a specific set of people as users.

Broadly we are aiming two types users for the system. One is an

Administrator and other is the Users. For the Administrator it matters only

the two Web forms that are designed to administrate the System. For

users, we assume that this group of people will contain people who are

novices in using computers. So testing of user form are done with a person

who is a novice in using Web Applications such as this. The reply was

good,. So this system is given a good rating in user acceptance testing.

5.2 System Implementation

System implementation is the final phase i.e, putting the utility

into action. Implementation is the state in the project where theoretical

design turned into working system. The most crucial stage is achieving a

new successful system and giving confidence in new system that it will

work efficiently and effectively. The system is implemented only after

through checking is done and if it is found working in according to the

specification.

Implementation Procedure



36/58


The Implementation procedure used for this system

contains following steps,

Test Plans

Training

Hosting

Test Plans

The implementation of a computer based system requires that

test data be prepared and that the system and its elements be tested in a

planned, structured manner. The computer program component is a

major subsystem of the computer based information system, and

particular attention should be given to the testing of this system element

as it is developed.

Training

Training have to be given for the administrator and it is only

the matter of getting familiar with two Web forms and the settings (what

each of the settings mean). For the users we cannot train the personally.

The system is developed in such a way that anybody who is familiar with

using internet based applications such as email can use it easily.

Furthermore they can use the FAQ help also to make their job easier.

Hosting

This system has one great feature which is its hassle free

installation. With many other Web based application we have to do a lot of

work to get the application up and running. Here it is so easy that the

system will be ready to use with just a click of the mouse. Tables will be

created, Xml files will get created and the necessary file hierarchies will

also be created. But if the customer is not using a third party hosting



37/58


service and they are hosting it on their own server they have to make sure

that the prerequisites are already installed on the server.

Post Implementation Review

After the system is implemented, a review should be conducted todetermine whether the system is meeting expectations and where

improvements are needed. System quality, user confidence and operating

systems statistics are accessed through such technique event logging,

impact evaluation and attitude surveys. The review not only assesses how

well the proposed system is designed and implemented, but also is a

valuable source of information that can be applied to a critical evaluation

of the system.

The reviews are conducted by the operating personals as well as thesoftware developers in order to determine how well the system is working,

how it has been accepted and whether adjustments are needed. The

review of the system is highly essential to determine the future

enhancements required by the system. The system can be considered

successful only if information system has met it objectives. The review

analyses the opinion of the users and identifies thier attitudes towards the

new system. Only when the merits and demerits of the implemented

system are known, one can determine what all additional features it

requires.



38/58


SYSTEM

MAINTENANCE

SYSTEM MAINTENANCE

The maintenance phase of the software cycle is the time in which a

software product performs the useful work. After a system is successfully

implemented, it should be maintained in a proper manner. System

maintenance is an important aspect in the software development cycle.



39/58


The system should be maintained and upgraded according to

the technological advancements. It ensures the data integrity, data control

and security. The system must be protected from fire and other natural

calamities. The backup copies of data must be maintained daily so that to

prevent the loss of data due to various reasons.

The need for the system maintenance is for it to make

adaptable to the changes in the software environment. There may be

social, technical and other environmental changes, which affect a system,

which is being implemented. Software product enhancement may involve

providing new functional capabilities, improving user displays and mode of

interaction, upgrading the performance characteristics of the system. Soonly through proper system maintenance procedures ,the system can be

adaptable to cope with these changes.Softwae maintenance is of course

,far more than finding mistakes.We may define maintenance by

describing four activities that are under taken to after a program is

released for use. Software maintenance activities can be classified in to

Corrective Maintenance

Adaptive Maintenance

Perfective Maintenance

Preventive Maintenance

Corrective maintenance removes software faults. Perfective

maintenance improves the system with out changing its functionality. The

objective of perfective maintenance should be to prevent failures and

optimize software.

Adaptive maintenance modifies the software to keep it up-to-date with

its operative environment. It may be needed because of changes in the

user requirements, changes I target platform, or changes in external

interface. Minor adaptive changes should be handled by normal



40/58


41/58


CONCLUSION

CONCLUSION



42/58


With this system the process of photo sharing has become

an easy process. Now no need to use other systems that are not intended

for this purpose. Its interface is very user friendly so that even people who

are novices in using internet applications can also use it very easily. It is

secure also because of the features like account lock out proofing against

XSS and SQL injection attacks.

7.1 Scope for future Enhancements

Though it offers may features, scope for future enhancements

are there some are,

Adding Note to specific areas of the picture: This feature will allow

users to mark a specific portion of the picture and give a text or note

attached to that marked area.

Allow users to search photos based on the camera model used to

take the picture : Currently users can search pictures based on the tags

attached to the pictures, if we implement this feature they can also search

pictures based on the camera that was used to take the picture.

Enhance the Upload Web Form : Enhance the picture uploading web

form so that it indicates how much portion of the picture is currently

uploaded using extensive use of AJAX.



43/58


BIBLIOGRAPHY



44/58


Microsoft .NET web-based Client Development

Authors-Glenn Johnson and Tony Northrup

Publisher-PHI Learning Private Limited.

System Analysis and Design

Author-Elias M. Awad

Publisher-Galgotia Publication.

Software Engineering, A Practitioners Approach

Author-Roger S. Pressman

Publisher-PHI McGraw Hill.

Database System Concepts

Authors-Avi Silberschatz, Henry F. Korth, S. Sudarshan.

Publisher-McGraw Hill

SQL Server 2005 Black Book

Authors-Patrick Dalton, Paul Whitehead.

Publisher-Dreamtech.



45/58


APPENDIX

9.1 SAMPLE SCREEN SHOTS



46/58


USER LOGIN FORM

ADMINISTRATOR SETTINGS FORM

USER SIGN UP FORM STAGE 1



47/58


USER SIGN UP FORM STAGE 2

USERS HOME PAGE



48/58


UPLOAD FORM

SAVE SETTINGS TO PICTURES AFTER UPLOAD



49/58


ALL COLLECTIONS OF THE USER

ORGANIZER



50/58


NEW GROUP CREATION

SEARCH IMAGES USING TAG



51/58


SEARCH RESULT

COMPOSE MAIL, ADD CONTACT



52/58


INBOX

COLLECTION CREATION



53/58


CREATE SLIDESHOW

SHOW SLIDESHOW



54/58


CROPPING A PICTURE

RESIZING A PICTURE



55/58


9.2 Some XML Files



56/58


1.Login.

10

4

Organize

Organize Your Photos With ease!

ImgPath

Edit

Edit Your Photos With ease!

ImgPath

Groups

Create Groups and share Your Photos With your group Friends!

ImgPath

Crop

Crop your Photos with ease

ImgPath



57/58


2.Adds.

6

THOB SYS software solutions pvt ltd.!.

Welcome all

google.com


Welcome all

google.com


Welcome all

google.com



58/58



Welcome all

google.com


Welcome all

google.com


Welcome all

google.com

Project Photo Share)

Documents

Transcript of Project Photo Share)