What is the process associated with the Unified Modeling Language?
It’s architecture-driven, and it’s incremental and iterative. Booch, Objectory, and OMT all have well-defined processes, and these are indeed sufficient for the Unified Modeling Language. Beyond that, we don’t yet specify a process. Our focus first is on a common, standard modeling language. Processes by their very nature must be tailored to the organization, culture, and problem domain at hand. What works for one context (shrink-wrapped software development, for example) would be a disaster for another (hard-real-time, human-rated systems, for example). This does not mean that we are blind to the importance of process. We do think we understand what such a process looks like, but it is unnecessary for us to bind the Unified Modeling Language to a particular process, because experience has shown that the modeling languages of Booch, Objectory, and OMT are amenable to a spectrum of different processes. Thus, we have kept in mind which artifacts are important for visualizing different as
Related Questions
- How can I find out more about the State Chart XML (SCXML) language and UML (Unified Modeling Language) 2.0 State Charts?
- What is the process associated with the Unified Modeling Language?
- Whats our schedule for the Unified Modeling Language?
- Whats our schedule for the Unified Modeling Language?
- What is Unified Modeling Language (UML)?
- What is Unified Modeling Language (UML)?
