A Conceptual Model of an Erp System Using Uml

Only available on StudyMode
  • Topic: Unified Modeling Language, UML diagrams, Software architecture
  • Pages : 12 (3409 words )
  • Download(s) : 418
  • Published : September 7, 2008
Open Document
Text Preview
A Conceptual Model Of An ERP System Using UML

Madhurima1(Lecturer), Madhulika (Lecturer)
Apeejay College of Engineering, Gurgaon1
Flat No.306, kaveri apptt.,GH-4,Sec-21D, Faridabad-121001
Mob no. 09350350814,E-mail-10madhurima@gmail.com
Apeejay College of Engineering, Gurgaon
madhulikabhatia@gmail.com

Abstract—In today’s competitive and ever changing environment every business demands paperless operations, a wireless communication of a result of fully transparent and automated operations of all centers in an integrated and coordinated manner taking care of the business, actions and decision demands. For this reason an Enterprise wide management support is needed. The Enterprise Resource planning is a way by which we can assess the resource needs for a given business plan to achieve required business objectives. The aim of this paper is to present the brief introduction of Unified Modeling Language (UML), its elements and benefits. Then the Enterprise Resource Planning is discussed along with its subsystems. The use-case diagram and the activity diagram of the sales order entry subsystem are implemented with the help of UML. The diagrams are created using Rational Rose Tool (Enterprise Edition).

Keywords—Business Modeling, ERP, Rational Rose, UML

1.INTRODUCTION

As the world is becoming more and more complex day by day, the computerized systems that inhabit the world have also increased in complexity. This means there are several pieces of hardware, software, connected to each other, linked to large data stores that deals with all this, how we will get our hands around the complexity. [4]

The solution for handling this complexity is to organize everything so that everyone involved in the development of the system can understand what to do, when to do etc.

The UML is the best solution for this organization.
2.DEVELOPMENT OF UML

The UML is a standard language that was conceived to assist in modeling complex software systems by using a common object-oriented notation. Originally the brainchild of Rational Corp.'s Grady Booch, James Rumbaugh, and Ivar Jacobson, the UML is rapidly becoming the de facto standard for describing and sharing system design data. For example, Microsoft has chosen the UML as its notation for its repository product to aid in sharing common software components among different third-party modeling and programming tools. Many other software vendors have lined up behind the UML, including Popkin and Platinum Technology [8]. The basic idea behind developing UML is to provide the development people with a design language that would be used for the development of computer applications. Just as we create the blueprint of a new building, similarly UML diagrams will document how software system will be built. Terry Quatrani has defined the notation as, "… the standard language for specifying, visualizing, constructing and documenting all the artifacts of a software system."[9]

The introduction of UML is by far the most exciting thing that had happened to the software industry in the recent years.

All the other engineering disciplines have a standard method of documentation.

Schematic Diagrams are used by Electronic Engineers.
Mechanical Engineers and Architects use blueprints.

Now the UML is for the Software Industry.

The UML has become a standard modeling language because it is independent of any programming language.

Precisely, UML is a graphical language for the visualization, specification, construction and documentation of the artifacts of a software intensive system, as well as for Business modeling and other non-software systems.

UML belongs to the Object Management Group (OMG) not rational, as many people believe [9].

2.1UML FEATURES

Syntax only
Independent of any language, process and tool
Properly documented
Comprehensive

The UML is just a language. It does not tell us what diagrams we should create. Rather, it tells what...
tracking img