Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
105 Cards in this Set
- Front
- Back
|
Data is _________ _________ without further meaning.
|
raw facts
|
|
|
Information is data that an Information System (IS) has ________________ into meaningful information.
|
transformed
|
|
|
Good Information Characteristics Always Take Real Sufficient Reliable Coats |
Accurate (free from errors), Timely (available when needed), Relevant (appropriate), Sufficient (the right amount), Reliable Cost-Effective (cost doesn't outweigh benefits). |
|
|
Two types of Information decisions
|
Structured - follows a formula Unstructured - several answers might work |
|
|
Managerial Information Systems E M O |
Executive - highly summarized Managerial - tactical decision making based upon Exec. Operational - Structured, detailed |
|
|
Five Component Parts in Information System (Howard, Saw, Dana, Poke, Peter) |
Hardware, Software, Data, Procedures, People |
|
|
Information Granularity
|
Coarse - Highly Summarized, usually a report. Fine - Highly detailed useful for low level managers |
|
|
3 User roles in Information Systems C S E |
Computer User - Basic, can operate the system Super User-Understands the IS and how it works Expert User - Can operate, train and convert old to new |
|
|
A network of activities, repositories, roles, resources and flows (series of steps) that interact to accomplish a business function. |
Business Process
|
|
|
A process whereby a network of IS takes inventory, reduces stock, tracks buying trends and identifies times to reorder. (Walmart) |
Fully Automated Process
|
|
|
A process whereby staff counts inventory, inputs inventory in spreadsheet or data collection tool and executes a purchase electronically. (small grocery) |
Partially Automated Process
|
|
|
A process where items are manually weighed, sold, and verbally providing the customer the price. (Farmers Market) |
Fully Manual Process
|
|
|
Business Process Engineering Phases Cathy Called In Albert |
Create As-Is model Create Components Implement the processes Assess the results |
|
|
a graphic representation, using ______ ________notation, of how data flow and how activities are related in an organization. |
Process Modeling
|
|
|
Process Modeling Symbol - Rectangle |
Activity
|
|
|
Process Modeling Symbol - Diamond |
Decision/Gateway
|
|
|
Process Modeling Symbol - Page |
Data
|
|
|
Process Modeling Symbol - Dashed Line |
Data Flows
|
|
|
Process Modeling Symbol - Solid Line
|
Control Flows
|
|
|
Components of the Business Process (After Running Fall Down) |
Activities, Resources, Facilities, Data Flows |
|
|
What are Facilities? |
storage areas (warehouses or Databases)
|
|
|
the alignment of an organization's planning, decisions, and actions to enable it to reach its goals, mission, objectives |
Organizational Strategy
|
|
|
Reasons why organizations create information systems obtain solve |
1. obtain its goals, objectives or mission. 2. solve a major problem or meet a challenge |
|
|
Michael Porter's Five Forces Model - Reasons (3) understand determine how to conduct |
1. better understand the industry 2. determine how attractive the prospect of starting a business in a given industry. 3. how to conduct a successful business in a given industry |
|
|
Porter's Five Forces Randy Takes Camille Shopping Today |
Rivalry Threat of Substitution Customer Bargaining Power Supplier's Power Threat of New Entrant |
|
|
Porter's Generic Strategies Model Reasoning (2) Leverage Identify |
1. Businesses leverage their strengths to select the strategy for best success 2. identify the best way to operate |
|
|
Porter's Generic Strategies B B Nay Nay |
Broad Cost Leadership - Across a industry Broad Differentiation - Unique Narrow Cost Leadership Narrow Differentiation |
|
|
reduced overall production/distribution cost, and appeal to cost-conscious customers. Lower prices (maintaining value (cost/quality) |
Broad Cost Leadership Strategy
|
|
|
products stand out, customers willing to pay premium price. Focus on satisfying under-served needs. |
Broad Differentiation Strategy
|
|
|
focus on cost behavior on a smaller segment (southwest - only in certain markets and one type of aircraft) |
Narrow Cost Leadership Strategy
|
|
|
focus on one market segment (Ferrari targets high performance car enthusiasts) |
Narrow Differentiation Strategy |
|
|
network of value creating activities with primary activities that create value and secondary activities that indirectly contribute to value creation |
Value Chain
|
|
|
Value Chain - Primary Activities I O O M S |
Inbound Logistics Operations Outbound Logistics Marketing and Sales Service |
|
|
Value Chain - Secondary Activities P H T I |
Procurement, Human Resources, Technological Development Infrastructure |
|
|
Value Chain Analysis Advantages Identify enhancing modifying identifying |
Identify inefficiencies enhancing activities modifying activities identifying weak information systems |
|
|
Approaching an IS using Porter's models 1. Five Forces - understanding of the ________ the company _______ in the industry 2. generic strategies - organization _________ the best way to ____________. 3. Value Chain - enables the org to ______ _______ processes to look for _____________. |
1. Five Forces - understanding of the forces the company faces in the industry 2. generic strategies - organization develops the best way to compete. 3. Value Chain - enables the org to break down processes to look for opportunities. |
|
|
Tasks to Determine Requirements - System Development C I E A |
1. Cooperate 2. Identify Expectations 3. Examine Previous Work 4. Ask Questions |
|
|
The _____ a project the harder it is to change
|
Larger
|
|
|
Budgeting Factors - Tools to Determine System Cost C C E |
Cost Benefit Analysis Cost Projection Examining Past Projects and their Costs |
|
|
Outsourcing Advantages (3) Management Cost Risk |
1. Management Advantage |
|
|
Outsourcing Disadvantages (3) Loss Benefits No |
1. Loss of Control 2. Benefits eventually outweighed by overall cost 3. No Easy Exit |
|
|
a rigid, phased approach to system development. Usually offers a high chance for success. |
System Development Life Cycle (SDLC)
|
|
|
System Development Life Cycle (SDLC) Strengths (6) Able detailed good great Easy staff |
1. Able to monitor and maintain control over large projects 2. detailed phases 3. Good documentation 4.Great input into requirements 5. Easy System Maintenance 6. Staff changes do not impact development |
|
|
System Development Life Cycle (SDLC) Weaknesses (6) Longer Higher needs Rigid difficulty limited |
1. Longer Development time 2. Higher Cost 3. needs well-defined systems at the beginning 4. Rigid Process 5. difficulty estimating scheduling and budgeting 6. Limited user input |
|
|
System Development Life Cycle (SDLC) Phases (People Always Delight In Meals) |
Planning Analysis Design Implementing Maintenance |
|
|
System Development Life Cycle (SDLC) Phase 1 Planning (3) define conduct form |
Planning - define the scope - conduct feasibility studies - form a project team |
|
|
System Development Life Cycle (SDLC) Phase 2 Analysis (5) Identify Identify Identify Identify create |
Analysis - identify system requirements - identify system object requirements - identify system security requirements - identify personnel procedures - create a data model |
|
|
System Development Life Cycle (SDLC) Phase 3 Design (5) H S D Create Create |
Design - HW - SW - DB - Create job descriptions - Create system procedures |
|
|
System Development Life Cycle (SDLC) Phase 4 Implementation (4+) Build Test++ Convert+++ Training |
Implementation - Build the system - test the system - - - Unit Test - - - User Test - Conversion - - - Parallel - - - Pilot - - - Plunge - Training |
|
|
System Development Life Cycle (SDLC) Phase 5 Maintenance (3) Resolve Addressing Issuing |
Maintenance - Resolve request for revisions - Addressing reported problems - Issuing Patches |
|
|
building a preliminary model of a proposed finished system / temporary systems that don't include all functionality
|
Prototyping
|
|
|
Prototyping advantages (4) Development Systems User Users |
1. Development time / cost is reduced 2. Systems likely to fulfill user requirements 3. User involvement provide valuable feedback 4. Users adapt easily to finished system |
|
|
Prototyping Disadvantages (4) Users Documentation Expectations prototyping |
1. Users use prototypes as final systems 2. Documentation is incomplete 3. expectations are high and lead to disappointment of final system 4. prototyping can not accommodate large amounts of users |
|
|
Prototyping Steps I D T R |
1. Identify 2. Develop 3. Test 4. Refine |
|
|
Prototyping is an __________ approach |
iterative |
|
|
Object Orientated Development (OOD) is an_____________ System |
unstructured
|
|
|
ability to appear in different forms (object appearing as a sub object) |
Polymorphism
|
|
|
act of storing data and procedures together in an object |
Encapsulation |
|
|
allows an object to inherit properties from objects in different classes
|
Inheritance |
|
|
collections of similar objects that can contain subclasses
|
Classes
|
|
|
entities that can interact with one another |
Objects
|
|
|
Object Orientated Development (OOD) Advantages (4) Code Objects Objects Security |
1. Code is modified easily using other objects 2. objects are reusable 3. objects are modular 4. Security is easy to set in program code |
|
|
Object Orientated Development (OOD) Disadvantages (6) Code OOD Takes Fewer Not Extensive |
1. Code is difficult to read and understand 2. OOD is ineffective at representing non-objects 3. it takes longer to execute routines 4. fewer functions 5. not user friendly 6. extensive evaluation and monitoring |
|
|
a methodology that enables a rapid development process for systems while maintaining an acceptable level of quality. |
Rapid Application Development (RAD)
|
|
|
Rapid Application Development (RAD) Qualities (5) Accomplished prototyping reuses uses 80/20 |
- Accomplished in small groups - prototyping and iterative testing - reuses software components - uses visual programming - 80/20 |
|
|
Rapid Application Development (RAD) develops software by ________ and ________ existing software components into a new system |
assembling, integrating (Component based Development) |
|
|
Rapid Application Development (RAD) Life Cycle (4) R U C I |
1. Requirements Planning 2. User Design 3. Construction 4. Implementation |
|
|
Rapid Application Development (RAD) Disadvantages (6) less more quality needs less prone |
1. less scalable, may not contain all the features 2. more costly 3. quality problems 4. needs not adequately met 5. less efficient 6. Prone to Problems |
|
|
Agile Systems Methodology Advantages (6) breaks iterations Small Face Working More adaptive |
1. breaks tasks into small increments with minimal planning -no long term planning 2. Iterations are short time frames (1-to 4 weeks)- - Each iteration involve planning, requirements analysis, design, coding, unit testing, and acceptance testing. 3. Small cross functional teams 4. Face to Face communications / Stand-Up Meetings 5. Working software is the primary measure of progress. 6. More adaptive to project changes than predictive. |
|
|
Agile Systems Methodology is based on _______ and ________ development. |
iterative and incremental development.
|
|
|
Extreme Programming (XP) is a _________-_______, ________ process |
customer-driven, agile process
|
|
|
Extreme Programming (XP) responds well to changes because of ____________ that enable _____________ _____________ and ____________. |
of checkpoints that enable customer feedback and review
|
|
|
Extreme Programming (XP) 12 core practices A Customer XP team XP use |
1. Customer Defines application with User Stories 2. XP team puts small code into production 3. XP use common system names and descriptions |
|
|
Extreme Programming (XP) 12 core practices B simply writes frequent |
4. simply written, object orientated code meets requirements 5. writes automated unit tests upfront uses through out the process. 6. frequent revise and edit of unit code (Refactoring) |
|
|
Extreme Programming (XP) 12 core practices C Pair Collective Integrate |
7. Pair Programming 8. Collective Ownership of code 9. integrate code and save to repository every couple hours |
|
|
Extreme Programming (XP) 12 core practices D programmers Customer Rep Common |
10. programmers work full time 11. Customer Rep onsite through out development 12. common coding structure |
|
|
Extreme Programming (XP) Phases Please, Don't, Chew, The, Line |
1. Planning 2. Designing 3. Coding 4. Testing 5. Listening |
|
|
XP Advantages (9) A focus A quality Simple Continuous Robustness Resilience Reduced High The ability |
1. A focus on Programming code for quick delivery of features 2. A quality methodology for smaller systems, resulting in low cost compared with other methodologies 3. Simple design, because each feature is coded, tested, and implemented independent of other functionalities 4. Continuous testing for ensuring quality feature development 5. Robustness, because each feature is listed along with a cost estimate for organizations to rank feature development 6. Resilience, because changes can be made late in the system's development life cycle, incorporated into development, and used without going back to an earlier phase as in other methodologies 7. Reduced risk in Programming and coding because two programmers work on each feature: one writing code and one testing it 8. High employee satisfaction because of users' intense involvement during the entire development process 9. The ability to add features at any time during the development process without negatively affecting development |
|
|
XP Disadvantages (7) Scant potential Unstable Limited Methodology Does not work Constant |
1. Scant documentation because of the lack of design-centered approach usually followed in larger systems development projects 2. The potential for user conflicts to bog down the development when agreements are hard to reach 3. Unstable requirements because of the lack of a formal requirements analysis before design and Programming are done 4. Limited overall design specifications because features are designed as needed. 5. Methodology geared toward single projects; not good for large projects 6. Does not work well when scalability issues exist because they cannot be integrated with other programs later 7. Constant contact with the customer is assumed, which can be difficult to ensure if users are ambivalent or do not want to be a part of the development team |
|
|
A type of audit that ensures an org system and applications are appropriate and controlled to maintain security and reliability |
Systems-Type Audit
|
|
|
A type of audit that includes a risk analysis of new and existing projects to determine how organizations compare |
Process-Type Audit
|
|
|
Successful management of IS....(4) keeps integrating strategic data |
1. keeps systems from being obsolete 2. integrating systems to avoid duplication 3. strategic approach 4. data integrity without duplication, inconsistencies and errors |
|
|
highest ranking exec, responsible for all IS within the org. |
Chief Information Officer (CIO)
|
|
|
IS Departments TODOD |
Technology, Operations, Development Outsourcing Relations, Data Admin |
|
|
Ethics are _________ guidelines in ________________. |
moral guidelines in organizations.
|
|
|
2 questions in ethics |
1. was harm done to anyone 2. did someone gain an undeserved advantage from the behavior. |
|
|
Approaches to Managing Ethics (4) IGWT |
1. Informal Approach - address as occurs 2. General Written Procedures 3. Written Code of Ethics 4. Top down Ethics Approach |
|
|
Important Steps in Promoting Ethics (5) Inform Incorporate Train avoid Formal |
1. Inform employees about policies and procedures 2. incorporate ethics in all areas of the organization 3. train employees how to recognize unethical behavior 4. help avoid circumstances 5. Hold Formal Training |
|
|
Types of threats to Information System (2)
|
1. Unintentional 2. intentional |
|
|
Types of Threats a (5) |
1. Natural 2. Human 3. Environmental 4. Physical 5. Technical |
|
|
Aspects to consider in a security plan (4) HSDP |
1. Hardware Security 2. Software Security 3. Data Security 4. People Security |
|
|
Physical Safeguards (3) ICS |
1. ID Badges 2. Cubical Design 3. Shredder |
|
|
Acts of Congress that require Data backups (3) SHG |
1. Sarbanes-Oxley Act 2. HIPPA 3. Gramm-Leach-Bliley Act (GLBA) |
|
|
Types of Media for Backups (4) OSMC |
1. Optical 2. Semiconductor 3. Magnetic 4. Cloud |
|
|
Organizations spend ____% of their IT budget on disaster recovery |
2-4%
|
|
|
Disaster Recovery Plans (DRP) Objectives (7) |
1. decrease risk of disaster 2. decrease probability of disaster 3. decrease insurance premiums 4. protect assets 5. reduce dependencies on human decision making 6. organization stability 7. improve employee safety |
|
|
Disaster Recovery Plans (DRP) Steps (4+) |
1. Select DRP Team - entire organization 2. conduct a risk analysis 3. identify recovery options 4. Create a DRP strategy - - - key contacts - - - HW / SW considerations - - - Data Files - - - Communications and Infrastructure - - - Org Facilities - - - Hot / Cold Sites |
|
|
Types of protected data (2) |
1. Business Financial Data 2. Personally Identifiable Information (Customer Data) |
|
|
Data Safeguards should ensure (3) CIA |
1. Confidentiality 2. Integrity 3. Availability |
|
|
If you are aware / witness a security compromise or breach (6) Protect Identify Limit Alert Resolution Enable |
1. protect company and customer 2. identify offender 3. limit damage 4. alert customers 5. help in the resolution of security incidents. 6. enable policies and procedures to be effective. |
|
|
Problem Management Benefits (4) Reduce Quality Increased Proactive |
1. Reduce number of errors/incidents 2. Quality of Service Improves 3. Increased Organizational Knowledge 4. Proactive problem management |
|
|
work done to resolve issues before they are reported
|
Proactive
|
|
|
customer initiates problem solving, contacting customer support |
Reactive
|
|
|
Problem Management Steps (5) Record Classify Check Track Provide |
1. Record 2. Classify / Categorize 3. Check the incident against known issues. 4. Track Progress 5. Provide closure |
|
|
Change Management Stages (5) Acceptance Classification Approval Building Post |
1. Acceptance and Filtering 2. Classification 3. Approval 4. Building, Testing and Implementing 5. Post Implementation Review |
