INFORMATION SYSTEMS DESIGN - Syllabus
Details of the discipline
Level of higher education | First (undergraduate) |
---|---|
Branch of knowledge | 12 Information technologies |
Specialty | 126 Information systems and technologies |
Educational program | Integrated information systems |
Discipline status | Normative |
Form of education | full-time/correspondence/distance |
Year of training, semester | 4th year, autumn semester |
Scope of the discipline | 5 ECTS credits/150 hours (36 hours – Lectures, 36 hours – Laboratory, 78 hours – SRS) |
Semester control/ control measures | Exam/examination paper |
Lessons schedule | http://rozklad.kpi.ua/Schedules/ScheduleGroupSelection.aspx |
Language of teaching | Ukrainian |
Information about the course leader / teachers | Lecturer: Ph.D., Prof. Bohdan Yaroslavovych Korniyenko, Laboratory: art. off Yalanetskyi Valery Anatoliyovych,v.yalanetskyi@kpi.ua, |
Placement of the course | https://campus.kpi.ua |
Program of educational discipline
Description of the educational discipline, its purpose, subject of study and learning outcomes
Description of the discipline. According to the standard of higher education in the specialty 126 Information systems and technologies of the field of knowledge 12 Information technologies for the first (bachelor) level of higher education and the educational and professional program of the first (bachelor) level of higher education of the discipline "Information systems design» forms (KZ2) withability to apply knowledge in practical situations, (KZ3) withability to understand the subject area and professional activity, (KS1) withthe ability to analyze the object of design or functioning and its subject area, (KS2) withthe ability to apply standards in the field of information systems and technologies when developing functional profiles, building and integrating systems, products, services and elements of the organization's infrastructure,(KS3) withability to design, develop, debug and improve system, communication and software hardware of information systems and technologies, the Internet of Things (IoT), computer-integrated systems and system network structure, their management, (KS4) withthe ability to design, develop and use the means of implementing information systems, technologies and information communications (methodical, informational, algorithmic, technical, software and others), (KS5) withthe ability to evaluate and take into account economic, social, technological and environmental factors at all stages of the life cycle of information and communication systems, (KS7)the ability to apply information technologies during the creation, implementation and operation of the quality management system and to estimate the costs of its development and maintenance, (KS8)the ability to manage the quality of products and services of information systems and technologies during their life cycle, (KS10)the ability to select, design, deploy, integrate, manage, administer and support information systems, technologies and information communications, services and infrastructure of the organization, (CS18)the ability to solve the problems of integration processes of information systems in the sphere of production and management using methods of analysis and synthesis of means of transmission, storage and processing of information, the basics of a service-oriented approach to servicing users of information systems, basic and applied information technologies and IT infrastructure toolsand (PRN2) withapply knowledge of fundamental and natural sciences, system analysis and modeling technologies, standard algorithms and discrete analysis when solving problems of designing and using information systems and technologies, (PRN4) pconduct a system analysis of design objects and justify the choice of structure, algorithms and methods of information transmission in information systems and technologies, (PRN5)justify the choice of software and technical means for the creation of information systems and technologies based on the analysis of their properties, purpose and technical characteristics, taking into account system requirements and operating conditions; have skills in debugging and testing software and technical means of information systems and technologies, (PRN7)justify the choice of technical structure and develop appropriate software that is part of information systems and technologies, (PRN8) fromapply the rules for the design of project materials of information systems and technologies, know the composition and sequence of project work, taking into account the requirements of the relevant regulatory and legal documents for implementation in professional activities,(PRN9) fromcarry out a systematic analysis of the enterprise architecture and its IT infrastructure, develop and improve its element base and structure.
This course introduces students to modern views on scientific and methodological foundations and standards in the field of designing information systems. The course begins with an introduction to information systems (IS) and their defining role for the successful implementation of enterprises and organizations. Different types of IS, organizational requirements for their implementation and operation, development strategy, data and information management are considered; IS life cycle, knowledge needed by analysts, such as communication skills, ability to analyze facts; IS components, feasibility and cost-effectiveness analysis; data flow diagram as a means of system analysis and CASE means of IS design. Popular tools for creating IS are also considered.
**The subject of the academic discipline:**the main modern methodologies and methods of building information systems and their management, the main classes, types and categories of information systems, their functionality and areas of application, modern methodologies, methods, models and instrumental means of creating and using information systems of various types.
**Interdisciplinary connections.**DisciplineInformation systems designis based on the disciplines: Software Development Technologies, Systems Theory and System Analysis, Computer networks,Databases, Theory of algorithms.
**The purpose of the educational discipline.**The purpose of the discipline is to thoroughly acquaint students with the theoretical foundations of the organization, operation and design of information systems (IS), mastering practical skills in the use and creation of IS and their components for various purposes, providing theoretical knowledge and practical skills in the design and support of information systems for various subject areas.
The main tasks of the academic discipline
Knowledge:
- essence and purpose of information systems;
- design stages and requirements for the design process of information systems;
- standards for the design of information systems and design documentation;
- systematic approach to the design of information systems, 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 for creating and supporting information systems, RUP technology, ARIS technology, pattern technology.
Skills:
- identify and analyze IS requirements;
- specify and document IS requirements;
- design data models and process models;
- design process models;
- apply the UML standard;
- use visual programming methods;
- apply modern CASE technologies for creating and supporting IS.
Pre-requisites and post-requisites of the discipline (place in the structural and logical scheme of training according to the relevant educational program)
**Prerequisites:**the ability to apply knowledge in practical situations, the ability to use information and communication technologies, the ability to search, process and analyze information from various sources, the ability to apply knowledge about the basic principles and methods of constructing algorithms and determining the main technological parameters.
**Post-requisites:**to know the systemological basics of creating and using 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 research models of information systems at the conceptual level and the level of the subject area; the basics of architectural design of information systems and their CASE support system; basic methodologies and methods of managing information systems 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 to implement professionally profiled knowledge and practical skills when solving tasks of typification of information systems and information technologies; 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; develop process analytical models of business systems and their information systems with the help of computer systems; explore the main structures and characteristics of process models.
Content of the academic discipline
Lecture classes
Section 1. IS design tools.
Chapter 2. Structural analysis and design of IS.
Laboratory classes
Programming of an automated control system in the language of sequential operations 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 between the virtual controller and the automation object
Development of a local human-machine interface
Object-oriented management program
Design of the regulator and programmer
WEB dispatching
Development of the operator's automated workplace in Trace Mode and its connection with the virtual controller
Interaction of the operator's automated workplace with external databases
Educational materials and resources
Basic literature
- Ananiev O.M. Information systems and technologies in commercial activity: textbook / O.M. Ananiev, V.M. Bilyk, Ya.A. Honcharuk - Lviv: Novy Svit, 2006. - 583 p.
- Hlivenko S.V. Information systems in management: training. manual / S.V. Hlivenko, E.V. Lapin, O.O. Pavlenko, S.S. Slabko, V.M. Swan. - Sumy: University Book, 2005. - 407 p.
- Guzhva V. M. Information systems and technologies at enterprises: training. manual / V. M. Guzhva. - K.: KNEU, 2001. - 400 p.
- Pasichnyk V.V., Lytvyn V.V., Shakhovska N.B. Information systems design. Study guide (authorized by the Ministry of Education and Culture of Ukraine) Lviv: 2013.– 380 p.
- Tomashevskyi O.M. Information technologies and modeling of business processes: Study guide. / O.M. Tomashevskyi, M.B. Tsegelyk, G.H. Viter, V.I. Dubuk. K.: Center of educational literature, 2005. – 296 p.
- Pavlenko P. N. Automated systems of technological preparation of extended productions. Methods of construction and management: monograph / P. N. Pavlenko. — K.: Knyzhnoe izd-vo NAU, 2005. — 280 p.
- Methodical instructions for performing laboratory work in the discipline "Designing information systems" of the credit module "Peculiarities of designing information systems" for students of specialty 126 "Information systems and technologies" [Text] / Compiled by: V.A. Yalanetskyi - K.: NTUU "KPI named after Igor Sikorsky", 2020. - 79 p.
Supporting literature
- Ushakova I. O. Fundamentals of system analysis of objects and processes of computerization: study guide. Part 2 / I. O. Ushakova. – Kh.: Ed. Khneu, 2008. – 324 p.
- Gavrylenko V. V. DBMS: technology for solving functional problems in transport: training. manual [for students higher education closed.] / V.V. Havrylenko, E.H. Logachov, L.M. Strunevych. — K.: NTU, 2007. — 168 p.
Fabrychev V. A. Information systems and technologies of enterprise: training. manual / V. A. Fabrychev, V. M. Borovyk. — K.: NAU, 2008. — 100 p.
Kosarev O. Y. Information systems on transport: comp. lectures / O. Y. Kosarev, A. M. Merzhvinska. — K.: NAU, 2001. — 112 p.
Educational content
Methods of mastering an educational discipline (educational component)
Lecture classes
No. z/p | The name of the topic of the lecture and the list of main questions (list of didactic tools, references to the literature and tasks on the SRS) |
---|---|
1 | Lecture 1.Purpose, tasks, functions, classificationIS design tools. Requirements for design tools. Factors affecting the choice of design tools. Criteria for choosing design tools. Manual design tools. Computer design tools. Types of computer design tools: supporting designinformation processing operations that support the design of individual components of the project, that support the design of sections of the project, that support the development of the project at the stages and stages of the design process. Literature: [1, pp. 5-31; 3, pp. 3...10; 4, p. 10...42.] *Tasks on SRS.*Purpose and classification of IS. |
2 | Lecture 2. Groups of design tools. Traditional programming systems; tools for creating file server applications; tools for developing "client-server" applications; means of automating office management and document management; 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 analyzing and designing the activities of the organization and the designed system, database design tools, 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, pp. 5-31; 3, p. 16...26; 4, p. 10...42.] *Tasks on SRS.*Purpose and classification of IS. |
3 | Lecture 3.Data model. Data model layers. 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. Mapping the data model in the Erwin tool. Creating a logical data model: logical model levels; entities and attributes; communication; entity types and inheritance hierarchy; keys; data normalization; domains Creating a physical data model: validation rules and default values; index triggers and stored procedures; database size calculation. Direct and reverse engineering. Generating client-side code using ERwin. Advanced attributes. Code generation. Creating reports. Generation of dictionaries. Literature: [1, pp. 5-31; 3, pp. 3...10; 4, p. 10...42.] *Tasks on SRS.*Functions and general requirements for IS. |
4 | Lecture 4.Flexible IS development technologies. Prerequisites for the emergence of RAD methodology (Rapid Application Development). Main features of RAD methodology, object-oriented approach to creating applications, use of visual programming tools, event programming. Limitations of the RAD methodology. Factors affecting the development time block. The user's role 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. The scope of the RAD model. SCRUM is an IS development management methodology. CASE technologies: definition and general characteristics, purpose. Advantages and opportunities of CASE technology. Comparison of traditional and CASE technology. Literature: [1, pp. 5-31; 3, pp. 3...10; 4, p. 10...42.] *Tasks on SRS.*Structure of information systems. |
5 | Lecture 5.RUP technology. General characteristics of RUP technology. Basic principles of RUP technology. Iterative development. Process management based on use cases. Focus on architecture. Dynamic structure: the beginning of the project (Inception), elaboration (Elaboration), construction (Construction), transfer (Transition). Static structure. Main disciplines: modeling of the subject area (business modeling, Business Modeling), definition of requirements (Requirements), analysis and design (Analysis and Design), implementation (Implementation), testing (Test), deployment (Deployment). Auxiliary disciplines: configuration and change management (Configuration and Change Management), project management (Project Management), project environment (Environment). IBM Rational tools supporting RUP technology. Literature: [1, pp. 5-31; 3, pp. 3...10; 4, p. 10...42.] *Tasks on SRS.*Characteristics of information systems. |
6 | Lecture 6.Structural (static) diagrams. Class diagrams. Diagrams of objects. Component diagrams. Deployment diagrams. Diagrams of the component structure. Package diagrams. Diagrams of (dynamic) behavior. Use case diagram. 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 recommendations for developing use case diagrams. Literature: [1, p. 61-76; 3, p. 42...53; 4, p. 388 ...402; 6, pp. 219..234.] *Tasks on SRS.*Ensuring the reliability of the functioning of information systems. |
7 | Lecture 7. Specification of functional requirements for IS. Process flow models. A process approach to the organization of the organization's activities. Connection of the concept of process approach to the concept of matrix organization. The main elements of the process approach: process boundaries, key roles, a tree of goals, a tree of functions, a tree of indicators. Identification and classification of processes. Basic processes, management processes, provisioning processes. Reference models. Conducting a pre-project inspection of the organization. Questionnaires, interviews, photos of the staff's working day. The results of the pre-project survey. Literature: [ 4, p. 42-87. ] *Tasks for SRS.*Methods of creating requirements. |
8 | Lecture 8. Modeling methodologies of the subject area. Methodology of subject domain modeling. Structural model of the subject area. Object structure. functional structure. Management structure. The organizational structure. Functional-oriented and object-oriented methodologies for the description of the subject area. IDEF functional technique. Functional technique of data flows. Object-oriented technique. Comparison of existing methods. Synthetic technique. Literature: [ 7, p. 38-55. ] *Tasks for SRS.*Determination of the image and boundaries of the project. |
9 | Lecture 9.Concept and terminology of object-oriented approach. OO-approach requirement models. UML is the OO standard of modeling technology. Use case diagrams - precedents - (use case diagrams - UCD). Elements and rules of UCD construction. Descriptions of precedents. Literature: [2, pp. 52-87; 4, p. 120-170.] *Tasks for SRS.*Requirements tracing. Functional decomposition of IS. |
10 | Lecture 10. Modular control work All preliminary material, including the basic means of design technology and IS creation methodology, is submitted to the control work. Tasks include theoretical and practical parts, as well as an additional task, in case of timely completion of the main questions. Tasks for SRS. Repeat the material of lectures 1-9. |
11 | Lecture 11. Information systems in ACS TP. SCADA-approach in ACS TP.Automatic and automated control. Basic concepts and definitions. Classification of ACS. Composition of ACS. Peculiarities of technological processes in the chemical industry. 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 SRS.*Life cycle of the information system. |
12 | Lecture 12. General concepts and structure of SCADA systems. Concept of SCADA. A short story. Definition and general structure of SCADA. Functional structure of SCADA. Features of SCADA as a control process. Literature: [3, pp. 118...135; 4, pp. 182...194] Tasks for SRS. Information system design methodology. |
13 | Lecture 13. Basic requirements for SCADA systems and their capabilities. Hardware and software of SCADA systems. Basic requirements for SCADA systems. Basic capabilities of modern SCADA packages. Trends in hardware and software development of SCADA systems.Literature: [6, pp. 226...239; 7, pp. 349-398.] *Tasks for SRS.*Organization of creation of information systems. |
14 | Lecture 14. Overview of popular SCADA programs. Consumer characteristics of information systems. Characteristics by level of management. Time characteristics of IS. Qualitative indicators of information processes. IS reliability. IS efficiency. Literature: [3, pp. 30...36; 4, p. 6...70, 433 ...448.] *Tasks for SRS.*IS design tools. |
15 | Lecture 15. SCADA architecture. Main components of SCADA systems. Explain the difference between a SCADA package and a SCADA system. Basic functions of SCADA. The difference in the functioning of SCADA in transport and production. Automation systems design technology based on SCADA packages. Literature: [3, pp. 30...36; 4, p. 6...70, 433 ...448.] *Tasks for SRS.*Typical design of information systems. |
16 | Lecture 16. Basic subsystems of SCADA packages. The main components of SCADA programs. The central component of SCADA. Tag properties. Distribution of tags by data source. Networks for information exchange between SCADA, controllers, transmitters and executive devices. Organization of access to driver data. Basic network protocols. Literature: [3, p. 15...22; 4, p. 6...50, 420 ...434.] Tasks for SRS. Pattern technology. |
17 | Lecture 17. Organization of access to SCADA data. Organization of access to SCADA data. A brief description of the ORS standard. Principles of building data visualization tools. Difference between events and alarms. Concept of trends. Two types of trends. reports Embedded programming languages. General characteristics of programming languages. Literature: [3, pp. 23...36; 4, p. 51...70, 433 ...448.] *Tasks for SRS.*Object-oriented design technology. |
18 | Lecture 18. Modular control work All preliminary material, including standards and stages of IS design, is submitted to the control work. Tasks for SRS. Repeat the material of lectures 11-17. |
Laboratory classes
No | The name of the laboratory work | Number of aud. hours |
---|---|---|
1 | Laboratory work 1. Programming of an automated control system in the language of sequential SFC operations Get an overview ofthe basics of software design of a virtual controller in the language of sequential SFC instructions without feedback. Learn the method of developing a program in the SFC language for a virtual controller using the example of an automated control system for an automation object without feedback. Literature: [12, p. 7] |
4 |
2 | Laboratory work 2. Programming of an automated control system with the addition of feedback Familiarize yourself with the addition processfeedback to the automated control system. Write down the algorithm of operation of the automated control system and add the variables and parameters of the automated control system. Modify the flow chart control program. Literature: [12, p. 18] |
4 |
3 | Laboratory work 3. Creating a script for the automation object simulator To study the basic provisions and principles of development of the software model of the automation object in the VBScript language. Familiarize yourself with the basics and syntax of the VBScript programming language. Learn the methodology and sequence of developing a virtual object of automation. Literature: [5, p. 29] |
4 |
4 | Laboratory work 4. Application of the MODBUS protocol for communication of the virtual controller with the automation object To study the main provisions of the standard and the capabilities of the MODBUS industrial protocol using a practical example of an automated control system. Familiarize yourself with the technology of virtual interfaces using the example of installing a virtual RS-232 port on the developer's platform. Learn the methodology and sequence of configuration and setting of the MODBUS protocol in the CoDeSys environment. Literature: [5, p. 38] |
4 |
5 | Laboratory work 5. Development of a local human-machine interface Learn the built-in visualization tools in the CoDeSys environment to create local operator seat HMI screens. Learn the methodology 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. 45] |
2 |
6 | Laboratory work 6. Object-oriented control program Get an overview ofbasics of object-oriented management program. Learn the method of program development in the SFC language using the example of an automated control system for an automation object. Literature: [12, p. 54] |
4 |
7 | Laboratory work 7. Design of the regulator and programmer Familiarize yourself with the addition processregulator and programmer to the automated control system. Write down the functioning algorithm of an automated control system with a regulator and a software setter. Modify the flow chart control program. Literature: [12, p. 62] |
4 |
8 | Laboratory work 8. WEB dispatching To study the basic provisions and principles of development of a software model of an automation object with WEB-dispatching. Familiarize yourself with the basic provisions and algorithm for creating a WEB interface. Learn the methodology and sequence of developing a virtual object of automation. Literature: [5, p. 68] |
4 |
9 | Laboratory work 9. Development of the operator's automated workplace in Trace Mode and its connection with the virtual controller Learn the main functions and capabilities of Trace Mode using a practical example of an automated control system. Familiarize yourself with the virtual controller technology. Learn the methodology and sequence of configuring and setting up the virtual controller. Literature: [5, p. 72] |
4 |
10 | Laboratory work 10. Interaction of the operator's automated workplace with external databases Explore the built-in tools of the automated operator workstation to create local operator workstation HMI screens. Learn the methodology of developing the interaction of the operator's automated workplace with external databases. Literature: [5, p. 75] |
2 |
Independent work of a student/graduate student
No. z/p | The name of the topic submitted for independent processing | Number of hours of SRS |
---|---|---|
1 | Purpose and classification of IS. | 6 |
2 | Functions and general requirements for IS. | 4 |
3 | Structure of information systems. | 6 |
4 | Characteristics of information systems. | 4 |
5 | Ensuring the reliability of the functioning of information systems. | 6 |
6 | UML standard: static and dynamic diagrams. | 4 |
7 | Methods and means of research of the object of automation | 6 |
8 | Life cycle of the information system. | 4 |
9 | Information system design methodology. | 4 |
10 | Organization of creation of information systems. | 4 |
11 | IS design tools. | 4 |
12 | Typical design of information systems. | 4 |
13 | Pattern technology. | 4 |
14 | Object-oriented design technology. | 4 |
15 | IS reengineering. | 4 |
16 | Exam preparation for the entire material of the module. | 10 |
Policy and control
Policy of academic discipline (educational component)
The system of requirements for the student:
- rules for attending classes: it is forbidden to evaluate the presence or absence of the winner in the classroom class, including the awarding of incentive or penalty points. According to the RSO of this discipline, points are awarded for the corresponding types of educational activity in lectures and laboratory classes;
- module tests are performed without the use of auxiliary information from the Internet, a distance course on the Sikorsky platform, notes; incentive points are awarded for educational activity in lectures. The number of encouraged points is no more than 10;
- academic integrity policy: Code of Honor of the National Technical University of Ukraine "Ihor Sikorsky Kyiv Polytechnic Institute"https://kpi.ua/files/honorcode.pdf establishes general moral principles, rules of ethical behavior of individuals and provides a policy of academic integrity for persons working and studying at the university, which they should be guided by in their activities, including when studying and preparing control measures for the discipline "Information systems design".
Types of control and rating system for evaluating learning outcomes (RSO)
The student's rating in the discipline consists of the points he receives for:
- performance and protection of 10 laboratory works;
- execution of 2 modular control works (MKR).
System of rating points and evaluation criteria
Laboratory works:
"perfectly", a complete answer to the questions during the defense (at least 90% of the required information) and a properly prepared protocol for laboratory work - 4 points;
"good", a sufficiently complete answer to the questions during the defense (at least 75% of the required information) and a properly prepared protocol for laboratory work - 3 points;
"satisfactory", incomplete answer to the questions during the defense (at least 60% of the required information), minor errors and a properly prepared protocol for laboratory work - 2 points;
"unsatisfactory", an unsatisfactory answer and/or an improperly prepared protocol for laboratory work - 0 points.
Modular control works:
"perfectly", complete answer (at least 90% of the required information) – 5 points;
"fine", a sufficiently complete answer (at least 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 problem solution), requires mandatory rewriting at the end of the semester - 0 points.
Incentive points
for active work at lectures1 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 certification (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 certification (14th week), the student receives "credited" if his current rating is not less than 16 points.
Maximum amountweight points of control measures during the semester is:
R=10*rlab+2*rmkr=10*4+2*5=50.
Exam:
Admission to the exam is subject to passing all laboratory work, writing both modular test papers, 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 at 25 points.
Question evaluation system:
"excellent", a complete answer, at least 90% of the required information, which was completed in accordance with the requirements for the "skills" level (complete, error-free solution of the task) - 23-25 points;
"good", a sufficiently complete answer, at least 75% of the required information, completed in accordance with the requirements for the "skill" level or there are minor inaccuracies (complete solution of the task with minor inaccuracies) - 20-22 points;
"satisfactory", incomplete answer, at least 60% of the required information, completed in accordance with the requirements for the "stereotypical" level and some errors (the task was completed 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 control work is transferred to the examination grade according to the table:
Table 1. Conversion of rating points to grades on the university scale
Points | Rating |
---|---|
95-100 | perfectly |
85-94 | very good |
75-84 | fine |
65-74 | satisfactorily |
60-64 | enough |
Less than 60 | unsatisfactorily |
Failure to complete seven laboratory works and completion of the MCR for the grade "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 topic of the discipline and offers students to take the corresponding free courses. After the student receives a certificate of completion of remote or online courses on the relevant topic, the teacher closes the relevant part of the course (laboratory or lectures) by prior agreement with the group.
Working program of the academic discipline (Syllabus):
Folded Professor, Doctor of Technical Sciences, Bohdan Yaroslavovych Korniyenko
Approved Department of ICT (protocol No. 21 dated 06.29.2023)
Agreed Methodical commission of the faculty1(protocol No. 11 dated 29.06.2023)
Appendix 1
List of theoretical questions for the exam
- Requirements for IS design tools.
- Classification of IS design tools.
- CASE design tools.
- Data modeling.
- Data model design in Erwin.
- Process modeling.
- Designing a VRwin process model.
- Purpose and development of a unified modeling language.
- UML structure and notation.
- Types of UML diagrams.
- Use case diagram.
- Purpose of RPTwin.
- The RPTwin tooling environment.
- Using RPTwin formulas.
- Design of interfaces of information systems
- Concepts, purposes and requirements for the user interface.
- Standardization of interfaces.
- User interface creation toolkit.
- User interface development process.
- RAD-methodology and CASE-technology of IS creation and support
- Flexible IS development methodologies.
- RAD-methodology of IS creation and maintenance.
- SCRUM is an IS development management methodology.
- CASE-technology of creation and maintenance of IS.
- RUP technology. ARIS technology
- Characteristics and principles of RUP technology.
- Dynamic and static structure of RUP.
- IBM Rational tools supporting 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.
- IS reengineering
- Prerequisites for the emergence and essence of the process-oriented approach.
- Terminology of the process approach.
- Stages of business process reengineering
-
Methodical council of the university - for general university disciplines.↩