Revision as of 16:55, 8 June 2014 edit MadScientistX11 (talk \| contribs) Extended confirmed users 4,453 edits Undid revision 611475563 by JaniDev (talk)These steps are not the same in all methodologies. Many use different names and some processes (e.g. Agile) avoid the traditional division of sequential step ← Previous edit		Revision as of 14:08, 19 July 2014 edit undo Monkbot (talk \| contribs) Bots 3,695,952 edits m Task 5: Fix CS1 deprecated coauthor parameter errors Next edit →
Line 8: *Abstraction. A goal of most software methodologies is to first address "what" questions and then address "how" questions. I.e., first determine the functionality the system is to provide without consideration of implementation constraints and then consider how to take this abstract description and refine it into an implementable design and code given constraints such as technology and budget. Modeling enables this by allowing abstract descriptions of processes and objects that define their essential structure and behavior. Object-oriented modeling is typically done via [[use cases]] and abstract definitions of the most important objects. The most common language used to do object-oriented modeling is the [[Object Management Group\|Object Management Group's]] [[Unified Modeling Language\|Unified Modeling Language (UML)]]. <ref>{{cite book\|last=Jacobsen\|first=Ivar\|title=Object Oriented Software Engineering\|year=1992\|publisher=Addison-Wesley ACM Press\|isbn=0-201-54435-0\|pages=15,199\|~~coauthors~~author2=Magnus Christerson, \|author3=Patrik Jonsson, \|author4=Gunnar Overgaard }}</ref> == References == {{reflist}}

Object-oriented modeling: Difference between revisions