This paper examines the evolving role of the systems analyst as a hybrid professional who must balance deep technical knowledge with strong business acumen. It traces the shift in organizational control over IT from the CIO to line-of-business managers, and explains how this has redefined what systems analysts are expected to deliver. The paper discusses key frameworks including the Systems Development Lifecycle (SDLC), Business Process Management (BPM), and Service-Oriented Architectures (SOA), and argues that modern systems analysts must function primarily as business process experts and change agents. Special attention is given to identifying the Voice of the Customer and managing organizational change as foundational steps in any successful systems analysis and design effort.
The role of the systems analyst is unique in that it is a hybrid one. Systems analysts are highly skilled in IT technologies and their applications to core business problems, yet they are also excellent analysts of business issues and how those issues can be resolved using IT-based solutions. At the center of the systems analyst's role is the ability to resolve business-related problems and accomplish line-of-business objectives by using information technologies to redefine business processes so they become more efficient and more aligned with a company's strategic objectives.
As a result of this core orientation, systems analysts must master the Systems Development Lifecycle (SDLC) and Business Process Management (BPM) in addition to core IT concepts such as how systems integrate with one another, how they are programmed, and the future interfacing and programming standards necessary to support the accomplishment of line-of-business objectives.
In many companies the role of the systems analyst is also a highly political one, requiring the analyst to span the core technologies of a company and its many internally focused IT agendas, tasks, and roadmaps — all measured and defined in their own language and acronyms. Juxtapose this with the need for the systems analyst to treat others in the company requiring their expertise as customers, and the essence of the conflicting roles becomes very clear. A systems analyst must champion the needs of line-of-business users to be successful, yet must also maintain loyalties and a reasonable level of status quo within the organization. IT staff tend to favor predictable routines and, for the most part, view line-of-business needs as an interruption to the grander plan of building out next-generation architectures, consolidating ERP, MRP, or CRM systems, or developing the next generation of Internet applications for the entire company.
The center of control over IT in many organizations globally has shifted from the CIO to the Chief Executive Officer (CEO), the Chief Marketing Officer (CMO) in some cases, and most definitively to line-of-business managers. This fundamental shift is critical for the future of systems analysis and design both today and going forward. Lessons drawn from Keller (1999), Mann (2002), and Worthington (2001) highlight the fact that systems analysts are becoming more focused on being business analysts first and systems or computer analysts second. This is also supported by the fact that many CIOs now report to the CFO, which demonstrates that line-of-business needs dominate IT budgets and direction more than ever before — signaling that CIOs must be business strategists first and technologists second. It is also common, for example, to find CIOs reporting to the CMO in marketing- and distribution-intensive businesses, where the use of technology is critical for planning, sensing, and responding to market demands.
According to AMR Research (2006), aligning IT's systems analysts more closely with business objectives has the potential to drive successful project completion rates from roughly 30% — when business goals are not internalized or understood — up to 85%. Systems analysts are therefore required to fulfill the much broader commitment that so many CIOs are making today: turning IT into a responsive, customer-centered resource for other departments in the organization, with further impact on all customer-facing strategies including attracting, selling, and servicing clients (AMR Research, 2006).
Paradoxically, this intersection of the CIO's role and that of systems analysts is what is driving the next generation of IT architectures — ones featuring a more service-oriented and modular design that can more easily align with the business strategies of organizations, with early adopters using the modular or meta-systems described by Keller (1999). Much has been written on the topic of service-oriented architectures (SOA) and their ability to help businesses respond quickly to market conditions (Keller, 1999; Mann, 2002; Worthington, 2001; AMR Research; Gartner Group). At the heart of so many of these discussions is the building blocks of SOA and their development of composite architectures complete with meta-systems that have the potential to map directly to business needs (AMR Research, 2005). This is a very strategic view of what is becoming a highly complex subject, and the core of the current discussion centers on Web Services, SOAP, and the era of the composite application structure (Gartner, 2004). Collectively, these technologies are used by systems analysts within development methodologies such as the SDLC to complete new development projects and address maintenance challenges.
Another aspect of the business analyst's role that will gain significant importance in the coming years is that of being a Business Process Management (BPM) analyst and strategist. BPM involves redefining core business processes to make them more efficient and economical while aligning them more closely with core business goals and objectives. As Keller (1999) points out, rules-based systems are being used as the foundation of BPM applications and tools that business analysts use to translate business requirements into IT components. Keller (1999) further notes how rules-based systems can become constrictive over time, as the realities of lines of business get modeled to the nth degree and, in the end, little actual change is delivered. Even so, the increasing use of rules-based systems for interpreting, analyzing, and ultimately translating business processes into applications is giving business analysts a critical tool as their role continues to evolve. Simply put, systems analysts are not so much project managers as they are interpreters of business requirements and translators of those requirements into business process improvements (Gartner, 2004).
At the core of the revolution happening in systems analysis is the need for these professionals to own the processes they are redefining, in conjunction with their line-of-business internal customers. Becoming expert in business processes first, and co-owning their redefinition to meet the requirements of internal customers, is critical for the success of anyone pursuing the systems analyst career path. This represents a significant departure from previous generations of the role, in which concentration on technology came first, systems tools second, and process redefinition a distant third — if it was addressed at all.
This new process-centric definition of the systems analyst role is gradually changing the entire definition of IT, because systems analysts are in effect the customer-facing part of any IT department (AMR Research, 2006). The internal "customers" of IT are redefining the agenda of information systems globally (Gartner, 2004). The bottom line of this process-centric revolution is that systems analysts will be called upon more than ever to understand business issues more deeply than technologies.
Keller (1999), Mann (2002), and Worthington (2001) have produced impressive bodies of research on meta-systems and the role of both rules-based and constraint engines as they relate to Web Services and the ability to quickly redefine business processes. Knowledge of Web Services is a must-have component of any systems analyst's analytical toolkit, as is the ability to design, lead the development of, and potentially program composite applications specifically built to align with a company's line-of-business goals and objectives (IBM Systems Journal, 2001).
"SDLC as a framework for project success and alignment"
"Capturing user needs and managing organizational change"
Progressing from the role of pure technologist to that of strategist and business process re-engineering expert — through the use of programming, SOA, and composite application development tools — the systems analyst is revolutionizing how companies use IT to support and enable the accomplishment of business objectives. The traditional role of IT as a cost center is being transformed as a result, with the CIO becoming one of the lead strategists in many organizations, accountable for the accomplishment of line-of-business objectives. This evolution from cost center to potential profit center is in direct proportion to the systems analyst's ability to function as a change agent who places business objectives first and uses technology as the competitive advantage and differentiator.
You’re 57% through this paper. Sign up to read the remaining 2 sections.
Sign Up Now — Instant Access Already a member? Log inAlways verify citation format against your institution’s current style guide requirements.