Week 3

                                                               UML

1. The unified modeling language is basically used for visualizing and documenting software system design and a object oriented design but the thing is it is an independent and specific programming language he primary goal of this work is an assessment of UML’s expressive power for modeling software architectures in the manner in which a number of existing software architecture description languages (ADLs) model architectures. This paper presents two strategies for supporting architectural concerns within UML.and can be used in business process too.

 

2. In the information system development the UML is used in many ways like in construction for making a sequence diagrams for the requirements checklist and fact finding also. In this we know what the information do user and the managers need from the system what is risk, budget, and security issues and timetable constraints for system development. Who, where, when, & how.

 

3.  The journals:

1.      A significantly higher level of precision in the definition of the language—this is a result of the need to support the higher levels of automation required for MDD. Automation implies the elimination of ambiguity and imprecision from models (and, hence, from the modeling language) so that they can be transformed and analyzed by specialized computer programs.

2.      An improved language organization—this is characterized by a modularity that not only makes the language more approachable to new users but also facilitates inter-working between tools.

3.      Significant improvements in the ability to model large-scale software systems—some modern software applications represent integration of existing stand-alone applications into more complex systems of systems. This is a trend that will likely continue, resulting in ever more complex systems. To support such trends, flexible new hierarchical capabilities were added to the language to support software modeling at arbitrary levels of complexity.

4.      Improved support for domain-based specialization—Practical experience with UML demonstrated the value of its extension mechanisms. These were consolidated and refined to allow simpler and more precise refinements of the base language.

5.      Overall consolidation, rationalization, and clarification of various modeling concepts resulting in a simplified and more consistent language—This involved consolidation of concepts, removal of redundant concepts, refinement of definitions, and the addition of clarifications and examples.