Directorate of Distance Education

SwamiVivekanandSubhartiUniversity
IIYear

CourseCode : MBA-IT2

CourseTitle : SystemAnalysis&Design&SoftwareEngineering

AssignmentNo. : MBA-IT2

Q1. What is System Analysis and Design?

Answer: System Analysis and Design (SAD) is a systematic approach to
solving business problems and improving organizational processes
through the development and implementation of information systems. It
involves understanding the requirements of a business, designing a
system to meet those requirements, and then implementing, testing, and
maintaining that system.
* System Analysis focuses on understanding and defining the "what" of
the system. It involves gathering information, analyzing current
processes, identifying problems and opportunities, and specifying the
functional and non-functional requirements of the new system.
* System Design focuses on defining the "how" of the system. It involves
creating a blueprint for the system, including its architecture, components,
interfaces, databases, and user experience. It translates the requirements
identified during analysis into a detailed technical specification.
In essence, SAD bridges the gap between business needs and
technological solutions, ensuring that the developed system effectively
supports the organization's goals.

1
Q2. What is the system analysis and design process?
Answer: The System Analysis and Design process typically follows a
structured lifecycle, often referred to as the System Development Life
Cycle (SDLC). While specific phases and terminology can vary, a common
SDLC model includes the following stages:
* Planning (or Project Initiation):
* Identify the problem or opportunity.
* Conduct a feasibility study (technical, economic, operational, schedule,
legal).
* Define the project scope, objectives, and deliverables.
* Form a project team and develop a project plan.
* Analysis:
* Gather detailed requirements from users and stakeholders using
techniques like interviews, surveys, observation, and document analysis.
* Analyze existing systems and processes.
* Model the system's functional and non-functional requirements (e.g.,
use cases, data flow diagrams, entity-relationship diagrams).
* Identify and prioritize system features.
* Design:
* Develop the logical design (what the system will do, independent of
technology) and physical design (how the system will be built, including
specific technologies).
* Design the system architecture, user interface (UI), database structure,
inputs, outputs, and controls.
* Create detailed specifications for programs, modules, and interfaces.
* Implementation (or Development):
* Code and build the system components based on the design
specifications.
* Perform unit testing of individual modules.

2
 * Integrate different modules and perform integration testing.
* Testing:
* Conduct various types of testing, including:
* System Testing: Testing the complete, integrated system to verify it
meets requirements.
* User Acceptance Testing (UAT): Users test the system to ensure it
meets their business needs.
* Performance Testing: Evaluating system responsiveness, stability,
and scalability.
* Security Testing: Identifying vulnerabilities.
* Deployment (or Conversion):
* Install the system in the production environment.
* Migrate data from old systems.
* Train end-users on the new system.
* Choose a conversion strategy (e.g., direct, parallel, phased, pilot).
* Maintenance (or Operations and Support):
* Monitor the system for performance and issues.
* Apply patches and updates.
* Perform corrective maintenance (fixing bugs), adaptive maintenance
(modifying to changing environment), and perfective maintenance
(improving features).
* Provide ongoing user support.
This iterative process helps ensure that the developed system is robust,
efficient, and meets the evolving needs of the organization.

3
Q3. Write the benefits of system analysis and design.
Answer: System Analysis and Design (SAD) offers numerous benefits to
organizations, leading to more effective, efficient, and user-friendly
information systems. Key benefits include:
* Improved Problem Solving: SAD provides a structured approach to
identify, analyze, and solve business problems, leading to well-defined
solutions rather than ad-hoc fixes.
* Better System Quality: By meticulously defining requirements and
designing the system before coding, SAD helps create systems that are
more reliable, accurate, secure, and performant.
* Increased User Satisfaction: Involving users throughout the analysis
and design phases ensures that the system meets their actual needs and
preferences, leading to higher adoption rates and satisfaction.
* Reduced Development Costs and Time: A clear understanding of
requirements and a well-thought-out design minimize rework, errors, and
scope creep during development, thereby reducing overall costs and
project timelines.
* Enhanced Communication: SAD provides standardized documentation
and models (e.g., DFDs, ERDs, use cases) that facilitate clear
communication among stakeholders, developers, and users, reducing
misunderstandings.
* Better Decision-Making: The analysis phase provides a deep
understanding of current processes and data, which can inform strategic
business decisions.
* Easier Maintenance and Evolution: Well-designed systems with clear
documentation are easier to maintain, troubleshoot, and adapt to future
changes or new requirements.
* Risk Mitigation: By identifying potential risks (technical, operational,
financial) early in the process, SAD allows for proactive strategies to
mitigate them, reducing project failures.
* Improved Business Processes: The analytical nature of SAD often
reveals inefficiencies in existing business processes, leading to process
re-engineering and optimization even before system development.

4
* Competitive Advantage: Organizations that effectively leverage SAD
can develop systems that are innovative, responsive to market changes,
and provide a competitive edge.
* Effective Resource Utilization: By having a clear plan, resources (human,
financial, technological) can be allocated more effectively, avoiding
wastage.

Q4. Discuss the 7 tools and techniques of system analysis and design.
Answer: System Analysis and Design employs various tools and
techniques to gather information, model processes, represent data, and
communicate system specifications. While the "7 tools" can vary
depending on the context or framework, here are seven commonly used
and essential tools and techniques:
* Data Flow Diagrams (DFDs):
* Purpose: Graphical representation of the flow of data through an
information system. They show how data enters, is processed, stored,
and exits a system.
* Components: Processes, external entities, data stores, and data flows.
* Benefit: Helps visualize the logical flow of data, identify inefficiencies,
and understand system boundaries.
* Entity-Relationship Diagrams (ERDs):
* Purpose: Illustrate the relationships between entities (data objects) in
a database. They are crucial for database design.
* Components: Entities (tables), attributes (columns), and relationships
(how tables are linked).
* Benefit: Provides a clear picture of the data structure, ensures data
integrity, and facilitates effective database design.
* Use Case Diagrams:
* Purpose: Describe the functional requirements of a system from the
user's perspective. They show how users (actors) interact with the

5
system to achieve specific goals (use cases).
* Components: Actors, use cases, system boundary.
* Benefit: Excellent for capturing functional requirements,
understanding user interactions, and defining system scope.
* Interviews:
* Purpose: A direct and personal method for gathering detailed
information, opinions, and insights from stakeholders, users, and experts.
* Technique: Structured, semi-structured, or unstructured conversations.
* Benefit: Allows for clarification, probing deeper into topics, and
building rapport.
* Questionnaires (Surveys):
* Purpose: Efficiently gather information from a large number of people.
They can be open-ended or closed-ended.
* Technique: Distributing written or electronic forms with a set of
questions.
* Benefit: Cost-effective for large groups, can gather quantitative data,
and ensures anonymity if required.
* Decision Tables/Trees:
* Purpose: Tools used to represent complex decision logic in a clear
and concise manner.
* Decision Table: A tabular representation showing conditions, actions,
and rules.
* Decision Tree: A tree-like model of decisions and their possible
consequences.
* Benefit: Helps in understanding and documenting business rules,
ensuring all conditions and actions are covered, and avoiding ambiguity.
* Prototyping:
* Purpose: Creating a preliminary working model of the system (or parts
of it) to get user feedback early in the development cycle.

6
 * Technique: Developing throwaway or evolutionary prototypes (e.g.,
mock-ups, wireframes, functional prototypes).
* Benefit: Reduces ambiguity, validates requirements, identifies design
flaws early, and improves user engagement and satisfaction.
Other important tools and techniques include Data Dictionaries,
Structured English, Pseudocode, Gantt Charts, PERT Charts, Feasibility
Studies, and various diagramming tools like UML (Unified Modeling
Language) for more comprehensive modeling.

Q5. What is system analysis and design in software engineering?

Answer: In the context of Software Engineering, System Analysis and
Design (SAD) represents the crucial initial phases of the software
development lifecycle (SDLC) that focus on understanding the problem
domain and devising a solution before actual coding begins. It is
foundational to building high-quality, maintainable, and successful
software systems.
Here's how SAD fits into software engineering:
* Requirement Engineering (Analysis Phase):
* This is where system analysis primarily takes place within software
engineering. It involves:
* Elicitation: Gathering requirements from stakeholders through
various techniques (interviews, brainstorming, surveys, observation,
prototyping).
* Analysis: Understanding, categorizing, and prioritizing requirements,
resolving conflicts, and ensuring completeness and consistency. This
often involves creating models like Use Case Diagrams, Data Flow
Diagrams, and functional decomposition.
* Specification: Documenting the requirements clearly and precisely in
a Software Requirements Specification (SRS) document.
* Validation: Reviewing and verifying that the documented
requirements accurately reflect the user's needs and are achievable.

7
 * Goal: To define what the software system must do to satisfy user
needs and business objectives.
* Software Design (Design Phase):
* This is where system design is performed. It translates the "what"
(requirements) into "how" the software will be built. It involves:
* Architectural Design: Defining the overall structure of the software
system, its major components, their relationships, and the
communication mechanisms between them. This includes choosing
design patterns and architectural styles.
* High-Level Design (System Design): Breaking down the system into
smaller, manageable modules or subsystems, defining their
responsibilities, and interfaces.
* Detailed Design (Component Design): Specifying the internal logic,
data structures, and algorithms for each module or component. This
often involves class diagrams, sequence diagrams, and pseudocode.
* Database Design: Designing the structure of the database, including
tables, relationships, and data integrity constraints (often using ERDs).
* User Interface (UI) Design: Designing the look, feel, and interaction
flow of the user interface.
* Goal: To create a detailed blueprint that guides the implementation
(coding) phase, ensuring the software is well-structured, efficient,
scalable, and maintainable.
Relationship and Importance in Software Engineering:
* Foundation for Quality: SAD lays the groundwork for software quality.
Errors or omissions in analysis and design are exponentially more
expensive to fix in later stages (coding, testing) or after deployment.
* Risk Reduction: Thorough SAD identifies potential technical,
operational, and financial risks early, allowing for mitigation strategies.
* Communication Bridge: It serves as a vital communication bridge
between business stakeholders (who understand the problem) and
technical developers (who build the solution).
* Structure and Disciplined Approach: Software engineering emphasizes

8
a systematic and disciplined approach to software development. SAD
provides this structure, ensuring that development is not haphazard.
* Maintainability and Scalability: A well-designed system is inherently
more maintainable, adaptable to future changes, and scalable to handle
increased loads or functionalities.
* Cost-Effectiveness: Although SAD involves upfront time and effort, it
significantly reduces rework and debugging later, leading to overall cost
savings.
In essence, System Analysis and Design are indispensable in software
engineering for translating abstract business requirements into concrete,
feasible, and effective software solutions. They dictate the success and
longevity of any software product.