Week1- Introduction
Introduction to Systems Analysis and Design
Presented by Dr. Azi Meskaran at Nottingham Trent University
Focuses on the formal techniques necessary for transforming business needs into effective information systems.
Overview of Systems Analysis and Design
Definition: A structured process for studying business needs, identifying issues, and creating efficient information systems.
Significance: Considered a core discipline in the Computing and Information Technology industry.
Learning Objectives
Introduction to the fundamental principles of Systems Analysis and Design.
Gain working knowledge of key systems development methodologies.
Learn techniques and tools for developing computer-based systems.
Importance of Systems Analysis and Design
Career Benefits:
Essential for careers in IT and systems development, as all modern societies depend on computer systems for economic functionality.
Involves developing knowledge and skills crucial for a Systems Analyst role, enabling significant contributions to systems development processes.
Project Failure Statistics
Failure Rate: Up to 70% of IT projects report failure, primarily due to poor system analysis and design.
Quote: "If you fail to plan, you plan to fail!"
Chaos Report Insights
Source: Standish Group International's Chaos Report (1994)
Survey Details:
Included responses from 365 US businesses regarding 8,380 IT applications.
Top 10 Reasons for Project Failure:
Lack of User Input: 12.8%
Incomplete Requirements & Specifications: 12.3%
Changing Requirements & Specifications: 11.8%
Lack of Executive Support: 7.5%
Technology Incompetence: 7%
Lack of Resources: 6.4%
Unrealistic Expectations: 5.9%
Unclear Objectives: 5.3%
Unrealistic Time Frames: 4.3%
New Technology: 3.7%
Examples of Software Failures
Major Losses in IT Systems:
Company
Year
System Details
Loss (USD $)
Ford Motor Co. (US)
2004
Purchasing system abandoned after deployment
400 million
Hewlett Packard (US)
2004
ERP with software errors
160 million
HRM Inland Rev (UK)
2004
Software errors led to tax credit overpayment
3.45 billion
Sainsbury's (UK)
2004
Supply chain system abandoned
527 million
Dept of Health (UK)
2006
NHS IT system integration delayed (80% completed)
20 billion
Ministry of Justice (UK)
2007-09
C-Nomis offender MIS abandoned
245 million
Cabinet Office (UK)
2007
Secure communications network abandoned
38.6 million
Border Agency (UK)
2007
eBorders system delayed to 2015
1.7 billion
BBC (UK)
2014
Failure to digitize media due to confusion
153 million
The Importance of Structured Approaches
Complex Systems Development:
Creating intricate systems is non-intuitive.
The cost of required changes escalates exponentially after the initial deployment.
Late modifications can lead to project failures characterized by budget overruns or reduced features.
Need for Building Models
Models as Visual Aids:
Models help visualize the final product, ensuring it aligns with client specifications.
Function as communication tools to confirm that proposed builds meet customer expectations.
Provide concrete support for identifying errors in requirement understanding.
Birthplace of Project Ideas
Identifying Business Needs:
Needs may arise from:
New marketing strategies
Targeting new customer demographics
Awareness of emerging technologies (e.g., Cloud Computing)
Responses to internal challenges (e.g., loss of market share).
Stakeholders in Information Systems
Definition: Any individual with an interest in the information system, technical or non-technical.
Classification of Stakeholders:
System owners
System users
Systems analysts
System designers
System builders (programmers)
IT vendors and consultants
Role of Systems Analyst
Key Responsibilities:
Analyze business situations and identify enhancement opportunities.
Design information systems to implement identified improvements.
Interact with diverse groups of individuals including technical specialists and business representatives.
Skills Required for Systems Analysts
Key Skills:
Technical: Understanding of relevant technologies.
Business: Knowledge of organizational processes.
Analytical: Problem-solving capability.
Communication: Ability to articulate ideas to both technical and non-technical audiences.
Interpersonal: Skills to lead and motivate teams effectively.
Ethics: Commitment to fair treatment and confidentiality in information handling.
Systems Development Life Cycle (SDLC)
Structure of SDLC:
Consists of four primary phases:
Planning
Analysis
Design
Implementation
Each phase is further broken down into specific steps and requires documentation (deliverables).
Execution Patterns
Phases can be executed in various ways:
Sequentially
Incrementally
Iteratively
Other methodological patterns will be explored in future lessons.
Overview of Methodologies
Definition of Methodology: A formalized approach to implementing the SDLC.
Categories of Methodologies:
Structured
Object-oriented
Rapid action development
Agile
Conclusion on Systems Analyst Roles
Systems analysts are crucial players in systems development projects, requiring diverse skills and adapting to various roles throughout the SDLC process.