Developing Business/it Solutions
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Developing Business/it Solutions as PDF for free.
More details
- Words: 2,164
- Pages: 52
Developing Business/IT Solutions
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 1
What is the Systems Approach? • A problem solving technique that uses a systems orientation to define problems and opportunities and develop solutions. • Analyzing a problem and formulating a solution involves the following interrelated activities: • Recognize and define a problem or opportunity using systems thinking • Develop and evaluate alternative system solutions • Select the system solution that best meets your requirements • Design the selected system solution • Implement and evaluate the success of the designed system Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 2
What is Systems Thinking? • Seeing the forest and the trees in any situation by: • Seeing interrelationships among systems rather than linear cause-and-effect chains whenever events occur • Seeing processes of change among systems rather than discrete snapshots of change, whenever changes occur • Ex: sales process of a business Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 3
Systems Thinking Example
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 4
Systems Development Lifecycle (SDLC)
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 5
Prototyping Definition: • The rapid development and testing of working models, or prototypes, of new applications in an interactive, iterative process that can be used by both IS specialists and business professionals
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 6
Prototyping Process
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 7
Systems Development Process Systems Investigation stage • Do we have business opportunities? • What are our business priorities? • How can information technologies provide information systems solutions that address our business priorities? Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 8
Feasibility Study Definition: • A preliminary study where the information needs of prospective users and the resource requirements, costs, benefits, and feasibility of a proposed project are determined
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 9
Feasibility Study • A team of business professionals and IS specialists formalize this study in a written report • It includes preliminary specifications and a development plan for a proposed business applications • If the management approves feasibility study , the development process can continue Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 10
Feasibility Categories • Organizational – how well a proposed system supports the strategic business priorities of the organization • Economic – whether expected cost savings, increased revenue, increased profits, reductions in required investment, and other types of benefits will exceed the costs of developing and operating a proposed system Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 11
Feasibility Categories • Technical – determine if reliable hardware and software capable of meeting the needs of a proposed system can be acquired or developed by the business in the required time • Operational – willingness and ability of the management, employees, customers, suppliers, and others to operate, use, and support a proposed system Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 12
Feasibility
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 13
Cost/Benefit Analysis • Tangible – costs or benefits that can be quantified • Ex: cost of h/w and s/w, employee salary • Intangible – costs or benefits that can not be quantified • Ex: loss of customer goodwill
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 14
Systems Analysis Definition: • An in-depth study of end user information needs that produces functional requirements that are used as the basis for the design of a new information system
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 15
What does Systems Analysis Study? • The information needs of a company and end users. • The activities, resources, and products of one or more of the present information systems being used. • The information system capabilities required to meet information needs of users, and those of other business stakeholders that may use the system. Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 16
Organizational Analysis • Study of the organization including: • Management Structure • People • Business Activities • Environmental Systems • Current Information Systems Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 17
Analysis of the Present System • Study the existing system • Analyze how this system uses hardware, software, network, and people resources to convert data resources into information products • Document how the information system activities of input , processing, output, storage and control are accomplished
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 18
Functional Requirements Definition: • End user information requirements that are not tied to the hardware, software, network, data, and people resources that end users presently use or might use in the new system
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 19
Functional Requirement Categories • User Interface • Processing • Storage • Control
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 20
Systems Design Definition: • Design activities that produce system specifications satisfying the functional requirements that were developed in the systems analysis process
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 21
System Design Categories
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 22
User Interface Design Definition: • Focuses on supporting the interactions between end users and their computerbased applications
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 23
Checklist for Corporate Websites • Remember the customer – successful websites are built solely for the customer, not to make company vice presidents happy • Aesthetics – successful designs combine fastloading graphics and simple color palettes for pages that are easy to read • Broadband Content – the Web’s coolest stuff can’t be accessed by most Web surfers; don’t make it the focus of a site Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 24
Checklist for Corporate Websites • Easy to navigate – make sure it’s easy to get from one part of site to another • Searchability – include a useful search engine • Incompatibilities – test site with target web browsers
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 25
Checklist for Corporate Websites • Registration forms – short registration forms are a useful way to gather customer data • Dead links – be sure to keep links updated
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 26
System Specifications Definition: • Hardware, software, network, data, and personnel specifications for a proposed system that formalize the design of an application’s user interface methods and products, database structures, and processing and control procedures
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 27
End User Development Definition: • IS professional plays a consulting role, while end user does his/her own application development
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 28
End User Development
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 29
Encouraging End User Web Development • Look for tools that make sense • Spur creativity • Set some limits • Give managers responsibility • Make users comfortable Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 30
Systems Implementation • Hardware and software acquisition • Software development • Testing of programs and procedures • Conversion of data resources • Conversion alternatives • Education and training of end users and specialists who will operate a new system Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 31
Project Management Definition: • IT and business unit managers enforce a project plan which includes job responsibilities, time lines for major stages of development, and financial budgets
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 32
Implementation Process
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 33
Hardware Evaluation Factors • Performance
• Ergonomics
• Cost
• Connectivity
• Reliability
• Scalability
• Compatibility
• Software
• Technology
• Support
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 34
Software Evaluation Factors • Quality
• Connectivity
• Efficiency
• Maintenance
• Flexibility
• Documentation
• Security
• Hardware
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 35
IS Services • Developing a company website
• System design
• Installation
• Contract programming
• Conversion • Employee training
• Consulting services • System integration
• Hardware maintenance Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 36
IS Services Evaluation Factors • Performance
• Backup
• Systems development
• Accessibility • Business Position
• Maintenance • Hardware • Conversion • Software • Training Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 37
System Testing • Testing and debugging software • Testing website performance • Testing new hardware • Review of prototypes of displays, reports and other output Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 38
Data Conversion • Converting data elements affected by new application • Correcting incorrect data • Filtering out unwanted data • Consolidating data from several databases • Organizing data into new data subsets Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 39
Importance of Data Conversion • Improperly organized and formatted data is frequently reported to be one of the major causes of failures in implementing new systems.
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 40
Importance of Documentation • Documentation serves as a method of communication among the people responsible for developing, implementing, and maintaining a computer-based system. • Documentation is extremely important in diagnosing errors and making changes, especially if the end users or systems analysts who developed a system are no longer with the organization. Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 41
Training • Data entry • All aspects of the proper use of a new system • Educate managers and end users in how the new technology impacts the company’s business operations and management Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 42
Conversion Methods • Parallel – both old and new systems are operating until the project development team and end user management agree to switch completely to the new system • Plunge – no overlap of old and new system
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 43
Conversion Methods • Phased – only parts of a new application or only a few departments at time are converted • Pilot – One department serves as a test site
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 44
Conversion Methods
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 45
Systems Maintenance Definition: • Monitoring, evaluating, and modifying of operational business systems to make desirable or necessary improvements
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 46
Systems Maintenance
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 47
Learning Curve Definition: • Personnel who operate and use the system will make mistakes simply because they are not familiar with it; though such errors usually diminish as experience is gained with a new system
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 48
Postimplementation Review Definition: • Periodic review or audit of a system to ensure that it is operating properly and meeting its objectives
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 49
Summary • Business end users and IS specialists may use a systems approach to help them develop information system solutions to meet business opportunities. • Prototyping includes the use of prototyping tools and methodologies, which promote an iterative, interactive process that develops prototypes of user interfaces and other information system components. Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 50
Summary • The application development capabilities built into many end user software packages have made it easier for end users to develop their own business applications. • End users should focus their development efforts on the system components of business processes that can benefit from the use of information technology. Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 51
Summary • Implementation involves acquisition, testing, documentation, training, installation, and conversion activities that transform a newly designed business system into an operational system for end users.
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 52
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 1
What is the Systems Approach? • A problem solving technique that uses a systems orientation to define problems and opportunities and develop solutions. • Analyzing a problem and formulating a solution involves the following interrelated activities: • Recognize and define a problem or opportunity using systems thinking • Develop and evaluate alternative system solutions • Select the system solution that best meets your requirements • Design the selected system solution • Implement and evaluate the success of the designed system Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 2
What is Systems Thinking? • Seeing the forest and the trees in any situation by: • Seeing interrelationships among systems rather than linear cause-and-effect chains whenever events occur • Seeing processes of change among systems rather than discrete snapshots of change, whenever changes occur • Ex: sales process of a business Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 3
Systems Thinking Example
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 4
Systems Development Lifecycle (SDLC)
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 5
Prototyping Definition: • The rapid development and testing of working models, or prototypes, of new applications in an interactive, iterative process that can be used by both IS specialists and business professionals
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 6
Prototyping Process
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 7
Systems Development Process Systems Investigation stage • Do we have business opportunities? • What are our business priorities? • How can information technologies provide information systems solutions that address our business priorities? Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 8
Feasibility Study Definition: • A preliminary study where the information needs of prospective users and the resource requirements, costs, benefits, and feasibility of a proposed project are determined
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 9
Feasibility Study • A team of business professionals and IS specialists formalize this study in a written report • It includes preliminary specifications and a development plan for a proposed business applications • If the management approves feasibility study , the development process can continue Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 10
Feasibility Categories • Organizational – how well a proposed system supports the strategic business priorities of the organization • Economic – whether expected cost savings, increased revenue, increased profits, reductions in required investment, and other types of benefits will exceed the costs of developing and operating a proposed system Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 11
Feasibility Categories • Technical – determine if reliable hardware and software capable of meeting the needs of a proposed system can be acquired or developed by the business in the required time • Operational – willingness and ability of the management, employees, customers, suppliers, and others to operate, use, and support a proposed system Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 12
Feasibility
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 13
Cost/Benefit Analysis • Tangible – costs or benefits that can be quantified • Ex: cost of h/w and s/w, employee salary • Intangible – costs or benefits that can not be quantified • Ex: loss of customer goodwill
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 14
Systems Analysis Definition: • An in-depth study of end user information needs that produces functional requirements that are used as the basis for the design of a new information system
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 15
What does Systems Analysis Study? • The information needs of a company and end users. • The activities, resources, and products of one or more of the present information systems being used. • The information system capabilities required to meet information needs of users, and those of other business stakeholders that may use the system. Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 16
Organizational Analysis • Study of the organization including: • Management Structure • People • Business Activities • Environmental Systems • Current Information Systems Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 17
Analysis of the Present System • Study the existing system • Analyze how this system uses hardware, software, network, and people resources to convert data resources into information products • Document how the information system activities of input , processing, output, storage and control are accomplished
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 18
Functional Requirements Definition: • End user information requirements that are not tied to the hardware, software, network, data, and people resources that end users presently use or might use in the new system
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 19
Functional Requirement Categories • User Interface • Processing • Storage • Control
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 20
Systems Design Definition: • Design activities that produce system specifications satisfying the functional requirements that were developed in the systems analysis process
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 21
System Design Categories
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 22
User Interface Design Definition: • Focuses on supporting the interactions between end users and their computerbased applications
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 23
Checklist for Corporate Websites • Remember the customer – successful websites are built solely for the customer, not to make company vice presidents happy • Aesthetics – successful designs combine fastloading graphics and simple color palettes for pages that are easy to read • Broadband Content – the Web’s coolest stuff can’t be accessed by most Web surfers; don’t make it the focus of a site Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 24
Checklist for Corporate Websites • Easy to navigate – make sure it’s easy to get from one part of site to another • Searchability – include a useful search engine • Incompatibilities – test site with target web browsers
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 25
Checklist for Corporate Websites • Registration forms – short registration forms are a useful way to gather customer data • Dead links – be sure to keep links updated
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 26
System Specifications Definition: • Hardware, software, network, data, and personnel specifications for a proposed system that formalize the design of an application’s user interface methods and products, database structures, and processing and control procedures
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 27
End User Development Definition: • IS professional plays a consulting role, while end user does his/her own application development
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 28
End User Development
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 29
Encouraging End User Web Development • Look for tools that make sense • Spur creativity • Set some limits • Give managers responsibility • Make users comfortable Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 30
Systems Implementation • Hardware and software acquisition • Software development • Testing of programs and procedures • Conversion of data resources • Conversion alternatives • Education and training of end users and specialists who will operate a new system Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 31
Project Management Definition: • IT and business unit managers enforce a project plan which includes job responsibilities, time lines for major stages of development, and financial budgets
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 32
Implementation Process
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 33
Hardware Evaluation Factors • Performance
• Ergonomics
• Cost
• Connectivity
• Reliability
• Scalability
• Compatibility
• Software
• Technology
• Support
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 34
Software Evaluation Factors • Quality
• Connectivity
• Efficiency
• Maintenance
• Flexibility
• Documentation
• Security
• Hardware
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 35
IS Services • Developing a company website
• System design
• Installation
• Contract programming
• Conversion • Employee training
• Consulting services • System integration
• Hardware maintenance Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 36
IS Services Evaluation Factors • Performance
• Backup
• Systems development
• Accessibility • Business Position
• Maintenance • Hardware • Conversion • Software • Training Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 37
System Testing • Testing and debugging software • Testing website performance • Testing new hardware • Review of prototypes of displays, reports and other output Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 38
Data Conversion • Converting data elements affected by new application • Correcting incorrect data • Filtering out unwanted data • Consolidating data from several databases • Organizing data into new data subsets Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 39
Importance of Data Conversion • Improperly organized and formatted data is frequently reported to be one of the major causes of failures in implementing new systems.
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 40
Importance of Documentation • Documentation serves as a method of communication among the people responsible for developing, implementing, and maintaining a computer-based system. • Documentation is extremely important in diagnosing errors and making changes, especially if the end users or systems analysts who developed a system are no longer with the organization. Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 41
Training • Data entry • All aspects of the proper use of a new system • Educate managers and end users in how the new technology impacts the company’s business operations and management Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 42
Conversion Methods • Parallel – both old and new systems are operating until the project development team and end user management agree to switch completely to the new system • Plunge – no overlap of old and new system
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 43
Conversion Methods • Phased – only parts of a new application or only a few departments at time are converted • Pilot – One department serves as a test site
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 44
Conversion Methods
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 45
Systems Maintenance Definition: • Monitoring, evaluating, and modifying of operational business systems to make desirable or necessary improvements
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 46
Systems Maintenance
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 47
Learning Curve Definition: • Personnel who operate and use the system will make mistakes simply because they are not familiar with it; though such errors usually diminish as experience is gained with a new system
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 48
Postimplementation Review Definition: • Periodic review or audit of a system to ensure that it is operating properly and meeting its objectives
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 49
Summary • Business end users and IS specialists may use a systems approach to help them develop information system solutions to meet business opportunities. • Prototyping includes the use of prototyping tools and methodologies, which promote an iterative, interactive process that develops prototypes of user interfaces and other information system components. Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 50
Summary • The application development capabilities built into many end user software packages have made it easier for end users to develop their own business applications. • End users should focus their development efforts on the system components of business processes that can benefit from the use of information technology. Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 51
Summary • Implementation involves acquisition, testing, documentation, training, installation, and conversion activities that transform a newly designed business system into an operational system for end users.
Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
12 - 52
Related Documents
Developing Business/it Solutions
October 2019 19
Developing Xml Solutions
November 2019 11
Developing Business/it Solutions
November 2019 19
Developing Visio Solutions Visio 2000
November 2019 36
Solutions
November 2019 54