Designing Abstract Interfaces for Device Independency Review of A Procedure for Designing Abstract Interfaces for Device Interface Modules by D. L. Parnas et al. Jianjun Hu Yakub Sailanawala CSE870 MSU 2002. PROBLEM SOLUTION GOAL.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Designing Abstract Interfaces for Device IndependencyReview of A Procedure for Designing Abstract Interfaces for Device Interface Modules by D. L. Parnas et al.
Changes in hardware device interfaces often lead to widespread changes in the whole system
The device interface module [DIM] containing the device dependent code
The remaining software components that should be independent of device specific details.
design good abstract interfaces for DIM
A Procedure for Designing Abstract Interfaces for Device Interface ModulesHeninger, K. Parker, R. Parnas, D.L.IEEE Fifth International Conference on Software Engineering - 1981
Naval Research Lab's redesign of the flight SW for A-7 aircraft
Assumption List: List of all the assumptions about the characteristics of the hardware devices the user programs are allowed to make
Functional Description: API & Events Specification
Assumption List explicitly states the assumptions about the characteristics that are implicit in the Functional description
These descriptions must be reviewed by the users, hardware engineers and experienced programmersDesigning Abstract Interfaces
Commonality Analysis: A Systematic Process for Defining FamiliesDavid M. Weiss Proceedings of IEEE Second International Workshop on Development and Evolution of Software Architectures for Product Families 1998
Analytical technique for defining families
Define purpose and scope of the family
Define parameters of variation
Structuring formal control systems specifications for reuse: Surviving hardware changesJ. Thompson, M. Heimdahl and D. EricksonIn Proc. 5th NASA Langley Formal Methods Workshop - 2000
To design software control system for members of a family that displays the same high level behavior and survives changes in replaceable hardware devices
Obtain a high-level software specification of the requirements
4 Variables Model was proposed by D. Parnas and Jan Madey
Device Independent Navigation and Interaction in Virtual EnvironmentsC. Faisstnauer, D. Schmalstieg, Z. Szalavari Proceedings of the 1998 VRST Adjunct Workshop on Computer Graphics, Taipei, Taiwan
Device independence by Mapper Structure of Mapper
An Abstract-Device Interface for Implementing Portable Parallel –I/O InterfacesR. Thakur, W. Gropp, and E. LuskProc. of the 6th Symposium on the Frontiers of Massively Parallel Computation, October 1996
Many File systems: Unix, PFS, PIOFS, NFS….
Many Parallel I/O API systems: IBM PIOFS, IntelPFS, RIO…
Interfaces are agreements on the functionalities that system should provide.
×Sacrifice power to generality
Concept of Transparency of Hierarchical System [Parnas. 1975]