HW3: Chapter 10


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

Dependable processes enforce five attributes that a software must be in order to be dependable: auditable, diverse, documentable, robust, and standardized. These mean that the software development process must be understandable by those who were not part of the development, it must have redundant and diverse verification activities with documentation, it should not fail if one process fails, and it should have a comprehensive set of software standards that is clear to understand. As long as these attributes are incorporated, it is reasonable to assume that the software developed will 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.

The first principle of the ACM SE states that “Software engineers shall act consistently with the public interest.” This coincides with the job of a regulator in that the goal of regulation is to ensure that the software in question has been developed using the most effective software engineering practices. As long as one is adhering to the ACM SE, then the need for regulation should have no bearing on innovation.

The use of older methods of systems development from other systems is somewhat reasonable since they already work and if the older methods did not work, then regulators would have no standard to compare a new system to. However, regulators should not be able to unconditionally impose their views on systems development because technology is constantly evolving and with it comes new requirements for safety standards.

Comments

Post a Comment

Popular posts from this blog

HW6: Chapter 4

1.       4.5.  Using the technique suggested here, where natural language descriptions are presented in a standard format, write plausible user requirements for the following functions: o     An unattended petrol (gas) pump system that includes a credit card reader. The customer swipes the card through the reader, then specifies the amount of fuel required. The fuel is delivered and the customer’s account debited. Function: Accept customer input for the amount of gas they want and charge them for it Description: The system will accept a customer’s credit card, allow the customer to specify the amount of gas they want, dispense the gas, and charge the customer for the gas Inputs: Customer credit card information, amount of gas that the customer specified Source: The card reader Outputs: The amount of gas that the customer specified Destination: The customer’s car’s gas tank. Action: The customer will swipe their card through ...
Read more

HW24: Chapter 23

Image
23.6.  Figure  23.14  shows the task durations for software project activities. Assume that a serious, unanticipated setback occurs, and instead of taking 10 days, task T5 takes 40 days. Draw up new bar charts showing how the project might be reorganized.
Read more

HW11: Chapter 6

Image
6.4.  Draw diagrams showing a conceptual view and a process view of the architectures of the following systems: ·          A ticket machine used by passengers at a railway station. Conceptual view: Process view: ·          A computer-controlled video conferencing system that allows video, audio, and computer data to be visible to several participants at the same time. Conceptual view: Process view: ·          A robot floor-cleaner that is intended to clean relatively clear spaces such as corridors. The cleaner must be able to sense walls and other obstructions. Conceptual view: Process view:
Read more