Faculty of Information Technology, BUT

Course details

Information Systems Analysis and Design

AIS Acad. year 2019/2020 Winter semester 5 credits

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.

Guarantor

Deputy Guarantor

Language of instruction

Czech

Completion

Credit+Examination (written)

Time span

39 hrs lectures, 13 hrs projects

Assessment points

51 exam, 15 half-term test, 34 projects

Department

Lecturer

Instructor

Subject specific learning outcomes and competences

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

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.

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.

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.

Prerequisite kwnowledge and skills

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

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.

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.

Syllabus of lectures

  1. Introduction, Software Projects
  2. Software Modelling Languages - function-/object-oriented design and UML 2, architectural views
  3. UML
  4. New Features in UML and Agile Modelling
  5. Unified Process and its Inception Phase - requirements analysis, FURPS+ and use case modelling
  6. Elaboration Phase in Unified Process - domain model, system sequence diagram and operation contracts
  7. Software Architecture - layered architecture, package dependencies and their elimination, model-view separation
  8. Architectural Patterns - Model-View-Controller (MVC), Presentation-Control-Entity-Mediator-Foundation (PCMEF), Model-View-Presenter (MVP)
  9. Object-Oriented Design - Responsibility-Driven Design (RDD), GoF design patterns, GRASP
  10. The Principles of Object-Oriented Design - SOLID principles, object visibility and scope
  11. Software Development - Test-Driven Development (TDD), code refactorisation
  12. Anti-pattern and Best Practices in Software Development
  13. Practices, Examples and Demonstrations of Software Design and Development

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.

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.

Schedule

DayTypeWeeksRoomStartEndLect.grpGroupsInfo
Wedother2019-12-11 C228 10:0013:50obhajoby projektů
Thulecturelectures D0206 10:0012:50 1MIT 2MIT MIS xx

Course inclusion in study plans

Back to top