
	Where results make sense

Topic: Fagan inspection

Related Topics

Michael Fagan

Software inspection

Software engineering

Code review

Software development process

Flawfinder

The Cathedral and the Bazaar

Agile software development

Peer review

List of mountains

In the News (Mon 28 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Why Code Inspections Fail
		If defects were found the inspection enters the Rework Phase where the Author fixes the problems, and later there will be a Verification Phase to make sure the fixes were appropriate and didn't open new defects.
		In our survey of published case studies and experiments in the past 20 years, we found that 95% of them tried inspections only in small pilot groups, and that in no case were they able to apply the technique to all their software development projects.
		Fagan inspections were designed in the days when business logic was written in assembly language and "computer science" wasn't a major and dinosaurs roamed the earth.
	smartbearsoftware.com /white-paper.php?content=docs/articles/Why-Code-Inspections-Fail.html (1505 words)

	A Business Case for Software Process Improvement Revised - Inspections (Site not responding. Last check: 2007-10-10)
		Inspections are formal processes that are intended to find defects in software and other products at or near the point of insertion of the defect, thereby using fewer resources for rework.
		Inspections are based on the inspection process developed by Fagan (1986)and are typically referred to as Fagan inspections.
		Fagan estimates that the cost of finding and fixing defects early is 10 to 100 times less than it would be during testing and maintenance.
	www.dacs.dtic.mil /techs/roispi2/inspections.shtml (1229 words)

	Lecture 8
		These inspections were applied throughout the development process, and were concerned with all aspects of the quality of the documents being inspected, not just whether they appeared to have errors in the logic or functionality that was being described.
		Fagan developed a number of rules for the procedures to be used in carrying out these inspections, and these are listed in section 12.1: they are as follows.
		However, it is the moderator's responsibility to ensure that there is a subsequent inspection of the reworked documents, so that they will not be signed off as fit for use in later stages of the development until a moderator is satisfied that they have passed an inspection.
	www.dcs.shef.ac.uk /~wmlh/inspect.html (799 words)

	[No title]
		The manner in which inspection data is categorized and made suitable for process analysis is an important factor in attaining the improvements.
		Fagan Inspections and other existing methods have been empirically shown to benefit the software development process, mainly by lowering the number of defects in software early in the development process.
		Nine independent inspection teams were given this URD with instructions to locate as many faults as possible using the N-fold requirements inspection technique developed by the authors.
	hea-www.harvard.edu /MST/doc/softeng/inspect (8275 words)

	About Michael Fagan
		Michael Fagan: Initially I managed IBM hardware products, but after we developed processes to uncover and resolve hardware design defects I was invited to join the IBM software development team, where products were more often late than on schedule.
		Fagan Associates' clients typically invest many thousands of dollars in the training curriculum, but then they experience immediate improved productivity, reduced cycle times, budget savings, and enhanced product margins that are often many times greater than what they've spent on the training.
		They find that when inspections are introduced into the requirements phase and applied to design and coding, the ROI breaks even after ten or twenty percent of the testing is complete.
	www.mfagan.com /MF_invue1.html (1517 words)

	Return on Investment (ROI) from Software Process Improvement (SPI) (Site not responding. Last check: 2007-10-10)
		Inspections are formal processes that are intended to find defects in software and otherproducts nearer the point of injection rather than wait until the test phase to find the defects, using less resources for rework.
		Inspections are based on the inspection process developed by Fagan (1986) and are typically referred to as Fagan inspections.
		In this process, as in inspections, errors are detected early in the life cycle closer to the point of insertion of the error.
	www.dacs.dtic.mil /topics/roi.shtml (4764 words)

	Embedded.com - Code Inspection Book
		Lightweight, because the traditional code inspection advocated by Michael Fagan and Thomas Gilb doesn't fit the needs of some teams, but the benefits of inspections are so profound that even the smallest outfits must take advantage of the technique.
		And sometimes it's hard to match the process of the Fagan approach to modern agile methods.
		The Cisco study showed a tremendous variability in inspection rates for a lot of reasons.
	www.embedded.com /showArticle.jhtml?articleID=193001411 (1185 words)

	Improving Quality Through Software Inspections
		Software inspections and their cousins, reviews and walkthroughs, are proven techniques for reducing the number of defects in a program before it goes out the door.
		Inspections shorten delivery time by reducing the time spent in the integration and system test/debug phases, since a cleaner product is passed into those late-stage quality filters.
		Data from inspection summary reports can be used to identify the most common or most costly kinds of bugs, determine their root causes, and change how work is performed so as to prevent those types of errors.
	www.processimpact.com /articles/inspects.html (5768 words)

	Formal Inspections
		Fagan 1976], [Fagan 1986], [IEEE 1997], [Gilb and Graham 1993], [Laitenberger 2002], and [NASA 1993]) characterize formal inspections.
		Fagan [1976] states that the conduct of trained moderators and the attitude of management are key to the acceptance of inspections by engineers.
		Inspections can be performed on analysis results (or artifacts of the analysis process) in preparation for technical decision making regarding COTS selection or implementation.
	www.goldpractices.com /practices/fi/index.php (4044 words)

	eliop_paper
		Regarding code inspections the average effort per inspection unit is 0,014 per LOC or, in an equivalent way 14 hours are devoted to complete the whole inspection process of one KLOC (including the planning, overview, preparation, rework and review phases).
		Sometimes, when the inspection team is composed of only two members and one of them adopts all the roles with the exception of "author", the number of inspected units per hour of inspection meeting significantly increases; that’s to say, an inspection team of two members seems to inspect considerably faster than a bigger team.
		During the first inspections, the adoption of the role of the moderator by the technical team head facilitates, due to his high degree of expertise, the cross-training of the inspectors, even more regarding key aspects of complex projects.
	www.iscn.at /select_newspaper/testing/eliop.html (5006 words)

	Software Inspecionts and Defect Prevention
		Formal inspections are distinguished from other types of inspection in that they follow a well-defined, tried, and proven process of evaluating the actual product or partial product with the intent of finding defects.
		Inspection Meeting All participants in the inspection team attend this meeting, the moderator collects statistics from each inspector, then the inspectors log their defects and pose their questions to the author.
		An inspection metric is a collection and evaluation of the data gathered from the inspection process which can be used to analyze the process and further provide feedback and evaluation of inspection process.
	pages.cpsc.ucalgary.ca /~davisk/621/WebDoc.html (3180 words)

	Learning software processes
		In this study, a full Fagan inspection used between 4 and 6 staff, plus the author of the artifact being inspected.
		The baseline inspection at this company was essentially a poorly performed Fagan inspection, The distinction between a proper Fagan inspection and the baseline is that staff would receive new training, checklists and support in order to significantly improve the effectiveness of the inspections.
		Walk through inspections were conducted by one by the author of the artifact being inspected in a relatively informal atmosphere.
	www.cs.pdx.edu /~timm/dm/kfarm1.html (1875 words)

	What’s So Great About Inspections?!?
		The Fagan inspection, as you may know, is a process-focused inspection.
		Bruce C. Hungerford reported at the 1997 Association for Information Systems conference that inspection meetings tend to slow project progress by an average of two weeks, and that the meetings found no more errors than the most competent participant did (although Hungerford admitted he was concerned with the accuracy of that particular finding).
		Many say that one inspection can only cover about 100 lines of code (again, note that most of what I am saying is about code inspection) before the participants are mentally exhausted.
	www.stickyminds.com /se/S2587.asp (1066 words)

	San Diego SSQ: April 2000 Meeting
		Michael Fagan will present The Fagan Defect-Free Process, which combines using the Fagan Inspection process (which is often not fully understood or exploited) with other proven methods to give you the biggest and most immediate benefit.
		Using the inspection method, but not getting the advertised results, you may be missing some of the key components required for a successful implementation.
		From 1983 to 1985, Michael Fagan was a Visiting Professor in the Department of Computer Science and was a member of the Graduate Council of the University of Maryland.
	www.ssq.org /chapter/sd/past/sdapr00.htm (625 words)

	Virtually Defect-Free Software in Less Time
		Истинный успех для "Fagan Defect-Free Process" и "Fagan Inspections" придет в том случае, если преимущества этих методологий заметят не только в индустрии программного обеспечения, но и в других областях, в которых создаются столь же разнообразные продукты и услуги.
		За создание методологии "Проверки Фэгана" (Fagan Inspection), а также за продвижение этой методологии среди лабораторий IBM по всему миру и в индустрии в целом Майкл был удостоен самой высокой награды компании IBM за индивидуальные корпоративные достижения (Corporate Achievement Award).
		Ассоциация Майкла Фэгана (Michael Fagan Associates) была создана в 1989 году, цель которой - обучать успешному применению данной методологии.
	secr.ru /2006/program/workshops/mfworkshopru (256 words)

	Why Isn't Inspection Used (Site not responding. Last check: 2007-10-10)
		Inspections are perceived as improving quality at the expense of other goals more important to the software developer.
		The questions concerning inspections were preceded by a precise definition of what was meant by a formal inspection.
		Inspections seem relatively poor at finding those faults; it's hard to realize you even need to consider that code way over there (especially when you're trying to keep change inspections cheap).
	www2.ics.hawaii.edu /~johnson/FTR/Bib/Brykczynski94a.html (4774 words)

	State-of-the-art: Software Inspections after 25 Years (Aybüke Aurum, Håkan Petersson, Claes Wohlin) - Electronic ...
		Software inspections, which were originally developed by Michael Fagan in 1976, are an important means to verify and achieve sufficient quality in many software projects today.
		This is a review paper focusing on the software inspection process in the light of Fagan's inspection method and it summarizes and reviews other types of software inspection processes that have emerged in the last 25 years.
		This paper also addresses important issues related to the inspection process and examines experimental studies and their findings that are of interest with the purpose of identifying future avenues of research in software inspection.
	www.bth.se /fou/forskinfo.nsf/alfs/b79930bf94ed0164c1256c2a0045c9b3 (207 words)

	[No title]
		Explain how a one-person inspection works and when it may be beneficial compared to a group inspection.
		Inspections are advantageous because they: encourage programmers to work carefully to avoid being embarrassed by sloppy mistakes; encourage programmers to produce quality work out of pride; train programmers to avoid programming errors.
		Interestingly, for this issue the answer is crisp and clear: Inspection is both more effective (in terms of the number of errors it finds) and cost-effective (in terms of the cost of finding those errors).
	cs.uwp.edu /Classes/Cs476/notes/Inspect.doc (828 words)

	Software Inspections and Peer Reviews
		The course consists of 9 modules with nearly 6 hours of audio and several practice activities that provide a comprehensive introduction to software peer reviews in general and the Fagan inspection technique in particular.
		The inspection process is introduced as a type of formal review.
		We discuss the participants in an inspection and their roles, and we explore whether managers and observers belong in inspections.
	www.processimpact.com /SIPR (1037 words)

	CSC340 projects FAQ
		Different size teams represent different kinds of challenges in coordination, sharing of workload, etc. It is possible that the number of students on the course will not divide exactly by 3, in which case we might end up with one team of a different size, but don't count on it.
		Although Fagan inspections were originally developed for inspecting code, the same basic principles apply to inspecting other things.
		The main emphasis in Fagan inspections is on studying the kinds of defects discovered, and using this to learn something about how to improve the processes of writing specifications, and the processes of inspecting them.
	www.cs.toronto.edu /~sme/CSC340F/2004/340-FAQ.html (1499 words)

	QAI India Ltd. - Training (Site not responding. Last check: 2007-10-10)
		Fagan's Inspection Method is a six-step highly structured means of performing reviews on intermediate and final software products (specifications, code, documentation, etc).
		Developed by Michael Fagan, when at IBM, this formal technique is considered amongst the most powerful and effective quality control tool used.
		This workshop will provide participants with a clear understanding of the Inspection technique, differentiating it from other review techniques.
	www.qaiindia.com /Training/int24.htm (224 words)

	San Diego SSQ: May 2000 Meeting
		The company standard "Inspection Database" (designed by Vicki Moore, Engineering Specialist at BAE Systems) will convey a user interface for data entry/collection of inspection data and quick retrieval for generating reports.
		The primary purpose of the inspection process (applicable to both hardware and software development life cycles) is to efficiently discover and remove defects from engineering work products early in the development life cycle and to eliminate systemic defects from the associated development phases.
		He has met occasionally with Michael Fagan regarding the Fagan Inspection process implementation and data analysis at BAE Systems for productivity improvement through defect-free development.
	www.ssq.org /chapter/sd/past/sdmay00.htm (571 words)

	Code Reviews - An Abridged Guide to Reviewing Code (Site not responding. Last check: 2007-10-10)
		In 1972 Michael Fagan of IBM used an industrual hardware inspection method on a software project he was managing.
		These inspection rules, which are now known as Fagan's Inspection Method, had to contribute to net profit to survive.
		This does not attempt to replace formal training (in Fagan's Inspection Method, or any other) in conducting code reviews.
	www.riverdog.co.uk /Articles/Technology/fog0000000013.html (1466 words)

	InApp \| Software Outsourcing \| Software Development \| Product Outsourcing \| Java \| .NET \| Multimedia
		The purpose of Peer Review (formal Fagan Inspection mechanism) is to remove defects from the artifacts early and efficiently.
		Peer Reviews involve a methodical examination of software work products by the author's peers to identify defects and areas where changes are needed.
		The purpose of the training program is to identify, plan and conduct timely training for all InAppians and not meant for external audiences such as customers and end-users.
	www.inapp.com /supp_proce.php (387 words)

	[No title]
		Functional correctness.¡TTª ® ¡ ó¾Ú¨Phased inspectionsª ¨Defects: indigenous seeded¡ ª ó{C¨Summaryª ¨ÎFagan inspection are a formal and rigorous method of checking quality.
		Inspections are a basic tool in software quality assurance.
		Some aspects of Fagan inspections are outdated and their should be updated.¡ÏÏª Ï ó —¨Further readingsª ª ó •¨Quality assessmentª ¨1.
	www.cs.put.poznan.pl /jnawrocki/mse/psp/Pspd.pps (694 words)

	Software Dioxide: Peer Reviews (Site not responding. Last check: 2007-10-10)
		Developed by Michael Fagan, when at IBM, Fagan's inspection method is a six-step highly structured means of performing reviews on intermediate and final software products (specifications, code, documentation, etc).
		Peer reviews is one of KPA's (Key Process Areas) of level 3 of the Software Capability Maturity Model® of the Software Engineering Institute.
		It will impart skills for participating in an inspection as a leader, recorder and author.
	www.softwaredioxide.com /Channels/ConView.asp?id=7371 (99 words)

	Michael Fagan Associates
		Michael Fagan created the Fagan Defect-Free Process (of which Fagan Inspections are a key part) to address these requirements.
		Our clients have reported significant cycle time reductions while simultaneously improving product quality, reducing costs and improving productivity.
		Or click on the headings at left to discover how the Fagan Defect-Free Process can help you foster self-perpetuating process improvements throughout your development organization that will prevent future product defects before they happen.
	www.mfagan.com (100 words)

Try your search on: Qwika (all wikis)