Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

MGCR 331 (IS) Final > Sessions 15 and 16 (Hardware and Software) > Flashcards

Sessions 15 and 16 (Hardware and Software) Flashcards

1
Q

___ bits make up one byte. One byte creates a ____.

A

8 bits. One byte creates a character

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

byte size measurement: (4)

A
  1. kilobyte
  2. megabyte
  3. gigabyte
  4. terabyte
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

CPU cycles determine:

A

how quickly a central processing unit executes software instructions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

examples of input devices

A
  • keyboard, mouse, touchscreen, pointing stick, microphone
  • point of sale: captures transactions
  • bar code reader –> needs to be in direct line of sight
  • radio frequency ID (RFID) –> ex. opus card
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

what is the limiting factor with hardware?

A

heat –> how we can compact more into less space

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

the operating system:

A

directs traffic, manages files, manages resources

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

what does utility manage

A

add-ons

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

what are the two types of application software?

A
  1. personal productivity (Word, Excel, desktop publishing, personal finance, etc.)
  2. enterprise software (ERP, CRM, SCM)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

what are types of personal operating systems (4?)

A
  1. Mac OS
  2. Microsoft Windows
  3. Linux –> open source OS for high-end workstations and network servers
  4. Handheld: Android, iOS
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

how to choose the operating system?

A
  • compatibility
  • cost
  • customization
  • ease of use
  • stability
  • security
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

desktop vs enterprise software?

A

desktop: apps installed on a personal computer, typically supporting tasks performed by a single user
enterprise: apps that address the needs of multiple simultaneous users throughout an organization or work group

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

what are the problems with implementing enterprise IT?

A
  • incompatible IS
  • inconsistent operating practices
  • info is fragmented and stored in a myriad of places
  • individual function, business unit, factory, office
  • help support a local activity
  • maintenance of legacy systems is a nightmare
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

advantage of enterprise systems

A

different departments can now talk to each other

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

impact of enterprise systems

A
  • re-engineer business processes
  • streamline workflows, reduce inventories
  • shorten cycle times
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

what is a database management system?

A
  • aka database software

- software used for maintaining, creating, manipulating data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

most enterprise software works in conjunction with:

A

a database management system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

what are erp systems

A
  • enterprise resource planning
  • commercial software systems that automate and integrate many or most of a business’ processes

objective:

  • tightly integrate functional areas of organization
  • enable seamless info flow across the functional area
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

enterprise resource planning previously included:

A
  • silos of info
  • walking office to office
  • long lines
  • lack of communication
  • open 8-5, 5 days of week
  • inconsistent info
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

erp now includes:

A
  • no silos/no hassle
  • customer focused
  • cross-departmental
  • accessed by web
  • seamless service
  • 24/7
  • consistent info
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

upstream activities are:

A

supplier

21
Q

downstream activities are:

A

customer

22
Q

your ERP is the ____ with both CRM and SCM

A

interface

23
Q

buy side: SCM interfaces with ___

A

suppliers

24
Q

sell side: CRM interfaces with ___

A

customers

25
Q

what do business intelligence systems allow?

A

enables collaboration and monitoring of critical data across the three systems (ERP, CRM, SCM)

26
Q

types of customer relationships to measure with data analytics:

A
  • relationship profitability
  • relationship duration
  • number of relationships
27
Q

examples of frictions on supply chain

A
  • time
  • cost
  • inventories
28
Q

discuss making your own ERP from scratch

A
  • can mix and match components
    pro: benefit of customization which fits need of firm
    con: advantage comes at expense of high development and maintenance costs; time consuming (longer implementation time)
29
Q

discuss buying an ERP (vs making)

A
  • most vendor’s ERPs are flexible enough that you can install some modules (finance/HR) without buying whole package
    pros: faster implementation, lower IT overhead, builds on industry best practice
    cons: may not always be exact fit for your organization; costly modifications to preserve processes that provide a competitive edge
30
Q

what are three interesting issues with software

A
  1. handling upgrades
  2. compatibility
  3. piracy issues
31
Q

conventional software firms vs. open source software

A

conventional:
- does not provide source code for commercial products
- treat intellectual property as closely guarded secret

OSS:

  • anyone can look at source code
  • anyone can change it and redistribute it provided modified software remains open and free
  • generally is free
32
Q

OSS examples

A
  • Linux (found on 30% of servers in corporate America)

- Firefox, OpenOffice, SugarCRM

33
Q

a popular combination of OSS: LAMP

A

Linux
Apache Web server software
MySQL
P (several programming languages- Perl, Python, PHP)

34
Q

why open source?

A
  • cost
  • reliability (many eyes on code, can fix problems quickly)
  • security
  • scalability (most can run on low-end to high-end hardware)
  • agility and time to market
35
Q

where is the money in OSS?

A

– Vendors make money on OSS by selling support
and consulting services (Redhat)
– Sell advanced hardware (Sun, IBM)
– Sell proprietary software to augment or optimize
OSS
– Steal customers from a stronger competitor
(Oracle)

36
Q

drawbacks of OSS? (3)

A
  1. Complexity of some OSS products
    – Difficult to install and maintain
    – Higher total cost of ownership for some products
  2. Concern about the ability of a product’s
    development community to provide support
    or product improvement
  3. Legal and licensing concerns
    – violation of software patents or other unauthorized
    use of proprietary code
    – Varying types of OSS licensing agreements
37
Q

what are the system development methodologies? (4)

A

 SDLC a.k.a. Waterfall methodology
 Prototyping
 Rapid application development (RAD)
 Agile Method

38
Q

the systems development life cycle looks at:

A

how do we develop the software?

39
Q

discuss phase 1 of the Waterfall method (planning):

A

 What are our opportunities
 What are our priorities
 Can IS be used to address these needs?

 Define the system to be developed
 Critical success factor - a factor simply critical to your
organization’s success
 Set the project scope
 Project scope document - a written definition of the
project scope and is usually no longer than a
paragraph
 Develop the project plan including tasks,
resources, and timeframes

40
Q

discuss phase 2 of the Waterfall method (Analysis):

A

The first challenge is finding the right people
to participate.
 The second challenge is collecting and
integrating the information

Functional Requirements:
User Interface Requirements
 Automatic entry of product data and easy-to-use
data entry screens for web customers
 Processing Requirements
 Fast, automatic calculation of sales totals and
shipping costs
 Storage Requirements
 Fast retrieval and update of data from product,
pricing, and customer databases

41
Q

discuss phase 3 of the Waterfall method (Design):

A
  • user interface design
  • data design
  • process design
42
Q

discuss phase 4 of the Waterfall method (Development):

A

Build the technical architecture
 Build the database and programs
 Both of these activities are mostly performed by IT
specialists

43
Q

what are the pros of the system development life cycle?

A 
Pros:
 Oldest and most widely used model
 Life cycle concept is very useful
 Still the optimal model when requirements are relatively
certain and not likely to change
44
Q

what are the cons of the system development life cycle?

A

Cons:
 Errors detected late are very costly
 Not very useful when requirements are uncertain
 Many real projects rarely follow a sequential flow
 Often difficult to know all requirements early on
 Customers and users need to be patient
 Developers get delayed, often unnecessarily

45
Q

What is this:

 A model of a proposed product, service, or
system
 An iterative approach to the systems
development lifecycle
 The process of building a model that
demonstrates the features of a proposed
product, service, or system.
A

prototyping

46
Q

what are potential issues with prototyping?

A

 Leads People To Think System Will Come Sooner
Than It Will
 Avoidance In Creating Formal Documentation
 Lack of Testing
 Project Is Often Hard To Terminate
 No Indication of Performance In Operational
Conditions
 Company Resources Not Often Used Efficiently
 Don’t Usually Fit Well With Other Corporate
Systems (stand alones)

47
Q

waterfall vs protyping

A 
Traditional SDLC
 Linear
 Structured
 Rigid
 Slow / Methodical /
Thorough
 First Delivered Is Last
Delivered
Prototyping
 Iterative or Cyclical
 Less Structured
 Flexible
 Fast Initial Delivery
 First Delivered Is
Rarely The Last
Delivered
48
Q

when to use traditional SDLC vs Prototype

A 
Traditional SDLC
 Requirements Well-Known
 Routine Issues
 Risk of Failure Low
 Cost Associated with
Failure is Lower
Prototyping
 Requirements Not WellKnown
 Non-Routine Issues
 Risk of Failure High
 Cost Associated with
Failure is Higher
 When Communication
Problems Exist
 When a Concrete Form is
Needed to Evaluate
49
Q

discuss rapid application development

A

RAD stresses the mechanics of the system
itself and does not emphasize the company’s
strategic business needs

 Might allow less time to develop quality,
consistency, and design standards

MGCR 331 (IS) Final (6 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions