Ami Parekh

I think you do a great job explaining the differences between each UML diagram and how each is connected to one another. Though I agree that creating a “new” diagram can help with the revising of the “old”, I think the “old” can decrease the amount of time it will take to develop the “new” because the actors, attributes, and actions will already…[Read more]

I think something important you mention is that making sure the main data requirements are the same. If secondary activities or attributes are different in a class diagram, it may not be as detrimental if there are some discrepancies.

I agree that it is possible to have multiple correct answers to a class diagram if all of the information mentioned in a narrative is considered and used correctly. Furthermore, evaluating attributes, logic, and relationships is a good idea for consistency.

I think your point sums up the idea very concisely and wholly. Different class diagrams can be correct as long as they have certain qualities that are the same.

Hi Iyana,
I think you bring up some great points of how we can assess and evaluate class diagrams objectively. Furthermore, as you mentioned, many class diagrams can be correct even if they look different as long as they use correct syntax and display the cases correctly.

I like how you mentioned the big data example for a time where data may not need analysis before database design. This is something I had not considered but is logical. I also agree, when moving to a new system, integrity may be lost if data is lost.

Hi Mahroo,

I like how you explained the idea that data modeling is not a workflow but rather an iterative process. Furthermore, the benefits you mentioned are some I had not thought of before but can see as being beneficial to companies.

I totally agree with you! When it comes to a project, it can be detrimental to go straight to solution without fully understanding and analyzing the problem. Doing the correct steps early on can save the company money, resources, time, and heartache.

I agree with you. Organizations should definitely analyze data before database design to reduce costs and errors. How do you think it will increase integrity? Can you explain this further?

I feel that moving straight to design once hearing the general requirements and viewing the data is not the most efficient way to handle this scenario. Doing this would be moving to finding/building a solution even before the problem has been fully established. This could waste time because if components from the data were missed during the design…[Read more]

I think your point regarding how different people interpret data is an important one. Having uniformity for this reason alone should be enough to make any organization want to use formal modeling processes. Furthermore, your reasoning explaining how formal processes can make the job of an auditor easier and more effective is a good one.

I agree with you. Formal techniques can make communication significantly easier and more effective. I like how you mentioned that uniform modeling techniques may also help with data analysis. I did not think about this before, but it does seem plausible.

I think what you mention in your post is very true–the more effective a model, the more effective solution can be delivered. I also feel that training new members with the new formal modeling techniques is a great idea. If new employees are taught these practices right off the bat, they will be able to implement them into their work more…[Read more]

I think you bring up some important points on the benefits of implementing a uniform, formal modeling tool within an organization. It would definitely save time and increase level of understanding. Furthermore, as you mentioned, using formal methods would help with moving along the business process.

Formal modeling techniques are important for an organization to use and recognize because using them would ease communication within a firm. If a firm is using informal methods, there is an increased chance of miscommunication between team members. Having a formal technique is like having a designated language to complete the tasks.

If I was…[Read more]

I think the methods of integration you mentioned above for different ways IT and the business can be woven are great. I think going with reciprocal integration would be the best idea for this type of scenario.

Hi JIng,

I think your points are fantastic and really capture some necessary steps that will need to be taken by the development team to make sure both IT professionals and business professionals have an understanding. Understanding corporate culture and using it to align business and IT goals is a great suggestion because most of the time this…[Read more]

I think you make some good points about IT and Business alignment. I also think risk and cost/benefit analyses are a good approach to coming to an agreement when deciding if a project is feasible.

I feel that both IT and Business professionals need to come to a consensus before the project even begins. In a book I am reading a quote that I found interesting is “consensus does not mean everyone agrees, it means everyone can support the solution.” This is important for both business and IT professionals to remember especially during initial…[Read more]