The development of state information systems, state electronic services, and electronic government systems require special approaches. However, at present, the requirements for the design notation of domestic state software are not defined and fixed. In the established practice, in the development of state software projects with a certain specificity and increased social significance, already existing technological solutions used in the private business are applied to the state information systems for various state departments of the Russian Federation. For the design of the state information systems and state e-services, it is suggested to use the unified methodology proposed by the authors, which includes subjects and objects, actions and processes, administrative restrictions, the IDEF0 standard, workflow class notation, the UML standard. The use of the proposed unified design methodology significantly structures, unifies and simplifies state software development. The advantages of using the proposed approach are illustrated in the implemented project to create a domestic customs inspection system.
Based on the analysis of software design methodologies (for example, see [4]), the following can be used as the basic methodology: UML, BPEL, ARIS, and others. However, there is no notation allowing documents to generate a description of administrative regulations in the established format.
We offer using a unified approach, combining IDEF0 and BPM methodologies, with additional notation elements. The use of existing symbols and rules (IDEF0 and BPMN) as a notation guarantees stability, improves understanding of the project by all parties (customer, contractor, etc.) and reduces the design time (because ready-made notations are used).
The toolkit available in the notations described above is not intended for a detailed description of the specifications of state processes and is not able to qualitatively and fully reflect all business processes of state e-services. Thus objects and subjects (see details in [2, 4]) were added to the proposed notation. Such notations as S-BPM, RDF, and some others also contain elements such as objects and subjects. They are successfully used in commercial projects, but they are not fully suitable for domestic state software projects.
An object is an entity that is affected. A subject is some influencing (acting) entity (for example, it can be both the applicant and the office). The description of new parameters contributes to the generation of detailed specifications, with the help of which it is possible to transfer the developed state software project to another state department, which meets the main principles of creating e-government projects. The process is called the interaction of subjects, their influence on objects through their actions.
Figure 2 shows the process of acceptance of documents for registration of a land plot with the additional administrative regulations element of notation.
legislation Acceptance of documents for registration of a
land plot application completed application application
form Consideration
of the application decision on the application Figure 2: Diagram of acceptance of documents for registration of a land plot
An analysis of state information systems creation and e-services development show the feasibility of creating a certain combined design methodology that combines various approaches. We propose to use a single unified design methodology, which includes subjects and objects, actions and processes, administrative restrictions, the IDEF0 standard. This standard greatly simplifies the manager's understanding of the used business process model and contributes to the full implementation of the development strategy of the relevant department.
In the author's methodology also included workflow class notation for lower levels (the sequence of execution of operations for developers), the UML standard for a more detailed description of the system (especially the logic of behavior of its individual components).
Using the proposed unified design methodology significantly structures, unifies and simplifies state software development.
The following Table 1 gives a summary of comparison of different design methodologies. 4. Implications
The benefits of using the proposed approach can be illustrated on the implemented project on the creation of the customs inspection system in the Volga Customs. In the notation used in the project, the functional model for conducting customs clearance of goods and the automatic generation of related documents are as follows, see Figure 3.
instructions regulations cargo vehicle cargo documents vehicle documents comparison files referral for inspection input and scan operator profile processing and analysis operator profile federal employee operator profile and resources / facilities Figure 3: Diagram of the customs inspection
Customs inspection using inspection system decision document about inspection inspection report printed images after analysis inspection file
A distinctive feature of the top-level diagram is the manager’s traceable point of view on the entire business process and the final inspection result. The input parameters and the result of the customs inspection system work are clearly visible. Of course, the basic algorithm of the customs inspection system work requires a more detailed study. Therefore, it is described at the lower levels, but using the same notation, for example, see Figure 4.
processing and analysis operator profile correct original image instructions
Image processing inspection id id and verified setting data id and scanned cargo documents id and scanned vehicle documents comparison files processed image instructions
Image analysis analysis and processing operator profile changes processing and analysis activity log cargo decision record analyzed image
Printing of inspection act and image inspection act printed analyzed image Figure 4: Diagram of the image processing and analysis
An analysis of state information systems creation and e-services development show the feasibility of creating a certain combined design methodology that combines various approaches. In the paper, it is proposed to use the single unified design methodology. The dissemination of the developed notation (see, for example, recent works [7, 8]) accelerates the development of state e-services for e-government systems in the Russian Federation. Using the proposed unified design methodology significantly structures, unifies and simplifies state software development. The advantages of using the proposed approach are illustrated in the implemented project to create a domestic customs inspection system.