
	Where results make sense

Topic: IEEE 829

Related Topics

ISEB

Institute of Electrical and Electronics Engineers

Grand Central Terminal

In the News (Sun 27 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Institute of Electrical and Electronics Engineers Summary
		The goal of the IEEE education programs is to ensure the growth of skill and knowledge among the technical profession and to foster individual commitment to continuing education among IEEE members, the engineering and scientific community, and the general public.
		IEEE also sponsors www.tryengineering.org, a website designed to help young people understand better what engineering means, and how an engineering career can be made part of their future.
		The IEEE requires that a proposed draft of the standard receive a response rate of 75% (i.e., at least 75% of potential ballots are returned) and that, of the responding ballots, at least 75% approve the proposed draft of the standard.
	www.bookrags.com /Institute_of_Electrical_and_Electronics_Engineers (4046 words)

	Britain.tv Wikipedia - IEEE
		The goal of the IEEE education programs is to ensure the growth of skill and knowledge among the technical profession and to foster individual commitment to continuing education among IEEE members, the engineering and scientific community, and the general public.
		IEEE also sponsors www.tryengineering.org, a website designed to help young people understand better what engineering means, and how an engineering career can be made part of their future.
		The IEEE requires that a proposed draft of the standard receive a response rate of 75% (i.e., at least 75% of potential ballots are returned) and that, of the responding ballots, at least 75% approve the proposed draft of the standard.
	www.britain.tv /wikipedia.php?title=IEEE (1789 words)

	Institute of Electrical and Electronics Engineers - Biocrawler (Site not responding. Last check: 2007-10-17)
		IEEE develops and participates in educational activities such as accreditation of electrical engineering programs in institutes of higher learning.
		IEEE produces 30 percent of the world's literature in the electrical and electronics engineering and computer science fields, and has developed more than 900 active industry standards.
		Most IEEE members are electrical engineers, computer engineers, and computer scientists, but the organization's wide scope of interests has attracted engineers in other disciplines (e.g., mechanical and civil,) as well as biologists, physicists, and mathematicians.
	www.biocrawler.com /encyclopedia/IEEE (651 words)

	What is IEEE? - A Word Definition From the Webopedia Computer Dictionary
		IEEE is an organization composed of engineers, scientists, and students.
		The IEEE is best known for developing standards for the computer and electronics industry.
		In particular, the IEEE 802 standards for local-area networks are widely followed.
	www.webopedia.com /quick_ref/IEEE.html (343 words)

	What is IEEE 829? - A Word Definition From the Webopedia Computer Dictionary
		The standard typically applies to any stage in the testing of developing software, and each stage in the software’s development typically is documented using the same application of the standard.
		The IEEE specifies eight stages in the documentation process, each stage producing its own separate document.
		IEEE 829 also is referred to as the 829 Standard for Software Test Documentation.
	www.webopedia.com /TERM/I/IEEE_829.html (366 words)

	IEEE 829 definition - isp.webopedia.com - The Glossary for Internet Service Providers
		The standard typically applies to any stage in the testing of developing software, and each stage in the software’s development typically is documented using the same application of the standard.
		The IEEE specifies eight stages in the documentation process, each stage producing its own separate document.
		IEEE 829 also is referred to as the 829 Standard for Software Test Documentation.
	isp.webopedia.com /TERM/I/IEEE_829.html (349 words)

	NRC: Regulatory Guide 1.170 - Software Test Documentation for Digital Computer Software Used in Safety Systems of ... (Site not responding. Last check: 2007-10-17)
		IEEE Std 829-1983 describes a method for software test documentation consistent with the previously cited regulatory requirements as they apply to safety system software.
		IEEE Std 829-1983 also provides for the inclusion of additional material in any of its defined documentation; therefore, any special testing information associated with unique circumstances may also be included.
		In section 4.2.2 of IEEE Std 829-1983, in describing the features to be tested by a given test design, it is noted that other features may be exercised but not identified.
	www.nrc.gov /reading-rm/doc-collections/reg-guides/power-reactors/active/01-170 (2767 words)

	Standards Chair Report - IEEE Software and Systems Engineering Standards Committee
		The IEEE standards process “speed of light” is 50 days (minimum critical path), but realistically, it takes several months to get the necessary reviews, action on comments, etc. This is why the ballot on 829 could not be expected to be done by the end of this year.
		The next phase would be for the IEEE and SC7 to converge on agreed definitions, editing the database contents and gradually updating the standards collections as each standard comes up for review/renewal.
		Other locations suggested were the IEEE Service Center in Piscataway where there are several conference meetings, an Embassy Suites where each person has a “meeting room” as part of their room, or a college/university.
	www.asq.org /software/standards/s2esc-2006-feb.html (3539 words)

	TABLE OF CONTENTS
		IEEE Std 828-1998, "IEEE Standard for Software Configuration Management Plans".
		IEEE Std 730-1998, "IEEE Standard for Software Quality Assurance Plans".
		There will be three formal presentations prepared by developer and evaluated by the committees at the end of each phase of development as described in project plan.
	www.cis.ksu.edu /~hzh8888/mse_project/SQA.htm (2629 words)

	Applying IEEE 829-1998 Standard for Software Test Documentation
		IEEE standard 829-1998 is a foundational standard that provides a framework for developing software test plans and reports for your own organization and projects.
		This is a practical workshop with many exercises to help you immediately apply the concepts in the IEEE standards.
		From this workshop, you will leave with a practical understanding of IEEE Standard 829-1998 for Software Test Documentation and how to tailor and apply it in your projects.
	www.riceconsulting.com /training/ieee_829.htm (605 words)

	Test Incident Report (Site not responding. Last check: 2007-10-17)
		The strategy is to compare defect existing data items with those suggested with IEEE Std 829, Bill Perry's A standard for Test Application Software, and Patricia Goglia's Client/Server Software Testing.
		IEEE Std 829 Standard for Software Test Documentation defines a Test Incident Report as having four sections.
		The incident details include what data was entered, the test procedure step which was executing, the GUI screen where the incident occurred, The sequence of keystrokes or mouse clicks that was entered, The error message which was displayed, attempts to repeat the incident, the actual results, and the expected results.
	www.csst-technologies.com /defectrp.htm (459 words)

	NAS Technical Reference Model (TRM) Documents - Standards Associated with a Specialty (Site not responding. Last check: 2007-10-17)
		The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.
		This document seeks to achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards.
		(1997) In addition a correlation between the content of software test documentation as defined in 829 and the content of such documentation as defined in IEEE 12207.1, will be added as an annex which will correlate the assumptions relating to content of the two documents and trace content between subject.
	www.faa.gov /asd/Standards/TRM-SpecCat.cfm?TRM=4&Category=22&Specialty=322 (2092 words)

	This email provides the following update information for the IEEE Std 829 Working group: (Site not responding. Last check: 2007-10-17)
		The original concept of many small groups working in parallel and merging their work when done is not optimal.
		As the working group has grown, it expanded to include divergent views that are not condusive to one common solution.
		The IEEE allows us to have "normative" sections – required for conformance to the standard, as well as "informative" sections – simply useful information.
	grouper.ieee.org /groups/829/Redirection_Lohr_12_02.htm (605 words)

	IEEE 829 Documentation and how it fits in with testing
		To provide a common set of standardised documents the IEEE developed the 829 Standard for Software Test Documentation for any type of software testing, including User Acceptance Testing.
		There are eight document types in the IEEE 829 standard, which can be used in three distinct phases of software testing:
		This is not an IEEE 829 document as all it values can be derived from the Test Incident Reports.
	www.coleyconsulting.co.uk /IEEE829.htm (1426 words)

	IEEE Standards Description: 829-1998
		IEEE Std 829-1998 IEEE Standard for Software Test Documentation -Description
		Annex C Guidelines for compliance with IEEE/EIA 12207.1-1997
		C.2.6 Life cycle data correlation between other data in IEEE/EIA 12207.1-1997 and IEEE Std 829-1998
	standards.ieee.org /reading/ieee/std_public/description/se/829-1998_desc.html (175 words)

	IEEE - Institute of Electrical and Electronics Engineers
		IEEE is the world's largest technical professional society, serving members in computing, electrical engineering and electronics.
		IEEE 81-1983 IEEE Guide for Measuring Earth Resistivity, Ground Impedance, and Earth Surface Potentials of a Ground System Part 1: Normal Measurements
		IEEE 519-1992 IEEE Recommended Practices and Requirements for Harmonic Control in Electrical Power Systems
	www.techstreet.com /info/ieee.tmpl (250 words)

	[No title]
		This paper explains the relevant section of the IEEE 829 standard in simpler terms and presents several different ways to break down the testing into groups of features.
		The IEEE Standard 829 for Software Testing Planning defines the following: A software feature is “a distinguishing characteristic of a software item (for example, performance, portability, or functionality).” A test plan “describes the scope and approach of intended testing activities.
		Using "feature" as a synonym for "functionality" often leads to an interpretation of the IEEE Standard 829 in which the testing is organized entirely around the functionality, which makes it difficult to plan adequately for the rest of the necessary testing.
	www.iinet.com /~iberle/articl1f.doc (4718 words)

	[No title] (Site not responding. Last check: 2007-10-17)
		IEEE software engineering standards comp.software-eng archive file "ieee" last changed 2 Oct 1991 This file contains information on the following subjects.
		Numbers in column 1 count distinct messages with the corresponding subject.
		Contact the IEEE Computer Society: IEEE Computer Society Headquarters or IEEE Computer Society 1730 Massachusetts Ave.
	hea-www.harvard.edu /MST/doc/softeng/ieee (323 words)

	Telecon Agenda IEEE Std 829 Working Group (Site not responding. Last check: 2007-10-17)
		IEEE Std 829 Working Group’s Core Planning Committee
		Excel can be used by any team that is working on changes, as it can be imported into Word.
		Coordination with other IEEE standards is deferred until a full draft is created.
	grouper.ieee.org /groups/829/Minutes_Core_Mtg_Lohr_2_13.htm (207 words)

	Templates - Design
		The purpose of the Test Plan is to document the approach to be used for testing the multimedia product at the different stages of its development.
		The purpose of the Test Procedure Specification is to specify the steps for executing a set of test cases or, more generally, the steps used to analyse a software item in order to evaluate a set of features.
		The Traceability Matrix enables the requirements to be traced to their final implementation, identifying at each stage the product components, modules and units and their contribution to each of the requirements.
	www.int.gu.edu.au /courses/3011int/impart/design/template.html (648 words)

	IIST - Journal (Site not responding. Last check: 2007-10-17)
		Application of the IEEE 829 Standard as a Basis for Structuring the Testing Process Adalberto Nobiato Crespo, Marcia Regina Martins Martinez, Mario Jino, Miguel de Teive e Argollo Junior
		Application of the IEEE 829 Standard as a Basis for Structuring the Testing Process
		The IEEE Std 829-1998 is a standard for software test documentation which can be very useful to help software houses to structure their software test projects.
	www.testinginstitute.com /preview/journal_2002_dec.php (1255 words)

	IEEE-SA Home Page
		Get connected to the IEEE 802® drafts service and much more.
		Enter here to learn how to get a direct avenue into the world-renowned IEEE standards development program, and get involved in the IEEE-SA community.
		Enter here to learn about the IEEE Standards Development Program—the process, rules, groups developing standards, how to get involved and get connected to myProject™.
	standards.ieee.org /index.html (267 words)

	IEEE Std. 2001-2002 References (Site not responding. Last check: 2007-10-17)
		This standard establishes the minimum required contents of a software configuration management plan and defines the specific activities to be addressed and their requirements for any portion of a software product's life cycle.
		This describes a set of basic test documents which are associated with the dynamic aspects of testing (that is, the execution of procedures and code).
		The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.
	acadweb.snhu.edu /Isaak_James/2001/wew/relatedmaterials/ibp2002references.htm (2858 words)

	CS 101 – Testing Plan
		The instructor is at your service to help you build you test design.
		Following the example and methodology described in IEEE Std.
		829 (or another widely accepted industry standard of your choice), you will construct a plan to test your software.
	www.cs.caltech.edu /~wrighton/cs101/project-testplan.htm (683 words)

	Implementing the IEEE Software Engineering Standards - $35.99 (Site not responding. Last check: 2007-10-17)
		Implementing the IEEE Software Engineering Standards is a practical and professional guide to implementing the IEEE Software Engineering standards in your software development process.
		One of the book's biggest benefits is that it helps software engineers reconcile some latest "best practices" such as rapid prototyping and use of CASE tools with use of the standards.
		IEEE Std 1074, Developing the Software Life Cycle Process.
	www.informit.com /title/0672318571 (182 words)

	Dr. Dobb's \| Test-Driven Development \| September 10, 2002
		The test-planning structure suggested by IEEE standard 829-1998 suggests conceptualizing test plans at different levels, either as individual documents or sections within a larger document.
		The diagram "A Sophisticated Standard" depicts the oft-followed test-planning structure suggested by IEEE standard 829-1998.
		While it's easy to see why many testers think that the IEEE standard requires voluminous documentation for its own sake, that approach provides no value, and we don't endorse it.
	www.ddj.com /184414911 (1570 words)

	[No title]
		This paper explains the relevant section of the IEEE 829 standard in simpler terms and presents several different ways to break down the testing into groups of features.
		The IEEE Standard 829 for Software Testing Planning defines the following: A software feature is “a distinguishing characteristic of a software item (for example, performance, portability, or functionality).” A test plan “describes the scope and approach of intended testing activities.
		Using "feature" as a synonym for "functionality" often leads to an interpretation of the IEEE Standard 829 in which the testing is organized entirely around the functionality, which makes it difficult to plan adequately for the rest of the necessary testing.
	www.kiberle.com /articl1f.doc (4718 words)

	IEEE Recommended Practice for Software Requirements Specications - Standards, of (ResearchIndex) (Site not responding. Last check: 2007-10-17)
		IEEE Recommended Practice for Software Requirements Specications - Standards, of (ResearchIndex)
		0.4: Applying the IEEE 1471-2000 Recommended Practice to a Software..
		IEEE Recommended Practice for Software Requirements Specifications", text = "Software Engineering Standards Commitee of the IEEE.
	citeseer.ist.psu.edu /429289.html (321 words)

	Some Pointers to Planning \| testingReflections.com
		Now I am not planning on re-analysing the IEEE 829 template test plan.
		I ask these sorts of questions all the time, at each phase of execution, at each phase of planning or creating charters for exploratory sessions and in retrospectives in the past tense to critically check the thinking applied and the testing done.
		Like James Bach, I am not a fan of the IEEE 829 document, just because it is a standard does not always make it appropriate or good.
	www.testingreflections.com /node/view/2603 (972 words)

	Wednesday Morning Conference Sessions (Site not responding. Last check: 2007-10-17)
		This presentation first describes the different types of documents used in the IEEE 829 standard and their relations to one another.
		We describe an experience where the IEEE 829 Standard for Software Test Documentation was used in the acceptance testing of a software system contracted by a Brazilian public company, whose business is to provide services of waste treatment and disposal and water supply and distribution.
		(The documents proposed in the IEEE 829 Standard have been adopted as a basis of the methodology).
	www.psqtconference.com /2002north/WednesdaySessions.htm (6463 words)

Try your search on: Qwika (all wikis)