We're in the process of defining interfaces for a system and would also like to capture message formats and protocols. Can anyone point me to some good documentation and best practices for doing so? The Rhapsody help system is pretty useless on this subject.
This topic has been locked.
1 reply Latest Post - 2013-08-31T23:30:59Z by AE91_SHINJI_KANAI
Pinned topic Creating interfaces
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
AE91_SHINJI_KANAI 110000AE91146 PostsACCEPTED ANSWER
Re: Creating interfaces2013-08-31T23:30:59Z in response to strat68
HelloOne benefit of modelling interfaces with Rhapsody is to ensure consistency in your model through clearly defining interfaces, leading to improve reusable nature across the system and simplify testing of sub-systems with using various automated model-based features (animated sequence diagram, stubbing out an interface and replace with a test driver, etc). Check out rhapsody enlightenment site from the link below and look for " Systems Engineering: Creating Interface Specifications with Rational DOORS and Rhapsody". You might find it helpful.In Rhapsody, ports and contracts are used to define interfaces just as described in UML specification. Some of samples like Dish Washer will show examples of interface usage. These are sources I always revisit when I got stack in interface designing.--Shinji