|February 1, 2017||Abstract and optional full paper submission begins|
|March 13, 2017||Exhibit & Supporter registration opens|
|April 30, 2017||Abstract and optional full paper submission ends|
|June 5, 2017||Acceptance notifications sent|
|July 24, 2017||Submit final abstracts and presenter biographies|
|August 28, 2017||Submit final presentations and optional full papers|
Connected Teams, Connected Code, and the Connected Device: The Complexities of IoT Development
How long before you refuse to write code that potentially could harm someone’s privacy or security? Especially when the lines between software and physical hardware are blending rapidly. Every day, every hour, every minute, more and more devices are becoming connected. The Internet of Things (IoT) has gone from a tech buzzword to a quickly advancing, innovative movement across the globe. But, like a stone tossed into a pond, the effects of the proliferating IoT are quickly rippling outward, causing immense changes and pressures to the software development environment surrounding it. While the manufacturing of IoT hardware continues to explode (there are already more than 5 billion connected devices across the world today), how will software developers and technology communities support the emergence and successful rollout of new platforms and devices? If one thing is clear, app developers need security to be at the core of their development process because a rapidly expanding connected world opens the doors to tumultuous hackers and cyber security threats. Not only that, but software delivery must now happen at lightning speeds because downtime is not an option for both the consumer and mission-critical IoT systems where software updates are constantly deployed straight to the device. There are currently more than 10 million app developers worldwide that are faced with a security, privacy Armageddon – purpose-building the right code for IoT necessities. This presentation will discuss and correlate the emergence of IoT systems and how Continuous Development and Continuous Delivery are particularly well-equipped for dealing with the demands of the connected device software delivery dilemma. As frequent updates are a requirement in IoT – which satisfies both the end users’ desire for a constantly updated device, as well as the developers’ need for a manageable development process – frequent software testing is now required for IoT security purposes. If these processes can be automated and accelerated, developers are able to help reduce the risk of security flaws in the device and are freed up to write new functions and features to keep up with the pace of innovation.
No handouts have been uploaded.
Prathap Dendi (Author), Ship.io, firstname.lastname@example.org;
Prathap has over 15 years of experience in technology executive and leadership positions in companies ranging from startups to public organizations. He has deep international business development background in software, hardware, services and Cloud Computing. Before joining Electric Cloud, Dendi served as IBM’s business development executive for the cloud computing business, where he was instrumental in establishing IBM’s cloud platform and services. Dendi played a key role in growing IBM’s Service Oriented Architecture platform through strategic partnerships with companies such as Capgemini, Accenture, Deloitte and Infosys. He was also responsible for driving software strategy including acquisitions and new technology creation, and held leadership roles at IBM in software, services, sales and business development. Prior to IBM, Dendi held senior positions with Actional, Abilizer, Aspect Development and Ramco Systems. His career includes work with several Fortune 500 companies including Allianz, Barclays Group, Visa, Disney, Gap, Chevron, Procter & Gamble, Nissan and Union Pacific. Dendi holds a bachelor of technology degree in electronics engineering and telecommunications engineering from the National Institute of Technology, Warangal, India.
Anders Wallgren (Primary Presenter), Electric Cloud, email@example.com ;