Software languages

There has been a flurry of interest over the past decade in the use of object-oriented tools that focus on the representation of human knowledge and how humans use that knowledge in reed situations to make decisions and act. An example of this approach is the Distributed Operator Model Architecture (DOMAR), developed by Dr. Michael Young of the Wright Patterson Air Force Research Laboratories and Mr. Stephen Deutsch of BBN Inc. (Young and Deutsch 1999). The system is composed of a framework of software languages and model-development tools. As with the other models discussed in this section, the intention is to provide the analyst with the necessary components to develop models that simulate both the human operators and the systems with which they interact. 

Flexibility to change with business and technical requirements Hardware and system software Language and development tools Compatibility with current systems... 

An SCA is not capable of validating the risk, if any, associated with software algorithms. The SCA will only perform software language and interface evaluations and cannot analyze the actual methods that a system uses to solve a certain kind of problem. Hence, hazard risks associated with these methods may go undetected during analysis. 

Kleppe A (2009) Software language engineering creating domain-specific languages using metamodels. Pearson Education, Boston... 

NOTE 2 The type of software language used (FPL, LVL or FVL) and the closeness of the language to the application functions may impact the scope of the V-model phases. 

The impact of software language used on the device selection process... 

Software languages have been partitioned into three new categories,(i.e., FVL, LVL, and FPL). 

Because OOIAXES is a systems language, its semantics is more general than a software language. For example, 001 AXES defined systems could run on a computer, person, autonomous robot, or an organization whereas the content of the types (or classes) in a software language is based on a computer that runs software. 

The discussions on SRS will not be completed until specific reference is made to software development. For software development, the lEC recognizes (Clause 12.2.2 of lEC 61511-1 2003) three types of software and three software languages as depicted in Fig. X/1.1.6-1. 

Rigorous efforts are put to make software languages clear. Similarly, efforts are also necessary to make the process definition language clear and well understood. 

In computer software languages, there are a few familiar features such as artifacts, scoping, looping, if-then-else, and sequencing, etc. So, it seems reasonable to have such software language approach in process definition languages also. 

Soft tree analysis is a tool that engineers and software progranuners can both understand. If the engineer is comfortable with fault trees, then it will not take long to feel comfortable with soft tree analysis. The logic gate symbols are the same. It can be used with any software language. NASA uses this method extensively on spacecraft control systans. 

In addition, there remains a non-disprovable concern that there may be a weakness to common-mode failure (CMF) if both sets of logic solvers in two nominally diverse systems are software-based. This concern is related to the complexity of software systems, and the associated difficulties of verification and validation (V V). In some undefined way, similarities in the software code design and production processes may yield the possibihty of CMF - even if different software languages and operating systems are employed in the two systems. Because of this concern, it has become common in some countries to specify that the diverse protection system should be hard-wired. 

DRM method In step 7, when the specification of the DCPN-based model and the risk decomposition are fully defined, they are implemented in software language in order to be able to run Monte Carlo simulations. Many software languages are suitable for this, as long as they accept all DCPN syntax principles. A major step in the software implementation is to test the code against all elements of the DCPN-based model and Risk decomposition. 

PauUieim, H., Oberle, D., Plendl, R., Probst, F. An architecture for information exchange based on reference model. In Sloane, A.M., Apmann, U. (eds.) Revised Selected Papers of the 4th International Conference on Software Language Engineering (SLE). Lecture Notes in Computer Science, vol. 6940, pp. 160-179 (2011)... 

---