STREAMLINE BUSINESS PROCESSES THROUGH THE SIMULATION AND OPTIMIZATION
Many organizations have learned to model their business processes, however, the introduction of process model in managing the organization did not contribute to its efficient operation and improve economic performance. The essence of the procedure lies in the fact that the modeled processes is not enough to operate smoothly. Prior to the implementation process model is needed its simulation and optimization. Article on the example of the “Business Case” business process “development of mobile networks,” shows how to do it. (Article delivered and published on: 9th International Conference on Perspectives in Business Informatics Research (October 2010), Rostock University – Germany).
SIMULATION AND OPTIMIZATION OF SYSTEM PROCESSES IN AN INTEGRATED IT ENVIRONMENT
Many organizations are building complex integrated IT environment that are constantly changing due to the changing market situation (introduction of new products and services) and competition. The cost of increased complexity of these environments becomes an important burden on the organization. Article based on a sample of integrated IT environment in the TELCO shows how to model and optimize the environment before it changes. (Article delivered and published on the symposium: Modeling and Computer Simulation in Technique, which was held at the School of Computer Science in Lodz, April 2010).
QUALITY MANAGEMENT IN PROJECTS THROUGH THE CONSTRUCTION OF REFERENCE MODELS
The standard project management methodologies such as Prince 2, PMBoK quality management is determined by defining the quality requirements for product manufacturing cycle. In complex production cycles, which produced the documents, software products and other (e.g. reports) managing quality requires the introduction of appropriate procedures. Process reference models for such procedures for the case of systems of type “Business Intelligence” reports the article below. (Article delivered and published on: 8th International Conference on Perspectives in Business Informatics Research (October 2009), Kristianstad University – Sweden).
MANAGEMENT OF THE SYSTEM REQUIREMENTS FOR THE IMPLEMENTATION OF READY-MADE SOLUTIONS
Business needs related to the introduction of a new IT solution to materialize through the construction of the model(s) the requirements for a solution. Standard techniques of SysML and UML use cases give us a method of constructing such a model, but do not provide methods or techniques to choose the best solution in the case, select the solution with ready-made functionality. Such techniques are given in this article. (Article delivered and published on: 16th International Conference on Systems Science (September 2007), Wroclaw University of Technology, Poland.
CONSTRUCTION OF MODEL REQUIREMENTS FOR SYSTEMS IN THE PUBLIC SECTOR FOR REGIONAL SOLUTIONS (MEDICAL INFORMATION SYSTEMS)
Build regional systems in the public sector especially those based on data warehouses use a variety of data sources and have a complex architecture. Article gives an example of the construction requirements and architecture for Regional Medical Information System (RSIM), built for the Lodz Region and three years of work experience as an expert author on the client. (Article delivered and published on the conference: TIAPiSZ’09 “Information technology in public administration and health care” (December 2009), SGH, Warsaw).
ENTERPRISE ARCHITECTURE – BUILDING OBJECTIVES FOR THE IT ARCHITECTURE AND BUSINESS ARCHITECTURE TO SUPPORT BUSINESS STRATEGIC MANAGEMENT
Enterprise architecture is becoming a central function of business and IT. Building enterprise architecture requires organizations to develop a set of principles and guidelines for both parts of the business and IT architecture. Construction should begin by the TOGAF ADM to determine the so-called Architecture Vision, which at the beginning you must determine the organization’s business objectives and IT environment objectives and their meters. The success of projects is closely bound with defining business and architectural goals, and their metrics. How to do this is given in the article below. (Article delivered and published on the conference: TIAPiSZ’10 “Information technology in public administration and health care “(December 2010), SGH, Warsaw).
ENTERPRISE ARCHITECTURE – A METAMODEL FOR QUALITY MANAGEMENT OF ARCHITECTURE
In a paper published by the authors in the publishing house Springer (Information and Software Technologies, Proc Int Conf of. ICIST 2013, ISBN 978-3-642-41946) provides a framework to identify, manage, simulate and optimize the quality of enterprise architecture based on defined by the authors 2 meta-models: classes and processes for quality management enterprise architecture. The second of these (meta process model) quality management developed in BPMN has undergone simulation and optimization using ARIS Business Process Simulator. The results of this simulation and optimization are presented in the article. The presented research method developed by the authors and the results relate to, and are a creative extension of the following ISO standards:
- Software Engineering – Metamodel for Development Methodologies – ISO/IEC 24744;
- Systems and Software Engineering – Software Life Cycle Processes – ISO/IEC 12207;
- Systems and software engineering – Architecture description – ISO/IEC 42010; oraz znanych metodologii: [ZACHMAN FRAMEWORK] A Framework for Information Systems Architecture. – Zachman, J. A. oraz [TOGAF 9.0] The Open Group Architecture.
INTEGRATION OF THE WATERFALL METHODOLOGY AND THE AGILE/SCRUM METHODOLOGY IN THE MANAGEMENT LAYER AND IN THE ARCHITECTURE LAYER OF IT SYSTEMS
The paper presents formal description an definition of so called Agile- Waterfall (hybrid) approach for adopting both methodologies essentially utilizing the best properities of both. One methodology may not be the only solution for all projects. The hybrid methodology requires a formal definition in the management layer and in the development layer. Definitions were given in the form of metamodels for the management and production layers, respectively. This is the purpose of this work. The work resulted from the needs of the market because the recipients demand on one hand to document the requirements and architecture of the application (Waterfall) and at the same time an effective iterative mode of its implementation (Scrum/Agile). The main aim of the hybrid methodology is to enable teams to define requirements and adapt to changing requirements through continuous feedback and delivery. The hybrid method retains the clarity and tracking system of Waterfall method, while embracing the adaptability and flexibility of Agile.
On the Integration of the Waterfall Methodology with the SCRUM Methodology at the Project Management Area and at the Area of High-Level and Low-level of Systems Architecture