Aligning the software to the business before the hardware (December 2017)

Abstract— The main objective of this document is to indicate the importance of first aligning the
software to the hardware that allows the business to save resources in infrastructure, which will allow it
to respond effectively to requests made to the system and allow natural scalability vertically in its
different applications.

I. INTRODUCTION

HIS document focuses on how in business today it is necessary to take into account the number of
requests they expect to receive in order to solve them. An important part is to understand that you
cannot first mount the infrastructure assuming the way in which the application behaves, it is necessary
to perform the corresponding tests to determine the necessary requirements so that it can be executed
and respond to the needs of the business.

II. BUSINESS AND SOFTWARE

In today's world, the vast majority of businesses move in the web world, with different applications
which should be aligned to the business, allowing the company to be more agile. The importance of
software for the operation of the business is crucial is here where we must emphasize the use of a good
software architecture that allows us to scalability to a future we should not take for granted that the
business will not grow on the contrary you should always have a vision in the future that allows us to
continue growing in the right way. Software is a double-edged sword that can be deceiving does not
always work as we expect it to work and works correctly is not always optimized this raises the cost in
spending on our infrastructure, creating an unsustainable application that with the step of time as the
business progresses will require more equipment expenses so that it continues to function as expected.
[1]

The hardware is an important part of the company which allows us to generate our structure in which all
our software requirements will be assembled, we should not expect this to work independently and this
should work as a unit in which the software uses the hardware as a means to achieve its objective. [2]

III. HARDWARE UNDER SOFTWARE

Put the hardware not as a priority of the organization, in the IT planning if we start from the structure as
it normally works the construction of a building we make an error if we conceive the software as a
normal construction process we are preparing a structure without knowing how many people will live In
our building, in addition to building a building that allows a number of people to stay, this will reach the
point where it will not support more floors and the construction will collapse. Always look that the
software needs specific hardware requirements, if you need to create always start by optimizing the
software and then add hardware. As a philosophy for a natural scaling of our software we prioritize the
vertical sense to the horizontal, making vertical software reference and horizontal to the hardware. [3]

IV. RESULTS

This research clearly shows the importance of first thinking about software applications and then
creating an infrastructure that is not overvalued and saves resources for the organization. This practice
is widely used and allows the generation of applications with great scalability and adaptability, always
working in the most optimal way.

V. DISCUSSION

Be clear about the importance of first turning the business before proposing a software architecture,
this allows the correct use of technologies to solve the specific problem for which it was created. A
powerful hardware infrastructure can be acquired simply with resources but it is not always the solution
there is a point where if you do not have a robust application the hardware will not do anything for the
company to make an unnecessary expense and can be resulted in the way The most optimal approach is
always to first seek to refactor parts of the code, use appropriate architectural styles and also the use of
different technologies depending on the context.
REFERENCES

[1] K. Nagesh y J. K.J, «Export of Software and Business Process Outsourcing from Developing Countries
Lessons from the Indian Experience,» Asia-Pacific Trade and Investment Review, New Delhi, 2005.

[2] Y. Ghanam y S. Carpendale, «A Survey Paper on Software Architecture Visualization,» Canada.

[3] R. C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship, San Francisco New York:
Practice Hall, 2008.