Software Architecture Chapter 12 Architecture-Based Software Development
foreword
This article is based on the bloggers during the XJU undergraduate period"Software Architecture Principles, Methods and Practice" Second EditionThe summary of the final test points, because it is a key summary of the classroom, so please forgive me for not covering some important knowledge points. The final course requirements of each school are different. If you want to learn the software architecture completely, please read Mr. Zhang Yousheng "Software Architecture Principles, Methods and Practice".
Table of contents
Readers can jump to the test summary of any chapter through the content link, or search through the [Software Architecture] column on my homepage. Welcome everyone to follow me or subscribe to the column you are interested in, and I will update the corresponding content regularly. If the summary of the test points in this series is helpful to you, please like it at the bottom of the page or leave a message in the comment area.
Summary
1. Generally speaking, a pattern has four basic components: pattern name, problem, solution and effect
- Pattern name: A pattern name is usually used to describe a design problem, its solution and effect, consisting of one or two words.
- Questions: Questions tell people when to use a design pattern, explain the problem and its context.
- Solution: The solution describes the basic elements of the design: their relationship, their respective tasks, and their cooperation with each other. A pattern is like a template that can be used in many different environments, and the abstract description enables people to apply the pattern to solve many different problems.
- Effects: Effects describe the results and trade-offs after applying a design pattern.
2. Three abstract classes included in the MVC pattern:
- View abstract class: It obtains display information from the model and displays it to the user in a specific form. There can be multiple different display forms or views for the same information.
- Controller abstract class: handles the interactive operation between the user and the software. Its responsibility is to determine the control process of the software and ensure the corresponding relationship between the user interface and the model. It receives the user's input and feeds the input back to the model, thereby realizing the computational control of the model. , and then according to the needs of the user, create a suitable view to return to the user interface.
- Model abstract class: It provides business logic services to views (View abstract class) and controllers (Controller abstract class).
conclusion
The above is the content of the test points of Chapter 12 summarized by the blogger. The software architecture column is being continuously updated. Welcome everyone to pay attention to me. If you have any mistakes or suggestions, you are welcome to put them forward in the comment area. Finally, I wish all the friends who are going to take the exam will pass every exam!