Course detail

Information Systems Analysis and Design

FIT-AISAcad. year: 2018/2019

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.

Learning outcomes of the course unit

  • 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.

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.

Prerequisites

  • Basic knowledge of software engineering. 
  • Knowledge of the paradigms of and practical experience with object-oriented programming.

Co-requisites

Not applicable.

Recommended optional programme components

Not applicable.

Recommended or required reading

  • 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 a unifikovaný proces vývoje aplikací. Computer Press, 2003, 408 s., ISBN: 80-7226-947-X.

  • 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. 
  • Arlow, J., Neustadt, I.: UML a unifikovaný proces vývoje aplikací. Computer Press, 2003, 408 s., ISBN: 80-7226-947-X.
  • Maciaszek, L.A.: Requirement Analysis and System Design, 2 ed. Addison-Wesley, Harlow England, 2005, 504 p., ISBN 0-321-20464-6.

Planned learning activities and teaching methods

Not applicable.

Assesment methods and criteria linked to learning outcomes

  • 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.

Language of instruction

Czech

Work placements

Not applicable.

Course curriculum

    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.

Aims

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.

Classification of course in study plans

  • Programme IT-MGR-2 Master's

    branch MBI , any year of study, winter semester, 5 credits, elective
    branch MPV , any year of study, winter semester, 5 credits, compulsory-optional
    branch MGM , any year of study, winter semester, 5 credits, elective
    branch MBS , any year of study, winter semester, 5 credits, compulsory-optional
    branch MIN , any year of study, winter semester, 5 credits, elective
    branch MMI , any year of study, winter semester, 5 credits, compulsory-optional
    branch MMM , any year of study, winter semester, 5 credits, elective
    branch MSK , 2. year of study, winter semester, 5 credits, compulsory-optional
    branch MIS , 2. year of study, winter semester, 5 credits, compulsory

Type of course unit

 

Lecture

39 hours, optionally

Teacher / Lecturer

Syllabus


  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.

Project

13 hours, compulsory

Teacher / Lecturer

Syllabus


  • 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.

eLearning