Think about how people would behave if they experience problems with the program or an app on their computer or mobile device. Think about the numerous options available to customers who are frustrated by these problems. You're fuming because of an issue with some kind of program or application. So, what do you think? In what ways did you make the necessary adjustments to fix it?

Think about how people would behave if they experience problems with the program or an app on their computer or mobile device. Think about the numerous options available to customers who are frustrated by these problems. You're fuming because of an issue with some kind of program or application. So, what do you think? In what ways did you make the necessary adjustments to fix it?

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Similar questions

Integrity testing is a waste of time, according to your supervisor. Not necessary if each app is fully tested separately. Continuing system testing as soon as possible is the recommended line of action. At that time, we will fix any modules that don't interact appropriately. Do you agree or disagree with the following statements? Your answer should be explained.
Think about the difficulties you'll have as you build the framework, and look into the specific problems and setbacks you'll encounter with each proposed answer. Is it possible that moving all of our computers to the cloud will make it easier to deal with these sorts of things? Is it important enough to include, or can we ignore it for the time being?
You are eliciting needs for a new version of an existing product that is currently under development. List one elicitation method that would be effective in addressing each of the needs elicitation issues mentioned in the next section (one technique per problem). Explain briefly why this approach is appropriate in this situation. Rather of just listening to what users say they do with the current system, you should investigate how they really utilize the system.To do this, you must first decide which aspects of a new suggested system are the most essential and required.
Get familiar with the many categories that access control methods fall under. Carry out a comparison and investigation of the myriad of distinct forms of controls that are made available by each alternative.
What steps can you take to mitigate the effects of this issue in the event it recurs in the future?
You are using a new release of an application software package. You think that you have dis-covered a bug. Outline the approach that you would take to confirm that it is indeed a bug. What actions would you take if it truly were a bug?
Where can I get the software I need for my application, and what are my other options? Your explanation must be supported by examples that are pertinent to the topic at hand.
Consider the difficulties you'll face as you construct the framework, and then look into the various solutions to those issues. Is it reasonable to believe that we will be better able to deal with these difficulties after migrating our PCs to the cloud? Should this be taken into account, or is it not essential here?
You are managing a software project. You are partway through the project,and your team has just delivered a preliminary version of part of thesoftware. You are holding a weekly status meeting, when one of the teammembers points out that an important stakeholder is running into a problemwith one of the features of the current software. The team member feels thatthere is a risk that the stakeholder will ask for a change in that feature, eventhough that change would be out of scope of the current release - and if thestakeholder requests that change, there is a high probability that the changecontrol board would approve the change. What is the BEST action to takenext?A. Add the risk to the risk register and gather information about its probability andimpactB. Mitigate the risk by asking a team member to get familiar with the feature of thesoftware that might be changedC. Schedule a meeting with the stakeholder to discuss the riskD. Add the risk to the issue log and revisit it when there is…
How would you characterize danger in terms of the software framework? Can you think of anything more to add?
What are my alternatives for obtaining software for my application? Your explanation should be backed up by relevant examples.
Think about the challenges you'll experience as you build the framework, and then look into the specific problems and blockages you'll run across with each proposed solution. Is it possible that moving our computers to the cloud will make it easier to deal with these issues? Is it necessary to take this into consideration, or is it irrelevant here?