Brainscape's Knowledge GenomeTM

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


See full index

MiS 374 > All > Flashcards

All Flashcards

1
Q

What is the flow of documentation?

A

SRR->As-Is Models->Root Cause->To Be Models -> UserStories (functional & non functional Reqs)->Tasks (ADCRD)-> Gantt Chart

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

What is the 2X2 grid for different kinds of stakeholders

A

Managerial/Executive & Operational By Internal & External

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

What role should always be a stakeholder?

A

Tech support (or whoever is going to maintain the system

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

What is the key term for SRR?

A

COMPLETENESS - you want all in favor & all opposed, everyone using reports generated

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

What is a good doc to start the SRR from?

A

An org chart. You want all names, roles & contact info

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

What are the 2 tables that are in an SRR

A

User Community & Development Community

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

What are the 4 squares of an empathy map?

A

Said, Did, Thought, Felt.

Try to use these to synthesize needs & then from needs, get insights

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

Who should go in the users table of the SRR?

A

Anyone affected by the project directly or indirectly.

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

In the SRR template, what is the difference between the Responsibity/Function column and the Comm Objective/Message column

A

The responsibility/function column is their current role in the org and if they have a role that is already specified for the project (ex: main contact, final approval, etc). The Comm Objective/Message is what you want to accomplish when project leaders talk to this person (ex: convince them of the project’s worth or gather info/wants)

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

Who should be in the development community table of the SRR?

A

The project team members & professor & anyone in the org that will be maintining/building the system

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

What are the 2 key ways to communicate effectively?

A

1) Consider the perspective of the audience when deciding content, format, feedback (you’re trying to sell them on an idea)
2) Make a communication plan grid (columns include audience, comm. obj., message, channel, Timing)

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

What is the purpose of an empathy map?

A

To thoroughly understand the user

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

90% of conflict in a project is due to ___

A

miscommunication

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

85% of projects cite ____ as a reason for failure.

A

lack of acceptance

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

What is the hardest part of the Information system to change?

A

Process and people. Hardware & software are easy

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

What is the test for if someone is a stakeholder?

A

“Are they affected by the system?”

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

How should you make an empathy map?

A

as a group; collectively

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

What is a key part of the communication plan?

A

an escalation plan (for when a stakeholder doesn’t respond)

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

What are some symbols for As-Is and To-Be Business Process Flow models?

A

Solid dot is a start state, A circled dot is a stop state, Activities are in bubbles, Diamonds are decision points, arrows are transitions, Conditions are in [] and should be put in arrows coming out of a decision point, a fat line is a synchronization bar, can use swimlanes

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

What are swimlanes for?

A

They day who is doing a given piece of work in a business process flow model

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

What is the problem chain in a root cause analysis?

A

the series of symptoms that eventually leads to the root cause

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

What do you do once you have found the root cause in a root cause analysis?

A

1) Define the system objectives and measureable perf. criteria
2) Identify internal/external roadblocks/constraints
3) Identify pain points of the management triple constraint

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

What is the point of a root cause analysis?

A

Keeps your from chasing down falase causees & results in a recommendation for a project solution

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

Each symptom should ahve at least one corresponding problem in the problem chain

A

True

25
Q

What is the rough flow of the root cause analysis?

A

Identify symptoms, Develop a problem chain, ID the problem, (Id The management triple constraint, objectives & perf criteria), and develop the final solution

26
Q

Where should you make sure to document all assumptions?

A

Document assumptions in the root cause analysis. Step into the clients shoes

27
Q

What is and is not the main prupose of a DFD

A

the data is the main purpose. The business process is not.

28
Q

What are the 4 key symbols for the DFD?

rectangle

A

a rectangle is an environmental entity or an external entity (a destination for or source of data that resides outside the system but not necessisarily outside the stakeholders)

29
Q

What are the 4 key symbols for the DFD?

arrow

A

an arrow is a dataflow. All of these should be uniquely labeled

30
Q

What are the 4 key symbols for the DFD?

Bubble rectangle

A

a process bubble a process that changes the data, label goes in center, ID goes in top, Actor goes on bottom, should be in verb-object format

31
Q

What are the 4 key symbols for the DFD?

3/4 closed rectangle

A

a 3/4 closed rectangle is a data store. Should have the ID sectioned off at the end and the label in the center. You can repeat the occurances of these on the diagram to make it less cluttered

32
Q

What is a context diagram?

A

The simplest DFD that only shows the external entities, their data flows to & from the system and a circle representing the system itself

33
Q

What is a figure 0 diagram

A

its one level more granular than the context diagram. It breaks up the system into processes (but no more than 7)

34
Q

What is a figure N diagram?

A

It is a zoomed in view of one of the processes. If you zoom in on process 2 and its the first level more granular, its a Level 1 (Figure 2) DFD.

35
Q

What are the 7 rules of DFDs

A

1) Inputs to processes are always different from outputs (processes should always transform the data)
2) Objects are consistently and uniquely named
3) Never have a process without an input or an output
4) Always have verb-object name for processes
5) Data is always a noun
6) Should not move data from store->entity or store-> store without a process
7) Arrows only go one way

36
Q

What are 5 Modeling Tips

A

1) Title the sketch
2) Combine the simple shapes
3) Express emotion or state
4) Label each noun
5) Arrows represent relationships

37
Q

What is the form a user story should take

A

As a , I want so that

It’s a thin vertical slice of functionality

38
Q

How long should a user story take?

A

1-2 weeks

Fit on a notecard

39
Q

Who turns the user stories into the functional requirements?

A

The dev team; should address backbone requirements to implement the functionality

40
Q

Why do functional requirements exist?

A

They allow you to break up tasks so different dev team members can work simultaneously

41
Q

What does a functioanl requirements table consist of?

What is its purpose?

A

The user story is on the left and the Must have, Should have , Could have, Wont have (MOSCOW) categories hold the functional requirements.

It makes sure you & client are on the same page with scope

42
Q

What are some things that functional requirements can relate to?

A

Tasks to build, to design, to define requirements, to test

43
Q

How many functional requirements should be associated with each user story?

A

3-10

44
Q

What is the point of an Organizational Impact Analysis

A

It analyzes how the project plays into the firm’s business strategy (competitive advantage), improves managers decision making, and improves operations

Helps to set reasonable expectations for the impact given the scope, schedule, and resources & and adjust if needed

45
Q

What does an Org Impact Analysis Look like?

A

Has Strategy, Management, and Operations sections. All three have a short paragraph addressing the heading and then lists key high level requirements and their priorities.

This is how you prove you’re adding value

46
Q

What are some kinds of non functional requirements?

A

maintainance, portability, scalability, security

Everything that is needed beyond it simply working

47
Q

What does a non functional requirements table look like?

A

It has sections for Maintainability, portability, scalability, and security. All of these have a short paragraph on the overall status and then lists requirements and priority levels for each

48
Q

What is the management triple constraint?

A

Time, Cost, Scope. They all trade off with each other

49
Q

What are the steps of teh inception phase?

A

SRR, As IS Models, Root cause, User Stories, Func & Non Func reqs, Scope priorities, To Be Model, Communication plan, GANTT CHART

50
Q

What are sprints and what phases to they use?

A

They are short pieces of work. Use the Analyze, Design, Construct, Review, Deploy to break the user stories into categorized tasks

51
Q

How do you decide which user stories to pick if your scope is too big?

A

Plot on a feasability & value scale & only take the ones high in both

52
Q

When shoudl you generate documentation?

A

as you go in the deploy section and make a rough outline in the development section

53
Q

What are the 5 categories of risk?

A

1) Characteristics of the org
2) Characteristics of the info system
3) Characteristics of system developers (project team & the ongoing team)
4) Characteristics of internal users
5) Characteristics of external users

54
Q

What document should you use to reduce the risk?

A

The risk evaluation grid (has questions relating to each of the areas and you give a ranking -1->1

The Risk Risk Reduction Strategies Grid (has a row for each category & space for you to list specific & practical reduction strategies)

55
Q

What is risk proportional to?

A

Scope

56
Q

What are some details about the project manager role?

A

Makes sure tasks are completed on schedule, Monitor the management triple constraint, Big picture view

57
Q

What are some details about the Business Analyst role?

A

Really invloved in inception and requirements gathering. Solve client needs
Lead testing

58
Q

What are some details about the developer role?

A

Technical lead, managed deployment, researches the right technology platform

MiS 374 (1 decks)

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