SYSTEM

SUBMITTED BY,

MUNAVIRA.VP

REG NO: 14P22J0328

WEB FILE MANAGEMENT

IN PARTIAL FULFILMENT OF THEREQUIREMENT OF THE AWARD FOR THE DEGREE OF BACHELOR OF COMPUTER APPLICATION

INTRODUCTION• File sharing is one of the oldest applications of the

internet. One way of sharing files online is for a user to upload files to a common space on the web and others users can download the files from the common web space.

• The objective of this project was to design an web file management system website where users can upload files and other users can download them

• . Web file management is practice of sharing files among different users across the internet. Common forms of file sharing are FTP (File Transfer Protocol) model for file sharing network. Users of a web file management system website, who use features like upload, download, share, search etc would want a website that is very interactive and fast

WEB FILE MANAGEMENT SYSTEM

• Using Web File Management system users can store files, documents, images, videos through online in a secured manner. In this user can store documents and files in any format and share them as a link with users. It’s a online web application here all the file details stores in MySQL Database and file stores in the server.

• This file manager which stores files, documents, images, video presentations, etc without any limit.

EXISTING SYSTEM• The existing Web File Management System of

collaboration uses computer tools such as email and Office. Users generally have to download each revised file and access it to make changes. They have to keep abreast of all the emails to ensure they know, which the current version of the document is. Any changes made in the document is difficult to note unless users take the effort to personally comment on each change. This system is time consuming and cumbersome to follow for most collaborators.

PROPOSED SYSTEM• The proposed Web File Management System will

provide a single platform for all the people working on a file to collaborate on. Security of the file will be ensured by rigorous authentication and users will be see all changes made. The file creator will maintain complete control over the changes in the document and can also control access of different users. There is no way that the file can escape the system unless the creator exports the file in a common file format

OBJECTIVES• First objective was to build a web file management system

website which not only reduces the annoying postbacks and loss of control focus, but also gives a faster and more interactive user interface.

• Second objective was to give the users different visualizations of their file system. where they have the option to sort their files and folders based on size, type, and time uploaded

• Third objective was to analyze the issue of file storage. Two common places where files can be stored are database and the web server

MODULES• Registration module• Uploading module• Searching module• Downloading module• Sharing module• Admin module

HARDWARE REQUIREMENTS

• PROCESSOR: Intel Pentium II or above

• RAM : 1 GB or above

• HDD : 2 GB

SOFTWARE REQUIREMENTS

• PLATFORM : WINDOWS 7

• FRONT END: JAVA SCRIPT, PHP, CSS

• BACK END : SQL SERVER

SYSTEM REQUIREMENTS

FEASIBILITY REPORT• Preliminary investigation examine project feasibility, the

likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time.

• There are aspects in the feasibility study portion of the preliminary investigation:

• Technical Feasibility• Operation Feasibility• Economical Feasibility

TECHNICAL FEASIBILITY

• security.

• A system is said to be technically feasible only if the system can be developed by using the existing technology. Our system satisfies technical feasibility, owing the existing technology, reliability, ease of access and

ECONOMIC FEASIBILITY

• This test is carried out to determine the costs of conducting a full system investigation, to costs of required hardware and software and the benefits in the form of reduced costs. The costs to conduct preliminary investigation, cost of hardware and software were not considerable due to the availability of all requirements at college. The benefits in developing the system are substantial

OPERATIONAL FEASIBILITY

• A system is said to be operationally feasible only if it can be turned into information systems that will meet the organizations operating requirements. The “Virus Tracking System” has no barrier in operation and implementation. Further, it reduces manual effort and increases the performance when compared to conventional methods. It increases efficiency and also it automatically valuated. Our system thus found to be operationally feasible.

SYSTEM DESIGN

• The system design starts by converting the logical model of the system into physical model. Physical model represents the transactions that take place in the system and the physical components that are involved; the documents for the physical models namely, flow of charts for the program.

NORMALISATION

• Normalization is the process of efficiently organizing data in a database. There are two goals of the normalization process: eliminating redundant data (for example, storing the same data in more than one table) and ensuring data dependencies make sense (only storing related data in a table). Both of these are worthy goals as they reduce the amount of space a database consumes and ensure that data is logically stored.

NORMALISATION (cotd)•  Insertion anomaly: Inability to add data to the database due to absence of other data.•  Deletion anomaly: Unintended loss of data due to deletion of other data.•  Update anomaly: Data inconsistency resulting from data redundancy and partial update•  Normal Forms: These are the rules for structuring relations that eliminate anomalies.•  FIRST NORMAL FORM:•  A relation is said to be in first normal form if the values in the relation are atomic for• every attribute in the relation. By this we mean simply that no attribute value can be • a set of values or, as it is sometimes expressed, a repeating group.• SECOND NORMAL FORM:• A relation is said to be in second Normal form is it is in first normal form and it should• satisfy any one of the following rules . Primary key is a not a composite primary key• No non key attributes are present Every non key attribute is fully functionally dependent • on full set of primary key.•  THIRD NORMAL FORM:• A relation is said to be in third normal form if their exits no transitive dependencies

E-R DIAGRAMS• E – R DIAGRAMS

The relation upon the system is structure through a conceptual ER-Diagram, which not only specifics the existential entities but also the standard relations through which the system exists and the cardinalities that are necessary for the system state to continue. The entity Relationship Diagram (ERD) depicts the relationship between the data objects. The ERD is the notation that is used to conduct the date modeling activity the attributes of each data object noted is the ERD can be described resign a data object descriptions. The set of primary components that are identified by the ERD are

• Data object • Relationships• Attributes• Various types of indicators. The primary purpose of the ERD is to represent data objects and their relationships.

DATA FLOW DIAGRAMS• A graphical tool is used to describe and analyze the

movement of the data through a system manually or automate including the process of data storage, and delay in the system. DFD’s are central tools and the basis for the development of other components. The transformation of data from one process to another process is independent of physical components. These types of DFD’s are called LOGICAL DATA FLOW DIAGRAMS. In contrast, physical data flow diagrams show the actual implementation and movements of the data through people, departments and workstations.

ADVANDAGES OF DFD• Users, persons who are part of the process being studied, early

understand the notations. So analysts can work with the users and involve them in the study of data flow diagram. For accurate business activity users can make suggestions for modification and also they examine charts and spot out the problems quickly. If the errors are not found in the development process they will be very difficult to correct latter and the system may be failure.

• Data flow analysis permits analyst to isolate areas of interest in the organization and study them by examining the data that enters the process and see how it is changed when it leaves the process.

DFD SYMBOLS

• DATA FLOW

• DATA STRUCTURE

• EXTERNAL ENTITY

OR DATA LINK

• PROCESS

• DATABASE

SOFTWARE TESTING• Software testing

Software testing is a crucial element of Software Quality Assurance and represents the ultimate review of specification design and coding. Errors tend to creep into our work when we design and implement the function, condition or controls that are of the main stream. The logical flow of the program sometimes encounter intuitive meaning that our unconscious assumptions about flow control and data may lead us to make design errors that are uncovered only once path testing commences.

• Verification

Verification is the process to make sure the product satisfies the conditions imposed at the start of the development phase. In other words, to make sure the product behaves the way we want it to.

TYPE OF TESTING• There are many types of testing like• Unit Testing• Integration Testing• Functional Testing• System Testing• Stress Testing• Performance Testing• Usability Testing• Acceptance Testing• Regression Testing• Beta Testing 

FILENAME EXTENSION

TYPE AND SIZE OF FILE

SAMPLE SCREENS

REGISTRATION MODULE

UPLOAD MODULE

SEARCH MODULE

TABLES USED

REGISTRATION TABLEColumn name Data type size constraintsReg_id int 15 Primary key

Reg_name varchar 20 null

Reg_mail varchar 25 null

Reg_password varchar 20 null

Reg_date date 10 null

UPLOAD TABLEColumn name Data type size constraintUp_field int 10 Primary key

Up_filename varchar 20 null

Up_file varchar 20 null

Up_filetype varchar 20 null

Up_filediscription varchar 20 null

Up_date date 10 null

Up_userid varchar 20 null

SEARCH TABLEColumn name datatype size constraintFile_id int 10 Primary key

File_name varchar 20 null

File_type varchar 20 null

DOWNLOAD TABLEColumn name Data type size constraintUp_field int 10 Primary key

Up_filename varchar 20 null

Up_file varchar 20 null

Up_filetype varchar 20 null

Up_filediscription varchar 20 null

Up_date date 10 null

Up_userid varchar 20 null

SHARE TABLEColumn name datatype size constraintid int 10 Primary key

Sender_id int 10 null

Receiver_id int 10 null

File_id int 10 null

THANK YOU