A debate is raging at the IT consulting firm where you work.
Some staff members believe that it is harder for experienced analysts to learn object-modeling techniques because the analysts are accustomed to thinking about data and processes as separate entities.
Others believe that solid analytical skills are easily transferable and do not see a problem in crossing over to the newer approach.
What do you think, and why?
An experienced systems analyst should already be familiar with the most popular systems analysis methods: structured analysis, object-oriented analysis, and agile methods. Although structured analysis “represents the system in terms of data and the processes that act upon that data.” (Systems Analysis and Design, p.18) and object-oriented analysis “views the system in terms of objects that combine data and processes.” (p.18), a solid analyst should be able to learn and utilize the benefits of O-O without too much difficulty.
According to A Comparison of Structured Analysis and Object-Oriented Analysis – An Experimental Study (Falessi et al., 2007) “One of the main benefits of the O-O approach is that it provides a continuum of representation from analysis to design to implementation, thus engendering a seamless transition from one model to another.” A structured design may be more familiar, however, the long-term benefits of an O-O approach should prove attractive to the experience systems analyst.
Falessi, D., Cantone, G., & Grande, C. (2007). A Comparison of Structured Analysis and Object-Oriented Analysis—An Experimental Study. In ICSOFT 2007—2nd International Conference on Software and Data Technologies, Proceedings (p. 221).
Tilley, S. (2017). Systems Analysis and Design (12th ed.). Cengage.