SUT 4.1 Stakeholders and Drivers of Information Systems PDF

SUT 4.1 Context of Systems Analysis and Design/ Information Systems Development Methodologies April 2024 Class Test 1 Feedback Maximum: 19 Average: 9 More than 10: 146 Absent from test: 9 Mark query deadline: By 10:00 24 April 2024 Learning Objec...

SUT 4.1 Context of Systems Analysis and Design/ Information Systems Development Methodologies April 2024 Class Test 1 Feedback Maximum: 19 Average: 9 More than 10: 146 Absent from test: 9 Mark query deadline: By 10:00 24 April 2024 Learning Objectives Discuss how information systems (IS) are used to solve business problems Identify IS stakeholders Identify and define the role & skills of the system analyst Describe current business drivers of IS development Distinguish between Front/back-office IS Explain the common IS development methodologies Module Resource Systems analysis and design methods by Whitten, Bentley & Dittman (7th Edition) Systems Analysis and Design Methods (PDF. 86 mb) Stakeholders and Drivers of Information Systems Source: Chapter 1: Whitten, Bentley & Dittman (7th Edition)  Problem-Solving What are the steps taken to solve problems? – First, you have to understand the problem – After understanding, then make a plan – Carry out the plan – Look back at the solution. How could it be better?  Problem-Solving and Developing systems Where does IS come from? – People build it! The System Analyst forms part of a team by following typical problem-solving steps: Identify Identify Design Implement Analyse Alternate chosen Evaluate problem problem requirements solutions solution the result solution Who are involved? System System Users System designers owners builders The system analyst facilitates and directs the overall process  Where do development projects come from? Problems: undesirable situations that prevent organization from fully achieving its purpose Opportunities: chances to improve the organization in the absence of specific problems Directives: new requirements that are imposed by management, government, or some external influence  Information Systems Stakeholders System Owners System Analysts System Designers Information workers System Users System Builders IS/IT Vendors 10 The roles of the Systems Analyst ▪ Analyse problems & business ▪ Business analyst – system analysis: needs to determine how business study the business problem domain, systems & IT can best solve recommend improvements & specify problems & accomplish the business requirements for the improvements solution ▪ System analysts does not always Application/system analyst –system design new systems…also have to design: specification or construction of a technical, computer-based customize existing systems solution for the business requirements identified during systems analysis 11  The importance of the Systems Analyst ▪ Initiate change – new IS or improved ▪ Bridge the communication gap between IS always implies change business experts and technology experts ▪ Need to serve the needs of the clients ▪ Need to see IS from different (system owners & system users) viewpoints – facilitate the development of IS through interaction with all stakeholders ▪ Often play the role of other stakeholders 12  Business Drivers of Information Systems Globalization of the Economy Collaboration & Partnership Electronic Commerce & Knowledge Asset Management Business Continuous Improvement & Total Quality Management Security & Privacy Business Process Redesign 13  Diverse Skills of the System Analyst Knowledge of information technology – INF112 Programming expertise – INF154, 164, INF 272, INF 354 Business knowledge – Economics, accounting etc. Data analysis - Statistics Problem-solving skills – INF113 and INF171 Communication skills – Group work (most modules) Interpersonal skills – Group work Flexibility and adaptability – Brain profiles (most modules) Character and Ethics Systems analysis and design skills – INF171; INF 271; INF 370 14  The Information System as a product Multiple Information System (IS) used to support business functions Two main categories: - Front-office IS: support business functions that reach out to customers - Back-office IS: support internal business operation and interact with suppliers  ‘Front-office’ and ‘back-office’ IS Example: Introduction to Systems Development Methodologies  Software Development Methodologies There are several software development methodologies: Waterfall Agile Hybrid  Waterfall Methodology Planning A sequence of phases in Analysis which the output of each phase becomes the input Design for the next Phases Development Testing Implementation Maintenance Timeline  Agile Methodology It consists of a series of tiny projects Aims for customer satisfaction through early and continuous delivery of useful software components A project is divided into sprints or smaller “chunks,” and collaborative teams are divided to work on sprints separately. At the end of a sprint, they come together to discuss their progress and to work out issues collaboratively Testing is also carried out at the end of each sprint, rather than at the end of the project, to ensure bugs (i.e. mistakes) are fixed right away.  Hybrid Methodology Agile development is rapidly becoming the preferred method of development. Yet, the advantages of waterfalls cannot be denied Project managers face the decision to go with one or the other and tend not to be completely satisfied with either. Hence the hybrid approach Combines the best of agile and waterfall and makes them work together Combines initial upfront planning with iterative development  INITIAL VISIONING INF370 BUSINESS ANALYSIS (INF370) Conduct Current State Conduct Future State Specify Initial Identify Key Business Requirements Analysis Analysis Transformations INF171 SUT5 INF171 SUT3 INF3/4 INF171 SUT3/4 INF 271 INF 271 INF 271 PROJECT PLANNING AND IMPLEMENTATION APPROACH SELECTION Select Implementation Approach Evaluate Initial Project Feasibility INF171 SUT3 Identify Options for Project Implementation INF 271 Select External Vendors & Products INF 271 Determine Sources & Costs of Resources Create Draft Statement of Work INF 271 INF370 A Hybrid Framework INF370 INF 271 C FUNCTIONAL AND INITIAL TECHNICAL DESIGN Downloadable version available on Specify Functional Design INF171 SUT6/7/8 INF 271 INF 370 Specify Initial Technical Architecture & High-Level Design INF 271 INF 370 ClickUP FINAL PROJECT APPROVAL AND EXECUTION PLANNING Refine & Approve Business Case Plan Change Management Complete & Approve Project Charter Plan Project Execution INF 271 INF 271 INF 370 INF 370 ITERATIVE CONSTRUCTION/CONFIGURATION Refine Functional Design INF 370 Refine Technical Architecture INF 370 Design & Code/Configure System Solution INF 370 Refine Functional Design INF 370 Let’s Test Our Knowledge!  Information systems are designed to address problems, capitalize on opportunities or comply with directives The PIECES Framework is a good framework for categorizing problems, opportunities, and directives. Different stakeholders are involved in IS development The Systems Analyst plays a vital role in the IS development process. Many organizations are moving away from the waterfall methodology to a more agile approach The Hybrid methodology combines the best of agile and waterfall and makes them work together Questions….