Globa L S, Chekmez A V, Kot T N National Technical University of Ukraine «ΚΡΙ» Kiev, 03056, Ukraine Ph:380-442417699, e-mail: gls@densoftcomua

Abstract-The paper is detailed description of Web-system interface prototype designing, its logical stages that form the integral and complete part of the whole Web-system, as the particular case of informational system (IS) designing The article includes the proposed methodology for IS development [1], some specific principles [2], that are typical for this sphere of scientific researches, software solutions, made as the result of real experiment and got results The designed software tools are also represented in the article

I                                      Introduction

Successful and productive work of both of the national and private enterprises is impossible without IS implementation in their functioning Requirements coordination, components interfaces and functionality setting appeared to be the key stage of the development process The further process development stages and successful completion of the whole development process is impossible without system interface prototype creation For that propose, quite widespread and convenient CASE-tools can used What is more some new decisions need to be found and software tools to be developed

Nowadays it’s impossible to imagine modern informational systems functioning, supported and realized by only one specific type of software tool Implementation of great variety of functions for the whole system functionality realization needs several software tools integration to the unified and specific software complex As the basis of IS software was taken network applications, as the most progressive, perspective and useful direction in the variety of application tools Modern, advanced and complex IS development make the demand for new generation software The development of such software tool makes the essence of the paper

II                                     Main Part

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

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 using Functions are system elements, in which data processing and/or decision making is realized The result of the made decision is either corresponding exit value or management passing on the corresponding path

The parts connection is realized by entry and exit points They are the sections, on which management passing between elements is done

The objects, used in the diagrams, which are the main adjectives of the proposed methodology, should be determined The first one is Entry point It is the rule of function call, fixing the set of function input parameters The second is Exit point It is the rule of function transfer activity, fixing the set of function output parameters And Access interface, which is a coordinated couple (entry point, exit point)

The informational system, built on this methodology, can be designed as connected with function calls forms sequence This sequence is shown in the graph form Such graph is forms and functions tree (FFT) FFT represents forms and functions interconnections and also system functioning process in the set of data move on the graph branches (Pic1)

Pic 1 Form and Function Tres

The technology means that already mentioned graphs are developed in the form of: form and functions (their code) sets, saved in the exact database tables, forms and functions parameters description, and forms and functions interconnections information

After the description of main objects of methodology, their interconnections and functioning principles, the stages of technical project development can be considered

Its first stage is system architecture development It includes structure and interface components development, functions settings, component technical requirements settings informational streams between main components settings components connections with each other 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 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 development process is related to exactly IS components interface and structure designing

The central figure in the represented development stage is Customer He revises and affirms 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 tool IS functioning prototype development It is to be developed

For proposed technology was created required development tools For creating FFT was created designing tool called «FFT Designer» «FFT Designer» is Java based application Main purpose of it is to create FFT, describe its structure of WEB-system and generate XML files from FFT, needed for creation of look and feel and functioning model

For demonstrating look and feel and functioning model of future system was developed special tool This tool allows showing customers model of future system Conceptual idea of this tool described at pic2

Pic 2 Demonstration scenario

This picture demonstrates how one step of demonstration works For demonstration we use common WEB browser such Microsoft Internet Explorer or other With help of WEB browser we connect to FFT Scenario Server and server return us page with accessible models We select needed model and send its ID to FFT Scenario Server, Server get proper XML file with scenario and return to browser first page of model Every page contains some buttons or links, but as address there are special IDs of exit points of this form When user clicks on some of links or buttons, browser sends that ID to FFT Scenario Server, by this ID server finds from XML scenario file next form for demonstration and sends it to browser Such process continues until scenario ends

In described process we didn’t use functions, because at this stage of development we need to demonstrate look and feel of future system

Function will be used at next step of development by programmers FFT help them better understand needs of customer and what programmers have to do Also FFT allows projects managers split work at small tasks and give them to different programming teams

As every theory it have to be checked at practice, so we tried to describe some system The investigation subject was WEB system for social protection management in MNS (Ministry of Emergency) and in regional state administrations

In that experiment we created forms and functions trees using our tools Then we created form pages and tried to demonstrate look and feel of system We have to say that this experiment lasted more that two month and was very useful for us During it we revised many things and changed some functionality of our tools Some ideas died as useless, new one appeared We still are in development and research process, but now we can surely say that we have some positive result and our work was not useless

III                                  Conclusion

The proposed methodology was realized in practice by new developed tools It provides the following advantages while Web-system development:

■            system look &amp feel and functioning model designing

■            possibility to create prototype of future system at early development stage, that will help to define clearly customers’ needs and avoid needless functions and products creation

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, p2, 2005, p17-24-29

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

[3]  http://wwwjbpmorg

ПРОЕКТУВАННЯ прототипів ІНТЕРФЕЙСУ WEB-СИСТЕМИ

Глоба Л С, Чекмез А В, Кот Т Н

1Чаціональний технічний університет України «ΚΠΙ4» м Київ, 03056, Україна тел :380-442417699 e-maii: gis@densoftcomua

Анотація – Стаття являє собою детальний опис процесу розробки прототипу інтерфейсу Web-системи У роботі запропонована методологія розробки інформаційних систем, програмні рішення, необхідні для роботи з запропонованої технологією

I Введення

Успішна робота як державних, так і приватних підприємств неможлива без впровадження інформаційних систем в їх інфраструктуру Визначення вимог до розроблюваних систем є ключовою стадією процесу розробки Саме цей етап визначає успішне завершення цілого процесу розробки Для цих цілей використовуються вельми поширені і зручні CASE-засоби Для якісного поліпшення процесу розробки були запропоновані інноваційні технологія та інструментарій

II                                    Основна частина

Для розробки прототипу майбутньої системи використовується підхід, в основі якого лежить уявлення обєктів в термінах форм і функцій, а їх взаємодії – у вигляді функціональних графів

Для використання цього підходу розроблені технологія та необхідний інструментарій Для тестування запропонованої технології, вона була застосована для розробки системи реальної предметної області

III                                   Висновок

в результаті експерименту був створений прототип системи, який дозволив продемонструвати можливості запропонованого підходу, а саме:

■ проектування інтерфейсу і функціональної моделі системи

■ можливість створення демонстраційного ролика, який дозволяє продемонструвати замовнику ще неопрацьовані систему, що в першу чергу дозволить вирішити проблему неточних або неправильних вимог

Джерело: Матеріали Міжнародної Кримської конференції «СВЧ-техніка і телекомунікаційні технології», 2006р