HW9: Reflections

Comments

Post a Comment

Popular posts from this blog

HW10: Chapter 5

Image
Ex 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. Ex 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 available courses. Ex 5.7. Based on your experience with a bank ATM, draw an activity diagram that models the data processing involved when a customer withdraws cash from the machine. Ex 5.8. Draw a sequence diagram for the same system. Explain why you mi...
Read more

HW26: Chapter 24

Ex 24.6  Explain why program inspections are an effective technique for discovering errors in a program. What types of error are unlikely to be discovered through inspections? Program inspections are an effective technique for discovering errors in a program because getting another person to look over your code is invaluable. After working on the same code for a while and looking at it for so long, you become so accustom to it that you are blinded in a way. Someone who has never see the code before and has fresh eyes may see problems that you have over looked. Also this person may know of techniques or code that can make you code more efficient or effective. Two minds are better than one as they say. It is always a good idea for a program inspection to make sure your code it high quality. Some errors that may be discovered are bugs or defects. Or maybe you are using a component of your code ineffectively or they can maybe show you how to do something in a better way.
Read more

HW24: Chapter 23

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