Brainscape's Knowledge GenomeTM

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


See full index

Systems analysis 1 > Chapter 4 / 5 > Flashcards

Chapter 4 / 5 Flashcards

0
Q

Rapid application development:

A

Team-based technique that speeds up information systems development and produces a functioning information system.

(JAD only a requirements model, RAD does that as well as actually make the product)

Cons: stresses the mechanics of system itself, does not emphasize the company’s business needs. Short time might produce a product of less quality, and consistency. Overall risky

Pros: develops product quickly with significant cost savings.

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

Joint application development:

A

User-oriented technique for fact-finding and requirements modeling.

(Involves users more.)

Cons:
More expensive and can be cumbersome if too many people involved.

Pros:
more accurate statement of requirements, better understanding of goals, stronger commitment to the success of new system.

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

Agile Method:

A

Attempt to develop a system incrementally, but building a series of prototypes and constantly adjusting them to user requirements. Uses continuous feedback.

Pros: flexible and efficient with change. Stress team interaction and community based values.
Frequent ‘final products’ validate the product and reduce risk.

Cons: high level technical and interpersonal skills. Lack of structure and documentation can leak to risk factors. Project can change significantly over time due to changing user requirements.

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

Functional Decomposition Diagram (FDD):

A

Top-down representation of a function or process. Shows business functions and breaks them down from top to bottom.

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

Business process modeling (BPM):

A

Describes one or more business processes; (such as handling an airline reservation, filing a product order, updating a customer account.)

Uses a standard language: Business process modeling notation (BPMN)

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

Scrum:

A

Type of agile development method, derived from the rugby term scrum, involves intense interaction but more mental than physical.

(Pigs and chickens)

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

Data Flow Diagrams:

A

Show how a system stores, processes and transforms data but does not show program logic or processing steps. What, not how.

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

Unified modeling language (UML):

A

Widely used method of visualizing and documenting software systems design. Uses object oriented design concepts but independent of a specific programming language. (Pseudo code)

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

Use-Case Diagram

A

Visually represents the interaction between users and the information system. User becomes an “actor” with a specific role showing how he/she interacts with the system.

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

Sequence diagrams:

A

Shows the timing of interactions between objects as the occur.

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

Systems requirement:

A

Characteristic or feature that must be included in an info. System to satisfy business requirements and its users.

Fall into 5 categories:

  1. outputs
  2. inputs
  3. Processes
  4. performance
  5. controls
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Examples of output, system requirement:

A
  • the website must report online volume statistics every 4 hours, and hourly during peak periods.
  • the contact management system must generate a daily reminder list for all sales reps.
  • the purchasing system must provide suppliers with up-to-date specifications
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Examples of input, system requirements.

A
  • the department head must enter overtime hours on a separate screen.
  • student grades must be entered on machine-scannable forms prepares by the instructor.
  • each input form must include date,time, product code, customer number, and quantity.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Examples of process, system requirements:

A
  • the student records system must calculate the GOA at the end of each semester. (Key word calculate)
  • the human resources system must interface properly with the existing payroll system.
  • The video rental system must not execute new rental transactions for customers who have overdue videos.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Examples of performance, system requirements.

A
  • the system must support 25 users online simultaneously.
  • response time must not exceed 4 seconds.
  • the student records system must produce class lists within five hours after the end of registration.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Examples of control, system requirements.

A
  • system must provide log-on security at the operating system level and at the application level.
  • system must maintain separate levels of security for users and the system administrator
  • all transactions must have audit trails
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Scalability:

A

the systems ability to handle increased traffic (business volume/transactions).

17
Q

Deliverable:

A

Something that is physically given, that shows progress. Could be a prototype.

18
Q

Fact finding involves 5 questions. And in each of these questions you must also ask ‘why.’

A
  1. Who? Who performs the procedures in the system. Why? Are the the correct people? Could other people do it?
  2. What? What is being done? Why? Why is that process necessary.
  3. Where? Where the operations are being performed? Why? Where could they be performed? Where could they be performed more efficiently.
  4. When? When is a procedure performed? Why Is is performed in that manner?
  5. How? How Is a procedure performed? Why is it performed in that manner?
19
Q

Interviews. (everything about them.)

A

Planned meet to obtain info from someone.

Seven general steps for an interview:

  1. determine people to interview
    - informal structure: some people have more influence or knowledge in a company than appears on an organization chart.
  2. Establish objectives for interview
    - find general areas, then specify certain facts you want.
  3. Develop questions
    - Avoid “leading questions” that suggest/favor a particular reply.
  4. Prepare for interview
  • pick a place, let interviewee know how long it’ll last.
  • let interviewee know of questions/documents before interview via email
  • neutral location or interviewees office
  1. Conduct the interview
  • make interviewee feel at least
  • engaged listening (notice verbal and non verbal communication)
  • summarize and seek confirmation at end of interview of your understanding of the discussion.
    6. Document interview
  • take notes and record information directly after interview.
  • tape recorders are effective but make interviewee uneasy.
  1. Evaluate the interview
    - identify biases.
20
Q

Document review (fact finding technique)

A

Helps one understand how the current system is supposed to work by analyzing forms and operating documents currently in use.

21
Q

Observation (fact finding technique)

A

Actual observation of the system in action to gain a better understanding of it.

22
Q

Types of interview questions:

A

-Open ended:
encourage spontaneous and unstructured responses. Better to understand s larger process and draw the interviewees opinions/suggestions.

-closed ended:
Limit the response. Used to find specific info. Or to verify facts

-range-of-response:
Closed-ended questions that ask the person to evaluate something by providing limited answers to specific responses or on a numeric scale. (1-10)

23
Q

Total Cost of Ownership (TCO):

A

Costs, both indirect and direct that apply to making/running an information system.

24
Q

Hawthorne Effect:

A

Productivity improves during observation whether working conditions were better or worse.

25
Q

Data Flow Diagram Symbols:

A

-we use Gane and Sarson symbol set (other is Yourdon).

-process symbol:
receives input and procedures output that has different content, form, or both. (Rectangle with rounded corners)

-data flow symbol:
Path from data to move from one part of info. system to another. (Arrow)

  • data store symbol: used to represent data that the system stores because one or more processes need to use the data at a later time. (Flat rectangle that is open on right ride, closed on left)
  • entity symbol: person/thing (BANK, CUSTOMER, PAYROLL DEPARTMENT) that does some action. (Rectangle with shading to make it appear to be 3D)

-

26
Q

Spontaneous generation:

A

Produces output with no input data flow.

27
Q

Black hole:

A

Process that has input but produces no output.

28
Q

Grey hole:

A

Has at least one input and one output but he input is insufficient to generate the shown output.

29
Q

Context diagram:

A

Top-level view of an information system that shows the system’s boundaries and scope. (Central process is Process 0)

30
Q

Diagram 0 (level 0)

A

“Zooms in” on the system and shows major internal processes, data flows and stores. More specific.

31
Q

Functional primitive:

A

Process that consists of a single function that is not exploded further.

32
Q

Leveling:

A

Process of drawing a series of increasingly detailed diagrams.

I assume this is where level 0 and level 1 come into play

33
Q

Data dictionary (data repository):

A

Central storehouse of information about the system’s data. Used to collect, document, and organize facts about a system.

34
Q

Data element (data item or field):

A

Smallest piece of data that has meaning within an information system.

35
Q

Records (data structures):

A

A meaningful combination of related data elements that is included in a data flow of retained in a data store.

36
Q

Three logical structures (control structures) that make up modular design:

A

Sequence: competition of steps in sequential order.

Selection: completion of two or more process steps based upon the results of a test or condition. (If conditions are met, do this)

Iteration: the completion of a process step that is repeated until a specific condition changes.

37
Q

Structured English:

A

Subset of the standard English that describes logical processes clearly and accurately. Resembles pseudocode.

38
Q

Correct/incorrect uses of data flows;

A

Process ↔️ Process: ✅

Process ↔️ Entity: ✅

Process ↔️ Data Store: ✅

Entity ↔️ Entity: ❌

Entity ↔️ Data Store: ❌

Data Store ↔️ Data Store: ❌

39
Q

Decision Table:

A

Logical structure that shows every combination of conditions and outcomes.

If this, then this.

40
Q

Decision Trees:

A

Graphical representation of conditions, actions, and rules found in a decision table.

If this, then this.

41
Q

Balancing:

A

Ensures that input and output data flows align properly. Ensures that data flows of the parent DFD are maintained on the child (lower level) DFD.

Systems analysis 1 (2 decks)

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