Cis465f00 2basiccon
Cis465f00 2basiccon
CUSTOMER
Manager who needs to hire an employee Applicant who receives responses about a job application
Government agency that receives reports about compliance to equal opportunity guidelines
PRODUCT
List of applicants who fit the criteria
Selected data items about each applicant Automatically generated rejection letters
BUSINESS PROCESS
Major Steps:
Define the criteria for selecting applicants Receive rsums Scan rsums and extract data
Select applicants meeting criteria and forward their rsums to the hiring manager
Send out rejection letters Track the hiring process Store applicant data for future searches Rationale: Instead of finding appropriate candidates by searching through paper rsums, extract the information on the rsums and do the search automatically.
PARTICIPANTS
Human resources employees Manager doing the hiring
INFORMATION
Description of job opening Scanned rsums converted into a database format List of qualified applicants
TECHNOLOGY
Rsumix software Scanner
Unidentified computers
DEBATE TOPIC
The technology is Resumix is designed to convert a resume into a series of fields in a database regardless of what the initial resume looks like. Statements that dont match these specific fields arent recognized. Does the use of this technology imply that a company does not care about the individuality of the applicants?
INTRODUCTION
Framework - brief set of ideas about organizing a thought process about a concept.It helps by identifying topics that should be considered and shows how they are related. Models - useful representation of reality. The describe or mimic reality without dealing with the details They both help us understand complexity
CIS 465 - WCA Framework
7
A Classification of Models
Mathematical Models
Mathematical (quantitative) models - the complexity of relationships sometimes can not be represented iconically or analogically, or such representations may be cumbersome or time consuming.A more abstract model is built with mathematics. Note: recent advances in computer graphics use iconic and analog models to complement mathematical modeling. Visual simulation combines the three types of models.
10
Mental Models
People often use a behavioral mental model. A mental model is an unworded description of how people think about a situation. The model can use the beliefs, assumptions, relationships, and flows of work as perceived by an individual. Mental models are a conceptual, internal representation, used to generate descriptions of problem structure, and make future predications of future related variables. Support for mental models are an important aspect of Executive Information Systems. We will discuss this in depth later.
CIS 465 - WCA Framework
11
Examples of Models
12
13
14
15
16
18
19
20
21
University registration system permits students to sign up for specific class sections
Work system supported by the information system: Registering for classes Aspects of the work system not included in the information system: Deciding which classes to take and which sections to sign up for in order to have a good weekly schedule
22
23
24
25
26
27
PERFORMANCE
How well do the components operate individually? How well does the system operate? (How well is the work performed?) How well should the system operate?
INFRASTRUCTURE
What technical and human infrastructure does the work rely on? In what ways does infrastructure present opportunities or obstacles?
CONTEXT
What are the impacts of the organizational and technical context? In what ways does the context present opportunities or obstacles?
RISKS
What foreseeable things can prevent the work from happening, can make the work inefficient, or can cause defects in the work product? What are the likely responses to these problems?
28
Important Point Improvements in a work system are usually related to the links between the architecture and the performance perspectives. Customer satisfaction is largely determined by product performance. Product performance is determined by a combination of product architecture and the internal work system performance. Note: efficiency vs. effectiveness
CIS 465 - WCA Framework
29
30
31
Architecture, Perspective #1
Architecture is a summary of how a work system operates. It focuses on the components of the system and how those components are linked, and how they operate together to produce outputs. It is not merely a technical issue; IT and business professional involved with a system need to understand how it operates. It is impossible to build an information system without detailed documentation of information and technology components of the architecture. We use successive decomposition for documenting and summarizing architecture. Process operation and process characteristics
CIS 465 - WCA Framework
32
Architecture, Perspective #1
33
Architecture, Perspective #1
CUSTOMER
Customers entire cycle of involvement with the product Requirements Acquisition Use Maintenance Retirement
PRODUCT
Components Information content
Physical Content
Service content (more in Chapter 6)
CIS 465 - WCA Framework
34
Architecture, Perspective #1
BUSINESS PROCESS
Process operation: Processes providing inputs Sequence and scheduling of major steps Processes receiving the outputs Process characteristics: Degree of structure Range of involvement Level of integration Complexity Degree of reliance on machines Linkage of planning, execution, and control
Architecture, Perspective #1
PARTICIPANTS
Formal and informal organization:
INFORMATION
Major data files in the database:
TECHNOLOGY
Major components: Hardware Software
Job responsibility
Organization chart
36
Performance, Perspective #2
Performance - How well the system operates. A complete analysis involves qualitative and quantitative measurements. Consider some performance variables.
37
Performance, Perspective #2
38
Performance, Perspective #2
CUSTOMER
Customer Satisfaction
PRODUCT
Cost Quality Responsiveness Reliability Conformance to standards and regulations
39
Performance, Perspective #2
BUSINESS PROCESS
Rate of output Consistency Productivity Cycle time Flexibility Security
40
Performance, Perspective #2
PARTICIPANTS
Skills Involvement Commitment Job satisfaction
INFORMATION
Quality Accessibility Presentation Prevention of unauthorized access
TECHNOLOGY
Functional capabilities Ease of use Compatibility Maintainability
41
SKILLS OF PARTICIPATION
Vague description: The sales people are very experienced. Measurement: Every salesperson has 5 or more years of experience; 60% have more than 10 years. Interpretation:This system is (or is not) appropriate for such experienced people.
Infrastructure, Perspective #3
Infrastructure: Essential Resources shared with other systems. Infrastructure failures may partially be beyond the control of people who rely on it (e.g. power outages). Evaluation is difficult because the same infrastructure may support some applications excessively and others insufficiently. Critical mass, having enough users to attain desired benefits, may be a key infrastructure issue. Distinguish between infrastructure and the supporting technology (laptops used in the sales process vs. used for company e-mail).
CIS 465 - WCA Framework
43
Infrastructure, Perspective #3
Technology can be infrastructure if it is outside the work system, shared between work systems, owned and managed by a central authority, or when details are largely hidden from users. Business professionals are often surprised at the amount of effort and expense absorbed by human infrastructure.
44
Infrastructure, Perspective #3
45
Infrastructure, Perspective #3
CUSTOMER
Technical and human infrastructure the customer must have to use the product
PRODUCT
Infrastructure related to information content Infrastructure related to physical content Infrastructure related to service content
46
Infrastructure, Perspective #3
BUSINESS PROCESS
Infrastructure related to internal operation of the process Infrastructure related to inputs from other processes Infrastructure related to transferring the product to other processes
47
Infrastructure, Perspective #3
PARTICIPANTS
Shared human infrastructure
INFORMATION
Shared information infrastructure
TECHNOLOGY
Shared technology infrastructure
48
Context, Perspective #4
50
Context, Perspective #4
CUSTOMER
Issues in the customers environment that may affect satisfaction or use Business and competitive climate
PRODUCT
Substitute products Ways the customer might bypass this type of product altogether
51
Context, Perspective #4
BUSINESS PROCESS
Organizational culture Concerns of stakeholders Organizational policies and initiatives Government regulations and industry standards
52
Context, Perspective #4
PARTICIPANTS
Incentives Other responsibilities and job pressures
INFORMATION
Policies and practices regarding information sharing, privacy, etc.
TECHNOLOGY
Technology policies and practices
53
Risk, Perspective #5
Risks: Foreseeable Things that can go wrong in terms of: accidents and malfunctions computer crime project failure (To be considered again in Chapter 13.)
54
Risk, Perspective #5
55
Risk, Perspective #5
CUSTOMER
Customer dissatisfaction Interference by other stakeholders
PRODUCT
Inadequate or unreliable products
Fraudulent products
56
Risk, Perspective #5
BUSINESS PROCESS
Operator error Sloppy procedures Inadequate backup and recovery Mismatch between process requirements and participants abilities Unauthorized access to computers, programs, data
57
Risk, Perspective #5
PARTICIPANTS
Crime by insiders or outsiders
INFORMATION
Data errors Fraudulent data
TECHNOLOGY
Equipment failure Software bugs Inadequate performance Inability to build common sense into information systems
Inattention by participants
Data theft Failure to follow procedures Inadequate training
58
Systems Analysis
Systems Analysis is different for the business professional than from the system builder. Technical vs. non-technical. Think of what will happen in the future when systems building tools become more effective for non-programmers.
59
60
Identify the purpose of the analysis and scope of the work system. Tradeoffs - broad vs. narrow. Constraints priorities system snapshots
61
62
CUSTOMER
Product used by: Internal or external customers who use or receive direct benefit from the product
Other stakeholders: People who have a significant stake in the work system or its product even though they do not use the product directly and do not participate directly in the work system
Infrastructure requirements: Infrastructure the customer should have to use the product effectively
63
PRODUCT
Information content: The aspects of the product that consist of information Physical content: The aspects of the product that consist of physical things Service content: The aspects of the product that consist of services performed for specific customers
64
BUSINESS PROCESS
Major steps: Listing the major steps in this business process Rationale: The overriding idea or approach that determined the process would be performed using the current approach rather than another Processes providing inputs: External processes outside the work system that produce inputs of information, physical things, or services needed in order for this business process to operate Processes receiving the product: The customers processes that receive and use the product of this work system
65
PARTICIPANTS
People who perform the work Shared human infrastructure
INFORMATION
Created or modified within this system
TECHNOLOGY
Technology within the system
66
Summary: Value of WVA Basic Ideas to Understanding work systems and information systems:
Six Elements of WCA Five Perspectives Four-Step General Systems Analysis Approach
4.Decide what to do
68
69
Customer
ignore customer and the fact that the customer should evaluate the product. Treating managers as customers even though they dont use the product directly.
Product
forget that the purpose is to produce a product or service for a customer. Forget that the product of a work system is often not the product of the organization.
70
Business Process
Define process so narrowly that improvement is of little consequence. Define process to widely that it is too complex. Confuse business process measures(consistency and productivity) with product measures (cost to the customer and quality perceived by customer). Think of business process as theory and ignore its support by participants, information, and technology
Participants
ignore incentives and other pressures focus on users rather than participants.
CIS 465 - WCA Framework
71
Information
assume better information generates better results. Ignoring the importance of soft information not captured by formal systems.
Technology
assume better technology generates better results. Focus on the technology without thinking about whether it makes a difference in the work system.
72
73
Context
tendency to ignore incentives, organizational culture, and non-participant stakeholders when designing systems.
Risks
tendency to assume system will operate as planned.
74