Infosys 3.0...Business Solutions...
The IT major Infosys Technologies is looking forward to move on by transforming its business and innovation capabilities into a whole new phase, the company names it as Infosys 3.0. The IT firm is looking forward to change its business capabilities from Technology Solutions to Business solutions hence, enhancing the capability of the company in major global trends such as: digital consumer (digital products), new commerce (Related to small mobile transactions), healthcare economy, sustainable tomorrow(Environment), pervasive computing (all devices becoming computing devices) and much more.
The company which is into technology solutions for three decades now has taken step further to compete with global peers such as IBM, Accenture which are high above it in terms of above mentioned technologies. Presently the company Infosys 2.0 works in developing end to end services capabilities, system integration capabilities, and some consulting and innovation enterprise. But, now the company’s COO SD Shibhulal the upcoming successor of CEO Kris Gopalakrishnan this year has placed his ideas to move the Infosys Technologies to the next phase Infosys 3.0. This rebooting process taken by company will take the IT major around 5-7 years to make it compete with its global competitors. New Infosys 3.0 will focus on employees by developing their talents in these new directions to ensure progress in their careers hence, changing the brand positioning of Infosys completely from ‘Win in the flat world’ to ‘Building tomorrow’s enterprise’.
Related Posts
EAV versus Row modeling
Following are main features/downsides EAV has over classic row modeling technique. A row-modeled table is homogeneous. I t will always carry same type of data in contrast to EAV modeled table where this cannot be an issue. The data type of the value column/s in a row-modeled table is pre-determined by the nature of the facts it records. In contrast, in an EAV table, the conceptual data type of a value in a particular row depends on the attribute in that row. A Row modeling technique data increase only in one direction i.e. from Upside-down whereas in EAV data model data increase in both directions i.e. from upside down as well as from left-right. Other Related Links: EAV(Entity-Attribute Value) Model EAV versus Row modeling Downsides of EAV data model over class row model Opting classic row modeling or EAV data modeling?
Difference in Verification and Validation of requirement? : Requirement Traceability Matrix?
The difference in Verification and Validation of requirements? Verification of requirement – a requirement meets the quality standard, fits the purpose, it is clear, consistent, complete, testable, unambiguous, understandable to stakeholders. Validation of requirement – requirement is aligned to the business need, goal, outcome, if it supports the delivery of needed value. Requirement Traceability Matrix? The technique used to trace the requirements. It ensures that all business requirements are covered. It helps in backward and forward traceability. Helps in faster impact analysis and reliable assessment for ensuring business requirement coverage. Requirement Traceability Matrix
Ex-HP CEO Hurd Pays $14 Million Bounty as Oracle Pledge Fee
Valleywag reports that ousted HP CEO Mark Hurd is paying dearly to roll with Oracle, giving up millions of dollars to settle the HP lawsuit that threatened to prevent him from working at his new job. Hurd will forfeit about 345,000 restricted HP shares that he was given as part of his HP exit package, which had a market value of $13.6 million. In addition to announcing the truce against the backdrop of Oracle's OpenWorld conference, HP and Oracle also reaffirmed their vows to each other.
The bug in the name of the C++ language.
From the internet, a popular quote goes like this: "Of course, while it is true that the ++ operator gives the C++ language its name, it also led to the first joke about the language. C++ haters point out that even the name of the language contains a bug: 'After all, it should really be called ... ++C, because we only want to use a language after it has been improved.' " We will now see why this joke is so absolutely hilarious. int main() { int x = 40; int y = ++x + 1; std::cout << x << '\n' << y; } Output: x = 41, y = 42. The pre-increment operator first increments the value of x (the ++) and then stores it in the variable. Hence, when the code is executed, x becomes 41 AFTER being assigned to y . The post-increment works the other way, the value is first stored in the lvalue before being assigned to the rvalue of the variable being incremented. int main() { int x = 40; int y = x++ + 1; std::cout <&l
Comments
Post a Comment
Let's discuss and learn more