Why is Artificial Intelligence important?

Image
The AI learning adventure explores intelligence and its connection to engineering and technology.  Using ideas about human intelligence and intelligence more broadly, engineers can create “artificial intelligence,”; that is, impart “human” intelligence into machines or technology (Classical AI) or design technology that can itself “create” intelligence (future AI).  In fact, understanding how the brain works—”reverse-engineering the brain”—and understanding how engineers design intelligent machines—machines that replicate human intelligence—is one of the “Grand Challenges of Engineering” as set forth by The National Academy of Engineering (NAE). The implications and benefits of understanding the brain are many.  In addition to advances in the treatment of brain injuries and diseases and advancements in communications technology and computer simulations, understanding the brain will allow the design of intelligent machines with even more signicant societal impacts.  Already, mac
2 comments

Some major effects of DevOps on Industries | NIIT digiNxt


The term DevOps is a methodology of Development and Operation worked in a sync manner. Software are now drop shipped as services(ex-, Amazon Web Services).  
Therefore advent of Cloud Computing, the software world had more or less settled in typical roles of Product, Development and QA; and once software is deployed on physical medium, the team moved on. Then, there was a scaled down Sustained Engineering team providing Service Packs and Hotfixes. At those times, the “Operations” happen at the customer’s premises for enterprise software or the user would do it by installing the software from a physical medium.

We always faces a standard question from testers, students and professionals in any Dev-Ops related presentations, “Will Dev-Ops remove the need for Testers?” Our simple answer is “No”. DevOps is not going to replace Testing as a discipline. Firms implementing DevOps have a vision for better product quality workable by brilliant Testing.  

So, things have changed. The software is provided as a service and the organization developing it is also hosting and maintaining it. If an organization fails to recognize the crucial role QA plays within a successful DevOps transformation, it will be unable to achieve smooth operation of a continuous delivery model. Developers will continue to unit test with functional-only tunnel vision and hand over the remainder of testing to QA at their own pace. This situation creates an almost invisible disconnect between development and operations that creates undue friction toward reaching continuous delivery goals.

With the help of DevOps development is being made facile. Software developers are responsible for production code, and testers who tested the software manually and sometimes automated tests. Mostly they worked in cellar.

 DevOps is an enabler for the following.

  • Reduction in IT Budgets
  • Efficient end-to-end delivery
  • Lean delivery framework
  • Working end-to-end automation framework
To increase test coverage, more and more people were employed to do QA who would meticulous read specification, write test cases, enact them over and over. Due to this, there is creation of sub-industry within the Software Development industry called “Testing Industry”, and after developers, the largest numbers of people employed were testers. With the advent of Agile, DevOps and Automation, testers are suddenly rattled…instead of adding more QA people, they are being reduced in order to cut costs. Industries are demanding Automation Engineers.
Overall, DevOps has put the bar for testing a tad higher and made it visible–which is a good thing. The “Testing Industry” would amalgamate back to “Software Industry” and probably there would be only high-quality “Engineers” left.



Comments

Post a Comment

Popular posts from this blog

Innovate your business through Test and Learning Approach

Image
More and more we are having discussions with businesses about a different way of approaching business challenges, from digital marketing to analytics and insight. A way of working which allows the business to inform their longer-term strategic decision making whilst seeing positive business benefits in the short-term. An approach which excites customers and empowers employees, whilst being cost-effective and flexible enough in today’s ever-changing digital world. More and more we are talking to them about a Test & Learn approach. Test & Learn, simply put, is a set of practices that allows a business to try out new ideas and concepts, either with a small subset of customers or in a limited number of locations (e.g. in only a handful of stores) in order to understand the impact it has on factors such as customer experience, employee productivity and sales. There are many reasons why a Test & Learn approach should be considered as part of any business strategy, but
Read it all»

Waterfall vs Agile and Scrum Methodology

Image
What Is Agile? Agile software development is based on an incremental, iterative approach. Instead of in-depth planning at the beginning of the project, Agile methodologies are open to changing requirements over time and encourages constant feedback from the end users. Cross-functional teams work on iterations of a product over a period of time, and this work is organized into a backlog that is prioritized based on business or customer value. The goal of each iteration is to produce a working product. In Agile methodologies, leadership encourages teamwork, accountability, and face-to-face communication. Business stakeholders and developers must work together to align the product with customer needs and company goals.  Agile refers to any process that aligns with the concepts of the Agile Manifesto. In February 2001, 17 software developers met in Utah to discuss lightweight  development methods. They published the  Manifesto for Agile Software Development , which covered how th
Read it all»

How to identify the right DevOps tools | NIIT digiNxt

Image
W e have broken down various DevOps tools in various phases: Plan Build Continuous integration Deploy Operate Continuous feedback 1. Plan Taking a page out of the agile handbook, we recommend tools that allow your development team to plan in iterations. In this way you can optimize your product from that feedback. Look for tools that provide sprint planning features. Another great practice is continuously gathering user feedback, organizing it into actionable inputs, and prioritizing those actions for your development teams. Look for tools that encourage “asynchronous brainstorming” (if you will). It’s important that everyone can share and comment on anything: ideas, strategies, goals, requirements, roadmaps and documentation. And don’t forget about integrations. Wherever you decide to scope your feature or project should be converted into user stories in your development backlog. Some tools: Confluence, Hipchat, Jira Software 2. Build Developers use tools l
Read it all»