Architecture « Business Database Solutions (BDS)

Architecture

Architecture

When you think of architecture, you often think of a bridge. Bridges connect two points together allowing for the movement of people, cars, or resources. Bridges need to be well built and should be wide enough to accommodate the quantity of users. Building a bridge requires careful planning so you understand how to build it before you start building.

In the internet world, you can think of software applications as bridges connecting users together and allowing the flow of information. The actions of User Requirements, Wireframing, Design and Prototyping are all under the heading of “Determining What to Build”. We now enter the territory of “How to Build It”.

The Architecture of Software Development

Software applications, as a standard rule, have the job of moving data from one user to another user or, from one point to another point. Developing a software application could be best compared to building a bridge. Normal bridges have two points of entry/exit whereas software applications can have several points of origin and destination. Software bridges can be even more complicated than an architectural bridge.

The number of users expected and where they are located might determine how far the bridge has to go, and how many lanes it needs to accommodate the users.

The type of information that needs to move across the bridge, and volume of data being moved might determine the materials we use in building the bridge.

Knowing where the data is going, and how heavy the load will be, and therefore what “materials” we need to use, is what allows a higher degree of accuracy in estimation, so budgets can be made and met. Estimates can be given before this point, but not quotes.

Ready to Get Started?

Our team is ready to begin your project

Let's Talk

Charles Mitchell, CEO
3715 Market Street
Montrose, CA 91208
818.281.6370
cmitchell@businessdatabasesolutions.com

Ready to Get Started?

Our team is ready to begin your project


Get Started