P-notation: High level discription language for software design

1980 ◽  
Vol 4 (8) ◽  
pp. 307-311 ◽  
Author(s):  
Steve Young
Keyword(s):  
Author(s):  
Pamela Munro ◽  
Richard Mogford

Airline dispatchers’ workflow is often described in broad terms like ‘flight planning’ and ‘flight following.’ Such high-level descriptions fail to recognize the number and complexity of tasks involved in these activities. An ethnographic study was conducted at three US airlines to understand the cognitive workload involved in flight planning. Fuel planning was identified as one of five key flight planning tasks. Fuel planning was conducted concurrently with other planning and monitoring tasks which often led to interruptions. Planning fuel was dynamic, with re-calculations required whenever other factors varied. This rework increased workload and opportunities for error while reducing efficiency. Beyond route changes, four main factors contributed variability to fuel planning: contingency planning, load planning, pilots, and station operations. Strategies for managing variability included pattern identification, use of buffers, rounding up, and leveraging software tools. Software design often added workload by forcing dispatchers to attend to low level tasks.


Author(s):  
DIMITER R. AVRESKY ◽  
PRADEEP K. TAPADIYA

This paper presents a multi-stage software design approach for fault-tolerance. In the first stage, a formalism is introduced to represent the behavior of the system by means of a set of assertions. This formalism enables an execution tree (ET) to be generated where each path from the root to the leaf is, in fact, a well-defined formula. During the automatic generation of the execution tree, properties like completeness and consistency of the set of assertions can be verified and consequently design faults can be revealed. In the second stage, the testing strategy is based on a set of WDFs. This set represents the structural deterministic test for the model of the software system and provides a framework for the generation of a functional deterministic test for the code implementation of the model. This testing strategy can reveal the implementation faults in the program code. In the third stage, the fault-tolerance of the software system against hardware failures is improved in a way such that the design and implementation features obtained from the first two stages are preserved. The proposed approach provides a high level of user-transparency by employing object-oriented principles of data encapsulation and polymorphism. The reliability of the software system against hardware failures is also evaluated. A tool, named Software Fault-Injection Tool (SFIT), is developed to estimate the reliability of a software system.


Author(s):  
Spiros Mancoridis

We have developed a framework for specifying high-level software designs. The core of the framework is a very simple visual notation. This notation enables designers to document designs as labelled rectangles and directed edges. In addition to the notation, our framework features a supporting formalism, called ISF (Interconnection Style Formalism). This formalism enables designers to customize the simple design notation by specifying the type of entities, relations, legal configurations of entities and relations, as well as scoping rules of the custom notation. In this paper we present the formal definition of ISF and use ISF to specify two custom design notations. We also describe how ISF specifications, using deductive database technology, are used to generate supporting tools for these custom notations.


Author(s):  
Gerrit Muller

The IT industry is suffering from severe budget overruns and ill-performing IT services. Some of the problems that have caused IT project disasters could have been anticipated in the early project phases and mitigated in the project follow-up by modeling the system context and the software design. This chapter shows how to make models of varied views and at varied levels of abstraction to guide software design choices. Models of the enterprise provide understanding of the objectives. Models of the specification provide understanding of system performance and behavior. Models of the design provide understanding of design choices, such as the allocation of functions, resource usage, selection of mechanisms for communication, instantiation, synchronization, security, exception handling, and many more aspects. High-level models are simple models with the primary goal to support understanding, analysis, communication, and decision making. The models have various complementary representations and formats, e.g. visual diagrams, mathematical formulas, and quantitative information and graphs. Model-driven and model-based engineering approaches focus mostly on artifacts to analyze and synthesize software and hardware. High-level models complement model driven approaches by linking the system context to more detailed design decisions. High-level modeling as discussed in this chapter is based on research performed in industrial settings; the so-called industry-as-laboratory approach.


2014 ◽  
pp. 1440-1460
Author(s):  
Gerrit Muller

The IT industry is suffering from severe budget overruns and ill-performing IT services. Some of the problems that have caused IT project disasters could have been anticipated in the early project phases and mitigated in the project follow-up by modeling the system context and the software design. This chapter shows how to make models of varied views and at varied levels of abstraction to guide software design choices. Models of the enterprise provide understanding of the objectives. Models of the specification provide understanding of system performance and behavior. Models of the design provide understanding of design choices, such as the allocation of functions, resource usage, selection of mechanisms for communication, instantiation, synchronization, security, exception handling, and many more aspects. High-level models are simple models with the primary goal to support understanding, analysis, communication, and decision making. The models have various complementary representations and formats, e.g. visual diagrams, mathematical formulas, and quantitative information and graphs. Model-driven and model-based engineering approaches focus mostly on artifacts to analyze and synthesize software and hardware. High-level models complement model driven approaches by linking the system context to more detailed design decisions. High-level modeling as discussed in this chapter is based on research performed in industrial settings; the so-called industry-as-laboratory approach.


2014 ◽  
Vol 599-601 ◽  
pp. 1158-1161
Author(s):  
Shan Ying Cheng ◽  
Xue Mei Zhou ◽  
Qin Jiang

According to the characteristics of mixed traffic flow of China, An intelligent traffic signal controller is introduced. STM32F207 and w5500 are used to design hardware structure. The software design is completed based on CoOS. Single point fuzzy control is used to improve dynamic traffic flow. Experimental results show that the intelligent traffic controller has high level of integration, powerful functions, and reliable performance.


Sign in / Sign up

Export Citation Format

Share Document