(Ebook) The Method Framework for Engineering System Architectures by Donald G. Firesmith, Peter Capell, Charles B. Hammons, DeWitt Latimer, Tom Merendino, Dietrich Falkenthal ISBN 9781420085754, 1420085751

(Ebook) The Method Framework for Engineering System Architectures by Donald G. Firesmith, Peter Capell, Charles B. Hammons, DeWitt Latimer, Tom Merendino, Dietrich Falkenthal ISBN 9781420085754, 1420085751

The architects of today’s large and complex systems all too often struggle with the lack of a consistent set of principles and practices that adequately address the entire breadth of systems architecture. The Method Framework for Engineering System Architectures (MFESA) enables system architects and process engineers to create methods for effectively and efficiently engineering high-quality architecture for systems, subsystems, and software components.

Meets the Needs of Specific Projects

The book begins by documenting the common challenges that must be addressed by system architecture engineering. It explores the major principles answering these challenges and forming the basis of MFESA. Next, the authors introduce MFESA, including its primary goals, inputs, tasks, outputs, and assumptions. Then they describe the fundamental concepts and terminology on which the systems architecture engineering is founded. This is followed by a description of each of the ten system architecture engineering tasks including associated goals and objectives, preconditions, inputs, steps, postconditions, work products, guidelines, and pitfalls.

Finally, the book documents the relationship between quality and architecture, explains the quality model underlying MFESA, and provides a summary of MFESA method framework, as well as a list of points to remember and future directions planned for MFESA.

В Explains Specific Rationales

 Organized as a handy desk reference, this book harnesses more than 100 years of the authors’ combined professional experience to provide extensive guidelines, best practices, and tips on avoiding possible pitfalls. It presents a direct rationale of why steps are taken, how things can go wrong, and guidance for how and when to tailor the model for a system’s specific context.