Xiaomin Dong

Nice explanation of each deployment methods of system, Organization should consider the values that each methods brings to us based on the variety of factors.

Nice point. Organization should consider do things within their capabilities. Deploy a system is not a moment, it has long way to go.

I totally agree with you. Cost, urgency, complexity and experience are really importance factors when considering deployment of a system.

In terms of two systems be run in parallel, it has pros and cons. The pros are parallel running allows results to be compared to ensure that the new system is working without any errors. If errors are found, user can refer to the old system to resolve the problem and make modifications to the new system thus operation can continue under the old…[Read more]

Nice point. I would recommend the AWS as well, not only from the cost perspective, but also the consideration of security controls.

I would like to recommend the Amazon Web Services (AWS). AWS provides on-demand cloud computing platforms to individuals, companies, and governments. The technology allows subscribers to have at their disposal a full-fledged virtual cluster of computers, available all the time, through the internet. The fees are based on a combination of usage,…[Read more]

Nice point. Emphasis is placed on the need for the implementation of “quality” information models to facilitate an integrated manufacturing environment. How information models are used to define data requirements and how, in a practical application, information models enable information sharing and exchange are described.

I agree with you. If I am working with an IT organization that has not adopted a formal standard for process modeling, the following might be my advice to entice them to do so.

Well said. Effective and efficient information sharing and exchange among computer systems have been critical issues.

Nice point. The data integrity is really important. In most companies, there are areas where important business decisions are routinely made based on data.

Well said. the risks that a project bypasses the formal analysis maybe a data leaks, deployment failures, the abuse of database features, hopscotch, broken databases, so and so forth.

Great point. In my opinion, the way that the developers start designing immediately based on their assumption about the objects that must be tracked in persistent storage is not appropriate and efficient.

Well said. during physical design, people transform the entities into tables, the instances into rows, and the attributes into columns.

I agree with you, the purpose of building a physical design of the database is to optimize performance while ensuring data integrity by avoiding unnecessary data redundancies.

Nice point, even if we draw a class diagram from the same narrative descriptions, we may have different interpretation of it.

Nice point, even if we draw a class diagram from the same narrative descriptions, we may not have different interpretation of it.

Nice point. In my opinion, we could also evaluating class diagrams by look at the cohesion and coupling in the diagrams. It is best to have classes that are loosely coupled and highly cohesion.

Well said. Even if we draw a class diagram from the same narrative descriptions, those class diagrams could not be all correct.

I agree with you. as the saying goes, there are a thousand Hamlets in a thousand people’s eyes.

I agree with you, a CRUD diagram shows what types of processing is performed on data by a system, indicating them in a matrix format for each function.