Introduction to Systems Analysis and Design

1. Introduction to Systems Analysis and Design

2. Information Systems Engineering! Systems Engineering! Software Engineering! Information Systems Development! Systems Analysis and Design! Other names! Which one?

3. Completed Information System Design and Implementation Analysis An idea SYSTEMS ANALYSIS AND DESIGN

4. SYSTEMS ANALYSIS AND DESIGN • Systems Planning • Systems Analysis • Systems Design • Systems Implementation • Systems Evolution Planning Analysis Evolution Design Implementation

5. Business problems come in all sizes and shapes. • Name & Address Book • Course Registration • Student Grades • Payroll • ATM machine • Check-Out Counters • Order Fulfillment • Securities Portfolio Management • Space Shuttle Flight • Election Results • Video Games (Arcade and Home) • Q-Zar Laser Tag For Example:

6. System • group of interrelated components working together to achieve a common goal • ex: transportation system, university, information system • natural systems vs. man-made systems

7. Systems Model with Six Components • Name & Address System • Automobile • University • Inventory Management boundary SYSTEM processing controls inputs outputs feedback

8. Systems Model Hierarchy Suprasystem System Subsystem Water Vehicles Cruise Ship Staterooms

9. data people software procedures hardware An AUTOMATED INFORMATION SYSTEM IS • a type of manmade system • used by one or more persons • to help them accomplish some task or assignment that they have • utilizes hardware and software

10. DATA FUNCTIONS BEHAVIOR Characteristics of an Information System • DATA - input, output, or stored • FUNCTIONS - transformations or actions • BEHAVIOR - the observable effects of a request

11. data people software procedures hardware INTRODUCTION • Systems Analysis and Design is the process people use to create information systems SA&D

12. INTRODUCTION • SYSTEMS ANALYSIS and DESIGN produces information systems that are: • used internally within the organization • sold commercially via mail order or retail store • imbedded in products

13. Data vs. Information • data • raw, unprocessed facts • ex: order entry data • information • data which has been summarized, aggregated, processed into a format suitable for decision-making • sales report summarizing orders by product category and region

14. Information System • accepts data from the environment (inputs), manipulates the data (processing) to produce information (output) • IPO • functions include input, processing, output, storage,and control

15. Information Systems • support transaction processing • order entry, payroll • provide information to management • sales reports, employee skills analysis • support decision-making • marketing planning information system

16. Information System Components • people • procedures • data • hardware • software

17. Information Systems: The System Environment • internal environment or organizational context • users, management, organization structure, policies, procedures • external environment • customers, suppliers, governmental regulatory agencies, competitors

18. The Systems Approach • analysis • reduces a complex problem to a set of components and develops a solution for each component • synthesis • integrates the solutions for individual components into a single system

19. Systems Development Life Cycle • an engineering model which is applied to the development of information systems in business organizations • stages and tasks to be completed during the stages are identified • used as a plan for developing information systems

20. Three Stages of the SDLC • Analysis • study existing systems and identify problems or opportunities • develop system requirements • provide alternative systems as solutions • Design • use system requirements to design system outputs, inputs, databases and files, and processes • design will be used by the developer

21. Three Stages of the SDLC • Implementation • develop and test new system • train users and refine documentation • install and evaluate system

22. Analysis • Problem Detection • Initial Investigation • Feasibility Study • Prototyping • Requirements Analysis • Proposal

23. Design • Detailed Design of: • Outputs • Inputs • Files and Databases • Processes and Behaviors

24. Implementation • Programming and Testing (or Software Purchase) • User Training • Conversion • System Changeover • System Evaluation

25. Nine Activities of the SDLC • systems planning • feasibility study • requirements determination • conceptual design

26. Nine Activities of the SDLC • physical design, prototyping, construction and testing or purchase and testing, and integration • conversion • training • implementation • evolution for enhancement and maintenance

27. Systems Development Catalysts • user demand motivated by problems with existing systems • errors, efficiency, compatibility, need for system enhancements • technology push • new technologies motivate the development of systems to take advantage of new technologies • ex: CNA is replacing its mainframe systems with client-server systems

28. Systems Development Catalysts • strategic pull • new business strategies “pull” an organization into developing new systems • ex: new focus on global markets

29. Systems Development Goals System Qualtiy Project Management Organizational Relevance

30. System Quality • functionality • the system performs functions reliably, clearly, and efficiently • reliable systems are relatively error-free • clear systems have consistent and predictable functions • efficient systems execute functions with an acceptable speed

31. System Quality • flexibility • the system is flexible and adaptive to change • the system is adaptible if components are loosely coupled • procedural flexibility is achieved when procedures are easily adapted to accommodate organizational changes • the system is portable if it can operate in a variety of environments

32. System Quality • maintainability • the system is easily maintained if a modular design and appropriate documentation facilitate system updates and modifications

33. Project Management • deliver a high quality system • on-time • within-budget • high level of user commitment

34. Organizational Relevance • increase organizational efficiency • increase organizational effectiveness • provide strategic value

35. Introduction to Systems Analysis and Design Part 2

36. What makes Systems Analysis and Design a difficult process? • Problems tend to have poorly defined BOUNDARIES, initially • Problem SOLUTIONS are artificial • Problems are DYNAMIC • Problem solutions require INTERDISCIPLINARY knowledge and skills • Systems Analyst’s KNOWLEDGEBASE is continually expanding • Systems Analysis and Design is a highly COGNITIVE activity • Working with PEOPLE

37. Systems Analyst may be acting as a Project Manager for some of these interactions. Steering Committee* Users* SYSTEMS ANALYST Managers* Vendors Programmers & Tech. Staff Database Administrators * = Stakeholders Systems Analyst interactions with people during Systems Analysis & Design

38. What does a Systems Analyst do? • Studies the problems and needs of an organization looking for improvement opportunities: • increasing revenue/profit • decreasing costs • improving quality of service • add new system capabilities to enhance company’s competitiveness

39. What is a Systems Analyst responsible for? • Effective and efficient: • CAPTURE of input data • PROCESSING & STORAGE of data • DELIVERY of timely and accurate information

40. Environments/Tools Methodologies Methods & Techniques Concepts & Principles Problem Solving & People Skills Skills and Competencies of a Systems Analyst • Functional Business Knowledge • Verbal & written communication skills • Systems Analysis and Design work experience PLUS:

41. Analyst Skills Required • help users to determine requirements • technical knowledge in a field which is constantly changing • abstract or cognitive skills • problem solving skills • people skills • communication skills

42. Role of the Systems Analyst • analyze current systems and propose new systems • communicate effectively with programmers and users • develop information requirements • determine technical specifications • project management

43. Stakeholder Information System (6) Requirements (1) Continued Involvement (5) Design and Implementation Requirements Specification (3) Analysis Problem Definition Skills (2) Problem Solution Skills (4) Information Technology Staff General Model of Information Systems Engineering (“Partnership”)

44. DESIGN ANALYSIS Activities: • Physical Design • Prototyping (optional) • Software Construction/Purchase • User Documentation • Testing • Training • User Acceptance • Conversion • Implementing the system Activities: • Systems Planning • Feasibility Study (optional) • Requirements Determination • User Acceptance • Prototyping (optional) Deliverables: • Requirements Specification • Prototype (optional) Deliverable: • Information System Systems Analysis and Design Activities and Deliverables Two on-going activities • Project Management • Continuous Documentation

45. Systems Analysis and Design Projects • Labor intensive • smallest team = you • next smallest team = you and one other (user) • average team = systems analysts and users • articulation of the business problem is difficult • users and systems analysts come in all sizes and shapes

46. Where Do Systems Analysis and Design Projects Come From? • Problems • Opportunities • Directives

47. Who Initiates Projects? • users • management • systems analysts • need to comply with new industry regulations or standards • steering committees • clients or customers

48. Models, Methodologies, Techniques, Tools • model • abstract representation of reality • methodology • systematic description of the sequence of activities required to solve a problem • ex: Booch’s object-oriented methodology

49. Models, Methodologies, Techniques, Tools • tool • software product or quantative method that supports a technique • ex: Visio for drawing diagrams • techniques • specific activities associated with and used to implement a methodology • ex: data flow diagram

50. Traditional Approaches to the SDLC • sequential SDLC • project is divided into stages and each stage is completed before the next is started • waterfall SDLC • linear approach with significant overlap between stages • iterative SDLC • feedback method with the ability to return to a previous stage