appendix a - link.springer.com
TRANSCRIPT
Appendix A
IntroductionThis appendix contains some useful web links and bookreferences. The world of software development is fastchanging and growing. Depending on your job, you may haveto keep up with the new advances in software engineering asit changes in response to new technologies such as theInternet, WAP, mobile devices and so on.
Web resources• Object Management Group: www.omg.org• Component Source: www.componentsource.com
• SELECT: www.selectst.com
Book referencesBooch, G. Object Oriented Analysis and Design with
Applications, 2nd Ed. Benjamin Cummins, 1993.Coad, P. ObjectModels: Strategies, Patterns, and Applications.
Prentice Hall (Yourdon Press), 1995.Coad, P. and Yourdon, E. Object Oriented Analysis. Prentice
Hall (Yourdon Press), 1991.Jacobson, I, Christerson, M, Jonsson , PM, Overgaard, G. Object
Oriented Software Engineering:A Use Case Driven Approach.Addison Wesley, 1992.
Jacobson, I, Ericcson, M, Jacobson, A. The Object Advantage:Business Process Re-engineering with Object Technology.Addison Wesley,1994.
Lorenz, M. Object Oriented Software Development: APractical Guide. Prentice Hall, NJ, 1993.
Pree, W. Design Patterns for Object Oriented SoftwareDevelopment. Addison Wesley, 1995.
Wirfs Brock, R, Wilkerson, B, Wiener, 1. Designing ObjectOrientedSoftware. Prentice Hall, 1991.
Yourdon,EN,Whitehead, K,Thomann, J,Oppel, K,Nevermann,P. Mainstream Objects: An Analysisand Design Approach forBusiness. Prentice Hall (Yourdon Press), 1995.
Appendix B
Use cases
x------UseCase
extends
Use Case-l
Class diagrams
UseCase
uses
UseCase-2
<<business>> 1 *1 <<business>>I::Class I ::C1ass-l
Attribute
Operation
<<business>>::C1ass-2
Collaboration diagrams
<<business>>Instance :C1ass
<<business>>Insta nce :C1ass-l
I 2',EventO
<<business>>Instance :Class-2
Sequence diagrams
<<business>> <<business>>Instance Instance:Class :Class-l
Event-l ~-,
Operation-l~
State diagrams
.------)l.~( State )Start
.@End
Activity diagrams
====:; ~.~-1~.:~( Aetivity-2~ ~
Index
A
abstract class diagrams· 66abstract use case(s) . 46-7
Account class· 56-9 , 127-9
user interface ' 151-3
actions, state diagrams ' 95-6
ActiveX, reusability' 186-7activities, state diagrams' 96activity diagrams' 212
modelling behaviour · 105
actor(s)CCDs ·73-4use case(s) . 39-41,43-4
aggregation relationships· 62-3,
65analysis and design
approaches ' 2-3
examples ' 191-202
analysis patterns' 118-20analysis, requirements' 47,193-5,
196-8analysis to design' 125-30
architecturescommon' 187-8tiered . 132-4see also Common Object
Request BrokerArchitecture
associations, class(es) . 50, 51-3 ,59-63
attributesclass diagrams . 56-8
class(es) . 50
indexing ·166-7
B
behavioural modelling' 9,201-2
behaviour diagrams · 130
bi-directional view, system
modelling· 176book references· 208bottom-top view, system
modelling' 175
BPM see Business Process
Modelling
Browse Class utility ' 57browsing a class· 55-6, 57
business class(es) ·51-3
business modelling· 8-9business processes
EBPs ·135-6
linking ' 139Business Process Modelling
(BPM) . 133-4
c
CASE tools· 3-4, 5
choosing · 15-16modelling · 15see also SELECf Enterprise
CASE toolC1C++
code generation ' 114-16user interface· 153-4
CCDs see Class Collaboration
Diagramscentralized control,
implementation' 184-5Class Collaboration Diagrams
(CCDs)' 69,70-7actor(s) . 73-4
class(es), adding' 74-5
class(es), deleting· 75-6
creating ' 71-4
event(s) , adding' 77
examples' 199-201
operation(s), adding ' 77
relationships, editing' 76-7
storyboarding . 10
class diagrams' 54-9 ,127-9,210abstract· 66attributes· 56-8
creating ' 54-9detailed· 66
class(es) . 49--66
adding, (CCDs)' 74-5adding, (CSDs) . 80-2
associations · 50, 51-3
attributes · 50
attributes, adding ' 56-8browsing' 55-6, 57
collection- 53
data management · 53deleting, (CCDs) . 75-6
deleting, (CSDs) ·80-2identification ·195--6, 198-9inheritance· 60-3
interaction between · 85--6linking· 59-63
methods, adding ' 58-9
modelling class interactions ·68-70
and object(s) . 20-1 , 50-1sequences between · 82-3structure ' 53types' 51-3user interface' 150-4
Class Sequence Diagrams(CSDs) · 69, 211
class(es) , adding' 80-2
class(es), deleting ' 80-2
creating' 79-80
datastore creation· 84editing relationships' 82-3
extends probe ' 86interaction between classes ·
85--6
iteration adding · 84
objects ' 78
sequence adding ' 83-5
statements' 78stimuli · 78
uses probe' 86code generators, SELECT
Enterprise extras ' 114-16collaboration diagrams see Class
Collaboration Diagrams
collection class(es) . 53
columns, tables · 163-4, 165
COM/COM+, reusability ' 186-7
Common Object Request BrokerArchitecture (CORBA)
CORBA IDL code
generation' 115-16databases · 170-1reusability' 186, 187-8see also architectures
completing the model · 173-81component diagrams,
implementation ' 185-8
components view, systemmodelling' 176-7
composite patterns' 121-2composition relationships ' 62-3,
65concurrences, PTDs . 146-7
concurrent states , modellingbehaviour · 103-5
conditions, state diagrams ' 97
consistency checking, SELECT
Enterprise extras' 112-14
control techniques,
implementation ' 184-5CORBA see Common Object
Request Broker Architecture
CSDs see Class SequenceDiagrams
D
databasesCORBA · 170-1employee' 191-202indexing attributes · 166-7middleware . 159
modelling ·157-71
multi-site deployment · 189-90
00 design '169-70
ORB ·170-1
primary keys ' 111, 164--5, 166relationships ' 167-9
tables ' 160-4types . 158-9
data dictionariesindexing attributes· 166-7
Links Editor · 138-9SELECT Enterprise extras ' .
111-12
data management class(es) ·53datastores . 33
creating ' 84CSDs ·84SELECT Enterprise ' 28-9
delegation, modelling classinteractions·69-70
deployment diagrams,implementation ' 189-90
design see modellingdesign, analysis and see analysis
and design
design class diagrams ' 127-9see also class diagrams
design expansion support · 130
design patterns ' 120-2, 123detailed class diagrams' 66detailed use case(s) ·46-7
dictionaries see data dictionaries
distributed control,
implementation ' 185
documentation· 179-80Document Object Model
(DOM) ·2domain modelling ·131-48
terminology' 132
dynamic modelling ' 88
E
Elementary Business Processes(EBPs) . 135-6
employee database · 191-202
Enabler toolCSDs ·80SELECT Enterprise ' 27-9
encapsulation, OOT . 53
entity relationship diagrams ·
158-9essential use cases · 126-7
event/action blocks · 99-101event(s)
CCDs ·77state diagrams ' 95
examples' 191-202employee database · 191-202
exclusive arc transitions , PTDs .145
extends link, use case(s) ·45-6extends probe, CSDs . 86
extensions, UML . 204
G
Gantt charts · 179General Graphics diagrams · 108
generic applications 9graphic user interfaces (GUls) .
153-4
see also user interface
H
hierarchies, modelling· 10
I
identification , class(es) . 195-6,198-9
implementation · 183-90component diagrams· 185-8
control techniq ues· 184-5
deployment diagrams· 189-90
indexing attributes, databases ·166-7
inheritance
adding · 63associations· 61-2class(es) . 60-3
multiple ·61-2and relationships· 21-2
reusability · 62see also polymorphism
interaction diagrams · 129
interaction modelling· 199-201interface, user see user interfaceiteration adding
CSDs ·84PTDs · 147- 8
J
Jacobson methodology· 4
Java Beans, reusability · 186-7
Java Swing package· 153-4
L
Larman methodology · 4life cycles, modelling· 10-14
linking
business processes· 139
class(es) . 59-63use case(s) . 44-6
Links Editor, PHDs . 138-9
M
many-to-many relationships· 60,
64-5, 167-9
methods, adding · 58-9
Microsoft COM, reusabili ty ·186-7
middleware, databases· 159
modelling
behavioural· 9, 201-2
business modelling· 8-9checklist· 181completing the model· 173-81
hierarchies · 10interaction · 199-201introduction to · 7-16
life cycles· 10-14
modelling diagrams· 177object-oriented · 18-1900 modelling views· 177storyboarding ·9-10structural · 9structured · 18-19sub-systems· 174system modelling views · 175-8
modelling behaviour· 87-105
activity diagrams · 105
dynamic modelling · 88
event/action blocks· 99-101state diagrams · 88-94
state messages · 94-9
super/sub-states· 100-5
modelling interaction· 67--86
CCDs ·70-7
CSDs ·78-86modelling class interactions·
68-70multiple inheritance· 61-2
o
object identifiers ' 58
Object Management Group(OMG) ·122
object-oriented analysis and
design (OOAD), patterns'117-23
object-oriented technology(OOT) . 2, 17-23class(es) . 20-1
concepts' 19-23encapsulation' 53inheritance ·21-2
inheritance and relationships'21-2
00 modelling· 18-19,177polymorphism' 22-3relational databases· 169-70responsibility ' 53
Object Request Broker (ORB),databases · 170-1
object(s) ·49-66and class(es) . 20-1, 50-1
CSDs·78
OMG see Object Management
Group
one-to-many relationships ' 63-4 ,167-9
one-to-one relationships' 167-9OOAD see object-oriented
analysis and designOOT see object-oriented
technology
open systems design 9
ORB see Object Request Broker
overriding, polymorphism'
22-3
p
package diagrams, SELECT
Enterprise CASE tool · 132-5patterns ' 117-23
analysis patterns' 118-20
composite patterns' 121-2
design patterns' 120-2, 123
recording ' 122-3state patterns ' 120-1transaction patterns'
119-20
PERT charts · 179PHDs see process hierarchy
diagramspolymorphism, OOT . 22-3
primary keysSELECT Enterprise extras'
111tables· 164-5, 166
process breaks, PTDs· 145-6process(es), use case(s) ·41-4process hierarchy diagrams
(PHDs) . 133-4,135-9
creating ' 136-7
editing' 137-9
process thread diagrams(PTDs) . 133-4, 140-8
adding a process ' 143concurrences . 146-7
creating ' 141-2
editing ' 142-3iteration adding' 147-8process breaks· 145-6transitions· 143-5
project management· 178-80
prototype life cycle
modelling· 11-12
see also spiral life cycleprototyping, user interface ·
154-5
PTDs see process threaddiagrams
R
Rap id Application Development(RAD)· 3, 180
Rational Rose CASE tool · 3-4, 5
and UML · 14, 15
real-time UML· 205real use cases· 126-7references, book · 208
relational databases see databasesrelationships
adding· 63-5editing · 82-3and inheritance · 21-2many-to-many . 60, 64-5, 167-9
one-to-many . 63-4, 167-9one-to-one relationships·
167-9table (relationship) diagrams·
160-4types· 167-9
reports, SELECT Enterpriseextras · 112-14
repositories
creating · 84
CSDs·84SELECT Enterprise · 28-9, 33
Repository Administrator,
SELECT Enterprise · 27-9
requirements gathering/analysis ·
47examples · 193-5, 196-8
responsibility, OOT . 53
responsibility view, system
modelling· 177-8reusability
component software · 186-8
inheritance · 62
s
security system, examples ·
196-202SELECT Enterprise CASE
tool· 3-4 ,5,25-33
client/server issues · 26-7, 33
datastores/repositories· 28--9, 33
design expansion support· 130Enabler tool · 27-9errors · 32-3
installing · 26-7, 32-3package diagrams · 132-5PHDs . 133-4, 135-9
process thread diagrams ·
133-4
SELECT Models · 29-30starting · 30-2state diagrams · 88-94and UML · 14, 15
SELECT Enterprise extras ·107-16code generators · 114-16consistency checking · 112-14
data dictionary ·111-12
General Graphics diagrams ·
108prime keys . 111
reports · 112-14
Storage Mapper· 108--11
Tools Customizer· 116
sequence diagrams see ClassSequence Diagrams
sequential states, modelling
behaviour · 101-3spiral life cycle, modelling' 12-13
SQL code generation' 114-16SSADM see Structured Systems
Analysis and Design Method
state diagrams ' 211actions· 95-6
activities · 96adding states ' 91-2
conditions · 97
creating' 89-91
deleting states' 91-2editing states ' 93-4event(s) · 95modelling behaviour· 88-94
state messages · 94-7transitions · 97-9
statements, CSDs . 78
state patterns' 120-1
state transition diagrams,storyboarding . 10
stimuli, CSDs . 78
Storage Mapper' 108-11, 169-70storyboarding, modelling · 9-10structural modelling ' 9structure, class(es) . 53structured modelling ' 18-19
Structured Systems Analysis andDesign Method (SSADM) ,
waterfall life cycle' 11
sub-systems modelling' 174
super/sub-states, modelling
behaviour ' 100-5
system modelling views · 175-8
T
tables
columns· 163-4, 165
databases · 160-4
deleting ' 163
editing' 163primary keys · 164-5table (relationship) diagrams '
160-4task management · 178-9
team working' 180
tiered architectures · 132-4
time boxing' 3, 178-9
time factor, modelling class
interactions· 70
time management · 178-9Tools Customizer, SELECT
Enterprise extras ' 116
top-bottom view, system
modelling' 175transaction patterns ' 119-20transitions
PTDs ·143-5
state diagrams' 97-9
u
Unified Modelling Language(UML)advantages ' 14extensions . 204
modelling' 14
real-time ' 205use case(s) · 35-47, 210
abstract ·46-7
actor(s) · 39-41, 43-4
adding ' 41-4
creating ' 38-9described · 36detailed · 46-7diagrammatic views· 36-7
essential use cases ' 126-7
linking· 44-6
Links Editor · 138-9
process(es) . 41-4
real use cases· 126-7
requirementsgathering/analysis · 193-5,
196-8
security system· 196-8storyboarding . 10
textual views· 37-8
use case diagrams · 4use case view, system modelling·
178user class(es) · 51- 3, 153-4user interface
class(es) . 150-4
design · 149-55prototyping . 154-5
SELECT Enterprise CASE
tool · 30-2storyboarding . 10
uses link, use case(s) ·45-6
uses probe, CSDs . 86
v
Visio graphical software· 5
Visual Basic, user interface ·
153-5
V-shaped life cycle, modelling ·13-14
w
waterfall life cycle, modelling · 11
web resources· 208