Agile Systems Engineering

Informationen zum Autor Embedded Software Methodologist. Triathlete. Systems engineer. Contributor to UML and SysML specifications. Writer. Black Belt. Neuroscientist. Classical guitarist. High school dropout. Bruce Powel Douglass, who has a doctorate in neurocybernetics from the USD Medical School, has over 35 years of experience developing safety-critical real-time applications in a variety of hard real-time environments. He is the author of over 5700 book pages from a number of technical books including Real-Time UML, Real-Time UML Workshop for Embedded Systems, Real-Time Design Patterns, Doing Hard Time, Real-Time Agility, and Design Patterns for Embedded Systems in C. He is the Chief Evangelist at IBM Rational, where he is a thought leader in the systems space and consulting with and mentors IBM customers all over the world. He can be followed on Twitter @BruceDouglass. Papers and presentations are available at his Real-Time UML Yahoo technical group (http://tech.groups.yahoo.com/group/RT-UML) and from his IBM thought leader page (www-01.ibm.com/software/rational/leadership/thought/brucedouglass.html). Klappentext Agile Systems Engineering presents a vision of systems engineering where specification of requirements, structure, and behavior meet larger concerns such as safety, security, reliability, and performance. Traditionally, systems engineering has resulted in many disconnected paper documents, each attempting to specify some aspect of the system. Errors in the documents themselves and in their interconnection are often missed because the primary means by which quality is ensured is painstaking, error-prone manual review. . Leading author Bruce Douglass incorporates Agile methods and model-based development to consider the goals of an entire system and avoid errors that can occur when functions are developed independently and disconnected from the big picture. Douglass covers the lifecycle of systems development, including requirements, analysis, design, and handoff stages to specific engineering disciplines. Throughout, Douglass couples Agile methods with system concepts to address the needs of system engineers, avoid many common specification defects, and improve system quality while reducing the effort and cost of systems engineering. Inhaltsverzeichnis 1. What is Model-Based Systems Engineering?2. What are Agile Methods and Why Should I Care?3. The importance of Agile methods4. Agile Stakeholder Requirements Engineering5. Agile Systems Requirements Definition and Analysis6. System Architectural Analysis and Trade Studies7. Agile Systems Architectural Design8. The Handoff to Downstream Engineering AppendixA. T-Wrecks Stakeholder RequirementsB. T-Wrecks System Requirements ...

Klappentext

Agile Systems Engineering presents a vision of systems engineering where specification of requirements, structure, and behavior meet larger concerns such as safety, security, reliability, and performance. Traditionally, systems engineering has resulted in many disconnected paper documents, each attempting to specify some aspect of the system. Errors in the documents themselves and in their interconnection are often missed because the primary means by which quality is ensured is painstaking, error-prone manual review. . Leading author Bruce Douglass incorporates Agile methods and model-based development to consider the goals of an entire system and avoid errors that can occur when functions are developed independently and disconnected from the big picture. Douglass covers the lifecycle of systems development, including requirements, analysis, design, and handoff stages to specific engineering disciplines. Throughout, Douglass couples Agile methods with system concepts to address the needs of system engineers, avoid many common specification defects, and improve system quality while reducing the effort and cost of systems engineering.

Inhalt

1. What is Model-Based Systems Engineering?2. What are Agile Methods and Why Should I Care?3. The importance of Agile methods4. Agile Stakeholder Requirements Engineering5. Agile Systems Requirements Definition and Analysis6. System Architectural Analysis and Trade Studies7. Agile Systems Architectural Design8. The Handoff to Downstream Engineering

AppendixA. T-Wrecks Stakeholder RequirementsB. T-Wrecks System Requirements