SYSTEM INTEGRATION AND ARCHITECTURE 1 WITH LAB

SYSTEM
ANALYST
SYSTEM ANALYST SKILLS
SYSTEM ANALYST ROLES
SDLC
PROJECT IDENTIFICATION
 SYSTEM ANALYST SKILLS

TECHNICAL
Understand the potential and limitations of information technology. It
helps to understand how computers, data networks, databases, and
operating systems work together. The system analyst must also be
able to work with complex programming languages.

BUSINESS
defined as the value of the business. It encompasses all elements
that determine the well-being and health of a business.

mtbl
 SYSTEM ANALYST SKILLS

ANALYTICAL
The ability to collect and analyze data is essential for a business
systems analyst. In this role, you must understand the data and identify
trends to make recommendations to improve the system.

INTERPERSONAL
or also known as people skills are the vital skills a person uses to
communicate and/or interact with others including persuasion,
delegation, and active listening. These skills are extremely important as
they help the system analyst work with other system professionals,
programmers, and importantly the end users.

mtbl
 SYSTEM ANALYST SKILLS

MANAGEMENT
help the system analyst manage projects, their resources, the possible
threats and risks, and finally the ongoing changes. This ability to
make decisions, understand concepts, develop ideas, and implement
strategies proves very important for a system analyst.

ETHICAL
professionalism, respect for the work and teammates, integrity,
timeliness, and discipline

mtbl
 SYSTEM ANALYST ROLES
SYSTEM ANALYST

A system analyst is someone who is in charge of designing,

transforming, modifying, and evaluating different systems to ensure
compatibility and users’ efficiency and effectiveness and also turns
user requirements into a set of functional specifications, which are
the blueprint of the system.

Duties of System Analysis

Consulting with management and users to determine the needs of the system.
Designing a system to meet the business objectives and goals
Specifying inputs and formatting outputs to meet users’ needs

mtbl
 SYSTEM ANALYST ROLES
BUSINESS ANALYST

A business analyst is a person who analyzes, organizes, explores,

and investigates an organization documents its business and also
assesses the business model, and integrates the whole organization
with modern technology.

Business analyst acts as a bridge and channel between the clients,

consumers, and the development team. Business development and
requirements are translated, transformed, and interpreted to
functional specifications by a business analyst.

mtbl
 SYSTEM ANALYST ROLES
REQUIREMENTS ANALYST

A requirements analyst is the person who elicits, analyzes, validates,

and manages the requirements throughout the project lifecycle.

Eliciting requirements
involve asking the right questions, listening actively, observing behaviors,
and facilitating workshops or interviews.
Analyzing requirements
ensure that they are clear, consistent, complete, feasible, and testable.

Validating requirements
ensure that they meet the expectations and needs of the stakeholders and
users. Validating requirements involves reviewing, verifying, and validating
the requirements with the relevant parties, as well as conducting tests,
prototypes, or simulations.
mtbl
 SYSTEM ANALYST ROLES
SKILLS
REQUIREMENTS ANALYST

Managing requirements
ensure that they are aligned with the project scope, objectives, and
changes. Managing requirements involves documenting, tracing,
baselining, and controlling the requirements throughout the project
lifecycle.

Communicating requirements
ensure that they are understood and agreed by all the project participants.
Communicating requirements involves creating, presenting, and distributing
the requirements artifacts, such as specifications, diagrams, or user stories.

Improving requirements
ensure that they are continuously refined and optimized. Improving
requirements involves evaluating, measuring, and improving the
requirements process, methods, and outcomes.
mtbl
 SYSTEM ANALYST ROLES
REQUIREMENTS ANALYST

Managing requirements
ensure that they are aligned with the project scope, objectives, and
changes. Managing requirements involves documenting, tracing,
baselining, and controlling the requirements throughout the project
lifecycle.

Communicating requirements
ensure that they are understood and agreed by all the project participants.
Communicating requirements involves creating, presenting, and distributing
the requirements artifacts, such as specifications, diagrams, or user stories.

Improving requirements
ensure that they are continuously refined and optimized. Improving
requirements involves evaluating, measuring, and improving the
requirements process, methods, and outcomes.
mtbl
 SYSTEM ANALYST ROLES
INFRASTRUCTURE ANALYST

An infrastructure analyst finds and fixes problems within an

organization’s computer network. As an infrastructure analyst, your
job duties include monitoring and assessing the systems and finding
areas that need upgrading or improvement.

Duties and Responsibilities

Provide internal support to users, diagnosing incidents and troubleshooting
problems
Create and implement plans for technology migrations and upgrades
Provide user support for mobile devices, tablets, and other business technology

mtbl
 SYSTEM ANALYST ROLES

CHANGE MANAGEMENT ANALYST

Change management analysts help businesses lessen the

unpredictability that comes with making necessary changes by
supervising the change-making process.

They ensure smooth communication across the company during the

changeover process, often using technological tools such as
Sharepoint to make sure that everyone is on the same page.

mtbl
 SYSTEM ANALYST ROLES
PROJECT MANAGER

Project managers play the lead role in planning, executing,

monitoring, controlling and closing projects.

They are accountable for the entire project scope, the project team
and resources, the project budget, and the success or failure of the
project. To succeed in their role, project managers must be adept at
coordinating resources, managing budgets, measuring and tracking
project progress, and communicating with team members and
stakeholders.

mtbl
System Design and Life Cycle
refers to a methodology with clearly defined processes for creating high-quality
software. In detail, the SDLC methodology focuses on the following phases of software
development:

Requirement analysis
Planning
Software design such as architectural design
Software development
Testing
Deployment

mtbl
STAGES & BEST PRACTICES
Following the best practices and/or stages of SDLC ensures the process works in a smooth,
efficient, and productive way.

1 Identify the Current Problems

“What are the current problems?” This stage of the SDLC means getting input from all
stakeholders, including customers, salespeople, industry experts, and programmers. Learn the
strengths and weaknesses of the current system with improvement as the goal.

2 Plan
“What do we want?” In this stage of the SDLC, the team determines the cost and resources
required for implementing the analyzed requirements. It also details the risks involved and
provides sub-plans for softening those risks.

In other words, the team should determine the feasibility of the project and how they can
implement the project successfully with the lowest risk in mind.
mtbl
STAGES & BEST PRACTICES
Following the best practices and/or stages of SDLC ensures the process works in a smooth,
efficient, and productive way.

1 Identify the Current Problems

“What are the current problems?” This stage of the SDLC means getting input from all
stakeholders, including customers, salespeople, industry experts, and programmers. Learn the
strengths and weaknesses of the current system with improvement as the goal.

2 Plan
“What do we want?” In this stage of the SDLC, the team determines the cost and resources
required for implementing the analyzed requirements. It also details the risks involved and
provides sub-plans for softening those risks.

In other words, the team should determine the feasibility of the project and how they can
implement the project successfully with the lowest risk in mind.
mtbl
STAGES & BEST PRACTICES
Following the best practices and/or stages of SDLC ensures the process works in a smooth,
efficient, and productive way.

3 Design
“How will we get what we want?” This phase of the SDLC starts by turning the software
specifications into a design plan called the Design Specification. All stakeholders then review this
plan and offer feedback and suggestions. It’s crucial to have a plan for collecting and
incorporating stakeholder input into this document. Failure at this stage will almost certainly
result in cost overruns at best and the total collapse of the project at worst.

4 Build
“Let’s create what we want.”

At this stage, the actual development starts. It’s important that every developer sticks to the
agreed blueprint. Also, make sure you have proper guidelines in place about the code style and
practices.
mtbl
STAGES & BEST PRACTICES
Following the best practices and/or stages of SDLC ensures the process works in a smooth,
efficient, and productive way.

5 Code Test
“Did we get what we want?” In this stage, we test for defects and deficiencies. We fix those issues
until the product meets the original specifications.

In short, we want to verify if the code meets the defined requirements.

6 Software Deployment
“Let’s start using what we got.”

At this stage, the goal is to deploy the software to the production environment so users can start
using the product. However, many organizations choose to move the product through different
deployment environments such as a testing or staging environment.
mtbl
PROJECT IDENTIFICATION

1 Business Identification

2 Emerging Technology

3 Reengineering

mtbl
Task 1: System Analyst

Select three (3) roles of a System Analyst. Cite different activities

that you have done in your previous subjects that can be related to
these roles. What characteristics should you have to successfully
accomplish these roles?

mtbl
ACTIVITY

THANKYOU
mtbl