Larson on Domain Model

1
Larson on Domain Model

• vs. Class Model

2
Software Crisis

• Software is generally
• Behind schedule
• Over cost
• Defective
• Incorrect (not what the user wanted)

3
(No Transcript)
4
(No Transcript)
5
(No Transcript)
6
(No Transcript)
7
(No Transcript)
8
(No Transcript)
9
SDLC
10
Not far reaching enough . . .

• Systems analysts deliver processes, not value.

11
IS Investment Failures

• Technical Failure
• Data Failure
• User Failure
• Organizational Failure
• Failure in the Business Environment

12
Outputs of the Analysis Phase

• The Domain Model
• The Class Model
• Activity Diagrams

13
Craig Larman

• Typically the output of the Analysis Phase is the
  Class Model, (PDD)
• The Class Model is a UML artifact used to
  model the software about to be developed
• Larman suggests the Domain Model, (SAD)
• The Domain Model looks like the Class Model
  but is used to model the business processes to be
  supported
• Some suggest including Activity Diagrams, (PDD)

Craig Larman, 2002, Applying UML and Patterns,
Prentice Hall, New Jersey
14
Inputs of the Analysis Phase

• Gather facts about the business system to be
  supported
• Gather facts about the desired information system
• Gather facts about the users of the system

15
Fact-finding Methods

• Research and site visits
• Existing documentation
• Observation
• Questionnaires
• Interviews