Материал: Крючков Фундаменталс оф Нуцлеар Материалс Пхысицал Протецтион 2011

seals. All this is virtual, i.e. the connection to real seals is the responsibility of the operator.

∙Generation of reports. In general terms, the system enables new reports to be easily added and you will do it as part of your lab practice. The base reports are reports for the following groups:

containers (transactions with containers and the content of containers); content of physical locations;

MBAs (transactions in the MBA selected and the MBA content); transactions (output of transactions as arranged by dates and users). Besides, the system supports generation of special reports for the

Federal NM Accounting System. As no form for such reports has been specified by the system establishment time, the system contains an arbitrary report.

There should be also an understanding that “report” , as seen by the E/Z MAS developers, is an ordered table, formed according to specific rules, that has been chosen from the database with the aid of an SQL query. Russian requirements to A&C systems demand that an electronic system should be backed up by collection and keeping of hard information copies. This does not imply anything that cannot be done, still one should understand that, in addition to the electronic version, a potential Russian user of the E/Z MAS is expected to make so that to be able to get printouts of reports in any form. It can be easily done in the MS Access environment.

∙Configuration of data. As mentioned hereinabove, the system includes rarely updatable tables (locations, MBAs, enterprises, users). These tables can be updated only for special authorized users with the administrator status.

∙DB interoperation with peripherals. The most recent E/Z MAS version offers a capability to database information directly from peripherals. Functions of communication with two types of devices (barcode equipment and scales) have been built in. The communication is via a com–port from a dedicatedly equipped workstation. Programmatically, Active–X that communicates with this port is used in the asp-file. This function entails a problem still requiring solution. When peripherals are off the computer, there are no these functions in the system interfaces. When a workstation gets connected to peripherals, the functions are on in all interfaces because of having been uploaded from one file on the Web–se rver. It is not a big problem and one solution to this is to switch on this function for users with special logins who have measurement and inspection authorizations.

361

∙ System access security also has a key role in operations. Each user has his/her name linked to a set of functions he/she is authorized to perform. The E/Z MAS supports three user types:

users with the right of viewing only authorized information; users with the right of modifying authorized information;

database administrators – users with the right of a uthorizing the rights of other users.

Examples of E/Z MAS interfaces

To conclude with, we shall consider examples of the system’s interfaces, that is, how the above-described functionality is realized in asppages. Here are some of the typical examples to illustrate how a script technique and a system form design can be used.

Fig. 7.13 shows the E/Z MAS home page opening in the browser as the system is logged in. The user is offered to enter the login and the password. There is a version of the E/Z MAS A&C system that requires two independent user identifiers to be entered. This version is realized for enterprises where the so-called two-person rule is practiced (two persons only may have access to an activity with NM or information thereon).

Fig. 7.13. The E/Z MAS initial page

362

The system has one uncertified component, the MS Access DBMS, which limits, mostly, its applicability. To be recertified, the system is being given a profound upgrade based on open-code base software.

To finalize this chapter on computerized NM A&C systems, we shall discuss how such systems are developed and commissioned and the whole process is regulated.

7.5. Development of computerized NM A&C systems

A study of computerized NM A&C systems has one important point to consider. This is about how a software product is being built throughout the series of phases, from the inception to the commercial implementation. In this respect, it is not only the system creation procedures that matter but also the documentation that becomes required.

Russian standards are fairly regulatory in this regard. The USA, with a much greater experience in establishing large software projects than Russia, has however in effect diverse procedures and techniques to plan, design, test and commission software. Software development concepts and methods demand a separate consideration, so these will be overviewed in brief further in this Chapter with some guidance provided.

Industry standard’s requirements to development, commissioning and operation procedures

The respective industry standard [1] identifies a number of phases involved in creation of A&C systems. The initial one is the predesign stage opened with a site survey. This needs a feasibility study and an analytical (data security) justification to be prepared for the A&C system development. A design specification is developed with well-defined information protection requirements included.

Next comes the design. The final step in this is the detail design, including organizational and technological concepts, software development, and data protection provisions and practices. All concepts accepted are to satisfy to the regulations and requirements of standards and the design specification requirements.

The hardware and software designed need to go through a series of tests. Hardware:

∙tests for functionality in the installing site’s environment;

∙tests for conformity to data security requirements.

364

The base and applied software undergoes a laboratory test series. Data security features shall be certified for conformity to respective data security regulations.

The system is commissioned at the subsequent phase. To commission an A&C system, it is required to:

∙develop the listing of operating documentation;

∙submit a general description of the system, including performance, application and required hardware data;

∙develop a package of regulatory working documentation;

∙submit a description of a package of organizational and technical measures, the institutional structure and the manning schedule of the enterprise to the extent concerned with the A&C system;

∙develop a systems programmer guide to include information on the system installation, setup, testing and crash recovery (reference to GOST State Standards follows);

∙develop a user guide with the information to support the user and A&C system software/hardware dialog;

∙submit the software acceptance certificate;

∙submit the A&C system commissioning schedule.

The commissioning shall involve the A&C system software certification for the conformity to information security requirements.

There can be pilot and commercial operation. Pilot operation of the system requires its prior certification by a special commission. The commission formed to bring the system into pilot operation shall be composed of the developer, customer and operator representatives. Where the A&C system is connected to the central information system, the commission shall also include a representative of the inspecting agency. A technical acceptance certificate shall be made out.

No further steps are regulated by the standard. Other standards exist on automated systems and information technologies. This is where maintenance, support and decommissioning issues are regulated. There is also an abundance of engineering documentation that accompanies the project.

Software lifecycle

The US standard introduces the concept of software lifecycle. This represents all processes relating to a particular software product, from conceptualization to decommissioning and substitution for a newer product.

365