456-0344/01 – System Analysis and Design (SAN)
| Gurantor department | Department of Computer Science | Credits | 6 |
| Subject guarantor | Ing. Svatopluk Štolfa, Ph.D. | Subject version guarantor | Ing. Svatopluk Štolfa, Ph.D. |
| Study level | undergraduate or graduate | Requirement | Optional |
| Year | 1 | Semester | summer |
| | Study language | Czech |
| Year of introduction | 2006/2007 | Year of cancellation | 2009/2010 |
| Intended for the faculties | FEI | Intended for study types | Follow-up Master |
Subject aims expressed by acquired skills and competences
The main goal of this subject is to extend the student's knowledge about the software development by the introduction and description of the initial software process disciplines that are concerning about the basics of software development. These disciplines are requirements gathering, analysis and design of software systems.
Teaching methods
Lectures
Tutorials
Project work
Summary
Subject is focused on techniques and methods how UML is used for software specification, analysis and design. The process of how models are created and transformed is described including the usage of analysis and design patterns.
Compulsory literature:
Aybuke Aurum, Claes Wohlin (Eds.): Engineering and Managing Software Requirements, ISBN-10: 3-540-25043-3
Charles S. Wasson: System Analysis, Design and Development, ISBN-10: 0-471-39333-9
Tom Pender: UML Bible, Wiley Publishing, ISBN: 0-7645-2604-9
Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides: Design Patterns: Elements of Reusable Object-Oriented Software, ISBN-10: 0201633612
Recommended literature:
Aybuke Aurum, Claes Wohlin (Eds.): Engineering and Managing Software Requirements, ISBN-10: 3-540-25043-3
Charles S. Wasson: System Analysis, Design and Development, ISBN-10: 0-471-39333-9
Tom Pender: UML Bible, Wiley Publishing, ISBN: 0-7645-2604-9
Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides: Design Patterns: Elements of Reusable Object-Oriented Software, ISBN-10: 0201633612
Way of continuous check of knowledge in the course of semester
Conditions for credit:
Presentation of the software project and its documenatation and models. To pass you must gain at least 50% (20) of the maximum of 40 points from coursework and 50% (30) of the maximum of 60 points from exam.
E-learning
Other requirements
Prerequisities
Subject has no prerequisities.
Co-requisities
Subject has no co-requisities.
Subject syllabus:
Lectures:
Requirements Gathering
Introduction to the subject. Requirement gathering methods and policies. Roles and their duties and responsibilities during the requirements gathering phase, iteration development of requirement model, usage of business modeling, use cases, text descriptions etc.
System Analysis
Analysis methods and policies. Roles and their duties and responsibilities during the analysis phase, iteration development, analysis patterns, practicies of model description, usage of UML.
System Design
Methods and policies of system analysis. Roles and their duties and responsibilities during the design phase. Differencies of the analysis and design model.
Design patterns and their usage.
Implementation of the software.
Realization of the software. Roles and their duties and responsibilities during the Implementation phase. Mapping of the logical model to the software components.
Exercises:
The main goal of the practices is the consultancy about software projects developed by the students (coursework).
Projects:
The project will include the following parts: requirements model and description, analysis model and description and desing model and decsription.
Conditions for subject completion
Conditions for completion are defined only for particular subject version and form of study
Occurrence in study plans
Occurrence in special blocks
Assessment of instruction