Академический Документы
Профессиональный Документы
Культура Документы
CONTENTS
1. TITLE OF THE PROJECT 2. INTRODUCTION AND OBJECTIVES 2.1 Background 2.2 Objective 2.3 Purpose 3. PROJECT CATEGORY 4. SYSTEM REQUIREMENTS
4.1 Tools / Platform 4.2 Software Requirement Specification 4.3 Hardware Requirement Specification
8. STRUCTURE
8.1 Modules 8.2 Module Description 8.3 Data Structure 8.4 Implementation Methodology 8.5 List of Reports
9. NETWORK ARCHITECTURE 10. SECURITY 11. FUTURE SCOPE AND FURTHER ENHANCEMENT 12. BIBLIOGRAPHY
2. INTRODUCTION
This Software titled as Resourse Planning Tool and Secure file Sharing System developed for tracking the project status and sharing them in secured manner. The expected audience of this document is the faculty of IGNOU (IRS) and the administrator officers of various organization .This documents is also facilitates the requirement of those who need to do back tracking in further.
2.1. BACKGROUND Existing System In existing system all the project activity are done manually by the project leader and the team members. The customer manually requests the project by visiting the organization directly. The employee manually receive request from the higher authorities and fix meetings and also ask them for modification manually. All the day to day works are done manually followed by the paper file system.Almost all organization in our state receives huge number of projects from their customers in every day. Then minimum 10-15 customers are reached every working day.The administrator of the the organization accepts all these requests and assigned to the corresponding project leaders .Then they scheduled the project and assigned to the employees. The documents are stored as paper files.
Proposed System
The proposed system overcomes all the problems involved in the existing system. The main aim of the system Resourse Planning Tool and Secure file Sharing System is to messure the project status and monitoring them to the clients in a transparent way.In the proposed system, the tool is used to help the project leaders to smoothly track and monitor the project activities, defines tasks, compare estimated with actual time report, create
chart and report. The project leaders manage the project on a day-to-day basis, coordinate communicate and facilitate all activities and review the project deliverables.User can store his own documentations in a centralised media with searching facility.The client can request the projects by online and check the progress of them and can give the proper suggestion to the employees.finally they can download the completed project from the site.The projects are protected with private key and can shared only by authorized people.the project leaders can easily scheduled the task and assigned to the team membaes in a structured manner.the proposed system provides a timeshhet management system and using this the authorities can check the total time of the individual employe for a particular task.So the documents will be completed on the fixed time that is requested by the clients.The admiminstrator can easily managed the entire system. 2.2 OBJECTIVE The main objective of the Proposed System is Office automation of the entire organization. To the proper completion of the documents in very short time. Timesheet management for every project.
Project track management. Update the employee details and client details. Easy way communication between cient and admin of the organization. . 2.3 PURPOSE Project tracking management is the main purpose of the proposed system. In the proposed system the client can demand their requests to the organization by online. Better interface to the clients is essential for catch the customer attraction ,the proposed system provide the better
presentation.Project scheduling ,time sheet management,proper checking the status ,uploading the documents on time are essential to complete the work on time,the proposed system helps to meet these needs. Proposed system stored the document the datas in secured manner and clients can easily downloading them. The proper staff ersonal and technical data also update through this system
3. PROJECT CATEGORY
Web based RDBMS is the project category selected for this system .
4. SYSTEM REQUIREMENTS
4.1 TOOLS / PLATFORM We have noticed that PHP along with the MYSQL server (RDBMS) is advisable for the project and decided to use the Windows platform.
: : :
About PHP
MySQL
MySQL is a relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases. The MySQL development project has made its source code available under the terms of the GNU General Public License, as well as under a variety of proprietary agreements. MySQL is owned and
sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned by Sun Microsystems, a subsidiary of Oracle Corporation. Members of the MySQL community have created several forks such as Drizzle and MariaDB. Both forks were in progress long before the Oracle acquisition (Drizzle was announced 8 months before the Sun acquisition).Free-software projects that require a full-featured database management system often use MySQL. Such projects include (for example) Word Press, phpBB and other software built on the LAMP software stack. MySQL is also used in many high-profile, large-scale World Wide Web products including Wikipedia, Google, Drupal and Facebook 4.2 SOFTWARE REQUIREMENTS Front end Middle ware Back End : : : html 4.0 PHP MYSQL
4.3 HARDWARE REQUIREMENTS Processor Main Memory Cache Memory CPU Speed Hard disk capacity CD ROM Drive Monitor : : : : : : : Pentium IV or above 256MB RAM 512KB 1.6MHz 20GB or above 52x 15 Color
5 REQUIREMENT ANALYSIS
5.1 PROBLEM DEFINITION It is very difficult to handle all the projects manually by the project leader and team members. It will take lots of time and man-work to prepare such repots. There is very high chance of mistakes on that reports. It will be very difficult to make a simple change in the reports. Computerization of the proposed system helps to prepare reports with accuracy and easy. It will be very easy to make changes in reports.In the existing system the customer has to request their demands by visiting the organization directly.But the proposed system helps the clients to submit the request by online and track the status of the project and finally download the completed document.Its very difficult to schedule the project manually.but the proposed project helps the employees to prepare the proper schedule and complet the Project on time.There is no security for the documents of the existing system.The proposed system helps to share the document for the users in a secured manner.
5.2 REQUIREMENT SPECIFICATIONS 5.2.1 Functional Requirements Main functions are: 1. Employee management 2. Technology management 9
Indira Gandhi National Open University
3. PL selection 4. TL selection 5. Client management 6. Key generation 7. Project management 8. Project scheduling 9. Timesheet management 10. Document management 11. Document sharing 5.3 PLANNING AND SCHEDULING A very elementary Gantt or Timeline Chart for the development plan is given below. The plan explains the tasks versus the time taken to complete the project. Gantt Chart: Novemb er Requirement Gathering Database & Interface Design Coding Quality Assurance Testing Build Documentation Decemb er Januar y February March
10
11
The software developing is upgradable and also additional features can be added. The tool selected is highly flexible in nature. Future this software can tied with other organizations to satisfy the all types of customer demand. This software is very much user-friendly .
12
13
14
15
16
8.STRUCTURE
8.1 MODULES The project Resource Planning Tool and Secure File Sharing is used to track the status of the projects and share them in secured manner This project has eleven modules 1. Employee management 2. Technology management 3. PL selection 4. TL selection 5. Client management 6. Key generation 7. Project management 8. Project scheduling 9. Timesheet management 10. Document management 11. Document sharing 8.2 MODULE DESCRIPTION EMPLOYEE MANAGEMENT
The Admission management module contains the employee details.This modules update the day to day status of their work according to their timeshhet It changes the project to the suggestion which is given by team leaders.This module is used to upload the finished project
TECHNOLOGY MANAGEMENT The document management stores the tasks and technology details
17
PL SELECTION This module select the project leaders from employ list,and select the team members under the PL
TL SELECTION This module select the Team leaders from employ list,and select the team members under the TL
CLIENT MANAGEMENT This module contains client details.This module helps to request the project,checking the status of the project
KEY GENERATION This module provides the private and public key for the users
PROJECT MANAGEMENT This module accepts the client request and approving or rejecting the project
PROJECT SCHEDULING This module assigns the project to the PL.Set the start date and the end date of the project.Decide the technologies and task duration of the project. This module
18
TIMESHEET MANAGEMENT This module is used to enter the hours worked per day by day by each employee with the type of work done and other details for each project.Tmesheet chart is calculated based on the employee login andlogout time.It also provides the status and description of the project. DOCUMENT MANAGEMENT This module is used to catogeries the document.Its used to upload the project to the application.the uploaded file metadata will go to the database for indexing and searching purposes.The file Content will goes to the system in encryoted format..This module provides the file browser ,from this window user can view his uploaded file can give suggestion ,searching and downloading the project.
DOCUMENT SHARING This module is used to share the data.its also use to set the permission to users.
19
8.3.
Data Structure
1. Client_details Table 1 Length Constraints 20 Primary Key 20 20 15 15 15 15 15 15 15 Not null Not null Not null Not null Not null Not null Not null Not null Not null
Field Name cl-id cl-name cl-address cl-email cl-website cl-contact person cl-contact phone cl-loginid cl-password cl-reg-date
Data Type Varchar char char char char char Varchar Varchar Varchar Date
Description Uniquely identifies client id Name of the client Address of the client Email of the client Website of of the client name of the contact person Phone no of the contact person Id of the client Password of the client Reg date of client
20
2. Project_details Table 2 Field Name Pjt_id Data Length Constraints Type Varchar 10 Primary key Description Stores the unique alphanumeric id of project Stores project name Stores description of the project Expected end date of the project Project request date Status of the project
25 25 10 10 10
Not null Not Null Not null Not null Not null
21
Data Length Constraints Type Varchar 10 Primary key Varchar Varchar Date Varchar 25 25 10 10 Foreign key Not Null Not null Not null
Description Stores id of approved project Stores project id Stores reply of the project request date of the reply Status of the repy
22
Description Stores the id of admin Stores password of the admin Stores the client suggestion
Varchar
50
Not Null
4.Technology_ details Table 5 Field Name Tech-id Tech-name Data Type Varchar Varchar Length Constraints 10 10 Primary key Not null Description Stores the id of technology Stores store the name of the technology
5.Task_details 23
Indira Gandhi National Open University
Table 5
Length Constraints 10 10 50
Description
Primary key Stores the id of task Not null Stores name of the task Not Null Stores the description of the task
6.Teammember_details Table 6 Field Name Mem-id Emp-id Data Type Varchar Varchar Length Constraints 10 10 Foreign key Foreign key Description Stores the id of member Stores store id of the employee
7..pjt-tecnology_details
24
Table 7
Length 10 25 25 10 10
Constraints Primary key Foreign key Not Null Not null Not null
Description Stores id of schedule Stores project id Stores start date of project End date of the project Description of the project
25
Length Constraints 10 10 10 50 Foreign key Foreign key Foreign key Not Null
Description Stores the id of project task Stores the id of task Stores the id of project Stores the total time of the task
10..pjt-assigned Pl_details Table 7 Field Name Pjt-id Emp-id Data Type Length Constraints Varchar Varchar 10 10 Foreign key Foreign key Description Stores the id of project Stores the id of emp
26
Data Type Length Constraints Varchar Varchar Varchar 10 10 10 Foreign key Foreign key Foreign key
Description Stores the id of project Stores the id of emp Stores the id of the project task
27
Field Name Data Type Tli-id Tli-dt Tli-time Tli-empid Tli-taskid Tli-des Varchar Date time Varchar Varchar Varchar
Length 10 10 10 10 10 10
Constraints Primary key Not null Not null Not null Not null Not null
Description Stores id of timelogin Stores date of timelogin Stores time of timelogin Stores id of timelogin emp Stores id of timelogin task Stores description
28
13.TS logout_details Table 13 Field Name Tlo-id Tli-id Tlo-dt Tlo-time Tlo-status Tlo-taskid Tli-des Tlo-perc Data Type Varchar Varchar Date time Varchar Varchar Varchar Varchar Length 10 10 10 10 10 10 10 10 Constraints Primary key Foreign key Not null Not null Not null Not null Not null Not null Description Stores id of timelogout Stores id of timelogin Stores date of timelogin Stores time of timelogin Stores status of project Stores id of timelogin task Stores description Stores the percentage of the project
29
30
Length 10 10 10 10 10 10 10
Constraints Primary key Primary key Foreign key Not null Not null Not null Not null
Description Stores id of document Stores name of document Stores the id of group Stores the name of created person Stores created date Stores path of thedocument Stores type of the document
16 Userkey_details Table 16 Field Name Pub-id Emp-id Pri-id Data Length Constraints Type Varchar 10 Not null Varchar Varchar 10 10 Foreign key Not null Description Stores the public key for user Stores the id of emp Stores the private key for user
31
17.permission_details Table 17 Field Name Perm-id Emp-id D-id permision Data Type Varchar Varchar Varchar Varchar Length Constraints 10 10 10 10 Not null Foreign key Foreign key Not null Description Stores the permission id for user Stores the id of emp Stores the document id Store the permission
32
Implementation is the final stage and it is an important phase. It involves the individual programming, system testing, user training and the operational running of developed proposed system that constitute the application subsystems. The implementation phase of the software development is concerned with translating design specifications in to source . The user tests the developed
system and changes are made according to the their needs . Implementation methods The three types of implementation are: Implementation of a new computer system to replace an existing one. Implementation of a modified application to replace an existing one. Implementation of a computer system to replace a manual.
8.5 LIST OF REPORTS Employ details Client details Project details Project documentation details
9 NETWORK ARCHITECTURE
The Proposed system
33
10 SECURITY REQUIREMENTS
Web services security constitutes the technological and managerial procedures applied to the system to ensure the confidentiality, integrity and availability of information that is exchanged by the web services. System security can also be ensured using validation mechanisms like: Identification and authentication
The verification of the identity, a process called authentication is considered a security measure. Passwords are the most common mechanism for authentication. Its often useful to limit the number of authentication attempts. Security Management
The system requires some sort of management generally an administrator who is entrusted with the safeguard of the data.
The document can be further enhanced such that it includes online help files that provide support to the users. The software is developed in PHP which makes the system more reliable and compatible with the other environments. The application proves better extensibility and flexibility for future enhancements. Any further requirement application is possible with the same features guaranteed.
34
12 BIBLIOGRAPHY
1. System Analysis And Design 2. Software Engineering A Practitioners Approach, McGraw-Hill 5th Edition By ROGER S. PRESSMAN 3. An Introduction to Database Systems, Galgotia 2002 By Bipin C Desai 4. MCS 034 Software Engineering, By IGNOU
35