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 that is present in the code. It's also feasible that the current climate at the company does not promote a blame-free mentality when it comes to finding and fixing errors during the peer review process. This could lead to an environment where certain developers are above reproach and their peers purposefully or otherwise overlook their faults to avoid conflict. Finally, if the company does not include developers from a diverse background, e.g. they all graduated from the same school around the same time, this may create knowledge gaps within the team that would otherwise be caught by a more diverse team.



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