[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> bib
|| [News] || [Research]

Bibliography Retrieval Engine(Beta)

Items in bibliography identified by a string matching SSADM

Alsaadi04
.Open Alsaadi04
 Ahmad Alsaadi
 A Performance analysis approach based on the UML Class diagram
 WOSP'04 & ACM SIGSOFT Software Engineering Notes V29n1(Jan 2004)pp254-260
 =EXAMPLe PERFORMANCE NORMALIZATION UML
 Can get speed by denormalizing physical data.
 Very like SSADM physical design control.
.Close

AmblerS97a
.Open AmblerS97a
 Scott Ambler
 Normalizing Classes
 Software Development V5n4(Apr 1997)pp69-72
 =DEMO DATA OBJECT-ORIENTED
 increasing cohesion and coupling by redesign but result is not in even 1NF in Codd terms.
 Adds a repeating group of enrollments to seminar.
 Better: Seminar<-<Enrollment>->Student and `new Enrollment(seminar student)` handles enrollments responsibillities for connecting seminars and students.
 Note: ends up with SSADM composite logical design!
.Close

Armstrong01
.Open Armstrong01
 Rob Armstrong
 Seven Steps to Optimizing Data Warehouse Performance
 IEEE Computer Magazine V34n12(Dec 2001)pp76-79
 =ADVERT PERFORMANCE OLAP DATA WAREHOUSE
 Good for OLTP is bad for OLAP.  Cf SSADM Physical design control in 1980's.
  steps: use relational OLTP data, implement special views via SQL, add indices, store more summaries, denormalize, denormalize irrationally, export data.
 Cycle: define requirement, understand benefits, determine needed data, find lowest step to get performance, calculate costs, implement or redefine requirements.
.Close

Black95
.Open Black95
 George Black
 British Government Puts New GUIs to the Test
 Software Magazine (May 1995)pp82-84
 =EXPERIENCE SSADM GRAPHIC USER GUI
 UK Customs & Excise Dept.
 SSADM (pre Vn4) not good for GUIs... using IEEE standards instead
.Close

Botting05a
.Open Botting05a
 Richard J Botting
 On the co-evolution of SSADM and the UML
 Chapter V in
.See [Yang05]
pp134-151
 =IDEA UML2.0 SSADM 
.Close

Brownbridge90
.Open Brownbridge90
 David Brownbridge(drb@paxis.co.uk)
 Using Z to Develop a CASE Toolset
 pp142-149 in Nicholls90
 =EXPERIENCE SSADM Z CASE 
 340 pages of Z -> 37KLOC object-oriented in 11 months
 no need of refinement
 needed for typechecker
 formal specification reviews are needed
 needed roadmap of hierarchy
.Close

Bryant90
.Open Bryant90
 Tony Bryant
 Structured methodologies and formal notations: Developing a framework for synthesis and investigation
 pp229-241 in Nicholls90
 =THEORY Z SSADM DEF STAN 0055
.Box
Chapter 2 section 4.1 clash between rigid method and dynamic system page 231
.Close.Box
.Close

Cortellessa01
.Open Cortellessa01
 V. Cortellessa & A. D'Ambrogio & G. Iazeolla
 Automatic derivation of software performance models from CASE documents
  Performance Evaluation V45n2-3 (Jul 2001) pp81-105 
.See http://www.elsevier.com/ 
.See [CR]
0201-0025
 =DEMO QUALITY PERFORMANCE MODEL SCENARIO  CASE UML Flowgraphs QUEUES LQN
 LQN::="Layered Queuing Network".
 (dick)|-`sounds like modern version of SSADM physical design control`.
.Close

Cutts88
.Open Cutts88
 Geof Cutts
 Structured Systems Analysis and Design Methodology
 Van Nostrand Reinhold NY NY 1988
 =TEXT SAD  ERD(cow format) DFD  DAD(using std not ELH) SSADM PQRST
.Close

DownsClareCoe8792
.Open DownsClareCoe8792
 Ed Downs & Peter Clare & Ian Coe
 Structured Systems Analysis and Design Method
 Prentice Hall International (UK) Herts UK 1988(1st edn) & 1992(2nd Edn) CR9305-0292
 =TEXT SSADM management COMPACT
 COMPACT for Office systems
 2nd Edn has Combined viewpoint diagrams(CCTA 1990) : two parts control+Process
.Close

GerhartCraigenRalston94
.Open GerhartCraigenRalston94
 Susan Gerhart & Dan Craigen & Ted Ralson
 Experience with Formal Methods in Critical Systems
 IEEE Software magazine v11n1(Jan 1994)pp21-28 CR9601-0044
 =EXPERIENCE FORMAL
.See [Craigenetal95]
.Box
Note:  more in Craigenetal93
Study of 12 cases of industrial use - including  SSADM tools, CICS, Cleanroom, Oscilloscopes, Inmos, VDM in the Lacos project, TBACS at NIST, HP Medical instruments

Conclusions
 Formal methods more useful at front than for code
 Tend to improve things
 refinement not cost effective

p27:"Mathematics involved in most formal methods is elementary, so the greater challenge may lie in teaching users how to model systems properly and carry design through."

p28: primarily used for
  Assurance, Domain Analysis,  Communication,  Evidence of best practice,  Re-Engineering
.Close.Box
.Close

Hall81
.Open Hall81
 John Hall
 System Development Methodology
 Learmonth & Burchet Management Systems Ltd London England Mar 1981
 =BLURB SSADM PQRST
.Close

Hares90
.Open Hares90
 John S Hares
 SSADM for the Advanced Practitioner
 John Wiley & Sons NY NY 1990
 =TEXT SSADM
Content
.Box
 1 Past and future
 2 strengths and weaknesses
 3. Pearls of PRactical Wisdom
 4 Distributed, Realtime, Conversational
 5 Expert Systems & Object Oriented Design
.List
  OOD
    Normalize logic as well as attributes.
    access paths ---> responsibillity clusters
.Close.Box
.Close

Hares94
.Open Hares94
 John S Hares
 SSADM version 4: the Advanced Practitioner
 John Wiley & Sons NY NY 1994 ISBN 0-471-93564-6 CR9502-0077
 =TEXT SSADM4
.Close

HaresSmart94
.Open HaresSmart94
 John S Hares & John D Smart
 Object Orientation: Technology& Techniques& Management and Migration
 John Wiley & Sones Inc NY NY 1994 $48.95 ISBN 0-471-94124-7 CR9511-0832
 =TEXT extends SSADM to Objects
 
.See [RobinsonBerrisford94]
.Close

HawkinsEtAl12
.Open HawkinsEtAl12
  Peter Hawkins & Martin Rinard & Alex Aiken & Mooly Sagiv & Kathleen Fisher
  An introduction to data representation synthesis
  Commun ACM V55n12(Dec 2012)pp91-99
.See http://doi.acm.org/10.1145/2380656.2380677
  =TOOL RelC COMPILES RELATIONAL DATA to STRUCTURES HASH LIST VECTOR PERFORMANCE 
 Method:=relational TNF data; logical queries; physical data structures; physical queries;  code; performance. 
 Essentially an implementation of Keith Robinson's data design theory from 1980 SSADM! 
.Close

Hellenack97
.Open Hellenack97
 Leslie J Hellenack
 Object-Oriented Business Patterns
 Object Magazine 6(11)(Jan 1997) pp23-30+70
 =IDEA SYSTEM REALITY OBJECTS
 SYSTEM+REALITY OBJECTS: adapts IBM's work in the 70's to OO
 OMT-like model looks like LDSTs of SSADM courses 1982
.Close

HincheyBowen99
.Open HincheyBowen99
 Michael G Hinchey & Jonathan P Bowen (Eds)
 Industrial-Strength Formal Methods in Practice
 FACIT Series of Springer-Verlag 1999 SBN 1-8533-640-4 QA76.9 F67 I53
 =EXPERIENCE FORMAL METHODS B BAN Z TABULAR ACL2 RAISE Z/EVES EVES V&V TOOL Cleanroom SSADM RSML
 for cs556/656
 Contains 
.See [BjornerGeorgePrehn99]
.See [LevesonEtal99b]
.See [KestenKleinPnueliRaanan99]
.See [BrockHunt99]
.See [LanoGoldsackSanchez99]
.See [BurrowsAbadiNeedham89]
.See [Anderson99]
.See [BernardLaffite99]
.See [BowenHinchey99]
.See [LingerTrammell99]
.See [BoralvStalmarck99]
.See [ArdisMataga99]
.See [MooreKlinkerMihelcic99]
.See [CraigenMeiselsSaaltink99]
.See [SemmensBryant99]
.See [Jacky99]
.Close

Hohpe05
.Open Hohpe05
 Gregor Hohpe
 Your coffee shop doesn't use two-phase commit
 IEEE Software Magazine V22n2(Mar/Apr 2005)pp64-66 & letter V22n3(May/Jun 2005)pp8-9
 =ARTICLE PATTERNS CONCURRENCY TRANSACTIONS ACID NONSEQUENTIAL
  4 strategies: write-off, retry, compensate/undo, coordinate.
 Compare 1970s SSADM/Jackson recognition problems.
 Shorter version at
.See http://www.enterpriseintegrationpatterns.com/ramblings/18-starbucks.html
.Close

Holmes06
.Open Holmes06
 Neville Holmes 
 The Data Doughnut and the Software Hole
 IEEE Computer Magazine V39n6(Jun 2006)pp100+98-99 
 =ESSAY MODULAR SYSTEMS ARCHITECTURE DATA vs INPUT vs OUTPUT INFORMATION IT DP ERP CSCI372  
 Claims that large systems fail because they are integrated rather than modular.
 Best architecture has a central data base plus information processing programs around it. 
 (dick)|- These observations are still true even if they were first made 30 years ago.
 (dick)|- However... there is a family of components that are neither input, output, or database.   These are interactive interfaces for editing data.
See Model-view-controler(MVC), Ambler on architecture, and so on back to SSADM and JSP.
 Also see Gankarz for the Unix way of modularizing programs.
.Close

JacksonTwaddle97
.Open JacksonTwaddle97
 Michael Jackson & Graham Twaddle
 Business Process Implementation: Building Workflow Systems,
 Addison Wesley ACM Press 199? ISBN 0-201-17768-4 3rd hd58.87.j32 1997
 =EXPERIENCE SPECIFICATION MODEL OFFICE WORKFLOW PEOPLE DATA PROCESS FLEXIBLE vs BUSINESS RULES TABULAR GRAPHIC METADATA
 workflow_problem_frame ::= following,
.Net
 |-(minimal_workflow_frame):The machine supports an office that interacts with an outside world.
 |-The prime business need is to keep track of long term commitments, contracts, and obligations.
 |-There  are rigid business rules and flexible activities.
 |- activities are multitasked error correcting that proceed at a human pace.
 |- not safety critical.
.Close.Net
  theoretical_method:= data; process; tasks; workflow.
 In practice incremental and iterative delivery is feasible.
 data:=`simple ERD`, like SSADM.
 task_types:=initiated performed content 
.See [task_details].
   initiated:=X | T | P | I.  X=eXternal, T=Time, P=follows Preceeding, I=Internally.
   performed= A | M, A=Automatically, M=not A, `Manually`,
   content:= E | K| U | D | O, E=dataEntry, K=checK, U=Update, D=Decision, O=Output.
  Tasks involve entities.  
 LC:=" life cycle".
 An entity life cycle is a defined sequence of stages but an entity may not progress thru the stages in such a simple way.  Office work may backtrack, hang up, fail, or multitask parts of stages at one time.  Stages may not be omitted.  Backtracking (a `setback`) means handling side-effects: beneficent, neutral, and intolerable. cf 
.See [JSP].
   In a stage contains a task that fails then the current life cycle fails and initiates a different one instead.
   Stages determine states:  State = ("In" | "Failed" | "Awaiting" | "Halted" ) stage.
    Within a Stage many tasks can execute in parallel.  some can spawn (one|many (inclusive | exclusive)) subtasks (sometimes). One subtask can be spawned by many tasks, and a subtasks can restart their parent tasks (in a loop).
    Task states = null; start; (n/a | run | failed | passed).  passed states do not spawn subtasks, run states must start their subtasks.  Task states determine life-cycle states.
  There are rules for assigning tasks to stages.
  One life cycle can depend on another one.  Changing stage depends on one(or all) other linked entities of a given type is|are past a certain stage.  Tasks can start and halt other life cycles.
  Entities are placed in classes. Classes form a `heterarchy` -- multiple inheritance.  Also classification entities -- classes of objects each defining a class of object!
  Entities play roles in entity life cycles.  roles require only a subset of the attributes,  Also several types of entity can play the part in a single role.
  Datasets are structured  navigation paths between entity types.  `from A access one B and many Cs`.  They are chosen to fit tasks.
 Programs support tasks - within task context and using task content. actions include SET_RESULT, START_LC, SUSPEND_LC, RESUME_LC, CANCEL_LC, SETBACK_LC, WAIT..., SIMPLE_CHECK, COMPLEX_CHECK, SIMPLE_SET, APPLICABLE_WHEN.  Some tasks must not be repeated, others may be repeated when backtracking.
 Decision Tables!
 Tasks and life cycle work mainly define wrong sequences.  Work flows help get good things done.   Work flows are about scheduling, options, menus, and efficiency.  Work flows are based on a relational data base:
 task_details:=Net{
 Each task is in a stage of a life cycle of an entity.
 Each task has a task_type that has a program, data set, and a set of skills.
 Tasks are related to users who can/should do them by Skills and by stages and departments for example. 
}.
  Detailed reporting and so tuning of the workflows.
 Life cycle definitions and the office workflow are also held in the data base. "Process representations become data".  Process data is PLANs and FEATUREs. 
 The only purpose of documentation is understanding.... but if documentation is in a data base is also useful to the software.
 dick:`the office workflow frame fits agile software development process.`
.Close

LamSuKoganti88
.Open LamSuKoganti88
 Herman Lam & Stanley Y W Su & Nageshwar R Koganti
 A Physical Database Design Evaluation System for CODASYL Databases
 IEEE Trans Soft Eng VSE-14n7(Jul 1988)pp1010-1022
 =DEMO DATA QUALITY VOLUME SPEED
 not unlike SSADM physical design control.
.Close

LangFitzgerald05
.Open LangFitzgerald05
 Michael Lang & Brian  Fitzgerald 
 Hypermedia Systems Development Practices: A Survey
 IEEE Software Magazine V22n2(Mar/Apr 2005)pp68-75
 =POLL 167 IRISH PROCESS WEB/NET MEDIA REQUIREMENTS MANAGEMENT PEOPLE
 Mixture of people from software development and from graphic design.  41% people with equal background.
 30% hit time targets and 47% hit cost target.  However 17% had 50% timed over run, and 14% had a cost overrun.
 Most of the problems where minor or moderate rather than major. 
  Project scope, feature creep, volatile and changing requirements tended to be more of a problem than estimation, time pressure, communication, or coordination.
 Most had a clear process and written requirements specification(mostly 10..50 pages).
 Wide range of methods including hybrid, custom, SSADM JSP, SDLC, RAD, XP, RUP plus tool focussed: PHP, Java, Flash, ASP, J2EE,UML. Pus FuseBox, WSDM, OOHDM, ...
 No evidence that academic research has produced methods for hypermedia/web that developers are using.  
.Close

LanoHaughton94
.Open LanoHaughton94
 Kevin Lano & Howard Haughton
 Object-oriented specification case studies
 Prentice Hall Englewood Cliffs NJ 1994 ISBN0-13-097015-8
 =DEMOS FORMAL MooZ OOZE/FOOPS VDM++ Z++ Object-Z Fresco OOSD OMT SSADM
.Close

LejkDeeks02
.Open LejkDeeks02
 Mark Lejk & David Deeks
 An Introduction to Systems Analysis Techniques (2nd edn.)
 Addison Wesley USA & Pearson Edn Ltd Harlow Essex UK 2002 ISBN 0-201-79713-5
 =TEXTBOOK SSADM  Object-Oriented  REALITY SYSTEM PURPOSE DFD SPECIFICATION ELHs PISO CRC Decision TABLES Management
 PISO::="Process Improvement for Strategic Objectives".
.Close

LiuFeketeGorton05
.Open LiuFeketeGorton05
 Yan Liu & Alan Fekete & Ian Gorton
 Design-level Performance Prediction of Component-Base Applications
 IEEE Trans Software Engineering  V31n11(Nov 2005)pp928-941
 =SIMULATION =THEORY QUEUE COMPONENTS PERFORMANCE EJB QNM
 Derives a queuing theory performance model for various kinds of transactions.
 Models calibrated by a very simple benchmark on two platforms.
 Models combined with a sequence diagram model of an application to predict performance.
  The predictions compares well with a simulation of the application.
 The predictions allow the selection of the better of two possible designs.
 No code is needed in to make the predictions.
 (dick)|- SSADM Physical Design Control used quantified models of DBMSs and application designs to select a physical design that was likely to perform well in 1979.
.Close

Maddisonetal83
.Open Maddisonetal83
 ?? Maddison ...
 Information Systems Methodologies
 UK Wiley Hayden
 =survey SAD SSADM DFD ERD PQRST
.Close

Maibaum09
.Open Maibaum09
 Tom Maibaum
 formal methods versus engineering
 ACM Inroads & SIGCSE Bulletin V41n2(Jun 2009)pp6-12
 =EDITORIAL ENGINEERING SCIENCE MATHEMATICS DESIGN HANDBOOKS EDUCATION METHODOLOGY COOKBOOK
 Quotes Vincenti90 and MAJackson.
Compare with
.See [Maibaum97]
 Engineers need standard cookbook methods and calculations suited to specific kinds of problems. 
 Fails to mention DDD(JSP, compilers, database, JSD, SSADM etc), Model checking ( SMV Alloy etc.)
 Does not discuss the intractability and/or unsolvability of the problem of calculating consequences of requirements.
 Implies that given pre/post conditions the code can be generated automatically
-- but actually the engineer needs to supply internal invariants, structures, and non-functional requirements to determine the best design for code.
 More on the scientific basis for software engineering
.See [JuristoMoreno02]
and compare with
.See [HincheyEtAl08]
on formal methods in software engineering.
.Close

MartinSwaran97
.Open MartinSwaran97
 David H Martin & Agni Swaran
 Designing for Performance: The ODBMS Impact on Design
 Object Magazine (Feb 1997)pp45-50
 =EXPERIENCE OBJECT-ORIENTED DATAbases two different projects with different lifecycles and domains
 Optimizations similar to SSADM Physical Design Control
 Time-to-market vs maintainability - 
.See [Botting97a]
.Close

NeilLaplante03
.Open NeilLaplante03
 Colin J Neil & Phillip A Laplante
 Requirements Engineering: The State of the Practice
 IEEE Software Magazine V20n6(Nov/Dec 2003)pp40-45
 =POLL 194 GRADUATE ALUMNI REQUIREMENTS PRACTICES
.Set
 Waterfall is still the most popular life cycle (just)
 But prototyping is popular -- especially for user interfaces. Scenarios and use cases are the most popular requirements technique. Focus groups and informal modelling are popular. Then JAD and other "involve the user" technique
s. Methodologies: "none" is most popular(32%), OO(30%), vs 40% structured: SADT(12%),
 SReM(10%), SSADM(8%), SERM(7%) and no JSD.
 Models: informal 51%, semiformal 27%, formal 7%. Success in 50% of projects.  Tho' management felt 50% of the time the project was 
either over budget or late or both.  Longer (> 2yrs) projects were less successful: over budget , late, less likely to 
be easy to use or to meet needs. Quality assurance: informal or formal walkthroughs plus some checklists and/or scenarios.
.Close.Set
.Close

Polack01
.Open Polack01
 Fiona Polack
 A Case Study using Lightweight formalism to Review an Information System Specification
 Software - Practice & Experience V31n8(10 Jul 2001)pp757-780
 =CASESTUDY V&V SPECIFICATION SAZ Z SSADM Ordnance Survey UK
 Lightweight formal review can detect many problems: unmet requirements, inconsistencies, contradictions, ambiguity, ...
 Original documents generated 100page Z+text +questions review.
 Uncovered missing constraints, ambiguities, conflicts, inconsistencies, ...
.Close

PolackWhistonMander93
.Open PolackWhistonMander93
 F Polack & M Whiston & K Mander
 The SAZ project: Integrating SSADM and Z
.See [WoodcockLarson93] pp541-557
.See [BourdeauCheng95] (ref)
 =THEORY Z SSADM
.Close

PurchaseWellandMcGillColpoys02
.Open PurchaseWellandMcGillColpoys02
 H Purchase & R Welland & M McGill & L Colpoys
 Comprehension of diagram syntax: an empirical study of entity relationship notations
 International Journal of Human-Computer Studies V61n2(??? 2004)pp187-203
 =EXPERIMENT SSADM vs ERD
 For binary realtions SSADM LDS are grasped more quickly than Chen ERD by naive subjects.
 Failed to test result of reifying many-many relations as SSADM requires,
.Close

PutryczWoodsideWu05
.Open PutryczWoodsideWu05
 Erik Putrycz & Murray Woodside & Xiuping Wu
 IEEE Software Magazine V22n3(Jul/Aug 2005)pp36-43 
 =ADVERT COMPONENTS PERFORMANCE ARCHITECTURE METHOD LOAD QUEUING MODEL 
 Not unlike the 1980s Physical Design Control step in SSADM!
.Close

RobinsonBerrisford94
.Open RobinsonBerrisford94
 Keith Robinson & Graham Berrisford
 Object-oriented SSADM
 Prentice Hall Inc Upper Sddle River NJ 1994 ISBN 0-13-309444-8  
.See [CR]
9504-0236& 
.See [CR]
9510-0775
 =HOWTO SSADM DAD DFD ERD ELH HCI LDD OBJECT-ORIENTED
 (CR9504-0236)|-`Model systems Inc., SSADM Vn 4, conceptual modeling, not university text`.
 (CR9510-0775)|- six parts(intro, 3models(relational,process,dynamic)+terms, OOP, entity data modeling, external design(UI), Reuse), 3-Schema Architecture

Less emphasis on DFD.
More on HCI interaction design.
.Close

RobinsonBPrior95
.Open RobinsonBPrior95
 Barbara Robinson & Mary Prior
 Systems Analysis Techniques
 Int Thomson Computer Press Boston MA 1995 ISBN 1-85032-183-3 
.See [CR]
9609-0690
 =HOWTO DFD ERD DAD ELH Entity-event matrices ?SSADM?
.Close

Sanden03
.Open Sanden03
 Bo Sanden
 Entity-Life Modeling: Modeling a Thread Architecture on a Problem Environment
 IEEE Software Magazine V20n4(Jul/Aug 2003)pp70-78 $CR 0405-0559
 =DEMO non-sequential  DAD ELM REALITY TECHNICAL THREADS interleaving FSM
 ELM::="Entity-Life modeling".
  To keep sane in a multithreaded architecture, make each thread  reflect a real (external) entity.
 Some threads can have an explicit pattern described in a state machine/chart.
 (dick)|- very close to JSD and ELH's in SSADM from the 1980's.
 History in
.See [Sanden09]
.Close

SemmensBryant99
.Open SemmensBryant99
 Lesley Semmens & Tony Bryant
 Rigorous Review Technique
 In 
.See [HincheyBowen99]
pp231-254
 =DEMO EXPERIENCE METHODS Z SSADM TELSTAR BT( British telecom) FORMAL SQA STRUCTURE  ANALYSIS DESIGN DFD ER DATA RRT
 RRT::="Rigorous Review Technique".
 How to use Z to check structured method outputs.
 It is easier to teach simplified Z mathematics to analysts than to teach a mathematically competent an understanding of analytical skills.
.Close

ShanksTansleyWeber03
.Open ShanksTansleyWeber03
 Graeme Shanks & Elizabeth Tansley & Ron Weber
 Using Ontology to Validate Conceptual Models
 Commun ACM V46n10(Oct 2003)pp85-89 $CR 0404-0429
 =ADVERT ONTOLOGY MODEL REALITY ERD
 Abuses the term "Grammar" to mean "modelling language".  Gives a bad SSADM model but doesn't show corrected one.
 Notes risks of seeing everything as tables of data.  Some relationships are best expressed as rules/code rather than tables.
 Quotes Bunges's theory of ontology that distinguishes: things, properties of things, states of things, laws, events in things, and couplings.
 Critiques ERD as not including rules.
 Important to:
.List
  Distinguish rules from relationships
  Model composites and aggregates as entities not relationships.
  Don't model relationships using attributes.
  Don't use optional attributes in entities.
  Distinguish objects/instances from classses.
 Distinguish things from their properties.
.Close.List
.Close

SnoeckDedene98
.Open SnoeckDedene98
 Monique Snoeck & Guido Dedene
 Existence Dependency:  The Key to Semantic Integrity Between Structural and Behavioral Aspects of Object Types
 IEEE Trans SE-24n4(Apr 1998)pp233-351
 =THEORY DAD DYNAMICS ERDS(PROBLEMS) GRAPHIC JSP/JSD OOA/OOD/OOSD QUALITY SSADM STD/FSM UML
 OET::="Object Event Table"
.See [DedeneSnoeck94] on MERODE
.Close

ThayerDorfman90
.Open ThayerDorfman90
 Richard H Thayer & Merlin Dorfman(eds)
 System and Software Requirements Engineering
 IEEE CS Press Tutorial Cat No.EH0304-6 QA76.758 S87
 =TEXT BOOK n-squared, std decision tables decision trees pdl statecharts rnet sdl petri net sa dfds era ooa ssadm jsd descartes(JE Urban's DDD), STARTS Z srem psa/psl glossary(pp605-676), bibliography(pp677-695) case studies(553-603)
.Close

Search for bibliographic items containing a matching string.


(Search uses POSIX regular expressions and ignores case)

To see the complete bibliography (1Mb+) select:[Bibliography]