Methodology
The information engineering (IE) methodology's main focus is on the data of the association. First, the data are represented by a data model similar as an reality relationship illustration. Second, the processes are represented by another model similar as an exertion scale illustration. The information engineering methodology supports an supposition that data should be the primary focus of a development methodology while traditional methodologies support processes as the primary focus. Figure 2 shows an illustration of an reality relationship illustration for a library.
Subscribe in to download full-size image
Figure 2. Partial reality relationship illustration.
The main difference in the traditional methodology and the information engineering methodology can be explained by order. Traditional methodologies identify the functions first and also the data. Information engineering methodologies identify the data first and also the functions. Still, some experimenters still contend that the information engineering methodology is better than the traditional methodology because data are the foundation ( first linked) for IE. These experimenters contend that data are more stable in associations than processes. So IE is a better methodology.
The primary advantage of the IE methodology is that data are linked first, also the functions are linked second. The IE methodology doesn't foster the complete corruption of the inputs, processes, and labors. In fact it can be argued that IE doesn't crescively putrefy the functions in the same way that the traditional methodologies do; this can be seen as an advantage not to have to train druggies to putrefy the functionality of the system.
The disadvantages of the IE methodology include the fact that druggies must be trained to understand the models and that druggies must be suitable to identify the data of the system first before relating the functions of the system
The information engineering (IE) methodology's main focus is on the data of the association. First, the data are represented by a data model similar as an reality relationship illustration. Second, the processes are represented by another model similar as an exertion scale illustration. The information engineering methodology supports an supposition that data should be the primary focus of a development methodology while traditional methodologies support processes as the primary focus. Figure 2 shows an illustration of an reality relationship illustration for a library.
Subscribe in to download full-size image
Figure 2. Partial reality relationship illustration.
The main difference in the traditional methodology and the information engineering methodology can be explained by order. Traditional methodologies identify the functions first and also the data. Information engineering methodologies identify the data first and also the functions. Still, some experimenters still contend that the information engineering methodology is better than the traditional methodology because data are the foundation ( first linked) for IE. These experimenters contend that data are more stable in associations than processes. So IE is a better methodology.
The primary advantage of the IE methodology is that data are linked first, also the functions are linked second. The IE methodology doesn't foster the complete corruption of the inputs, processes, and labors. In fact it can be argued that IE doesn't crescively putrefy the functions in the same way that the traditional methodologies do; this can be seen as an advantage not to have to train druggies to putrefy the functionality of the system.
The disadvantages of the IE methodology include the fact that druggies must be trained to understand the models and that druggies must be suitable to identify the data of the system first before relating the functions of the system
No comments:
Post a Comment