Skip to main content

The Power of Prototyping: The Client View

"After visiting Naked Element with my document management idea. Within a few days they were able to take that idea, and transform it into a working prototype. It was quite remarkable! Thank you Naked Element" 


- Jonathan Knight of Norfolk IT Support

When you come to see Naked Element for the first time at the start of a new project, you’ll tell us about your requirements and we’ll explain how we can implement them for you. However, we’re a new supplier. You’re new to Naked Element and we’re new to you. We haven’t worked together on a project before, so there hasn’t been the chance for trust to build up between us. And although we know we can deliver, because we have experience from many projects we’ve completed in the past, we know you would feel more comfortable if we had something to show you.

Ideally we would like to be able to show you the work we’ve done before and in a lot of cases we can. However, there are at least two reasons why we may not be able to. A lot of the work we do is internal to clients and therefore cannot be shown to a third party, even under NDA. Another reason might be that we may not have built some aspects of your requirements before so there is nothing to show.

What we can do in a lot of cases is build a basic end-to-end prototype which demonstrates a few key features and/or how a number of key technologies might work together.

For example a client recently came to speak to us and said he was looking for a system which would allow scanned documents to be stored in the cloud, classified and searched. We worked on a system in the past that included similar features, but we were unable demonstrate it as it was an internal system belonging to someone else.

To demonstrate that we could fulfil the clients requirements, we spent a few hours building a simple prototype web application which stored scanned documents in a well known cloud storage service, indexed them in an enterprise level search system and could search and retrieve them. As this was a prototype, the functionality was basic and as we knew we’d be throwing it away, we worked without our customary automated tests, continuous integration, static analysis or security.

Once we had something reasonably presentable we invited the client in to see the results. He was immediately pleased and excited about our prototype and we had demonstrated that we could deliver his requirements. Of course we explained clearly, as we would to you, that this wasn’t production ready software and further development would require investment.

Naked Element does not give away services for free, but there are occasions where a quick, basic, non-production prototype can add value to the requirements gathering process.

Prototypes are a powerful way for us to demonstrate to you what we can do, when we don’t have an appropriate example to show you. When you come to see us, ask us if a prototype is appropriate for your project with Naked Element.

This is a piece I originally wrote for the Naked Element blog. The original can be read here. You can also read the consultancy view here.

Comments

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...