Research Paper on:
Object Oriented and Structural System Analysis

Unformatted Sample Text from the Research Paper:
the cover of Business Week in 1991, as the publication promised "Software made simple." Most analysts will not go so far as to say that object-oriented analysis is simple,  but most will say that it facilitates nearly any task that needs to be done at the application level. Structural and object-oriented analyses share several common traits, among them  the need to locate a specific location in application code. Decomposition Hierarchical decomposition provides a means for analyzing system effectiveness and locating the  point in application code that needs to be adjusted. Martin, Brown, DeHayes and Hoffer (2002) give a concise definition of hierarchical decomposition. The authors describe "the system" as  "a set of interrelated components" (Martin, et al., 2002; p. 318), and that any one of the components making up the larger system can itself be viewed as a system.  In turn, this subsystem can further be broken down into a more narrowly-defined set of components, which also may be able to be viewed as subsystems themselves. Martin,  et al. (2002) explain that there are five primary goals of hierarchical decomposition: * Break the larger system down into more manageable and understandable segments; * Analyze or change only  part of - rather than all - a system; * Allow chronological design or construction of a specific subsystem; * Allow targeted use of a specific subsystem; and * Allow  more independent operation of system components (p. 318). Understanding of the explanation and rationale is rather straightforward; full understanding of method can be  a different matter. Lee (n.d.) provides examples of functions and approaches illustrating at what levels systems are assessed. Lee (n.d.) provides a nontechnical explanation of high- and low-level