SAD Introduction
- 1. SYSTEMS ANALYSIS AND DESIGN INTRODUCTION
- 2. Course Instructor Er. Ashwani Malhotra ( B.Tech(IT) , M.Tech(CSE) (Pursuing) )
- 3. What is Systems Analysis and Design (SAD)? Systems Analysis : understanding and specifying in detail what an information system should do • System Design : specifying in detail how the parts of an information system should be implemented Why is it important? • Success of information systems depends on good SAD • Widely used in industry - proven techniques • Part of career growth in IT - lots of interesting and well-paying jobs! • Increasing demand for systems analysis skills
- 4. Systems Analysis and Design is the process people use to create (automated) information systems Systems Analysis & Design Information System
- 5. Information Systems Engineering! Software Engineering! Information Systems Development! Systems Engineering! Systems Analysis and Design! Other names...! Which one? Is there an “official” name?
- 6. A title given to a person who studies the problems and needs of an organization looking for improvement opportunities. Systems Analyst Other names: Software Engineer Systems Engineer Software Developer Programmer/Analyst Nerd or Hacker! (joking!)
- 7. An idea Analysis Design and Implementation Completed Information System SYSTEMS ANALYSIS AND DESIGN: A Condensed (Informal) Perspective Time
- 8. SYSTEMS ANALYSIS AND DESIGN : A Complete (Formal) Perspective Systems Planning Systems Analysis Systems Design Systems Implementation Systems Evolution Planning Evolution Implementation Design Analysis
- 9. System Natural Fabricated Information Systems Others Automated Information Systems Others
- 10. Name & Address Book CD Collection Course Registration Reservations Student Grades Payroll ATM machine & Banking in General Check-Out Counters at Retail Stores Order Fulfillment - Mail or Web Ordering Manufacturing Securities Portfolio Management Space Shuttle Flight Election Results Video Games (Arcade and Home) Business “problems” come in all sizes and shapes! Examples:
- 11. A SYSTEM is a set of: interrelated components working together for a common purpose System
- 12. A Generic System Model (with Six Components) Examples: Automobile Student Registration System Others... SYSTEM boundary inputs outputs processing controls feedback
- 13. System Model Hierarchy Water Vehicles Cruise Ship Staterooms Suprasystem System Subsystem “ bigger” “ smaller” Template Example
- 14. An INFORMATION SYSTEM is: a type of fabricated system used by one or more persons to help them accomplish some task or assignment they have people procedures data An Information System: includes the 3 aspects of a system supports policies & procedures has three additional components - data, people, procedures - in addition to the six general system components
- 15. An AUTOMATED INFORMATION SYSTEM IS: a type of fabricated system used by one or more persons to help them accomplish some task or assignment they have utilizes hardware and software in addition to data, people, procedures … plus all the aspects of a system people procedures data software hardware
- 16. DATA - input, output, or already stored electronically FUNCTIONS - transformations or actions taken BEHAVIOR - the observable effects from interaction An AUTOMATED INFORMATION SYSTEM has three basic characteristics to consider: (Plus the six system components: input, output, processing, control, feedback and boundary) DATA FUNCTIONS BEHAVIOR
- 17. Systems Analysis and Design is the process people use to create (automated) information systems people procedures data software hardware SA&D
- 18. The people who do SYSTEMS ANALYSIS and DESIGN produce information systems that are: used internally within the organization sold commercially via mail/web order or retail store imbedded in products
- 19. Initially, problem domains (areas) tend to have poorly defined BOUNDARIES Problem domain SOLUTIONS are artificial Problem domains are DYNAMIC Problem domain solutions usually require INTERDISCIPLINARY knowledge and skills Systems Analyst’s KNOWLEDGEBASE is continually expanding Systems Analysis and Design is a highly COGNITIVE activity Working with PEOPLE What makes Systems Analysis and Design a difficult activity?
- 20. Systems Analyst’s interactions with people during Systems Analysis & Design SYSTEMS ANALYST Users* Steering Committee* Vendors Programmers & Tech. Staff Database Administrators Managers* * = Stakeholders Systems Analyst may be acting as a Project Manager for some of these interactions.
- 21. Studies the problems and needs of an organization looking for improvement opportunities for: increasing revenue/profit decreasing costs improving quality of service What does a Systems Analyst do?
- 22. Effective and efficient: CAPTURE of input data PROCESSING & STORAGE of data DELIVERY of timely and accurate information What is a Systems Analyst responsible for?
- 23. Functional Business Knowledge Verbal & written communication skills Systems Analysis and Design work experience Skills and Competencies of a Systems Analyst PLUS: Concepts & Principles Environments/Tools Problem Solving & People Skills Methods & Techniques Methodologies
- 24. Requirements Specification (3) General Model of Information Systems Development (“Partnership”) Stakeholder Information Technology Staff Analysis Design and Implementation Requirements (1) Continued Involvement (5) Information System (6) Problem Definition Skills (2) Problem Solution Skills (4)
- 25. Systems Analysis and Design Activities and Deliverables ANALYSIS Activities: Systems Planning Feasibility Study (optional) Requirements Determination Conceptual Design User Acceptance Prototyping (optional) Deliverables: Requirements Specification Prototype (optional) DESIGN Activities: Deliverable: Physical Design Prototyping (optional) Software Construction/Purchase User Documentation - “Deliverable” Testing Training User Acceptance Conversion Implementing the system Information System Project Management Project Documentation - “Scaffolding” Two (2) additional on-going activities:
- 26. Labor intensive Smallest team = you Next smallest team = you and one other (user) Average team = several systems analysts and users Articulation of the business problem is difficult Users and systems analysts come in all sizes and shapes Systems Analysis and Design Project Observations
- 27. Problems - “something needs to be fixed” Opportunities - “good deals” Directives - “do it…or else…” Where Do Systems Analysis and Design Projects Come From? ... and are bounded by Constraints
- 28. Planning Feasibility Study (optional) Requirements Determination Conceptual Design Physical Design Construction and/or Purchase (prototype) Training Conversion - old to new Implementation Evolution - maintenance & enhancements SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC) Analysis Design and Implementation
- 29. Sequential or Traditional SDLC 1. Planning for an information system 2. Feasibility Study (optional) 3. Requirements Determination (gathering) 4. Conceptual design 5. Physical design and/or purchase and/or prototyping 6. Conversion from current system to new/changed system 7. Training 8. Implementation 9. Evolution for enhancements and maintenance Waterfall or Staircase SDLC Planning Feasibility Study Requirements Determination Conceptual Design Physical Design Conversion Training Implementation Evolution “ Begin” “ End” “ Begin” “ End”
- 30. Planning Feasibility Study Requirements Determination Conceptual Design Physical Design Conversion Training Implementation Evolution Iterative SDLC Risk Analysis Spiral SDLC SDLC Activities Verification/Test
- 31. Boehm, 1988
- 32. The system is for the user A W ork B reakdown S tructure should be used (ie., SDLC) Systems analysis and design is iterative and overlapping Information systems are capital investments for the business Project manager may have the authority to cancel a project Project documentation is important all along the way Senior management approval/support is very important Principles to Guide Systems Analysis & Design
- 33. Thanks