1. Working with Agentic AI: Computer Systems Analyst

How human skills and agentic skills are dynamically integrated and coordinated across computer systems analysis responsibilities

1.1. Computer Systems Analyst as an Occupation

A computer systems analyst studies an organization’s current computer systems, procedures, and business workflows to design technological improvements that enhance operational efficiency. This occupation serves as the critical bridge between business objectives and information technology (IT) implementation. Unlike software developers who primarily focus on writing application code, or business analysts who focus on high-level process optimization, the computer systems analyst evaluates the entire technological ecosystem—including hardware, software, networking, and data architecture—to design integrated solutions that solve complex data processing and operational problems. To ensure these systems deliver tangible value, the analyst must understand how business requirements, technical constraints, cost-benefit ratios, system compatibility, and user capabilities collectively determine the viability of an IT solution.

Typical responsibilities of a computer systems analyst include:

• business requirements analysis and cost-benefit evaluation;
• system architecture design and technical specification;
• system integration and compatibility management;
• system implementation, testing, and quality assurance; and
• user training, documentation, and production support.

These responsibilities are fulfilled through distinct tasks and subtasks, each requiring one or more actions with specific skill requirements. Human skills and agentic skills both contribute to these responsibilities, but their levels and forms of involvement differ according to the responsibility, task, action, data, technical environment, and expected outcome.

1.2. Human Skills and Agentic Skills in Computer Systems Analysis

Computer systems analysis increasingly integrates both human skills and agentic skills.

Human skills are reusable capabilities possessed and developed by computer systems analysts. They include business process reasoning, systems thinking, architectural judgment, stakeholder communication, cost-benefit analysis, technical translation (bridging IT and business vocabularies), problem sensitivity, and deductive reasoning.

Agentic skills are reusable capabilities available to AI agents through their underlying models, contextual information, instructions, constraints, tools, and computational resources. In computer systems analysis, these skills include requirements extraction from interview transcripts, diagram generation (e.g., UML, data flow diagrams), code snippet generation for integration scripts, automated test case creation, log parsing for system troubleshooting, technical documentation drafting, and API compatibility scanning.

Both skill types contribute to the same occupational responsibilities, but their involvement varies by action. Understanding the nuanced political and operational constraints of a legacy business unit relies primarily on human knowledge of organizational dynamics and workflow realities; an AI agent may then use agentic skills to structure those qualitative insights into formal use cases and user stories. In system design, the analyst first determines the logical boundaries between hardware and software components, and an AI agent subsequently generates the initial architecture diagrams and suggests standard integration patterns. Across these actions, human and agentic skills are activated sequentially or iteratively based on task requirements, with the human professional maintaining oversight and final judgment.

The relationship between these skills is not a fixed division where certain responsibilities permanently belong to humans and others to AI. Instead, human and agentic involvement shifts across tasks and between different actions within the same task.

1.3. Dynamic Human–Agentic Skill Integration and Collaboration in Computer Systems Analysis

Computer systems analysis functions can be understood as an occupation where responsibilities are fulfilled through tasks and subtasks, tasks and subtasks are executed through actions, and actions require appropriate configurations of human and agentic skills.

An occupation provides the overall professional context. For computer systems analysis, this context encompasses aligning IT infrastructure with business goals, designing system modifications, ensuring cross-platform compatibility, and overseeing the technical lifecycle of enterprise solutions.

A responsibility represents an expected area of professional work or an outcome that the computer systems analyst accomplishes or maintains. Responsibilities such as requirements gathering, system design, and integration management each contain multiple tasks.

A task is a context-dependent unit of work used to fulfill part or all of a responsibility. When a task is too broad or complex for reliable execution, it is decomposed into smaller subtasks.

Tasks and subtasks are executed through one or more actions. Actions represent reusable and configurable operations such as interviewing a stakeholder, drafting a data flow diagram, calculating the return on investment (ROI) for a hardware upgrade, writing a script to map legacy database fields to a new cloud schema, or generating a user acceptance testing (UAT) plan.

Each action has skill requirements. These requirements describe the capabilities needed for effective and reliable execution. Depending on the action and its context, human skills, agentic skills, or an integration of both can satisfy these requirements.

The skills available for computer systems analysis reside in a skill space containing both human skills and agentic skills. Relevant skills in this space can serve as candidate skills for executing the actions required by a particular task. A human skill in systems thinking, for example, can serve as a candidate for identifying how a change in the inventory module will cascade into the financial reporting system, while an agentic skill in schema comparison can serve as a candidate for mapping the specific database fields involved in that cascade.

Candidate skills are evaluated relative to the requirements of the action and its occupational and task context. Appropriate skills are then selected and organized into a skill configuration for execution. Depending on these requirements, a configuration may rely mainly on human skills, mainly on agentic skills, or on an integrated arrangement of both.

1.3.1. Skills Competition and Skills Collaboration

Two important relationships can occur between human skills and agentic skills when constructing a skill configuration: skills competition and skills collaboration.

Skills competition occurs when both a human skill and an agentic skill can satisfy the same or similar requirements for an action, but simultaneous application of both is unnecessary. Under a particular occupational and task context, one skill type can provide a better fit for the action than the other.

For example, both a computer systems analyst and an AI agent can draft a standard technical specification document for a new API endpoint. When the input parameters, security protocols, and formatting templates are clearly defined, the agentic skill provides fast and scalable execution. When the specification requires negotiating a compromise between the security team’s strict encryption requirements and the operations team’s latency constraints, the analyst’s human skills provide the necessary contextual judgment and stakeholder mediation.

The purpose of skills competition is not to establish whether human or agentic skills are generally superior. Rather, it identifies which available skill provides the better fit for a particular action under particular conditions.

Skills collaboration occurs when one skill type alone cannot effectively satisfy the requirements of a task or its actions, or when combining complementary human and agentic skills produces stronger task performance.

Collaboration does not require human and agentic skills to operate simultaneously. Instead, they are activated at different stages of action execution in a sequential, iterative, or recursive manner according to evolving task requirements.

For example, an analyst first conducts workshops with department heads to identify bottlenecks in a legacy supply chain workflow. An AI agent then processes the workshop transcripts, extracts the core business rules, and generates initial process models and data flow diagrams. The analyst subsequently reviews these diagrams, identifies a critical logical flaw where the proposed automated handoff violates a regulatory compliance requirement, and revises the system logic. Based on the analyst’s direction, the agent next updates the technical specifications and generates a revised cost-benefit analysis for the new architecture. Throughout this sequence, human and agentic skills are activated iteratively as task requirements evolve, while the analyst directs the design and evaluates its business viability.

This dynamic relationship allows computer systems analysts to leverage the complementary strengths of both skill types rather than relying on a permanent allocation of work.

1.3.2. Skill Configuration and Task Execution

A skill configuration specifies which human skills and agentic skills are used to execute the actions associated with a task or subtask and how those skills are coordinated.

The configuration depends on factors such as action requirements, legacy system complexity, organizational constraints, technical feasibility, expected reliability, available integration tools, information sensitivity, decision consequences, and intermediate results.

For one action, an agentic skill may independently satisfy the requirements. For another, a human skill may provide the better fit. A complex task may require several configurations across multiple actions, with human and agentic skills repeatedly interacting as the task progresses.

The configuration is therefore dynamic rather than permanent. It may change when the action changes, new business constraints emerge, an agentic result fails to satisfy expected technical standards, or human interpretation identifies a hidden workflow dependency.

Throughout this process, the computer systems analyst remains the professional responsible for directing and controlling the work associated with the occupation and its responsibilities. Agentic AI provides powerful complementary capabilities that expand what the professional can model, calculate, map, test, visualize, and document.

1.3.3. Task Performance Evaluation and Skill Space Adaptation

The performance produced through a selected skill configuration is evaluated against predefined evaluation metrics. These metrics determine whether the human skills, agentic skills, or their integrated configuration are sufficiently capable of performing the relevant task and its required actions.

Evaluation criteria depend on the work being performed. In computer systems analysis, they include architectural soundness, business alignment, integration compatibility, testing coverage, documentation clarity, cost estimation accuracy, and system reliability.

When a selected skill or skill configuration produces performance above the defined threshold, it passes the performance evaluation and is retained for future applications under appropriate conditions. Repeated successful use provides additional evidence about where that skill or configuration performs effectively.

When performance falls below the required threshold, the corresponding skill or configuration is not reused without modification. The relevant human or agentic skills may be refined or reconfigured, existing skills can be combined differently, or new human and agentic skills may be developed or constructed from scratch when the existing skill space lacks adequate capability.

For example, an AI agent is configured to automatically generate data mapping scripts between a legacy on-premise database and a new cloud application. However, task performance evaluation reveals that the agent frequently fails to account for custom, undocumented data transformation rules embedded in the legacy system’s old stored procedures. The agentic skill is then refined through the integration of specialized code-parsing instructions, requiring the agent to analyze legacy SQL scripts before generating the mapping logic. The revised skill is evaluated again, and once it satisfies the required performance criteria, it is retained. Human skills follow a corresponding development process: when an analyst encounters a novel distributed ledger technology proposed for supply chain tracking, the relevant architectural capability is developed through studying the protocol and experimenting with sandbox environments before its performance is evaluated through subsequent system design tasks.

Refined and newly constructed skills that satisfy the required performance criteria are added to the skill space. In this way, task performance evaluation provides feedback not only for completing current work but also for continuously optimizing and expanding the available skill space.

The skill space is not constructed as an isolated collection of occupation-specific representations. Many human and agentic skills used in computer systems analysis are reusable across occupations. Requirements gathering, process modeling, technical writing, code generation, log analysis, and stakeholder communication contribute to work in software engineering, enterprise architecture, IT project management, business analysis, and many other fields.

Reusable skills can therefore be represented once and configured differently according to the responsibilities, tasks, actions, and contexts of different occupations. This allows the skill space to serve a growing range of occupations without unnecessarily duplicating or exploding the number of skill representations. Occupational specialization is introduced through task context, action requirements, parameters, data sources, tools, constraints, and skill configurations rather than by creating a completely separate skill representation whenever the same underlying capability appears in another occupation.

The resulting process is adaptive: occupational responsibility → task and subtask → actions → skill requirements → candidate human and agentic skills → skill configuration → task execution → task performance evaluation → skill refinement, reconfiguration, or construction → optimized and expanded skill space

This cycle allows human and agentic capabilities to evolve alongside the requirements of computer systems analysis work.

1.4. Essential Responsibilities of Computer Systems Analyst

1.4.1. Business Requirements Analysis and Cost-Benefit Evaluation

Business requirements analysis and cost-benefit evaluation establishes the foundational justification for any technological intervention. This responsibility involves consulting with management and end-users to understand operational bottlenecks, gathering and validating functional and non-functional requirements, assessing the usefulness of commercially available software versus custom builds, and preparing return-on-investment (ROI) analyses to guide executive decisions.

Agentic skills contribute extensively to interview transcription, requirements extraction, initial use-case drafting, and industry benchmarking for hardware/software cost estimations. Human skills remain essential for reading between the lines of stakeholder requests, understanding the political and operational realities of the business unit, resolving conflicting requirements between different departments, and determining whether a proposed technological solution actually addresses the root business problem.

For example, a department requests a complete overhaul of their inventory tracking system. The computer systems analyst conducts workflow observations and interviews to understand the actual friction points. An AI agent processes the interview transcripts, categorizes the requested features, and generates a draft requirements matrix. The analyst reviews the matrix and realizes that the core issue is not the software interface, but a hardware limitation in the warehouse barcode scanners causing data latency. The analyst pivots the project scope toward a hardware upgrade and network optimization, instructing the agent to recalculate the cost-benefit analysis based on the revised, significantly cheaper infrastructure approach.

1.4.2. System Architecture Design and Technical Specification

System architecture design and technical specification translates approved business requirements into actionable blueprints for developers and network engineers. This responsibility includes defining system boundaries, planning data flows, specifying hardware and software configurations, creating logical operational steps, and developing comprehensive technical documentation.

Agentic skills are well suited to generating diagram code (e.g., PlantUML, Mermaid), drafting API specifications, suggesting standard design patterns, and checking documentation for internal consistency. Human skills contribute to applying systems thinking to ensure the architecture scales appropriately, designing secure data handoffs, balancing technical debt against delivery timelines, and ensuring the design aligns with the organization’s broader enterprise architecture.

For example, an analyst is tasked with designing a new customer portal that integrates with three legacy internal databases. The analyst defines the high-level data governance rules and the required latency thresholds. An AI agent then generates the initial sequence diagrams, drafts the JSON schema for the API payloads, and outlines the server resource requirements. The analyst reviews the architecture and identifies that the proposed synchronous data calls will cause system timeouts during peak traffic. The analyst revises the design to incorporate an asynchronous message queue, and the agent updates the technical specifications and sequence diagrams to reflect the new event-driven architecture.

1.4.3. System Integration and Compatibility Management

System integration and compatibility management ensures that disparate hardware, software, and network components operate cohesively within the organization’s ecosystem. This responsibility involves analyzing legacy system limitations, designing data migration strategies, coordinating the linking of systems to increase compatibility, and resolving data format or protocol mismatches.

Agentic skills assist with scanning existing API documentation, identifying data schema discrepancies, generating data transformation scripts, and mapping legacy fields to modern cloud schemas. Human skills remain important for evaluating the business risk of data loss during migration, designing fallback procedures, understanding the historical context of why legacy systems were built with specific idiosyncrasies, and negotiating integration timelines with external vendors.

For example, an organization acquires a smaller company and needs to integrate the acquired company’s customer relationship management (CRM) platform into the parent company’s enterprise resource planning (ERP) system. An AI agent analyzes both database schemas, flags conflicting data types (e.g., date formats, currency precision), and generates the initial SQL transformation scripts. The analyst reviews the mapping and recognizes that the acquired company tracks “customer status” using a qualitative sales methodology that does not map cleanly to the parent company’s rigid financial categories. The analyst designs a new intermediate classification logic, and the agent updates the transformation scripts to accommodate this business-specific nuance.

1.4.4. System Implementation, Testing, and Quality Assurance

System implementation, testing, and quality assurance verifies that the configured hardware and developed software perform as expected in a real-world environment before full deployment. This responsibility includes overseeing installation, developing test procedures, facilitating user acceptance testing (UAT), troubleshooting system malfunctions, and ensuring quality standards are met.

Agentic skills contribute to automated test case generation, log parsing to identify error patterns, executing load testing scripts, and tracking defect resolution metrics. Human skills define the critical business scenarios that must be tested, interpret ambiguous system behaviors that automated tests might miss, prioritize defects based on operational impact, and make the final authorization for system deployment.

For example, during the UAT phase of a new automated billing system, testers report intermittent calculation errors that the automated unit tests failed to catch. An AI agent parses the server logs and application traces during the failing transactions, isolating the errors to a specific timezone conversion library. The analyst reviews the agent’s findings and realizes the error only occurs for international clients billed on the last day of the month due to a leap-year logic flaw in the legacy code. The analyst defines the exact mathematical correction required, instructs the development team to apply the patch, and the agent generates a new suite of regression tests specifically targeting edge-case calendar dates to ensure the fix is permanent.

1.4.5. User Training, Documentation, and Production Support

User training, documentation, and production support ensures that the organization can effectively adopt and maintain the new or modified systems. This responsibility involves writing instruction manuals, training staff and end-users, monitoring system performance indicators post-launch, and troubleshooting production issues to sustain application stability.

Agentic skills assist with drafting user manuals from technical specifications, generating interactive training modules, monitoring production logs for early warning signs of degradation, and drafting initial troubleshooting runbooks for the IT helpdesk. Human skills evaluate the clarity and accessibility of the training materials for non-technical users, design change-management strategies to encourage system adoption, and handle complex, multi-system escalations that defy standard runbooks.

For example, a newly deployed enterprise workflow system experiences a sudden drop in user adoption and a spike in helpdesk tickets. An AI agent analyzes the helpdesk ticket metadata and system usage logs, identifying that users are abandoning the process at a specific multi-factor authentication (MFA) prompt. The agent drafts a proposed technical workaround to bypass the prompt for internal IP addresses. The analyst reviews the proposal and rejects it due to security policy violations. Instead, the analyst determines that the MFA timeout window is too short for the complex data entry required at that step. The analyst instructs the agent to adjust the session timeout parameters in the configuration and drafts a targeted communication to the users explaining the improvement, thereby resolving the friction point securely.

1.5. Changing Human and Agentic Involvement Across Computer Systems Analyst Responsibilities

Human skills and agentic skills are involved throughout computer systems analysis, but their relative involvement differs across responsibilities and changes during task execution.

These involvement levels are not permanent allocations. A single responsibility may contain actions where human and agentic skills compete as alternative capabilities and other actions where they collaborate sequentially, iteratively, or recursively.

The practical objective is to construct skill configurations that use the most suitable available capabilities for each part of the work and revise those configurations when task performance evaluation shows that another arrangement performs more effectively or reliably.

1.6. Working as a Computer Systems Analyst with Agentic AI

Agentic AI is becoming an increasingly powerful component of computer systems analysis. Computer systems analysts should therefore adopt and integrate AI agents as complementary participants in professional workflows rather than treating them only as occasional tools for drafting documentation, generating diagrams, or parsing error logs.

This shift does not reduce the importance of systems thinking, business acumen, and architectural expertise. Human professionals remain responsible for the occupation and its corresponding responsibilities. They understand organizational objectives, define meaningful system requirements, interpret business constraints, determine appropriate technological configurations, evaluate integration risks, communicate across technical and non-technical domains, control consequential deployment decisions, evaluate task performance, and decide how human and agentic skills are configured and improved.

At the same time, agentic skills greatly expand the volume and complexity of analytical and technical work that can be executed. AI agents process vast amounts of stakeholder transcripts, generate complex architectural models, scan millions of lines of legacy code for integration points, automate rigorous testing protocols, monitor production environments, and synthesize extensive technical documentation at a scale difficult to achieve through direct human effort alone.

Strong computer systems analysis practice is therefore not based on maximizing human work or agentic work independently. It is based on finding appropriate configurations of human skills and agentic skills for the responsibilities, tasks, subtasks, and actions being performed.

Where a human skill and an agentic skill can independently perform the same action, skills competition identifies which is better suited to the current context. Where work requires complementary capabilities, skills collaboration results in human and agentic skills being activated sequentially, iteratively, or recursively to achieve stronger task performance than either skill type achieves alone.

Task performance evaluation then determines whether selected skills and configurations satisfy predefined expectations. Successful skills are retained and reused, while inadequate skills are refined, reconfigured, or newly developed. The resulting capabilities return to an increasingly useful skill space that supports computer systems analysis and, where capabilities are reusable, other occupations as well.

For a computer systems analyst, working effectively with agentic AI means treating AI as a powerful complementary capability integrated into everyday professional routines while maintaining human control of occupational responsibilities. Through appropriate skill selection, competition, collaboration, evaluation, and continuous improvement, human professionals and agentic AI work together to achieve system architectures that are more efficient, scalable, adaptable, timely, and fundamentally aligned with organizational success.