Scribd
Upload
47 views

IT-510 Module 1 Part Two

A systems analyst requires both technical and business knowledge to span IT areas horizontally and integrate vertical expertise. They must understand how different teams in areas like web development, business intelligence, security, and more can work together to design solutions like a sales dashboard. While not experts in any one area, a systems analyst needs to communicate effectively to bring teams together. Strong communication is key, as poor communication can cause project struggles.

Uploaded by

petetg5172
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
47 views

IT-510 Module 1 Part Two

A systems analyst requires both technical and business knowledge to span IT areas horizontally and integrate vertical expertise. They must understand how different teams in areas like web development, business intelligence, security, and more can work together to design solutions like a sales dashboard. While not experts in any one area, a systems analyst needs to communicate effectively to bring teams together. Strong communication is key, as poor communication can cause project struggles.

Uploaded by

petetg5172
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Systems Analyst

Being a systems analyst requires both technical and


business knowledge. The knowledge needs to span IT
horizontally. A systems analyst is typically not a vertical
expert on a topic. The better systems analysts are the
ones that know how to build knowledge networks and are
well versed in the technology. In doing so, a superior
systems analyst must still rely on technical competencies
for detailed knowledge. Consider a user request to add
sector-level dashboard reporting for monthly sales by
department and further by sales person. A systems analyst
would need to horizontally span the following vertical
areas of IT to design the solution:

• Web Team: This team would build out the


presentation layer of the dashboard.
• Business Intelligence Team: This team would design
the dashboard and data.
• Security Team: This team would properly secure the
access to the dashboard.
• Operations Team: This team would need to schedule
the operational updates to the data via scheduled
batches.
• Infrastructure Team: This team would allocate the
proper server configures and resources.
• Database Team: This team would need to create the
databases and backups of data.
• Disaster Recovery (DR) Team: This team would need
to incorporate the changes into DR scenarios.
• Quality Assurance (QA) Team: This team needs to
ensure that the solution meets guidelines defined for
IT solutions.
The systems analyst should not expect to be able to
vertically distinguish all of the details of each of the areas
noted above. However, the systems analyst must know
how to communicate to each of the specified teams and
understand how to integrate and bridge the vertical areas
to properly create a system design.

In addition to the technology discussed above, the


systems analyst needs to understand business technology
models such as internet applications, B2B, enterprise
systems, transactional processing systems, user
productivity systems, etc. Each of the systems represents
a different type of solution design. The SDLC that is used
also changes with the different type of solution. The
systems analyst must be well versed in terms of business
technology models and the different types of solution
design.

Communication is typically the singular point of failure for


any systems analyst. The ability to recognize one’s
audience and properly communicate the design vision as
the design relates to that audience is what differentiates a
good systems analyst from a great systems analyst. In
meetings with different audience types, being able to
fluidly transition across communication lines can make a
project. The systems analyst builds confidence with the
different audiences by having strong communication skills.
If communication does breakdown, the project struggles.
The systems analyst has to then work extra hard to rebuild
the project vision and confidence in the plan.

In Module Two, students will explore project management


that involves the creation and management of a project
plan. In Module Two, students will learn how to create a
project plan by decomposing the business problem into a
work breakdown structure (WBS), organizing the WBS into
tasks, and finally applying timelines.

You might also like