Module 3
Information Systems Analysis and Design
InforMatIon SySteMS analySIS and deSIgn
Applications of Information System
Information System for Strategic Advantage
Strategic role for information system
Breaking business barriers and Improving business qualities
Business process reengineering
Information system analysis and design: Information SDLC
Stages in System Analysis – Structured SAD and tools like DFD
(Data Flow Diagram)
Context Diagram Decision Table
System Development models
Emerging Concepts and Issues in Information Systems
BUSINESS PROCESS REENGINEERING (BPR)
Business process reengineering (BPR) is a strategic approach aimed at
radically redesigning and improving business processes to achieve
significant gains in efficiency, quality, and competitiveness.
BPR focuses on optimizing end-to-end processes and eliminating
redundancies.
BPR improvements can impact various aspects of the business including
cost, output, service, speed, and quality.
BUSINESS PROCESS REENGINEERING (BPR)
several key aspects:
1. Efficiency Enhancement
2. Customer-Centric Focus
3. Agility and Adaptability
4. Technology Integration
5. Cross-Functional Collaboration
6. Performance Measurement
7. Risk Mitigation
8. Cultural Transformation
9. Regulatory Compliance
10. Competitive Advantage
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
The Software Development Life Cycle (SDLC) is a systematic process for
planning, creating, testing, deploying, and maintaining software
applications or systems.
It provides a structured framework to manage software
development projects effectively, ensuring that the final product meets
quality standards and aligns with business requirements.
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
There are several models and methodologies used for SDLC, each with its own
variations, but they generally follow these key phases:
1. Planning
2. Analysis
3. Design
4. Implementation
5. Testing
6. Deployment
7. Maintenance and Support
8. Evaluation and Feedback
9. Documentation
10. Quality Assurance
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
1. Planning:
Objective: Define the project's purpose, goals, scope, and
requirements.
Activities: Gather user requirements, analyze feasibility, create
project schedules, allocate resources, and develop a project plan.
SoftWare deVeloPMent lIfe CyCle (SdlC)
2. Analysis:
Objective: Understand and document detailed requirements and
specifications.
Activities: Conduct interviews, surveys, and workshops with
stakeholders to gather in-depth requirements, create use cases,
and define system functionality.
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
Use cases
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
3. Design:
Objective: Develop a detailed blueprint of the software's
architecture and design.
Activities: Create high-level and low-level design documents,
define data structures, system architecture, user interfaces, and
algorithms.
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
3. Design:
High-Level Design
Overall system architecture
Major components and their relationships
Technology stack selection
Data flow diagrams
Database architecture
SoftWare deVeloPMent lIfe CyCle (SdlC)
Overall
system
architecture
SoftWare deVeloPMent lIfe CyCle (SdlC)
3. Design:
Low-Level Design
Module specifications
Interface definitions
Class diagrams and dependencies
Algorithm details
Data structure definitions
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
Class
diagrams
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
4. Implementation (Coding):
Objective: Transform design specifications into working code.
Activities: Write, test, and review code, following coding
standards and best practices. This phase involves actual software
development.
SoftWare deVeloPMent lIfe CyCle (SdlC)
4. Implementation (Coding):
Following established coding standards and guidelines
Implementing version control with tools like Git
Using continuous integration pipelines
Conducting regular code reviews
Documenting code properly
Employing test-driven development (TDD) where appropriate
SoftWare deVeloPMent lIfe CyCle (SdlC)
5. Testing:
Objective: Verify that the software meets requirements and
functions correctly.
Activities: Develop test cases, perform unit testing, integration
testing, system testing, and user acceptance testing (UAT).
Identify and resolve defects.
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
5. Testing:
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
6. Deployment (or Deployment and Release):
Objective: Deploy the software for end-users or clients.
Activities: Prepare installation packages, conduct system rollout,
provide user training, and ensure smooth transition from
development to production.
SoftWare deVeloPMent lIfe CyCle (SdlC)
6. Deployment (or Deployment and Release):
Preparing the production environment
Data migration (if applicable)
User training and documentation
Phased rollout strategies (canary releases, blue-green
deployment)
Monitoring for immediate post-deployment issues
SoftWare deVeloPMent lIfe CyCle (SdlC)
7. Maintenance and Support:
Objective: Sustain and enhance the software throughout its
lifecycle.
Activities: Address bug fixes, update software for new
requirements or technologies, and provide ongoing support to
users.
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
7. Maintenance and Support:
Bug fixes and patch management
Performance optimization
Feature enhancements
Security updates
User support
Documentation updates
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
8. Evaluation and Feedback:
Objective: Continuously improve the development process based
on feedback and lessons learned.
Activities: Gather feedback from users, developers, and
stakeholders to identify areas for process improvement.
SoftWare deVeloPMent lIfe CyCle (SdlC)
9. Documentation:
Objective: Create and maintain comprehensive documentation
throughout the SDLC.
Activities: Document requirements, design, code, test cases, and
user manuals to ensure clarity and maintainability.
SoftWare deVeloPMent lIfe CyCle (SdlC)
10. Quality Assurance:
Objective: Ensure that the software is of high quality and meets
defined standards.
Activities: Implement quality control processes, code reviews,
testing methodologies, and adherence to coding standards.
SYSTEM ANALYSIS
System analysis is a crucial phase in the development or
improvement of information systems.
It involves a systematic process of gathering, documenting, and
analyzing information to understand the existing system or to design
a new one that meets specific requirements.
SYSTEM ANALYSIS
The stages in system analysis typically include:
1. Problem Identification and Definition
2. Feasibility Study
3. Requirements Gathering and Analysis
4. System Modeling
5. Data Analysis and Design
6. System Architecture and Design
7. User Interface Design
8. System Requirements Specification
9. Cost-Benefit Analysis
[Link] Analysis
11. Review and Validation
[Link] System Proposal
SySteM analySIS
1. Problem Identification and Definition:
- Identify the need for a new system or the need to improve an
existing one.
- Define the objectives, scope, and constraints of the project.
- Establish clear goals and expectations for the system analysis
process.
SySteM analySIS
2. Feasibility Study:
- Evaluate the feasibility of the proposed project in terms of
technical, economic, operational, legal, and scheduling
aspects.
- Determine if the project is financially viable and justifiable.
- Explore alternative solutions and assess their pros and cons.
SYSTEM ANALYSIS
3. Requirements Gathering and Analysis:
- Gather information about the current system (if applicable) and
the needs of stakeholders.
-Create a detailed list of functional and non-functional
requirements.
- Conduct interviews, surveys, workshops, and observations to
elicit requirements.
SYSTEM ANALYSIS
4. System Modeling:
- Develop models and diagrams to represent the current system
(as-is) and the proposed system (to-be).
- Common modeling techniques include data flow diagrams
(DFDs), entity-relationship diagrams (ERDs), and use case
diagrams.
- Create process models to illustrate workflow and data flow
within the system.
SySteM analySIS
5. Data Analysis and Design:
- Analyze the data requirements, including data structures, data
sources, and data relationships.
- Design the database schema, data dictionaries, and data
flow diagrams.
- Define data validation rules and data storage mechanisms.
SySteM analySIS
6. System Architecture and Design:
- Define the system architecture, including hardware,
software components, and interfaces.
- Create system design specifications that detail the system's
structure and components.
- Consider scalability, security, performance, and integration
requirements.
SYSTEM ANALYSIS
7. User Interface Design:
- Design the user interface to ensure it is user-friendly and meets
user expectations.
- Create prototypes, wireframes, and mock-ups to visualize
the user interface.
- Gather user feedback and refine the design accordingly.
SYSTEM ANALYSIS
8. System Requirements Specification:
- Document all gathered requirements, including functional and
non-functional requirements, in a comprehensive specification
document.
- Ensure that the document is clear, concise, and well-
organized.
SySteM analySIS
9. Cost-Benefit Analysis:
- Conduct a cost-benefit analysis to evaluate the project's
financial feasibility.
- Compare the costs of development and maintenance with the
expected benefits and return on investment (ROI).
SySteM analySIS
10. Risk Analysis:
- Identify potential risks and uncertainties associated with
the project.
- Develop a risk mitigation plan to address and manage these
risks effectively.
SYSTEM ANALYSIS
11. Review and Validation:
- Review the system analysis documentation with stakeholders
to ensure accuracy and completeness.
- Validate that the proposed system aligns with the initial project
objectives and requirements.
SYSTEM ANALYSIS
12. Final System Proposal:
- Create a final system proposal that includes a summary of
findings, recommended solutions, project timeline, and
budget estimates.
- Seek approval from stakeholders to proceed with system
development or implementation.