**DESIGN OF INFORMATION SYSTEMS-2. METHODOLOGIES AND TOOLS FOR DESIGNING INFORMATION SYSTEMS
Syllabus
Details of the discipline
Level of higher education | First (bachelor's) |
---|---|
Branch of knowledge | 12 Information technologies |
Specialty | 126 Information systems and technologies |
Educational program | Integrated information systems |
Discipline status | Normative |
Form of study | full-time (full-time / part-time) |
Year of preparation, semester | 4th year, spring semester |
The scope of discipline | 150 hours (36 hours - Lectures, 18 hours - Laboratory, 96 hours - VTS) |
Semester control / control measures | Exam / examination work |
Lessons schedule | http://rozklad.kpi.ua/Schedules/ScheduleGroupSelection.aspx |
Language of instruction | Ukrainian |
Information about the course leader / teachers | Lecturer: Doctor of Technical Sciences, Professor, Kornienko Bogdan Yaroslavovich, mob. +38 (096) 965-05-17 Laboratory: Art. off Yalanetsky Valeriy Anatoliyovych, mob. +38 (067) 750-08-87 |
Course placement | https://campus.kpi.ua |
Curriculum of the discipline
Description of the discipline, its purpose, subject of study and learning outcomes
**Description of the discipline.**This course introduces students to modern views on scientific and methodological foundations and standards in the field of information systems design. The course begins with an introduction to information systems (IS) and their key role in the successful operation of enterprises and organizations. Different types of IP, organizational requirements for their implementation and operation, development strategy, data and information management are considered; IS life cycle, knowledge needed by analysts, such as sociability, ability to analyze facts; IP components, feasibility and cost-effectiveness analysis; data flow diagram as a system analysis tool and CASE IP design tools. Popular IP tools are also discussed.
Subject of academic discipline: basic modern methodologies and methods of building and managing information systems, basic classes, types and categories of information systems, their functionality and scope, modern methodologies, methods, models and tools for creating and applying information systems of different types.
Interdisciplinary connections. Discipline Design of information systems-2. Methodologies and tools for designing information systems based on disciplines: Design of information systems-1. Features of information systems design,, Software development technologies, systems theory and systems analysis, Computer networks, Databases, Theory of Algorithms.
The purpose of the discipline. The aim of the discipline is to thoroughly acquaint students with the theoretical foundations of organization, operation and design of information systems (IS), mastering practical skills of using and creating IP and their components for various purposes, providing theoretical knowledge and practical skills of designing and maintaining information systems for various subjects.
The main tasks of the discipline
Knowledge:
essence and purpose of information systems;
design stages and requirements for the information systems design process;
standards for designing information systems and design documentation;
system approach to information systems design, topology and architecture of information systems;
structural, object-oriented and typical design technology;
data models and process models;
UML standard, information systems interface;
RAD-methodology, CASE-technology of creation and support of information systems, RUP technology, ARIS technology, pattern technology.
Skills:
identify and analyze IP requirements;
specify and document IP requirements;
design data models and process models;
design process models;
apply the UML standard;
- use methods of visual programming;
- to apply modern CASE-technologies of creation and support of IP.
Prerequisites and postrequisites of the discipline (place in the structural and logical scheme of education according to the relevant educational program)
Prerequisites: ability to apply knowledge in practical situations, skills in the use of information and communication technologies, the ability to search, process and analyze information from various sources, the ability to apply knowledge of the basic principles and methods of building algorithms and determining basic technological parameters.
Postrequisites: know the systemic foundations of the creation and use of information systems; basics of classification, typification and clustering of information systems; basic types, classes and categories of information systems; types and main classes of information technologies and their characteristics; basic methodologies and models of information systems research at the conceptual level and the level of the subject area; basics of architectural design of information systems and their CASE support systems; basic methodologies and methods of information systems management at the stages of their implementation and application; basics of information management.
After completing the discipline, students will be able to use knowledge of fundamental disciplines and mathematical apparatus for the implementation of professional knowledge and practical skills in solving problems of typification of information systems and information technology; determine the main architectural parameters of information systems based on the construction and analysis of information models of the subject area; apply modern software tools for modeling organizational and technical systems; to develop with the help of computer systems process analytical models of business systems and their information systems; to study the basic structures and characteristics of process models.
The content of the discipline
Lectures
Section 1. IP design tools
Section 2. Practice of UML application
Section 3. Structural analysis and design of IP
Section 4. Object-oriented analysis and design of IP
Laboratory classes
Object-oriented control program
Design of the controller and software
WEB-dispatching
Development of an automated operator's workstation in Trace Mode and its connection with a virtual controller
Interaction of the automated workplace of the operator with external databases
Training materials and resources
Basic literature
Vendrov AM Software design of economic information systems: Textbook. - 2nd ed., Reworked. and ext. - М .: Финансы и статистика, 2006. - 544 с.
Buch G. Object-oriented analysis and design with examples of applications in C ++ - M .: "Binom", St. Petersburg: "Nevsky dialect", 1999. - 560 p.
Butch G., Rambo J., Jacobson A. The language of UML. User's guide - M .: DMK, 2000. - 432 p.
Gamma E., Helm R., Johnson R., Vlissides J. Object-oriented design techniques. Design patterns - St. Petersburg: "Peter", 2001.- 368 p.
Alexandrov DV Information management tools. CASE-technologies and distributed information systems / D.V. Александров. - М .: Финансы и статистика, 2011. - 224 с.
Ananiev OM Information systems and technologies in commercial activity: textbook / О.М. Ananiev, VM Bilyk, Ya.A. Goncharuk. - Lviv: Novyi Svit, 2006. - 583 p.
Glivenko SV Information systems in management: textbook. way. / SV Glivenko, EV Lapin, OO Pavlenko, SS Slabko, VM Swan. - Sumy: University Book, 2005. - 407 p.
Grekul VI Information systems design: Course of lectures. Uch. allowance / V.I. Grecul, G.N. Денищенко, Н.Л. Korovkin. - M .: Internet University of Information Technologies, 2005. - 304 p.
Solovyov IV Design of information systems / IV Solovyov, AA Majors. - М .: Академический Проект, 2009. - 400 с.
Gvozdeva TV Design of information systems / T.V. Гвоздева, Б.А. Ballod. - Rostov-on-Don: Phoenix, 2009. - 512 p.
Pavlova EA Technologies of development of modern information systems on the Microsoft .NET platform / Е.А. Pavlova. - M .: Binom, 2009. - 112p.
Methodical instructions for laboratory work in the discipline "Information Systems Design" credit module "Features of information systems design" for students majoring in 126 "Information Systems and Technologies" [Text] / Compiled by: VA Yalanetsky. - K .: NTUU "KPI them. Igor Sikorsky », 2020. - 79 p.
Supporting literature
Lelek A. Analysis and design of information systems using UML 2.0 / A. Lelek. - М .: Вильямс, 2008. - 816 с.
Fedotova DE CASE technologies. Workshop / D.E. Fedotova, Yu.D. Semenov, KN Чижик. - M .: Hot Line-Telecom, 2005. - 160 p.
Frimer E. Patterns of design / E. Freemason. - СПб .: Питер, 2011. - 656 с.
Kent Beck, Extreme Programming, Peter Publishing House · 2002 · 224 p.
Leszek A. Matsyashek, Requirements analysis and system design, Development of information systems using UML: Per. From English - Moscow: Williams Publishing House, 2002 -432 p.
Constantide L., Lockwood L. Software development. - St. Petersburg: Peter, 2004. - 592 p.
Boggs W., Boggs M. UML and Rational Rose - M .: "LORI", 2000. - 582 p.
Educational content
Methods of mastering the discipline (educational component)
Lectures
№ s / n | Title of the lecture topic and list of main questions (list of didactic tools, references to literature and tasks on VTS) |
---|---|
1 | Topic 1.1. IP design tools. Lecture 1. Purpose, tasks, functions, classification IP design tools. Requirements for design tools. Factors influencing the choice of design tools. Criteria for selecting design tools. Manual design tools. Computer aided design tools. Types of computer-aided design tools: supporting designinformation processing operations that support the design of individual components of the project, supporting the design of project sections, supporting the development of the project at the stages and stages of the design process. Literature: [1, p.5-31; 3, p.3… 10; 4, p.10… 42.] Tasks on VTS. Purpose and classification of IP. |
2 | Lecture 2. Groups of design tools. Traditional programming systems; tools for creating file server applications; client-server application development tools; office automation and document management tools; Internet / Intranet application development tools; design automation tools (CASE-technologies). Local, small, medium and large integrated CASE-tools. Classification of CASE-tools by functionality: tools for analysis and design of the organization and the designed system, tools for designing databases, requirements management tools, documentation tools, testing tools, project management tools, reverse engineering tools. Application of CASE-technologies: advantages and disadvantages. Introduction of CASE-technologies. Literature: [1, p.5-31; 3, p. 16… 26; 4, p.10… 42.] Tasks on VTS. Purpose and classification of IP. |
3 | Topic 1.2. Data models, process models and their design with ERwin. Lecture 3.Data model. Data model levels. External (conceptual) data model. Logical data model. Physical data model. Entity-relationship diagram (ERD). IDEFI data modeling method. CASE data modeling tool ERwin Process Modeler. Display the data model in the Erwin tool. Creating a logical data model: levels of the logical model; essences and attributes; communication; types of entities and hierarchy of inheritance; keys; data normalization; domains. Creating a physical data model: validation rules and default values; trigger indices and stored procedures; calculating the size of the database. Direct and reverse design. Generate client code using ERwin. Advanced attributes. Code generation. Creating reports. Generation of dictionaries. Literature: [1, p.5-31; 3, p.3… 10; 4, p.10… 42.] Tasks on VTS. Functions and general requirements for IP. |
4 | Lecture 4. CASE process modeling tool ERwin Process Modeler (BPwin). Principles of IDEF0 model construction: context diagram, subject of modeling, purpose and point of view. IDEF0 diagrams: context diagram, decomposition diagrams, node tree diagrams. Works. Arrows. Tunneling of arrows. Numbering of works and diagrams. Chart frame. Merger and split models. Creating reports. Literature: [1, p.5-31; 3, p.3… 10; 4, p.10… 42.] Tasks on VTS. The structure of information systems. |
5 | Topic 2.1. UML standard: static and dynamic charts Lecture 5. Practice of UML application. History of UML creation: UML 1.X UML 2.X. Definition and purpose of UML language. UML notation elements. Relationship of UML notation, methodology and tools. Classification of models in UML 2.X. Recommendations for charting in UML notation. UML language extension mechanisms. Literature: [1, p.5-31; 3, p.3… 10; 4, p.10… 42.] Tasks on VTS. Characteristics of information systems. |
6 | Lecture 6. Structural (static) diagrams. Class diagrams. Diagrams of objects. Component diagrams. Deployment charts. Component structure diagrams. Package diagrams. Diagrams of (dynamic) behavior. Diagram of usage options. Activity charts. State diagram. Interaction diagram: sequence diagram, interaction overview diagram, communication diagram, synchronization diagram. Purpose and composition of the diagram of use cases. Rules and guidelines for developing usage diagrams. Literature: [1, p. 61-76; 3, p. 42… 53; 4, p. 388 ... 402; 6, p.219..234.] Tasks on VTS. Ensuring the reliability of information systems. |
7 | Topic 2.2. Object-oriented modeling. Lecture 7. The concept and terminology of object-oriented approach. Models of requirements of OO-approach. UML-standard OO modeling technology. Diagrams of use cases -precedents - (use case diagrams - UCD). Elements and rules of construction of UCD. Descriptions of precedents. Literature: [2, p.52-87; 4, p. 120-170.] Tasks for VTS.Trace requirements. Functional decomposition of IP. |
8 | Lecture 8. Basic diagrams object-oriented approach. Activity Diagram-Activity Diagram. Defining inputs and outputs - System sequence diagram (SSD). Development of the system sequence diagram (System Sequence). Interaction diagrams: sequence diagrams and cooperation diagrams. Class diagram. Class and class attributes. Visibility of attributes. Variable, method, constructor. Stereotypes of classes. Connections, dependencies. Class interfaces. Identification of object behavior. State Machine Diagram. Literature: [7, p. 38-55. ] Tasks for VTS.Methods of creating requirements. Defining the image and boundaries of the project. |
9 | Lecture 9. Modular control work All previous material is submitted for control work, which includes the basic tools of design technology and methodology for creating IP. Tasks include theoretical and practical parts, as well as additional tasks, in case of timely completion of the main issues. Tasks for VTS. Repeat the material of 1-8 lectures. |
10 | Topic 3.1. Design of information systems interfaces. Lecture 10. The concept of user interface, its purpose. Interface requirements. Standardization of interfaces. Types of interfaces. Command interface. Graphical interface. Desktop. Windows. Desktop folders. Widgets.UI creation tools. Transmission of information in a visual way. Menu bar and toolbar. Use of color, sound, animation in the interface. Drag and Drop method. Window layout and design. Object approach to interface design. Graphical interface components. Choice of dialogue structure. Development of a dialogue scenario. User interaction with the application. General rules of interaction with objects. Shipment and object creation operations. Literature: [2, p. 88-127; 3, p. 56-148; 4, p. 170-186; 5, p. 56-90, 107-110; 7, p. 137-188. ] Tasks for VTS. Information system life cycle. |
11 | Lecture 11. The process of developing a user interface. Stages of user interface development. Collective approach to development. Iterative nature of development. Stages of development: collection and analysis of information coming from users, development of user interface; construction of user interface; confirmation of the quality of the user interface. Literature: [3, p.118 ... 135; 4, p.182 ... 194] Tasks for VTS. Information system design methodology. |
12 | Topic 3.2. RAD-methodology and CASE-technology of creation and maintenance of IP. Lecture 12. Flexible IP development technologies. Prerequisites for the emergence of RAD-methodology (Rapid Application Development). The main features of RAD-methodology, object-oriented approach to creating applications, the use of visual programming tools, event programming. Limitations of RAD methodology. Factors influencing the time block of development. The role of the user in application development. Phases of the RAD life cycle model: requirements analysis and planning phase; design phase; construction phase; implementation phase. Advantages of the RAD model. Disadvantages of the RAD model. Scope of the RAD model. SCRUM - methodology for managing IP development. CASE-technologies: definition and general characteristics, purpose. Advantages and opportunities of CASE-technology. Comparison of traditional and CASE-technology. Literature: [6, p.226 ... 239; 7, pp.349-398.] Tasks for VTS. Organization of information systems creation. |
13 | Lecture 13. RUP technology. General characteristics of RUP technology. Basic principles of RUP technology. Iterative development. Process management based on usage precedents. Focus on architecture. Dynamic structure: project start (Inception), elaboration (Elaboration), construction (Construction), transfer (Transition). Static structure. Main disciplines: subject area modeling (Business Modeling), requirements definition (Requirements), analysis and design (Analysis and Design), implementation (Implementation), testing (Test), deployment (Deployment). Ancillary disciplines: Configuration and Change Management, Project Management, Project Environment. IBM Rational tools that support RUP technology. Literature: [3, p.30… 36; 4, p. 6… 70, 433 ... 448.] Tasks for VTS. IP design tools. |
14 | Lecture 14. ARIS technology. ARIS methodology. The basic concept and principles of methodology. Advantages of ARIS methodology. The main components of the ARIS architecture. Types of representation (types of models): organizational models, functional models, information models (data models), process models (control), input / output models. Relationship of representation types in ARIS. Levels of description of the modeled object in ARIS: definition of requirements, project specification, description of implementation. Literature: [3, p.30… 36; 4, p. 6… 70, 433 ... 448.] Tasks for VTS. Typical design of information systems. |
15 | Topic 4.1. Pattern technology. Lecture 15. Purpose of the design model. Scheme of the "Design" process. Purpose and composition of the class diagram. Rules and recommendations for building a class diagram. The concept of pattern. Design pattern. Pattern system, pattern language. Pattern description templates. Template elements. Types of patterns by type of tasks. Analysis patterns. Architectural patterns. Design patterns in the narrow sense. Idioms. Pattern organizations. Process patterns. Literature: [3, p. 15… 22; 4, p. 6… 50, 420 ... 434.] Tasks for VTS. Pattern technology. |
16 | Lecture 16. Classification of patterns according to the level of description of the IP. Class / object design level patterns: structural patterns, class / object design patterns, behavior patterns, generating patterns. System architecture level patterns. Structural patterns. Control patterns. Patterns of corporate IP integration. Structural integration patterns. Patterns by methods of integration. Integration patterns by type of data exchange. Literature: [3, p.23… 36; 4, p. 51… 70, 433 ... 448.] Tasks for VTS. Object-oriented design technology. |
17 | Lecture 17. Modular control work All preliminary material, including standards and stages of IP design, is submitted for control work. Tasks for VTS. Repeat the material of 10-16 lectures. |
18 | Topic 4.2. Structural and object-oriented design technology. Lecture 18. IP reengineering. Prerequisites for the emergence of a combined process-oriented approach: process approach to management, the shortcomings of traditional approaches, the development of information technology. The essence of process-oriented design. Terminology of the process approach. Process. Basic and auxiliary processes. Master of the process. Input and output of the process. Process resources. Limits of the process. Process interface. Concepts of modern approaches to management and the purpose of the organization. The concept of business process. Stages of changing the management system of the organization: mission definition, business process reengineering. The purpose of reengineering. The concept of engineering. Stages of business process reengineering. Identification of business processes. Reverse engineering. Development of models of a new organization of business processes. Implementation of the business process reengineering project. Implementation of business process reengineering project. Literature: [3, p.30… 36; 4, p. 6… 70, 433 ... 448.] Tasks for VTS. IP reengineering. |
**
**
Laboratory classes
№ | Name of laboratory work | Number of aud. hours |
---|---|---|
1 | Laboratory work 1. Object-oriented control program Get a general idea of basics of object-oriented control program. To master a technique of development of the program in SFC language on an example of the automated control system for object of automation. Literature: [12, p. 19] |
4 |
2 | Laboratory work 2. Design of the controller and software Get acquainted with the addition process controller and software to the automated control system. Write an algorithm for the operation of an automated control system with a controller and a software task. Modify the control program of the technological scheme. Literature: [12, p. 35] |
4 |
3 | Laboratory work 3. WEB-dispatching To study the basic provisions and principles of development of software model of object of automation with WEB-dispatching. Get acquainted with the basic provisions and algorithm for creating a WEB-interface. Master the methodology and sequence of development of a virtual object of automation. Literature: [5, p. 42] |
4 |
4 | Laboratory work 4. Development of the automated workplace of the operator in Trace Mode and its communication with the virtual controller To study the main functions and capabilities of Trace Mode on a practical example of an automated control system. Get acquainted with the technology of the virtual controller. Master the technique and sequence of configuring and configuring a virtual controller. Literature: [5, p. 53] |
4 |
5 | Laboratory work 5. Interaction of the automated workplace of the operator with external databases Examine the built-in tools of the automated operator's workplace to create screens of the human-machine interface of the local operator's place. Master the method of developing the interaction of the automated workplace of the operator with external databases. Literature: [5, p. 68] |
2 |
Independent work of a student / graduate student
|
The name of the topic submitted for self-study | Number of hours of VTS |
---|---|---|
1 | Purpose and classification of IP. | 6 |
2 | Functions and general requirements for IP. | 6 |
3 | The structure of information systems. | 6 |
4 | Characteristics of information systems. | 6 |
5 | Ensuring the reliability of information systems. | 6 |
6 | UML standard: static and dynamic charts. | 6 |
7 | Methods and means of research of the object of automation | 6 |
8 | Information system life cycle. | 6 |
9 | Information system design methodology. | 6 |
10 | Organization of information systems creation. | 6 |
11 | IP design tools. | 6 |
12 | Typical design of information systems. | 6 |
13 | Pattern technology. | 6 |
14 | Object-oriented design technology. | 6 |
15 | IP reengineering. | 6 |
16 | Preparation for the exam for all module material. | 6 |
Policy and control
Course policy (educational component)
The system of requirements for students:
attending lectures and laboratory classes is a mandatory component of studying the material;
at the lecture the teacher uses his own presentation material; uses Google Drive to teach the material of the current lecture, additional resources, laboratory work, etc .; the teacher opens access to a certain directory of the Google disk for downloading electronic laboratory reports and responses to MCR;
at lectures it is forbidden to distract the teacher from teaching the material, all questions, clarifications, etc. students ask at the end of the lecture in the allotted time;
laboratory works are defended in two stages - the first stage: students perform tasks for admission to the defense of laboratory work; the second stage - protection of laboratory work. Points for laboratory work are taken into account only in the presence of an electronic report;
modular test work is written in lectures without the use of aids (mobile phones, tablets, etc.); the result is sent in a file to the appropriate directory of Google Drive;
incentive points are awarded for: active participation in lectures; participation in faculty and institute Olympiads in academic disciplines, participation in competitions of works, preparation of reviews of scientific works; presentations on one of the topics of the VTS discipline, etc. Number of encouraged points for more than 10.
Types of control and rating system for evaluation of learning outcomes (RSO)
The student's rating in the discipline consists of points that he receives for:
performance and protection of 5 laboratory works;
performance of 2 modular control works (MCR).
Rating points system and evaluation criteria
Laboratory works:
"perfectly", a complete answer to the question during the defense (not less than 90% of the required information) and a properly executed protocol for laboratory work - 8 points;
"Good", a sufficiently complete answer to the question during the defense (not less than 75% of the required information) and a properly executed protocol for laboratory work - 7 points;
"Satisfactory", incomplete answer to the question during the defense (not less than 60% of the required information), minor errors and a properly executed protocol for laboratory work - 5 points;
"Unsatisfactory", unsatisfactory answer and / or not properly executed protocol for laboratory work - 0 points.
Modular tests:
"perfectly", complete answer (not less than 90% of the required information) –5 points;
"fine", a sufficiently complete answer (not less than 75% of the required information), or a complete answer with minor errors - 4 points;
"satisfactorily", incomplete answer (but not less than 60% of the required information) and minor errors - 3 points;
"unsatisfactorily", unsatisfactory answer (incorrect solution of the problem), requires mandatory rewriting at the end of the semester - 0 points.
Encouragement points
for active work at lectures 1 point
Intersessional certification
According to the results of educational work for the first 7 weeks, the maximum possible number of points is 20 points. At the first attestation (8th week) the student receives "credited" if his current rating is not less than 10 points.
According to the results of 13 weeks of training, the maximum possible number of points is 32 points. At the second attestation (14th week) the student receives "credited" if his current rating is not less than 16 points.
The maximum amount weight points of control measures during the semester is:
R = 5 * rlab + 2 * rmkr = 5 * 8 + 2 * 5 = 50.
Exam:
The condition for admission to the exam is enrollment in all laboratory work, writing both modular tests and a starting rating of at least 17 points.
At the exam, students perform a written test. Each ticket contains two theoretical questions (tasks). The list of theoretical questions is given in appendix 1. Each question (task) is estimated in 25 points.
Question evaluation system:
"Excellent", complete answer, not less than 90% of the required information, performed in accordance with the requirements for the level of "skills" (complete, error-free solution of the problem) - 23-25 points;
"Good", a sufficiently complete answer, not less than 75% of the required information, which is performed in accordance with the requirements for the level of skills or there are minor inaccuracies (complete problem solving with minor inaccuracies) - 20-22 points;
"Satisfactory", incomplete answer, not less than 60% of the required information, performed in accordance with the requirements for the "stereotypical" level and some errors (the task is performed with certain shortcomings) - 15-19 points;
"Unsatisfactory", the answer does not meet the conditions for "satisfactory" - 0-4 points.
The sum of starting points and points for the examination test is transferred to the examination grade according to the table:
Table 1. Translation of rating points to grades on a university scale
Bali | Rating |
---|---|
95-100 | perfectly |
85-94 | very good |
75-84 | fine |
65-74 | satisfactorily |
60-64 | enough |
Less than 60 | unsatisfactorily |
Failure to perform seven laboratory works and perform MCR on the assessment of "unsatisfactory" | not allowed |
Additional information on the discipline (educational component)
the list of theoretical questions submitted for semester control is given in Appendix 1;
at the beginning of the semester the teacher analyzes the existing courses on the subject of the discipline and offers students to take the appropriate free courses. After the student receives a certificate of distance or online courses on the subject, the teacher closes the relevant part of the course (laboratory or lectures) by prior arrangement with the group.
Work program of the discipline (Syllabus):
Folded Professor, Doctor of Technical Sciences, Bogdan Yaroslavovich Kornienko
Approved Department of AUTS (protocol № 1 from 27.08.2020)
Agreed Methodical commission of the faculty[1] (Minutes № 1 dated 02.09.2020)
Appendix 1
List of theoretical questions for the exam
Requirements for IP design tools.
Classification of IP design tools.
CASE design tools.
Data modeling.
Designing a data model in Erwin.
Process modeling.
Design of BPwin process model.
Purpose and development of a unified modeling language.
UML structure and notation.
Types of UML charts.
Diagram of usage options.
Purpose of RPTwin.
RPTwin tool environment.
Using RPTwin formulas.
Design of information systems interfaces
Concepts, purpose and requirements for the user interface.
Standardization of interfaces.
UI creation tools.
The process of developing a user interface.
RAD-methodology and CASE-technology of IP creation and maintenance
Flexible methodologies for IP development.
RAD-methodology for creating and maintaining IP.
SCRUM - methodology for managing IP development.
CASE-technology of creation and support of IP.
RUP technology. ARIS technology
Characteristics and principles of RUP technology.
Dynamic and static structure of RUP.
IBM Rational tools that support RUP technology.
ARIS technology: concept, principles, components of architecture.
Pattern technology
Design model in a unified process.
Class diagram.
Concepts, language and patterns of pattern description.
Types of patterns.
IP reengineering
Prerequisites and the essence of the process-oriented approach.
Terminology of the process approach.
Stages of business process reengineering
[1] Methodical council of the university - for general university disciplines.