Scribd
Upload
7 views

Chapter 2

Uploaded by

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

Chapter 2

Uploaded by

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

1. Why Do Businesses Need Systems Analysts?

Systems Analysts are critical to businesses because they bridge the gap between business
needs and technology solutions. Here are some expanded points:

• Bridging Communication: Systems Analysts act as intermediaries between


technical teams (like developers) and non-technical business stakeholders. They
ensure everyone is on the same page, particularly when translating business
requirements into technical specifications.

• Technology Alignment: In today’s digital age, technology plays a pivotal role in


optimizing processes, improving efficiency, and supporting innovation. Systems
Analysts help ensure that technological systems are aligned with business
objectives and add value to the company.

• Business Competitiveness: By optimizing systems, a business can operate more


effectively, stay competitive, and deliver better products/services.

2. Users, Analysts in Various Functional Areas

Different users and analysts focus on unique parts of the system, and understanding these
roles is key for systems analysts:

• End-Users: The employees or customers who directly interact with the system.
Analysts must understand their needs and pain points to make systems user-
friendly and effective.

• Managers: They require systems that provide them with high-level insights into
business performance, such as reports and dashboards, which help them make
decisions.

• IT and Business Analysts:

o IT Analyst: Focuses on the technology (infrastructure, hardware, software)


and ensures it works correctly.

o Business Analyst: Works to ensure that technology helps meet business


goals, like increasing efficiency or profitability.

• Data and Process Analysts:

o Data Analyst: Focuses on collecting and interpreting data generated by


systems to help with strategic decisions.
o Process Analyst: Works on optimizing business processes and workflows,
ensuring the system is designed to make operations smoother.

3. Role of a Systems Analyst

The Systems Analyst’s role is multifaceted and varies based on project needs:

• Liaison Between Departments: Analysts interact with different departments


(finance, marketing, HR, etc.) to understand their specific needs. They must ensure
that any system developed can serve various functions within the organization.

• Problem Solver: They identify issues with existing systems, which can range from
slow performance to poor user experience, and then devise solutions to improve or
replace those systems.

• System Designer: Analysts work with the development team to design systems that
meet business needs. This includes everything from designing user interfaces (UI) to
ensuring data flows correctly between different system components.

• Project Manager: Often, analysts oversee projects from start to finish, managing
timelines, resources, and ensuring all milestones are met.

4. Duties of a Systems Analyst

Here are some expanded duties:

• Requirement Gathering: The analyst must interview stakeholders (employees,


customers, management) to understand the needs of the system. This involves
detailed conversations to ensure the system will fulfill its intended purpose.

• Feasibility Study: Before implementing a system, analysts check whether it is


feasible by evaluating:

o Technical Feasibility: Can the current technology support the system?

o Operational Feasibility: Will the system be easy to integrate into daily


operations?

o Economic Feasibility: Does the system fit the business budget, and will it
provide a good return on investment?
• System Design and Documentation: Once requirements are clear, the analyst
creates system designs (blueprints), showing how the system should be developed,
and writes comprehensive documentation that guides developers and testers.

• Testing and Implementation: After development, the analyst ensures the system is
tested thoroughly (for bugs, usability, etc.) and helps during the rollout to ensure
smooth implementation.

• Maintenance: Even after the system is deployed, the analyst continues to monitor
its performance, addresses issues, and suggests improvements or updates.

5. Qualifications of a Systems Analyst

A successful systems analyst typically has:

• Education: A degree in Computer Science, Information Systems, or Business with a


technology focus. This gives them the technical and analytical background needed
to understand and design systems.

• Experience: Hands-on experience in IT roles, such as software development or


system administration, gives analysts the technical knowledge they need to design
effective systems.

• Certifications: Certifications such as CBAP (Certified Business Analysis


Professional) for system and business analysis or PMP (Project Management
Professional) help systems analysts stand out by showcasing their formal
knowledge.

6. Analytical Skills

Systems Analysts need to have strong analytical abilities to:

• Solve Complex Problems: They must look at the current systems, identify what’s
wrong, and figure out the most efficient solutions.

• Critical Thinking: They evaluate multiple solutions, considering their benefits and
drawbacks, before deciding which to implement.

• Detail Orientation: Systems have many components, and a small mistake can
cause major issues. Therefore, analysts must pay close attention to every detail in
their designs.
• Data Analysis: Analysts often look at system data (performance metrics, user
interactions) to make informed decisions about necessary improvements.

7. Technical Skills

While systems analysts are not always developers, they need technical knowledge to
communicate with IT teams and to ensure their designs are practical:

• Programming Knowledge: Familiarity with programming languages (like Java,


Python, or C++) helps them understand what’s possible and what’s not.

• Database Expertise: Knowledge of database systems (SQL, NoSQL) is crucial


because almost every system will need to store and retrieve data efficiently.

• System Design Tools: Tools like UML diagrams, flowcharts, and data flow diagrams
(DFD) are essential for mapping out how the system will work.

• Networking Knowledge: Understanding how networks function ensures that the


system can communicate effectively with other systems, databases, and users.

8. Management Skills

Systems Analysts often have project management responsibilities:

• Project Management: They manage timelines, ensuring the system is delivered on


time and within budget. They also handle any changes in scope, ensuring that
unexpected requirements don’t derail the project.

• Team Leadership: Analysts may lead teams of developers, testers, and other IT
professionals. Strong leadership ensures that everyone works together toward the
project goals.

• Risk Management: They identify potential risks (e.g., budget overrun, technical
challenges) and develop plans to mitigate these risks before they become major
problems.

• Time Management: Given that systems development is often on a strict timeline,


analysts need to manage time efficiently, ensuring the project stays on track.

9. Interpersonal Skills
Systems analysts work with people from different departments, so their interpersonal skills
are crucial:

• Communication: They must explain technical concepts to non-technical


stakeholders clearly. This includes writing reports, giving presentations, and leading
meetings.

• Collaboration: They often work with teams from different departments. Being able
to collaborate and balance different perspectives is essential.

• Negotiation: Sometimes, different stakeholders have conflicting needs. The analyst


must negotiate with them to find solutions that work for everyone.

• Customer-Oriented Approach: Since the ultimate goal of system development is


to make the user’s (customer or employee) life easier, analysts must be responsive
to user feedback and make improvements accordingly.

You might also like