Information Systems Analysis and Design

IT-MSC-2MBS-Compulsory-Elective - group S
IT-MSC-2MMI-Compulsory-Elective - group M
IT-MSC-2MPV-Compulsory-Elective - group D
IT-MSC-2MSK2ndCompulsory-Elective - group M
Language of Instruction:Czech
Private info:http://www.fit.vutbr.cz/study/courses/AIS/private/
Completion:credit+exam (written)
Type of
Guarantor:Zendulka Jaroslav, doc. Ing., CSc. (DIFS)
Deputy guarantor:Rychlý Marek, RNDr., Ph.D. (DIFS)
Lecturer:Rychlý Marek, RNDr., Ph.D. (DIFS)
Zendulka Jaroslav, doc. Ing., CSc. (DIFS)
Instructor:Bartík Vladimír, Ing., Ph.D. (DIFS)
Rychlý Marek, RNDr., Ph.D. (DIFS)
Faculty:Faculty of Information Technology BUT
Department:Department of Information Systems FIT BUT
Advanced Information Systems (PIS), DIFS
Tueexam - 2. oprava2019-01-29E104 11:0012:501MIT 2MIT
Tueexam - řádná2019-01-15D105 12:0013:501MIT 2MIT
Tueexam - 1. oprava2019-01-22E112 15:0016:501MIT 2MIT
Wedobhajoby projektů2018-12-12C236 09:0011:50
Wedobhajoby projektů2018-12-12C236 12:0013:50
Friobhajoby projektů2018-12-14C236 10:0011:50
Learning objectives:
  The goal of the subject is to give students knowledge of methods and tools used in information system development and to learn them to apply these methods and tools.
  Software process, software development lifecycle models. Modelling techniques of the  UML 2.0. Introduction to Unified Process. Inception, requirements capturing and specification. Elaboration, domain model. Architecture design, architectural patterns and frameworks. Model-View-Controller pattern. JEE platform, SOA. Class design, GRASP principles. Design patterns. Programming, test-driven design, refactoring. Activities in next iterations. A project oriented to requirement analysis and software design.
Knowledge and skills required for the course:
  • Basic knowledge of software engineering. 
  • Knowledge of the paradigms of and practical experience with object-oriented programming.
Subject specific learning outcomes and competencies:
  • Students will know fundamentals of essential stages in information system development at a level, which is further evolved in specialized subjects.
  • They will be able to develop suitable models during information system requirements analysis and design, mainly in the UML language.
Generic learning outcomes and competencies:
  Students will learn how to analyze a design solution of a given problem in a small team. They learn to present and defend  both partial and final results of the project.
Why is the course taught:
  Requirement analysis of new or updated software and its subsequent design are important prerequisites for efficient software deployment and successful deployment, operation, and maintenance, whether it is the development of information systems, mobile applications, or embedded software for dedicated devices. Proper object design, knowledge of UML or agile approaches, advanced technologies for implementation or development (code management, CI/CD, etc.) are useful for every developer, designer, analyst, or system architect.
Syllabus of lectures:
  1. Software process, software development lifecycle models.
  2. Modelling techniques of the  UML 2.0 - object structure modelling, use case modelling.
  3. Modelling techniques of the  UML 2.0 - interaction, state and activity modelling, component and deployment modelling. Other types of diagrams.
  4. Introduction to Unified Process. Inception.
  5. Elaboration, domain model.
  6. Architecture design - dependencies and their elimination, layers.
  7. Architectural patterns and frameworks. Model-View-Controller pattern. Particularity of web applications.
  8. Introduction to JEE platform, SOA.
  9. Class design, GRASP principles.
  10. Design patterns.
  11. Comments to programming, test-driven design, refactoring.
  12. Modelling techniques and activities in next iterations.
  13. A lecture of an expert from industry.
Syllabus - others, projects and individual work of students:
  • Informal requirement specification of a given part of an information system being solved as the project.
  • Requirements specification and design of the of the system in UML.
Fundamental literature:
  • Larman, C.: Applying UML and Patterns. An Introduction to Oject-Oriented Analysis and Design and Iterative Development. 3rd edition. Prentice Hall PTR, Upper Saddle River, USA, 2004, 703 p., ISBN 0-13-148906-2.
  • Maciaszek, L.A., Liong, B.L.: Practical Software Engineering. A Case Study Approach. Addison-Wesley, Harlow England, 2005, 864 p., ISBN 0-321-20465-4. 
  • Maciaszek, L.A.: Requirement Analysis and System Design, 2 ed. Addison-Wesley, Harlow England, 2005, 504 p., ISBN 0-321-20464-6.
Study literature:
  • Larman, C.: Applying UML and Patterns. An Introduction to Oject-Oriented Analysis and Design and Iterative Development. 3rd edition. Prentice Hall PTR, Upper Saddle River, USA, 2004, 703 p., ISBN 0-13-148906-2.
  • Maciaszek, L.A., Liong, B.L.: Practical Software Engineering. A Case Study Approach. Harlow England, Addison-Wesley, 2005, 864 p., ISBN 0-321-20465-4.
  • Arlow, J., Neustadt, I.: UML and the Unified Process: Practical Object-Oriented Analysis and Design. Addison-Wesley Professional, 2002, 416 p., ISBN 0-201-77060-1.
Progress assessment:
  • Mid-term written examination - 15 point
  • Evaluated project with the defense (four partial submissions) - 34 points
  • Final written examination - 51 points; The minimal number of points which can be obtained from the final exam is 20. Otherwise, no points will be assigned to the student.
Exam prerequisites:
  Duty credit consists of submitting and defending project results, and of obtaining at least 24 points for activities during semester.

Your IPv4 address:
Switch to IPv6 connection

DNSSEC [dnssec]