Chapter 12 Developing BusinessIT Solutions Chapter 13 Building

Chapter 12 Developing Business/IT Solutions & Chapter 13 Building Information Systems Chapter 12 - O’Brien Chapter 13 - Laudon

Systems Analysis and Design (O’Brien) n Systems analysis and design is the overall process by which information systems are designed and implemented. It includes: ¨ Identification of business problems ¨ Proposed solution in form of information systems ¨ Design and implementation of that solution Chapter 12 Developing Business/IT Solutions 2

Systems Development Lifecycle (SDLC)(O’Brien) Chapter 12 Developing Business/IT Solutions 3

Systems Investigation (O’Brien) n Systems Investigation ¨ The first step in the systems development process ¨ May involve consideration of proposals generated by a business/IT planning process ¨ Also includes the preliminary feasibility study of proposed information system solutions Chapter 12 Developing Business/IT Solutions 4

Systems Investigation (O’Brien) n n Feasibility Studies: a preliminary study to determine the ¨ Information needs of prospective users ¨ Resource requirements ¨ Costs ¨ Benefits ¨ Feasibility In some cases, a feasibility study is unnecessary Chapter 12 Developing Business/IT Solutions 5

Systems Investigation (O’Brien) n n Operational Feasibility: How well the proposed system will ¨ Support the business priorities of the organization ¨ Solve the identified problem ¨ Fit with the existing organizational structure Economic/Financial Feasibility: An assessment of ¨ Cost savings ¨ Increased revenue ¨ Decreased investment requirements ¨ Increased profits ¨ Cost/benefit analysis 6

Systems Investigation (O’Brien) n n n Technical feasibility: Determine the following can meet the needs of a proposed system and can be acquired or developed in the required time ¨ Hardware ¨ Software ¨ Network Human factors feasibility: Assess the acceptance level of ¨ Employees ¨ Customers ¨ Suppliers ¨ Management support Determine the right people for the various new or revised roles Chapter 12 Developing Business/IT Solutions 7

Systems Investigation (O’Brien) n Legal/political feasibility: Assess ¨ Possible patent or copyright violations ¨ Software licensing for developer side only ¨ Governmental restrictions ¨ Changes to existing reporting structure Chapter 12 Developing Business/IT Solutions 8

Systems Analysis (O’Brien) n n An in-depth study of end user information needs ¨ It produces the functional requirements used as the basis for the design of an IS It typically involves a detailed study of the ¨ Information needs of a company and end users ¨ Activities, resources, and products of one or more of the information systems currently being used ¨ Information system capabilities required to meet the information needs of business stakeholders Chapter 12 Developing Business/IT Solutions 9

Systems Analysis (O’Brien) n n Organizational analysis: Study of the organization, including… ¨ Management structure ¨ People ¨ Business activities ¨ Environmental systems Analysis of the present system: Before designing a new system, it is important to study the system to be improved or replaced. It includes ¨ Hardware and software, network, and people resources used to convert data resources into information products ¨ System activities of input, processing, output, storage, and control 10

Systems Analysis (O’Brien) n n Logical analysis: A logical model is a blueprint of the current system ¨ It displays what the current system does, without regard to how it does it ¨ It allows an analyst to understand the processes, functions, and data associated with a system regardless hardware and software Functional requirements: This step of systems analysis is one of the most difficult ¨ Determine what type of information each business activity requires ¨ Determine the information processing capabilities required for each system activity (input, processing, output, storage, and control) ¨ The goal is to identify what should be done, 11 not how to do it

Systems Analysis (O’Brien) n Examples of functional requirements: ¨ User Interface: automatic entry of product data and easy-to-use data entry screens for Web customers ¨ Processing: fast, automatic calculation of sales totals and shipping costs ¨ Storage: fast retrieval and update of data from product, pricing, and customer databases ¨ Control: signals for data entry errors and quick e-mail confirmation for customers Chapter 12 Developing Business/IT Solutions 12

Systems Design (O’Brien) n Systems design focuses on three areas Chapter 12 Developing Business/IT Solutions 13

Systems Design (O’Brien) n n User interface design: Focuses on supporting the interactions between end users and their computerbased applications ¨ Designers concentrate on the design of attractive and efficient forms of user input and output ¨ Frequently a prototyping process ¨ Produces detailed design specifications for information products, such as display screens System Design specifications: Formalizing the design of ¨ User interface methods and products ¨ Database structures ¨ Processing procedures ¨ Control procedures 14

Systems Design System Design Specifications (Laudon) OUTPUT Medium Content Timing INPUT Origins Flow Data entry USER INTERFACE Simplicity Efficiency Logic Feedback Errors DATABASE DESIGN Logical data model Volume and speed requirements File organization and design Record specifications PROCESSING Computations Program modules Required reports Timing of outputs MANUAL PROCEDURES What activities Who performs them When How Where CONTROLS Input controls (characters, limit, reasonableness) Processing controls (consistency, record counts) Output controls (totals, samples of output) Procedural controls (passwords, special forms) SECURITY Access controls Catastrophe plans Audit trails DOCUMENTATION Operations documentation Systems documents User documentation CONVERSION Transfer files Initiate new procedures Select testing method Cut over to new system TRAINING Select training techniques Develop training modules Identify training facilities ORGANIZATIONAL CHANGES Task redesign Job redesign Process design Organization structure design Reporting relationships 15

Systems Design (O’Brien) Examples of System Specifications (O’Brien) User interface specifications Use personalized screens that welcome repeat Web customers and that make product recommendations Database specifications Develop databases that use object/relational database management software to organize access to all customer and inventory data and to multimedia product information Software specifications Acquire an e-commerce software engine to process all e-commerce transactions with fast responses, i. e. , retrieve necessary product data and compute all sales amounts in less than one second Hardware and network specifications Install redundant networked Web servers and sufficient high-bandwidth telecommunications lines to host the company e-commerce website Personnel specifications Hire an e-commerce manager and specialists and a webmaster and Web designer to plan, develop, and manage e-commerce operations 16

Implementing New Systems (O’Brien) n The systems implementation stage involves ¨ Hardware and software acquisition ¨ Software development (programming) ¨ Testing of programs and procedures ¨ Conversion of data resources ¨ System Conversion alternatives ¨ Education/training of end users and specialists who will operate the new system Chapter 12 Developing Business/IT Solutions 17

Evaluating Hardware, Software, Services (O’Brien) n n n Establish minimum physical and performance characteristics for all hardware and software ¨ Formalize these requirements in an RFP/RFQ Send RFP/RFQ to appropriate vendors Evaluate bids when received ¨ All claims must be demonstrated ¨ Obtain recommendations from other users ¨ Search independent sources (blogs or information services) for evaluations ¨ Benchmark test programs and test data for hardware and software 18

Hardware Evaluation Factors (O’Brien) 19

Software Evaluation Factors (O’Brien) 20

Evaluating IS Services (O’Brien) n Examples ¨ Developing a company website ¨ Installation or conversion of hardware/soft ware ¨ Employee training ¨ Hardware maintenance ¨ System design and/or integration ¨ Contract programming ¨ Consulting 21 services

Other Implementation Activities Programming (Laudon) System specifications from design stage are translated into software program code using Java, C++, C# etc. Testing (Laudon) Ensures system produces right results Unit testing: Tests each module in system separately System testing: Test functioning of system as a whole such as load testing, performance testing in peak hour etc. Acceptance testing: Makes sure system is ready to be used in production setting. Systems tests are evaluated by users and reviewed by management 22

Other Implementation Activities Conversion SYSTEM CONVERSION (Laudon) Process of changing from old system to new system Four main strategies § Parallel strategy: old and new systems are run at the same time. It is the safest conversion strategy because in the event of error with the new system, the old system can be used as backup. § Direct cutover: replaces the old system entirely. It is a risky strategy. § Pilot study: new system is introduced at some part (branches, regional offices) of the organization. § Phased approach: introduces new systems in stages. 23

Other Implementation Activities DATA CONVERSION (O’Brien) n Data conversion includes ¨ Converting data elements from the old database to the new database ¨ Correcting data errors ¨ Filtering out unwanted data ¨ Consolidating data from several databases ¨ Organizing data into new data subsets n Improperly organized and formatted data is a major cause of implementation failures TRAINING and DOCUMENTATION (Laudon) n Requires end-user training to use the new system n Finalization of detailed documentation showing how system works from technical and end-user standpoint 24

Production and maintenance (Laudon) § After the new system is installed and conversion is complete, the system is said to be in production. In the production stage system is reviewed to determine if revisions needed. This may include postimplementation audit document. Maintenance Changes in hardware, software, documentation, or procedures to a production system to correct errors, meet new requirements, or improve processing efficiency ¨ 20% of time for debugging, emergency work ¨ 20% changes to hardware, software, data, reporting ¨ 60% of work: User enhancements, improving documentation, recoding for greater processing 25 efficiency

Prototyping (Laudon) n The process of developing a prototype can be broken down into four steps. Because a prototype can be developed quickly and inexpensively, systems builders can go through several iterations, repeating steps 3 and 4, to refine and enhance the prototype before arriving at the final operational one. 26

Outsourcing (Laudon) § § Several types Cloud computing and Saa. S providers ¨ Subscribing companies use software and computer hardware provided by vendors External vendors ¨ Hired to design, create software ¨ Domestic outsourcing § Driven by firms need for additional skills, resources, assets ¨ Offshore outsourcing § Driven by cost-savings Chapter 12 Developing Business/IT Solutions 27

Rapid application development (RAD) (Laudon) § § Process of creating workable systems in a very short period of time Utilizes techniques such as: Visual basic programming and other tools for building graphical user interfaces Iterative prototyping of key system elements Automation of program code generation Close teamwork among end users and information systems specialists Chapter 12 Developing Business/IT Solutions 28

Mobile application development (Laudon) n Mobile application § A mobile Web site n A version of regular Web site that is scaled down in content and navigation for easy access and search on a small screen n Responsive Web design for multiple Web sites to be used on different devices e. g. PC, smartphones, tablets § A native app n Standalone application designed to run on a specific platform and device. It is installed on a mobile device. It is able to take advantage of mobile features n Saving resources- bandwidth, screen space, memory, processing, data entry, and user gestures are top priorities while developing mobile Web or app 29