Interfaces are the functional and/or physical interface between two components with a system. The components can be internal or external to the system.  It’s key to understand these interfaces in systems engineering to make sure a systems components work properly with each other. See Interface Management

Interface definition and control
Interface definition and control are activities that begin in parallel with the development of Functional Architectures. Typically a system is initially depicted by a System Diagram that bounds the system by depicting the system along with its external elements. Source documentation, such as Capabiity Development Documents (CDD), CRDs, external element specifications, and interface documents, might also provide interface requirements to ensure interoperability between systems and make sure required capabilities are achieved. An operational concept may also provide descriptions, interactions, and requirements between the system and the external elements. An interface definition process will evolve interface architectures and requirements in conjunction with the overall systems definition process. The interfaces will mature as the operational and system requirements mature. First an initial top level interface architecture is created. This architecture is also a reflection of the system concept. If alternative concepts are under consideration, alternative interface architectures are also developed. The functional decompositions of the interfaces are performed in concert with that of the system since the interface elements must be tightly coupled to the to system architectures. This one-for-one correlation initiates the interface architecture that is triggered by and traceable to identified system functions and any associated source and derived requirements. This procedure significantly reduces requirements conflicts and supports a more rapid interface design change process. [1]

AcqLinks and References:

Updated: 7/17/2017

Print Friendly, PDF & Email