Showing posts with label systems engineering. Show all posts
Showing posts with label systems engineering. Show all posts

5/16/2012

Architecture and Principles of Systems Engineering (CRC Complex and Enterprise Systems Engineering) Review

Architecture and Principles of Systems Engineering (CRC Complex and Enterprise Systems Engineering)
Average Reviews:

(More customer reviews)
This text is a broad high level survey of systems engineering in the age of model-driven system development. Looking at the table of contents the coverage is extensive, but the depth on any given topic is pretty shallow. If you are a university student who hasn't had any exposure to systems engineering concepts (or software engineering concepts for that matter), then this text isn't a bad introduction to the terminology, (some of the)tools and process descriptions in modern systems engineering, especially if coupled with a project-based course where you can have a chance to apply some of these concepts directly. For such an audience, add one star to my rating. If, on the other hand, you are a practicing systems engineer (or software engineer), even if you're not all that familiar with the model-driven systems engineering paradigm, then this text is likely to come up a bit short, given its lack of depth on any given topic. For this second group of potential readers, take one star away from my rating. I was going to be cheeky and say that this is a great book for talking about systems engineering, but not so much if your interest is in doing systems engineering.
The description on the back cover is definitely over-hyped - publisher's perogative, I guess. You will not learn the obstacles, both technical and cultural, that model-driven systems engineering faces today. You will not learn UML or SysML. Executable models are introduced in the case studies, but again with little depth. Domain-specific modeling versus generic modeling (with say UML) is a hot topic not covered in the text. The advantages and disadvantages of auto-generated software are also not covered. Problems of integrating the model-based paradigm with legacy sysems is also missing. Pattern-based architectural development is also not covered. The case studies themselves specifically address classroom exercises with assignments and intructor responses, so depth seems intended to be obtained beyond the text through instructor interaction and hands on development. Each chapter could be expanded into an entire book.
What would I recommend as a more bit more practical introduction to model-driven systems engineering which addresses an audience both inside and outside the university classroom? Your favorite book on UML, A Practial Guide to SysML by Friedenthal, Moore and Steiner, and Systems Engineering with SysML/UML by Weilkiens. The Friedenthal et al. book has an introductory section which motivates the model-based systems engineering paradigm. I'd also recommend software architecture books, Documenting Software Architectures 2nd ed by Clements, Bachman, Bass and Garlan and Software Architecture: Foundations, Theory, and Practice by Taylor, Medvidovic and Dashofy (a bit more theoretical and not particularly model-based).
Don't be surprised if you see my copy available soon on Amazon Marketplace. I guarantee that it is in like new condition :)

Click Here to see more reviews about: Architecture and Principles of Systems Engineering (CRC Complex and Enterprise Systems Engineering)

The rapid evolution of technical capabilities in the systems engineering (SE) community requires constant clarification of how to answer the following questions: What is Systems Architecture? How does it relate to Systems Engineering? What is the role of a Systems Architect? How should Systems Architecture be practiced?A perpetual reassessment of concepts and practices is taking place across various systems disciplines at every level in the SE community. Architecture and Principles of Systems Engineering addresses these integral issues and prepares you for changes that will be occurring for years to come. With their simplified discussion of SE, the authors avoid an overly broad analysis of concepts and terminology. Applying their substantial experience in the academic, government, and commercial R&D sectors, this book is organized into detailed sections on: Foundations of Architecture and Systems EngineeringModeling Languages, Frameworks, and Graphical ToolsUsing Architecture Models in Systems Analysis and DesignAerospace and Defense Systems EngineeringDescribing ways to improve methods of reasoning and thinking about architecture and systems, the text integrates concepts, standards, and terminologies that embody emerging model-based approaches but remain rooted in the long-standing practices of engineering, science, and mathematics. With an emphasis on maintaining conceptual integrity in system design, this text describes succinct practical approaches that can be applied to the vast array of issues that readers must resolve on a regular basis. An exploration of the important questions above, this book presents the authors' invaluable experience and insights regarding the path to the future, based on what they have seen work through the power of model-based approaches to architecture and systems engineering.

Buy NowGet 8% OFF

Click here for more information about Architecture and Principles of Systems Engineering (CRC Complex and Enterprise Systems Engineering)

Read More...

5/06/2012

Abstract State Machines: A Method for High-Level System Design and Analysis Review

Abstract State Machines: A Method for High-Level System Design and Analysis
Average Reviews:

(More customer reviews)
This is a well written good about an interesting, sensible formalism. I haven't tried using any of it in my line of work yet, but I'm pretty sure I will. Abstract State Machines (ASMs) are based on guarded, synchronously concurrent state transitions, with state effectively defined as a (finite) set of named, finite relations. The core of the formalism seems very simple and elegant and lends itself to clear, concise models at both high and low levels of abstraction. I believe it is more readily comprehended by practicioners than purely algebraic and / or functional approaches, being firmly rooted in the notion of state, operational abstract execution runs and state changes.
They models can be designed in a modular and composable manner in a natural way. The book gives a clear, rigorous account of it all, is readable and well organized, and positively loaded with helpul examples and references. My only complaint is that fully asynchronous (i.e. distributed) systems seem to get somewhat of a short thrift.
Overall, I am really excited about this stuff, and looking forward to a time when all system development can be undertaken and supported with such elegant, refinable models, as opposed to the hodgepodge scripting-language-centric mess that is the current practice.

Click Here to see more reviews about: Abstract State Machines: A Method for High-Level System Design and Analysis

The systems engineering method proposed in this book, which is based on Abstract State Machines (ASMs), guidesthe development of software and embedded hardware-software systems seamlessly from requirements capture to actual implementation and documentation. The method bridges the gap between the human understanding and formulation of real-world problems and the deployment of their algorithmic solutions by code-executing machines. Within a single conceptual framework it covers design, verification by reasoning techniques, and validation by simulation and testing. ASMs improve current industrial practice by using accurate high-level modeling and by linking the descriptions at the successive stages of system development in an organic and efficiently maintainable chain of rigorous and coherent system models at stepwise-refined abstraction levels. In several industrial projects the ASM method has proven its superiority compared to the popular UML methodology when designing complex parallel or dynamic systems.This book combines the features of a textbook and a handbook: the reader will find detailed explanations, proofs, and exercises as well as numerous examples and real-world case studies. Researchers will find here the most comprehensive description of ASMs available today and professionals will use it as a "modeling handbook for the working software engineer." As a textbook it supports self-study or it can form the basis of a lecture course. The book is complemented by a CD containing the whole book text, additional course material, solutions to exercises, and additional examples. Even more information can be found on the related website maintained by the authors: http://www.di.unipi.it/AsmBook/

Buy NowGet 19% OFF

Click here for more information about Abstract State Machines: A Method for High-Level System Design and Analysis

Read More...

12/31/2011

Modeling Embedded Systems and SoC's: Concurrency and Time in Models of Computation (Systems on Silicon) Review

Modeling Embedded Systems and SoC's: Concurrency and Time in Models of Computation (Systems on Silicon)
Average Reviews:

(More customer reviews)
The writer of this book, Dr. Axel Jantsch, is a professor at the Royal Institute of Technology in Stockholm, Sweden. As a postgraduate student at the Technical University of Denmark, I have participated Dr. Jantsch's course whose curriculum was dictated by this book.
Dr. Jantsch is a splendid lecturer and his a pioneer in his comprehensive, yet highly-readable, cover of modelling technieques for embedded systems. The book covers in depth notions such as final state machines, petri nets, as well as the untimed, timed and synchronous computation models. Dr. Jantsch does not, unlike other sources, sticks only to the formalism related to the modelling, but also includes "real life" examples that make the reader apprieciate what model of computation is the more optimal for his modelling aims.

Click Here to see more reviews about: Modeling Embedded Systems and SoC's: Concurrency and Time in Models of Computation (Systems on Silicon)



Buy NowGet 7% OFF

Click here for more information about Modeling Embedded Systems and SoC's: Concurrency and Time in Models of Computation (Systems on Silicon)

Read More...

9/03/2011

Systems Engineering with SysML/UML: Modeling, Analysis, Design (The MK/OMG Press) Review

Systems Engineering with SysML/UML: Modeling, Analysis, Design (The MK/OMG Press)
Average Reviews:

(More customer reviews)
SysML is hard! So it should not be surprising that authors writing on the subject will be faced with a difficult task. To better understand the difficulties we all encounter in mastering SysML, we need look no further than its name. The Sys refers to Systems Engineering. To be a good systems engineer requires, first understanding the technical domains under study. Then systems engineering techniques needs to applied so that a comprehensive understanding of component relationships both among themselves and their environments can be achieved. The ML refers to the Unified Modeling Language (UML) upon which SysML is based. Thus, to understand SysML, one really needs a background in UML. But UML was designed to depict abstractions of object-oriented programs which logically leads to the realization that OO programming experience is also necessary, or at least very helpful. With these prerequisites, OO programming, UML, systems engineering and domain knowledge under your belt, you are ready to master SysML.
The author clearly understands this as the book is largely structured along these lines in six chapters, starting with introductory material related systems engineering. Chapter 2 extends these ideas to a case study showing how various SysML diagrams and features can be brought to bear in understanding a system from various perspectives. This is followed by a chapter on UML as it pertains to SysML. The final two chapters, 62 pages, are devoted to SysML.
I am unsure of the rationale of putting the case study at the beginning as it uses information from subsequent chapters. Readers may find useful to look first at the UML and SysML chapters, and return later to the case study.
The actual text and presentation of information is spotty, good information without a follow-up on its utility. For example, on page 167, we find, "There are associations between classes, links between objects and connectors between roles." This sentence very concisely organizes a vast amount of information by relating similar concepts across different levels of abstraction. However, if you are not aware of abstraction-level notions, this sentence would likely be lost on you. And unfortunately, the author does not pursue this avenue further.
I also found definitions at times less than precise. Consider the definition for the SysML Block element on page 243, "A block describes parts of the structure of a related system. It is a stereotype «block» of the UML element class." I have two problems with this definition. First, readers might assume that structure in the context of a block refers to structural features and in so doing make the assumption that blocks do not encompass behavioral features, which is not true. Second, I do not believe the assertion that a block is a stereotype of class expresses the concept completely.
The definition is followed by additional explanatory text, possibly modifying the definition: "Together with the block, SysML defines an element to be used for describing the static structure of systems." And, "The notation deviates slightly from the standard representation of stereotyped classes." Unfortunately, neither of these sentences seems clear.
By way of comparison, the OMG specification (p33) starts its block definition as follows, "Blocks are modular units of a system description, which define a collection of features to describe a system or other elements of interest. These may include both structural and behavioral features, such as properties and operations, to represent the state of the system and behavior that the system may exhibit." The specification also has the following to say about the relationship between blocks and classes, "SysML blocks are based on UML classes as extended by UML composite structures. Some capabilities available for UML classes, such as more specialized forms of associations, have been excluded from SysML blocks to simplify the language. SysML blocks always include an ability to define internal connectors, regardless of whether this capability is needed for a particular block. SysML Blocks also extend the capabilities of UML classes and connectors with reusable forms of constraints and multi-level nesting of connector ends. SysML blocks include several notational extensions as specified in this chapter."
My criticism is not in that the author is incorrect, rather that the lack of precision, perhaps in the interest of brevity, often makes the material difficult to understand and relate to other information. This would be especially true for readers unfamiliar with the subject area, the target group.
The above notwithstanding, the author provides readers with a considerable amount of information which by-in-large is accessible to a wide audience. Personally, I have found the book valuable, especially when used in conjunction with the OMG specification. Together, I am able to compare/contrast ideas from two perspectives allowing me to achieve deeper understandings of what can often be complex and abstract concepts.
I am sure other texts will appear having better organization, focus and precision. However, these future authors will be building on Tim Weilkiens' work.


Click Here to see more reviews about: Systems Engineering with SysML/UML: Modeling, Analysis, Design (The MK/OMG Press)

UML, the Universal Modeling Language, was the first language designed to fulfill the requirement for "universality." However, it is a software-specific language, and does not support the needs of engineers designing from the broader systems-based perspective. Therefore, SysML was created. It has been steadily gaining popularity, and many companies, especially in the heavily-regulated Defense, Automotive, Aerospace, Medical Device and Telecomms industries, are already using SysML, or are plannning to switch over to it in the near future. However, little information is currently available on the market regarding SysML. Its use is just on the crest of becoming a widespread phenomenon, and so thousands of software engineers are now beginning to look for training and resources. The proposed book will provide an introduction to SysML, and instruction on how to implement it, for all these new users. *The first available book on SysML in English *Insider information! The author is a member of the SysML working group and has written sections of the specification *Special focus comparing SysML and UML, and explaining how both can work together

Buy NowGet 21% OFF

Click here for more information about Systems Engineering with SysML/UML: Modeling, Analysis, Design (The MK/OMG Press)

Read More...