Unified Modeling Language Essay

BENEFITS OF USING BUSINESS MODELS AND PRACTICES IN ORGANISATIONS.

Introduction

The purpose of this study is to discourse the benefits of utilizing concern mold ( UML ) in Information System ( IS ) administrations.

To gain the purpose of this study two academic diaries would be used and facts/s would be drawn from these diaries. These diaries will assist us sketch the benefits of utilizing concern mold in administrations.

The diaries which would be used in this study and are:

Unified Modeling Language ( UML ) Topics: The Past, the Problems, and the Prospects
Dimension of UML Diagram Use: A Survey of Practitioners.

The first subdivision of this study will be a literature reappraisal ; this subdivision will discourse concern theoretical accounts and their benefits harmonizing to certain UML practicians.

In the 2nd subdivision, I would be analyzing the diaries above and concentrating on how concern theoretical accounts are used in administrations ( Organisational UML use ) , information conveyed by utilizing UML diagrams and function of UML diagrams.

Besides within this subdivision ; the point of views of the studies would be discussed and analysed.

The concluding portion will be the decisions. This subdivision would besides integrate the recommendations.

For the intent of this study I would be concentrating on Unified Modeling Language ( UML ) .

UML is the ocular mold linguistic communication for Object Oriented ( OO ) system development ; it is derived from unifying assorted patterning methods to organize a combined analysis and design technique which today is referred to as UML.

( Siau et al, 2005: 40 )

LITERATURE REVIEW

Model

Satzinger et Al explains that ‘A theoretical account is a representation of some facet of the system being built. ‘

Business theoretical accounts are used to analyze or/and design package.

Kruchten ( 1995 ) states that ‘A complete concern theoretical account is shown in a figure of positions, similar to how a package system is modeled in a figure of positions. ‘

An analyst, in most instances a concern analyst gathers the demands of the system being built from the users ( stakeholders ) within the administration ; he digests the information and creates assorted demand theoretical accounts to showcase/convey the demands gathered at a glimpse.

The theoretical accounts are used at the assorted phases of the undertaking life rhythm depending on the methodology/information system being used.

The analyst determines the appropriate theoretical accounts to be used based on the information he wants to picture.

Eriksson, H. & A ; Penker, M. ( 2000 ) have come up with a list of slug points sketching how the concern theoretical account can assist make the package system ( s ) that best supports and tantrums into an administration.

The concern theoretical account is used in package patterning to:

Identify the information systems that best support the operation of the concern: Can be new systems, standard systems, or bequest systems.

Find functional demands: Identifies the right set of maps that the system should provide to the concern processes.

Find non-functional demands: E.g. hardiness, security, handiness, and public presentation.

Act as a footing for analysis and design of the system: E.g. Information about resources in the concern theoretical account can be used to place categories in the system.

Identify suited constituents: Modern package development makes usage of constituents ; Business theoretical accounts are a good manner to place countries of functionality and to specify the appropriate set of services.

TYPES OF MODELS

There are assorted grounds for utilizing multiple theoretical accounts ( diagrams ) to showcase the undertaking functionalities/requirements, as each theoretical account conveys different information to the intended users.

Eriksson, H. , & A ; Penker, M. ( 2000 ) explains that ‘s ‘Many development processes that usage UML advocator that the system development should get down with usage instance patterning to specify the functional demands on the system ‘

UML supports the undermentioned sorts of theoretical accounts:

Use Cases

* Static Models – Class diagrams

Dynamic Models – Activity diagrams, Sequence diagrams, State charts etc.

THE BENEFITS OF MODELS

Models makes it easier for the intended users to understand complex/complicated information that would be hard to understand when explained verbally ; It besides showcases the chief facets of the system being built so its easier for the stakeholders to understand and therefore give appropriate unfavorable judgment or feedback as to what they want the system to make and non make ( Functional /Non Functional demands ) .

Besides, another benefit of theoretical accounts is it enables the users to visualize the system/process flows and facilitates communicating amongst the undertaking squad and the users ( Stakeholders ) ; client engagement has been considered important to successful system development.
Analysis of Diaries

Journal 1: Unified Modeling Language ( UML ) Topics: The Past, the Problems, and the Prospects.

This diary gives an penetration as to what the yesteryear, the jobs and the chances of UML in the hereafter are.

One of the major benefits of UML is it is designed with a rich set of diagrammatic notations which can be used to pattern any type of package application. Hence UML can be used in a huge figure of undertakings for demands finding, analysis & A ; design and cryptography.

The author ( s ) of this diary province that there are a figure of interesting research areas/prospects on UML subjects which include:

Serviceability concerns
Cognitive affairs
Complexity issues
Web applications
Data mold and repositing facets
Modeling restraints
Model goaded architecture
Sphere mold
Component based development
Object restraints
UML ‘s function in nimble methodological analysiss
Ontology concerns
Training issues
Course of study












From the authors ‘ point of views, UML diagrams are used in assorted undertakings.

The most often used theoretical accounts are category diagrams, usage instance diagram and sequence diagrams severally whilst usage instances descriptions are the least used.

Therefore the authors challenges use-case goaded premises.

Interesting findings on UML use is discovered based on: Organizational size, undertaking size, answering experience, UML tools handiness, Industry and system type.

Contrary to beliefs, stakeholders volitionally approve the usage of UML diagrams in undertakings and are custodies on to assist develop UML diagrams.

UML has been adopted by a figure of methodological analysiss such as RUP. Methodologies help streamline a undertaking and with the expertness of UML ; it is expected to turn to organizational and project direction issues.

UML has some restrictions as with every other merchandise on the shelf ; irrespective of its restrictions, the acceptance of UML and its tools has been widespread.

Journal 2: Dimension of UML Diagram Use: A Survey of Practitioners.

This diary employs the study research scheme to look into how UML is used in pattern.

The authors ‘ belief is ; understanding current patterns can do an of import part to both theoretical and applied research on UML.

The author besides buttresses his point by adding, from a practical position, usage forms consequences to outdo patterns and understanding how the linguistic communication is used can assist back up its development.

A research was conducted in a local UML group along with about a twelve of informal interviews carried out on UML practicians.

The practicians ‘ attacks differed from one another with a rebuff or higher grade.

The usage of UML diagrams depended on how frequently the analyst used them if at all ; most of the users drew a Use instance ( Ranging from simple to complex 1s on the same information set ) .

A study was conducted to garner some informations on the respondent experience in IT.

Table 1 below shows the consequences ; the respondents have a broad scope of experience in IT field, describing up to 45 old ages and 200 undertakings.

Table 1. Answering experience in old ages and undertakings.

Another study was carried out refering to overall UML diagram use. Respondents were asked “What proportion of the object-oriented/UML undertakings that you have been involved with have used the undermentioned UML constituents?

A five point use graduated table was used which are: None, & lt ; 1/3. 1/3, -2/3, & gt ; 2/3 and All.

The inquiry focussed on diagrams used in undertakings and non diagrams used personally by respondent as respondents tends to specialize in utilizing specific UML diagrams dependant on their occupation role/types of undertaking involved in/expertise.

Table 2. UML diagram use

From the tabular array above, 44 % of respondents study that usage instance narrations are used in tow-thirds or more of their undertakings.

Class diagrams were the most often used, with 73 % use in two-thirds of their undertakings.

Use instance diagrams and sequence diagrams were ranked 3rd and 4th severally.

Role of UML Diagrams

The chief function UML plays during System Development Life Cycle is it facilitates communicating amongst the undertaking squad and stakeholders.

Harmonizing to the study conducted, the consequence showcases the utility of all UML diagrams in relation to verifying and formalizing user demands.

A usage instance diagram provides an overview of the system being built. Based on the study as discussed earlier, category diagrams are noted as the most utile and most used UML diagram.

A study inquiry was posed to the respondents “How successful has the UML been in easing communicating with clients” ?

The average consequence was 3.28 with the graduated table being a 5 point graduated table 0 to 5 ( Not to really successful )

Recommendations

On the issue of complexness as this has been one of the restrictions of UML diagrams, the linguistic communication could be simplified to extinguish this restriction.

In add-on, some work and research might necessitate to be carried out in order to simplify the UML diagrams which might include modifying the diagrams, sentence structure and notations.

Besides based on my findings coaction and province diagrams are used less frequently in comparing to category diagrams as illustrated in Table 2, so these diagrams could be eliminated to do analyst dressed ore on the other UML diagrams.

Promoting stakeholders to take part in development and reappraisals of artefacts would be good to the analyst and in bend would be good for the administration as it would assist extinguish bringing of a incorrect system which wastes capital, resources, manpower and more significantly clip.

Decision

Pender ( 2003 ) states that UML has quickly become the de facto criterion for patterning object-oriented systems development.

With the assistance of the diaries used ; we have been able to analyze the benefits of concern theoretical accounts. From this, I am able to pull my decisions on how utilizing concern theoretical accounts would profit organisations/individuals and besides look into why concern theoretical accounts are used and non used in administrations.

We were able to happen out from the diaries that most respondents specialise in One or two UML diagrams and do non trouble oneself larning others due to the fact they believe there is no demand for it. However, the diaries explains that each theoretical account has its ain usage and is used based on what the analyst would wish to show/ analyst discretion.

Business patterning diagrams shows the intended user activities performed in a system at a glimpse and creates room for ideas as the diagrams are visualised by the users and tends to lodge in their memory more than when it was merely a verbal conversation.

Surveies shows worlds are more likely to retrieve what they see ( graphical diagrams ) and perceive than when they hear or read.

Mentions

Batra, D. ( ) Unified Modeling Language ( UML ) Topics: The Past, the Problems, and the Prospects. Journal of Database Management.

Dobing, B. , & A ; Parsons, J. ( 2008 ) . Dimensions of UML diagram usage: A study of practicians. Journal of Database Management, 12 ( 1 ) , 4-14

Eriksson, H. , & A ; Penker, M. , 2000. Business Modeling With UML: Business Forms At Work. New York: John Wiley & A ; Sons, Inc

Jackson, R. , Burd, S.D. & A ; Satzinger, J.W. 2004. Object-Oriented Analysis and Design with the Unified Process.Course Technology Inc

Kruchten, P.1995. The 4+1 View Model of Architecture. IEEE Software, IEEE.

Pender, T. ( 2003 ) . UML bible.Indianapolis, IN: Wiley Publishing.

Siau, K. , Erickson, J. & A ; Lee, L.Y. 2005. Theoretical V. Practical Complexity: The Case of UML. Journal of Database Management.16 ( 3 ) , pp. 40-57