Ami Parekh

I think you mention great points regarding some difficulties people would face if they were visually impaired. I feel like the alternative you mention are easy to implement and very practical and useful. I also like how you tied in your example to the case we have been working on in this class. Making sure On the Spot Courier has digital devices…[Read more]

A accessibility issue that could be faced with people who are diagnosed with muscular atrophy and distrophy is trying using a traditional keyboard. Muscular atrophy is when the muscles deteriorate and the patient effected cannot move or use their muscles to their full ability. A way user interfaces can accommodate people with this disability are…[Read more]

I think your description and suggestion of prediction software available for students/children who have learning disabilities is a great idea. These tools would enhance the experience for students and help them with the learning process. I think Temple may have the resources in place already but definitely should consider adding more facilities to…[Read more]

I think you bring up a good point suggesting that both senior management and stakeholders should be involved when deciding on database design and the creation process. I think you mention good points regarding security as well. Having password protection, encryption, and regular audit are good ways to make sure there are no gaps in coverage.

I agree with you that designing a database is a collaborative effort. Everyone involved has special skills that can help with database design in the most effective way. You also did a good job explaining the different methods of data encryption and their scalability.

I think you are correct with your idea that a database needs multiple people working because it has a lot of moving parts.

I think you make a solid point defining that all business practices are different therefore require multiple diagrams to make sure they are depicted correctly.

I think you bring up a good point about cross checking and how doing so will help with finding discrepancies within UML diagrams. Putting this idea into practice will help solidify the diagrams and make sure all users are on the same page.

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.