ONLINE PROJECT MANAGEMENT SYSTEM Submitted in Partial Fulfillment of the Requirements for the Award of the Degree of MASTER

OF COMPUTER APPLICATIONS (M.C.A) BY Neha Sahotra 04511604409

BHARATI VIDYAPEETH’S INSTITUTE OF COMPUTER APPLICATIONS & MANAGEMENT (GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY) NEW DELHI 2012

CANDIDATE’S DECLARATION
I hereby declare that the work which is being presented in this project work entitled “Online Project Management System” in partial fulfillment of the requirements for the award of the degree of Master in Computer Applications at Bharati Vidyapeeth’s Institute of Computer Applications and Management, New Delhi is an authentic record of my own work carried out during the period, February – April 2012 under the supervision and guidance of Mr. Shivendra Goel (Internal Guide) and Mr. A. Saurikhiya (Project Guide). I have not submitted the matter embodied in this project work anywhere for the award of any degree or diploma.

NEHA SAHOTRA

ACKNOWLEDGEMENT
It is my proud privilege to express my profound gratitude to the entire management of Bharati Vidyapeeth and teachers of the institute for providing me with the opportunity to avail the excellent facilities and infrastructure. The knowledge and values inculcated have proved to be of immense help at the very start of my career. Special thanks to Hon’ble Founder, Bharati Vidyapeeth, Pune for having provided us an excellent infrastructure at BVICAM. I am grateful to Dr. M.N. Hoda (Director, BVICAM) and Mr. Shivendra Goel (Project Guide) for their astute guidance, constant encouragement and sincere support for this project work. I would like to thank CRRI (Central Road Research Institute) for providing me with an opportunity to pursue my industrial training, as it is an important part of the MCA course and it is the one that exposes you to the industry standards and makes you adapt yourself to the latest trends and technologies. At the same time, it gives an experience of working on a project. I feel pride and privileged in expressing my deep sense of gratitude to all those who have helped me in presenting this assignment. I would be failing in my endeavor if I do not place my acknowledgement. I express my sincere gratitude to Mr. Manish for his inspiration, constructive suggestion, mastermind analysis and affectionate guidance in my work, without which this project work completion would have been impossible for me. Sincere thanks to all my seniors and colleagues at CRRI for their support and assistance throughout the project.

NEHA SAHOTRA

meetings and reminders in order to make better communication. We have used ASP. This project is based on . sending messages to each other. This project entitled “Online Project Management System” is a web based application has been designed to improve team work .ABSTRACT A well planned. Project is designed user friendly and given good GUI (graphical user interface). Setting events. receiving on other end and sending back the answer. CSS and JSP at Front End and SQL Server 2008 at Back End The project has been an enriching experience for me in the field of programming. C#.net. systematically executed industrial training helps a great deal in inculcating a good work culture. In this Project. project Manager will be posting new project along with deadlines for the project and project Leader will be dividing the work among developers in order to make the work done. to Improve communication between team members and to improve effectiveness of work which includes go thru the menu options. .net. pressing the required buttons. It provides a linkage between students and the industry in order to develop awareness of the industrial approach to problem solving based on broad understanding of operations of the industrial organizations.NET environment.

5.1 6.LIST OF FIGURES Figure No.4 6.5.5.1 6.6 6.2 6.5.5.12 Screen Snapshot –assign module Screen Snapshot –Task form Screen Snapshot –Message form Screen Snapshot –Project form Screen Snapshot –Team Member form Screen Snapshot –About us Screen Snapshot –Features form 40 40 41 41 42 42 43 .8 6.5 Description Entity Relationship Diagram Use Case Diagram Level -0 DFD Level -1 DFD Level -2 DFD Screen Snapshot – Sign Up form Screen Snapshot – Home Page Screen Snapshot – About Us Page Screen Snapshot – Events form Screen Snapshot – Meeting form Page No.2 6.4 6.11 6.5.5.5. 14 33 34 35 36 37 38 38 39 39 6. 3.7 6.5.9 6.5.5.10 6.5.3 6.3 6.1 6.

1 2 3 4 5 6 7 8 9 10 11 Description Deliverables System Interface User Table Project Table Module Table Task Table Meeting Table Activity Table Role table Usermodule Table ErrorLog Table Page No. 4 5 15 15 16 16 17 17 17 18 18 .LIST OF TABLES Table No.

LIST OF ABBREVIATIONS Abbreviation ERD DFD GUI ASP act det dsg dur fu info msg phn reg rol sec unam usr wel usr Description Entity Relationship diagram Data Flow Diagram Graphical user interface Active Server Pages Activity Detail Designation Duration File Upload Information Message Phone Registration Role Security Username User Welcome User .

3 Leader Dashboard 3.4 Testing Phase 2.1 Logical Database Design 3.1.2 Table Structures 3.2.4 Constraints 2.4 Deliverables CHAPTER 2: PROJECT DESCRIPTION 2.1.1 ERD 3.2.1 Layout 3.1 Layout 1 2 3 4 5 5 5 5 8 9 10 10 11 11 12 12 14 15 19 19 20 .2.2 Manager Dashboard 3.3 Development Phase 2.1 Introduction about the Company 1.2.1 Layout 3.2.2.1 Login 3.2 Design Phase 2.3.2.1 H/W Requirements 2.3.2 Purpose 3.6 User Characteristics CHAPTER 3: FUNCTIONALITY 3.1 System Interfaces 2.3.2 S/W Requirements 2.2.1.2.2.3.CONTENTS CHAPTER 1: INTRODUCTION 1.2 Input Design 3.1 Requirement Phase 2.5 Assumptions & Dependencies 2.2.3 Proposed Solution 1.2 System Specifications 2.2 Purpose 3.2 Problem Statement 1.2.3.1.3 Methodology & Tools Used 2.

8 Current projects 3.5.3.3.3.1 Purpose 3.3.2.3.1 Layout 3.1.3.7 Meetings Page 3.4 Post Conditions 3.2.1.2 Purpose 3.3 Preconditions 3.4 Post Conditions 20 21 21 22 22 22 23 24 .1 Login 3.2 Actors 3.3.2.1 Layout 3.3.2.2 Purpose 3.2 Actors 3.7.2.3.3.4.6 Reminders Page 3.2.3.2.5.4 Post Conditions 3.8.3.2.2.3.3.3.2 Purpose 3.3.2.3.3 Preconditions 3.2.5 Basic Flow 3.1.3.1 Layout 3.1 Layout 3.3.5 Messages Page 3.3.2.2.3.1 Purpose 3.2.4.2 Purpose 3.5 Basic Flow 3.2 Purpose 3.6 Alternate Flow 3.2.6 Alternate Flow 3.2.2.2.3.2.3 Preconditions 3.6.2.7.3.2.8.1 Purpose 3.3 Messages 3.6.1.2.1 Layout 3.2 Authentication 3.3.2 Actors 3.3 Use Case Description 3.1.4 Developer Dashboard 3.2 Purpose 3.1.3.

3 Preconditions 3.3.3.3.7.3 Preconditions 3.4.3.5 Basic Flow 3.4.8.5 Basic Flow 3.6 Alternate Flow 3.3 Preconditions 3.8.3.3.1 Purpose 3.7.3.5 Basic Flow 3.3.5.6 Alternate Flow 3.5 Delete Leader 3.6.3.4 Post Conditions 3.3.3.3.6 Alternate Flow 3.3.6 Alternate Flow 3.3.5.3.6.5 Basic Flow 3.3.8.3.4 Add leader 3.3.3.4.3.4 Post Conditions 3.6.2 Actors 3.4 Post Conditions 3.7.8.5.3.6.4 Post Conditions 3.3.1 Purpose 3.3.6.3.6 Alternate Flow 3.5.2 Actors 3.3 Preconditions 3.4 Post Conditions 3.5.8 Subtask Planner 3.4.4.1 Purpose 3.3.2 Actors 3.7.3.2 Actors 3.6 Alternate Flow 24 25 25 26 27 .4.3.3 Preconditions 3.2 Actors 3.6 Add Developer 3.3.8.3.7.6.5 Basic Flow 3.3.5 Basic Flow 3.3.8.3.3.1 Purpose 3.3.7.3.3.3.3.1 Purpose 3.5.3.3.7 Delete Developer 3.

2.3.1 Purpose 3. 10.3.9.2 Tools Used For System Testing 4.3.9.6 Alternate Flow CHAPTER 4: TESTING 4.3. 10. 10.2 Unit Testing 4.2.2 Tools Used For Integration Testing 4.1 Methodology Used 4.1 Methodology Used 4.5 Acceptance Testing CHAPTER 5: CONCLUSION AND REFERENCES 5.3 References/Bibliography CHAPTER 6: APPENDICES A-1 Use Case Diagram A-2 Level – 0 DFD A-3 Level – 1 DFD 27 28 29 29 30 30 31 31 32 33 34 35 .3 Integration Testing 4.4 Post Conditions 3.6 Alternate Flow 3. 10.3.2 Actors 3.4.2 Tools Used For Unit Testing 4.3.1 Purpose 3.3.3.1 Conclusion 5.9 Subtask Report 3.4 Post Conditions 3.3.3.3 Preconditions 3. 10.5 Basic Flow 3.1 Methodology Used 4.3.3.10 Project Status 3.4 System Testing 4.1 Testing Activities 4.2 Future Scope for Modification 5.9.9. 10.4.3.3.2 Actors 3.3.3.9.9.3 Preconditions 3.3.5 Basic Flow 3.

A-4 A-5 Level – 2 DFD Input Design Layout 36 37 .

4 Introduction about the Company Problem Statement Proposed Solution Deliverables .2 1.CHAPTER 1 INTRODUCTION 1.1 1.3 1.

consultancy services and human resources. improvement of marginal materials. Pavement Engineering and Materials. a constituent of Council of Scientific and Industrial Research (CSIR) is engaged in carrying out research and development projects on design. utilization of industrial waste in road construction. road traffic safety and analysis & design.Introduction about the Company 1. The R&D areas of the Institute are on various aspects of roads transport and related activities viz.1 ABOUT CRRI CENTRAL ROAD RESEARCH INSTITUTE (CRRI) a premier national laboratory established in 1948. Geotechnical  1  . The Institute was founded in 1952 and is situated at the eleventh kilometer on Delhi .. construction and maintenance of roads and runways. service life assessment and rehabilitation of highway & railway bridges. wind. corrosion studies. management of roads in different terrains. CRRI endeavors to develop professional excellence in the area of roads and road transport through world class research and development program.Mathura Road (NH-2) in New Delhi. performance monitoring/evaluation. fatigue. traffic and transportation planning of mega and medium cities. ground improvements environmental pollution. Institute has the competence to organize National & International Training Programme continuing education courses since 1962 to disseminate the R&D finding to the masses. landslide control.

Planning & Management in addition to state of art computing facilities. Bridges and Instrumentation Engineering. Transportation Planning and Environment. Bureau of Indian Standards. most of the work involved in the software development process has to be done manually which is very time consuming and cumbersome and also. An attempt to get the complete working automated failed as the system could not be integrated into a functional whole.Engineering. I felt this shortcoming becoming glaringly evident. Moreover. accuracy and speed of retrieval of data. It is not that no effort has been made towards this end. code of practices issued by Indian Roads Congress. safety and socio-economic analysis. infrastructure divisions and administrative sections. CRRI plays an unique role in the preparation of national standards and specifications. traffic engineering. geometric and pavement design of roads. requirements and budget. sponsored and contract R&D projects and also continues to provide consultancy services to government. Road Development. Government of India) in all road transportation related areas especially on materials. road construction maintenance management. A discussion with my project guide produced enthusiastic response and I decided to take the challenge. Being a premier national laboratory.2 Problem Statement A Client/User who wishes to get his software/project developed has to contact different Providers either physically or telephonically before deciding upon a particular Provider that best suit his needs. CRRI has carried out extensive in-house.  2  . public and private sector organizations. it reduces the efficiency. Traffic Engineering and Road Safety. Ministry of Roads Transport & Highways and National Rural Road Development Agency (Ministry of Rural Development. 1. The institute has highly qualified and experienced 120 Scientists with PhD/Master degrees in various subjects to undertake interdisciplinary activities.

 3  . events. The proposed system is a computerized system.  The system enables security benefit to stores all the detail into the database very easily. All will be given different functionalities.  The system enables to provide communication between the project leader and member of the project. Through which they can share there projects with other professionals projects. The problem is that we want to develop a web portal for R& D professional in the roads and transportation sector. he will b registered as Manager or Leader or Developer. after that he will become member of our web portal. First person have to register with website.Our goal during requirements analysis is to understand “what” the customer “needs” us to build. There are three types of users. 1. The OPMS web portal has been developed for CRRI. Exploitable technology and latest news will also be displayed on the home page of website. And project leaders can communication with other project leader and member of the project. We build a model of the application and validate that our model will actually meet the customer’s needs. messages and meetings.  The system enables the data store the professional and other personal detail into the database. current projects. all projects. It would considerably reduce the late work and late response. And without any reference person nobody can make a member of that system. The sections will be my projects. This will after successful completion of development and testing work the website will be submitted to NIC for final hosting at domain server of NIC. And login will authenticate users by user name and password and according to their designation they will be redirected to their corresponding dashboards.3 Proposed Solution The New proposed system will increase the efficiency and effectiveness of the current system.

and provide facility to improve the existing system of the CRRI.  4  . Phase 1 Requirement Analysis Deliverable Requirement Document. No. the project leader and member of the project also send the add member request to the other project member.  System login through mail id and password. 1.  The system enables to reduce paper work. use case 2 Design Entity Relationship Diagrams . connect direct mechanism 3 4 5 6 7 Implementation Unit Testing Integration Testing System Acceptance testing User Acceptance Testing Coding Test Results Test Results Complete operational System Validation of system by users of the system Table-1: Deliverables Page No.  In the system all major and manage process doing by the Administrator.4 Deliverables S. Activity Diagram . The system enables to view profile of the project leader and member of the other project.

1 H/W requirement 2.3 Development Phase 2.1 Requirement Phase 2.4 Testing Phase 2.4 2.2 Design Phase 2.1 2.5 Post Implementation Maintenance 2.3.2.3.2 S/W requirement 2.2 System Interfaces System Specifications 2.3 Methodology and Tools Used 2.3.3.2.3.CHAPTER 2 PROJECT DESCRIPTION 2.6 Constraints Assumptions & Dependencies User Characteristics .5 2.

2.1 .NET Framework System Requirements To ensure adequate performance.2.NET Framework has the following minimum and recommended system requirements for client and server applications:  Operating System Requirements:  5  .2 S/W Requirements 2. Description Table 2 2.2.css.net . c#.net.2 System Specifications 2.2. No.1 System Interfaces Sr.2.1 H/W Requirements Scenario Required Processor Recommended Required RAM Recommended Client Server Pentium 500 MHz* Pentium 1 GHz Pentium 667 MHz* Pentium 1 GHz 64 MB* 128 MB* 128 MB or higher 256 MB or higher 2. Used for database connectivity. .NET framework SQL Server 2008 Used Asp. 1 2 Content/ Component/ Application(s) .

0 Server with service pack 6.0a or later MS Windows 2000 Professional MS Windows 2000 Server MS Windows 2000 Advanced Server MS Windows 2000 Datacenter Server MS Windows XP Home Edition Professional MS Windows Server 2003 Family Note: On all these systems.0a or later MS Windows NT 4.0 MS Windows 2000 Server with service pack 2. MS Internet Explorer 5.01 or later and MS Windows Installer 2. Server MS Windows 2000 Professional with service pack 2.0 MS Windows 2000 Advanced Server with service pack 2.0 Workstation with service pack 6.0 or later are also required.NET Framework is supported on the following platforms: --------------------------------------------------------------------------------------------------Scenario Operating System -------------------------------------------------------------------------------------------------Client MS Windows 98 MS Windows 98 Second Edition MS Windows Millennium Edition MS Windows NT 4.The .0  6  .

Net.6 or later Windows Management Instrumentation (WMI) SQL Server . COM+ services and SQL Server . Windows.7  7  .0 MS Windows XP Professional MS Windows Server 2003 Family  Additional Software Requirements: To use additional features such as ASP.MS Windows 2000 Datacenter Server with service pack 2.Net Data Provider MS Data Access Components (MDAC) 2. Millennium Edition and Windows XP) COM+ Services Windows 2000 service pack 2.NET Data Provider. you will need the following additional software: --------------------------------------------------------------------------------------------------Scenario Feature Required Software --------------------------------------------------------------------------------------------------Client Components Provider Access to system management (MDAC) 2.Net Data MS Data Access (Installed with OS on Windows 2000.0 Server SQL Server .

This helped him in deciding the interface.3 Methodology and Tools Used 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. Development of the prototype obviously undergoes design. coding and testing. then converted to classes and objects. Later on. input and output requirements. converted to coding using Visual Studio. The goal of prototyping based development is to counter the first two limitations of the waterfall model discussed earlier.Net 3.3.5 and MS SQL Server 2005 for backend. A prototype is a working model that is functionally equivalent to a component of the product. that prototype was further improved to be “Online Project Management System”. This prototype is developed based on the currently known requirements. Object oriented approach is the approach followed overall. then their functions and roles were searched and at the last stage. Method of Prototyping Model is followed to gather the user specifications. The basic idea here is that instead of freezing the requirements before a design or coding can proceed.0 2.ASP. A throwaway prototype of the proposed system. And those requirements should be  8  .Net MS Internet Information Services (IIS) 5. The objects of the entities related to the system were designed. 2. based on the currently known requirements. that is what is required and what is need of client. was initially given to the user so that he has a fair idea about how the proposed system is going to be like.1 Requirement Phase In the development of the system first step is gathering requirements. a throwaway prototype is built to understand the requirements.

higher priority functionality can be designed first and implemented first. Fact-finding is the first step in Requirement Elicitation.  Events can be set. Functions required by client were:  Dashboard as per designation of user. determination of scope.documented for throughout reference of project. As project is to be developed for an organization so requirement should be very clear as it will be used by so many users and they will be having different needs 0.  Reminders can be set. In this approach sub modules can be added  9  .  Member can check project currently running. Requirement Engineering is a process which includes Requirement Elicitation. These functions can be integrated into one of the main module of the development.  Messaging system. it is known what is required by the user. 2. Requirement analysis and Requirement documentation. Project is designed using bottom up approach. Requirements are captured from various viewpoints in activity.3. then next step designing interface which should be user friendly and appropriate to fulfill all the functionality demanded by user.  Meetings can be set. Number of meetings is held to take the requirements. identification of similar systems. and identification of domain and risk surveys. it includes the covering up the facts and listing down all the activities and key terms whatever comes to mind.2 Design Phase After Requirement Phase.  Member can check his projects.

Integration and System Testing. the major interfaces can be tested. An excel sheet was maintained for quick reference.NET. c#. So. In object oriented approach. Thus. Design phase of the project includes:  Level – 0 DFD  Level – 1 DFD  Level – 2 DFD 2.e. JSP. at the beginning of the project. CSS.3.any time even if requirement changes as requirement can be changes at any instant of time.  SQL Server 2003. Front end Designing is done in Asp.net.net. so it is better to   10 . that is all data is picked from database so read data and write data functions are created in order to read from database and write into the database.3 Development Phase The technologies used in developing this project are namely:  ASP. .4 Testing Phase The testing phase for the project comprised of Unit. 2. our project is completely dependent on database connection . verified or exercised. Our development phase started with writing down the procedures of sql server in order to save compile time. the whole development process is object oriented and implementation is also done in object oriented environment i.net.3. We did the manual testing for all the three types and no tool was used in any of the three level of testing. the semantic constructs appear at all the stages. As already mentioned. anticipated testing technique automatically implies to be object oriented.

Step 4: Finally. Step 2: Unit testing was exercised in context to object orientation in which each class with their methods and operations were scrutinized. One client can add many projects at a time on Website Assumptions: We will be provided with required software and hardware required to perform the test automation.5 Assumptions and dependencies  The cost and price estimation for a project undertaken by a given organization is already known and is not considered by the system.4 None Constraints 2.   11 .  A single project can be awarded to only one service provider. Step 3: Integration testing at various stages of testing was exercised to find associative errors. Regression testing was utilized but at the same time. stress testing. security testing. the testing strategy is divided in the following steps: Step 1: Object oriented analysis and object oriented design models were checked for consistency. 2. it was also based on object oriented view.find the problem in early stages so that we start testing parallel to development process and will be taken in consideration at each stage. recovery testing etc.  One service provider can work on many projects at a time. Grossly. termination of testing was supported by Validation testing and System testing which includes requirements review.

General Manager. Chairman Etc.  Adequate manpower resources with required skills will be available Any delays in feedback. brought to the attention of the manager.  Access to required environments available. approvals and sign-offs may result in a change to the project schedule and cost. shall be resolved as soon as practically possible. The resources should be available for any query/clarification. CEO. 2. Lower Level Management: Like. comments.  Issues/ Queries/ Review comments from the manager and other senior members. Technical Expertise   12 .Team Leader.6 User Characteristics User classes Top Level Management of Any Organization: Like.Any queries or concerns impacting the project. Middle Level Management: Like.Software Engineer.Managers of the Organization. Dependencies:  Strategy document sign-off. QA Members etc Educational Level The user should be software professional or having good knowledge of computers and comfortable with the English.

The user should be comfortable with using general purpose application software for any organization   13 .

CHAPTER 3 FUNCTIONALITY 3.3.2.2.2.2.5 Messages Page 3.2.2 Purpose 3.7 Reminders Page 3.2 Purpose 3.6 Meetings Page 3.1 Layout 3.1 Login 3.1 Layout 3.1.1 Logical Database Design 3.2.2 Table Structures Input Design 3.7.2.2.2.2.2.1 Layout 3.1.1 ERD 3.2 Manager Dashboard 3.7.6.2.5.2.2.1 Layout 3.2.4.3 Leader Dashboard 3.2 Purpose 3.2.2.2 .1.6.2 Purpose 3.2.2 Purpose 3.2 Purpose 3.2.1 Layout 3.4 Developer Dashboard 3.2.8 Current projects 3.2 Purpose 3.2.2.2.8.1 Layout 3.1 Layout 3.1.3.2 Purpose 3.4.5.2.8.2.1 Layout 3.2.

3.3.5.3 Preconditions 3.2 Actors 3.3.5.3.3.1.3.2 Actors 3.3.3.2.3.3.6 Alternate Flow 3.2 Authentication 3.3.3 Preconditions 3.3.3.2 Actors 3.2 Actors 3.3.3.4.2.3.3 Messages 3.5.5 Delete Leader 3.3.3.3 Preconditions 3.5.3.3.6 Alternate Flow 3.2.6 Alternate Flow 3.1.6 Add Developer .1 Purpose 3.3.2 Actors 3.1 Purpose 3.3.3 Use Case Description 3.5 Basic Flow 3.1 Login 3.3.3.3.4 Post Conditions 3.2.4 Post Conditions 3.3.4.3.3.3.5 Basic Flow 3.3.4 Post Conditions 3.4.3.3 Preconditions 3.3.5.3.6 Alternate Flow 3.4 Post Conditions 3.1 Purpose 3.5 Basic Flow 3.3.6 Alternate Flow 3.3.3.1.3.1.1.4.5 Basic Flow 3.1.2.4.3.1 Purpose 3.3.3.3 Preconditions 3.1 Purpose 3.5.4 Post Conditions 3.3.4.4 Add leader 3.5 Basic Flow 3.2.3.3.

3.5 Basic Flow 3.9. 10.3.3.3.7.2 Actors 3.3. 10.3.3.2 Actors 3.3.3.9.9 Subtask Report 3.6 Alternate Flow 3.3.5 Basic Flow 3.6 Alternate Flow 3.6.6 Alternate Flow 3.3.8.4 Post Conditions 3.7.8.7.7 Delete Developer 3.5 Basic Flow 3.7.2 Actors 3.3 Preconditions 3.9. 10.3.1 Purpose 3.3.3.3.3.3.4 Post Conditions 3.3 Preconditions 3.7.9.3.3.4 Post Conditions 3.6.2 Actors 3.1 Purpose 3.6 Alternate Flow 3.1 Purpose 3.3. 10.3.8.6 Alternate Flow .4 Post Conditions 3.6.9.3.3.3 Preconditions 3.3. 10.3.3.9.5 Basic Flow 3.5 Basic Flow 3.6.3.4 Post Conditions 3.8.3 Preconditions 3.6.1 Purpose 3.8. 10.3.8 Subtask Planner 3.6.8.7.3.3 Preconditions 3.3.3.10 Project Status 3.3.3.1 Purpose 3.3.3.2 Actors 3.

1. For a Project like.3. ER Diagram  14 . all level of user’s requirement along with the interface should be given higher priority.1 ERD After gathering all the requirements when each and every requirement is clear that is what is needed by the system then Entity Relationship Diagram is designed.1 Logical Database Design 3. Online Project Management System where system will be used for management of big project. Use case diagram all the entities were first found out then their relation was established and then we came across the full .1.Entity Relationship Diagram For Online Project Management system. Figure 3.

0) Contains Project id which is foreign key in most of the tables. 3. 0) Contains project start date Contains project completion date Contains project status.3. 0) decimal(18.  15 . p_title p_obj p_leader nchar(50) nchar(50) decimal(18. 4 Project Table Field Name Data Type Description p_id decimal(18. 0) nchar(20) nchar(20) nchar(20) nchar(20) nchar(20) decimal(18.1. 0) Contains user id’s for login Contains user name Contains user Passward for login Contains user type i. User table Field Name Data Type Description u-id u_name u_pass u_type u_add u_email u_mobile decimal(18. Contains project cost.2 Table Structures Table No.e user designation Contains user address Contains user email id Contains user mobile number Table No. 0) Contains Current quantity in hand Contains Name of the Medicines Contains project leader id so that it can establish relation with user Table p_sdate p_cdate p_status p_cost date date decimal(18.

Contains module priority. 6 Task Table Field Name Data Type Description t_id mod_id mem_id decimal(18. 0) decimal(18. 0) decimal(18. 0) nchar(20) date date decimal(18. 0) Contains Task start date Contains Task completion date Contains name of task Contains Task status. 5 Module Table Field Name Data Type Description m_id p_id mem_id m_name m_sdate m_cdate m_status m_pri decimal(18. 0) Contains Task id Contains Module id of that task Contains Member id to whom task is aloted t_stdate t_cdate t_name t_status date date nchar(20) decimal(18. Table No. 0) decimal(18.   16 . 0) decimal(18. 0) Contains Module id Contains Project id Contains Member id Contains module name Contains Module start date Contains project completion date Contains Module status. 0) decimal(18.Table No.

7 Meeting Table Field Name Data Type Description mt_id pr_id mt_text mt_date mt_time mt_venue m_purpose decimal(18. 0) decimal(18. 0) nchar(50) date time(7) nchar(50) nchar(50) Contains meeting id Contains Project id Contains meeting Text Contains meeting date Contains meeting time Contains meeting venue Contains meeting purpose Table No. 9 Role Table Field Name Data Type Description RoleID RoleName smallint nvarchar(50) Contains role id Contains Role name   17 . 0) Contains activity id Contains activity description Contains activity Status Contains task id as foreign key Table No.Table No. 0) nchar(50) decimal(18. 8 Activity Table Field Name Data Type Description a_id a_des a_status t_id decimal(18. 0) decimal(18.

11 ERRORLOG Table Field Name Data Type Description ErrID Message Source Method STacktrac PageLocation n uniqueidentifier nvarchar(200) nvarchar(50) nvarchar(50) nvarchar(MAX) varchar(200) Contains Error ID Contains message Contains Source Contains method Contains Stack trace Contains page location where error appered GeneratedOn datetime Contains date when error appered  18 . 0) decimal(18. 10 USermodule Table Field Name Data Type Description UserID ModuleID decimal(18. 0) Contains user id Contains Module ID Table No.Table No.

2 3.1.11.2.2.1.2 Manager Dashboard 3.4 Constraints:  Id should exist otherwise access to main application is not allowed  Blank password is not allowed 3.2.2.1. 3.4 Data Storage Table: user.2.1 Login Screen Name – login page Ref No . He will assign project to leader. Once a user is created he/she can enter and manage the system by doing login with his/her id and password 3. reminders and project report. And user is asked to enter the id and password again. figure 6. Blank id and password is not allowed. Information required is user id and password. Referred Table:  19 .2.2.2.1. his messages . The control is passed over to his dashboard else access is denied.1 Layout Screen Name – manager-form Ref No .3.7) 3.2 Purpose The first screen is login screen which will redirect user to his dashboard. figure 6.(Appendix A-5.2.2 Purpose This screen contains all data related to manager like his projects.2.2. Page no.9) 3.(Appendix A-5. 41. 38.3 3. Here we have to enter the login id and password and if the password matches with its particular id which is checked against the table User.1 Input Design Layout 3.2. 3. Page no.5.3 Data Storage Table: User.2.2.

4 Constraints:  Null values not allowed in Project id and project name.2. Blank use id and password is not allowed.id is not allowed  Blank password is not allowed 3.2 Purpose   20 . 3.4 3.5.2 Purpose This screen contains all data related to Leader like his projects.(Appendix A-5.4. events table. 40. events table.2. Constraints:  Blank user. reminders and project progress and he can allot modules and task to developers. 3. his messages .6) 3. reminders table.3.2. Page no.2.3 Data Storage Table: user.2. reminders table.2. Referred Table:  Message table. Information required is user id and password.3.1 Layout Screen Name – leader Form Ref No .3.3.2.3 Leader Dashboard 3. figure 6.2.3 3. Once a user is created he/she can enter and manage the system by doing login with his/her id and password 3.1 Developer Dashboard Layout Screen Name – Developer Form 3. Message table.2.3.4.

8) 3.4 Referred Table:  Project  21 .2.6. his messages.5.2.(Appendix A-5. to whom msg is to send and by whom.6 Reminder Table 3.2. reminders and developer can post new progress.2.This screen contains all data related to Developer like his projects. 3.3 Data Storage Table: Reminder 3.  To update status num of tasks completed cannot be null.3 Constraints:  Module id can’t be null.2 Purpose This will give the reminder 3.2.2. figure 6. 3.5. Once a user is created he/she can enter and manage the system by doing login with his/her id and password 3.5. Information required is user id and password.2.5.6. 41.6.5 Messages page 3.1 Layout Screen Name – Messages Form Ref No .2. Blank id and password is not allowed.2.3 Data Storage Table: message table Referred Table: Project table 3.2.6.1 Layout Screen Name – Reminder Form 3.4.e.2 Purpose Message screen will show all the info related to messages i. Page no.

2. time.5) 3.6.2.2. Page no.7.2.1.5 Constraints: 3.3. 3. purpose.(Appendix A-5.2.3.8.2.3 Use Case Descriptions 3. 3.1 Login  22 .2 Actors  Manager  Leader 3.7. user name and password will be validated. figure 6.3.8. This functionality is given to all type of users.7.4 Referred Table: Project 3.8 Current project page 3. 3.2.1 Layout Screen Name – Meeting Form Ref No .3 Data Storage Table: Project table 3.1 Purpose All users will be redirected to their corresponding dashboard after login.3 Data Storage Table: meeting table 3.1. and venue of meeting.8.2 Purpose Meeting screen will show all the info related to meeting i.7.8 Meeting page 3.1 Layout Screen Name – current project Form 3.2 Purpose This screen contains all current projects running which is opened by link given in the menu at left.2. 39.3.2.5.7 None 3.2.e.2.

2.2 Authentication 3.3.3 Preconditions Id and password should be entered 3.2.2.6 Alternate flows None 3.5 Basic flow Login will be followed by registeration.3.1 Purpose User id and password should be authenticated for security purpose so that no unauthorized action can take place. 3.3. 3.3. developer 3.1.3.3 Preconditions All users should be registered first.2 Actors  Manager  Leader  developer 3.1.5 member Basic flow At time of login user name and password validated.3.3.3.2. 3.3.2.3.4 Post Conditions System is secure only those users can access which are authorized 3.1.3 Messages   23 .3.1.4 Post Conditions Member will be reflected to his dashboard 3.3.2. 3.6 Alternate flows None. 3.

3.4..3.3.6 Alternate flows  24 .3.6 Alternate flows He can directly send messages to any other member.4 Post Conditions He can check status of project i.4.1 Purpose To make more communication between team members.4. 3.3.3.3.3. 3.2 Actors  Manager 3.3.e..3 Preconditions  Member should login.3.5 Basic flow He will login then check status of other projects then post project and then can add leader to project.3. 3.2 Actors  Manager  Leader  developer 3.3.4 Add Leader 3.3 Preconditions  Manager firstly post new project.3.4. can check project progress.5 Basic flow Member user first can check his inbox then can reply back thru message.4.3.3.4 Post Conditions The messages are send which can checked late.3.3. 3. 3.1 Purpose To assign project work to leader 3. 3.3. 3.3.4.3. 3.

3.5.6. 3. 3.3.5. can check project progress.1 Purpose To assign project task to developer 3.5. 3.6 Add Developer 3.3. 3.3 Preconditions  Manager should login.3. 3.5 Delete Leader 3.3.6.3.2 Actors  Manager 3..4 Post Conditions He can assign same project to other leader.5 Basic flow   25 . 3.6.e.5.5.4 Post Conditions He can check status of project i.3.3.5.3.3.6.6 Alternate flows None.5 Basic flow He will login then check status of other projects then post project and then can delete leader to project. 3.1 Purpose To take authorities back from leader if he is not performing well.6.None.3.3.3.2 Actors  Leader 3. 3.3 Preconditions  Manager will first divide project into modules and then into task then assign task to member developer.

3.3. 3.He will login then check status of other projects then divide project and then can add developer to task.8.2 Actors  developer 3.2 Actors  Manager 3.6.6 Alternate flows None.8.8.1 Purpose To make work more efficiently.7 Delete Leader 3.1 Purpose To take authorities back from leader if he is not performing well. 3.4 Post Conditions  26 .8.3. 3.3.5 Basic flow He will login then check status of other projects then post project and then can delete leader to project.3 Preconditions  Manager should login.3.7. 3.7.6 Alternate flows None.7. 3.3.7.3. 3.3. 3.4 Post Conditions He can assign same project to other leader.3.3. 3.3. 3.7.7.3.8 Subtask planner 3.4 Preconditions  Developer should login.3.

9.3 Preconditions  Developer should login.9.3.10 Project Status 3.3.3.3.1 Purpose To give progress of project.2 Actors  Leader  Manager 3. 3.9.9.5 Basic flow He will login then post status of his tasks.9.10. 3.8.2 Actors  developer 3.9 Subtask report 3.10.3.3.6 Alternate flows He don’t make planner 3.He can implement the planner to do the work.3 Preconditions  27 .1 Purpose Can be viewed by leader and Manager.3.10.3.3. 3.3.6 Alternate flows None 3. 3.3. 3.8.5 Basic flow He will login then post status of his projects then can add planner for his work.9. 3.3.3.4 Post Conditions He can check updates 3.

10.5 Basic flow He will login then check status of projects.3. Manager and Developer should login to check status. 3.6 Alternate flows None  28  .3.10.4 Post Conditions Can check updates 3. 3.10.3.

4 System Testing 4.1 Methodology Used 4.3.4.2.2 Tools Used 4.1 Methodology Used 4.2 Tools Used 4.2 Tools Used 4.CHAPTER 4 TESTING 4.1 4.4.2 Testing Activities Unit Testing 4.5 Acceptance Testing .3.2.3 Integration Testing 4.1 Methodology Used 4.

4.2 Tools Used None. 4.1 Methodology Used Manual testing was carried out.4. The approach of testing was to make sure the system does everything that its specification claims.3 Integration Testing The integration testing was also done manually by adding forms which are linked together and flow is checked.  The unit testing was done by the developer itself by running the indivisiual 4. Checked if data from one page to another page is moving correctly.1 Methodology Used Integration testing was also done manually. No third party tool was used in this. and does not do anything that it should not. So testing starts from very first step after designing. unit. 4.3.   29 .2 Unit Testing pages and checks the validation of page considering requirement specification. integration and system testing.2. The unit test cases were prepared with the help of requirement specification and system test cases were prepare by taking the help of use case diagram.e. We used the manual testing approach for all the three levels of testing i.2.1 Test Activities Testing is very important as it is better to add lesser functionalities rather than number of bugs. 4.

4.3.2 Tools Used
None.

4.4

System Testing

For System Testing a test document was prepared which was based on the use case diagram which had all the requirements of the system which were given by client.
4.4.1 Methodology Used

System Testing was done based on test specification. 4.4.2 Tools Used
None.

4.5

Acceptance testing

The user acceptance testing was done by the user itself. A document is there in which all the test cases are there includes all the requirements that the user has asked for is mentioned in that document. This document is prepared during requirement analysis. 4.5.1 Methodology Used User Acceptance Testing was done based on test specification, the testing was done manually. 4.5.2 Tools Used
None.

 

30

CHAPTER 5 CONCLUSION AND REFERENCES
5.1 5.2 5.3 Conclusion Future Scope for Modifications References/Bibliography

5.1

Conclusion
The aim of our project was to develop a web based application which will

be used to online management of projects as the old system was manual and there is so much wastage to time if for any small review, or for a discussion a meeting is to organize. Fully functional web based Online Project management system that ensures efficient, timely and easy management of Project work improve quality and save time. Also it insists on standardizing the workflow, division of task along with time constraints enhance overall performance of the project. Through Intranet services, management will have access of online information as well as communication become quite simple. It is very good for planning and sequence of activities is defined. Priority of work can b set so that higher priority work is finish first. Timely management of task is there. It is well clear who is doing what so that it keep track of work load over a member. Also it gives project progress i.e. percentage of project finished and left and according to deadlines of project development speed can be increased so that work can be finished on time

5.2 Future Scope for Modification
As it is need of time to change as technology changes. Changes are must and it is very important that our applications work according to the latest demand of the market. The application exists only till these are able to satisfy user demands. Its human beings nature to always demand for more. So updating in the work is the need of today’s world. Project modifiable anytime according to the changing needs and technology so “Online Project Management System” has the provision to be updated to strand strongly against user demands.

In old system there is no automation of projects management everything is manual. so Online Project Management System is introduced . 

31

Aggarwal “ Software Engineering” .Wrox publication.  Elmasri/Navathe “Fundamentals of Database Systems” 3rd Edition 5th Reprint 2001  K. 5.” Professional C# with .Willey India Pvt.net  Online MSDN  32 . New Delhi.K. As security is major issue for an organization security constraints can be enhanced in future .We can work on left out validations to enhance the security of the application. Search feature based on different parameters can also be added.We can extend this project and add that feature too.NET ”. References Websites  www.  Christian Nagel “Professional C# 2008” . Apress publication.asp.3 References/Bibliography  Andrew Troelsen. New Delhi.Ltd. Last but not least we can make a provision to generate reports based on different criteria as will be entered by the users.

CHAPTER 6 APPENDICES 6.2 6.4 6.5 Use Case Diagram Level – 0 DFD Level – 1 DFD Level – 2 DFD Input Design Layout .1 6.3 6.

6.1 Use Case Diagram Use Case Diagram   33 .

2 Data Flow Diagram  34 .6.

3 Level – 1 DFD Level 1Dfd   35 .6.

6.4 Level – 2 DFD Level 2 DFD   36 .

6.1 Sign Up form Figure 6.5.5 Input Design Layout 6.1 Screen Snapshot – home(sign up)  37 .5.

2 Home Page Figure 6.5.3 Screen Snapshot – Home Page(Login) 6.5.4 Screen Snapshot – About Us Page   38 .6.3 About Us Figure 6.5.5.

6.5.5 Screen Snapshot – Events form 6.5Meeting Figure 6.5.4 Events Figure 6.5.5.6 Screen Snapshot – Meeting form  39 .

7 Task Font Figure 6.5.5.6 Module Form Figure 6.5.6.7 Screen Snapshot –Leader dashboard click on assign module 6.5.8 Screen Snapshot –Leader dashboard click on assign module then task is assigned of particular module by taking module id  40  .

5.9 Screen Snapshot –Message Form 6.5.6.10 Screen Snapshot .8 Message Figure 6.5.9 Project Figure 6.Manager Dashboard click on post new project  41  .5.

5.11 About Us Figure 6.5.5.5.11 Screen Snapshot –Leader dashboard click on Team Member 6.6.10 Team Member Figure 6.12 Screen Snapshot –About us page  42 .

12 Features Figure 6.5.5.6.13 Screen Snapshot –Features page   43 .

Sign up to vote on this title
UsefulNot useful