HW13: Chapter 8

Chapter 8: Software Testing

This chapter went over development testing, test-driven development, release testing, and user testing. The first question below was interesting to do as the scenarios in the text had user interactions and that made it easier to visualize how the system may be used. The wilderness weather system does not interact with a user, therefore, the scenario revolved around what the system might encounter in daily operation. 

 8.7. Write a scenario that could be used to help design tests for the wilderness weather system.

 A particular wilderness weather system is to be accessed by satellite uplink. The wilderness system collects its readings from the Anemometer, Barometer, thermometers, rain, sunshine, and visibilities gauges. Due to inclement weather, the wilderness weather system has not transmitted this data over the satellite link. The weather in the area of this system is very frigid with low visibility and has had to pause instrument operation to generate sufficient power via the wind and solar systems.
The diagnostic tests for the system indicate the system has had a longer than expected time between relaying information through the satellite link. In other systems, this was often due to a faulty antenna, but the weather may also play a role.

The Anemometer has indicated a dramatic increase in wind speeds, possibly due to an extreme weather event and activated a protocol to protect the instruments and power generating equipment from damage.


The system determined through barometric pressure, thermometer, and sunshine readings (or some other way?) that the extreme weather event likely passed. Therefore, the power generating equipment and instruments were reactivated.

8.10. A common approach to system testing is to test the system until the testing budget is exhausted and then deliver the system to customers. Discuss the ethics of this approach for systems that are delivered to external customers.

This depends largely on the initial budget allocated for testing, the system's use/purpose, and what testing was able to be completed. 

 First, the budget must be realistic for testing purposes to start with. Assuming that the initial budget was reasonable, the system's use must be considered. If the system is used in a manner where lack of testing may result in significant harm to a person, then it is immoral to deliver this product knowing it is unsafe. A key component of this question is communication with the customer. If, as a developer, you believe the testing process has not adequately tested the product, it is incumbent upon you to communicate that to the customer clearly. If the customer requirements are not tested/met then it is unethical to deliver a product that does not meet these agreed-upon requirements unless the customer explicitly agrees to the change. 

Comments

Post a Comment

Popular posts from this blog

HW10: Chapter 5

Image
System Modeling 5.3. You have been asked to develop a system that will help with planning large-scale events and parties such as weddings, graduation celebrations, and birthday parties. Using an activity diagram, model the process context for such a system that shows the activities involved in planning a party ( booking a venue, organizing invitations, etc.) and the system elements that might be used at each stage. This diagram does not include food, drinks, decorations, chairs, equipment, DJ, photography, or the other myriad of things possible at a party. It simply goes through the process of determining the size, date, venue, guest list, and invitations.     5.5 Develop a sequence diagram showing the interactions involved when a student registers for a course in a university. Courses may have limited enrollment, so the registration process must include checks that places are available. Assume that the student accesses an electronic course catalog to find out about a...
Read more

HW11: Chapter 6

Image
This is my take on the conceptual and process views of 3 different machines. I found myself having difficulty distinguishing between the two in some instances. I seemed to want to go directly to the process view and skip the conceptual view altogether. I'd like to find some simple, real-world examples of conceptual and then process view diagrams of the same system to see the differences. 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. A computer-controlled video conferencing system that allows video, audio, and computer data to be visible to several participants at the same time. 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. %3CmxGraphModel%3E%3Croot%3E%3CmxCell%20id%3D%220%22%2F%3E%3CmxCell%20id%3D%221%22%20parent%3D%220%22%2...
Read more

HW26:Chapter 24

24.6. Explain why program inspections are an effective technique for discovering errors in a program. what types of errors are unlikely to be discovered through inspections? Program inspections are essentially peer reviews of code that take place during development. Teams collaborate and walk through code line-by-line in search of bugs, exceptions, erroneous conditions, in house compliance issues, as well as things the team deems worthy to discuss. They are considered good practice because they bring together a diverse set of engineers to review the code and it can also help create a company culture that understands the importance of acknowledging errors and moving forward to improving. Sommerville states that during program inspections, there is broad use of checklists to help guide the process. These checklists are typically language-based and cover a wide range of common errors found in the past. This could lead to a reliance on such lists and overlook some more technical issue...
Read more