Discussion 3

***All discussions need to be 4-6 sentences***

 

1“Use Case Description versus Activity Diagram”  Please respond to the following:

• Compare a use case description and an activity diagram. Devise a scenario in which you would use a case description, and devise a scenario in which you would use an activity diagram.
• Consider a system needed to store information about computers in a computer lab at a university, such as the features and location of each computer. Ascertain the domain classes that might be included within the domain model. Discuss whether or not you believe an entity-relationship diagram (ERD) would be a suitable model.

 

 

2“CPUs and Programming” Please respond to the following:

• From the first e-Activity(below), identify the following CPUs: 1) the CPU that resides on a computer that you own or a computer that you would consider purchasing, and 2) the CPU of one (1) other computer. Compare the instruction sets and clock rates of each CPU. Determine which CPU of the two is faster and why. Conclude whether or not the clock rate by itself makes the CPU faster. Provide a rationale for your response.
• From the second e-Activity, examine two (2) benefits of using planning techniques—such as writing program flowcharts, pseudocode, or other available programming planning technique—to devise and design computer programs. Evaluate the effectiveness of your preferred program planning technique, based on its success in the real world. Provide one (1) example of a real-life application of your preferred program planning technique to support your response.

 

eActivity:

• Use the Internet to research the various features of the Central Processing Units (CPU) of one (1) or two (2) computers. Be prepared to discuss.
• Select your preferred computer program planning technique, such as flowcharting or pseudocode. Use the Internet and Strayer Library to research whether or not the selected technique has proven to be successful. For example, take note of whether or not there has been any research that indicates labor hours and dollars that have been saved due to programs initially being written with a lower number of programming errors. Be prepared to discuss.