Gülesir, GürcanAmerica, PierreBenschop, FrankBerg, van den KlaasAksit, MehmetLaar, van de PierrePunter, Teadehttp://purl.utwente.nl/publications/74865nullbookSectionSpringer20109789048198481In todays industrial practice, behavioral designs of software-intensive systems such as embedded systems are often imprecisely documented as plain text in a natural language such as English, supplemented with ad-hoc diagrams. Lack of quality in behavioral design documents causes poor communication between stake holders, up to 100 times more costly rework during testing and integration, and hard-to-maintain documents of behavioral designs. To address these problems, we present a solution that involves the usage of (a) data-flow diagrams to document the input-output relation between the actions performed by a software-intensive system, (b) control-flow diagrams to document the possible sequences of actions performed by the system, and (c) Vibes diagrams to document temporal or logical constraints on the possible sequences of actions performed by the system. The key benefit of this solution is to improve the separation of concerns within behavioral design documents; hence to improve their understandability, maintainability, and evolvabilitySpringer 2010 URN:NBN:NL:UI:28-74865 193 207