SubjectsSubjects(version: 945)
Course, academic year 2023/2024
   Login via CAS
Information Systems I - NSWI049
Title: Informační systémy I
Guaranteed by: Department of Software Engineering (32-KSI)
Faculty: Faculty of Mathematics and Physics
Actual: from 2015
Semester: winter
E-Credits: 6
Hours per week, examination: winter s.:2/2, C+Ex [HT]
Capacity: unlimited
Min. number of students: unlimited
4EU+: no
Virtual mobility / capacity: no
State of the course: cancelled
Language: Czech
Teaching methods: full-time
Teaching methods: full-time
Guarantor: RNDr. Michal Žemlička, Ph.D.
prof. RNDr. Jaroslav Král, DrSc.
Class: Informatika Mgr. - Softwarové systémy
Classification: Informatics > Software Engineering
Pre-requisite : NDBI025
Is co-requisite for: NSWI050
Annotation -
Last update: T_KSI (16.05.2003)
The first part of a course of two lectures covering all the essential knowledge needed during the development and use of information systems. The emphasis is on the completeness of the knowledge and of the topics typical for information systems (social consequences and/or conditions, organizational types, global systems, requirements specification issues). The lectures contain many examples from practice. The students use UML and CASE tools.
Literature - Czech
Last update: RNDr. Pavel Zakouřil, Ph.D. (05.08.2002)

Král J., Demner J.: Softwarové inženýrství. Academia Praha, 1991

Sochor J., Richta K.: Projektování programových systémů. Vyd.ČVUT Praha, 1994

Míčovský A., Šešera L.: Objektovo orientovaná tvorba systémov a jazyk C++. Perfekt Bratislava, 1994

Rumbough J. et al: Object Oriented Modeling and Design, Prentice Hall, 1991

Manuály požitých CASE nástrojů

Syllabus -
Last update: T_KSI (16.05.2003)

What is information system (IS). Development cycle, reasons of development problems, complexity indicators. Operational and management levels. Unclear or indirect effects of information systems, information and knowledge society.

Computer ergonomics and its consequences for the specification and design of IS.

IS architectures and their consequence for the requirements specification strategies. Confederations, XML. The praxis of requirements collection. What to know from the partner knowledge domain.

IS for risk management, IS for risk management as an example of some typical problems with requirements specification. Critical requirements

Negotiations, winer/winer, the use of consultants.

Organizational types and IS

Basic notions of software processes. Prototypes, iterations, increments, reviews, inspections and supporting IS

Project supporting models. CPM and critical chain also as example of implicit assumptions

 
Charles University | Information system of Charles University | http://www.cuni.cz/UKEN-329.html