🎧 New: AI-Generated Podcasts Turn your study notes into engaging audio conversations. Learn more

211-Module01 (1).pdf

Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...

Full Transcript

IT 211 RAM Module 1: Introduction COMPUTER-BASED INFORMATION SYSTEMS SYSTEM DEVELOPMENT LIFE CYCE Learning Outcomes Describe computer-based information systems and its components. Differentiate the different phases of the SDLC. Describe role of and expectations from th...

IT 211 RAM Module 1: Introduction COMPUTER-BASED INFORMATION SYSTEMS SYSTEM DEVELOPMENT LIFE CYCE Learning Outcomes Describe computer-based information systems and its components. Differentiate the different phases of the SDLC. Describe role of and expectations from the analyst Computer-based IS information system (IS) o set of interrelated components that collect data, manipulate, store and disseminate information (notice the Input-Process-Output concept) and through a feedback mechanism, improvements can be introduced (Stair, Chesney, Reynolds, 2018) Computer-based IS computer-based information system (CBIS) o people, procedures/processes, data, tasks/roles and technology (hardware, software, communication tech) o embedded in products such as appliances, cars, IOT devices and mobile gadgets o types transaction processing systems office automation systems management support systems In the technology field, the terms IS or system are referred to synonymously with CBIS System Development Life Cycle SDLC Model (Reprinted from Systems Analysis and Design (11th ed., p.20) by S. Tilley and H. Rosenblatt, 2016, Boston, MA: Cengage Learning. 2017 by Cengage Learning) System Development Life Cycle Planning o process of fundamental process of understanding why an information system should be built (or improved) and determining how the project team will go about building it: Project initiation o driven by a business need improve one or more of: economics, efficiency, service to customers, suppliers, partners or employees, performance, information, control or security entail resolving problems in and/or introducing changes to an information system or a business process. o initiative may come from top management or some department in the organization (may be the IT department) System Development Life Cycle Planning Project initiation o system request is the summary of the business need and how addressing it creates business value feasibility analysis is conducted in order to determine whether the project will move forward o IT firm may be hired to provide the solution you may work in-house or be part of an organization that provides IT services / products System Development Life Cycle Planning Project Management o occurs after request approval o project manager creates a work plan, sets up the project team, oversees the implementation of the project and monitors project progress o project types new CBIS is developed (transition from manual to CBIS) enhance an existing CBIS Project management is “the application of knowledge, skills, tools and techniques to project activities to meet project requirements” (PMBOK® Guide, Fourth Edition, 2008, p. 6) System Development Life Cycle Analysis o aims to provide the project team with a clear understanding of the project existing business process/es and system/s in place are investigated problem areas and/or opportunities for improvement are identified the proposed system is conceptualized. o requirement elicitation and analysis data gathering and modeling System Development Life Cycle Analysis o requirement elicitation and analysis data gathering modeling of o current system (as-is system) o proposed system (to-be system) artifacts / by-products / output o background information, understanding of the current system, models, prototypes, requirements definition o combined into a requirements document or specification requirements become the basis for design System Development Life Cycle Design o specifies the components of the proposed system and how such components will operate and interact with each other decide on how the system will be developed establish the system architecture (hardware and software components) user interface design data design and file specifications (data modeling) program design (class diagrams and templates, decision tress, flowcharts, etc.) System Development Life Cycle Implementation o build (or purchase); implement the design o application development coding and testing o utilization of development tools and technologies, test tools, IDE’s, etc. o integration of components o deployment prepare the system for release package the software prepare documentation, trainings, support plan System Development Life Cycle As the system is used o user support training help desks o maintenance tasks o check if the system needs to be enhanced – leads to a new project put into the SDLC decommissioned – system retirement Application Development Life Cycle Focuses on the process of developing software applications. Tailored specifically for software application Deals with software integration & UI design Development / Project Team People involved include: o Project Manager o Users: People who will regularly inter- act with the system o Systems Analyst: professional who specializes in analyzing and designing the system. o Programmer: responsible for modifying or developing programs to satisfy user requirements o Test Engineers / QA specialists o UI / UX designers o stakeholders: those who ultimately will be affected (for better or worse) by the systems development project. Systems Analyst Responsibilities o helps translate business requirements into IT projects o performs the entire spectrum of requirements analysis activities o selects hardware and software packages, contributes to the design of systems, works closely with programmers and trains users o participates in project planning o conducts meetings, delivers presentations, writes memos, reports, and documentation role may be specific or overlap with other team roles Systems Analyst Skill set o analytical skills must be a problem solver Systems thinking is the ability to break down a system into parts, examine these components and their interrelationships analysts must have the ability to conceptualize and evaluate alternative solutions o technical skills reasonable programming skills highly skilled in tools and techniques for analysis and design awareness of trends in technology Systems Analyst Skill set o technical skills analyst can be in the shoes of both the nontechnical people involved in the system and the development team o interpersonal skills communication o ask questions, listen, observe, explain, present, persuade, compromise, negotiate o business knowledge and managerial skills References o Dennis, A., Wixom, B., & Tegarden, D. (2015), System Analysis & Design: An Object-Oriented Approach with UML (5th ed.), Wiley o Jirava, P. (2004), System Development Life Cycle, Retrieved June 9, 2020 from www.researchgate.net, https://www.researchgate.net/publication/44982277 o R. Stair, and G. Reynolds ( 2016), Information Systems (8th ed.), Cengage Learning o Tilley, S. & Rosenblatt, H. (2017), Systems Analysis and Design (11th ed.), Cengage Learning

Use Quizgecko on...
Browser
Browser