Secrets of Going Codeless

How to Build Enterprise Apps without Coding

Building applications without code still requires methods and skills. In this article I describe the methods that Encanvas has used for well over a decade to successfully deliver situational applications developments.

The first application created on Encanvas in a codeless form was a silly form for appraisals.  That was in 2002 I seem to recall.  Since then the size and scale of applications authored 'codeless' have included several enterprise-wide systems, a few pan-regional systems and even industry-wide systems.

In the early years of Encanvas, most of the applications were created by Andrew Lawrie (the creator of Encanvas) himself.  It was impressive enough that Andy could take an enterprise requirement and just 'make it happen' all by himself, but since then the community of Encanvas authors and architects has grown exponentially.

The types of backgrounds of authors too is wide and varied.  I've produced a few systems and my background is generally sales and marketing.  A couple of the guys are 'proper developers' that have sold their soul to the codeless god, while many are domain expert consultants, entrepreneurs, project managers and analysts.  What do they have in common?  They can all use a mouse I guess!!

As the scale of applications gets bigger, and the variety of author skills broadens, it becomes more important to adopt methods to optimize the authoring process. No question, it is possible without method to be able to produce results with codeless software, but then that places a 100% reliance on the talents of the practitioner.

CAAD came out of a series of 'interventions' to streamline the codeless authoring process that all hang together pretty well and perform certain key tasks well (like requirements gathering).

Hopefully you find the linked document interesting and easy enough to absorb.  If you have any questions, I'd be happy to field them.

Ian.

Keywords:

Enterprise Applications, Codeless Software Development, CAAD, Encanvas, Situational Applications, IT Strategy, Application Life-Cycle Management

Mining Sub-Surface Spend Economies - The role of Federated Spend Analytics Platforms

Sub Surface Spend

Slideshare presentation on sub-surface spend

In this presentation I argue the case for federated spend management software tools as a vehicle to affordably source sub-surface spend economies in organizations where procuement teams have harvested the low hanging fruit and now need to consider digging deeper into spend behaviors to achieve the next stage of procurement economies.

Key words:
Sub-Surface Spend, federated spend analysis platforms, encanvas, situational applications, data mashups, actionable insights, procurement strategies

Real-Time Data Diagnostics - How Encanvas Takes Agile To A New Level

Have you ever created an application only to find it doesn’t work?  

Sounds crass doesn’t it.  The fact is that most manually programmed applications have errors in them.  But modern codeless applications design environments like Encanvas overcome the majority of programming ‘hick-ups’ by auto-generating the code that underpins authored applications through the use of drag-and-drop, point-and-click and wizard based interfaces.   That means almost no testing, tuning or re-working costs for business IT projects.

This is important to the software and data integration industry that has a pretty sour track-record of project delivery.  The article ‘Why Your IT Project May Be Riskier Than You Think’ by HBR (November 2011), that followed a survey of 1,471 IT projects with an average spend of $167m, found that:

• The average overrun was 27%
• One in six of the projects studied was a black swan, with a cost overrun of 200%.
• Almost 70% of black swan projects also overrun their schedules.

One area that has remained to challenge the software development industry has been how to overcome data integration errors on deployed applications.  No matter HOW a design environment links to data sources, such is the complexity of the task that it becomes almost inevitable that some data integration errors will creep in when developing a complex database-centric application.  For example, a field in a table could be re-named or deleted in the source database resulting in no data appearing on the published site page because the database is unable to find the requested data.  Sometimes it’s quite easy to track down these issues; other times – with complex applications – it takes a pretty neat understanding of the application and how the data hangs together in order to overcome the issue.  When applications designers have spent hours working on a great application, the very last thing they need is to fall at the last hurdle and find ‘the app doesn’t work’.

Thankfully, Encanvas now overcomes this problem area too with its new real-time data diagnostics technology.

Those familiar with Encanvas will know that the design of applications all takes place in ENCANVAS CREATE DESIGN STUDIO in a codeless environment.  It offers design elements, data linking and action linking features to build content and logic into applications using an easy to learn design interface that has the look and feel of a desktop application. What it actually produces are cloud deployed ASP.NET portals that present data in HTML so they can be used on desktop, tablet. Mobile and digital TV platforms.  While it adheres to Microsoft Enterprise Platform standards of security, performance tuning and scalability, it removes the use of programming and means application can be authored in workshops with users and stakeholders.

When applications are published to the cloud, Encanvas’s new visual diagnostic mode allows designers to review the data connections employed in applications using an innovative visual referencing system.

Each field is audited for its data connections and the results are presented on the screen.

Full details of connections are presented when clicking on the associated icon. Using the live data diagnostic features of Encanvas removes the last major hurdle in applications engineering for authors of business applications.

The roll call of applications authoring productivity features in Encanvas now includes:

• Codeless platform and server installation
• Codeless private cloud creation (and replication)
• Codeless data connectors
• Codeless information flow automation
• Codeless data mashup and automated data structure creation
• Codeless design elements
• Codeless logic link creation
• Codeless action layer automation
• Codeless KPI creation
• Codeless map creation
• Codeless upload/ETL automation
• Codeless download (export) with formatted reporting/printing
• Codeless social network creation
• Codeless graphing (and graphing logic) creation
• Codeless email workflow creation
• Codeless publishing
• Codeless UI design 
• Codeless federated user identity management augmentation
• Codeless site structure design
• Codeless and real-time data diagnostics
• Automated design element creation from data structures
• Automated database creation from designed data structures
• Automated lookup table generation
• Automated form creation

If you’ve yet to try Encanvas, it’s easy to arrange. Simply email sayhello@encanvas.com and request a secure private-cloud Remote[Space] to have a go at codeless situational applications authoring for yourself.

Big Data Training Workshop 1: Introducing Situational Applications

BIG DATA TRAINING WORKSHOP 1: INTRODUCING SITUATIONAL APPLICATIONS

Situational Applications are any software applications designed to serve the long-tail of demand from individual information workers (or small communities of workers) for ‘better ways to analyze data, capture it and act on it’.  They may be created for a moment and then discarded, or later adopted and absorbed into enterprise systems.  Sometimes they are unkindly described as throw-away or experimental applications but I prefer to think of them as the first step on the accelerated business innovation journey.  They are key to the world of BIG DATA because they are the tool-kit to apply learning lessons from data and turn it into better ways of working.

I’ve had such overwhelming feedback and interest on the Big Data Situational Applications articles I’ve penned that it’s encouraged me to write a few more that walk through how we use Encanvas to assimilate data from various sources, analyze it and act on what matters.  Of course there are a wide variety of Encanvas partners and solutions providers that offer ‘off-the-shelf’ industry solutions so in this series of articles I’m assuming that the application is something ‘custom’ or new that hasn’t been addressed before.

In this series of articles I plan to include the following topics:

1. Introduction to situational applications 
2. Data assimilation: what it is and how to do it
3. Operational Analytics: making sense of data with useful tools
4. ACT: designing apps to iterate processes one canvas at a time

The obvious article that’s missing is a training course on HOARDING technologies like Hadoop, Microsoft Business Intelligence, SAP hana etc.  The reason I’ve missed this step is because (a) I don’t know anything about it and, (b) In many cases you don’t need to hoard data and organize it before creating situational applications.

Just a few brief introductions before we start…
If you’ve not encountered Encanvas software before, it’s basically a business computing platform designed to exploit data held in different places and different formats by designing situational applications to analyze data and apply learning lessons. Unlike business intelligence systems and other platforms that HOARD data and create a data warehouse before you can do anything, Encanvas connects to, and organizes data into new structures by exposing data to designers in a consistent format to enable ‘drag and drop’ selection and formation of new data structures.  It’s really easy to use for business analysts, and it produces results quick, so it’s realistic to develop situational applications in workshops with stakeholders, users and sponsors present (yes really!).

Companies like USTech Solutions, NDMC Consulting, Ambridge Consulting, Nybble, SovereignTech and others use Encanvas as a tool-kit to author situational applications as a service.


Everything you wanted to know about situational applications but were afraid to ask
The first ever situational application platform was the spreadsheet.  Times are changing.  Information workers need to deal with much bigger data sets and IT leaders must ensure that data is organized, always-secure and any software application must adhere to necessary standards of governance and compliance.  The new generation of situational applications platforms like Encanvas are engineered to meet ‘IT hygiene standards’ of security, performance and scalability, yet they provide unrivalled self-service tooling to enable web workers to fully exploit accessible data resources.

History
Encanvas was conceived in 2002 by the founders of NDMC Consulting.  It was initially an idea (perhaps a belief) that in future, business users would seek to work in social groups that would span across and beyond enterprise boundaries and, having experienced this new form of business workplace, key knowledge workers and creative contributors to business processes would seek to be able to author applications for their communities in a form purposely sculptured to the needs of the community of use.

This idea of socially-centric, built-for-purpose and potentially thrown-away software was unknowingly endorsed by technology thought-leader Clay Shirky in his essay ‘Situated Software’ published in March 2004 when he wrote, “Part of the future I believe I'm seeing is a change in the software ecosystem which, for the moment, I'm calling situated software. This is software designed in and for a particular social situation or context. This way of making software is in contrast with what I'll call the Web School (the paradigm I learned to program in), where scalability, generality, and completeness were the key virtues.”

In August 2007, Luba Cherbakov and a team from IBM wrote the first of two articles on what they described as ‘Situational Applications’.  In their paper titled ‘SOA meets situational applications, Part 1: Changing computing in the enterprise’, Cherbakov and her colleagues defined the attributes of Situational Applications, stating, “The loosely accepted term situational applications describe applications built to address a particular situation, problem, or challenge. The development life cycle of these types of applications is quite different from the traditional IT-developed, SOA-based solution. SAs are usually built by casual programmers using short, iterative development life cycles that often are measured in days or weeks, not months or years. As the requirements of a small team using the application change, the SA often continues to evolve to accommodate these changes. Significant changes in requirements may lead to an abandonment of the used application altogether; in some cases it's just easier to develop a new one than to update the one in use. The idea of end-user computing in the enterprise is not new. Development of applications by amateur programmers using IBM Lotus® Notes®, Microsoft® Excel spreadsheets in conjunction with Microsoft Access, or other tools is widespread. What's new in this mix is the impressive growth of community-based computing coupled with an overall increase in computer skills, the introduction of new technologies, and an increased need for business agility. The emergence of Asynchronous JavaScript + XML (Ajax)—which leverages easy access to Web-based data and rich user interface (UI) controls—combined with the Representational State Transfer (REST) architectural style of Web services offers an accessible palette for the assembly of highly interactive browser-based applications.”

Today
Situational applications remain a largely misunderstood concept in enterprise computing due to pre-conceived notions about how IT works that are now proven to be fatally flawed.  These include:

• Applications that can be designed cheaply enough to ‘throw-away’ can’t possibly be expected to meet enterprise data integration, security, performance and tuning expectations.
• It’s not possible to create the critical-mass of building blocks and tooling required to remove the majority of programming overheads.
• Organizations are better off buying best of breed solutions, to then mackle them together.
• There is no competitive advantage to be gained from IT as companies now use the same platforms. 
• If players like Microsoft, Google, Oracle and IBM haven’t made it work then it isn’t possible!

In many ways the demand for situational applications has never gone away but, until the emergence of the BIG DATA story, the message of Situational Applications has struggled to find a voice within organizations as it is a genre of technology designed to meet the many and varied ‘small’ needs of a variety of communities. It has lacked any understandable clarity of purpose in IT architectures.  Instead of sourcing expert tools, CIOs with other things to think about have instead done their best with 'approved enterprise tools' – Content Management applications like Microsoft SharePoint and Enterprise Applications Platforms like IBM Websphere and Oracle Weblogic.

BIG DATA has led to the re-discovery of the important role of expert situational applications tooling as organizations acknowledge the need to equip analysts and middle-managers with self-service, community-centric applications to assimilate, analyze and act on the actionable insights they’re surfacing.  Technologies designed support the creation of Situational Applications are by necessity ‘codeless’ which means the authoring of applications is done using drag and drop, point and click or wizard based interfaces that automatically generate the programming code rather than it being authored ‘manually’.  This reduces errors in code.  It also means that applications can be authored in near real-time; very often within a workshop environment.  Having stakeholders directly engage in the authoring process creates better applications in a shorter time.

In the next article in this series, read about the first stage in Accelerated Business Innovation: Data assimilation: what it is and how to do it.

BIG DATA with Encanvas (infographic)

In this infographic I explain how Encanvas employs big data as its raw material to accelerate the pace of business innovation.  Of course, data doesn't have to be BIG to be useful.  Over the last 10-years I've seen many good ways of extracting value from data by simply having more data of different types accessible to business analysts. For example, one professional services company was able to improve their presentation of credentials by exploiting data from a third party database to enrich their customer records and map their customer records onto their project data to build a richer understanding of what they'd delivered (how and to whom) to improve the quality of their case stories.

Accelerating the pace of business innovation requires not just the means to harvest data and analyze it - businesses ALSO need the tools to improve their processes and embed learning lessons into their day-to-day activities.  This is by far no mean feat!

Encanvas overcomes the natural reticence of organizations to change, break age old 'norms of behavior' and embrace better ways of working by creating applications without asking organizations to invest in IT infrastructure or spend days, weeks or months on IT projects with no clear ROI.  Building a situational application in a day or half-day workshops session means that businesses can understand the value of data - and apply it - removing the risk and cost of process change.

Speaking to users of Encanvas, they will very often rebuild apps many times as they learn from their data and re-apply learning lessons to improve processes.  This would not be practical or affordable if a traditional software development or enterprise platform like Microsoft SharePoint was used to fashion applications.

The original infographic can be viewed on slideshare here.