I Sys 201 Final

Front 1

Occurs when organizations use software that filters content to prevent the transmission of unauthorized information.

Back 1

Content filtering

Front 2

Floods a web site with so many requests for service that is slows down or crashes the site.

Back 2

Denial-of-service attack

Front 3

The good guy hackers that look for weaknesses.

Back 3

White-hat hacker

Front 4

Bad guy hackers.

Back 4

Back-hat hackers

Front 5

Hackers that think they have the right to hack.

Back 5

Hacktivist

Front 6

Attack a computer's system by transmitting a virus hoax, with a real virus attached.

Back 6

Hoaxes

Front 7

A broad term encompassing the protection of information from accidental or intentional misuse by persons inside or outside an organization.

Back 7

Information Security

Front 8

Legitimate users who purposely or accidentally misuse their access to the environment and cause some kind of business-affecting incident.

Back 8

Insider

Front 9

Searches out patterns in information and network traffic to indicate attacks and quickly responds to prevent any harm.

Back 9

Intrusion detection software (IDS)

Front 10

Includes a variety of threats such as viruses, worms, and Trojan horses.

Back 10

Malicious code

Front 11

Altering the contents of packets as they travel over the internet or altering data on computer disks after penetrating a network.

Back 11

Packet Tampering

Front 12

Technique to gain personal information for the purpose of identity theft, usually by means of fraudulent e-mail.

Back 12

Phishing

Front 13

A device that is around the same size as a credit card, containing embedded technologies that can store information and small amounts of software to perform some limited processing.

Back 13

Smart card

Front 14

A program or device that can monitor data traveling over a network

Back 14

Sniffer

Front 15

Using one's social skills to trick people into revealing access credentials or other information valuable to the attacker.

Back 15

Social Engineering

Front 16

The forging of the return address on an e-mail so that the e-mail message appears to come from someone other than the actual sender.

Back 16

Spoofing

Front 17

Benchmarks for systems success in SDLC.

Back 17

1.Guaranteed Performance
2. Development Costs
3. Scalability

Front 18

Sequential, activity based process in which each phase in SDLC is performed sequentially from planning through implementation and maintenance.

Back 18

Waterfall

Front 19

Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a a system to accelerate the systems development process.

Back 19

Rapid Application Development (RAD)

Front 20

Breaks a project into tiny phases, and developers cannot continue on to the next phase until the first phase is complete

Back 20

Extreme programming (XP)

Front 21

A form of XP, aims for customer satisfaction through early and continuous delivery of uesful software components. Fast and efficient, small and nimble.

Back 21

Agile

Front 22

A framework of best practice approaches intended to facilitate the delivery of high quality IT services. Important in the Agile Methodology.

Back 22

Role of ITIL

Front 23

Agile Principles

Back 23

o Slash the Budget (causes focus on essentials)
o If it Doesn't Work, Kill it (get rid of unnecessary products/systems that aren't doing the job)
o Keep Requirements to a Minimum (Only develop necessary features. Scope creep - increase of the scope of a project. Feature Creep - feature list growth.)
o Test and Deliver Frequently (add working pieces frequently - each week or month)
o Assign non-IT Executives to Software Projects (gives Exec's a feeling of ownership and desire to succeed.)

Front 24

Project Management Applied to SDLC

Back 24

Application of knowledge, skills, tools, and techniques to meet or exceed needs and expectations

Front 25

Feasibility Factors

Back 25

1. Technical - can we build and integrate this
2. Economical - financial benefits and costs
3. Legal - examines legal ramifications
4. Operational - will it attain desired objectives
5. Scheduling - is it in an appropriate timeframe, will completion date be met
6. ethics - does it match company ethics

Front 26

Implementation (construction) tasks and strategies

Back 26

see http://docs.google.com/Doc?docid=0AQiifrdRwm9qZGZnZjhyejdfNWd2a3BxcWY4&hl=en&pli=1

Front 27

Project Plan needs

Back 27

Easy to understand and read, communicated to key stakeholders, appropriate for project (size, complexity, etc), and prepared by the whole team. Managers must manage people, make sure the plan is understandable, and increase by-in from stakeholders.

Front 28

Process of proactive and ongoing identification, analysis, and response to risk factors. Done during plan creation. Identification, quantitative analysis, qualitative analysis, response planning.

Back 28

Risk Management

Front 29

Risk Mitigation

Back 29

promote project leadership skills, learn from previous experience, share knowledge, create project management culture

Front 30

Sequential, activity based process in which each phase in SDLC is performed sequentially from planning through implementation and maintenance

Back 30

Waterfall

Front 31

Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a a system to accelerate the systems development process

Back 31

Rapid Application Development (RAD)

Front 32

Breaks a project into tiny phases, and developers cannot continue on to the next phase until the first phase is complete.

Back 32

Extreme programming (XP)

Front 33

A form of XP, aims for customer satisfaction through early and continuous delivery of useful software components. Fast and efficient, small and nimble.

Back 33

Agile

Front 34

A framework of best practice approaches intended to facilitate the delivery of high quality IT services. Important in the Agile Methodology.

Back 34

ITIL

Front 35

Agile Principles

Back 35

-Slash the Budget (causes focus on essentials)
-If it Doesn't Work, Kill it (get rid of unnecessary products/systems that aren't doing the job)
-Keep Requirements to a Minimum (Only develop necessary features. Scope creep - increase of the scope of a project. Feature Creep - feature list growth.)
-Test and Deliver Frequently (add working pieces frequently - each week or month)
-Assign non-IT Executives to Software Projects (gives Exec's a feeling of ownership and desire to succeed.)

Front 36

Application of knowledge, skills, tools, and techniques to meet or exceed needs and expectations

Back 36

Project Management Applied to SDLC

Front 37

Discard old system and jump into the new system (Something could go horribly wrong)

Back 37

Direct/Plunge Conversion

Front 38

Use both systems till the new one is obviously working well. (Extra effort required by employees)

Back 38

Parallel conversion

Front 39

Implement phases of the system until it is apparent that the new one works well (Lots of time to implement, also problems can arise in syncing systems.)

Back 39

Phased Conversion

Front 40

Have a small number of people use the new system until it is proven to work well (somewhat the same as above)

Back 40

Pilot Conversion

Front 41

Determines whether a system satisfies its acceptance criteria, enabling the customer to decide whether or not to accept the system

Back 41

Acceptance testing

Front 42

Process of proactive and ongoing identification, analysis, and response to risk factors. Done during plan creation. Identification, quantitative analysis, qualitative analysis, response planning.

Back 42

Risk Management

Front 43

Promote project leadership skills, learn from previous experience, share knowledge, create project management culture

Back 43

Risk Mitigation

Front 44

Collaborative webpages that allow users to edit documents, share ideas, or monitor the status of a project

Back 44

Business wikis

Front 45

An IT based set of tools that supports the work of teams by facilitating the sharing and flow of information

Back 45

Collaboration system

Front 46

Provides tools to manage the creation, storage, editing, and publication of information in a collaborative environment

Back 46

Content management system

Front 47

An organization's key strength or business function that it does better than any of its competitors

Back 47

Core competency

Front 48

Similar to document management, generally works with binary rather than text files, such as multimedia file types

Back 48

Digital asset management system

Front 49

Organizations that cannot adapt to the new demand placed on them for surviving in the information age are doomed to extinction

Back 49

Digital Darwinism

Front 50

When those with access to technology have great advantages over those without access to technology

Back 50

Digital divide

Front 51

A new way of doing things that initially does not meet the needs of existing customers

Back 51

Disruptive technology

Front 52

Supports the electronic capturing, storage, distribution, archival and accessing of documents

Back 52

Document management system

Front 53

Global public network of computer networks that pass information from one to another using common computer protocols

Back 53

Internet

Front 54

Problem solving done by an expert and a novice

Back 54

Joint problem solving

Front 55

involves capturing, classifying, Evaluating, retrieving and sharing information assets in a way that provides context for effective decisions and actions

Back 55

Knowledge management

Front 56

Involves shared participation in business processes such as workflow in which knowledge is hardcoded as rules

Back 56

Process collaboration

Front 57

Standards that specify the format of data as well as the rules to be followed during transmission

Back 57

Protocols