ВАВОК: Requirements analysis and design definition
The training is designed and developed for business analysts and other experts involved in the process of requirements analysis and design definition.
Our training shows you how to describe the structure and operation logic of a use case, and how to represent each one as a set of diagrams containing all the necessary information.
20 hours
English
Online
To be determined
A clear description of functional requirements in the form of use cases is a convenient way to structure and understand the entire set of functional requirements of the system. This form is also convenient for agreeing with the customer about how the system will look and behave. However, once the requirements are approved, the system must be designed and developed. The task of analysis at this stage is to transform the description of use cases into a technically correct description of the structure and behavior of the system, understandable for the architect, developers, and testers. Good practice for such a description is visual modeling, including using UML (Unified Modeling Language).
UML allows you to represent all aspects of the designed system with any required accuracy. At the same time, for each use case, several diagrams of different types can be created - each type depicts its own aspect. The entire set of diagrams that reveal the inner logic of use cases constitutes the so-called system analytical model. It's on the basis of this model that the system architecture is further designed, system functions are implemented, and data structures are created.
This course is devoted to the study of the process of creating models – from the highest level to more detailed. During the course, trainees will practice creating and analyzing models. They will acquire the skills of detailed modeling of the system's functionality and rational distribution of responsibilities between its various parts. The basement of the course practice is an almost completed document that should be analyzed and improved by participants. So, participants obtain not only modeling and UML experience but also training in peer review, document analysis, and other activities that are natural to real projects. Some parts or principles of practical examples can be used by participants in their own projects.
Formation of the student's knowledge and skills necessary for object-oriented analysis and system design, in particular:
The course is intended for those who are faced with the design of software systems, as well as for anyone who wants to understand the basics of object-oriented analysis and design using UML:
To improve understanding of course material, it’s recommended participants to have the following preliminary knowledge:
For trainees, it is desirable to have experience participating in software development projects or understanding the development process.
Topic |
Lection, hours |
Practice, hours |
Object-oriented approach to the analysis and design of systems |
||
· Objects and Classes |
1 |
|
· Abstraction, Encapsulation, Modularity, Hierarchy |
1 |
0.3 |
Models hierarchy |
||
· Types of models used in the analysis and design of the system |
0.7 |
|
· Decomposition |
0.25 |
|
· System architecture |
1 |
|
Object-oriented analysis |
||
· Domain model |
1.2 |
|
· Ways to identify and describe objects and classes |
0.5 |
1 |
· Determination of potential architecture |
0.6 |
|
· Analysis of system behavior |
0.75 |
1.5 |
· Use Case Realization Model |
1.5 |
1 |
Object-Oriented Design |
||
· Criteria for the quality of design solutions |
1.5 |
|
· Refinement of the class model |
1.5 |
1.5 |
· Moving from analysis to design |
1.5 |
|
Best Software Engineering Practices |
||
· Using analysis and design patterns |
1 |
|
· GRASP design patterns |
1.2 |
|
15.2 (76%) |
4.8 (24%) |
|