David P. Gluch's Books

Model-Based Engineering with AADL

An Introduction to the SAE Architecture Analysis & Design Language

By: Peter H. Feiler,David P. Gluch

Write a review Read reviews Take a Quiz Solve Book Puzzle

Model-Based Engineering with AADL

An Introduction to the SAE Architecture Analysis & Design Language

By: Peter H. Feiler,David P. Gluch

Conventional build-then-test practices are making today’s embedded, software-reliant systems unaffordable to build. In response, more than thirty leading industrial organizations have joined SAE (formerly, the Society of Automotive Engineers) to define the SAE Architecture Analysis & Design Language (AADL) AS-5506 Standard, a rigorous and extensible foundation for model-based engineering analysis practices that encompass software system design, integration, and assurance. Using AADL, you can conduct lightweight and rigorous analyses of critical real-time factors such as performance, dependability, security, and data integrity. You can integrate additional established and custom analysis/specification techniques into your engineering environment, developing a fully unified architecture model that makes it easier to build reliable systems that meet customer expectations. Model-Based Engineering with AADL is the first guide to using this new international standard to optimize your development processes. Coauthored by Peter H. Feiler, the standard’s author and technical lead, this introductory reference and tutorial is ideal for self-directed learning or classroom instruction, and is an excellent reference for practitioners, including architects, developers, integrators, validators, certifiers, first-level technical leaders, and project managers. Packed with real-world examples, it introduces all aspects of the AADL notation as part of an architecture-centric, model-based engineering approach to discovering embedded software systems problems earlier, when they cost less to solve. Throughout, the authors compare AADL to other modeling notations and approaches, while presenting the language via a complete case study: the development and analysis of a realistic example system through repeated refinement and analysis. Part One introduces both the AADL language and core Model-Based Engineering (MBE) practices, explaining basic software systems modeling and analysis in the context of an example system, and offering practical guidelines for effectively applying AADL. Part Two describes the characteristics of each AADL element, including their representations, applicability, and constraints. The Appendix includes comprehensive listings of AADL language elements, properties incorporated in the AADL standard, and a description of the book’s example system.

Average ratings

N/A

Write a review

Solve jigsaw puzzle

Age

Page Count

765

Publisher

Addison-Wesley

Published Date

ISBN 10

0133132900

ISBN 13

9780133132908

Documenting Software Architectures

Views and Beyond

By: Paul Clements,Felix Bachmann,Len Bass,David Garlan,James Ivers,Reed Little,Paulo Merson,Robert Nord,Judith Stafford

Write a review Read reviews Take a Quiz Solve Book Puzzle

Documenting Software Architectures

Views and Beyond

By: Paul Clements,Felix Bachmann,Len Bass,David Garlan,James Ivers,Reed Little,Paulo Merson,Robert Nord,Judith Stafford

Software architecture—the conceptual glue that holds every phase of a project together for its many stakeholders—is widely recognized as a critical element in modern software development. Practitioners have increasingly discovered that close attention to a software system’s architecture pays valuable dividends. Without an architecture that is appropriate for the problem being solved, a project will stumble along or, most likely, fail. Even with a superb architecture, if that architecture is not well understood or well communicated the project is unlikely to succeed. Documenting Software Architectures, Second Edition, provides the most complete and current guidance, independent of language or notation, on how to capture an architecture in a commonly understandable form. Drawing on their extensive experience, the authors first help you decide what information to document, and then, with guidelines and examples (in various notations, including UML), show you how to express an architecture so that others can successfully build, use, and maintain a system from it. The book features rules for sound documentation, the goals and strategies of documentation, architectural views and styles, documentation for software interfaces and software behavior, and templates for capturing and organizing information to generate a coherent package. New and improved in this second edition: Coverage of architectural styles such as service-oriented architectures, multi-tier architectures, and data models Guidance for documentation in an Agile development environment Deeper treatment of documentation of rationale, reflecting best industrial practices Improved templates, reflecting years of use and feedback, and more documentation layout options A new, comprehensive example (available online), featuring documentation of a Web-based service-oriented system Reference guides for three important architecture documentation languages: UML, AADL, and SySML

Average ratings

N/A

Write a review

Solve jigsaw puzzle

Age

Page Count

651

Publisher

Pearson Education

Published Date

ISBN 10

0132488590

ISBN 13

9780132488594

Real-Time UNIX® Systems

Design and Application Guide

By: Borko Furht,Dan Grostick,David Gluch,Guy Rabbat,John Parker,Meg McRoberts

Write a review Read reviews Take a Quiz Solve Book Puzzle

Real-Time UNIX® Systems

Design and Application Guide

By: Borko Furht,Dan Grostick,David Gluch,Guy Rabbat,John Parker,Meg McRoberts

A growing concern of mine has been the unrealistic expectations for new computer-related technologies introduced into all kinds of organizations. Unrealistic expectations lead to disappointment, and a schizophrenic approach to the introduction of new technologies. The UNIX and real-time UNIX operating system technologies are major examples of emerging technologies with great potential benefits but unrealistic expectations. Users want to use UNIX as a common operating system throughout large segments of their organizations. A common operating system would decrease software costs by helping to provide portability and interoperability between computer systems in today's multivendor environments. Users would be able to more easily purchase new equipment and technologies and cost-effectively reuse their applications. And they could more easily connect heterogeneous equipment in different departments without having to constantly write and rewrite interfaces. On the other hand, many users in various organizations do not understand the ramifications of general-purpose versus real-time UNIX. Users tend to think of "real-time" as a way to handle exotic heart-monitoring or robotics systems. Then these users use UNIX for transaction processing and office applications and complain about its performance, robustness, and reliability. Unfortunately, the users don't realize that real-time capabilities added to UNIX can provide better performance, robustness and reliability for these non-real-time applications. Many other vendors and users do realize this, however. There are indications even now that general-purpose UNIX will go away as a separate entity. It will be replaced by a real-time UNIX. General-purpose UNIX will exist only as a subset of real-time UNIX.

Average ratings

N/A

Write a review

Solve jigsaw puzzle

Age

Page Count

338

Publisher

Springer Science & Business Media

Published Date

ISBN 10

1461539781

ISBN 13

9781461539780

Book's by David P. Gluch

Model-Based Engineering with AADL

Model-Based Engineering with AADL

Documenting Software Architectures

Documenting Software Architectures

Real-Time UNIX® Systems

Real-Time UNIX® Systems

Username

Password

Username

Password

Password again

Birthday

Email