Transcription of Documenting Software Architecture: Documenting Interfaces
{{id}} {{{paragraph}}}
Documenting Software Architecture: Documenting InterfacesFelix BachmannLen BassPaul ClementsDavid GarlanJames IversReed LittleRobert NordJudith StaffordJune 2002 TECHNICAL NOTECMU/SEI-2002-TN-015 Pittsburgh, PA 15213-3890 Documenting Software Architecture: Documenting InterfacesCMU/SEI-2002-TN-015 Felix BachmannLen BassPaul ClementsDavid GarlanJames IversReed LittleRobert NordJudith StaffordUnlimited distribution subject to the 2002 Architecture Tradeoff Analysis InitiativeThe Software Engineering Institute is a federally funded research and development center sponsored by the Department of 2002 by Carnegie Mellon WARRANTYTHIS CARNEGIE MELLON UNIVERSITY AND Software ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN AS-IS BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL.
the interfaces of the elements shown in that view. What is an interface? Various communities use various definitions, but we use the following ... (RPCs), data streams, shared memory, and message passing. These constructs, which provide points of direct interaction with an element, are called resources. Other interactions are indirect.
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}