A software package to implement a data base is ?->(Show Answer!)

1. A software package to implement a data base is

Write Comment

Comments

Tags

Show Similar Question And Answers

QA->JAVA toolkit package containing classes that implement platform independent GUI is :....

QA->In a data base, the column of a table is referred to as the :....

QA->A program Graph has ‘start’ and ‘end’ nodes. The total number of paths from start to end is equivalent to the -----------set of test data required to test the software.....

QA->Red data book provides data on :....

QA->4G LTE is a standard for wireless communication of high speed data for mobile phone and data terminals. What does LTE stand for?....

MCQ->Which two can be used to create a new Thread? Extend java.lang.Thread and override the run() method. Extend java.lang.Runnable and override the start() method. Implement java.lang.Thread and implement the run() method. Implement java.lang.Runnable and implement the run() method. Implement java.lang.Thread and implement the start() method.....

MCQ-> DIRECTIONS for questions:These questions are based on the situation given below:Recently, Ghosh Babu spent his winter vacation on Kyakya Island. During the vacation, he visited the local casino where he came across a new card game. Two players, using a normal deck of 52 playing cards, play this game. One player is called the Dealer and the other is called the Player. First, the Player picks a card at random from the deck. This is called the base card. The amount in rupees equal to the face value of the base card is called the base amount. The face values of Ace, King, Queen and Jack are ten. For other cards, the face value is the number on the card. Once, the Player picks a card from the deck, the Dealer pays him the base amount. Then the dealer picks a card from the deck and this card is called the top card. If the top card is of the same suit as the base card, the Player pays twice the base amount to the Dealer. If the top card is of the same colour as the base card (but not the same suit) then the Player pays the base amount to the Dealer. If the top card happens to be of a different colour than the base card, the Dealer pays the base amount to the Player. Ghosh Babu played the game 4 times. First time he picked eight of clubs and the Dealer picked queen of clubs. Second time, he picked ten of hearts and the dealer picked two of spades. Next time, Ghosh Babu picked six of diamonds and the dealer picked ace of hearts. Lastly, he picked eight of spades and the dealer picked jack of spades. Answer the following questions based on these four games.If Ghosh Babu stopped playing the game when his gain would be maximized, the gain in Rs. would have been
....

MCQ->What will be the output of the following program? #include<iostream.h> class Base { int x, y; public: Base() { x = y = 0; } Base(int xx) { x = xx; } Base(int p, int q = 10) { x = p + q; y = q; } void Display(void) { cout<< x << " " << y << endl; } }objDefault(1, 1); class Derived: public Base { Base obj; public: Derived(int xx, int yy): Base(xx, xx + 1) { } Derived(Base objB = objDefault) { } }; int main() { Derived objD(5, 3); Derived ptrD = new Derived(objD); ptrD->Display(); delete ptrD; return 0; }....

MCQ->Which of the following can be facilitated by the Inheritance mechanism? Use the existing functionality of base class. Overrride the existing functionality of base class. Implement new functionality in the derived class. Implement polymorphic behaviour. Implement containership.....

MCQ-> It’s taken me 60 years, but I had an epiphany recently: Everything, without exception, requires additional energy and order to maintain itself. I knew this in the abstract as the famous second law of thermodynamics, which states that everything is falling apart slowly. This realization is not just the lament of a person getting older. Long ago I learnt that even the most inanimate things we know of ―stone, iron columns, copper pipes, gravel roads, a piece of paper ―won’t last very long without attention and fixing and the loan of additional order. Existence, it seems, is chiefly maintenance.What has surprised me recently is how unstable even the intangible is. Keeping a website or a software program afloat is like keeping a yacht afloat It is a black hole for attention. I can understand why a mechanical device like a pump would break down after a while ―moisture rusts metal, or the air oxidizes membranes, or lubricants evaporate, all of which require repair. But I wasn’t thinking that the nonmaterial world of bits would also degrade. What’s to break? Apparently everything.Brand-new computers will ossify. Apps weaken with use. Code corrodes. Fresh software just released will immediately begin to fray. On their own ―nothing you did. The more complex the gear, the more (not less) attention it will require. The natural inclination toward change is inescapable, even for the most abstract entities we know of: bits.And then there is the assault of the changing digital landscape. When everything around you is upgrading, this puts pressure on your digital system and necessitates maintenance. You may not want to upgrade, but you must because everyone else is. It’s an upgrade arms race.I used to upgrade my gear begrudgingly (Why upgrade if it still works?) and at the last possible moment. You know how it goes: Upgrade this and suddenly you need to upgrade that, which triggers upgrades everywhere. I would put it off for years because I had the experiences of one “tiny” upgrade of a minor part disrupting my entire working life. But as our personal technology is becoming more complex, more co-dependents upon peripherals, more like a living ecosystem, delaying upgrading is even more disruptive. If you neglect ongoing minor upgrades, the change backs up so much that the eventual big upgrade reaches traumatic proportions. So I now see upgrading as a type of hygiene: You do it regularly to keep your tech healthy. Continual upgrades are so critical for technological systems that they are now automatic for the major personal computer operating systems and some software apps. Behind the scenes, the machines will upgrade themselves, slowly changing their features over time. This happens gradually, so we don‘t notice they are “becoming.”We take this evolution as normal.Technological life in the future will be a series of endless upgrades. And the rate of graduations is accelerating. Features shift, defaults disappear, menus morph. I’ll open up a software package I don’t use every day expecting certain choices, and whole menus will have disappeared.No matter how long you have been using a tool, endless upgrades make you into a newbie ―the new user often seen as clueless. In this era of “becoming” everyone becomes a newbie. Worse, we will be newbies forever. That should keep us humble.That bears repeating. All of us ―every one of us ―will be endless newbies in the future simply trying to keep up. Here’s why: First, most of the important technologies that will dominate life 30 years from now have not yet been invented, so naturally you’ll be a newbie to them. Second, because the new technology requires endless upgrades, you will remain in the newbie state. Third, because the cycle of obsolescence is accelerating (the average lifespan of a phone app is a mere 30 days!), you won’t have time to master anything before it is displaced, so you will remain in the newbie mode forever. Endless Newbie is the new default for everyone, no matter your age or experience.Which of the following statements would the author agree with the most?
....