UNIT 1 - Introduction to Systems Analysis and
Design (SAD)
1. Introduction to SAD
• Definition: Systems Analysis and Design (SAD) involves the process of creating and
supporting information systems. It includes various methodologies and approaches
for developing these systems.
• Importance: SAD is crucial for ensuring that information systems meet user and
business requirements and are efficient, effective, and sustainable.
1.2 Fundamentals of Systems
1.2.1 Important Terms Related to Systems
• System: An organized relationship among functioning units or components.
• Subsystems: Smaller systems within a larger system, each contributing to the
overall goal.
• Environment: Everything external to the system that interacts with it.
1.2.2 Classification of Systems
• Formal vs. Informal: Formal systems have predefined rules and structures, while
informal systems do not.
• Physical vs. Abstract: Physical systems are tangible (e.g., computers), while
abstract systems are conceptual (e.g., a company).
• Open vs. Closed: Open systems interact with the environment; closed systems are
isolated.
• Manual vs. Automated: Manual systems require human intervention; automated
systems are used without direct human input.
1.2.3 Real Life Business Subsystems
• Examples: Product design, production, sales, delivery, and service.
• Integration: These subsystems work together to achieve business goals.
1.3 Real-Time Systems
• Definition: Systems that respond to input at once.
• Types: Hard (strict time constraints) and Soft (more flexible).
1.4 Distributed Systems
• Characteristics: Data and process components are distributed across multiple
network locations.
• Benefits: Resource sharing, computation speedup, reliability, and improved
communication.
1.5 Development of a Successful System
• Approach: Involves understanding requirements, problem-solving, and adopting a
suitable development method.
• Phases: Analysis, Design, Construction & Implementation, and Support.
,1.6 Various Approaches for Development of Information Systems
1.6.1 Structured Analysis and Design Approach
• Focus: Emphasizes reducing maintenance time and effort through systematic
analysis and design.
• Techniques: Data flow diagrams for process modeling, entity-relationship diagrams
for data modeling.
1.6.1 Prototype
• Concept: Developing a functional version of the desired system to test ideas and
assumptions.
• Process: Iterative development based on user feedback.
1.6.2 Joint Application Development (JAD)
• Method: Collaborative approach involving users, managers, and analysts.
• Goal: To define system requirements and complete design details through intensive
meetings.
Potential Questions and Answers
Q: What is the importance of real-time systems in SAD? A: Real-time systems are crucial
in SAD as they ensure immediate response to inputs, which is vital in applications with
strict time constraints, like medical or industrial control systems.
Q: How does the prototype approach help the development of information systems?
A: The prototype approach allows for testing and refining system functionalities iteratively
based on real user feedback, leading to a more user-centered and efficient final product.
Q: What is the role of distributed systems in modern business? A: Distributed systems
align with the needs of modern, geographically dispersed businesses by supplying resource
sharing, faster computations, reliability, and improved communication across multiple
locations.
Q: Why are structured analysis and design important in SAD? A: Structured analysis
and design supply a systematic approach to understanding and documenting the business
requirements and functionalities of a system, leading to more efficient development and
easier maintenance.
UNIT 2 - Systems Analyst – A Profession
2.2 Why Do Businesses Need Systems Analysts? (Page 18)
• Need for Systems Analysts:
o Businesses require systems analysts to design and analyze computerized
systems.
, o Their role is crucial in bridging the gap between business needs and
technological solutions.
o They ensure that information systems are effectively developed and
operated, aligning with business objectives.
2.3 Users (Page 18)
• User Classification:
o Users are classified as internal (employees) and external (customers and
other businesses).
o Systems analysts must understand and cater to the needs of both types of
users.
2.4 Analysts in Various Functional Areas (Page 19)
• 2.4.1 Systems Analyst in Traditional Business:
o Centralized information services.
o Systems analysts focus on system development, data administration,
telecommunications, end-user computing, and computer operations.
• 2.4.2 Systems Analyst in Modern Business:
o Decentralized, dynamic teams.
o Focus on outsourcing and consulting.
o Adapting to changing business environments and technologies.
2.5 Role of a Systems Analyst (Page 20)
• Roles:
o Change Agent: Managing and implementing change.
o Investigator and Monitor: Investigating existing systems and monitoring
project progress.
o Architect: Designing information system architecture.
o Psychologist: Understanding user behavior and needs.
o Motivator and Intermediary: Encouraging system use and mediating
between different parties.
2.6 Duties of a Systems Analyst (Page 21)
• Key Duties:
o Defining and prioritizing user requirements.
o Analyzing and evaluating current systems.
o Solving problems and providing alternative solutions.
o Drawing up functional specifications and designing systems.
o Evaluating systems post-implementation.
2.7 Qualifications of a Systems Analyst (Page 22)
• 2.7.1 Analytical Skills:
o System study and organizational knowledge.
o Problem identification, analysis, and solving.
• 2.7.2 Technical Skills: