
	Where results make sense

Topic: IEEE 12207

Related Topics

How to Irritate People

Institute of Electrical and Electronics Engineers

Monty Python

March 21

In the News (Wed 30 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	ASQ : Software
		IEEE 1044 (on anomalies, i.e., defects) - David Card is the Working Group Chair for this effort and he will be turning the standard into a Defect Causal Analysis process standard, taking the existing defect taxonomy and making it an appendix.
		IEEE 730 (on software quality assurance) - The standard, when its revision begins later this year, may need “lightening up” to match IEEE 12207 as 12207 is “lite” on the SQA since it builds QA into processes through PDCA improvement expectations.
		IEEE 1648 (on agile methods) - It was suggested that this work, needs to address those aspects of 12207 and 15288 not addressed by agile methods.
	www.asq.org /software/standards/s2esc-2005-feb.html (1020 words)

	Using IEEE Standards to Support America?s Army Gaming Development
		The benefit of pairing the CMMI and IEEE SWE standards is that CMMI served as the motivator, and IEEE standards provided the sound foundation on which to build our software engineering processes and practices.
		The IEEE 12207 standards—adopted as IEEE CS SS&E standards—provide a wealth of information to support software and systems life-cycle processes that tie together the organizational-level, supporting, and primary processes.
		Using the IEEE SS&E standards was ideal for this approach.
	www.computer.org /portal/site/computer/menuitem.5d61c1d591162e4b0ef1bd108bcd45f3/index.jsp?&pName=computer_level1_article&TheCat=1090&path=computer/homepage/1106&file=standards.xml&xsl=article.xsl& (1269 words)

	Ieee 12207
		ieee 1394, ieee org to ieee standard is required for ieee 488.
		ieee 1394 analysers by ieee 1394b, texas instrument ohci compliant ieee 1394 host controller and related to ieee 802.16, ieee 1394 test equipment into ieee 1394 networking device, ieee wireless, dv ieee 1394.
		1394 cable dv ieee is required for ieee 1394 exerciser, ieee 1394 to usb and topics related to ieee 1394 bus analysers.
	www.hostmerit.com /ffalinks/ieee12207.html (354 words)

	IEEE PINS
		This is an IEEE adoption of ISO/IEC 20000-1.
		IEEE 99 provides a format for developers of standards to establish test methods for thermal evaluation of insulation systems by manufacturers of insulating materials and manufacturers of equipment to result in thermal classifications derived in a consistent and verifiable manner.
		IEEE Std 1003.1-200x defines a standard operating system interface and environment, including a command interpreter (or "shell"), and common utility programs to support applications portability at the source code level.
	www.incits.org /incits_ieee/2006/ieee_2006ss.htm (8100 words)

	U.S. Software Lifecycle Process Standards - July 97
		IEEE SESC has an active program to achieve and maintain "harmonization" among the various software lifecycle process standards that are available.
		IEEE and EIA, under a cooperative working agreement to produce high-quality software standards based on the best commercial practices, have a single joint working group for the development of J-STD-016 and IEEE/EIA 12207.
		IEEE is the administrator of the TAG, and an IEEE representative currently serves as the chair of the TAG.
	www.stsc.hill.af.mil /crosstalk/1997/07/lifecycle.asp (2270 words)

	Ieee-12207-online - holidayinsalina.com (Site not responding. Last check: )
		Ieee 12207 online unless there is a compelling business case to use them.
		Ieee 12207 what is the impact of applying new tools and technologies.
		Ieee 12207 nbk will suffice (in 85 cases nbk same or better than j48).
	www.holidayinsalina.com /Ieee-12207-online (84 words)

	Abelia Corporation - Introduction to IEEE/EIA 12207
		And, in their ISO packaging, the IEEE/EIA 12207 engineering requirements are the world's definitive description of the software life cycle.
		IEEE/EIA 12207 is compatible with the new, agile software development techniques and also with traditional object-oriented and structured methods.
		This course is a one-day explanation of the key elements of IEEE/EIA 12207.
	www.abelia.com /12207_Intro.htm (240 words)

	NAS Technical Reference Model (TRM) Documents - Standards Associated with a Specialty (Site not responding. Last check: )
		IEEE 1044 provides a uniform approach to the classification of anomalies found in software and its documentation is provided.
		The primary purpose of the document would be to facilitate communication between acquirer and supplier (who may be either internal or external to the organization), oparticularly regarding questions on the scope of the contract and questions regarding who bears the expense and gains the benefits of reuse efforts.
		This was developed to achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards.
	www.faa.gov /asd/standards/TRM-SpecCat.cfm?TRM=4&Category=1&Specialty=143 (2156 words)

	San Diego SSQ: January 2000 Meeting (Site not responding. Last check: )
		IEEE/EIA 12207, published by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Association (EIA), has been adopted by DOD to replace MIL-STD-498.
		12207 is also cited by the SPAWAR Systems Center, San Diego as the basis for their future software engineering activities.
		12207 addresses not only the development of software systems, but also the acquisition, supply, maintenance, and operation of them.
	www.ssq.org /chapter/sd/past/sdjan00.htm (249 words)

	ISO 12207 and Related Software Life-Cycle Standards
		Since it is a relatively high-level document, 12207 does not specify the details of how to perform the activities and tasks comprising the processes.
		The ISO is currently developing such guides and assessment procedures to complement 12207; the IEEE Software Engineering Standards Committee is also planning to reorganize its collection of standards to complement 12207.
		Second, the IEEE and the EIA are collaborating on another joint standard--the "U.S. Industrial Implementation" of 12207--which will be structured around the process framework of 12207 but add the "technical goodness" of J-016 to the development process.
	www.acm.org /tsc/lifecycle.html (811 words)

	sw mtg 01
		SVVP as defined in IEEE 1012 includes many references to the safety requirements that may not be applicable to IEEE P1588.
		IEEE 1483 starts with a safety assurance plan and addresses the verification and validation efforts.
		Finally, Annex A of IEEE Std 730-1998 explores the correlation between the IEEE Std 730-1998 and IEEE/EIA 12207.0-1996.
	www.tsd.org /rsc/wg12/wg12mom09final.htm (1093 words)

	Connector Specifier - IEEE Okays Supplemental Standard for Reliability Prediction in Electronics
		The new standard, IEEE 1588 (TM), "Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems," supports system-wide synchronization at the sub-microsecond range for heterogeneous systems having clocks of various precisions, resolutions and stabilities.
		The new standards project, IEEE P1621 (TM), "Standard for User Interface Elements in Power Control of Electronic Devices Employed in Office/Consumer Environments," will make power controls in all electronic devices similar so home, office and other users find them easier to use and are more likely to take advantage of energy-saving power management features.
		The IEEE Standards Association, a globally recognized standards-setting body, develops consensus standards through an open process that brings diverse parts of an industry together.
	cs.pennnet.com /Articles/Article_Display.cfm?Article_ID=158278&CFID=292453&CFTOKEN=87920798 (452 words)

	Abelia Corp. - IEEE/EIA 12207 Complete
		IEEE/EIA 12207 is the industry implementation of ISO/IEC 12207, "Software Life Cycle Processes." It was adopted for use by the United States Department of Defense on May 27, 1998.
		A major difference between IEEE/EIA 12207 and ISO/IEC 12207 is that the ISO standard only mentions types of data items to develop and record during the software life cycle.
		They will be able to incorporate appropriate requirements from this standard into a software development plan for a project and into their organization's defined software process.
	www.mariadata.se /12207_2d.htm (635 words)

	IEEE Software Engineering Standards Zone - Overview
		Over the past twenty years since the first IEEE software engineering standards were published, the practice of software engineering has grown from an individual craft to a highly organized team effort.
		There has been the growing emphasis on the adoption of organization-level processes that are intended to be applied repeatedly to all software engineering projects within an organization.
		And all IEEE software engineering standards dealing with software processes and the data that they produce have been harmonized with the umbrella standard.
	standards.ieee.org /software/overview.html (316 words)

	MIL-STD-498
		None the less, there are still people (eg, prime contractors for UK MoD projects) who stick with 498, for various reasons:
		There's not a very great deal of difference between the standards anyway (I can't vouch for that one!)
		A 498 project would fit fairly well under the IEEE standard, but not vice versa, since the IEEE one is much less prescriptive).
	www.pogner.demon.co.uk /mil_498.html (191 words)

	Product Detail
		IEEE/EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Alliance (EIA) as formulated by a joint project of the two organizations.
		IEEE/EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Association (EIA) as formulated by a joint project of the two organizations.
		This IEEE Standards product is part of the family on Software Engineering.
	shop.ieee.org /ieeestore/Product.aspx?product_no=SH94603 (330 words)

	Presentation Summary (Site not responding. Last check: )
		This presentation will clarify the management software life-cycle process in IEEE/EIA 12207 by comparing it to project management, as project management is defined by the Project Management Institute (PMI).
		This presentation will explain the IEEE/EIA 12207 management process activities - initiation, planning, execution and control, review and evaluation, and closure - by relating them to the process groups in the Project Management Body of Knowledge (PMBOK) - initiating, planning, executing, controlling, and closing.
		Later, when interpreting the management process requirements in IEEE/EIA 12207, those who see this presentation can go back easily to PMBOK for further guidance, on the job.
	www.sstc-online.org /Proceedings/2002/pres731.cfm (140 words)

	Tantara: Hotlist -- ISO 12207 (Site not responding. Last check: )
		Read this pdf-report if you are interested in a quick summary of the ISO 12207's recommended set of processes and their basic relationships.
		IEEE has released ISO 12207 as a 3 part document set.
		This is the sub-committee that manages the ISO 12207 model's evolution.
	www.tantara.ab.ca /iso12207.htm (251 words)

	System Technology Institute - Software Systems Engineering, Management and Assurance Training
		IEEE/EIA 12207 is the United States implementation of ISO/IEC 12207, "Software Life Cycle Processes." IEEE/EIA 12207 is packaged in three volumes: IEEE/EIA 12207.0-1996 (the base standard), IEEE/EIA 12207.1-1997 (guide to life cycle data), and IEEE/EIA 12207.2-1997 (guide to process implementation).
		ISO/IEC 12207 was the first standard on software to be issued for international use.
		Covers those rules that were employed to design the standard itself and discusses in detail the concepts that are necessary to understand the standard and its place as a software aid in the big picture of systems and life cycles.
	www.stitraining.com /curriculum.php?cid=01t30000000Xdy5AAC (749 words)

	[No title]
		IEEE Std1471—2000, IEEE Recommended Practice for Architectural Description, Institute of Electrical and Electronics Engineers, Inc., United States.
		IEEE Std1058—1998, IEEE Standard for Software Project Management Plans, Institute of Electrical and Electronics Engineers, Inc., United States.
		IEEE Std1220—1998, IEEE Draft Standard for Application and Management of the Systems Engineering Process, Institute of Electrical and Electronics Engineers, Inc., United States.
	www.aitp.org /isedj/isecon/2002/243d/ISECON.2002.Steenkamp.txt (4535 words)

	get here: ieee 12207 pdf (Site not responding. Last check: )
		The Get IEEE 802® program makes IEEE 802® standards available at no charge in PDF format thanks to the sponsors listed to the right.
		IEEE PDF eXpress is an IEEE-sponsored online tool, freely available to assist conference organizers...
		IEEE 1003; IEEE 1076; IEEE 1164; IEEE 1219; IEEE 12207; IEEE 1284; IEEE 1471; I cont.
	halorecovery.co.uk /ieee_12207_pdf.html (250 words)

	بخش هفتم - معرفي استاندارد IEEE/EIA 12207 (Site not responding. Last check: )
		اين استاندارد برگرفته از استاندارد بين المللي ISO / IEC 12207 مي‌‌باشد و مي‌‌تواند براي سيستمهاي تجاري و نظامي هم براي مشتريان داخلي و هم براي مشتريان خارجي استفاده شود.
		همانطور كه در قسمتهاي قبل اشاره گرديدISO/ IEC 12207 به عنوان يك استاندارد بين المللي در سال 1995 ارائه گرديد.
		به منظورحفظ سازگاري استانداردIEEE/EIA 12207 در آمريكا با نسخه ISO آن، بجاي تمركز برروي سطوح پروژه‌‌هاي مجزا ،سطوح سازماني مدنظر قرار گرفت بدينصورت كه پيشنهاد شد سازمانها، مجموعه پروسه‌‌ها و رويه‌‌هاي خود را با اصول IEEE/EIA 12207 تطبيق دهند.
	www.irandoc.ac.ir /com/Reports/Documentation_std/report_7.htm (641 words)

	IEEE Computer Society::Software Engineering, Volume 1, The Development Process, 3rd Edition (Site not responding. Last check: )
		Both volumes consist of original papers written expressly for the two volumes, as well as authoritative papers from the IEEE archival journals, along with papers from other highly regarded sources.
		Software Engineering is further anchored in the concepts of IEEE/EIA 12207.0-1997 Standard for Information Technology—Software Life Cycle Processes, which provides a framework for all primary and supporting processes, activities, and tasks associated with software development.
		By emphasizing the IEEE software engineering standards, the SWEBOK, and the contributions of key authors, the two volumes provide a comprehensive orientation to the landscape of software engineering as practiced today.
	www.wiley.com /WileyCDA/WileyTitle/productCd-0471684171,miniSiteCd-IEEE_CS.html (445 words)

	[No title] (Site not responding. Last check: )
		The criticality of an anomaly is assessed in accordance with the standards described in the template for the NARA IV&V Anomaly Report, found in Appendix B of this document.
		At this level, a function or system capability that fails may have catastrophic consequences on the NARA mission, however there is an infrequent likelihood of such a failure.
		Using statistical sampling and analysis techniques, verify all operations, including system administration and maintenance, are performed in accordance with the respective documentation to insure the completeness, correctness, and consistency of the user documentation.
	www.archives.gov /era/about/era-ivvp.doc (10733 words)

	INFORMATION TECHNOLOGY STANDARDS GUIDANCE (Site not responding. Last check: )
		IEEE 1003.2/ISO/IEC 9945-2 lacks most of the programming language and compiler facilities present in XPG4, SVID, and OSF/1, such as the link editor ("ld"), macro definition expander ("m4"), the assembler ("as"), the C language program checker ("lint"), and the C program beautifier ("cb").
		The IEEE 1003.2 standard method for calling the compiler to compile standard C programs is "c89" compared to the "cc" command traditionally used to call the compiler.
		Although the IEEE 1387.2 standard is based on Hewlett-Packard's "swinstall" and "swpackage" systems, the standard has modified the specifications so that they are not exactly like the HP systems.
	sw-eng.falls-church.va.us /itsg/P02V31.htm (6915 words)

	Institute of Electrical and Electronics Engineers - Wikipedia, the free encyclopedia
		The IEEE consists of 39 societies, organized around specialized technical fields, with more than 300 local organizations that hold regular meetings.
		IEEE offers educational opportunities such as Expert Now IEEE, the Education Partners Program, Standards in Education and Continuing Education Units (CEUs).
		The major interests of the AIEE were wire communications (telegraph and telephony) and light and power systems.
	en.wikipedia.org /wiki/IEEE (1769 words)

	About IEEE
		For what it's worth, I'm a member of IEEE's computer society, and I agree with Richard that the term "engineering" is not exactly a good fit because of the reasons he submits.
		There are some analogues (such as books on algorithms telling you their relative performance in different situations so you can choose the right one for the job, etc), just that their emphasis is on the project management side rather than the product design side, or at least that's the impression I've gotten.
		I think the IEEE's goals here are worthwhile, but represent one of many views of software development, and they are really good to know about as another tool in your arsenal.
	www.codecomments.com /message496493.html (1436 words)

	CHAPTER 10 (Site not responding. Last check: )
		IEEE/EIA 12207: This is the strategic standard that addresses the three primary objectives described in the previous paragraph.
		The object is to have an organization develop its own set of processes and procedures compliant with the requirements of US 12207, which would be applied across the entire organization.
		ISO/IEC 12207 is going through an amendment and this document is scheduled to be re-published in CY 2002.
	guidebook.dcma.mil /55/Guidebook/GuidebookChapter_10.htm (3132 words)

Try your search on: Qwika (all wikis)