Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

analysis and design > part 2 analysis lec 5 > Flashcards

part 2 analysis lec 5 Flashcards

(39 cards)

Start Studying
1
Q

why the analysis phasa named this

A

because the analysis phase

breaking the whole into parts

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

critical thinking skillls

A

is the ability to recognize strengths and weaknesses and recast an idea in an improved form

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

the finial deliverable of the analysis phase

A

is the system proposal

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

what is the system proposal

A

is pressnted to the approval committee

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

whats is requirments

A

a statment of what the system must do or what characterterstics it needs to have

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

businees reqerments include

A

increase market share
shorten order processing time
reduce customer service costs
lower inventory spoilage

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

IIBA

A

lnternational instiute of businees analysis

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

define function requirements

A

the product capalities or things that a product must do for its users

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

interviews

A

the most commonly used

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

there three types of interview quastaions

A

closed ended quastions
open ended quastions
probing Questions

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

open ended questions

A

are those that leave room for elaboration on the part of interviewee

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

jad

A

join Application development
is information gathering techniqe that allow the project team users and management to work together to identify the requirements for the system

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

quastionnaire

A

is a set of written quastions for obtaining information from individuals

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

what is the types of the requirments

A

Business requirements
User requirements
System requirements

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

Business requirements

A

o what the business needs (recall Ch 1; system request)

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

define the user requirments

Study These Flashcards
A

o what the users need to do

17
Q

What is a System Requirement?

Study These Flashcards
A

QA statement of what the system must do
o “functional requirement”;

or

QA statement of characteristics the system
must have (how the system should be b
18
Q

Functional Requirements

Study These Flashcards
A

Q Specify the support the system will provide
to the user in fulfilling his/her work tasks.

1 Two types:
o A process the system should perform as a part of
supporting a user task, or
© Information the system should provide as the user
performs a task

19
Q

Nonfunctional Requirements

Study These Flashcards
A

Q Behavioral properties the system must have
© Operational — physical and technical operating environment
o Performance — speed, capacity, and reliability needs
o Security —the authority
© Cultural and political — legal requirements, cultural norms

Q Nonfunctional requirements are discussed more in

Chapter 8 (Architecture Design)
o But it is good to collect them early when possible
20
Q

O Requirements definition document

Study These Flashcards
A

© Text document listing requirements in outline form

21
Q

(proposal)

Study These Flashcards
A

Business requirements ave in the system request

22
Q

define interviews and what is the most carsterictis

Study These Flashcards
A

Most important and wost used fact-finding technique

QQ The systems analysts collects information from individuals
face to face

23
Q

Who should be interviewed?

Study These Flashcards
A

Managers in early project stages to get broad understanding

o Staff can provide details and specifics later.

o Political issues are important — may be necessary to interview
influential people, even if they are not too knowledgeable

24
Q

Interview Structure

Study These Flashcards
A

© Top-Down (broad to specific; most common)
o Bottom-up (specific to broad; useful for collecting
details)

25
Question Type
Open-ended — broad concepts; opinions o Closed-ended — learn or confirm facts and details o Probing — resolve confusion; follow-up
26
Interviewing — Practical Tips
Cl Prepare, prepare, prepare! Q Don’t waste the interviewee’s time Q Take notes during and after the interview Q Dow't be afraid to ask for clarification Q Be aware of non-verbal cues (body language) O Send interview summary as soon as possible. Request confirmation and corrections
27
Interview as a Requirements Elicitation | Technique STRENGTHS WEAKNESSES
STRENGTHS WEAKNESSES ° Interviewee can respond freely ° Very time-consuming, and and openly to questions. therefore costly, fact-finding ° Interviewee can be asked for approach. more feedback. ° Success is highly dependent ° Questions can be adapted or on the systems analyst's reworded for each individual. human relations skills. » Interviewee’s nonverbal ° May be impractical due to communication can be peace the location of interviewees.
28
Questionnaires
Special-purpose documents that allow the analyst to collect information and opinions from respondents. o Mass produced and distributed. o Respondents complete the questionnaire on their own time. Q Facts are collected from a large number of people while maintaining uniform responses. o When dealing with a large audience, no other fact-findi
29
Questionnaires, con’t.
Q Fixed -format questions © Similar to a multiple choice exam question o Must be able to anticipate potential answers to questions © Easy to tabulate results QO Free-format questions o Like an essay question — open-ended o Response is unpredictable o Harder to tabulat
30
Questionnaires — Practical Tips
Q To Develop a (Good) Questionnaire o Determine what facts and opinions must be collected and from whom you should get them © Based on the needed facts and opinions, determine whether free- or fixed-format questions will produce the best answers. A mix of types may be ideal. © Pretest the questions on a small sample of “typical” respondents — not just other systems analysts o Understand that response rates are often low.
31
Questionnaires as a Requirements Elicitation Technique STRENGTHS WEAKNESSES
° Most can be answered ° Response is often low. How to quickly (if properly designed). motivate participation? ° Relatively inexpensive. > Tend to be inflexible. ° Allow individuals to maintain ° Body language cannot be observed. anonymity. Cannot clarify a vague or
32
3. JAD — Joint Application Development
An extensive, structured group process Q GOAL: produce complete requirements definition document Q Directly involves project sponsor, key managers, and key users with systems analysts O Requires a trained facilitator and a comfortable facility for long-term, intensive group work Expensive but valuable
33
why it is important Electronic JAD — e-JAD
Q e-JAD helps group overcome group dynamic issues — | dominance, status differences, fear of reprisal
34
JAD as a Requirements Elicitation | Technique
STRENGTHS WEAKNESSES ° Understand wultiple ° Facilitator required perspectives at once. ° Can take valuable time from ° Have user feedback while other work documentation is being ° Coordination required and made group issues arise
35
4. Observation
O Participate in or watch a person perform activities to learn about the system Q Use when the validity of data collected using other methods is in question. Q Use when the complexity of certain aspects of the system prevents end-users from providing a clear explanation
36
Observation as a Requirements | Elicitation Technique
STRENGTHS WEAKNESSES ° Data gathered may be highly ° People may perform differently reliable. when being observed. ° Can see exactly what is being ° Work may vary in difficulty and done. volume. ° Relatively inexpensive ° Some activities may take place a (comer with other fact - odd times. inding techniques). ° The tasks being observed ave subject to various types of interruptions.
37
. Document Analysis
Q Collect Facts from Existing Documentation © Organizational chart © Screens of current system or printout or paper forms © Documentation of previous system studies and designs performed by systems analysts and consultants. QO Analyze Facts to Determine Currency © Even outdated documentation may be useful, but recognize what is current and what is outdated.
38
Document Analysis, con’t.
Q Analyze to Understand the Documentation o Take notes, draw pictures, and use systems analysis and design tools to model what you are learning or proposing for the system. Q To Employ Document Analysis Well... © Learn as much as you can from existing documentation. No one wants to spend time talking about things you could have learned about from existing documentation.
39
Document Analysis as a Requirements | Elicitation Technique
STRENGTHS WEAKNESSES ° Easy to find nonfunctional ° Harder to see process-based requirements functional requirements ° Easy to find information- ° Functions and characteristics based functional of the current system may requirements be different than what is wanted/needed in the new system

analysis and design (8 decks)

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