Active In SP
Joined: Mar 2010
22-04-2010, 04:05 PM
Inspection Tool.doc (Size: 91 KB / Downloads: 67)
ABOUT THE PROJECT
The project and implimentation deals with automation of some of the steps involved in inspection process. As mentioned earlier, inspection is carried out in all major phases of SDLC (software development life cycle) to ensure the reliability and credibility of software. In this era of software revolution, inspection plays a significant role. All the software development firms follow their own stringent policies to ensure software reliability. Hence, there arose a necessity for such a software to reduce the burden of handling software development in a more easy and user friendly way.
The software is used to meet the requirements of OSTPL (overtake software private limited) in software development. The software is an intranet application which can be extended to the Internet with a very few modifications. The employees are provided with a well-defined GUI to carry out their operations irrespective of their location along with a greater security and ease.
Thus, the software monitors the software development at various phases of SDLC. Each user deals with his own duties to accomplish the tedious task of software development in a simple manner, which is the main goal achieved through the software.
Various processes such as selection of members for inspection, conducting meetings, sending and receiving important informationâ„¢s, operations performed by various personnelâ„¢s are automated in the course of this project and implimentation. Other minute informationâ„¢s of great consideration to the project and implimentation leaders such as project and implimentation status, Inspection dates, employee details etc. can be retrieved easily through this intranet site. These are the main objectives attained through this project and implimentation.
Organizations wishing to optimize their inspection processes should consider this type of estimation tool. Inspections are still the most cost-effective way to detect defects in software
After the inspectors enter the inspection data into the tool, the output is the number of defects remaining in the inspected software (assuming all defects already detected will be fixed). The estimate adjusts for bad fixes. The tool also provides a recommendation as to whether the software module should be reinspected or not based on the desired quality levels of the organization
This software achieves the following:
Verifies that the software element(s) satisfies its specification & applicable standards.
Identifies deviation from standards and specifications.
Collects Software Engineering data regarding the Process towards improving the process itself.
Identifies the bugâ„¢s earliest in the software cycle.
It is a static technique (verification) compared to testing, which is a dynamic technique (validation) involving actual execution of the implemented code.
1.3 NECESSITY OF THE SYSTEM
Necessity of the system to do in automatically from previous system done such of completely manual technique for finding and correcting errors, An unprepared reviewer can sit quietly and say nothing, Lack of resources Previous bad experience, Big egos, Time.
Thus this Tool is used to overcome all the drawbacks that were used previously so that all activities and tasks are carried through automation. So complete manual task was isolated and provides easy way to carry out the tasks.
2.1 EXISTING SYSTEM
In the Existing system the process is done by only through manual. So the time consumption is high. The process such as defect bugs and in turn all the process involved in inspecting the product makes more complex. The conference of every task is difficult
to make the product robustness.
2.2 LIMITATIONS OF EXISTING SYSTEM
The limitations of the existing system are
High Human Resource.
No powerful Decision tool.
A completely manual technique for finding and correcting errors
Observation: An unprepared reviewer can sit quietly and say nothing.
Previous bad experience
2.3 PROPOSED SYSTEM
A powerful statistical engine to estimate the number of defects in a software module during software inspections. A combination of techniques and data collected from the software inspection process itself are used to estimate quality.
After the inspectors enter the inspection data into the tool, the output is the number of defects remaining in the inspected software (assuming all defects already detected will be fixed). The estimate adjusts for bad fixes. The tool also provides a recommendation as to whether the software module should be reinspected or not based on the desired quality levels of the organization.
Organizations wishing to optimize their inspection processes should consider this type of estimation tool. Inspections are still the most cost-effective way to detect defects in software.
2.4 ADVANTAGES OF PROPOSED SYSTEM
Advantages of the proposed system are
High Response Time.
Group Conference [Chatting].
Automation Process between Author, Moderator, Inspector & Team Members.
Prevent introduction of defects - cheaper than repair.
Better understanding of software quality control.
Reduce effort expended on defect repair.
Reduce costs due to defects.
Improved product quality.
PROCESSOR : 32 BIT, Pentium â€œ IV
RAM : 256 MB
HARD DISK : 40 GB
MONITOR : SVGA Monitor (800 * 600 RESOLUTIONS)
CLOCK SPEED : 266 MHz
KEYBOARD : 101 KEYS
MOUSE : Logitech
FLOPPYDRIVE : 1.44 MB
3.2 SOFTWARE SPECIFICATION
OPERATING SYSTEM : Windows 2000/XP.
FRONT END : XML, HTML, DHTML
MIDDLEWARE : J2EE
BACK END : Oracle 8i
SERVER : Web Logic 6.1
LEVEL 0 :
Use Search at http://topicideas.net/search.php wisely To Get Information About Project Topic and Seminar ideas with report/source code along pdf and ppt presenaion
Active In SP
Joined: Aug 2010
06-08-2010, 03:18 PM