1111111C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi1202127000000269300000013210247682694000000212700000010000002127000000269300000010.0000001.000000244786512205004912Structured Analysis Diagram Progression (3 of 3)1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi110202100000021270000001321024768269400000020210000005670000002021000000212700000010.0000001.000000244786512205004911Event Diagram (more complex)1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi100190000000020210000001321024768269400000019000000006730000001900000000202100000010.0000001.000000244786512205004910SoundStage Partial Event Decomposition Diagram1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi90177600000019000000001321024768269400000017760000007940000001776000000190000000010.0000001.00000024478651220500499SoundStage Partial Use Case List1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi80161100000017760000001321024768269400000016110000009180000001611000000177600000010.0000001.00000024478651220500498Structured Analysis Diagram Progression (2 of 3)1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi701491000000161100000013210247682694000000149100000010830000001491000000161100000010.0000001.00000024478651220500497SoundStage Functional Decomposition Diagram1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi601279000000149100000013210247682694000000127900000012030000001279000000149100000010.0000001.00000024478651220500496SoundStage Context DFD1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi501142000000127900000013210247682694000000114200000014150000001142000000127900000010.0000001.00000024478651220500495Structured Analysis Diagram Progression (1 of 3)1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi409750000001142000000132102476826940000009750000001552000000975000000114200000010.0000001.00000024478651220500494Modern Structured Analysis (More Commonly Practiced)1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi3072400000097500000013210247682694000000724000000171900000072400000097500000010.0000001.00000024478651220500493When to Draw Process Models1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi2047800000072400000013210247682694000000478000000197000000047800000072400000010.0000001.00000024478651220500492Types of Logical Processes1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi1022100000047800000013210247682694000000221000000221600000022100000047800000010.0000001.00000024478651220500491Differences Between DFDs and Flowcharts1C:\Documents and Settings\james\My Documents\millerjwcom\dom\gbis722online\week4\Chap09aSummary\Chap09aSummary.avi0002210000001321024768269400000002473000000022100000010.0000001.00000024478651220500490Models: Logical and Physical100x000003E9Models: Logical and Physical1002210000000x000003EADifferences Between DFDs and Flowcharts1014780000000x000003EBTypes of Logical Processes1027240000000x000003ECWhen to Draw Process Models1039750000000x000003EDModern Structured Analysis (More Commonly Practiced)10411420000000x000003EEStructured Analysis Diagram Progression (1 of 3)10512790000000x000003EFSoundStage Context DFD10614910000000x000003F0SoundStage Functional Decomposition Diagram10716110000000x000003F1Structured Analysis Diagram Progression (2 of 3)10817760000000x000003F2SoundStage Partial Use Case List10919000000000x000003F3SoundStage Partial Event Decomposition Diagram101020210000000x000003F4Event Diagram (more complex)101121270000000x000003F5Structured Analysis Diagram Progression (3 of 3)101232000
Teaching Notes
In some books, the term logical is called a conceptual or
Teaching NotesIn some books, the term logical is called a conceptual or
essential. The term essential comes from the notion that the model represents the “essence”
essential. The term essential comes from the notion that the model represents the “essence”
of the system.
For database-oriented instructors, the term logical
of the system.For database-oriented instructors, the term logical
in the world of systems analysis is NOT equivalent to the term logical in the world
in the world of systems analysis is NOT equivalent to the term logical in the world
of database. In the database world, a “logical schema” is already constrained by the
of database. In the database world, a “logical schema” is already constrained by the
choice of a database technology, which runs contrary to the systems analysis
choice of a database technology, which runs contrary to the systems analysis
expectation that a logical model is technology-independent.
expectation that a logical model is technology-independent.
In some books, the term physical is called implementation or technical.
In some books, the term physical is called implementation or technical.
Emphasize that there are nearly always multiple technical solutions for any given set of
Emphasize that there are nearly always multiple technical solutions for any given set of
business requirements. In most projects, there is one logical model that represents the
business requirements. In most projects, there is one logical model that represents the
mandatory and desirable business requirements, regardless of how those requirements might be implemented. On the other hand, given that one logical model, there are multiple candidate physical models that could represent alternative, technical implementations that could fulfill the business requirements (although analysts rarely draw more than one or two of those physical models).
mandatory and desirable business requirements, regardless of how those requirements might be
No additional notes
No additional notes
No additional notes
No additional notes
Teaching Notes
This is a context slide only. In this chapter, our
Teaching NotesThis is a context slide only. In this chapter, our
demonstration of DFDs is exclusively for “systems analysis,” specifically
demonstration of DFDs is exclusively for “systems analysis,” specifically
“requirements modeling.”
“requirements modeling.”
Teaching Notes
Although this process may not be as familiar to some adopters as
Teaching NotesAlthough this process may not be as familiar to some adopters as
the top-down, fully leveled, classical “physical-logical-logical-physi
the top-down, fully leveled, classical “physical-logical-logical-physi
cal” approach in the 1976 DeMarco methodology, this is the more contemporary approach
cal” approach in the 1976 DeMarco methodology, this is the more contemporary approach
and is taught in our book. The original approach is rarely, if ever, practiced because it is so
and is taught in our book. The original approach is rarely, if ever, practiced because it is so
labor intensive and time consuming.
labor intensive and time consuming.
Teaching Notes
The numbers in red correspond to the numbers on the previous
Teaching NotesThe numbers in red correspond to the numbers on the previous
slide.
slide.
Teaching Notes
Emphasize that a context DFD does not have to show every net
Teaching NotesEmphasize that a context DFD does not have to show every net
data flow. For most systems, that would overwhelm the reader. Trivial or less common
data flow. For most systems, that would overwhelm the reader. Trivial or less common
flows can be omitted until later diagrams, and composite data flows can be created to
flows can be omitted until later diagrams, and composite data flows can be created to
combine multiple flows. As a result, and in the strictest sense, not all primitive data
combine multiple flows. As a result, and in the strictest sense, not all primitive data
flows may “balance” up to the context DFD, but we sacrifice that balancing to improve
flows may “balance” up to the context DFD, but we sacrifice that balancing to improve
readability and validation. All data flows on the context DFD will balance down to the
readability and validation. All data flows on the context DFD will balance down to the
lower-level DFDs (although composite data flows will be replaced by their separate
lower-level DFDs (although composite data flows will be replaced by their separate
component data flows).
component data flows).
No additional notes.
No additional notes.
Teaching Notes
The numbers in red correspond to the numbers on the slide 33.
Teaching NotesThe numbers in red correspond to the numbers on the slide 33.
Teaching Notes
Walk through this so that students understand what goes
Teaching NotesWalk through this so that students understand what goes
in a use case list for DFDs.
This is an abbreviated list from what is shown in the text.
in a use case list for DFDs.This is an abbreviated list from what is shown in the text.
Teaching Notes
Most event decomposition diagrams will require multiple
Teaching NotesMost event decomposition diagrams will require multiple
pages (or one very large plotter-style page) because most systems are required to
pages (or one very large plotter-style page) because most systems are required to
respond to many events (possibly dozens or hundreds).
respond to many events (possibly dozens or hundreds).
No additional notes.
No additional notes.
Teaching Notes
The numbers in red correspond to the numbers on the slide 33.
Teaching NotesThe numbers in red correspond to the numbers on the slide 33.