Posts

Showing posts from September, 2019

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...

HW8: Chapter 2

Ex 2.1 Suggest the most appropriate generic software process model that might be used as a basis for managing the development of the following systems. Explain your answer according to the type of system being developed: A system to control antilock braking in a car Since this system could be the difference between someone living and dying, I would have to say water fall software process model. Carefully thought out requirements with a focus on safety need to be put into place before software development begins. A virtual reality system to support software maintenance Incremental software process model since it would most likely be a team working on this together all changes would be mapped out nicely and easy to see and communicate about as well as build off of other team members changes.  A university accounting system that replaces an existing system Integration and configuration because this would allow for software developers to re use the old code from the prev...

HW7: Reflections

All the reading for this homework all have to do with memory and creating new things. The article titled "The Magic Number Seven" talks about some funny things that go on in our brains when we try to remember stuff and how the human brain's memory is not perfect. There is no true way to tell what our brains can and cannot remember. Everyone's brains are so different and what we remember has to do with our past experiences. I think that this is for sure true because my girl friend of almost seven years always seems to remember little, tiny things that I have no recollection of. Like what outfit we were both wearing on a random date a few years ago.  This article also talked about how when we have too many things to do or ideas out brains cannot handle them all and we start forgetting them. The solution to this problem which we can apply to our software engineering practices is breaking tasks down into parts and give it structure so we do not forget everything and compl...

HW5: Reflections

The Therac-25 article showed the very scary reality of what can happen when software engineers can be overconfident and not be extra careful when designing software for equipment that involves other peoples lives. Radiation machines need to be handled with extra care because they can be the determinate on whether someone lives or dies and radiation treatment is so expensive the equipment needs to be top notch. Like most people, I know a lot of people who have had cancer and have had to get radiation treatment. So, these accidents were especially scary and disturbing to read about. I cannot imagine the horror of a family member or someone I know getting radiation treatment and them feeling an electric shock or a "red hot sensation." And then that person having horrible radiation burns. The worst part is that the AECL knew about the first accident where the sixty-one year old woman had to have her breast removed and lost use of her shoulder and arm AND was in constant pain. The...

HW6: Chapter 4

Ex 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: 1. 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: Give gas to customer, accept and charge the customer's credit card, and print a receipt.   Description:  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. Inputs: Amount of gas that the customer wants and the customer's credit card information Source: credit card machine/reader and either screen where the amount of gas the customer wants is inputted or i guess the amount of gas is determined when the customer re-racks the gas nozzle. Outputs: amount of g...