The case analysis tool is
a useful resource to present a solution for a problem. The organization of the completed project
provides a readable narrative flowing from background information to a
recommendation. Specific sections of the
completed project may vary, with some being easier to follow than others.
This academic term’s
project was organized to provide the reader with an informative background to
the issue, identification and severity of the problem, alternate actions, and a
recommended solution. This analysis
process is logical and follows a reasonable sequence. A process not much different is used in my
workplace. The majority of course of
action (COA) briefings follow a similar process. This is especially true when the senior
leader selecting the COA may not be the subject matter expert on the specific
issue. Sufficient background information
must be provided to be informative without being overwhelming. Proposed COAs must have sound reasoning. Software model test cases also use a similar
process. Requirements and reasoning are
provided for context. Problems
identified through failed trials in test cases and their severity should be
thoroughly documented. Workarounds and
suggested solutions by the testers can assist with debugging. In each case, an important component of
problem solving is a good understanding of the problem from the beginning of
the process (Rusbult, 1989).
The parts of the case
analysis tool has differed from class to class.
Some classes have required sections discussing design overview and
decisions. These two sections can
overlap and present a challenge in separating the discussions. Another section often required is logic
design. This section can prove a
challenge for cases in which software development or modification is not a
significant factor in the proposed solution.
Solutions that make use of “off-the-shelf” software will not have much
discussion for this part. Problem
solving requires flexibility to handle the challenges in developing a solution
(Rusbult, 1989). This applies to the
case analysis tool as well. The format
and parts in the project should be customized for a particular problem. The right approach to address one problem may
not be right for another.
Referenecs:
Rusbult, C. (1989).
Strategies for Problem Solving. The American Scientific Affiliation. Retrieved from http://www.asa3.org/ASA/education/think/202.htm
No comments:
Post a Comment