Home
Schedule
Conference Info
Sponsorship Information
IBM Watson AI Day
Registration
Press Registration
Speakers
Sessions
Sponsors
Exhibitors
JETRO × Six Prefectures of Japan Pavilion Exhibitors
  Media Sponsors
  Topics
  Call For Papers
  Hotel Info
  Past Events
Untitled Document
2017 West
Premium Sponsors
Diamond



Platinum
@DevOpsSummit

Bronze










Untitled Document
2017 West
Keynote Sponsor


Untitled Document
2017 West Exhibitors
























@ThingsExpo











Untitled Document
2017 West Media Sponsors














Untitled Document
2017 East
Premium Sponsors
Diamond



Platinum
@DevOpsSummit

@DevOpsSummit

Silver
@DevOpsSummit


Bronze










Untitled Document
2017 East Exhibitors
@DevOpsSummit




































Untitled Document
2017 East Media Sponsors
















Untitled Document
2016 West
Premium Sponsors
Platinum Plus



Silver
@ThingsExpo

Bronze







Untitled Document
2016 Welcome Reception Sponsor

Untitled Document
2016 West Exhibitors










@DevOps Summit






@DevOps Summit

@WebRTC Summit












@WebRTC Summit









@DevOps Summit

Untitled Document
2016 West Media Sponsors











Untitled Document
2016 East Gold Sponsors

@ThingsExpo

Untitled Document
2016 East Silver Sponsors


@DevOps Summit

Untitled Document
2016 East Bronze Sponsors

Cloud Expo







Cloud Expo

Untitled Document
2016 East Vendor Presentation Sponsors

@DevOps Summit

Untitled Document
2016 East Exhibitors

@DevOps Summit





@ThingsExpo



@DevOps Summit

@ThingsExpo


@DevOps Summit









@DevOps Summit







@DevOps Summit










Untitled Document
2016 East Media Sponsors










Untitled Document
2015 West Gold Sponsors

Untitled Document
2015 West Silver Sponsor


Untitled Document
2015 West Bronze Sponsors

Cloud Expo |@ThingsExpo

Cloud Expo | DevOps Summit


@ThingsExpo





@DevOps Summit

@ThingsExpo


@ThingsExpo

 


Untitled Document
2015 West Exhibitors












@DevOps Summit





@DevOps Summit












@DevOps Summit

@DevOps Summit




@ThingsExpo


@DevOps Summit

 


Untitled Document
2015 West E-Bulletin Sponsors

DevOps Summit

Untitled Document
2015 West
Associate Sponsor

Untitled Document
2015 West Media Sponsor

Untitled Document
2015 East Gold Sponsors


WebRTC Summit

DevOps Summit

Untitled Document
2015 East Silver Sponsors
DevOps Summit
WebRTC Summit

Untitled Document
2015 East Bronze Sponsors

DevOps Summit

Cloud Expo | DevOps Summit
@ThingsExpo

DevOps Summit

DevOps Summit

Untitled Document
2015 East Delegate Bag Sponsors


Untitled Document
2015 East Exhibitors

DevOps Summit


@ThingsExpo



DevOps Summit






Cloud Expo | @ThingsExpo
Internet of @ThingsExpo
@ThingsExpo
DevOps Summit

DevOps Summit
@ThingsExpo
DevOps Summit
DevOps Summit
DevOps Summit
DevOps Summit
DevOps Summit



@ThingsExpo

Untitled Document
2015 East Associate Sponsor

Untitled Document
2015 East
Media Sponsors

Software Engineering in Startup Companies
Software Engineering in Startup Companies

The discussion about software engineering in the special environment of startup companies continues with a focus on the software life cycle model and the tracking of requirements.

Software Life Cycles
According to classical software engineering (SE), the development of software takes place in stages. Each stage has distinct outputs, which can be tested before you proceed to the next stage. They are:

  • Analysis: The problem and requirements for a solution are identified. Main output: Software requirements document.
  • Design: A software system is designed to fulfill the previously identified requirements. Main output: High- and low-level design documents.
  • Implementation/coding: The software system is implemented according to the previously defined design. Main output: Source code.
  • Testing: Individual components as well as the entire system are tested for fulfillment of the requirements identified during the analysis stage. Main output: Test results.

    Numerous models that describe the arrangement of the individual stages and the feedback among them have been suggested. These are called the software life cycle models. Some examples are the waterfall model, spiral model and incremental model, which are thoroughly discussed in SE literature (for example, Software Engineering: A Practitioner's Approach, 4th ed., by R. Pressman, McGraw-Hill).

    Consciously following a life cycle model lends structure to an otherwise amorphous effort. When you can identify the end of a stage, you know the time has come to perform specific tests, tests that enable you to find errors at an early stage in the development process. A major design flaw that can be fixed with just a stroke of a pen during the design stage may require major recoding if discovered when the software's almost finished. It's therefore important to perform these tests not just at the end of the development effort, but rather from the beginning and throughout the process. A lifecycle model facilitates this.

    By testing the output of a stage, you provide a well-understood and firm foundation for the team to build on. Once such a foundation is set, it's not supposed to change. In the ideal case all team members know what to achieve next, since this was set forth in the previous stage in a nonambiguous manner.

    In a startup company, however, the software life cycle is usually not well ordered. Markets develop swiftly, and requirements change even long after the analysis stage has supposedly been completed. Time and time again the engineering department finds itself under pressure to do whatever it takes to provide new features originally not planned.

    Is there a lifecycle model that not only works under these conditions but also helps to improve them? Of the many models developed, the incremental model seems to lend itself most closely to the way a startup company operates, but it requires a few modifications.

    As you can see in Figure 1, individual releases of the software are developed in a "pipelined" fashion. In theory this allows the rapid release of new features for your software. The incremental model works well for conventional companies operating in established markets, which use it to reduce the complexity of an individual release. Many of the features for the next releases are already known through market observation, feedback from customers of other products, established marketing channels and so forth. The more established companies also have the resources to maintain multiple parallel development streams.

    The startup reality renders this model impractical. Hiring qualified personnel is particularly difficult for a startup. It's unrealistic to assume that you'll hire a team of experienced analysts at the very beginning, followed first by designers and then by developers. In theory, software engineers should be able to handle all phases of product development. Unfortunately, the proliferation of this title throughout the industry has greatly reduced its value. Many people who call themselves software engineers really don't have a thorough software engineering education and often their experience is only in coding and maybe some design. I am in the same situation and am still learning. So while you can find many software engineers, those with the necessary skills, training and experience for all product-development stages are few and far between.

    The overall head count in your company is likely to be very low for an initial period, only to increase quite rapidly later on. Thus, in the beginning, each developer is also in the position of analyst as well as designer. Obviously, given the lack of personnel, you may not be able to do the analysis for the next release during the design phase of the first release. You have neither enough resources nor sufficient market feedback to begin the development cycle of the second release right away. After all, you haven't even released the first version of your product. Occasional feedback is passed on to you by marketing and sales, gathered from discussions with potential customers. But you won't get true customer feedback until you've shipped the first version to beta customers. Compared to established markets that provide a brightly illuminated playing field, a startup operates in the dark.

    During analysis - and design - you may have to perform research to prove technical concepts or ideas on which you plan to base your product. This may be done in the form of a prototype, which provides feedback for the analysis and design stage, adding complexity to the initial development stages.

    Quickly developing markets, initially missing customer feedback and lack of resources as well as analysis and design stages influenced by research lead me to suggest a modified incremental life-cycle model for startup companies.

    As Figure 2 indicates, analysis, research and design are intertwined for the first release. Analysis for the second release begins at a later stage when two conditions have been met:
    1. Requirements for the next release are available.
    2. Enough new developers have been hired to free the most senior developers to work with marketing on the analysis stage of the next release.

    The analysis for the second release starts after enough customer feedback has been collected to get a good feel for what the market wants. Without that feedback there's really no point in attempting to release yet another version of a product that may have had a lukewarm reception the first time around. The feedback is important and therefore needs to be properly analyzed and prioritized. You have to resist the temptation to stuff all requested features into the next release.

    Once you have a product on the market, you'll get a constant stream of requests. Thus, after the initial lag, you can start working on new releases earlier and earlier as staffing permits. The modified incremental life cycle model reflects this reality.

    Also note that the research component becomes less with each subsequent release. The reason is simply that you've established a core technology with the first release from which you'll continue to leverage. Yours is a commercial company, not a research lab. It's important for you not to have too much research in the critical path of your project as you progress, since research can't be scheduled properly.

    By keeping the first release small and simple, you'll receive market feedback sooner. Such early feedback is important to align the company and its product with the market. The longer it takes you to get feedback, the more time you spend developing "blind," in possibly the wrong direction. Provide the core functionality in the first release. The market will let you know in which direction to go. Potential customers are often willing to negotiate now if the fancy feature they want can be promised to them in an upcoming release. This lifecycle model sets you up for quick releases to satisfy customers without having to drastically change the requirements for an ongoing development cycle.

    Tracking Requirements
    As we discussed in the first part of this series (JDJ, Vol. 3, Issue 7), the analysis stage will not be as rigorous as classical SE would suggest. Many requirements are not known at all, or at least are not understood enough to formulate them in a quantifiable manner.

    Yet it's important not to drop a requirement accidentally through simple oversight. Consequently you have to track as many requirements as possible and as completely as possible. The traditional tool used for this task is the "traceability matrix."

    The matrix is essentially a table. The individual requirements are written from top to bottom and hence label the rows. The individual development stages (analysis, design, implementation, testing) are written from left to right and label the columns. Each cell of the table contains a record of where and how the requirement was addressed in that stage. For the development of product documentation, either a similar table should be created or documentation should become an additional column in the matrix.

    At the end of each development stage each requirement should be checked to see whether it has been addressed during that stage. A look at the table will reveal any omissions, which would be very costly to fix in later stages of product development. Such a matrix can save time and money.

    A traceability matrix will provide a company with an important benefit. Since the matrix records the trace of each requirement throughout the development stages, it shows the team which aspects of the product are affected by requirement changes. If the actual design and implementation takes place in a modular fashion, exhibiting low coupling and high cohesion (see the previously mentioned article), chances are that only those aspects of the product mentioned in that feature's matrix row need to be modified. As discussed earlier, flexibility and quick turnaround is a key point, especially for startup companies. The traceability matrix will facilitate such fast reaction times.

    Startups have two particular problems with maintaining a traceability matrix. First, as already mentioned, not all requirements are known and not all are quantified. The requirement itself may thus have to be formulated in a very unspecific manner, making it difficult to fill the matrix cells with precise information. In that case the matrix should still be maintained. Unquantified requirements should be marked and revisited as soon as more information becomes available. When that occurs the matrix will aid in identifying those parts of the product that need to be tested to see whether the modified requirement is still fulfilled.

    The second startup difficulty with traceability matrices is the work required to maintain them. On complex products a very detailed matrix can fill hundreds if not thousands of pages. Clearly, a compromise needs to be made here. For starters, in many cases it doesn't have to be one monolithic matrix covering the whole product. Even though a complete matrix is always recommended to achieve product completeness, a company might choose to have each team maintain its own matrices. The requirements within one subcomponent or project are identified and listed in a matrix. Maintaining such a smaller matrix is naturally a much less resource-intensive task. On the downside, overall product requirements may suddenly be listed in the matrices of several product teams. In that case some communication overhead is required to keep these matrices in sync.

    One might also choose to leave some of the requirements generally undefined and untraced. This is not at all ideal, but may be necessary due to a lack of resources. In that case the matrix should be limited to requirements that somehow have been deemed more critical than others. This method is risky since it again allows some requirements to be forgotten or not to be traceable if a change is required.

    A traceability matrix is a powerful tool to ensure product completeness and a quick trace of a feature's "footprint" within the product. Even though startup companies are likely to compromise on some aspects of the matrix, it's highly recommended to keep it as complete as possible. The payoffs are significant.

    Design, implementation and change control will be the topic of the next installment in this series.

    About Juergen Brendel
    Juergen Brendel is a software architect at Resonate Inc.

  • In order to post a comment you need to be registered and logged in.

    Register | Sign-in

    Reader Feedback: Page 1 of 1

    Presentation Slides
    Traditional on-premises data centers have long been the domain of modern data platforms like Apache Hadoop, meaning companies who build thei...
    Using new techniques of information modeling, indexing, and processing, new cloud-based systems can support cloud-based workloads previously...

    Register and Save!
    Save $405
    on your “Golden Pass”!
    before October 30, 2017!
    Call 201.802.3020


    Santa Clara Call for Papers Open
    Submit
    submit your speaking proposal
    for the upcoming WebRTC Summit in
    Santa Clara!
    [Oct 31- Nov 2, 2017]


    WebRTC Summit 2017 West
    Sponsorship Opportunities
    Please Call
    201.802.3021
    events (at) sys-con.com
    Sponsorship opportunities are now open for WebRTC Summit 2017 Santa Clara, Oct 31-Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA, and for WebRTC Summit 2018 New York, June 5-7, 2018, at the Javits Center in New York, NY. For sponsorship, exhibit opportunities and show prospectus, please contact Carmen Gonzalez, carmen (at) sys-con.com.



    WebRTC Summit Silicon Valley All-Star Speakers Include

    MATTHIEU
    Octoblu

    MAHADEV
    Cisco

    MCCARTHY
    Bsquare

    FELICIANO
    AMDG

    PAUL
    VenueNext

    SMITH
    Eviot

    BEAMER
    goTraverse

    GETTENS
    goTraverse

    CHAMBLISS
    ReadyTalk

    HERBERTS
    Cityzen Data

    REITBAUER
    Dynatrace

    WILLIAM-
    SON

    Cloud
    Computing

    SCHMARZO
    EMC

    WOOD
    VeloCloud

    WALLGREN
    Electric Cloud

    VARAN-
    NATH

    GE

    SRIDHARA-
    BALAN

    Pulzze

    METRIC
    Linux

    MONTES
    Iced

    ARIOLA
    Parasoft

    HOLT
    Daitan

    CUNNING-
    HAM

    ReadyTalk

    BEDRO-
    SIAN

    Cypress

    NAMIE
    Cisco

    NAKA-
    GAWA

    Transparent
    Cloud

    SHIBATA
    Transparent
    Cloud

    BOYD
    Neo4j

    WARD
    DWE

    MILLER
    Covisint

    EVAVOLD
    Covisint

    MEINER
    Oracle

    MEEHAN
    Esri

    WITECK
    Citrix

    LIANG
    Rancher Labs

    BUTLER
    Tego

    ROWE
    IBM Cloud

    SKILLERN
    Intel

    SMITH
    Numerex
    WebRTC Summit New York All-Star Speakers Include

    CLELAND
    HGST

    VASILIOU
    Catchpoint

    WALLGREN
    Electric Cloud

    HINCH-
    CLIFFE

    7Summits

    DE SOUZA
    Cisco

    RANDALL
    Gartner

    ARM-
    STRONG

    AppNeta

    SMALL-
    TREE

    Cazena

    MCCARTHY
    Bsquare

    DELOACH
    Infobright

    QUINT
    Ontegrity

    MALAU-
    CHLAN

    Buddy Platform

    PALIOTTA
    Vector

    MITRA
    Cognizant

    KOCHER
    Grey Heron

    PAPDO
    POULOS

    Cloud9

    HARLAN
    Two Bulls

    GOLO
    SHUBIN

    Bit6

    PROIETTI
    Location
    Smart

    MARTIN
    nfrastructure

    MOULINE
    Everbridge

    MARSH
    Blue Pillar

    PARKS
    SecureRF

    PEROTTI
    Plantronics

    HOFFMAN
    EastBanc

    WATSON
    Trendalyze

    BENSON-
    OFF

    Unigma

    SHAN
    CTS

    MATTELA
    Redpine

    GILLEN
    Spark
    Coginition

    SOLT
    Netvibes

    BERN-
    ARDO

    GE Digital

    ROMAN-
    SKY

    TrustPoint

    BEAMER
    GoTransverse

    LESTER
    LogMeIn

    PONO
    -MAREVA

    Google

    SINGH
    Sencha

    CALKINS
    Amadeus

    KLEIN
    Rachio

    HOASIN
    Aeris

    SARKARIA
    PHEMI

    SPROULE
    Metavine

    SNELL
    Intel

    LEVINE
    CytexOne

    ALLEN
    Freewave

    MCCAL-
    LUM

    Falconstor

    HYEDT
    Seamless

    WebRTC Summit Silicon Valley All-Star Speakers Include

    SCHULZ
    Luxoft

    TAM-
    BURINI

    Autodesk

    MCCARTHY
    Bsquare

    THURAI
    SaneIoT

    TURNER
    Cloudian

    ENDO
    Intrepid

    NAKAGAWA
    Transparent

    SHIBATA
    Transparent

    LEVANT-LEVI
    testRTC

    VARAN NATH
    GE

    COOPER
    M2Mi

    SENAY
    Teletax

    SKEEN
    Vitria

    KOCHER
    Grey Heron

    GREENE
    PubNub

    MAGUIRE
    HP

    MATTHIEU
    Octoblu

    STEINER-
    JOVIC

    AweSense

    LYNN
    AgilData

    HEDGES
    Cloudata

    DUFOUR
    Webroot

    ROBERTS
    Platform

    JONES
    Deep

    PFEIFFER
    NICTA

    NIELSEN
    Redis

    PAOLAL-
    ANTORIO

    DataArchon

    KAHN
    Solgenia

    LOPEZ
    Kurento

    KIM
    MapR

    BROMHEAD
    Instaclustr

    LEVINE
    CytexOne

    BONIFAZI
    Solgenia

    GORBA-
    CHEV

    Intelligent
    Systems

    THYKAT-
    TIL

    Navisite

    TRELOAR
    Bebaio

    SIVARAMA-
    KRISHNAN

    Red Hat
    Cloud Expo New York All-Star Speakers Included

    DE SOUZA
    Cisco

    POTTER
    SafeLogic

    ROBINSON
    CompTIA

    WARUSA
    -WITHANA

    WSO2 Inc

    MEINER
    Oracle

    CHOU
    Microsoft

    HARRISON
    Tufin

    BRUNOZZI
    VMware

    KIM
    MapR

    KANE
    Dyn

    SICULAR
    Basho

    TURNER
    Cloudian

    KUMAR
    Liaison

    ADAMIAK
    Liaison

    KHAN
    Solgenia

    BONIFAZI
    Solgenia

    SUSSMAN
    Coalfire

    ISAACSON
    RMS

    LYNN
    CodeFutures

    HEABERLIN
    Windstream

    RAMA
    MURTHY

    Virtusa

    BOSTOCK
    IndependenceIT

    DE MENO
    CommVault

    GRILLI
    Adobe

    WILLIAMS
    Rancher Labs

    CRISWELL
    Alert Logic

    COTY
    Alert Logic

    JACOBS
    SingleHop

    MARAVEI
    Cisco

    JACKSON
    Softlayer

    SINGH
    IBM

    HAZARD
    Softlayer

    GALLO
    Softlayer

    TAMASKAR
    GENBAND

    SUBRA
    -MANIAN

    Emcien

    LEVESQUE
    Windstream

    IVANOV
    StorPool

    BLOOM-
    BERG

    Intellyx

    BUDHANI
    Soha

    HATHAWAY
    IBM Watson

    TOLL
    ProfitBricks

    LANDRY
    Microsoft

    BEARFIELD
    Blue Box

    HERITAGE
    Akana

    PILUSO
    SIASMSP

    HOLT
    IBM Cloudant

    SHAN
    CTS

    PICCIN-
    INNI

    EMC

    BRON-
    GERSMA

    Modulus

    PAIGE
    CenturyLink

    SABHIKHI
    Cognitive Scale

    MILLS
    Green House Data

    KATZEN
    CenturyLink

    SLOPER
    CenturyLink

    SRINIVAS
    EMC

    TALREJA
    Cisco

    GORBACHEV
    Systems Services Inc.

    COLLISON
    Apcera

    PRABHU
    OpenCrowd

    LYNN
    CodeFutures

    SWARTZ
    Ericsson

    MOSHENKO
    CoreOS

    BERMING-
    HAM

    SIOS

    WILLIS
    Stateless Networks

    MURPHY
    Gridstore

    KHABE
    Vicom

    NIKOLOV
    GetClouder

    DIETZE
    Windstream

    DALRY-
    MPLE

    EnterpriseDB

    MAZZUCCO
    TierPoint

    RIVERA
    WHOA.com

    HERITAGE
    Akana

    SEYMOUR
    6fusion

    GIANNETTO
    Author

    CARTER
    IBM

    ROGERS
    Virtustream
    Cloud Expo Silicon Valley All-Star Speakers

    TESAR
    Microsoft

    MICKOS
    HP

    BHARGAVA
    Intel

    RILEY
    Riverbed

    DEVINE
    IBM

    ISAACSON
    CodeFutures

    LYNN
    HP

    HINKLE
    Citrix

    KHAN
    Solgenia

    SINGH
    Bigdata

    BEACH
    SendGrid

    BOSTOCK
    IndependenceIT

    DE SOUZA
    Cisco

    PATTATHIL
    Harbinger

    O'BRIEN
    Aria Systems

    BONIFAZI
    Solgenia

    BIANCO
    Solgenia

    PROCTOR
    NuoDB

    DUGGAL
    EnterpriseWeb

    TEGETHOFF
    Appcore

    BRUNOZZI
    VMware

    HICKENS
    Parasoft

    KLEBANOV
    Cisco

    PETERS
    Esri

    GOLDBERG
    Vormetric

    CUMBER-
    LAND

    Dimension

    ROSENDAHL
    Quantum

    LOOMIS
    Cloudant

    BRUNO
    StackIQ

    HANNON
    SoftLayer

    JACKSON
    SoftLayer

    HOCH
    Virtustream

    KAPADIA
    Seagate

    PAQUIN
    OnLive

    TSAI
    Innodisk

    BARRALL
    Connected Data

    SHIAH
    AgilePoint

    SEGIL
    Verizon

    PODURI
    Citrix

    COWIE
    Dyn

    RITTEN-
    HOUSE

    Cisco

    FALLOWS
    Kaazing

    THYKATTIL
    TimeWarner

    LEIDUCK
    SAP

    LYNN
    HP

    WAGSTAFF
    BSQUARE

    POLLACK
    AOL

    KAMARAJU
    Vormetric

    BARRY
    Catbird

    MENDEN-
    HALL

    SUPERNAP

    SHAN
    KEANE

    PLESE
    Verizon

    BARNUM
    Voxox

    TURNER
    Cloudian

    CALDERON
    Advanced Systems

    AGARWAL
    SOA Software

    LEE
    Quantum

    OBEROI
    Concurrent, Inc.

    HATEM
    Verizon

    GALEY
    Autodesk

    CAUTHRON
    NIMBOXX

    BARSOUM
    IBM

    GORDON
    1Plug

    LEWIS
    Verizon

    YEO
    OrionVM

    NAKAGAWA
    Transparent Cloud Computing

    SHIBATA
    Transparent Cloud Computing

    NATH
    GE

    GOKCEN
    GE

    STOICA
    Databricks

    TANKEL
    Pivotal Software


    Testimonials
    This week I had the pleasure of delivering the opening keynote at Cloud Expo New York. It was amazing to be back in the great city of New York with thousands of cloud enthusiasts eager to learn about the next step on their journey to embracing a cloud-first worldl."
    @SteveMar_Msft
    General Manager of Window Azure
     
    How does Cloud Expo do it every year? Another INCREDIBLE show - our heads are spinning - so fun and informative."
    @SOASoftwareInc
     
    Thank you @ThingsExpo for such a great event. All of the people we met over the past three days makes us confident IoT has a bright future."
    Yasser Khan
    CEO of @Cnnct2me
     
    One of the best conferences we have attended in a while. Great job, Cloud Expo team! Keep it going."

    @Peak_Ten


    Who Should Attend?
    Senior Technologists including CIOs, CTOs & Vps of Technology, Chief Systems Engineers, IT Directors and Managers, Network and Storage Managers, Enterprise Architects, Communications and Networking Specialists, Directors of Infrastructure.

    Business Executives including CEOs, CMOs, & CIOs , Presidents & SVPs, Directors of Business Development , Directors of IT Operations, Product and Purchasing Managers, IT Managers.

    Download Cloud Expo Show Guide
    Cloud Expo Show Guide
    Download PDF

    Join Us as a Media Partner - Together We Can Rock the IT World!
    SYS-CON Media has a flourishing Media Partner program in which mutually beneficial promotion and benefits are arranged between our own leading Enterprise IT portals and events and those of our partners.

    If you would like to participate, please provide us with details of your website/s and event/s or your organization and please include basic audience demographics as well as relevant metrics such as ave. page views per month.

    To get involved, email Patricia Henderson at patricia@sys-con.com.

    Digital Transformation Blogs
    Today’s AI cannot create an algorithm that satisfies a human’s intent in all but the simplest cases. What we do have is AI that can divine insights from patterns in large data sets. If we can boil down algorithms into such data sets, then we can make some headway. For example, if an AI-based application has access to a vast number of human-created workflows, then it can make a pretty good guess as to the next step in a workflow you might be working on at the moment. In other words, we now have autocomplete for algorithms – what we call ‘next best action.’ We may still have to give our so...
    Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more business becomes digital the more stakeholders are interested in this data including how it relates to bus...
    Having been in the web hosting industry since 2002, dhosting has gained a great deal of experience while working on a wide range of projects. This experience has enabled the company to develop our amazing new product, which they are now excited to present! Among dHosting's greatest achievements, they can include the development of their own hosting panel, the building of their fully redundant server system, and the creation of dhHosting's unique product, Dynamic Edge.