YOURDON Systems Method: Model-driven Systems DevelopmentThe method described here draws upon twenty years of experience of YOURDON, Inc., whose business has been applying, adapting, and enhancing system development techniques. This intuitive, model-driven approach to systems development is suitable for both the business information and real-time engineering communities. YOURDON Systems Method (YSM) 3.0 has guided thousands of project teams and individuals, helping them meet tight project deadlines while satisfying user requirements and delivering successful solutions within budget. |
From inside the book
Results 1-3 of 69
Page 165
... terminators they will only be available to the system when the terminator is active ; when the terminator is not active , the flow will not be available . Generally speaking , the system cannot control the periods of time at which the ...
... terminators they will only be available to the system when the terminator is active ; when the terminator is not active , the flow will not be available . Generally speaking , the system cannot control the periods of time at which the ...
Page 169
... Terminators show a potential role , rather than individual instances . Thus the terminator " Attending Physician " is used , rather than " Dr Smith " . Terminators are often entities ( see §2.2.3.3 ) . Events ( see §2.22 and §2.23 ) ...
... Terminators show a potential role , rather than individual instances . Thus the terminator " Attending Physician " is used , rather than " Dr Smith " . Terminators are often entities ( see §2.2.3.3 ) . Events ( see §2.22 and §2.23 ) ...
Page 473
... terminators . For example , the event : Customer makes deposit suggests that " Customer " will be a terminator on the context diagram . Of the two ' nouns ' present in this , the " Customer " is identified as the signalling agent ...
... terminators . For example , the event : Customer makes deposit suggests that " Customer " will be a terminator on the context diagram . Of the two ' nouns ' present in this , the " Customer " is identified as the signalling agent ...
Contents
Introduction | 1 |
Modelling Tools 35 3 | 35 |
The Enterprise Essential Model | 367 |
Copyright | |
3 other sections not shown
Common terms and phrases
abstract data type access flow allowed associative entity specification bSTD context diagram continuous data flow continuous event flow control process corresponding create data flow diagram data items data process data store defined delete described discrete data flow discrete event flow discrete process discussed Enterprise Essential Model entities and relationships entity relationship diagram entity-event table entry eSTD event store example flow specification function given Guidelines identifier Implementation Model information model inherited Instructor interface internal model machine manual meaning minispec model components Modelling Tools number of occurrences operation organisation output parameters parent ADT participate Patient pencil and paper post-condition process group processors real-world referred relationship frame relationship specification release of YSM response restriction Rules Scheduled course shown stimulus structure structure chart subtype supertype system ERD System Essential Model system modelling techniques terminator Transition Diagram type conversion update variable