000 03802cam a2200385 a 4500
001 37370257
003 OCoLC
005 20250703170037.0
008 970721s1998 njua b 001 0 eng
010 _a97033977
015 _aGB9814934
_2bnb
015 0 0 _ab9814934
020 _a0137488807
020 _a9780137488803
035 _a(OCoLC)37370257
_z(OCoLC)1137036739
_z(OCoLC)1171474165
040 _aDLC
_beng
_cDLC
_dC#P
_dUKM
_dNLGGC
_dYDXCP
_dBTCTA
_dX$T
_dAVCLL
_dOCLCO
_dOCLCF
_dOCLCQ
_dDEBSZ
_dOCLCQ
_dICN
_dDHA
_dOCLCQ
_dMST
_dOCLCA
_dOCLCQ
_dBGU
_dOCLCQ
_dUKMGB
_dUKUOY
_dAZU
_dOCLCQ
_dMM9
_dIL4J6
_dOCLCO
_dOCLCQ
_dOCLCO
050 0 0 _aQA76.9.O35
_bL37 1998
082 0 0 _a005.1/17
_221
100 1 _aLarman, Craig
245 1 0 _aApplying UML and patterns :
_ban introduction to object-oriented analysis and design /
_cCraig Larman
260 _aUpper Saddle River, N.J. :
_bPrentice Hall PTR,
_c℗♭1998
300 _axix, 507 pages :
_billustrations ;
_c27 cm
336 _atext
_btxt
_2rdacontent
337 _aunmediated
_bn
_2rdamedia
338 _avolume
_bnc
_2rdacarrier
504 _aIncludes bibliographical references (pages 495-496) and index
505 0 0 _gpt. I.
_tIntroduction --
_g1.
_tObject-Oriented Analysis and Design --
_g2.
_tIntroduction to a Development Process --
_g3.
_tDefining Models and Artifacts --
_gpt. II.
_tPlan and Elaborate Phase --
_g4.
_tCase Study: Point-of-Sale --
_g5.
_tUnderstanding Requirements --
_g6.
_tUse Cases: Describing Processes --
_g7.
_tRanking and Scheduling Use Cases --
_g8.
_tStarting a Development Cycle --
_gpt. III.
_tAnalyze Phase (1) --
_g9.
_tBuilding a Conceptual Model --
_g10.
_tConceptual Model -- Adding Associations --
_g11.
_tConceptual Model -- Adding Attributes --
_g12.
_tRecording Terms in the Glossary --
_g13.
_tSystem Behavior -- System Sequence Diagrams --
_g14.
_tSystem Behavior -- Contracts --
_gpt. IV.
_tDesign Phase (1) --
_g15.
_tFrom Analysis to Design --
_g16.
_tDescribing Real Use Cases --
_g17.
_tCollaboration Diagrams --
_g18.
_tGRASP: Patterns for Assigning Responsibilities --
_g19.
_tDesigning a Solution with Objects and Patterns --
_g20.
_tDetermining Visibility --
_g21.
_tDesign Class Diagrams --
_g22.
_tIssues in System Design --
_gpt. V.
_tConstruct Phase (1) --
_g23.
_tMapping Designs To Code --
_g24.
_tProgram Solution In Java --
_gpt. VI.
_tAnalyze Phase (2) --
_g25.
_tChoosing Development Cycle 2 Requirements --
_g26.
_tRelating Multiple Use Cases --
_g27.
_tExtending the Conceptual Model --
_g28.
_tGeneralization --
_g29.
_tPackages: Organizing Elements --
_g30.
_tPolishing the Conceptual Model --
_g31.
_tConceptual Model -- Summary --
_g32.
_tSystem Behavior --
_g33.
_tModeling Behavior in State Diagrams --
_gpt. VII.
_tDesign Phase (2) --
_g34.
_tGRASP: More Patterns for Assigning Responsibilities --
_g35.
_tDesigning with More Patterns --
_gpt. VIII.
_tSpecial Topics --
_g36.
_tOther UML Notation --
_g37.
_tDevelopment Process Issues --
_g38.
_tFrameworks, Patterns, and Persistence
520 1 _a"A proficient software engineer must have the ability to design robust, scalable, maintainable object systems. Applying UML and Patterns was written especially to provide the foundation for how to build systems using object technology." "Applying UML and Patterns provides students and developers with a detailed activity roadmap to guide them through each step of requirements, analysis, design, and coding. During the design phase, it places special emphasis on the critical skills needed for responsibility and collaboration design."--Jacket
650 0 _aObject-oriented methods (Computer science)
650 0 _aUML (Computer science)
650 0 _aSystem analysis
650 0 _aSystem design
776 0 8 _iOnline version:
_aLarman, Craig.
_tApplying UML and patterns.
_dUpper Saddle River, N.J. : Prentice Hall PTR, ℗♭1998
_w(OCoLC)655111056
942 _2lcc
_cBOOKS
_n0
999 _c1844
_d1844