Linlan Chen

– Poor performance
– Longer Duration
– Lower Efficiency
– Higher Costs

This is a good point! Thank you for sharing your opinion. Appreciate!

Yes, I definitely agree with Hanqing’s view that it will affect the data integrity if we create a new database before analyzing data, which may cause low efficiency of working. but If we analyze data before designing a new database, it will help organization to reduce errors, reduce costs, increase integrity.

Hello Karabo, I agree with you that we should understand the data dependencies and relationships between data, the process flows, how data is stored, and the rules for data processing.

Hello Dongjie, you bring up some interesting point that if the company move the data directly to database would cause some risks, such as losing data integrity and leading errors in data and applications. These risks will impact on cost and work efficiency during the database development.

Hello, Xinteng, Thank you for sharing your view. I agree with you if the company directly transfer the data to database, it will cost the company lose the data. because during this process. it may have many risk we can not control.

It is important for individual or organization to analyzed data then creating the physical database. as the question said ” they tend to start designing immediately based on their assumptions about the objects that must be tracked in persistent storage.” every creating physical database base on their assumption. if the assumption was wrong?…[Read more]

Hello Mengqiao, Thank your for sharing your opinion on the benefit or challenge when the company used modeling technique. I also agree with you that using modeling technique can help IT auditors save time and better communicate with each other. It also improve the work efficiency.

Hello Karabo, I agree with you using modeling technique can improve the work effective and decrease the rate of miscommunication.

I like your opinion on the benefit of using modeling technique. like you mentioned “it helps with the business process. It helps with expression, analysis, design, structuring, relationship, and communication. Formal modeling are important because they save time, they have unique symbols or features that represent the physical and logical…[Read more]

I agree with you, Using rough drawing techniques may increase the rate of miscommunication, if the inside communication is not good which may due to the whole project or system or some else failed.

Iyana, I agree with you that “The more effectively we can model, the better the system we can design and build.” the efficiency modeling technique can help company save time and cost.

Formal modeling diagram syntax is important for organization because it can help stakeholder better understand and analyze data. also it is easier for them to communicate. in IT environment. Formal modeling diagram is like a language to talk with each other.

If I work for a company who did not use formal modeling diagram syntax or did not pay…[Read more]

I also agree with Dongjie, if the stakeholder’s advice is different with the designed, we should find way to persuade the stakeholder and get theirs support.

Thank you James, I agree with you that when you decisions are greatly influenced by stakeholder input, it could lead to project failure. sometimes, stakeholder is the key important in projects but not every decision which stakeholder made is correct. we should analysis every situation before we do.

Well, we discuss the importance of stakeholder buy-in when staring a project. For example, I have worked for a real estate company a few years ago. Before the company start to build up, they will do the market survey. Such as how many people interested in this real estate and estimate what percentage people would buy it after the building…[Read more]

I agree with you. it is the first time jim know his team member, he need more time to fit his new situation and also introduce them to each other. it is challenging for him to adapt to new environment and project.

Hello Dongjie,
I agree with you that the schedule should the one of the risk jim will face. because people are come from different department, such as IT, marketing, operation, and customer relationship, as you said, it is challenging to find suitable meeting times for all the group members!

I agree with you that people have different background, and they present different people, if they don’t communicate well, it may cause lower working Efficiency.

Hello Mengqiao,

Thank you for sharing your idea! I agree with you that Scope risk. When the project grows in complexity as the resource of customer relationship was getting bigger and customer loyalty might develop from many aspects. With the in-depth investigation, the proposal might have to be changed again and again.

Hello Binju,

I agree with you ! Jim is new to this project and team leader and may not have fully immersed into the company culture.