MGS351- Test 3 Chapter 6: Systems Development Organizational Change: 4 degrees**understand relationships with risk and return*1. Automation- speeding up performance, simplest form, have existing system and then automate (keep the same)2. Rationalization of procedures- streamlining op operating procedure, use technology to influence change for profit, takes existing procedure and make it better 3. Business process reengineering (BPR)- radical design of business process, build whole new process, think outside the box, much greater degree of change, use technologya. Ex) ordering process for bookstore- keep physical store but also make online 4. Paradigm shift- radical re-conceptualization- greatest change a. Ex) local bookstore- with technology can shut down physical store andonly sell books online Why Systems Fail: 20% of systems succeed, 80% fail- Unclear or missing requirements- Skipping SLDC phases (take short cuts in designing)- Failure to manage project scope, the details (scope creep and feature creep)- Failure to manage project plan (larger budget issues)- Changing technology- Inadequate testing and/or poor implementation- Not planning for the future When building an information system you are influencing organizational change andneed to understand risk ex) HUB, shifted from old to new Information Systems Planning- needs to support organization mission - Organization Mission (everyone needs to be aligned)- Business Assessment (IS planning process) - Organization Strategic Plan ex) UB 2020 - Current information technology architecture- IS strategic plan, works with organization strategic plan ex) voice of IP upgrade for UB 2020 - New information Technology Architecture- need architecture in place to support strategic plan ex) UB voice over IP system, but network was not up topar, so upgraded equipment on campus - IS Operational Plan- IS development Projects (voice over IP) - Look at chart in slides Systems Development Life Cycle (SDLC)- traditional approach- SDLC- the development method used by most organizations today for large, complex systems - Waterfall approach- a sequence of steps in the SDLC with cycles returned to previous stops- Systems Analysts- IS professionals who specialize in analyzing and designing information systems (from business perspective, no technology)- Programmers- IS professionals who modify existing computer programs or write new computer programs to satisfy user requirements, build systems - Technical Specialists- experts in a certain type of technology, such as databases or telecommunications SDLC- 7 STEPS** 1. Plan- Define the system to be developed, set the project scope, develop the project plan including tasks, resources, and timeframes a. Project Scope Document- a written definition of the project scope and is usually no longer than a paragraph (outlines what is and what isn’t, brief description)b. Project Plan- defines the what, when, and the who questions of systemdevelopment including all activities to be performed, the individuals or resources who perform the activities, and the time required to complete each activity (outlines details)c. Project Milestones- represents key data for which you need a certain group of activities performedd. Project Manager- an individual who is an expert in project planning and management, defines and develops the project plan and tracks theplan to ensure all key project milestones are completed on time (understand how to stay on budget, on time, on target) e. Feasibility study determines the probability of success of proposed systems development project (does this make sense to do?) and assesses the projects:i. Technical Feasibility- do we have technical infrastructure or expertise? Ex) wireless ii. Economic Feasibility- Are we going to make $? Intangibles-> customer satisfaction iii. Behavioral Feasibility- ex) paper system- changes to computerized system to track deliveries and generate invoices, there are so many benefits that had to be given up, company was very nervous about having to give up “papers” ex) possibility of resistance, people don’t like change and like consistency2. Analysis- looking at requirements of a system through business perspective (What are the problems? What does system need to do?)a. Involves the examination of the business problem the organization plans to solve with information systems b. Requires end users and IT specialists to work together to gather, understand, and document the business requirements or the proposed systemc. Joint application development (JAD) is often used to accomplish this (get everyone together and facilitate process, come to consensus)d. Requirements definition document (documentation of JAD)- prioritizes the business requirements and places them in a formalcomprehensive document, requires a “sign off” (approval) by the knowledge workerse. Also may include:i. Strengths and weaknesses of the existing systemii. Functions that the new systems must have to solve the business problemiii. User information requirements for the new systems 3. Designa. Develop a technical blueprint of how the proposed system will work and define the technical architectureb. Technical design- system outputs, inputs and user interfaces, hardware, software, databases, telecommunications, personnel, and procedures (how these computers are integrated)4. Development- take implications and build a. The translation of the design specifications into the computer code which becomes the actual systemb. Also, build the technical architecture, databases and programs 5. Test- need to figure out how much testing is enougha. Checks to see if the computer code will produce the expected and desired results under certain conditionsb. Syntax Errors- misspelled word or a misplaced comma (good errors, because know when are happening, something will pop up and can fix them)c. Logic errors- permit the program to run, but result in incorrect output (dangerous, exist in calculation of code, just produce bad outputs)i. Ex) 1st gulf war- Iraq had missiles and US had missile defense system, the software was tested but only for a day at a time andeventually error became worse (rounding error) d. Unit testing (test modules or units ex) delivery system- pricing), system testing (does everything work together?), acceptance testing (show to end user), test plan (shows each step, what expected results, and what you got)e. Involve end users in testing6. Implementa. The process of converting from