life
life
life
cycle
life
cycle
life cycle
life
cycle
System Development life cycle
System Development life cycle
plays a crucial role in the implementation of information systems
System Analysis and Design process in the System Development life cycle is a crucial stage where:
System Analysis and Design process in the System Development life cycle is a crucial stage where:
the needs of the business or users are
studied and translated into a specific software or system solution
System Analysis
Week 3 : System requirements
System analysis refers to the process of
What is System analysis?
System analysis refers to the process of
What is System analysis?
System analysis refers to the process of
Organizations can also evaluate how improvements might address future business needs at this point.
What is System analysis?
Objective: The main goal is to understand and document
what the system needs to do (requirements).
What is the objective of system analysis?
Objective: The main goal is to understand and document
what the system needs to do (requirements).
It involves identifying problems with the current system, defining user requirements, and understanding business processes.
What is the objective of system analysis?
The key aspects of Information System Analysis
1. Problem Identification: Understanding and describing the main problem or need that the information system aims to address is the first step in this process.
The key aspects of Information System Analysis
1. Problem Identification: Understanding and describing the main problem or need that the information system aims to address is the first step in this process.
It involves determining the difference between the planned and actual states of situations.
The key aspects of Information System Analysis
1. Problem Identification: Understanding and describing the main problem or need that the information system aims to address is the first step in this process.
It involves determining the difference between the planned and actual states of situations.
The 'what' and 'why'—what problems are being addressed and why a new or improved system is required—are the main points of focus here.
The key aspects of Information System Analysis
1. Problem Identification: Understanding and describing the main problem or need that the information system aims to address is the first step in this process.
The key aspects of Information System Analysis
1. Problem Identification: Understanding and describing the main problem or need that the information system aims to address is the first step in this process.
The key aspects of Information System Analysis
2. Requirements Gathering: Once the problem or need is clearly identified, the next step is to collect detailed information about what users, stakeholders, and the business itself require from the system.
The key aspects of Information System Analysis
2. Requirements Gathering: Once the problem or need is clearly identified, the next step is to collect detailed information about what users, stakeholders, and the business itself require from the system.
Requirements gathering is a critical process as it forms the foundation for how the system will be designed and developed. It includes gathering both functional requirements (specific features or functions the system should have) and non-functional requirements (such as usability, reliability, and performance criteria).
The key aspects of Information System Analysis
2. Requirements Gathering: Once the problem or need is clearly identified, the next step is to collect detailed information about what users, stakeholders, and the business itself require from the system.
The key aspects of Information System Analysis
2. Requirements Gathering: Once the problem or need is clearly identified, the next step is to collect detailed information about what users, stakeholders, and the business itself require from the system.
The key aspects of Information System Analysis
3. Data Analysis: Analyzing the organization's offer data flows as well as processes is part of this aspect. To map out how data is now processed, where it comes from, how it's used, and where it goes.
The key aspects of Information System Analysis
3. Data Analysis: Analyzing the organization's offer data flows as well as processes is part of this aspect. To map out how data is now processed, where it comes from, how it's used, and where it goes.
Mistakes, errors, and gaps in the current data management system are found with the aid of this analysis. It offers information about how data handling might be enhanced as well as recommendations for how the new system should handle, store, and process data.
The key aspects of Information System Analysis
3. Data Analysis: Analyzing the organization's offer data flows as well as processes is part of this aspect. To map out how data is now processed, where it comes from, how it's used, and where it goes.
The key aspects of Information System Analysis
4. Requirement Specification: The final step in the analysis phase is to document all the findings in a clear and comprehensive set of requirements. This document, often called a Requirements Specification, serves as a blueprint for the design and development of the system (Next week).
The key aspects of Information System Analysis
4. Requirement Specification: The final step in the analysis phase is to document all the findings in a clear and comprehensive set of requirements. This document, often called a Requirements Specification, serves as a blueprint for the design and development of the system (Next week).
Most crucially, though, is that it leaves open the question of how these criteria should be technically achieved; that is the domain of system design (Next week).
Use Case Diagram
Use case diagram is frequently used for the following reasons, and use case diagrams are usually created early in the development process:
Use Case Diagram
Use case diagram is frequently used for the following reasons, and use case diagrams are usually created early in the development process:
Use Case Diagram (Visual Representation)
Actor
Use Case Diagram (Visual Representation)
Use Case
Use Case Diagram (Visual Representation)
Use Case Diagram (Visual Representation)
Use Case Relationship
<<Extends>>: an extended partnership.
An optional or additional functionality
Use Case Diagram (Visual Representation)
Use Case Relationship
<<Extends>>: an extended partnership.
An optional or additional functionality
<<Include>>: The relationship is defined as an include relationship
To denote a relationship that is required
Use Case Diagram (Visual Representation)
Use Case Diagram (Visual Representation)
Use Case Diagram (Visual Representation)
Activity Diagram
To describe dynamic aspects of the system
Activity Diagram
To describe dynamic aspects of the system
Activity Diagram
To describe dynamic aspects of the system
Determine potential use cases by looking at business procedures.
Exercise 1: Use Case Diagrams
Exercise 2: Activity Diagrams
Assignment: Information System Analysis Report
(the deadline for submissions is Week 4)