a PowerPoint presentation of a topic in computer studies.

1. Roles of System analyst
 The Systems analyst performs the following
roles during various phases of SDLC. He
works as a:

2. • Problem Investigator: The analyst studies the
problems and needs of an organization during
feasibility and requirements analysis phases of
SDLC. He visits the various departments of the
organization and interviews the users. He
analyses the problems of the current system
and collects their new requirements. The
analyst initially works as an investigator by
extracting the real problems of the users.

3. • Problem Solver: The analyst solves the problems of the
current system faced by the users. He determines how
people, method and technology can improve the current
system. After feasibility analysis, he presents the system
proposal to the management.
• Systems Designer: The analyst creates a detailed physical
(current) and logical (proposed) design of the system.
• Motivator: The analyst motivates users to participate in
development and implementation of the proposed system.
This helps to understands user’s feelings about the
proposed system. The analyst interprets the thoughts of
users and hence, draws conclusions. He appeals
management and users for getting the support in
development and implementation of the proposed system.

4. • Project Manager: The analyst monitors the
development and implementation of software
in relation to quality, cost and time. He works
with the project leader for managing the
project properly. For development of small
systems, the Systems analyst is generally the
project leader.

5. Roles of System developers
• System developers formulates and defines system scope
and objectives for assigned projects combining knowledge
and disciplines of all aspects of a computing system.
• Develop and implement applications and programs for
parts of IT systems that are hidden from users but that keep
organizations running smoothly.
• Perform tasks related to the design, development,
modification and administration of software systems and
applications.
• They identify and assess users’ needs or project
requirements, and design or configure systems and
programs that meet those needs.

6. • Typical duties include:
• Discussing clients’ and colleagues’ requirements
• proposing solutions, often in collaboration with
colleagues
• Designing and building web applications using a
range of frameworks and scripting languages
• Testing projects and responding to any problems
or bugs revealed
• Managing projects through their lifecycle
• Developing documentation and training to
support new applications
• Reporting on functionality of web applications
and devising plans for improvements.

7. • Users are critical to determine the user requirements
for the system being developed. Typically, these user
requirements are developed by a system analyst based
on the input from users. Users are also involved in
system testing, including the testing of any prototypes
• User involvement in the field of information system
development is usually considered as vital mechanism
to enhance system quality and ensure successful
system implementation.
• The involvement of the user increases knowledge
about the project. Therefore, user participation is an
important role in choosing a suitable model. .

8. Roles of a system owner:
• Muller, 2018). Decision Maker: The system owner is
responsible for making crucial decisions regarding the
system's development, implementation, and future
enhancements.
• Budget Oversight: They manage and allocate financial
resources for the system's maintenance, upgrades,
and improvements.
• System Visionary: The owner sets the strategic direction
and long-term goals for the system in line with
organizational objectives.
• Stakeholder Liaison: They interact with stakeholders to
gather requirements, address concerns, and ensure
the system aligns with their needs.
• Risk Management: The system owner assesses and
mitigates risks related to the system's security, privacy,
and compliance.

9. • Performance Monitoring: They monitor system
performance and ensure it meets the established
service level agreements (SLAs).
• Vendor Management: If the system involves third-
party vendors, the owner oversees vendor
relationships and contracts.
• Change Management: They implement changes to the
system, ensuring minimal disruptions and smooth
transitions.
• Security and Access Control: The system owner
enforces security policies and controls access to the
system's sensitive data and functionalities.
• Compliance: They ensure the system adheres to
industry standards, regulations, and internal policies

10. Difference between the four
• The system analyst studies the problems and needs of an
organization during feasibility and requirements analysis
phases of SDLC. He visits the various departments of the
organization and interviews the users.
• System developers formulate and define system scope and
objectives for assigned projects combining knowledge and
disciplines of all aspects of a computing system.
• The system owner is responsible for making crucial
decisions regarding the system's development,
implementation, and future enhancements.
• Users test prototypes and giving feed up to the system
analyst.