New SOA file

Part A: JSON – based on Part 2.5

1. A reduced class diagram

2. Class diagram defining the structure you want to use to represent the data in JSON.

The employment can be painstaking as an “associative type”, sometimes it is called the relation between the class that is answerable for model connections with method and distinctiveness. connect group are characteristically planned and reconstruct by means of the study.

Till present times, to my accepting at least there is no general programming source code which is promoting the plan of relations that need obligations. As we are going to form our software completely in this manner.

The explanation of the link was calculated. We could have insert a “ List for the waiting candidates name” attribute in the “seminar course” but favored to form it in a relation because it really does: the seminar artifacts hold zero or more items from the students wait list. Attributes and connections in UML 2.0 are the similar, hence they are essentially viewed as the same kind of stuff.

Figure 1: Mapping using JSON

3.The JSON object

The following grades, as shown in figure, are done by means of transformation method.

(1) Udating Action belongs to the database of class named relation.

(2) “JSON Aysis” and “Aysis Read class”, “JSON read-object class” and model change class. (3)” Doc class” does type of data that model class has.

(4)Class name “ read”is the original class utilised for calling other classes including filling in all the file measures.

(5) The Account type is a goal configuration level, which displays get-and-getter for all characteristics. No description of other data models.

(6) The picture file output grade is FileOut that converts all binary data to JPG pictures.

Part B: XML – based on Part 2.1 – 4

1. Reduced Class Diagram

5.XML- specific Class Diagram

We create the students.dtd file as below:

<?xml_version = “1.0”?>

<!–students.dtd-a document type definition for the students.xml–>

<!ELEMENT students (student+)>

<!ELEMENT student (name,address)>

<!ELEMENT name (first_name,last_name)>

<!ELEMENT firstname (#PC_DATA)>

<!ELEMENT lastname (#PC_DATA)>

<!ELEMENT address (street,city,email,phone)>

<!ELEMENT street (#PC_DATA)>

<!ELEMENT city (#PC_DATA)>

<!ELEMENT email (#PC_DATA)>

<!ELEMENT lastname (#PC_DATA)>

To use the DTD file, we must add this code into the XML file.

<!DOCTYPE students SYSTEM “students.dtd”>

students2.xml is completed in XML file.

<?xml version = “1.0”?>

<!– students2.xml for the DTD –>

<!DOCTYPE students SYSTEM “students.dtd”>

<name>

<first_name> Rosy </first_name>

<last_name> Peterson </last_name>

</name>

<street> 56 Elm Street</street>

<email> [email protected] </email>

</address>

</student>

<name>

<first_name> Elena </first_name>

<last_name> Gilbert </last_name>

</name>

<street> 202 Dason Road </street>

<city> portsmorth </city>

<email> [email protected]</email>

</address>

</student>

</students>

7.Mapping from the class diagram

Object Diagram

As we are aware of the fact that the “object diagram” explains the operation of the specific class occurrence are integrated at run-time, it consists of the same aspects at any moment as a “class diagram”, on the other hand contain classes and connections that demonstrate connections. But a small difference exists.

Part C: Data Integration – based on Part 3.2

1. Identifying conceptual overlaps

The technical wholeness, perseverance, suppleness, revival as well as an unplanned inquiry ability also is crucial features and distinctiveness of object-oriented databases. “Object-oriented database management systems” are following frameworks of structural decomposition of object-oriented analysis, layout and coding.

The technique recommended in this work is stimulated by concern with the “object oriented model” and thus, in places where the framework object-oriented is extended, the study is more significant. However, study into varied systems integrates many similarities in the areas of overlapping elements identification, conflict reconciliation in elements and system integration.

9.Explain it in a single sentence and say how you chose to resolve it in the integrated model.

In this case we have assigned parameters in the different variable so redundancy is removed.

10. Integrated Class Diagram

Required Algorithm:

for all element “e” that is operated do

operation pre=null

for all operation p in operation list do

if p does not operate on then

continue inner iteration

else if p!=PO then

Pre:=null

else if pre=null then