History of Arrays

It is typically well known that questions regarding arrays will be asked during a software engineer position interview. Yet, what is the connection between software engineering and arrays?
In the 1968 NATO Software Engineering Conference, it was the debut of the term of “software engineering”. Its debut was to stimulate thoughts during the “software crisis” then.
Software engineering is understood as a profession to develop software, which endeavors to treat it as a formal process more like traditional engineering. The job scope is to design, implement, and modify software so as to produce affordable and maintainable and speedier building software of higher quality. It differs from common engineering as it comprises of crafting an application, refining and polishing it instead of a series of logic instructions in common engineering. In this field, before the first line of managed code is written, the whole design process has to be formally managed. One of the famous disasters in the noble world of software engineering is the case of Ariane 5. It was a rocket system for delivering satellites into orbit. Ended up, it was blown up in June 1996, 40 second after taken off due to an arithmetic overflow bug and that the system was not fully tested.
To mingle well in the world of software engineering, one has to excel in programming languages. One of which is the arrays.
The arrays can be defined as a series of elements of the same type. They are placed in a contagious memory locations so that they can be referred separately. This is by adding an index to a unique identifier. For instance, 5 values of type int in the arrays can be stored without the need to declare 5 different variables, each one with a different identifier. Alternatively, 5 values of the same type int can be stored with a unique identifier. Isn’t this of great convenience?
The arrays come with some unique elements. One of which is called the Zero-based indexing. The first element of an array a[ ] is called [0} and the second one is a [1] and the list continues. Other characteristics include arrays length and memory representation. The memory representation occurs when one uses new to create an array, Java will reserve space in memory for it. This process is called memory allocation. Bounds checking and setting array values at compile time are the elements which complete the arrays.
So you think you want to be a part of the world of software engineering? Please master the arrays!