The Information System
June 23, 2012
Information System
• Capture and management of data to produce useful information that supports an organization and its employees, customers, suppliers and partners
ClassificationTransaction Processing System Process Business Transaction such as
orders, time cards, payments and reservation
Management Information System Use Transaction data to produce information needed by managers to run the business
Decision Support Systems Systems that help various decision makers identify and choose between option and decisions
Expert Systems Systems that capture and reproduce the knowledge of an expert problem solver or decision maker and then simulate the “ thinking” of an expert
ClassificationCommunication and Collaboration Systems
Enhance communication and collaboration between people, both internal and external to the organization
Executive Information System Systems tailored to the unique information needs of executives who plan for the business and asses performance against plan
Office Automation System Help employee create and share documents that support data to day office activities
System Stakeholders
Business Drivers of Information System
An Electronic Commerce Storefront
Technology Drivers of Information System
Enterprise Application
Supply Chain Management
Customer Relationship Management
System Development and Problem Solving
Information System Development
System Development Process
• Set of activities, methods, best practices, deliverables and automated tools that stakeholders use to develop and continuously improve information systems and software
Capability Maturity Model
• A standardized framework for assessing the maturity level of an organization’s information systems development and management processes and products. It consist of five levels of maturity
Capability Maturity Model
Capability Maturity ModelLevel 1 Initial At this level, systems development projects follow no consistent
process. Documentation is sporadic or not consistent from one project to the next thus creating problems for those who must maintain a system over its lifetime.
Level 2 Repeatable At this level, project management process and practices are established to track project cost, schedules and functionality
Level 3 Defined At this level, a standard system development process ( methodology) . As a result of using standardized process for all projects , each projects results in consistent and high quality documentation and deliverables
Level 4 Managed AT this level, measurable goals for quality and productivity are established. Detailed measures of the standard system development process s and product quality are routinely collected and stored in data base.
Level 5 Optimizing In this level, the standardized system development process is continuously monitored and improved based on measures and data analysis established in level 4
System Development Methodology
• A formalized approach to systems development process; a standardized process that includes the activities, methods, best practices, deliverables and automated tools to be sued for information systems development
Systems Development Methodologies
• Executes the systems development stage of a systems life cycle. Each individual information systems has its own life cycle. The methodology is the standard process to build and maintain that systems and all other information system through their life cycle
Systems Methodologies
• Architected Rapid Application Development• Dynamic Systems Development Methodology• Joint Application Development• Rapid Application Development• Rational Unified Process• Structures analysis and Design• eXtreme Porgramming
System Life Cycle
• The factoring of the lifetime of an information sytem into two stages: (1) systems development (2) systems operations and maintenance – first you built it, the you use it and maintain it
The System Life Cycle
Principles systems development• Get the system users involved• Use a problem solving approach• Established phases and activities• Document throughout development• Establish standards• Manage the process and projects• Justify information system capital investment• Don’t be afraid to cancel• Divide and Conquer• Design system for growth and change
Where do systems development projects come from?
• Problems – an undesirable situations that prevents the organization from fully achieving its mission, vision and goals or objectives
• Opportunity – a chance to improve the organization even in the absence of an identified problem
• Directive - an new requirement that is imposed by management, government or some external influence
Framework for Problem Identification
• P - the need to correct or improve performance• I - the need to correct or improve information• E - the need to correct or improve economics (controlled cost or increase profit)• C - the need to correct or improve control or security• E - the need to correct or improve efficiency of people or process• S - the need to correct or improve service to customers, suppliers, partners, employees, etc.
PIECES
Systems Development Phases
Systems Development Phases
Scope Definition Establish the size and boundaries of the project, the project vision, any constraints and limitation, the required project participants , the budget and schedule
Problem Analysis Determine if the project is “worth doing”. Will the benefit of solving these problems exceeds the cost of building the system to solve these problems?This stage determine whether to continue, Reduced or expand the scope , Canceled if the problems where deemed not worth solving
Requirement Analysis Determine what systems must do. Determines the priorities of the system. Requires a clear understanding of the business needs.
Logical Design The translation of business user requirements into a system model that depict only the business requirements and not any possible technical design or implementation of those requirements
Systems Development PhasesDecision Analysis Identify candidate technical solutions, Analyze those technical
solution for feasibility, recommends a candidate system as the target solution to be designedTechnical feasibilityOperational feasibilityEconomic feasibilitySchedule feasibility
Physical Design and Integration
The translation of business user requirements into a system model that depicts a technical implementation of the user’s business requirements
Construction and testing
Begin to construct and test system component for the designImplement the interface between the new system and the old systemData Bases , Data WarehouseUser and system interfaceCustom built software and commercial software
Installation and Delivery
Sometimes called the production Produce manuals, train user, etc.
END