Software architecture
- Description
- Curriculum
- FAQ
- Reviews
The architecture describes the processes and structures of the entire project, determining the data throughput in different parts of the project, and allows you to optimize and scale the project in the future.
Good architects are often people who learn from even better architects. Perhaps this is because some conceptual requirements are inherent in almost all projects. Each conceptual requirement is formulated as a question that the architect must ask himself during the project. Of course, some systems may have their own additional critical conceptual requirements.
We will get to know the types of software architectures. We will be able to create our own simple software architecture. We will be able to use and expand the software architecture. As a result, this course will be useful not only for architects or people who plan to become one. And, technical leaders of the development group, developers of different levels and testers.
In first section, I reveal the main objective of the course. In second section you will be introduced to the types of software architectures. In third section you will be able to create his own simple software architecture. In forth section you will be able to use and extend the software architecture. In fifth section the nuances of software architecture will be considered. Six section will help you understand which part of the course will be most useful to you.
Course Topics and Structure:
1. Introduction
2. Familiarity with software architecture.
2.1 Introduction
2.2 Principles of software architecture.
2.3 The content of the architecture.
2.4 Static structural diagrams.
2.5 Dynamic diagrams.
2.6 Conclusions.
3. Creation of software architecture.
3.1 Introduction
3.2 How to start creating software architecture.
3.3 The interface and what it should describe.
3.4 Interaction of components and objects.
3.5 Database. Content, objects, interaction.
3.6 Dynamic diagrams, how to do and why you need them.
3.7 Conclusions.
4. Support and use of software architecture.
4.1 Introduction
4.2 What to do with the software architecture after its creation.
4.3 Helpful information for the programmer on software architecture.
4.4 Support of software architecture.
4.5 Extending the software architecture.
4.6 Conclusions.
5. Software architecture. Next level.
5.1 Introduction
5.2 Summary of the main structures.
5.3 Impact of software architecture on the future life of software.
5.4 A software architect is not a profession, but a calling.
5.5 Twelve architecture mistakes.
5.6 Conclusions.
6. Conclusions and results of the course. Summing up.
-
2
Introduction lessonWhat will be in the section.
-
3
Elements of software architecture
In this lecture, we will discuss what basic questions and how software architecture helps to answer.
-
4
Architecture content
What you should do when developing an architecture, what is desirable and what you should think about when there is a foundation.
-
5
Static structural diagrams
The structural aspects of architecture manifest themselves in many ways, and as a result, most definitions of architecture are deliberately left undefined. A structural can be a subsystem, a process, a library, a database, a computational node, a system in the traditional sense, a finished product, and so on.
-
6
Dynamic diagrams
Software projects are always about processing information in time and interacting with the environment. How architectural elements interact over time.
-
7
Summing up the section lesson
We:
Discussed the topic.
Acquainted with the section contents.
We did practical tasks.
-
8
Knowledge check
-
9
Introduction lesson
What will be in the section.
-
10
How to start creating software architecture
Quick overview of the tools for architecture creation.
-
11
Interface and what should be described in it
Program will interact with the outside world through interfaces. Receive data and output it in a specific format.
-
12
Interaction of components and objects
Here we will learn how to make structures of different types. Connect them with each other, already studied interfaces, and not only.
-
13
Database. Content, objects, interaction
Data is everything, because data is the blood of software. It is the data that is processed by any software. Accordingly, when creating a software architecture, we must learn how to create data structures and the interaction between objects with this data. There will also be a practical lesson - creating data structures, objects.
-
14
Dynamic diagrams, how to make and why you need them
In this section, we will look at the importance of dynamic diagrams
-
15
Summing up the section lesson
We:
Discussed the topic.
Acquainted with the section contents.
We did practical tasks.
-
16
Knowledge check
-
17
Introduction lesson
What will be in the section.
-
18
What to do with software architecture after it is created
In this section, we will look at the architect's tasks.
-
19
Useful information for a programmer in software architecture
Helpful information for the programmer on software architecture.
-
20
Support of software architecture
In this lecture we discuses one of part architecture lifecycle. Support of software architecture.
Or maintains of software architecture.
-
21
Extending software architecture
In this lecture we continue discuses architecture lifecycle. Expansion of software architecture.
-
22
Summing up the section lesson
We:
Discussed the topic.
Acquainted with the section contents.
We did practical tasks.
-
23
Knowledge check
-
24
Introduction lesson
What will be in the section.
-
25
Summary of major structures
Software development can be described as a complex systemic process that requires expertise in various spheres of technology as well as the concerned business. An integral part of this software development process is facilitated by defining the architecture of software just like a blueprint of a master plan.
This lecture about some famous architecture.
-
26
The impact of software architecture on the future life of software
How architecture affects the software life cycle.
-
27
A software architect is not a profession, but a vocation
In this lecture, we will discuss what qualities an architect should have. And what is necessary for his career growth.
-
28
Twelve architecture mistakes
The most common mistakes in software architectures.
-
29
Summing up the section lesson
We:
Discussed the topic.
Acquainted with the section contents.
We did practical tasks.
