UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

CRC - AUE8075

Modeling Software Behavior : A Craftsman's Approach

active, Most Current
Organization: CRC
Publication Date: 21 July 2009
Status: active
Page Count: 224
scope:

A common problem with most texts on requirements specifications is that they emphasize structural models to the near exclusion of behavioral models-focusing on what the software is, rather than what it does. If they do cover behavioral models, the coverage is brief and usually focused on a single model. Modeling Software Behavior: A Craftsman's Approach provides detailed treatment of various models of software behavior that support early analysis, comprehension, and model-based testing.

Based on the popular and continually evolving course on requirements specification models taught by the author at universities and corporate environments, the text covers six behavioral models-providing the background behind these models and the required mathematics. As evidence of models at work, the author introduces eleven continuing examples. Five of these examples are illustrated with the six models, allowing readers to easily compare the expressive power of the various models. The examples chosen reflect a wide variety of behavioral issues.

Providing complete coverage that includes flowcharts, decision tables, finite state machines, two variations of Petri Nets, and StateCharts, this book will help students develop the understanding of the expressive capabilities and limitations of models of system behavior needed to make informed and appropriate choices among different models when confronted with new challenges.

Document History

AUE8075
July 21, 2009
Modeling Software Behavior : A Craftsman's Approach
A common problem with most texts on requirements specifications is that they emphasize structural models to the near exclusion of behavioral models—focusing on what the software is, rather than what...
Advertisement