Input-driven development process

Company SHE information systems, on the other hand, are man-made artefacts that have not been exposed to the rigorous laws of natural selection. In developing SHE information systems, experts have a tendency to ask questions such as What information can we get What do we do about it These questions are typical for an input-driven development process, where the end result often is inefficient and even inadequate. History is full of examples of data graveyards, where elaborate databases on accidents have... 

The IT security development process, compliant to [6], corresponds to the step by step creation of ST or PP specifications. It encompasses 6 stages, presented below, each having wizard driven steps. Wizard functionalities represent the essence of IT security development methodology. For each step, the developer, aided by the tool and provided with necessary input data to analyze it, specifies output data. For attaching items to the specification, a short justification and coverage status can be added. The wizards, itemizing the actions, suggest sequential nature of the development process. It is not true - it is complex, rather recursive and incremental. 

Setting up a safety information system for a single project or product may be easier. The effort starts in the development process and then is passed on for use in operations. The information accumulated during the safety-driven design process provides the baseline for operations, as described in chapter 12. For example, the identification of critical items in the hazard analysis can be used as input to the maintenance process for prioritization. Another example is the use of the assumptions underlying the hazard analysis to guide the audit and performance assessment process. But first the information needs to be recorded and easily located and used by operations personnel. 

Any program developed in-house must be easy to use, or user-friendly. If the program has various options for input, analysis, computation, and output, then it must provide the user with a fast way to select them. To meet this need, the system is likely to be menu-driven. The peripheral interactive devices such as mice, joysticks, light pens, graphic tablets, and templates are helpful and often used to expedite the selection process. 

In our effort to collect the appropriate data and develop the requisite understanding of geochemical processes, we have developed some adjunct computer programs. These include AACALC (Atomic Absorption and emission spectrometry CALCulation), EQLIST (Equilibrium computation LISTing), and EQPRPLOT (Equilibrium computation PRinting and PLOTing). AACALC (FORTRAN) reduces atomic absorption or emission spectrometry data to concentrations, EqLIST (PL/1) constructs tables from the WATEqZ (input) card file, and EqPRPLOT (FORTRAN) constructs ratio and scatter plots of dissolved constituents, activity products (AP), or activity product to solubility product ratios (AP/K) via computer terminal printer or tape-driven plotter. 

Furthermore, SE specifies that the inputs for the creation of physical models are to be provided by the logical model that represents the systems view (Fig. 9.7). This enables therefore the parallel creation of domain specific models instead of a sequential development of the physical models, that would be driven by the mechanical design. Since concurrent engineering addresses the parallelization of diverse phases and processes of product development, it can be considered as a complementary for systems engineering. 

The CAPP system will be driven by input from the CAD system. CAPP features will include the determination of material, process, machine and tooling requirements and the development of process plans which detail how the house will be made. Process plans will include material routings and operations sheets detailing operations at each workstation. 

---