What is systems analysis and design, and why is it important?

What is systems analysis and design, and why is it important?

 

• Computer Application (app)
• A computer software program that executes on a computing device to carry out a specific function or set of related functions

 

• Information System
• A set of interrelated computer components that collect, processes, stores, and provides as output the information needed to complete business tasks

 

• Data
• Raw, unorganized facts are known as data. Data is useless until they set processed

 

• Information
• Processed data is known as information. Information are presented in a giving context and it is useful and it carries a value

 

Example:

• Data > 23
• Information > there are 23 students in the classroom

 

What is system analysis and design (SA&D)

 

• Systems analyst
• Process that help a person to get the idea and identify what the new system should accomplished.
• The person who is able to understand and capture the vision of the persons funding the project.
• Systems design
• Process which define and describe that details of the needed system

 

 

Why SA&D?

 

• The process of assessing a company issue with the goal of improving it through improved procedures and methods is referred to as system analysis and design
• System analysis and design is concerned with re sharping companies, enhancing performance and reaching profitability and growth goals

 

• System analyst
• A person who uses analysis and design techniques is known as a system analyst

 

 

Role of system analyst

 

• Researches problems and solutions for them
•  gather information to determine requirements
• Enhance a current system or design a new system
• Identifying the user requirements and the technical issues which the client is facing

 

Q1: Identify knowledge and skills needed by a system analyst to efficiently perform his role

 

• Team working
• Consulting for IT/IOT
• Communication skill
• Working under pressure
• Database design
• Designing

System development life cycle (SDLC)

 

The process of determining how an information system (IS) can support business needs, designing the system, building it, and delivering it to users

 

 

 

 

SDLC - planning

 

• The fundamental process of understanding
• why an information system should be built, and determining
• how the project team will go about building it
• Two steps:
• Project identification and selection
• Project initiation and planning
• Outcomes:
• System request, Feasibility report

 

Feasibility study

 

1. Feasibility study (conducted by system analyst )

 

• Time
• Budget
• Team competency
• Skill
• Knowledge
• Tech infrastructure
• Stakeholders
• Client
• System-users
• Owners
• Dev-team
• Sponsors

2. Time planning
3. Scope of work
4. Staff allocation
• Derived the development process into different parts and analysis amount of resources 

 

SDLC - Analysis

 

• The analysis phase answers the questions
• who will use the system
• what the system will do
• where and when it will be used

 

• Steps
• Study of the current system (as-is system)
• Requirements gathering

 

• Outcome:
• System proposal

 

• Content of system proposal
• Title page of project.
• Table of contents.
• Executive summary (including recommendations).
• Results of the systems study with appropriate documentation.
• Systems alternatives (three or four possible solutions).
• Systems analysts’ recommendations.
• Proposal summary.
• Appendices (assorted documentation, summary of phases, correspondence, and so on).

 

 

SDLC -  Design

 

• Decides how the system will operate,
• in terms of the hardware, software, and network infrastructure; the user interface, forms, and reports that will be used; and the specific programs, databases, and files that will be needed.
• Four steps
• Design Strategy
• Architecture Design
• Database and File Specifications
• Program Design

 

• Outcome
• Systems specification / system requirement specification - (SRS)

 

SDLC - Implementation

 

• The system is either developed or purchased (in the case of packaged software) and installed.
• Usually the longest and most expensive part of the process.

 

• Three steps
• System Construction
• Installation
• Support Plan

 

• Accuracy of the system