SA1.pdf

SYSTEM ANALYSIS AND DESIGN  Module 1 Sub Topic 1 - Information Systems Introduction to System Analysis and Design Information system  Information systems are interrelated components working together to collect, process, store, and disseminate information to sup...

SYSTEM ANALYSIS AND DESIGN  Module 1 Sub Topic 1 - Information Systems Introduction to System Analysis and Design Information system  Information systems are interrelated components working together to collect, process, store, and disseminate information to support decision making, coordination, control, analysis, and visualization in an organization. Major Types of Information System  Enterprise Computing Systems  Transaction Processing Systems  Business Support Systems  Knowledge Management Systems  User Productivity Systems Major Types of Information System  Enterprise Computing Systems  Refers to information systems that support company-wide data management requirements. Ex: airline reservation, credit card billing  Enterprise Resource Planning (ERP) systems provide cost-effective data access for users and managers throughout the company. Major Types of Information System  Transaction Processing Systems (TPS)  Transaction Processing (TP) systems and Online Transaction Processing (OLTP) systems are called operational systems because they process data generated by day-to-day business operations. Ex: customer billing, accounts receivable, warranty claim processing. Major Types of Information System  Business Support Systems  Provide job-related information support to users at all levels of a company  Management Information System (MIS) Major Types of Information System  Knowledge Management Systems  Sometimes called expert systems because they simulate human reasoning by combining a knowledgebase and inference rules that determine how the knowledge is applied. Major Types of Information System  Knowledge Management Systems  A knowledge base consisting of a large database allows users of find information by clicking menus, typing keywords, or entering text questions in normal English phrases. Major Types of Information System  Knowledge Management Systems  Inference rules are logical rules that identify data patterns and relationships.  Fuzzy logic allows logical inferences to be drawn from imprecise relationships. Major Types of Information System  User Productivity Systems  Provide employees at all organizational levels with a wide array of tools that can improve quality of job performance Ex: LAN, WAN, email, video conference Information System Users Information System Users Information System Users Organizational Structure Top Management Top managers develop long-range plans, called strategic plans that define the company’s overall mission and goals. Information System Users Organizational Structure Middle Management Middle managers focus their goals on a shorter time frame, usually ranging from one month to one year. They develop plans to achieve business objectives in a process called tactical planning. Information System Users Organizational Structure Lower Management Supervisors and team leaders oversee operational employees and carry out day-to-day operational plans. Information System Users Organizational Structure Operational Employees Operational employees primarily use TP systems to enter and receive data they need to perform their jobs. A trend, called empowerment, gives employees more responsibility and accountability. SYSTEM ANALYSIS AND DESIGN  Module 1 Subtopic 2 - The System Analyst Introduction to System Analysis and Design Information Technology Department The information technology (IT) department develops and maintains a company’s information systems The IT group provides technical support Information Technology Department Application Development – Team may include users, managers and IT Staff members Systems Support and Security – Deployment team User Support – Help desk or information center (IC) Information Technology Department Database Administration – Database design, management, security, backup, and user access Network Administration – Includes hardware and software maintenance, support, and security Web Support – Webmasters Information Technology Department Quality Assurance (QA) – Reviews and tests all applications and systems changes to verify specifications and software quality standards – Is a separate unit that reports directly to IT management. System Analyst Position A systems analyst investigates, analyzes, designs, develops, installs, evaluates, and maintains a company’s information systems On large projects, the analyst works as a member of an IT department team Smaller companies often use consultants to perform the work. The System Analyst Position A systems analyst investigates, analyzes, designs, develops, installs, evaluates, and maintains a company’s information systems On large projects, the analyst works as a member of an IT department team Smaller companies often use consultants to perform the work The System Analyst Approach to Problem Solving Research and understand the problem Verify the benefits of solving the problem outweigh the cost Define the requirements of solving the problem Develop a set of possible solutions Decide which solution is best and make a recommendation Define the details of the chosen solution Monitor to make sure that you obtain the desired result The Systems Analyst Position Responsibilities Translate business requirements into practical IT projects to meet needs Required Skills and Background Solid communication skills and analytic ability Business knowledge and technique The system analyst needs to know the following: What business function does the organization perform? How are organizations structured? How are organizations managed? What type of work goes on in organization? People knowledge and Skills It is critical that the analyst understand how people Think Learn React to change Communicate Work Integrity and Ethics System analyst are expected to uphold the highest ethical standards when it comes to private proprietary information they might encounter on the job Typical Job Titles Programmer analyst Business system analyst System liaison System Consultant System Support Analyst System Designer Software Engineer System Architect Web Master Web Developer SYSTEM ANALYSIS AND DESIGN  Module 2 Subtopic 1 – Business Case System Planning  Chapter Objectives Explain the concept of a business case and how a business case affects an IT project Describe the strategic planning process and why it is important to the IT team Explain the purpose of a mission statement  Chapter Objectives Describe the SDLC, and explain how it serves as a framework for systems development and business modeling Describe risks and risk management features List the reasons for information systems projects and the factors that affect such projects  Chapter Objectives Explain the initial review of systems requests and the role of the systems review committee Define operational feasibility, technical feasibility, economic feasibility, and schedule feasibility Describe the steps in a preliminary investigation and the end product of an investigation Introduction The term business case refers to the reasons, or justification, for a proposal Systems development typically starts with a systems request, followed by a preliminary investigation, which includes a feasibility study  Strategic Planning – A Framework for IT Systems Development Strategic planning is the process of identifying long-term organizational goals, strategies, and resources Strategic Planning Overview – SWOT analysis Strategic Planning – A Framework for IT Systems Development From Strategic Plans to Business Results – Mission statement – Stakeholders – Goals – Objectives Strategic Planning – A Framework for IT Systems Development A Business Example – Critical success factors – Critical business issues – Case for action Strategic Planning – A Framework for IT Systems Development The Role of the IT Department in Project Evaluation – Management leadership and information technology are linked closely, and remarkable changes have occurred in both areas – Today, systems development is much more team oriented – Although team-oriented development is the norm, some companies see the role of the IT department as a gatekeeper Strategic Planning – A Framework for IT Systems Development The Future – If you could look into the future, here is what you might see: New industries, products, and services emerging from amazing advances in information technology, customers who expect world-class IT support, a surge in Internet-based commerce, and a global business environment that is dynamic and incredibly challenging What Is a Business Case? Should be comprehensive, yet easy to understand Should describe the project clearly, provide the justification to proceed, and estimate the project’s financial impact Information Systems Projects Main Reasons for Systems Projects – Systems request – Improved service – Support for new products and services – Better performance – More information Information Systems Projects Main Reasons for Systems Projects – Stronger controls Encryption and biometric devices – Reduced cost Factors that Affect Systems Projects – Internal and external factors affect every business decision that a company makes, and IT systems projects are no exception Information Systems Projects Internal Factors – Strategic plan – Top managers – User requests – Information technology department – Existing systems and data  Information Systems Projects External Factors – Technology Electronic Product Code (EPC) is a universal identifier that aims to render a unique identity to every possible physical object of the world. – Suppliers Just-in-time (JIT) Information Systems Projects External Factors – Customers Customer Relationship Management (CRM) Electronic proof of delivery (EPOD) – Competitors – The economy – Government Information Systems Projects Project Management Tools – All IT projects, large and small, must be managed and controlled – Project management begins with a systems request, and continues until the project is completed or terminated Risk Management – Every IT project involves risks that system analysts and IT project managers must address Evaluation of Systems Requests Systems review committee Computer resources committee Systems Requests Forms Evaluation of Systems Requests Systems Review Committees – Most large companies use a systems review committee to evaluate systems requests – Many smaller companies rely on one person to evaluate system requests instead of a committee – The goal is to evaluate the requests and set priorities SYSTEM ANALYSIS AND DESIGN  Module 2 Subtopic 2 – SDLC System Planning Planning and Modeling a Systems Development Project The SDLC (Software Development Life Cycle) Waterfall Model Waterfall model is the pioneer of the SDLC processes. It was the first model which was widely used in the software industry. It is divided into phases and output of one phase becomes the input of the next phase. It is mandatory for a phase to be completed before the next phase starts. In short, there is no overlapping in the Waterfall model Planning and Modeling a Systems Development Project The SDLC Waterfall Model Disadvantage in the built-in structure of the SDLC, because the waterfall model does not emphasize interactivity among the phases This criticism can be valid if the SDLC phases are followed too rigidly However, adjacent phases usually interact Planning and Modeling a Systems Development Project The SDLC Waterfall Model Usually includes five steps Systems planning Systems analysis Systems design Systems implementation Systems operation, support, and security Planning and Modeling a Systems Development Project Systems planning Systems request Purpose of this phase is to perform a preliminary investigation whose key part is a feasibility study Systems Analysis First step is requirements modeling End product is the System requirements document Planning and Modeling a Systems Development Project Systems Design Identify all outputs, inputs, and processes End product is system design specification Systems Implementation New system is constructed Users, managers, IT staff trained to operate and support the system System evaluation performed Planning and Modeling a Systems Development Project Systems Operation, Support, and Security A well-designed system must be secure, reliable, maintainable, and scalable After several years of operation, systems need extensive changes SDLC ends with system replacement Planning and Modeling a Systems Development Project Adaptive Methods and Models Attempt to develop a system incrementally, by building a series of prototypes and constantly adjusting them to user requirements Extreme Programming (XP) Analysts should recognize that these approaches have advantages and disadvantages Planning and Modeling a Systems Development Project Joint Application Development and Rapid Application Development Methods and Models Joint application development (JAD) Rapid application development (RAD) Other Development Methods and Models Rational Unified Process (RUP®) Microsoft Solutions Framework (MSF) Planning and Modeling a Systems Development Project The Importance of Project Management Regardless of the development strategy, people, tasks, timetables, and expenses must be managed effectively Complex projects can involve dozens of people, hundreds of tasks, and many thousands of dollars Systems Development Guidelines Stick to a plan Involve the users throughout the development process Listening is very important Use project management tools to identify tasks and milestones Remain flexible Develop accurate cost and benefit information SYSTEM ANALYSIS AND DESIGN  Module 2 Subtopic 3 – Feasibility and Preliminary Investigation System Planning OVERVIEW OF FEASIBILITY A systems request must pass several tests, called a feasibility study, to see whether it is worthwhile to proceed further OVERVIEW OF FEASIBILITY Technical Feasibility – Technical feasibility refers to technical resources needed to develop, purchase, install, or operate the system Economic Feasibility – Total cost of ownership (TCO) – Tangible benefits – Intangible benefits Schedule Feasibility EVALUATING OF FEASIBILITY The first step in evaluating feasibility is to identify and weed out systems requests that are not feasible Even if the request is feasible, it might not be necessary Feasibility analysis is an ongoing task that must be performed throughout the systems development process SETTING PRIORITIES Factors that Affect Priority – Will the proposed system reduce costs? Where? When? How? How much? – Will the system increase revenue for the company? Where? When? How? How much? SETTING PRIORITIES Factors that Affect Priority – Will the systems project result in more information or produce better results? How? Are the results measurable? – Will the system serve customers better? – Will the system serve the organization better? SETTING PRIORITIES Factors that Affect Priority – Can the project be implemented in a reasonable time period? How long will the results last? – Are the necessary financial, human, and technical resources available? – Whenever possible, the analyst should evaluate a proposed project based on tangible costs and benefits that represent actual (or approximate) dollar values SETTING PRIORITIES Discretionary and Nondiscretionary Projects – Projects where management has a choice in implementing them are called discretionary projects – Projects where no choice exists are called nondiscretionary projects PRELIMINARY INVESTIGATION OVERVIEW Preliminary investigation Interaction with Managers and Users PRELIMINARY INVESTIGATION OVERVIEW Planning the Preliminary Investigation – During a preliminary investigation, a systems analyst typically follows a series of steps – The exact procedure depends on the nature of the request, the size of the project, and the degree of urgency PRELIMINARY INVESTIGATION OVERVIEW Step 1: Understand the Problem or Opportunity – A popular technique for investigating causes and effects is called a fishbone diagram, or Ishikawa diagram – Pareto chart PRELIMINARY INVESTIGATION OVERVIEW Step 2: Define the Project Scope and Constraints – Project scope – Project creep – Constraint PRELIMINARY INVESTIGATION OVERVIEW Step 2: Define the Project Scope and Constraints – Present versus future – Internal versus external – Mandatory versus desirable – Regardless of the type, all constraints should be identified as early as possible to avoid future problems and surprises PRELIMINARY INVESTIGATION OVERVIEW Step 3: Perform Fact-Finding – Fact-finding involves various techniques – Fact-finding might consume several hours, days, or weeks – Analyze Organization Charts PRELIMINARY INVESTIGATION OVERVIEW Step 3: Perform Fact-Finding – Conduct interviews Determine the people to interview Establish objectives for the interview Develop interview questions Prepare for the interview Conduct the interview Document the interview Evaluate the interview PRELIMINARY INVESTIGATION OVERVIEW Step 3: Perform Fact-Finding – Review documentation – Observe operations – Conduct a user survey Step 4: Evaluate Feasibility – Evaluate the project’s operational, technical, economic, and schedule feasibility PRELIMINARY INVESTIGATION OVERVIEW Step 5: Estimate Project Development Time and Cost – What information must you obtain, and how will you gather and analyze the information? – What sources of information will you use, and what difficulties will you encounter in obtaining information? PRELIMINARY INVESTIGATION OVERVIEW Step 5: Estimate Project Development Time and Cost – Will you conduct interviews? How many people will you interview, and how much time will you need to meet with the people and summarize their responses? – Will you conduct a survey? Who will be involved? How much time will it take people to complete it? How much time will it take to prepare it and tabulate the results? PRELIMINARY INVESTIGATION OVERVIEW Step 5: Estimate Project Development Time and Cost – How much will it cost to analyze the information gathered and to prepare a report with findings and recommendations? – You should provide an estimate for the overall project, so managers can understand the full cost impact and timetable PRELIMINARY INVESTIGATION OVERVIEW Step 6: Present Results and Recommendations to Management – The final task in the preliminary investigation is to prepare a report to management – The format of the preliminary investigation report varies from one company to another PRELIMINARY INVESTIGATION OVERVIEW Step 6: Present Results and Recommendations to Management Introduction Systems request summary Findings Recommendations Project Roles Time & cost estimates Expected benefits Appendix