This fact is of little surprise to us. In fact, we have done a lot of research in this area and found that there is NO consistency and agreement on how various organizations manage interfaces. Let me explain…. For existing systems, how another system can interface to the existing system should have been already documented. When two systems are in development, the definition of the interfaces evolve with the design. The name is not as important as the content.
What Is an Interface Control Document?
Interface control document - Wikipedia
A user interface specification UI specification is a document that captures the details of the software user interface into a written document. The specification covers all possible actions that an end user may perform and all visual, auditory and other interaction elements. The UI specification is the main source of implementation information for how the software should work [ citation needed ]. Beyond implementation, a UI specification should consider usability, localization , and demo limits.
Subscribe to RSS
Every organization needs a document management strategy. Having one:. Not having one puts your organization at an unnecessary risk and decreases overall efficiency.
Within the traditional textual based development process, an ICD was either a text-based document or, a UML type diagram or a combination of the two. Within the MBD development process, it is not entirely clear if additional supporting documentation is required or if the Model can serve as the ICD. With most topics that I write about I have reached a firm conclusion on what is the accepted best practice.