Hatley-Pirbhai modeling

From Wikipedia, the free encyclopedia

What follows is a fairly accurate description of Hatley-Pirbhai modeling when applied to software only. The Hatley/Pirbhai methods are, however, much broader than described here. They are system-level methods that apply to multi-disciplinary systems of all kinds, where software is just one technology of many. Examples of such systems are: a complete automobile or aircraft; the Intelligent Highway System (ITS); the International Space Station; and many more. The methods deal with the physical structure of the system as well as the functionality that it performs. The flows within the models represent material, energy, or information.^[1]

Hatley-Pirbhai modeling is an extension of the concept that every computer system can be modeled through the usage of an input-processing-output model by including the two additional features of user interface process and maintenance/self testing.^[2] These 5 components are added to a system model template to allow allow for modeling of the system which allows for proper assignment to the processing regions.^[2] The templates components are User Interface, Input, System Function and Control, Output and Maintenance/Self Test.^[2] This modeling technique allows for creation of a hierarchy of detail of which the top level of this hierarchy should consist of a System Context Diagram.^[2] The developed system context diagram serves the purpose of, "establish[ing] the information boundary between the system being implemented and the environment in which the system is to operate."^[2] Further refinement of the system context diagram requires analysis of the system designated by the shaded rectangle through the development of a system flow diagram.^[2]

[edit] References