8/28/2023 0 Comments Simple diagrams in architecture![]() ![]() They can be very fiddly and even buggy e.g. there’s one architecture diagram for Atlassian Marketplace with an old outdated box that can’t be deleted using the software it was diagrammed in, it just won’t allow that, for some reason. Most diagramming tools require you to use the mouse, pointing and clicking and dragging and drawing. We don’t see this very much and I think part of the problem is that architecture diagrams can be costly. Ideally, we’d have dozens of architecture diagrams - from various views, from various proposals, from various teams. Some teams and projects will have a diagram and point to it as “here is the architecture” - but it’s not the architecture, it’s just one particular view. It’s not wrong to have a big box representing your backend it’s just one way of viewing an abstraction. That means all architecture diagrams are views into an abstraction. The people focused on backend had the reverse - a huge box just labelled frontend!Īctual relationships do exist between systems (e.g. network calls, shared storage) but an architecture diagram can’t give all details without becoming the code it’s meant to represent. The people focused on frontend had things like Jira, Embedded Marketplace, Commerce, Provisioning, Atlassian Connect, then an arrow to a huge box - just labelled Marketplace backend. When my previous engineering manager joined the Atlassian Marketplace team, he asked everyone to draw an architecture diagram. Probably the best form of communication is a diagram, with boxes representing systems (or components) and lines representing relationships between them. The concept is also a way to communicate the idea of the project to stakeholders and clients, and it is often presented in the form of sketches, diagrams, or models.For the past few years I’ve been the most senior developer on my teams in Atlassian, in both position (Principal Engineer) and time (almost 9 years) - this means I usually take on the responsibility of managing our software architecture.Īrchitecture is the relationships between systems, which can be fairly tricky to talk about. They are used to inform the design decisions and shape the final outcome of the project. It is the starting point for the architectural process and encompasses the overall vision, goals, and objectives for the project.Ĭoncepts can be based on a wide range of factors such as function, location, context, history, culture, and sustainable principles. ![]() In architecture, a concept refers to the fundamental idea or inspiration that guides the design and development of a building or structure. Efficiency – The use of resources in the design and construction of buildings in an efficient way to minimize waste and cost.Safety and Security – The design of buildings to protect the safety and security of the people who use them.Human Needs – The design of spaces that cater to the physical, social and mental needs of the building’s users.Innovation – The use of new technologies and materials in the design and construction of buildings.Context – The relationship of a building to its surrounding environment, including its cultural, historical, and natural context.Accessibility – The ability of a building to be easily accessible and usable by people with disabilities.Sustainability – The use of environmentally friendly materials and construction techniques to minimize a building’s impact on the environment.Durability – The ability of a building to withstand the elements and maintain its structural integrity over time.Aesthetics – The visual appeal of a building, including its form, proportion, and ornamentation. ![]() Functionality – The primary purpose of a building and how it will be used by the people who occupy it.The basic concepts of architecture include: FAQ’s about architectural concept books What are the basic concepts of architecture? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |