Jekyll2019-08-08T02:28:14+00:00/feed.xmlIn this blog I will write about the topics I encounter in my journey into Software Engineering2019-08-09T17:00:00+00:002019-08-09T17:00:00+00:00/software/2019/08/09/fallacies<p>Hello! In this post we will briefly explore the so called <code class="highlighter-rouge">Fallacies of Distributed Computing</code>, that were first drafted by <a href="https://en.wikipedia.org/wiki/L._Peter_Deutsch">Peter Deutsch</a> in 1994 while working at <a href="https://en.wikipedia.org/wiki/Sun_Microsystems">Sun Microsystems</a>, and 25 years later are still relevant.</p> <p>The <code class="highlighter-rouge">Fallacies of Distributed Computing</code> are a series of 7 assumptions that inexperienced software architects are likely to make when designing distributed systems, these assumptions become problems and correcting them can be very expensive the longer the project is allowed to continue while ignoring this issues.</p> <p>In 1997, <a href="https://en.wikipedia.org/wiki/James_Gosling">James Gosling</a> included a new fallacy, taking the total to 8:</p> <ul> <li><strong>The Network is Reliable</strong></li> <li><strong>Latency is Zero</strong></li> <li><strong>Bandwidth is Infinite</strong></li> <li><strong>The Network is Secure</strong></li> <li><strong>Topology Doesn’t Change</strong></li> <li><strong>There is one Administrator</strong></li> <li><strong>Transport Cost is Zero</strong></li> <li><strong>The network is Homogeneus</strong></li> </ul> <p>That’s about it for today’s topic. Peace.</p>

Hello! In this post we will briefly explore the so called Fallacies of Distributed Computing, that were first drafted by Peter Deutsch in 1994 while working at Sun Microsystems, and 25 years later are still relevant.

2019-08-02T17:10:00+00:002019-08-02T17:10:00+00:00/software/engineering/2019/08/02/guide-swebok<p>Hello there! Welcome to the first entry in this blog dedicated to all things related to Software Engineering. Today’s topic, fittingly, is foundational to this area.</p> <p>The <code class="highlighter-rouge">SWEBOK</code>, or <code class="highlighter-rouge">Software Engineering Body of Knowledge</code> are the generally accepted principles that govern the practice of Software Engineering worldwide. It is published as a guide or technical report by the <code class="highlighter-rouge">IEEE Computer Society</code> and has become an <code class="highlighter-rouge">ISO</code> standard. In 2013 version 3 of the guide was published and can be <a href="https://www.computer.org/education/bodies-of-knowledge/software-engineering">downloaded for free</a>.</p> <p>A total of 15 knowledge areas are found on the guide:</p> <ul> <li><strong>Software Requirements</strong> Elicitation, analysis, specification, validation and management of software requirements in the whole lifecylce of a software product.</li> <li><strong>Software Design</strong> The process of defining the architecture, components, interfaces and other characteristics of a system.</li> <li><strong>Software Consruction</strong> The creation of software through coding, verification, unit testing, integration testing and debugging.</li> <li><strong>Software Testing</strong> The verification that a program provides expected behaviors on a finite set of test cases.</li> <li><strong>Software Maintenance</strong> Planning for postdelivery operations, ensuring maintainability of code and documentation and logistics for transition activities.</li> <li><strong>Software Configuration Management</strong> The functional and physical characteristics of hardware and software that are documented and achieved in a software product.</li> <li><strong>Software Engineering Management</strong> Planning, coordinating, measuring, monitoring, controlling and reporting to ensure effective and efficient software delivery.</li> <li><strong>Software Engineering Process</strong> Requirements, design, construction, testing and configuration management processes for development, maintenance and operation of software.</li> <li><strong>Software Engineering Models and Methods</strong> Structures to make software engineering systematic, repeatable and success-oriented.</li> <li><strong>Software Quality</strong> Capability of software product to satisfy its requirements, for this to happen, the requirements must accurately represent the needs, wants and expectations of stakeholders.</li> <li><strong>Software Engineering Professional Practice</strong> Knowledge, skills and attitudes that software engineers must possess to practice software engineering in a professional, responsible and ethical manner.</li> <li><strong>Software Engineering Economics</strong> Aligning software technical decisions with the business goals of the organization, to ensure sustainably staying in business.</li> <li><strong>Computing Foundations</strong> All software engineers must have a good underderstanding of the computer and its underliying principles of hardware and software.</li> <li><strong>Mathematical Foundations</strong> Mathematics helps engineers understand the formal logic that computers and programs use to work.</li> <li><strong>Engineering Foundations</strong> The application of systematic, disciplined, quantifiable approach to structures, machines, products, systems or procesess.</li> </ul> <p>All the above summaries have been adapted or copied from the introduction section of each chapter in the <code class="highlighter-rouge">SWEBOK</code>.</p> <p>It should be noted that the <code class="highlighter-rouge">SWEBOK</code> should be used as a guide and a reference, and that each of the knowledge areas described above have a vast ammount of published literature, and each topic has many subtopics that will be explored in future entries to this blog. All of these topics are also active areas of research.</p> <p>Finally, it should also be noted that the <code class="highlighter-rouge">SWEBOK</code> makes no asumptions about the specifics of types of processors, operating systems, programming languages, development methodologies and practices, etc, because its objective is to be as general as possible.</p> <p>That’s about it for today’s topic, if you would like to add or correct anything on this blog feel free to send an email (or even better, fork the <a href="https://github.com/Ragnarok540/Ragnarok540.github.io">GitHub repository</a> and make a pull request with your changes!). Peace.</p>

Hello there! Welcome to the first entry in this blog dedicated to all things related to Software Engineering. Today’s topic, fittingly, is foundational to this area.