{"id":36782,"date":"2016-08-20T18:04:28","date_gmt":"2016-08-20T23:04:28","guid":{"rendered":"http:\/\/www.katiachumakova.com\/?p=43"},"modified":"2016-08-20T18:04:28","modified_gmt":"2016-08-20T23:04:28","slug":"the-story-behind-software-engineering","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/the-story-behind-software-engineering\/","title":{"rendered":"The story behind software engineering."},"content":{"rendered":"
\t\t\t

In the 60\u2019s programmers had to write their programs and could not test them, they were sent to technician and processed. <\/p>\n

The first widely used programming language was Fortran \u2013 released in 1957 for mathematical and scientific computing, then Cobol, in 1962 for business applications. <\/p>\n

One of the most important transitions was to use a time-sharing model instead of batch processing, which was and industrial process.<\/p>\n<\/div>\n\t\t<\/div>

\n\t

And thus...<\/h3>

THE SOFTWARE CRISIS<\/h1>\t\t\t\t\t
\n\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div><\/div><\/div>
\n
\n\n\t\n\t\t\n\t\t
\n\n\t\t\t\t\t\t\n\t\t\t\t<\/span>\t\t\t<\/div>\n\t\t\t\n\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\tLate\t\t\t\t\t\t\t\t\t\t\t<\/h5>\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\n\t\n\t\t\n\t\t
\n\n\t\t\t\t\t\t\n\t\t\t\t<\/span>\t\t\t<\/div>\n\t\t\t\n\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\tOver Budgeted\t\t\t\t\t\t\t\t\t\t\t<\/h5>\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\n\t\n\t\t\n\t\t
\n\n\t\t\t\t\t\t\n\t\t\t\t<\/span>\t\t\t<\/div>\n\t\t\t\n\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\tLow Quality\t\t\t\t\t\t\t\t\t\t\t<\/h5>\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\n\t\n<\/div>\n<\/div><\/div>
\t\t\t

Even though software engineering changed the world, one fourth of software projects failed, so the crisis stayed throughout the 60\u2019s, 70\u2019s and in the 80\u2019s..
\nIn 1968 NATO organized a software conference that forked the discipline of Software Engineering (Up to that point hardware was the main focus).
\nThere were 3 main problems to be addressed:<\/p>\n<\/div>\n\t\t<\/div>

\n
\n\n\t\n\t\t\n\t\t
\n\n\t\t\t\t\t\t\n\t\t\t\t<\/span>\t\t\t<\/div>\n\t\t\t\n\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\tEliminate Human Error\t\t\t\t\t\t\t\t\t\t\t<\/h5>\n\t\t\t\t\n\t\t\t\t\t\t\t\t\t

Apply math to programming & develop formal methods, this was very expensive. People assumed that if they did enough math they wouldn\u2019t need tests. <\/p>\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\n\t\n\t\t\n\t\t

\n\n\t\t\t\t\t\t\n\t\t\t\t<\/span>\t\t\t<\/div>\n\t\t\t\n\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\tEliminate Internal Complexity\t\t\t\t\t\t\t\t\t\t\t<\/h5>\n\t\t\t\t\n\t\t\t\t\t\t\t\t\t

The source code of projects became really complex, BUT! Most complexity is essential complexity: Not complexity in the solution, but complexity in the problem.<\/p>\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\n\t\n\t\t\n\t\t

\n\n\t\t\t\t\t\t\n\t\t\t\t<\/span>\t\t\t<\/div>\n\t\t\t\n\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\tEliminate Project Variability\t\t\t\t\t\t\t\t\t\t\t<\/h5>\n\t\t\t\t\n\t\t\t\t\t\t\t\t\t

Eliminate the craftsmanship, and create an industry with something like assembly lines. This meant standardizing the design process, which was impossible because software is not a defined process, it involves context.<\/p>\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\n\t\n<\/div>\n<\/div><\/div>

\n\t

All of these attempts<\/h3>

FAILED...<\/h1>\t\t\t\t\t
\n\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div><\/div><\/div>
\t\t\t

So we found an alternative strategy:
\nSoftware as an empirical process<\/p>\n

AGILE:<\/p>\n

1.\tObservation
\n2.\tHypothesis
\n3.\tExperiment<\/p>\n<\/div>\n\t\t<\/div>

\n\t

Soooo\u2026 <\/h3>

basically, the Scientific Method.<\/h1>\t\t\t\t\t
\n\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div><\/div><\/div>
\t\t\t

In the 70\u2019s, modular pieces where introduced, which communicated via interfaces. Projects could be fragmented which became a key idea in systems thinking. <\/p>\n

In the 80\u2019s Object Oriented programming was introduced and they could be independent and hold specific states. This was the abstraction that allowed programmers to interact with something that almost physical with Graphical user interfaces (GUI\u2019s). <\/p>\n

Due to computing power increasing following Moore\u2019s Law (The idea that thepower of integrated circuits doubled every two years), engineers stopped being careful about the amount of memory and processing power used in code and this led to \u201cwasteful\u201d software. <\/p>\n

In 1989, the world wide web was developed by Tim Berners-Lee and in the 90\u2019s the browser was created with graphical access.
\nIn the 90\u2019s developers grew tired of only having access to only executable binaries and not the real source code, so open-source rose in popularity and has since become the major reason for software engineering productivity. <\/p>\n

Then came the development of commodity computers and the \u201ccould\u201d that allow applications to be updated and accessed in real time. <\/p>\n

After that came mobile development with smartphones and tablets. <\/p>\n<\/div>\n\t\t<\/div>

\t\t\t

SOURCES:<\/p>\n

Baruco 2012: A short history of Software Engineering by Paolo Perrotta <\/a>
\nA Brief History of Software Engineering <\/a>
\n Image Source <\/a><\/p>\n<\/div>\n\t\t<\/div><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"

In the 60\u2019s programmers had to write their programs and could not test them, they were sent to technician and processed. The first widely used programming language was Fortran \u2013 released in 1957 for mathematical and scientific computing, then Cobol, in 1962 for business applications. One of the most important transitions was to use a … Continue reading The story behind software engineering.<\/span><\/a><\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,4],"tags":[134,25],"class_list":["post-36782","post","type-post","status-publish","format-standard","hentry","category-blogs","category-syndicated","tag-mastery-topics","tag-tc1019"],"_links":{"self":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/36782","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/comments?post=36782"}],"version-history":[{"count":3,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/36782\/revisions"}],"predecessor-version":[{"id":37376,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/36782\/revisions\/37376"}],"wp:attachment":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/media?parent=36782"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/categories?post=36782"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/tags?post=36782"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}