THE INTEGRATED ENVIRONMENT FOR DESIGN, PROGRAMMING, TESTING AND REENGINEERING OF THE DISTRIBUTED INFORMATION RESOURCES

January 17, 2013 by admin Комментировать »

L. S. Globa National Technical University of Ukraine «Kiev Polytechnic Institute» Kiev, 03056, Ukraine Ph.: 044-2417699, e-mail: globa@densoft.com.ua

Abstract- The paper deals with development of the integration environment for designing, programming, testing and reengineering information and computation resources distributed in global telecommunication network.

I.                                      Introduction

The paper deals with the proposed methodology for the distributed information system (IS) development based on the some specific principles described in the paper [1]. Some of this principles are typical and some of

them, based like ^ ^ -principles, are not typical for scientific research in fields of both information and telecommunication technologies. There are new solutions for software design. The designed new software tools are also represented in the paper. There is detailed description of software development project logical stages that form the integral and complete project running and completion.

II.                                     Main Part

There are some overview of the main research fields in articles [1,2]. Main standard approaches the requirements to the developed platform are shown in [3].

In the methodology of IS functioning the concept of ICRP (Information Computation Resource Platform) is used. This methodology is discussed in the paper [1].

Pic. 1. IS functioning based on the ICRP

In this technology, on the stage of interconnection with user, the system is organized on the principle of graphical user interface (GUI) and internal logic division of program functioning.

GUI is designed by using Forms. They are manage elements set, which gives the customer the opportunity to look through data, edit them and inform the system about made decisions.

Transitions between forms are realized by Functions. They are system elements, in which data processing and^r decision making is realized. The result of the made decision is either corresponding exit value or management of the corresponding path.

The parts connection is realized by entry and exit points. They are the sections, on which management of elements is done. It is represented on the following diagram.

The information system, designed by using this methodology, can be represented as connected with function sequences of the forms calls. These sequences can be represented in the graph. Such graph is forms and functions tree (FFT). FFT represents forms and functions interconnections and also system functioning process using the set of data, moving on the graph branches (Pic.2).

Pic.2. Form and Function Tree (FFT), Functioning

Algorithm and Information Workflow applied to FFT

The technology main points are following: the graphs, mentioned already, are represented in the form of form and functions (their code) sets, saved in the database tables. This database tables describe forms and functions parameters and information about their interconnections features.

The ICRP development covers the testing aspect. The scheme representation of suggested testing subsystem is represented on the Pic. 3. Such approaches to the IS realization conform the suggested principles for designing distributed IS completely. So, the testing technologies are integrated into software product life cycle from the earliest stages.

The appropriate platform, being under the development, is the platform for carrying out some basis stages of the life cycle when the distributed system designing. They include: business process description, creation of the specifications, prototypical project and then project draft for the developed system and its subsystems designing, the IS functionality scheme visual representation by means of proprietary diagrams (UML-similar), functionality and interfaces testing at the earlier development stages, creation of prototypical project demo as the first temporary project draft stage.

Throughout the methodology description, the further theoretical basis for software systems development stages is shortly overviewed.

Its first stage is system architecture development. It includes structure and interface components development, functions settings, component technical requirements settings; data streams between main components settings; components connections and external objects settings.

The second stage is Detailed Design. It also includes several steps. They are: every component specification development, testing requirements development, components for the integration plan development, program modules hierarchy designing, internal modules structure designing.

The consideration of demo mode IS development stage starts with the necessity to mention some software development realities. The most considerable part of the whole modified development process is related to exactly IS components interface and structure design (Pic.4).

The central figure in the represented development stage is Customer. He fixes forms and functions interfaces, the way of their interconnection, and their parameters. As the result of such determination, customer needs to see not only every separate part of the future IS, but the prototype of future IS functioning. There is no existing tools IS functioning prototype development. It has to be developed. But there is one very important moment here: while designing the necessary tools, already existing tools and informational technologies for another life cycle stages can be used and integrated.

Pic. 3. Modified interpreter Functioning Aigoritiim

After describing all requirements to be agreed and met, it is necessary to realize the next step of process development. This is implementation and debugging of designed system prototype. For its implementation, the forms and functions execution is necessary.

The main concept is Graph oriented programming. That is used in JBRM. It is a technique for solving problem ofthe execution suspending and persisting. Because of its limited scope, this technique is easy to understanding and serves as the building block for other functionalities targeted by workflow, BPM and orchestration solutions.

Fig. 4 Demo mode designing process

The necessity of the whole project representation in database form question is very important. It is necessary to find some useful and practical solution for the project database development. Some idea for finding solution is following. The project development stages uses like a base for database structure designing. (Pic.5).

In the suggested realization all project data, information, objects and entities are stored in separate blocks, corresponding with the development stages. As the result of such diagram designing, it becomes clear, that IS components interface and structure development is the key stage of the IS development. It has the greatest influence on the project completion success.

The second idea, connected with project database is two forms ofthe database structure representation. They are:

1.    Corporation Team Development Database. It supports project development independence from developers (participants) and time project integrity.

2.    Every Participant of Development Team File Form Database, which provides project parts portability and time and place independence of the every part and development step.

The completion of IS components interface and structure development is continued by the implementation and debugging stages, which suppose code (functionality) adding to the designed system prototype.

The system functionality designing in the absolute accordance with its design principles, testing technologies implementation into the software product life cycle are provided using testing subsystem concept (Pic.6).

The next development stage is Deployment. It means IS implementation into exact application field. By the developers’ team, this step was integrated with module named integration and system testing. And as the result, the experiment in concrete application field was made.

Pic. 6. IS functioning scheme running in testing mode

Pic. 5. The database structure based on the development stages

The considerable changes in standard software tools realized by Designer are diagram opening algorithm and GUI.

III.                                    Conclusion

1.          IS all development stages were considered and applied, as the result – new software and methodological solutions were developed.

2.          Modified solution of IS development process steps (Fig. 1, Fig.2, Fig.3) and its new conceptions (Fig. 4, Fig. 5) give the following advantages:

❖          new developed software tools allow to design IS like look & feel and using functioning model;

❖          simultaneous logical and physical design allows to appreciate real abilities and make IS design plans while «Preliminary Design»;

❖          IS development stages DB provides:

–            convenient data structure representation and modernization;

–            easier error finding and their correction;

❖          2 outer subschemas of database structure representation provides:

–           time & place independence of IS development process;

–           project parts portability;

3.         JBPM mechanisms as the solution for FFT scenarios playing are applied.

4.         New software solutions are realized: «FFT Designer» (Modified version of «Designer») and «Process Execution Core» (Designer and JBPM integration).

IV.                                        Literature

[1]  L. S. Globa, Prof., Dr. Sci. Tech, «Approaches and technologies of creating data-processing resources in the telecommunication environment». Electronics and Communication, p.2, 2005., p.17-24-29

[2]  L. S. Globa, Prof., Dr. Sci. Tech, «New approaches to the data-processing resources development on the EJB-Basis », CriMiCo 2005. p. p. 171-174.

[3]  G. S. Ivanova, «Programming Technology», Manual for high educational establishments, Moscow National Technical University by N. E. Bauman, 2002, p.320

[4]  http://www.jbpm.org

ИНТЕГРИРУЮЩАЯ СРЕДА ПРОЕКТИРОВАНИЯ, ПРОГРАММИРОВАНИЯ, ТЕСТИРОВАНИЯ И РЕИНЖЕНИРИНГА РАСПРЕДЕЛЕННЫХ ИНФОРМАЦИОННЫХ РЕСУРСОВ

Л. с. Глоба

Национальный технический университет Украины «Киевский политехнический институт»

Киев, 03056, Украина тел.: 044-2417699, e-mail: gls@densoft.com.ua

Аннотация – В статье рассматривается развитие концепции создания интегрированной среды проектирования, программирования, тестирования и реинжениринга распределенных в Internet информационных и вычислительных ресурсов, а также реализация процессов их взаимодействия.

I.                                       Введение

Как начало дальнейшего развития данной работы взята ранее предложенная методология разработки распределенных информационных систем (ИС), построенная на определенных специфических принципах [1]. Некоторые из этих принципов являются типичными, а некоторые, такие как

^ ^ – принцип, – нетипичными для научных исследований в области как информационных, так и телекоммуникационных технологий. В результате таких исследований были найдены новые решения для разработки оригинального программного обеспечения (инструментария), краткое описание которого представлено в статье. В работе также рассматривается детальное описание логических этапов процесса создания программного обеспечения, которые формируют целостное и полное выполнение и завершение проекта.

II.                                Основная часть

Обзор основных областей научных исследований, стандартных подходов к проектированию информационных систем, а также требований к разрабатываемой платформе для разработки, программирования, тестирования и реинжениринга распределенных в глобальной среде Интернет информационных систем (ИС) был сделан в ранее представленных работах [1, 2, 3].

В методологии функционирования И С предлагается использование концепции ICRP (Платформы информационновычислительных ресурсов).

Согласно предлагаемой методологии на уровне взаимодействия с пользователем разрабатываемая система проектируется по принципу GUI (графического интерфейса пользователя) и внутреннего логического разделения функционирования программы.

GUI спроектирован с использованием понятия «Форма». Именно Формы определяют набор элементов, которые позволяют заказчику просматривать данные, изменять их и информировать о принятых решениях в процессе определения требований к будущей информационной системе. Связь между Формами осуществляется через Функции.

Связь между отдельными частями системы, спроектированными с использованием Форм и Функций, осуществляется через точки входа и точки выхода.

ИС, спроектированная по представленной методологии, может быть представлена в виде последовательностей вызовов Форм, связанных между собой Функциями. Таким образом, формируется граф, представляющий собой дерево Форм и Функций.

Концепция ICRP предусматривает аспект тестирования. Интеграция технологий тестирования в жизненный цикл разработки программного обеспечения реализует создание ИС в полном соответствии с принципами методологии ее разработки.

Важным вопросом, который также обсуждается в работе, является структура и форма представления базы данных проекта. Предложена структура проектной базы данных, соответствующая этапам разработки системы с одной стороны, и с учетом целостности БД для корпорации в целом и целостности БД каждого участника команды разработчиков с другой стороны.

Рассматривая все этапы разработки ИС, акцент делается на этапе создания модели интерфейса и функционирования системы, где центральной фигурой является заказчик. Применение предложенной методологии выполнения этого этапа проектирования осуществляется с использованием разработанного и существующего инструментария: JBPM, FFT Designer and Converter.

III.                                    Заключение

Рассмотрены и изучены все этапы разработки ИС, некоторые из них – модифицированы, а на некоторых – сделан акцент. В результате детального изучения этих этапов предложена новая методология и программные решения для процесса создания распределенной информационной системы. Проведено обоснование целесообразности и преимуществ использования предложенного подхода и инструментария по сравнению со стандартными подходами и существующими инструментальными средствами.

Источник: Материалы Международной Крымской конференции «СВЧ-техника и телекоммуникационные технологии», 2006г. 

Оставить комментарий

микросхемы мощности Устройство импульсов питания пример приемника провода витков генератора выходе напряжение напряжения нагрузки радоэлектроника работы сигнал сигнала сигналов управления сопротивление усилитель усилителя усиления устройства схема теория транзистора транзисторов частоты