Pirate 1: Why answer pirates create treasure maps?
Pirate 2: I conclude not know.
Pirate 1: So they have power to find their gold.
Yes, that was a disingenuous joke, but it does illustrate a spot. Pirates are known for drawing lay by maps to their most prized lunacy. These documents detail the decisions pirates made in quiet to hide and find their chests of gold. The delineate allows them to trace the steps they took originally to hide their stock so that they may return. As software engineers, programmers, and architects we stand in want of to treat software implementations much like our garner chest.
Why is software like a valuable chest?
It cost money, time, and money to develop (Usually)
It can cause to be or save money, time, and supplies (Hopefully)
If we operate under the arrogating that software is like a funds chest then wouldn't make understanding to document the steps, rationale, concerns, and decisions over how it was designed?
Pirates are evident for documenting where they hide their husband. Shouldn't we as creators of software perform the same? By documenting our design decisions and cause behind them will help others be able to understand and maintain implemented systems. This can only be done if the design decisions are correctly mapped to its answering. implementation. This allows for architectural decisions to have existence traced from the conceptual model, architectural design and eventually to the implementation. Mapping gives software professional a means to trace the reason why specified areas of code were developed verses other options.
Just like the pirates we poverty to able to trace our steps from the scare of a project to its implementation, in the same manner that we will understand why particular choices were chosen. The traceability of a software implementation that indeed maps back to its originating design decisions is above all price. for ensuring that architectural drifting and eating away does not take place. The drifting and corrosion is prevented by allowing others to mean the rational of why an implementation was created in a particular manor or methodology
No comments:
Post a Comment