Object-Orientation Development can be a great help when using an iterative development process. Groups of objects can be identified that are needed to provide certain functions of a system, these groups of objects can be manipulated and modified to perform certain tasks, other objects can then be added to the system in order to expand functionality. This can result in usable systems being rolled out to users with limited functions and then increased functionality being introduced later. Examples of this can be seen in the way that online interfaces offered to customers by online retailers such as Amazon, the initial user interface provided basic functions to allow users to select the product they wanted and enter their details to purchase it, over time Amazon increased the functionality of the system providing users with options such as the ability to view related products or pick alternative delivery locations. The Unified Modelling Language (UML)In recent years, UML has become the industry standard modeling language used in object-orientated design.
UML consists of a series of 13 different types of diagram; these diagrams provide formats for designers to model the various different parts of a system.
The diagrams can be split into two separate camps: Structure – Class, Composite Structure, Object, Component, Deployment & Package. These diagrams are concerned with the logical structure of a system and are used to indicate how the system will store information. Behavior – Activity, Use Case, State Machine, Sequence, Communication, Interaction & timing. These diagrams are concerned with the functionality of a system and are used to indicate how the different components of the system can work together to perform the desired tasks. Cement Mountain Ltd.
has taken the decision to implement a new information system to help them improve the service they offer to their users.
Fowler, M. & Scott, K. (2004). UML Distilled: A Brief Guide to the Standard Object Modelling Language. 3rd Edition. Object Technology Series. Reading, MA: Addison Wesley. (ISBN: 0-321-19388-7)
Maciaszek, L.A. (2005). Requirements Analysis and Systems Design: Developing Information Systems with UML. Addison Wesley. (ISBN: 0-321-204641-6) [The 1st Edition of this book will also suffice (ISBN: 0-201-70944-9)]
Bennet, S., McRobb, S. & Farmer, R. (1999). Object-Oriented Systems Analysis and Design using UML. McGraw Hill. (ISBN: 007 709497 2)
Schmuller, J. (2002). Sams Teach Yourself UML in 24 Hours. 2nd Edition. Sams Publishing. (ISBN 0-672-32238-2)
Brown D.W. (2002). An Introduction to Object Oriented Analysis: Object and UML in Plain English. John Wiley. (ISBN: 0-471-42728-4)
Booch, G., Rumbaugh, J. & Jacobson, I. (2001). The United modelling Language User guide. Addison Wesley. [ISBN: 81-7808-169-5]