A Conceptual Model of an Erp System Using Uml

“During the object-oriented analysis (OOA) phase object-modeling techniques are used to analyze the functional requirements for a system and create models which reflect the logical design of the system. During the object-oriented design (OOD) phase of the system, models are elaborated upon to include implementation specific details that show how the physical design of the system will come together. OOA focuses on what the system does (its static structure and behavior), OOD on how the system does it (its run-time implementation).”

This step creates model of the software system based on the stockholder’s requirements, then requirements are analyzed again to produce a fine model of the software

Logical and physical models represent the key elements and processes of the software development. The logical model describes the processes, and data, in as much detail as possible, without giving regard to how the system will be implemented. Logical data models include

Here the model depicts five use the logical view, the process view, the physical view, development view and use case view. These views of the system are concurrent and each offers its own

As design moves forward, the development teams begin to generate a tremendous amount of detailed information about the system. Modules, classes, data fields, data structures, forms, reports, methods, subroutines, and tables are all being defined in substantial detail in the design model. The key design tasks are decomposing the application into layers, clients, and servers, distributing the “pieces” across hardware platforms, and defining the physical network and protocols.

UML which stands for Unified Model Language is a developmental modelling language that allows the user to specify and visualise document models of software systems. UML comes in a large amount of tools that allow you to analyse your applications future requirements and develop a solution to achieve these requirements. The current version of Unified Modeling Language version contains thirteen different types of diagrams that can be separated into three categories: Structure Diagrams and Behaviour Diagrams and Interaction Diagrams.

for the logical design model, segments an application's components into three tiers of services. It

Change Vision, Inc. in 2006 as a vendor of modeling tool "Astah" (earlier know as JUDE). From that point forward, Astah has been picked and embraced in the embedded system development, enterprise software development, software development trainings and many academic establishments to show UML with because of its "ease of use".

It is very difficult to represent the architecture in the set of boxes and arrows which shown on these diagrams.So as the remedy,author has proposed the description of a software architecture using several concurrent views,each one address one particular set of concerns.

The (UML) Unified Modeling Language is a general-purpose modeling language in the field of software application design, which is developed to supply a conventional means to envision the design of a system. It was produced and created by James Rumbaugh, Ivar Jacobson and Grady Booch at Rational Software during 1994-95 with additional advancement led by them with 1996. In 1997 it was embraced as a basic by the (OMG) Object Management Group, and has actually been handled by this company since. In 2000 the Unified Modeling Language was likewise approved by the (ISO) International Organization for Standardization as an authorized ISO specification. Ever since it has actually been regularly modified

The Unified Modeling Language (UML), with its fourteen various diagram types, is a standard notation for the modeling of real-world objects as a first step in developing an object-oriented design method. Although a lot of semantics in the UML, we can widely describe in the more details the system that will be developed, but we cannot make sure the correctness and consistency of the designed model. Therefore, it is important to reduce the error from verifying user model in the early phase, When those errors are discovered early in the design process it is easier and more cost helpful to fix than if they were discovered at a later phase. The issue of consistency and inconsistency have appeared since its infancy of the software development. These problems are bigger still in UML software development, and are mainly reason of the presence of multiple-views (models) for the same system, and It can contain potentially contradictory system specifications. In other meaning, the UML diagrams describing a software must be consistent because inconsistencies between all diagrams in UML It will be the source of the increase defects and errors in the software systems. It is therefore important that these inconsistencies be detected in the system, analyzed and hopefully fixed before implementing it. Without consistency analysis, it would be hard to evolve the model and ensure that the collaborative effort is coherent. Although there are a lot of research and studies that focus on the

The Unified Modeling Language (UML) may be a graphical language for visualizing, specifying, constructing, and documenting the artifacts of software-intensive systems. UML provides parts and functions to support the need of complicated systems. UML follows the item destined ideas and methodology. Therefore object destined systems square measure typically sculpt risqué mistreatment the pictorial language. The UML has a vital role during this Object Oriented analysis and style, The UML diagrams square measure wont to model the look. That the UML has a vital role to play.

A key requirement of the software design of a computer-based system is to transform basic requirements into an architecture that describes the software 's top-level structure and identifies its components. Accomplishment of this requirement is through architectural design, providing a blueprint for developing the framework of the software (Mattsson, Lundell, Lings, & Fitzgerald, 2009). The establishment of the framework involves examining the software requirements document and designing a model for providing necessary implementation details. The details specify components of the system along with all inputs, outputs, functions, and the interactions between the components. This paper includes a description of the architectural design of a computer-based system that has transform characteristics, and includes a data flow diagram with process narrative, and evaluation of the architectural design. Further, an assessment of the structuring requirements associated with software architecture is included.

The main advantage of this approach to benefit from the UML standard modeling notation and the training done with software engineers to model the software with the UML notation

Context diagrams are important to software engineering as it provides overall view of the system and the interaction among entities, different elements of the system. It ensures that entities in the system belongs to the system and thus help in development and refactoring of system completely. Context diagrams should be developed and analyzed before any system is refactored. Since in context diagram we know the inputs and outputs of the system we can predict how the system works and anticipate any errors, and if any output is not got from input We can easily make out whether the system is working properly or not for particular interval or not and thus it improves safety and reliability.