This is the 26th day of my participation in the August More Text Challenge

What is the development view

Development View __ is the implementation view of the logical view, which describes the static organization structure of software in the development environment. It focuses on the organization and management of software modules.

The development view focuses on packages, including not only the source programs to be written, but also third-party SDKS and off-the-shelf frameworks that can be used directly, class libraries, and the system software or middleware on which the developed system will run. There may be some mapping between the development view and the logical view: for example, the logical layer typically maps to multiple packages.

Its general architecture is shown below:

In most cases, the internal requirements of the development architecture are related to several factors: development difficulty, software management, reusability and versatility, and limitations imposed by toolsets and programming languages. The development architecture view is the basis for activities such as requirements allocation, team work allocation (or team organization), cost assessment and planning, project schedule monitoring, software reuse, portability, and security. It is the foundation on which product lines are built.

Rules for developing views

  • block
  • grouping
  • visibility

Develop the structure of the view

The style of the development view is usually hierarchical, with each layer providing well-defined interfaces to the next, and the lower the level, the more generic the better.

The meaning of developing views

The development view is the foundation for requirements allocation, facilitating work assignments for development teams, facilitating cost assessment and planning ahead, monitoring project progress, software reuse, portability, and security reasoning. From the development view, it is easy to figure out the allocation of project developers.

The development view of software architecture should provide practical guidance for developers. Any design decisions that affect the overall situation should be completed by the architecture design. If these decisions are “missed” in the later stage of large-scale parallel development, they may lead to the occurrence of a large number of “temporary decisions made by programmers”, and the software quality will inevitably decline and even lead to project failure.

The practical application

In practice, the development view adds a lot of content to the logical view, such as a lot of interfaces, helper classes, and so on.

A well-designed development view should satisfy the following requirements:

  • All of its code and all of its binary deliverables can be found through the logical architecture element
  • For each code source file, you can find the logical schema element to which it belongs
  • With each binary deliverable, you can find out which logical architectural elements it integrates

conclusion

That’s a brief introduction to developing views, and I hope it helps!

~

Thanks for reading!

~

Learn interesting knowledge, meet interesting friends, shape interesting soul!

Hello everyone, I am the author of “programming Samadhi”, I am king Yi, my public account is “programming Samadhi”, welcome to pay attention, I hope you can give me more advice!

You come, with expectations, I have ink to welcome! You return, no matter gain or loss, only to yu Yun give each other!

Knowledge and skills should be paid equal attention to, internal force and external power should be repaired simultaneously, theory and practice should grasp both hands, both hands should be hard!