DESIGN OF INFORMATION SYSTEMS-1. FEATURES OF INFORMATION SYSTEMS DESIGN
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, autumn semester |
The scope of discipline | 90 hours (36 hours - Lectures, 18 hours - Laboratory, 36 hours - VTS) |
Semester control / control measures | Test |
Lessons schedule | http://rozklad.kpi.ua |
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-1. Features of information systems design based on disciplines: Software Development Technology, 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. Basic concepts of IP design technology
Section 2. Methodologies and technologies of IP development
Section 3. Technologies for creating IP
Section 4. Project management in IP development
Section 5. IP design tools
Laboratory classes
Programming of the automated control system of language of consecutive operations of SFC
Programming of an automated control system with the addition of feedback
Creating a script for the automation object simulator
Application of the MODBUS protocol for communication of the virtual controller with object of automation
Development of a local human-machine interface
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.2 | Topic 1.1. The structure and content of the course. RSO. Topic 1.2. General Information. The concept of IP. Lecture 1.2. Purpose, tasks, functions, classification of IP. The concept of information system, its purpose. Tasks and functions of IP. Regulations for the operation of IP. Manual, automated, automatic ICs. Classification of IP: on the basis of structured tasks, on the basis of functionality, levels of management and staff qualifications. Documentary and factual IP. IP depending on the scope, by types of management processes, by cost. Corporate IP. Evolution of corporate information systems. Standards of corporate IP. Literature: [1, p.5-31; 3, p.3… 10; 4, p.10… 42.] Tasks on VTS. Tasks and functions of corporate information systems. Standards of corporate IP. |
3 | Topic 1.3. Architectures and technologies for creating IP. Lecture 3. Information processing systems Information processing cycle. Attributes of information. Types of information systems. Operations processing systems. Management information systems. Decision support systems. Group decision support systems. Information systems of the head. Expert systems. Classification of architectures of economic information processing systems, characteristics and areas of promising use. Options for decisions made in organizations. Data warehouse and principles of its organization. IP architecture. Typical information system files. Types of data processing: batch, online batch, online. 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. Methodologies for creating IP. Reasons for changing IP in organizations. PIECES is the basis for identifying a business problem. A classic approach to solving a problem situation. Advantages of methodology. Methodologies based on modeling. Structural analysis and design. Infotenics. Object-oriented analysis and design. Rapid Application Development (RAD). Purchase of ready-made software. Literature: [1, p.5-31; 3, p.3… 10; 4, p.10… 42.] Tasks on VTS. The structure of information systems. |
5 | Lecture 5. Principles and stages of IP creation. Principles of system development. The classic method of a waterfall. Evolutionary model. Spiral model. Characteristics of the "difficult process". Principles of rapid development. Principles of Agile methodology. The concept of Extreme Programming (XP). SCRUM-methodology. Principles and stages of RUP methodology. Literature: [1, p.5-31; 3, p.3… 10; 4, p.10… 42.] Tasks on VTS. Characteristics of information systems. |
6 | Topic 1.4. IP requirements. Lecture 6. Functions and requirements for IP. Defining the requirement. Reasons for the complexity of requirements development. Methodologies and standards governing the work with the requirements: IEEE, RUP. Classification of requirements. Product and process requirements. Requirement levels: business requirements, user requirements, functional requirements. System requirements and software requirements. Functional, non-functional requirements and product characteristics. Properties of requirements: completeness, clarity, correctness, consistency, verifiability, necessity, usefulness in operation, feasibility, modification, traceability, ordering in importance and stability, the presence of quantitative metrics. 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 | Lecture 7. IP requirements management. Requirements management processes. Decomposition of the requirements creation process in SWEBOK, RUP, MSF. Identification of requirements. Sources of requirements. Means of identifying requirements: interviews, questionnaires, observations, self-identification of requirements, joint seminars, prototyping. Requirements analysis, business analysis. Methodologies and models of business analysis. Requirements for IP architecture. Relationship of requirements analysis with other RUP workflows Literature: [2, p.52-87; 4, p. 120-170.] Tasks for VTS.Trace requirements. Functional decomposition of IP. |
8 | Lecture 8. Basic technologies for the implementation of requirements. Requirements management levels: no requirements, requirements are documented, requirements are organized, requirements are structured, requirements are traced, requirements are integrated. Requirements management support tools. Requirements management processes in Rational RequisitePro: requirements management plan development, requirements collection, glossary and concept development, Use Cases, add-ons / specifications, Test Cases creation, Use Cases creation, Test Cases with additional specification, system design. Structure of Rational Requi-sitePro. Types of requirements, types of types of requirements; attributes of requirements types and their values, dependencies between requirements in Rational RequisitePro. Document templates. RequisitePro. 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 concepts 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 2.1. Standards of IP design and design documentation. Lecture 10. The concept of standardization, certification. Types of standards. Advantages of standardization in the IT sphere. Organizations-developers of international standards in the field of software engineering. Basic standards in the field of software engineering. Definition of the concept of life cycle. Life cycle of the design object, its state. Features of the IP life cycle. Stages of lifeIP cycle. IP life cycle cycles. ISO 12207 standard (DSTU 3918-1999): basic definitions, structure of the IP life cycle, processes of the IP life cycle. ISO 15504 standard, its connection with ISO 12207. Standards of maturity of the organization's capabilities. SMM model. CMMI model. Composition and content of design stages. 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. Standards of project documentation. Documentation of requirements in RUP. Purpose and content of documents "Vision", "Specification of use cases", "Additional specification of requirements". Composition and content of project documentation in accordance with GOST 34. Documentation of requirements based on IEEE Standard 830-1998. Documentation of requirements in MSF. Documentation of requirements on the basis of GOST 34.602-89 "Terms of reference for the creation of an automated system". Literature: [3, p.118 ... 135; 4, p.182 ... 194] Tasks for VTS. Information system design methodology. |
12 | Topic 2.1. System approach to IP design Lecture 12. IP design from the standpoint of a systems approach. Information system from the point of view of system analysis: integrity, purposefulness, integration properties, identification of functions and structure, informal methods of description. Principles of a systematic approach to IP design. Decomposition of IP. Types of elements used in the analysis of IP. Functional components of IP. Subject, functional and problem principles of allocation of functional subsystems. IC support components. Composition and structure of information support. Extra-machine and machine information support. Technical support. Software. Linguistic support. Technological support. Organizational components of IP. Organizational support. Ergonomic support. Legal support. Literature: [6, p.226 ... 239; 7, pp.349-398.] Tasks for VTS. Organization of information systems creation. |
13 | Lecture 13. Stages of IP design and analysis The work performed at the stage of preliminary analysis. Information service request. The content and objectives of the preliminary analysis stage. Identification and formulation of the problem. The concept of system scale. Preliminary analysis of business processes. Models of analysis of object-oriented approach. Identification of system classes and methods of their detection. Detection of system limitations. Planning the next stages of the project. Literature: [3, p.30… 36; 4, p. 6… 70, 433 ... 448.] Tasks for VTS. IP design tools. |
14 | Topic 2.2. IP topologies and client-server IP architecture. Lecture 14. The concept of system topology. Information topology, IP topology. Types of IP topology: "point - point", "hub - needle". Information system architecture. Basic definitions. Application elements. Software interface (API). Basic functions of IP. User interface. Business logic. Data management. History of IP architecture development. Centralized architecture. A personal computer. File server architecture. Client-server architecture. Three-tier client-server. N-level client-server. Enterprise architecture and service-oriented architecture (SOA) IS. SOA standards. SOA levels at the enterprise. Literature: [3, p.30… 36; 4, p. 6… 70, 433 ... 448.] Tasks for VTS. IP topologies and client-server IP architecture. |
15 | Lecture 15. Typical IP design. The concept of a standard design solution (TPD). Types of typical design methods. The essence of the use of TPD in the elemental method of design. The essence of the use of TPD in the subsystem design method. Advantages of object design methods. The main flows and components of TPD at parametric adjustment. Technological network of design at parametric adjustment of TPD. IP configuration with a model-oriented approach. The essence of model-oriented design. Components of the enterprise model. Technology of model-oriented design. The concept of IP profile. Types of IP profiles. Principles of IP profile formation. Relevance of using IP profiles. Structure of IP profiles. Basic functional profiles of IP. Literature: [3, p.30… 36; 4, p. 6… 70, 433 ... 448.] Tasks for VTS. Typical design of information systems. |
16 | Lecture 16. Modular control work All previous material, including standards and stages of IP design, system approach to IP design, system topologies, is submitted for control work. Tasks for VTS. Repeat the material of 10-15 lectures. |
17 | Topic 3.1. Structural and object-oriented design technology. Lecture 17. Structural design technology. The concept of the problem area. Requirements for the problem area model. Structural aspects of the functioning of the problem area. Object structure. Functional structure. Management structure. The organizational structure. Technical structure. Graphic notations. Evaluate aspects of the functioning of the problem area. Levels of detail of problem area models. External level. Conceptual level. Internal level. Approaches to problem area modeling. Concepts, features and principles of structural analysis. Diagrams used in structural analysis. Works performed in structural design. SADT analysis and design methodology. Methods of Heine - Sarson and Yodan de Marco. Data modeling methodologies. IDEF3 workflow modeling methodology. Structural design. Literature: [3, p.30… 36; 4, p. 6… 70, 433 ... 448.] Tasks for VTS. Creating a usage chart. |
18 | Lecture 18. Object-oriented design technology. The essence of the object approach. Basic concepts of object-oriented methodology. Principles of object approach. Models used in the object-oriented approach. Features of object-oriented design. Object design standards. Object-oriented design technology. Literature: [3, p.30… 36; 4, p. 6… 70, 433 ... 448.] Tasks for VTS. Object-oriented design technology. |
**
**
Laboratory classes
№ | Name of laboratory work | Number of aud. hours |
---|---|---|
1 | Laboratory work 1. Programming of the automated control system of language of consecutive operations of SFC Get a general idea of basics of software design of a virtual controller in the language of sequential SFC instructions without feedback. Master the method of developing a program in the SFC language for a virtual controller on the example of an automated control system for an object of automation without feedback. Literature: [12, p. 19] |
4 |
2 | Laboratory work 2. Programming of the automated control system with addition of feedbacks Get acquainted with the addition process feedback to the automated control system. Write down the algorithm of operation of the automated control system and add variables and parameters of the automated control system. Modify the control program of the technological scheme. Literature: [12, p. 35] |
4 |
3 | Laboratory work 3. Creation of a script of the simulator of object of automation To study the basic provisions and principles of development of software model of automation object in VBScript language. Get acquainted with the basic provisions and syntax of the VBScript programming language. Master the methodology and sequence of development of a virtual object of automation. Literature: [5, p. 42] |
4 |
4 | Laboratory work 4. Application of the MODBUS protocol for communication of the virtual controller with object of automation To study the main provisions of the standard and the possibilities of the industrial protocol MODBUS on a practical example of an automated control system. Get acquainted with the technology of virtual interfaces on the example of installing a virtual port RS-232 on the developer platform. Learn the method and sequence of configuration and configuration of the MODBUS protocol in the CoDeSys environment. Literature: [5, p. 53] |
4 |
5 | Laboratory work 5. Development of a local human-machine interface Learn the built-in visualization tools in the CoDeSys environment to create human-machine interface screens of the local operator location. Master the technique of developing static and dynamic visualization in CoDeSys, namely the creation of graphical primitives of the human-machine interface for the virtual controller. 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 | Tasks and functions of corporate information systems. Standards of corporate IP. | 2 |
2 | Functions and general requirements for IP. | 2 |
3 | The structure of information systems. | 2 |
4 | Characteristics of information systems. | 2 |
5 | Ensuring the reliability of information systems. | 2 |
6 | Trace requirements. Functional decomposition of IP. | 2 |
7 | Methods of creating requirements. Defining the image and boundaries of the project. | 2 |
8 | Information system life cycle. | 2 |
9 | Information system design methodology. | 2 |
10 | Organization of information systems creation. | 2 |
11 | IP design tools. | 2 |
12 | IP topologies and client-server IP architecture. | 2 |
13 | Typical design of information systems. | 2 |
14 | Creating a usage chart. | 2 |
15 | Object-oriented design technology | 2 |
16 | Preparation for the test on all material of the module. | 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", full answer to the questions during the defense (not less than 90% of the required information) and properly executed protocol for laboratory work - 10 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 - 8 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 - 6 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) - 25 points;
"fine", a sufficiently complete answer (not less than 75% of the required information), or a complete answer with minor errors - 20 points;
"satisfactorily", incomplete answer (but not less than 60% of the required information) and minor errors - 16 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 * 10 + 2 * 25 = 100.
Students who have a rating of less than 60 points at the end of the semester, as well as those who want to increase the grade, perform a test.
The test consists of 4 questions. Each is rated 25 points.
The sum of points for each of the four questions () is transferred to the credit score according to the table:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Test:
The sum of starting points and points for the modular test is transferred to the credit score according to the table:
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 credit
Define the concept of system.
What is an information system.
Define the factual system.
What is an information retrieval (reference) system.
What is an integrated (corporate) system.
What is a monitoring information system.
What do you know about the scope of IP.
Define the software life cycle.
What do you know about the main processes of the software life cycle?
What is software verification?
What is software validation?
What are the main strategies for designing IP?
List the main advantages and disadvantages of the cascade model of LF IP.
List the main advantages and disadvantages of the spiral model of LF IC.
List the advantages and disadvantages of canonical IP design technology.
List the advantages and disadvantages of RUP-technology of IP design.
List the advantages and disadvantages of XP technology.
List the advantages and disadvantages of SCRUM-technology.
What do you know the stages and stages of creating IP using canonical technology?
Define the concept of object.
List the team roles of the project.
List the responsibilities of the project manager.
Define the concept of adaptive requirements and adaptive customer.
What is the object of business process modeling?
What two approaches to business process modeling exist in terms of the iterative nature of the IP development process? Which one is better and why?
What are the basic concepts of business process modeling?
Which models involve business process modeling?
What stereotypes does the business analysis model contain?
What charts can a business analysis model contain?
Name three main strategies for constructing a process model.
[1] Methodical council of the university - for general university disciplines.