SA500 Foundations of Systems Analysis Flashcards

0
Q
  1. Name several key factors identified in the Standish Group studies that caused IT projects to be challenged.
A

The top three factors leading to challenged projects were:

1) lack of user input
2) incomplete requirements
3) changing requirements

SA500 slide 8

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
1
Q
  1. What did the Standish Group studies find out about IT success rates?
A

The success rates ranged from 16% to 32%.

SA500 slides 6 and 7

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q
  1. Give the most compelling reason that analysis is so important.
A

Because a great solution to the wrong problem is not worth much.

SA500 slide 13

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q
  1. How does the cost to correct errors made during analysis depend on the phase in which the error was detected?
A

The costs grows exponentially the later the error is discovered.

SA500 slide 14

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q
  1. What is the main reason that the cost to fix requirements errors rises exponentially with the time to their discovery?
A

The high cost and complexity of rework in software.

SA500 slide 14

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q
  1. Name the 7 different categories of requirements.
A
  1. Business requirements
  2. User requirements
  3. Functional requirements
  4. Business rules
  5. Quality attributes
  6. External/internal interfaces
  7. Design/implementation constraints

SA500 slide 18 and 26

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q
  1. How are business requirements related to user requirements?
A

Business requirements are the primary driver for user requirements. The user requirements should ensure that the business requirements are being met.

SA500 slides 18 and 26

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

8.What are functional requirements?

A

Functional requirements describe what the developer is supposed to build.

SA500 slide 21

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q
  1. Business rules are not considered requirements per se, so how are they related to requirements?
A

Business rules are not considered requirements per se, but they must often be implemented and enforced by software.

SA500 slide 22

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q
  1. What is the best way to specify human user interfaces?
A

Prototyping is one of the best ways specify human user interfaces.

SA500 slides 24 and 37

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

What is a software development cycle? Compare this to a methodology.

A
  1. A software development life cycle is an organized high-level approach or framework. For building software systems to solve business problems. Methodologies are sets of tools and techniques that implement life cycles. There may be different methodologies with a given life cycle model.

SA500 slides 29 and 30.

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