CHAPTER 7 – ARCHITECTURE

--Originally published at Newbie Programmer

In the chapter 6 we analyze the big problems, and we learned that we can make the big problem into small pieces, but we need to know how these pieces fit together, and more important how to begin with this, and that’s why we need architecture
The architecture is a design structure that show us the most important parts of the project, and the relationship between the parts, that we already know because we used use case diagram, but it’s not clear how they interact.

To begin with the architecture, we need to retake the three concepts of making a good software from the first chapter. First, make sure your application does what the customer wants to do, second, apply the principles of object oriented, and third, make and maintainable reusable software.

First, we have feature list of what the system is suppose to do, but we need to choose what are the most important or architecturally significant, because those are the pieces we need to do first, and to know what are the pieces we need to do first we need to ask the there questions of architecture, first, if it is part of the essence of the system, the essence is those parts that we can’t imagine the product without them, second , if we don’t know what this feature means we need to pay attention to make sure its clear what is it about, and third, how do I do it, this are features that are hard or new programming tasks, we need to make sure we can deal with the problem and spend time with this features to not create problems in the future.

We know if we choose the right the important features if they create risk, because if we can’t finish one of these

cant build what we are suppose to build, and we don’t have to waste time deciding what to do first, because it doesn’t not matter what is first, the important its to do what are we supposed to do and begin with the architecturally significant ones and not get distracted with features that don’t reduce risk.
After doing the important features we need to do the next ones, we got a structure and we can begin with the common features that have relationship with the features that we already done, and with done this we are focusing in the things that reduce risk and create order.

This chapter is important, because shows you the importance of an architecture, because it’s like a building where you need to do first the hardest and important parts before doing easy or little things, because when you finish doing this its easily to attach new features or little details, and we accomplish what are supposed to do.

Photo by barnyz