INFORMATION SYSTEMS IN MANAGEMENT IV

ling categories of UML language. The deft reaction to changes is their featurewhich results from good communication in the team and the whole processadaptation to changeable conditions. Their most important product is working andtested system code.The agile methodology must be reinforced in the sphere of practice. Largescaleundertakings of information technology, which are connected with largecomplex systems (developed and modified for many years), require such methodologyof project running which accurately reflects and defines every process elementof software creation (such as RUP methodology). Using formal (hard)methodology in this case is necessary just because of the scale and potential durationof the project. It is to provide security for the undertaking and achieveintended aims. It can be thought with a real change that in the near future the professionallevel will increase among proponents of light methodology. [Bartyzel M.]It will handle great undertakings provided that they provide a higher control levelover work on the project in every moment of its duration without losing its agileactivity.3. FUNCTIONALITY COMPARISION OF CHOSEN CASE TOOLSUML language has got considerable support in a form of CASE tools[Malina W., Szwoch M.] which provide help in modelling and creating suitableproject documentation. Among the most important functions that prove the advancedposition of a particular CASE tool and provide a suitable control levelwhich meets user’s requirements in the project we may distinguish: data dictionary(repository of metadata with the management system), graphic notations editor(diagrams editor), correctness control module (searching mistakes in diagrams andrepositories), project quality evaluation module (e.g. complexity scale evaluationand evaluation of connections between project elements), generators of reports andtechnical documentation, source code generators, user’s interface designing module,reverse engineering module (possibility of displaying data dictionary or diagramson the basis of the source code or data base structure), import and exportmodule of data as well as group work management module. [Chmielarz W.][Bednarczyk M.]Introducing 2.0 version of UML language caused the necessity of developingCASE tools. Currently many programs support this version, however, there is awide range of solutions, especially non-commercial, which stayed in the standard1.4 UML.In the comparison there were qualified solutions available and spread in thelocal (academic) environment. Among commercial CASE tools there were chosenthe following: Enterprise Architect (version 7.1) enterprises Sparx System[Sparx System, Enterprise…], Poseidon for UML (version 6.0.2) enterprises9