Object-Oriented Software Development with UML - UNU-IIST ...

More documents

Recommendations

Info

Zhiming Liu is a research fellow at UNU/IIST, on leave from the Department of Mathematics and ComputerScience at the University of Leicester, England, where he is a lecturer in computer science. Hisresearch interests include formal theories and methods of computing systems in general and formal semantics,specification and verification of fault-tolerant, real-time and concurrent systems; and formal techniquesfor object-oriented system development. He had taught OO with UML for 4 years during 1998 - 2002 atthe University of Leicester. E-mail: Z. Liu@iist.unu.edu.Copyright c 2002 by UNU/IIST, Zhiming Liu¡
ContentsiContents1 Introduction 11.1 Reading List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Introduction to Software Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Software Development Process 52.1 Software Development Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1.1 Requirement capture and analysis . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1.2 System design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.1.3 Implementation and unit testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1.4 Integration and system testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1.5 Operation and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 The Waterfall Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3 Evolutionary Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.4 Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Introduction to OO Development 153.1 The Inherent Complexity of Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 Mastering Complex Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.1 Examples of complex systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.2 The five attributes of a complex system . . . . . . . . . . . . . . . . . . . . . . . 203.2.3 The generalization-specialization hierarchy . . . . . . . . . . . . . . . . . . . . . 213.2.4 Function-oriented and object-oriented methods . . . . . . . . . . . . . . . . . . . 223.3 The Rest of The course . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.4 Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Requirement Capture and Analysis – Use Cases 274.1 Understanding requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.1.2 Case study: Point-of-sale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.1.3 Requirements specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.2 Use Cases: Describing Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.2.1 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.2.2 Identifying use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.2.3 Writing use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.2.4 Essential and real use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.2.5 Use-case diagrams and use-case model . . . . . . . . . . . . . . . . . . . . . . . 394.2.6 Use cases within a development process . . . . . . . . . . . . . . . . . . . . . . . 424.2.7 Actors and use cases of the POST system . . . . . . . . . . . . . . . . . . . . . . 434.2.8 Summing up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.3 Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 Requirement Capture and Analysis – Conceptual Model 475.1 Conceptual Model – Concepts and Classes . . . . . . . . . . . . . . . . . . . . . . . . . . 475.1.1 Conceptual Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.1.2 Defining terms and modelling notation for a concept . . . . . . . . . . . . . . . . 49Report No. 259, July 2002UNU/IIST, P.O. Box 3058, Macau
Page 1 and 2: UNU/IISTInternational Institute for
Page 3: UNU/IISTInternational Institute for
Page 7: Contentsiii8.3 Questions . . . . .
Page 11 and 12: Chapter 1IntroductionTopics for Cha
Page 13 and 14: Introduction to Software Engineerin
Page 15 and 16: Chapter 2Software Development Proce
Page 17 and 18: Software Development Process 7Devel
Page 19 and 20: Software Development Process 9There
Page 21 and 22: Evolutionary Development 11Requirem
Page 23 and 24: ¦§¤Questions 13Source of errorEf
Page 25 and 26: Chapter 3Introduction to OO Develop
Page 27 and 28: Mastering Complex Systems 17The pro
Page 29 and 30: Mastering Complex Systems 19roots a
Page 31 and 32: Mastering Complex Systems 215. A co
Page 33 and 34: The Rest of The course 23Main funct
Page 35 and 36: Questions 253. Fred is a Dodge deal
Page 37 and 38: Chapter 4Requirement Capture and An
Page 39 and 40: Understanding requirements 29Use ca
Page 41 and 42: Understanding requirements 31Ref #
Page 43 and 44: Use Cases: Describing Processes 334
Page 51 and 52: Use Cases: Describing Processes 41B
Page 53 and 54: Use Cases: Describing Processes 43C
Page 55 and 56:
Questions 45How can you, as a requi
Page 57 and 58:
Chapter 5Requirement Capture and An
Page 59 and 60:
Conceptual Model - Concepts and Cla
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Conceptual Model - Associations 55*
Page 67 and 68:
Conceptual Model - Associations 57b
Page 69 and 70:
Conceptual Model - Associations 59A
Page 71 and 72:
Conceptual Model - Associations 61B
Page 73 and 74:
Conceptual Model-Attributes 63uses:
Page 75 and 76:
Conceptual Model-Attributes 65Keep
Page 77 and 78:
Conceptual Model-Attributes 67Desig
Page 79 and 80:
Steps to Create a Conceptual Model
Page 81 and 82:
Recording Terms in the Glossary 71R
Page 83 and 84:
Questions 73Term Category CommentsB
Page 85 and 86:
Questions 7513. Consider the follow
Page 87 and 88:
Chapter 6System Behaviour: System S
Page 89 and 90:
System Sequence Diagram 79Make Phon
Page 91 and 92:
System Sequence Diagram 81Buy Items
Page 93 and 94:
Contracts for System Operations 83d
Page 95 and 96:
Contracts for System Operations 856
Page 97 and 98:
Contracts for System Operations 87R
Page 99 and 100:
Chapter 7Design Phase: Collaboratio
Page 101 and 102:
Collaboration Diagrams 91this reque
Page 103 and 104:
Collaboration Diagrams 93msg1():POS
Page 105 and 106:
Collaboration Diagrams 95msg1()1a:[
Page 107 and 108:
Creating Collaboration Diagrams 977
Page 109 and 110:
Creating Collaboration Diagrams 99T
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Creating a new ¿-ÀÁ†ÆDÂ;Ã]
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Questions 125(a) an object Ù recei
Page 137 and 138:
Chapter 8Implementing a DesignTopic
Page 139 and 140:
Mapping a Design to Code 1298.2.1 D
Page 141 and 142:
Mapping a Design to Code 1318.2.3 D
Page 143 and 144:
Mapping a Design to Code 133public
Page 145 and 146:
Chapter 9Advanced Modelling Concept
Page 147 and 148:
Iterative Development Process 137De
Page 149 and 150:
Iterative Development Process 139Al
Page 151 and 152:
Generalisation 1410..1CashPaymentSa
Page 153 and 154:
Generalisation 143of the supertype
Page 155 and 156:
Figure 9.9: Justifying the subtypes
Page 157 and 158:
More about Associations 147Payment*
Page 159 and 160:
More about Associations 149Storeadd
Page 161 and 162:
Packages: Organizing Elements 151A
Page 163 and 164:
Modelling Behaviour in State Diagra
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Chapter 10Summing UpTopics of Chapt
Page 175 and 176:
Summing Up 165Conceptual ModelsCate
Page 177 and 178:
¢¢¢¢¢Chapter 11Coursework11.1
Page 179:
Bvis Car Hire Company: The Problem
show all

Object-Oriented Software Development with UML - UNU-IIST ...

Create successful ePaper yourself

Delete template?

Save as template?