Is This a Revolutionary Idea, or Not?
The article discusses the construction of a computer software system from its requirements by Professor R. Geoff Dromey, of Griffith University's Software Quality Institute, in Brisbane, Queensland. Each requirement, should be translated into its corresponding "behavior tree." A behavior tree is mad...
| Publicado en: | Communications of the ACM Vol. 47; no. 11; pp. 23 - 26 |
|---|---|
| Autor principal: | |
| Formato: | Artículo |
| Publicado: |
Association for Computing Machinery
Nov2004
|
| Materias: | |
| Acceso en línea: | Ver este registro en EBSCOhost |
| fields | @attributes: recordID: 1 pdfLink: plink: https://search.ebscohost.com/login.aspx?direct=true&db=hlh&AN=14957848&site=ehost-live header: @attributes: shortDbName: hlh uiTerm: 14957848 longDbName: Humanities International Complete uiTag: AN controlInfo: bkinfo: jinfo: jid: 00010782 ACM jtl: Communications of the ACM issn: 00010782 maglogo: N pubinfo: dt: Nov2004 vid: 47 iid: 11 pid: 68 pub: Association for Computing Machinery artinfo: ui: 14957848 10.1145/1029496.1029514 ppf: 23 ppct: 3 formats: tig: atl: Is This a Revolutionary Idea, or Not? aug: au: Glass, Robert L. su: Computer software development Dromey, R. Geoff Software engineering Brisbane (Qld.) Queensland sug: subj: Brisbane (Qld.) Queensland Computer software development Dromey, R. Geoff Software engineering ab: The article discusses the construction of a computer software system from its requirements by Professor R. Geoff Dromey, of Griffith University's Software Quality Institute, in Brisbane, Queensland. Each requirement, should be translated into its corresponding "behavior tree." A behavior tree is made up of software pieces, states, events and decisions/constraints data that the components exchange, and the causal, logical, and temporal dependencies. They have to be placed together like a jigsaw puzzle, where clear points of intersection between the trees cause the puzzle pieces to fit together. This design activity creates a solution-focused representation, also tends to rationalize the components from which the completed system will be constructed. Dromey likes to refer to this whole process as "Genetic Software Engineering." The whole point of this approach is to master the complexity that accompanies building a significant software system. As a fringe benefit of this approach, the traceability of the original requirements into the as-built software system becomes much easier. It is also a powerful way to find defects in a system early--only when a requirement arises. pubtype: Periodical doctype: Article src: R language: English refInfo: copyright: @attributes: flag: Y dt: @attributes: year: 2004 holdings: @attributes: islocal: N |
|---|