What Are Tools and Techniques of System Analysis and Design
What Are Tools and Techniques of System Analysis and Design
STATE.
NAME: OYELOLA BUKOLA BIDEMI
MATRIC NO.: 23/0565
DEPARTMENT: HIM
LEVEL: 300L
COURSE TITLE: SYSTEM ANALYSIS AND DESIGN
CODE: CIS 342
LECTURER’S NAME: DR. ONAMADE
AND DATE: 15/04/2024
TOPIC: WHAT ARE TOOLS AND
TECHNIQUES OF SYSTEM ANALYSIS
AND DESIGN?
WHAT ARE TOOLS AND TECHNIQUES OF SYSTEM ANALYSIS AND DESIGN?
Systems analysis and design refers to the process of examining a business
situation with the intent of improving it through better procedures and methods.
Systems development can generally be thought of as having two major
components: Systems Analysts and Systems Design. Systems design is the process
of planning a new system or replace or complement an existing system. But before
this planning can be done, we must thoroughly understand the existing system
and determine how computers can best be used to make its operation more
effective. Systems analysis, then, is the process of gathering and interpreting facts,
diagnosing problems and using the information to recommend improvement to
the system. In brief, we can say that analysis specified what the system should do.
Design states how to accomplish the objectives.
There are various tools and techniques used throughout the process to ensure
that the system meets the requirements and objectives of the organization. Here's
an overview of some common tools and techniques:
1. Interviews: Conducting interviews with stakeholders, including end-users,
managers, and technical staff, to gather requirements and understand the
current system's strengths and weaknesses.
2. Questionnaires and Surveys: Distributing questionnaires or surveys to a
wider audience to collect data on user preferences, needs, and opinions.
3. Observation: Observing users in their work environment to gain insights
into how they interact with the current system and identify areas for
improvement.
4. Joint Application Development (JAD): Bringing together key stakeholders,
users, and developers in intensive workshops to collaboratively define
system requirements, features, and design elements.
5. Prototyping: Developing prototypes or mock-ups of the system to provide
stakeholders with a visual representation of the proposed solution and
gather feedback early in the development process.
6. Data Flow Diagrams (DFDs): Representing the flow of data through a
system using graphical models to illustrate processes, data stores, and data
flows.
7. Entity-Relationship Diagrams (ERDs): Modeling the relationships between
different entities in a system to design databases and understand data
requirements.
8. Structured Analysis: Breaking down the system into smaller, manageable
components to analyze processes, data flows, and dependencies.
9. Use Case Diagrams: Identifying and documenting various use cases to
illustrate how users interact with the system and the functionalities it
provides.
10.Structured Query Language (SQL): Using SQL to define and manipulate
databases, including creating tables, querying data, and managing
relationships between entities.
11.Unified Modeling Language (UML): Utilizing a standardized visual modeling
language to represent system architectures, designs, and processes using
diagrams such as class diagrams, sequence diagrams, and activity diagrams.
12.Decision Tables: Structured tables used to model complex business rules
and decision-making processes within a system.
13.Cost-Benefit Analysis: Evaluating the costs associated with developing and
implementing the system against the anticipated benefits to determine the
project's feasibility and return on investment.
14.Risk Analysis and Management: Identifying potential risks and
uncertainties associated with the project and developing strategies to
mitigate them.
15.Feasibility Study: Assessing the technical, operational, and economic
feasibility of implementing the proposed system to determine its viability.
These tools and techniques are often used iteratively throughout the system
analysis and design process, allowing for continuous refinement and improvement
of the proposed solution until it meets the organization's needs and objectives.
REFERENCES
Analysis & design of information systems – James A Senn, Mc-Graw Hill Book Co.
(1986)
Structured Analysis and Systems Specification – Tom De Marco, Prentice Hall
(1979)
Practical Guide to Structured system Design – Page Jones Mellir, The Yourdon
press (1980)