Friday, December 9, 2016

Time Based Tasks Tracking System





Object Oriented Analysis & Design 
Time Based Tasks Tracking System

Complete Source Code
Download Here


UML Diagrams
Download


Plate form
JAVA



Table of Contents
1.      INTRODUCTION.. 3
Defining the problem... 3
2.      Admin Module. 3
3.      Project Manager Module. 4
4.      DEVELOPER MODULE. 5
5.      STRUCTURE FLOW DIAGRAM... 5
6.      DEVELOPING SOLUTION STRATEGIES. 6
Benefits. 6
7.      IMPLEMENTATON PROCEDURE. 7
8.      INPUT OF BUG TRACKING SYSTEM... 7
9.      QUALITY ASSURANCE. 8
10.         SECURITY TECHNOLOGIES AND POLICIES. 8
11.         RESULT. 8
Advantages. 9
12.         CONCLUSION.. 9

1. INTRODUCTION


 This is the world of information. Bug and issue tracking systems are often implemented as a part of integrated project management system. This approach allows including bug tracking and fixing in a general product development process, fixing bugs in several product versions, automatic generation of a product knowledge base and release notes.


Defining the problem

The problem in the older system can be defined as the whole project maintenance, users maintenance and their assignment has to be maintained manually. The Software development companies have to face a lot of problems while maintaining manually all the maintenance of the projects, their bugs and their status. This type of problem makes the whole system an inefficient one and thus making a poor and unorganized working. In order to remove this type of problem, So that the paper is planned to develop. Bug tracking software is a “Defect Tracking System” or a set of scripts which maintain a database of problem reports. Bug tracking software allows individuals or groups of developers to keep track of outstanding bugs in the product effectively. Bug tracking software can track bugs and changes, communicate with members, submit and review patches, and manage quality assurance. This web-based business application is a great tool for assigning and tracking issues and tasks during software development and any other projects that involve teams of two or more people.

2. Admin Module


 The administrator too has the authority to update the master details of severity level , status level, etc, modules of the project. The administrator adds the users and assign them responsibility of completing the project. Finally on analyzing the project assigned to the particular user, the administrator can track the bugs, and it is automatically added to the tables containing the bugs , by order of severity and status.

 3. Project Manager Module
The administrator can know the information in tact the various projects assigned to various users, their bug tracking status, their description etc in the form of reports from time to time. The project wholly uses the secure way of tracking the system by implementing and incorporating the Server side scripting. The administrator can now add the project modules, project descriptions etc. He too adds the severity level, its status etc.

4. DEVELOPER MODULE










5. STRUCTURE FLOW DIAGRAM



6. DEVELOPING SOLUTION STRATEGIES

The main objective of the proposed system is to full analyze the bugs and report the same to the administrator in an efficient manner so that he can get right information at right times. The paper objective is to fully systematize everything so that the possibilities of bugs should be reduced at all levels.

Benefits

1) To track the status level of each project.
2) To track the status level of each bug in the project module.
3) To assign the projects to the users by the administrator.
4) To add the bugs by the administrator.
5) To add the status, severity levels by the administrator
6) To add a detailed bug information.
7) To add the modules in the project and to track the person developing it.
8) To add the project status levels by the project managers
9) To add the project bug levels by the users.
10) To give an efficient reporting system so that right decisions can be taken and at right times.
11) Moreover to make the system fully utilize to reduce the bugs.


7. IMPLEMENTATION PROCEDURE

Implementation is the stage, which is crucial in the life cycle of the new system designed. The main stage in the implementation is planning, training, system testing. Implementation is converting a new or revised system into an operational one. Conversion is the main aspect of implementation. It is the process of changing from the old system to the new one. After system is implemented, user conducts a review of the system. It is used to gather information for the maintenance of the system. The basic review method is a data collection method of questionnaire, interview etc.

8. INPUT OF BUG TRACKING SYSTEM

Input data is a part of the overall system design, which requires very careful attention. If the data going into the system is incorrect then the processing and output will magnify these errors. Input can be categorized as internal, external, operational, computerized and interactive. The analysis phase should consider the impact of the inputs on the system as a whole and on the other systems. In this paper, the inputs are designed is such a way that occurrence of errors are minimized to its maximum since only authorized user or administrator can able to access this tool. The input is given by the administrators are checked at the entry form itself. So there is no chance of unauthorized accessing of the tool. Any abnormality found in the inputs are checked and handled effectively. Input design features can ensure the reliability of a system and produce results from accurate data or they can result in the production of erroneous information.

9.         QUALITY ASSURANCE

Quality Assurance is „a planned and systematic pattern of all actions necessary to provide adequate confidence that the item or product conform to established technical requirements‟. This package is tested for Software Quality Assurance. During analysis and design phase, it is verified whether the requirements are satisfied by the design documents and found that the source code is consistent with the requirements specifications and design documentation. The Acceptance test plan is executed and the developer is satisfied with the expected outcomes.

10.                 SECURITY TECHNOLOGIES AND POLICIES

Software safety is a software quality assurance activity that focuses on the identification and assessment of potential hazards that may impact software negatively and cause the entire system to fail. The system is highly secured that all Forms are interlinked and follows the login so that only authorized users who have known the correct password can only enter and work with the system. The package could not exposed to outside hosts.

11.                 RESULT

The older system is a system which suffers from a lot of disadvantages:
1) Limitations of the older System
2) Has to maintain the whole system of
3) software development manually
4) Has to maintain the details of the project managers manually.
5) Has to maintain the details of the status of different projects manually.
6) Has to maintain the bug details, project descriptions, project status details, project description details, project list details manually.
7) No efficient reporting system.
In this paper we presented the results to overcomes the problem with older system. The bug tracking system fulfills different requirements of administrator and employee of a software development organization efficiently. The specific purpose of the system is to gather and resolve issues that arise in different projects handled by the organization. The advantages of this paper is:
Advantages

1) The different groups and representatives can interact each through internet.
2) Main objective of the system is to gather and resolve issues (bugs) that arise in different projects of the organization.
3) Reduce The Timing.
4) Internet application.

12.                 CONCLUSION

This Paper Bug Tracking and Reporting System helps an Software Concern to detect and manage the bug in their products effectively-efficiently. Utilizing bug tracking software can assist in troubleshooting errors for testing and for development processes. With the ability to provide comprehensive reports, documentation, searching capabilities, tracking bugs and issues, bug tracking software is a great tool for those software development needs. Depending on your development needs and the bug tracking software, you can hope to gain several benefits from bug tracking software. Some of the benefits are:
1) Improve communications between groups of people
2) Increase the quality of the software
3) Improve customer satisfaction with bug free software
4) Provides a form of accountability
5) Increases overall productivity


Library Management System






LIBRARY MANAGEMENT SYSTEM
 like link:

Uid: yasir.jaseem@gmail.com
Pwd: admin

Download Complete Source Code:
LMS

Plateform:
PHP Codeigniter Platform 

Table of Contents
Table of Contents.......................................................................................................................... iii
Revision History............................................................................................................................ iii
1.    Introduction.............................................................................................................................. 1
1.1         Purpose............................................................................................................................. 1
2.    Overall Description.................................................................................................................. 1
2.1         Product Perspective.......................................................................................................... 1
2.2         Product Functions............................................................................................................. 2
2.3         User Classes and Characteristics....................................................................................... 2
2.4         Operating Environment..................................................................................................... 2
2.5         Assumptions and Dependencies....................................................................................... 3
3.    External Interface Requirements........................................................................................... 3
3.1         Hardware Interfaces......................................................................................................... 3
3.2         Software Interfaces........................................................................................................... 3
3.3         Communications Interfaces.............................................................................................. 3
4.    System Design........................................................................................................................... 4
4.1         Application Architecture................................................................................................... 4
4.2         Database Modeling and Design......................................................................................... 4
5.    System Testing.......................................................................................................................... 4
5.1         Functional Testing............................................................................................................ 4
5.2         User Acceptance Testing.................................................................................................. 4
6.    UML Diagrams........................................................................................................................ 5
6.1         ERD.................................................................................................................................. 5

 


1.     Introduction

Library Management System is an online project where manager issue the books to registered students. This is a web based application where admin can add user, delete user, add book, delete book, issue book to the student, and make duplicate of the book.

1.1     Purpose

The purpose of this project is to keep track even a single book of library and record the history of books whenever is issued to students.

2.     Overall Description

2.1     Product Perspective

Library Management System is a real time application. Through this project all manual record of the library can be computerized and minimize the chances of errors. This is a web based project where manager issue the books to registered students. In this application admin can add user, delete user, add book, delete book, issue book to the student, and make duplicate of the book.



2.2     Product Functions


The functions of the system include
  • The admin can create users.
  • The admin can delete users.
  • The admin can edit users.
  • The admin can add students.
  • The admin can delete students.
  • The manager can add book in the system.
  • The manager can edit book.
  • The manager can delete book when it is lost.
  • The manager can issue book to the student.

2.3     User Classes and Characteristics

There are three types of user for the Help Desk Software:

  • Administrator: Admin of the system. He is responsible to add, update, delete users and student.
  • Manager: Manager of the library. He is responsible to add, update, delete book in the library and issue to the student.
  • Student: Student of the campus. He will issue books from library and responsible to return the book on time.

2.4     Operating Environment

This application is compatible with any browser that supports HTML5.

2.4.1    PHP

PHP is a server-side scripting language that provides database access, form processing, user authentication. In short, it has the capabilities for developing the Library Management System with all of the functionality described in the requirements’ analysis. It is used in conjunction with the Apache web server. It will also run on both Microsoft Windows and on the Linux platform.

2.4.2    My SQL Database

There are many different relational database management systems (RDBMSs) from a number of software manufacturers. Library Management System’s Analysis, design and implementation of a system decision to use My SQL is consistent with the choices made with the rest of the infrastructure.

2.5     Assumptions and Dependencies

·         The user should have sufficient knowledge about computer.
·         The computer should have internet connection and web browser.
·         The users know the English language, as the interface will be provided in English.

3.     External Interface Requirements

3.1     Hardware Interfaces

-|-   Client Side:    PC
-|-   Server Side:   PC

3.2     Software Interfaces

-|-   Front End Client:  CSS, HTML5
-|-   Data Base Server: My SQL
-|-   Back End: PHP

3.3     Communications Interfaces

·         Web Browser (Internet Explore, Firefox, Chrome)
·         Internet connection



4.     System Design


4.1     Application Architecture


The architecture of the application is designed to fit into the infrastructure at Library Management System which leads to a distributed n-tier application. This is defined as a model that helps developers to create flexible and reusable applications by breaking it up into different tiers. As a result, it is likely that if changes are made to a single tier, it is possible that the entire application will not need updating when those changes are made.

4.2     Database Modeling and Design


A sound database design will be the key to the success of this system. By ensuring that, at this stage, all the relevant information is incorporated into the system, the rest of the system design will fall easily around the database. Database design is generally thought to involve the modeling of different Entities, Relationships and Attributes. the design of the database is broken down into different stages:
 Conceptual database design
 Logical database design
 Physical database design

5.     System Testing

5.1     Functional Testing


The sole aim of the functional testing carried out is to ensure that the user cannot ‘break’ the system by entering erroneous data, where certain functionality has not been implemented. Library Management System has agreed that future developments will address this absence. Because of the prototyping approach, coupled with the fact that a second iteration now needs to be developed, it is felt that the tests provide some very positive feedback about the system. One of the most significant outcomes of the functional testing is the uncovering of the fact that field validation needs to be implemented on each of the forms.

5.2     User Acceptance Testing


At the beginning of this project, after all the requirements capture and analysis had been undertaken, it was necessary for Library Management System to sign-off the requirements list and for them to have an understanding of what would be included in the first prototype. More important than the validation testing is the acceptance from the Users that it works as they expect it to.


6.     UML Diagrams

6.1     ERD