Unfortunately, at most companies, EAP, or EA, was placed under the information technology function. It was often directed toward addressing narrow technology needs for particular business units, or subsumed into complex exercises in documenting incompatible systems. Then, as EAP was combined with reengineering during the 1990s, it was frequently used as an excuse for wholesale cost cutting, which ultimately tended to make companies weaker. This history helps explain why many EAP groups developed a poor reputation, or did not deliver value to the enterprise. Today, companies can proceed in a more strategic way — with something close to EA in scope, but more ambitious in spirit and pragmatic in achieving results.
The first year, CIOs put together a plan; the second year, they execute on that plan; and the third year, "things don't turn out quite the way you'd like them to," said Langer, director of the Center for Technology Management and academic director of the executive Masters of Science Program atColumbia University. Then, they're gone. What sets apart the CIOs who don't fit this pattern? Langer described 23 characteristics in his recent webinar, Strategic IT: The Transition Taking Place in the CIO Role. The material was based on research and interviews that he and his colleague Lyle Yorks conducted for their similarly named book.
“A lot of people talk about automation being adopted at the kind of usual pace of safety systems, which is a kind of 20 year adoption curve,” Reed says. “I think it's going to be different. “Use cases like driverless shuttles in cities could happen quite quickly. Similarly automated driving by cars and platoons of trucks on motorways.” While some companies are looking towards pods and new ownership models, others are focusing on more traditional cars gaining increasing levels of automation over a longer timeline. Reed predicts the two models will co-exist, with adoption rates being different for each. “Adoption of fully automated vehicles will take longer due to the associated technical and regulatory challenges.” He predicts that although the technology will be a premium technology at first, it will trickle down to lower value vehicles and gain rapid adoption once practical.
“Focusing on a standard EA framework doesn’t work,” he said. “In the past EA practicioners focused on deliverables that were useful to enterprise architects but not valuable to senior management and/or did not respond to a specific business IT need. “We’ve witnessed a change in mind-set, execution and delivery of EA. The value of EA is not in simply ‘doing EA’, but rather in how it can help evolve the business and enable senior executives to respond to business threats and opportunities,” (for more on responding to threats and opportunities, the Agile way see here). Brian Burke’s statements are echoed across the industry. Enterprise Architecture has got to become more about business outcomes and the deliverables that steer an organization toward them.
It’s obvious that enterprises will retain on-premises infrastructure for the foreseeable future. Given the use of public cloud computing there is, ipso facto, hybrid computing. The key question: How much infrastructure will remain on-premises and in what form? One vision proffered for hybrid cloud is an on-premises cloud environment based on, say, OpenStack, which interoperates with a similar public environment. Another vision proffered is an on-premises cloud environment interoperating with a dissimilar public environment. Yet a third is an unchanged on-premises environment, say a vSphere cluster, along with use of some public environment. Depending upon what form of hybrid cloud one envisions, the appropriate solution varies widely. And the question of what will emerge as the dominant form of hybrid cloud emerges victorious will dictate the fortunes of both users and vendors in the future.
“When we talk about affective devices today, we’re really looking at primary emotions and that’s what we think is going to be responded to,” notes Wendell Wallach, acclaimed ethicist and scholar from Yale University's Interdisciplinary Center for Bioethics and author of, A Dangerous Master: How to Keep Technology from Slipping Beyond our Control. “But if you look at Paul Ekman’s charts, he’s got thousands of secondary ideas that represent subtler secondary states. As technology picks up on these subtle emotions it would avoid manipulating you in a very crude state one could filter out to manipulate you using those subtler cues.” Dr. Paul Ekman is the pioneer of micro-expressions, or "very brief facial expressions that occur when a person either deliberately or unconsciously conceals a feeling."
Never before in the history of mankind, such a huge number of people are leaving their digital footprints. They are sharing, purchasing and surfing, searching and reviewing—and all of this is documented. You may analyze or may discard this humongous amount of data, but it certainly has a meaning. They give a clue to something that you don’t know. Companies having a foresight understand its importance. There are businesses, on the other hand, believe it more a hype. But sooner or later they will have to adopt it as this is an inevitability since technology has arrived. Human subjectivity is not going to be eliminated soon, but BIG data will be a major tool for the crucial marketing and business decisions.
UseCompressedStrings feature was rather conservative: while distinguishing between char and byte case, and trying to compress the char into byte on String construction, it done most String operations on char, which required to unpack the String. Therefore, it benefited only a special type of workloads, where most strings are compressible (so compression does not go to waste), and only a limited amount of known String operations are performed on them (so no unpacking is needed). In great many workloads, enabling -XX:+UseCompressedStrings was a pessimization ... implementation was basically an optional feature that maintained a completely distinct String implementation in alt-rt.jar, which was loaded once the VM option is supplied. Optional features are harder to test, since they double the number of option combinations to try.
Privilege Control is very common mechanism. In real life, people are allocated into different roles. Some of who can maintain sensitive information based on his/her access level, and the other cannot. In computer world, that is the same. Microsoft Window is a famous PC OS and it also has a user management system in it. Administrator can create user account and assign different privileges to different user account. E.g. Ricky’s role is administrator and Jenny’s role is guest, both of who launch the system based on his/her Login Name and Password, Ricky can control everything of the computer and Jenny does not have any permission except view right. That is based on theirs privilege.
More than a third of organizations said that big data analytics was one of their most important spending drivers. Patient engagement and consumer retention and management tools are also attracting attention, with 31.6 percent of respondents stating that they are actively seeking new technologies to help them track and communicate with their patient base. In 2016, close to 40 percent of providers are looking to enhance or refresh their patient portal offerings, while a similar number are planning to expand their electronic communications capabilities by implementing wellness and chronic disease management programs that take advantage of online communication techniques, as well as texting and phone-based initiatives.
Quote for the day:
"It is the framework which changes with each new technology and not just the picture within the frame." -- Marshall McLuhan