27-08-2014, 02:53 PM
DefectTrackeris a web based application to manage the Testing processes in IT Company for their developed Software/Web Applications. The application has three types of users; Administrator, Tester & Programmer. All the users of the system have assigned different rights according to their User Type(s). Administrator can create new users (Tester as well as Programmer) & manage Projects to be tested. Also administrator can see the list of bugscorrepesonding to each project. Along with, all these privileges, administrator could also update the statuses of users, projects etc. The projects added by the administrator would be having some priorities as well as statuses. The administrator will assign the project to a tester as well as a programmer. Tester can maintain a list of Bugs of a specific project with sufficient information in the .DefectTracker. system. Programmer can view the bugs logged by the Tester, after fixing the Bugs, Programmer change the Status of bug(s). Also the programmer / tester can change the status of the projects if he/she feels that the project assigned to him/he
PROJECT DEFINITION
DefectTracker is a web based application to manage the Testing processes in IT Company for their developed Software/Web Applications.The application has three types of users; Administrator, Tester & Programmer. All the users of the system have assigned different rights according to their User Type(s). Administrator can create new users (Tester as well as Programmer) & manage Projects to be tested. Also administrator can see the list of bugs correpesonding to each project. Along with, all these privileges, administrator could also update the statuses of users, projects etc. The projects added by the administrator would be having some priorities as well as statuses.
The administrator will assign the project to a tester as well as a programmer. Tester can maintain a list of Bugs of a specific project with sufficient information in the .DefectTracker. system. Programmer can view the bugs logged by the Tester, after fixing the Bugs, Programmer change the Status of bug(s). Also the programmer / tester can change the status of the projects if he/she feels that the project assigned to him/her has been completed successfully. Tester is allowed to reopen any fixed Bug(s), if he/she is not satisfied. Using .DefectTracker., IT Company can easily keep track of the bugs in the Testing of Projects.
OBJECTIVES
The objective of the system would be:
1. It demolishes the paper work involved in Testing process of a IT company as automates the
processing of posting the project, testing the project as well as removal of bugs by the programmer.
2. To maintain the information of users(about Testers as well as Programmers) of a Company.
3. To provide proper interface for generating Bug Reports.
4. To provide the user friendly interface for managing the status of Project for Testing Phase.
5. To provide the user friendly interface for managing the status of Bugs corresponding to each project for Testing Phase.
6. It allows a Company to easily keep track of Bugs to evaluate a Project.
System Study and Problem Formulation
Requirements specification:
Requirements specification is the activity during which requirements are recorded which may be in natural language or in a graphical form. The requirements specification describes:
· what the system will be to the users
what kind of system the designers need to build what kinds of things need to be tested for the testers
· All needed hardwares and software.s for the proposed software are available.
· The proposed software is economically feasible.
Detailed Study of the Existing System
This phase provides the overall requirement for the system what is to be done. Input for this phase is the information collected through several data collecting schemes such as survey, cross-questioning-answering etc and the raw data obtained which is not properly ordered and not in the precise manner. So here this raw data is converted into useful information written in precise manner and thus output is a formal document. After collecting all the information and requirements, they were verified from the concerned persons by presenting a diagrammatic version of the proposed system. The points missing were added to the system specifications for the desired system. So this final document provides the system requirement specifications for the desired system. It helps in reducing the total development cost and also establishes the various points for validation and verification.
User Requirements
Since end users are the ones who are finally going to use the system, their requirements need to be identified. This involves questioning the end users what their expectations were. The main requirement of the end user is that the system should be easy to use and take less time. In addition to these another important factor was to eliminate the need for database conversion and migration that had to be carried out presently. After conducting interviews with the users a document called the software requirement specification was created. This is the most important document that forms the basis for system development. It should be consistent, complete, unambiguous, traceable and inter-related.
This document has the following components:
Functional Requirements: The functional requirements specify relationship between the inputs and outputs. All the operations to be performed on the input data to obtain output are to be specified. This includes specifying the validity checks on the input and output data, parameters affected by the operations and the other operations, which must be used to transform the inputs into outputs. Functional requirements specify the behavior of the system for valid input and outputs.
Performance Requirements: This section includes performance of the product that is set by user interaction and studying the existing system of the organization. These are stated in complete measurable terms, so that they can be verified during system evaluation phase. Some of the performance requirements are stated below:
· User Friendly: the system produced is user friendly, understandable and easy to use so that the users of the system can easily learn to use the system. For this the system is made menu-driven with well-documented programs.
· Time Element (response and processing time): the response time of the system is very less and takes less time to execute queries and triggers.
· Maximum Throughput: the system gives maximum throughput with relevant output
· Robustness: the system will be able to handle undesirable situations and errors encountered at various levels e.g. if the user supplies invalid input for processing, the system gracefully halts, displaying a message to the user indicating the cause of the error and prompting him it enter the correct input.
· Flexibility: the system is flexible in nature so that likely changes and alterations can easily be made.
· Information Security: records in the system must be safe, confidential and must be prevented from unauthorized access.
· Moral and User Satisfaction: system will be able to satisfy the user requirements; this is the main and conspicuous measure of the system performance. Also the system must raise the moral of the user. The higher the moral, greater the expected work performance level.
External Interfaces and Data Flow: This heading specifies the externally observable characteristics of the software product. Several graphical tools are used to express the requirements of a system rather than writing long lines of text. These are very effective tools for use during the system analysis phase.
User Displays
These are extremely useful tools for interactive applications where fast response is needed. The user displays consist of screens that help in designing a menu driven system. The menus attached to the screens help in making a system interactive and user friendly by providing an easy to use point and click interface to the application. These menus consist of a list of options from which the user can choose an action depending on the task to be performed. So these forms or so called user displays is the key to the success of the entire system.
The Proposed System
Objectives of the Proposed System
The development of the proposed system is done keeping in view the problems in the existing system. The proposed system will not only overcome the limitations of the present system but will also provide the following characteristics.
The objective of the system would be:
1. It demolishes the paper work involved in Testing process of a IT company as automates the processing of posting the project, testing the project as well as removal of bugs by the programmer.
2. To maintain the information of users (about Testers as well as Programmers) of a Company.
3. To provide proper interface for generating Bug Reports.
4. To provide the user friendly interface for managing the status of Project for Testing Phase.
5. To provide the user friendly interface for managing the status of Bugs corresponding to each project for Testing Phase.
6. It allows a Company to easily keep track of Bugs to evaluate a Project.
Business Functions Provided in Proposed System
Managing Users: - System provides the administrator to activate or deactivate user account of type tester and programmer. The system also provides the administrator to create user accounts of type tester and programmer.
Projects Maintenance and Allocation: That allows adding or updating the details of all projects under development. The projects could be assigned or reassigned to a programmer and a tester by the administrator. The users could be able to change the status of the project in case he/she feels that the project alloted to him/her has been completed. Also the project could be reopened by administrator in case he/she feels that the project has not been completed yet.
Bugs Logging and Tracking: It allows the valid user of type tester to log and view the bugs of all projects under development after the successful login into the system. But if the user is of type administrator or programmer then view the list of bugs and programmer can change the status of bugs.
Account Maintenance: - The system allows the registered user to manage information of their account.
Change Account Information: Update Account information like Name, Email ID & other detail.
Change Password: Change own password.
Login Functionality: - To access this application, users would be required to login through a login screen. After authentication user would be able to access the application according to his/her privileges.
Requirements of the System
Input Requirements of the System
Login details.
Projects under development information
Users (tester, programmer) of the company information
Assignment of projects to a programmer and a tester
Output Requirements of the System
Status of the bugs of all the projects
Status of all the projects
Development, Operation and Maintenance Environments
Development Environment: Having constant interaction with the users as well as management aids in the system development. The logical user suggestions sure certainly welcomed and considered. There is a multi-user environment in the organization. For the development of new system we use NetBeans along with PHP, MySQL (rdbms package), Apache Server etc. for server side programming and JavaScript, AJAX, Cascading Style Sheets, HTML etc. for client side programming.
Operating Environment: The input data required are obtained from the documents, which contain all the details of the transactions. After validation and relevant processing, the data is to be stored in the database. The user selects the desired database table on after which the query is formulated. The query is generated by filtering the database based on the user defined conditions and constraints. The formulated query is executed on the database to obtain the required information.
Maintenance Environment: The proper maintenance of the new system is very important for its smooth working. The maintenance of the software is to be done by the system analyst and programmers in the organization. But for hardware maintenance engineer may be called from where hardware was purchased.
.
Feasibility study
A feasibility study is an evaluation of a proposal designed to determine the difficulty in carrying out a designated task. Generally, a feasibility study precedes technical development and project implementation.
A feasibility study is a test of a system proposal according to its workability impact on organization, ability to meet user needs and effective use of resources. The objective of a feasibility study is not to solve a problem but to acquire a sense of its scope. In other words, a feasibility study is an evaluation or analysis of the potential impact of a proposed project. During the study, the problem definition is crystallized and the aspects of the problem to be included in the system are determined. After the initial investigation of system, this helped to have in-depth study of existing system, understanding its strength and weaknesses & requirements for new proposed system.