DIAGRAMME DE FLUX MERISE PDF
27 déc. Le diagramme de flux de données (DFD ou Data Flow Diagram) pour définir les données traversant un système et leurs traitements éventuels. Exercice Merise – Download as Word Doc .doc), PDF File .pdf), Text File .txt) or read online. Construire le MCC (diagramme de flux), 2. Présenter le modèle. 25 oct. Figure I Découpage traditionnel des flux de matière et d’information dans la chaîne. Figure I La Figure III Diagramme de séquences – Optimisation des maillons de la chaîne. Figure III . MERISE .
|Published (Last):||18 November 2012|
|PDF File Size:||16.47 Mb|
|ePub File Size:||9.95 Mb|
|Price:||Free* [*Free Regsitration Required]|
The present invention relates to a method for modeling reference data of an information system ISas well as an algorithm based on this model, allowing the location of reference data fields of a system ‘information. L’invention concerne donc le domaine des techniques logicielles. The invention thus relates to the field of software techniques. In an organization, SI is formed by the set of all elements that contribute to treatment and information flow within the organization database, application software, procedures, documentation, etc.
Modeling an IS IF involved in the design phase and is to create a virtual representation of the business processes of an organization as well as inventory and information flows illuminating these processes. This is a computer analysis method dedicated to the establishment of an IS. MERISE method is based on the separation of data and processing to be performed in a number of conceptual and physical models.
Among them, the Conceptual Data Model CDM or allows for a clear representation of the data of the IS and defines functional dependencies of data between them. So this is a representation of data, easily understandable for writing SI using entities. An entity is a representation of a material or immaterial element having a role in the system that is to be described.
The entities of the same type, that is to say the definition is the same, are grouped in a set called feature class. Semantic links may exist between several entities. Also, relationships are defined to represent these semantic links and a relationship class contains all of the same type relationships thus linking the entities belonging to the same feature classes.
However, data modeling proposed in a Conceptual Data Model from the Merise method does not translate the repository notion of a given or a relationship between two data. This notion of referential data is extremely important in an IF, and particularly with a view to create or develop urbanism of an IS.
In addition, SI, to remain efficient and improve its services, must necessarily grow at the pace of development of the organization and the evolution of its strategy. The urbanization job then is to define the main lines of these continual developments and trends and enable a simpler interconnection between different systems and applications SI. Also, in this context, the Repository concept of a given or a relationship between two data is very important to optimize the urbanization of SI.
Indeed, each applying an IF which has in its repository, referential data must be able to offer client applications.
This notion of data offering by a customer to supplier obviously impacts the functional planning of the SI. Now the Conceptual Data Model derived from the Merise method does not represent homogeneous groupings of data or dependency relationships between these groupings useful representation of the repository concept. This method does not allow the construction of a model based on principles based on the reference data of an IS and is therefore limited to the optimization of the operational planning phase of an IS.
In addition, data modeling proposed in a Conceptual Data Model from the Merise method is also limited in diagrammf it does not allow for new data of IF, locate deposits of reference data. This is yet again a very important feature in order to optimize the urbanization of SI. Also, in view of the above, an object of the present invention to provide a method of data modeling of SI which overcomes the disadvantages of the aforementioned prior art, particularly that provides a mapping of repository notion of a dependency relationship between data and data themselves.
Another object of the present invention to provide a method of locating deposits reference data for new data of an IS to support the principles of the proposed modeling method, fe determines what data repository that is to say, under the responsibility of any application, must be given referential.
To do this, the invention proposes to apply the concept of object modeling UML, acronym for “Unified Modeling Language” for modeling reference data of an information system. The invention therefore relates to a referential data modeling method of an information system, characterized in that it is based on a UML modeling reference data of merisr information system SI listed in application data fields any referential data of the information system being defined by a specialized concept inheriting characteristics of a generic concept, said method comprising the steps of: According to a feature of the invention, the grouping of categories according to a predefined typing is to define categories related to feeds grouping generic concepts and specialized concepts that have a life cycle exactly corresponding to that of a process, categories related inventory grouping generic concepts and specialized concepts that change state after activation of a stream and have an unlimited life cycle to that of a process, and coding categories grouping generic concepts for referencing information related to flows or stocks.
Preferably, a UML dependency relationship between a flow type of category and a category type of stock is directed to the type of category to category flow type stock.
Preferably, a UML dependency relationship between meeise flow type category or a category type stock and a coding type of category is oriented in the flow type category or type of stock to the coding type of category. In an embodiment in which two reference data are related, said relationship resulting in a UML metise relationship between membership categories of the two generic concepts including specialized concepts corresponding to said reference data inherit, said UML dependency relationship is oriented, taking as origin the membership class of the generic concept corresponding to the referential data whose data field comprises the referential data containing the relationship between said pair of reference data.
The invention also relates to a method for locating reference data fields of an information system, characterized in that it comprises an implementation step of modeling the reference data of the information system according to the principles defined above and in that it comprises the following steps: According to one embodiment, the orderly course of the diagram is made of flow type categories to the coding type categories.
Advantageously, the method comprises the following steps: According to one characteristic of the invention, the step of locating the reference data field associated with a category of designating the responsibility of any application is the reference data related to said category.
Other features and advantages of the invention more clearly from the description given below, for information only and in no way limiting, with reference to the following figures wherein: UML is a modeling tool consisting of an object approach. Also, such a model may seem a priori inappropriate where we want to manipulate data, the functional approach is more intuitive in this case.
It is precisely a strong principle of the invention to go against this prejudice by applying concepts from the UML notation for modeling reference data of an IS.
Also, in this context, any data of an IS can be interpreted as the implementation of a specialized concept UML class stereotype. The specialization of a generic concept is then to be foux of merlse urbanism of an IS. Specialization is a concept related to inheritance in UML notation. More specifically, inheritance is a relationship between classes that allows the definition and implementation of a class based on other existing classes.
Thus, the fulx relationship allows a class to reuse attributes and methods defined for a more general class. For example, if one takes in the context of a company can define a generic command line entitled concept. This can, in a first case, be diagtamme by segmenting customer market business, consumer or by technology products or services of the company’s commercial catalog analog, digital, The invention advantageously proposes to use a UML possibility for achieving homogeneous groupings of data.
Thus, the various concepts defined are grouped into categories according to logical criteria. These categories can be represented by the concept of UML package. An important feature of the invention then consists in building a category diagram where categories are grouped according to a predefined typing of these categories.
This typing classes of an IS according to the invention, and therefore the content concepts or corresponding data to specialized concepts is defined as follows in conjunction with Figure 1: With reference to Figures 2 to 5, a first embodiment of the invention is described using UML modeling data to describe the reference data of an existing SI and deposits.
In this example, the SI corresponds to that of a business, and data repository is any location of data that can be a valuable source on the informational level, such as corporate databases, files, etc This embodiment of the invention is that an existing SI in which, for planning purposes, the description of the reference data and their deposits is required. The flow studied in this example is of the order from a supplier, a customer already has a business park for the manufacturer and an account diagrwmme him.
The command, as dee Business Park are referenced by a commercial catalog.
Forme de modélisation Merise
From the typing of categories provided by the present invention is obtained, with reference to Figure 2, a first diagram of the manipulated categories: A flow type category F is defined as the class order, S stock type category is defined as the customer category, Commercial Customer Park and Customer Account, and a type of category coding C is defined as the category Commercial Catalog.
The various categories thus defined are linked with one another on the diagram by UML dependence relations each materialized by one or more reference data SI. UML dependence relations are schematically by the dashed lines in the figures. Once this grouping categories by typing done, an essential feature of the invention is to bring coherence to the groupings of generic concepts in the same category with the data fields of IS applications.
This coherence is defined by applying the principle that the reference data defined by the specialized concepts inheriting generic concepts of the same category and with the same specialization must belong to a data repository and a single application. However, in our example the category related to stock S contains specialized concepts whose corresponding reference data belong to different fields in the SI. The reference data related to the Client are in a supplier’s customer management application, those related to the Commercial Customer Park are in specific control applications to technology and those related to the Customer Account are in a billing application.
From the principle described above, the definition of categories becomes one shown in Figure 3: Thus, according to the invention, the generic concepts of a class must define reference data belonging to a single data repository, that is to say to the deposit of the same application.
Another important step of the process according to the invention is to define a direction for UML dependency relationships binder categories therebetween. The orientation of the relationships between categories, previously only dependent on the relationships between data SI studied, was first linked to the typing of these categories. Thus, according to the invention, the orientation of relationships from the typing is defined as a UML dependency relationship between a flow type of category and a category type of stock is directed to the type of category flow to the category of type of stock, and a UML dependency relationship between a flow type category or a category type stock and a coding type of category is oriented in the flow type category or type of stock to the coding type of category.
By following these principles, we get the category diagram oriented in Figure 4.
Thus, the orientations of UML dependence relations having as end the type of flow control class F represent this category type flows as origin. In these dependency relationships with the category Command taken as the origin, the categories S1, S2 stock type, respectively Commercial Client and Customer Park as well as Category C type coding Commercial Catalog, are target groups.
Finally, the direction or orientation of a UML dependency relationship between categories also depends on the deposit of the referential data containing the relationship.
Indeed, if two reference data are related, this relationship has resulted in a UML dependency relationship between membership categories of the two generic concepts including specialized concepts corresponding to said reference data inherit.
The UML dependency relationship is then oriented according to the invention taking as origin the membership category of generic concept corresponding to the referential data including the data repository includes referential data containing the relationship between the two reference data.
In other words, if the referential data containing the relationship between two referential data D1 and D2 is in the same field as the referential data D1, then the dependency relationship between the corresponding generic concepts, CG1 for D1 and CG2 for D2 is oriented towards CG1 CG2.
Thus, this is the application which is located the bearing of the referential data D2 which must provide, via for example a service, the application containing the referential data D1 in its field and not the reverse.
Meaning of “merise” in the French dictionary
The repository concept for a relationship between data is then translated as a relationship between UML oriented generic concepts dependency under the responsibility of the generic concept of the original dependency. This orientation between generic concepts refers immediate way between their categories of membership in the form of dependency relations oriented in the same direction.
The consequence for the planning of an IS is to describe, for existing IF, or set for a change of SI, which applications must provide data to other IS applications.
Thus, the definition of meaning to the dependency relationships between classes related to the repository concept based on the principle described above, allows to complete the figure category diagram of the 4 SI modeling data for the chart of Figure 5.
It is the application that the deposit contains the referential data describing a customer must provide this data to the application that the deposit contains the referential data describing a customer commercial fleet.
Similarly, it is the application that the deposit contains the referential data describing a customer account which must provide diagramms data to the application that the deposit contains the referential data describing a customer commercial fleet.
In support UML modeling principles defined in the description above with reference to Figures 1 to 5, the present invention also relates to a method for locating the reference data deposits.
This second aspect of the invention is described with reference to Figure 6 illustrating a category diagram relating to an IF consists of a box office software, more commonly known software package “front office” according to English terminology, and a billing software package that implements respectively ordering and invoicing flows.
The location method according to the present invention requires entry into a category diagram where all dependence relationships are aligned with the previously defined principles. The chart categories 6 is therefore developed according to the principles defined by the UML modeling reference data of an IS according to the present invention. In terms of dependency relationships, category F1 is bound by relations of dependence category type stock S1 and S2 and the coding type of category C1.
According to the principles governing the orientation of dependence relations seen above, the meaning of these relations originates category F1 and as a target categories respectively S1, S2 and C1. Class F2 is linked by a relationship of dependency with the type of category S3 stock.
According to the principles governing the orientation of dependence relations seen above, the direction of this relationship originates category F2 and S3 as the target categories. Category S1 is bound by two dependency relations respectively to the categories of stock type S2 and S3.
According to the principles governing the orientation of dependence relations seen above, the meaning of these relationships has its origins as the category S1 and S2 and S3 target categories respectively. Finally, the category S1 is linked by a relationship of dependency codification type of category C1. According to the principles governing the orientation of dependence relations seen above, the direction of this relationship originates category S1 and C1 categories as target.
To locate data fields referential matching specialized concepts that belong to the same category, the method according to the invention proposes to effect an orderly course of diagram categories, starting with the flow type categories to categories type coding.
The location reference data deposits made to support an ordered course as defined, is based on an algorithm implementing the steps of: The steps of the localization algorithm of locating the reference data deposit associated with a category is to actually designate the responsibility of what application is reference data related to search.