11/11 Class Flashcards

1
Q

cycle

A

risks and assertions

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

controls

A

we need them

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

periodic method

A

we had to do some closing entries

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

closing entries for closing out the month and year

A

allow for doubtful, income summary/temporary accounts,

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

controls

A

we need them

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

systems development life cycle

A
  1. What does management want?
  2. Then they hire good people
  3. In IT we need to control those guys,
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

steering committee

A

made up of CTO, accounting, and other people that will look at the IT department and what they do to funnel it and make things better. We need to see if we have the money or the time to do things. Rate of return

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

programmers

A

tweak the code

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

IT governance

A

decides who accesses what

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

database administrators

A

people who maintain an application and mapping it.

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

security professionals

A

chief security officers people who look for hackers and other security threats

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

Rule 1

A

segregation of duties - we have to have different people doing different things in IT

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

list of people

A

system administrators, programmers, isolate programmers into the programming cycle and don’t let them into the real environment

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

System development lifecycle

A

give them a budget tell them what it should look like and follow them along the way
we build it or we buy it

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

phases of system development lifecycle

A

planning - decide what we want
analysis - do an analysis of our current situation, find out how it is working and what the problems are. Then we see what the users want and make if functional with our companies
design - when we put it on paper and then the administrators and programmers make it, we have to make it user friendly, verify it aligns with the company strategy
implementation - putting the system in
maintenance

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

BPR business process reengineering

A

we look at a process and see how to make it better

17
Q

RFP Request for proposal

A

we find someone who finds what the options are out there and then find out who can do it, if we can’t find someone then we build it.

18
Q

Feasibility study

A

can we do this?

19
Q

parallel

A

doing both systems at the same time

20
Q

direct cutover, big bang theory,

A

you stop the old system and start the new one

21
Q

phase in

A

do it one system at a time to find any errors

22
Q

pilot

A

when you have only one area test it and find if it works

23
Q

scrubbing data

A

getting the data ready for the new system

24
Q

change management

A

one person does each thing