Planguage
Planguage.[1][2][3][4][5][6] is a general-purpose, systems engineering, planning language; for any system, including software systems. Planguage scope is requirements, design, project management, and quality control. It is well documented in Competitive Engineering[1]
Planguage was developed by Tom Gilb in the 1960s and has now been practiced for decades. It is open source; anybody can use it for anything, in whole or part, freely. It is a large integrated ‘toolbox’, containing hundreds of distinct tools. Any set of these tools can be added to any other set of tools, or any framework. In particular, it is suitable as a set of ‘practices’ to evolve one’s own method within a stable Kernel. Planguage was designed to be interpreted by computers and the furthest advanced software service using Planguage is "Needs & Means".[7]
Characteristics[edit]
The central distinguishing characteristic of Planguage is it’s ability to directly integrate any quality (any ‘-ility’, not just reliability) statement quantitatively into the requirements, the designs, the project management, and the quality-control methods it contains. The second distinguishing characteristic of Planguage is that it allows and encourages very ‘rich’ planning specification of the background information for each individual requirement and design. This supports risk management, change management and dynamic prioritization. A third distinguishing characteristic is a systematic devotion to clarity and intelligibility of specification. Ambiguity, and lack of testable clarity is unacceptable. Even for ‘soft’ characteristics. Metrics, measurability and frequent numeric feedback about performance and costs is a primary notion.
Adoption[edit]
The two largest scale adoptions of Planguage were at HP (from 1988), and is at Intel[8] (over 17,000 engineers, over 10 years). A body of literature exists for this. Other noteworthy adoptions documentable, but often less than Corporate, sometime lasting only a few years include IBM[9] (Corporate Quality Policy, CMM 4), ICL (1982, top management, sw product development), Boeing (1990, aircraft engineering QC, Process Error Prevention method), McDonnell Douglas (aircraft engineering, 1998-90), Citigroup (2003-2006), Credit Suisse, JP Morgan, Union Bank of Switzerland, Philips Medical Systems, Ericsson (ERA, 1990s), Nokia & Symbian, Microsoft (Test).
References[edit]
- ↑ 1.0 1.1 Gilb, Tom (August 30, 2005). Competitive Engineering. Butterworth-Heinemann. p. 1. ISBN 9780750665070. Search this book on
- ↑ "Planguage Concept Glossary". Kai and Tom Gilb homepage. Retrieved 17 June 2018.
- ↑ "Why delivering value to customers makes your business successful and sustainable". Today Software Magazine. Retrieved 17 June 2018.
- ↑ Gilb, Tom (June 2004). "The Use of Planguage to Improve Requirement Specifications". INCOSE International Symposium. 14 (1): 1604–1614. doi:10.1002/j.2334-5837.2004.tb00598.x. Retrieved 17 June 2018.
- ↑ Wiegers, Karl. "Specifying Quality Requirements With Planguage". Modern Analyst. Modern Analyst. Retrieved 18 June 2018.
- ↑ Berzal, Fernando (2006). "Crosscutting Concerns in Software Architecture". IEEE Software. 23 (4): 101–102. Retrieved 18 June 2018.
- ↑ "Needs and Means". Needs & Means. Retrieved 18 June 2018.
- ↑ Terzakis, John. "Specifying Effective Non-Functional Requirements with Planguage" (PDF). Iaria. ICCGI Conference, Italy 2012. Retrieved 18 June 2018.
- ↑ Wiegers, Karl. "Success criteria breed success". IBM.com. IBM. Retrieved 19 June 2018.
This article "Planguage" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Planguage. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
