Derrick A. Gyamfi

Hi Jing,

Very short and concise post, I think your comment provides a different perspective on the technical nature of class diagram evaluation and modeling. Thanks for sharing!

Hana,

You bring another great point in the “correctness” of a diagram. I agree that diagrams will be different as a result of the different understanding of the narrative. However, if the narrative is misinterpreted – does this make the diagram wrong, even if it meets all the necessary data requirements?

Casid,

Very well written and concise post – I think you hit the nail right on the head. The adherence of the class diagram to the data requirements is the most important aspect of the narrative.

Berel,

Great point bringing into perspective the potential of logical errors in the class diagrams. I had not thought about this when making my initial post but I completely agree with you. Kudos!

Hi Sarush,

Great idea referencing the class diagram back to the business requirements. It is easy to forget the business requirements of any IT system diagram while trying to meet the necessary data and technical requirements. Great connection!

It is possible that each class diagram can be correct. This is because although class diagrams may vary be design as a result of the diversity of thoughts and perspectives – it is possible that all class diagrams will capture the necessary data requirements. These requirements include:
1. Identify and Model Classes – An analysis of the i…[Read more]

Ugo,

I like how listed and explained the importance of data analysis in the designing of a project. I think this is well-defined and a great contribution to the posed question. Thank you.

Yijiang,

I agree with your point the effectiveness and efficiency of the project deteriorating as a result of no formal analysis. However, this also leaves me to wonder – what if the scope of the project does not require an analysis?

Hi Dongjie,

Great job listing out the benefits of formal analysis. It is clear and very easy to follow. Kudos!

Hi Ami,

Great idea identifying the risk of not meeting the requirements. I think this is very viable since prior analysis will easily mitigate this risk. Thanks!

Hanqing,

Great thoughts in regards to the impact of non-analysis on data integrity. As auditors, we know how important the integrity of data is so it is quite imperative to always make that connection. Thanks!

Iyana,

Thanks for sharing your ideas about the timeliness of things. I also think this will be great in enticing an organization to adopt a standard modeling technique. This is because if an organization understands that their lack-of is inhibiting them from making the necessary forward steps towards their said strategic mission, vision, and…[Read more]

Rouying,

Great analogy relating the use of formal modeling techniques to the use of languages. I think this hits the nail right on the head in much simpler terms. Thanks!

Aaron,

Great idea in discussing the streamlining of communication within organizations by employing standard modeling techniques. However, this also leaves me to think, what if as an IT auditor, each organization we audited had its own internal standard modeling technique?

Yijiang,

I think it is great that you identified the ease of identifying vulnerabilities in the organization’s systems during IT audits. I think this can also be used as a method to entice an organization to adopt these techniques. Thanks for sharing.

Zhixin,

Thanks for sharing. I agree with your benefit of formal modeling techniques allowing for high-quality modeling of processes and systems. It is always important to have something standard and formal rather than rough drawings of techniques.

Formal modeling techniques are important in various ways including:

1. Uniformity:

2. Ease of Communication

3. More Informative Models

If I was working with an IT organization that has not adopted a formal standard for process modeling, I will explain the importance and monetary benefits to them to entice them to adopt one.

As an IT…[Read more]