Software Development and Engineering Blog


HW28: Chapter 25

Sam Word | 21 Nov 2017

HW27: Chapter 24

Sam Word | 16 Nov 2017

HW19: Team Progress II

Sam Word | 14 Nov 2017

HW25: Chapter 23

Sam Word | 09 Nov 2017

HW24: Chapter 22

Sam Word | 06 Nov 2017

HW22: Chapter 21

Sam Word | 02 Nov 2017

HW19: Team Progress I

Sam Word | 31 Oct 2017

HW21: Chapter 20

Sam Word | 26 Oct 2017

HW20: Chapter 19

Sam Word | 24 Oct 2017

HW18: Chapter 18

Sam Word | 18 Oct 2017

HW17-B: Chapter 17

Sam Word | 11 Oct 2017

HW17-A: Chapter 16

Sam Word | 08 Oct 2017

HW16: Chapter 9

Sam Word | 05 Oct 2017

HW15: Chapter 15

Sam Word | 02 Oct 2017

HW14: Testing Reflections

Sam Word | 28 Sep 2017

HW13: Chapter 8

Sam Word | 28 Sep 2017

HW12: Mythical Man Month

Sam Word | 26 Sep 2017

HW11: Chapter 6

Sam Word | 21 Sep 2017

HW10: Chapter 5

Sam Word | 13 Sep 2017

HW9: Reflections

Sam Word | 12 Sep 2017

HW8: Chapter 2

Sam Word | 12 Sep 2017

HW7: Reflections

Sam Word | 07 Sep 2017

HW6: Chapter 4

Sam Word | 07 Sep 2017

HW5: Reflections

Sam Word | 05 Sep 2017

HW4: Chapters 11 & 12

Sam Word | 30 Aug 2017

HW3: Chapter 10

Sam Word | 28 Aug 2017

HW2: Responses

Sam Word | 27 Aug 2017

HW1: Chapter 1

Sam Word | 24 Aug 2017

HW0: Introduction

Sam Word | 23 Aug 2017

HW3: Chapter 10


28 Aug 2017

10.6

Explain why it is reasonable to assume that the use of dependable processes will lead to the creation of dependable software.

Software that was created using dependable software processes means that the software was created using standardized and robust techniques, and redundant and diverse validation and verification. Dependable processes are also auditable, meaning that people not a part of the process can understand the process as well, so that others can verify that standards were enforced during software development. Also, dependable processes are documentable so that the process documents what activities are to be in the process, and documentation is made during those activities.

Assuming that software created using dependable processes is similar to assuming that a building is dependable if it was created using dependable processes. We generally determine whether or not buildings are safe if they were built using dependable materials, the building was built to meet certain codes, and the builders used proper construction techniques. Software is created using much different processes, but if those processes are dependable, then the software should also be dependable.

10.10

It has been suggested that the need for regulation inhibits innovation and that regulators force the use of older methods of systems development that have been used on other systems. Discuss whether or not you think this is true and the desirability of regulators imposing their views on what methods should be used.

Innovation in software requires regulation. Creating software, unlike solving physical science problems, is bound only to a set of requirements made up by humans. Creating software to do something new is possible, but if that software is not dependable, then I believe that the software is not truly an innovative piece of software. Sure, the software may introduce a novel concept, but if it’s not dependable, then the software can cause frustration, economic loss, or physical damage. Solutions that can introduce more problems, are often not solutions at all, and therefore not innovative.

Though they may feel restricting at times, regulations are often in the best interests of creating dependable software, and generally desirable. However, not all regulations may be desireable. Our ideas of right and wrong change, and our standards of safety change as we learn more about health and the environment around us. In order for a regulation to be desirable, it must be periodically revisited in order to reflect the most recent standards for health, safety, ethics, environmental impact, etc. Out of date regulations can be detrimental to our society because they allow for potentially unsafe software to be in use.