Brainscape's Knowledge GenomeTM

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


See full index

COMP 291 System Design & Analysis > Examen 2 > Flashcards

Examen 2 Flashcards

1
Q

System requirements

A

A characteristic or feature that serves as benchmark to measure the overall acceptability of the finished system.

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

Requirements engineering is composed of three main activities:

A
  1. Gathering requirements: understanding the problem.
  2. Representing requirements: describing the problem.
  3. Validating and verifying requirements: agreeing upon the problem.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Functional Requirement

A

Is a statement of the services a system provides.

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

Non-Functional Requirement

A

Is a statement of operational system constraint. Also known as quality attributed. May be more critical than functional requirements. If they are not satisfied, the system is useless.

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

Gathering Requirements

A

Is the first step in the requirements engineering process. Although software can help gather and analyze requirements, no program gathers them automatically. To obtain answers to these questions, the analyst develops a fact-finding plan.

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

Fact Finding

A

Who, What, Where, When, How, and Why?

  1. Who does it? Why does this person do it? Who should do it?
  2. What is done? Why is it done? What should be done?
  3. Where is it done? Why is it done there? Where should it be done?
  4. When is it done? Why is it done then? When should it be done?
  5. How is it done? Why is it done this way? How should it be done?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Gathering Requirements Through Interviews

A

An interview is a planned meeting during which the analyst obtains information from another person.

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

Interview Steps

A

Step 1 - Determine the people to interview.
Step 2 - Establish objetives for the interview.
Step 3 - Develop interview questions.
Step 4 - Prepare for the interiview.
Step 5 - Conduct the interview.
Step 6 - Document the interview.
Step 7 - Evaluate the interview.

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

Other Fact-Finding Techniques

A
  1. Document Review - Review of baseline documentation. Helps analyst understand how the current system is supposed to work.
  2. Observation - Provides additional perspective and a better undestanding of the system procedures. Should be planned in advanced.
  3. Questionnaires and Surveys - Make sure that the questions collect the right data in a form that can be used to further the fact-finding effort.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Suggestions for designing a questionnaire

A
  1. Keep the questionnaire brief and user-friendly.
  2. Provide clear instructions.
  3. Arrange the questions in a logical order.
  4. Phrase questions to avoid misunderstandings.
  5. Try not to lead the response.
  6. Limit the use of open-ended questions that are difficult to tabulate.
  7. Limit the user of questions that can raise concerns about job security or other negative issues.
  8. Include a section for general comments.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Interviews vs Questionnaires

A

Interview - is more familiar and personal. Costly and time-consuming process.
Questionnaire - gives people the opportunity to provide input and suggestions. Recipients can answer the questions at their convenience.

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

Brainstorming

A

Small group discussion of a specific problem, opportunity, or issue (Structured brainstorming and Unstructured brainstorming).

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

Research

A
  1. The internet, IT magazines, and books to obtain background info, technical material, and news about industry trends and developments.
  2. Attending professional meetings, seminars, and discussions with other IT professionals.
  3. Site visits.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Data Flow Diagrams (DFD)

A

Shows how data moves through an information system but does not show program logic or processing steps. Shows What the system does, NOT How the system does it.

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

DFD Symbols

A

DFD uses four basic symbols that represent processes, data flows, data stores, and entities.

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

Process Symbol (Rectangle w rounded corners)

A

Receives input data and produces output that has different content, form, or both.

17
Q

Data Flow Symbol (Line w single or double arrow head)

A

A path for data to move from one part of the information system to another.

18
Q

Data Store Symbol (Flat rectangle opened on the right side)

A

Represents data that the system stores because one or more processes need to use the data at a later time.

19
Q

Entity Symbol (Rectangle shaded to make it look 3D)

A

Only shows external entities that provide data to the system or receive output from the system.

20
Q

Guidelines for drawing DFDS

A
  1. Draw context diagram to fit in one page.
  2. Use the name of the info system as the process name in the context diagram.
  3. Use unique names within each set of symbols.
  4. Do not cross lines.
  5. Provide a unique name and reference number for each process.
  6. Obtain as much input and feedback as possible.
21
Q

Steps for drawing DFDS

A
  1. Draw Context Diagram - start by placing a single process symbol in the center of the page. To determine which entities and data flows to place, begin by reviewing the system requirements to identify all external data sources and destinations.
  2. Draw Diagram 0 - Provides an overview of all the components that interact to form the overall system.
  3. Draw Lower-Leveled Diagrams - To create lower-level diagrams, leveling and balancing techniques must be used.
22
Q

Data Dictionary

A

Central storehouse of info about the system data. Analyst uses the data dictionary to collect, document, and organize specific facts about the system, including the contents of data flows, data stores, entities, and processes.

23
Q

Traditional Development

A
  1. Compability issues including existing hardware and software platforms and legacy system requirements, influence systems design.
  2. Systems are designed to run on local and wide-area company networks.
  3. Scalability can be affected by network limitations and constraints.
  4. Many applications require substantial desktop computing power and resources.
  5. Security issues usually are less complex than with web-based systems, because the system operates on a private company network, rather than the internet.
24
Q

Web-based Development

A
  1. Web-based systems are easily scalable and can run on multiple hardware environments.
  2. Large firms tend to deploy web-based systems as enterprise-wide software solutions for applications sucha as customers relationship management, order procesing, and materials management.
  3. Web-based software treats the software application as a service that is less dependent on desktop computing power and resources.
  4. When companies acquire web-based software as a service rather than a product they purchase, they can limit in-house involvement and have the vendor install, configure, and maintain the system by paying agreed-upon fees.
  5. Web-based solutions open more complex security issues that should be addressed.
25
Q

Emerging Trends

A
  1. Web 2.0
  2. Cloud Computing
  3. Mobile Devices
26
Q

Developing Software In-House Benefits

A
  1. Satisfy unique business requirements.
  2. Minimize changes in business procedures and policies.
  3. Meet constraints of existing systems.
  4. Meet constraints of existing technology.
  5. Develop internal resources and capabilities.
  6. Satify unique security requirements.
27
Q

Purchasing a Software Package Benefits

A
  1. Lower costs
  2. Requires less time to implement.
  3. Proven reliability and performance benchmarks.
  4. Requires less technical development staff.
  5. Future upgrades provided by the vendor.
  6. Obtain input from other companies.
28
Q

Customizing a Software Package Benefits

A
  1. You can purchase a basic package that vendors will customize to suit your needs.
  2. You can negotiate directly with the software vendor to make enhancements to meet your needs by paying for the changes.
  3. You can purchase the package and make your own modifications, if this is permissible under the terms of the software license.
29
Q

Outsourcing

A

The tranfer of info systems development, operation, or maintenance to an outside firm that provides these services, for a fee, on temporary or long-term basis.

30
Q

Offshoring

A
  1. Offshore outsourcing - global outsourcing
  2. Many firms are sending IT work overseas at an increasing rate.
  3. The main reason for offshore outsourcing is the same as domestic outsourcing: lower bottom-line costs.
  4. Offshore outsourcing, however, involves some unique risks and concerns.
31
Q

Outsourcing issues and concerns

A
  1. Moving IT work overseas raises even more issues, including potential concerns about control, culture, communications, and security.
  2. Before outsourcing, a company must carefully review issues relating to insurance, potential liability, licensing and info ownership, warranties, and disaster recovery.
32
Q

Role of the Systems Analyst

A

When selecting hardware and software, system analysts often work as an evaluation and selection team. The primary objective of the evaluation and selection team is to eliminate sytem alternatives that will not meet requirements, rank the system alternatives that are feasible, and present the viable alternatives to management for a final decision.

33
Q

Software Acquisition Process

A
  1. Step 1 - Evaluate the Info System Requirements.
  2. Step 2 - Identify Potential Vendors or Outsourcing Options.
  3. Step 3 - Evaluate the Alternatives.
  4. Step 4 - Perform Cost-Benefit Analysis.
  5. Step 5 - Prepare a Recommendation.
  6. Step 6 - Implement the Solution.

COMP 291 System Design & Analysis (2 decks)

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