Welcome!

You will be redirected in 30 seconds or close now.

ColdFusion Authors: Yakov Fain, Jeremy Geelan, Maureen O'Gara, Nancy Y. Nee, Tad Anderson

Related Topics: ColdFusion

ColdFusion: Article

A Fusebox How-To

A Fusebox How-To

I recently received an inquiry from a developer about my Guru-on-Call service (www.TeamAllaire.com/hal). He requested help in identifying the fuses he would need for his application.

After reading my first two Fusebox articles in last year's CFDJ (Vol. 1, issues 3 and 4), he wrote, "I understand what you are explaining but implementing it is a little harder than I thought."

I wonder if others may be having this same problem - understanding the theory but a little hung up on the details. In this article I'm going to walk through developing a Fusebox application so you can see the theory put into reality. I'm assuming you've already read enough about the Fusebox methodology to understand how it works. If you need a refresher on this, check out the back issues of CFDJ online for the two articles I wrote with Steve Nelson and Gabe Roffman, or see the sidebar for a quick recap of Fusebox rules.

I find the hardest part of a large Web application is not the actual coding - thanks to Fusebox - but determining what the actual job requirements are. I'm not alone in this; it's a common complaint of developers. Over the years I've tried, in a variety of ways, to nail down customers so they wouldn't keep changing their minds. One day it occurred to me that the reason customers wouldn't stop making changes is because they couldn't. They couldn't tell me the "requirements" until they saw them reflected in the application.

If this is true, it's my job to make sure the users can see the application - and prod, poke and punch it - until they're sure that what they see is what they want. Only then do I begin the actual coding. I place great emphasis on a simulated application that looks like the real thing to the users. When they click buttons, things happen. Links are live. Forms accept inputs. And while it looks like a real application, it's a completely different matter under the hood. There's no database hooked up to the application. There are no persistent variables, perhaps no variables at all. Any use of code (CFML or otherwise) is there only to present a convincing simulation. We haven't begun coding yet; we're doing this because experience has shown that it's the only way to find out what kind of application we should build.

This methodology takes some of the stress off skilled programmers. In practice I find that over half the work required in developing an application can be done without involving programmers - a welcome discovery as they're hard to find. This prototype is handled by people skilled in interface design and graphical arts who create essentially static Web pages that mimic their real counterparts.

It's during this process that questions, comments and concerns surface. I needed a way to capture and contain this information in a central location where all those involved in the development of the application could communicate and contribute. Over time we've developed a method that effectively lets us define and refine what the application should be, do and look like.

This method relies on some ColdFusion code running alongside the designer's prototype work. Since designers typically aren't coders, we ask only that they save the Web files with a .cfm extension and append the following code onto each of these pages:

<cfinclude template="devnotes/index.cfm"> At runtime this code calls a small Fusebox application at the bottom of the page that produces something similar to Figure 1.

This allows us to preserve the history of the development of the application while providing a map for its continued evolution. I'm going to show you how I approached building this Fusebox-based mini-app, which I hope will make the process of creating a Fusebox application clearer than a mere reading of the rules.

I start off application development - even of small apps - by creating "use cases" to identify requirements for the application. These are natural language statements that require no technical background and are ideal for communicating between client and developer. At this point, use cases form the basis of our understanding of what the application should do. A sample use case might look like this:

"User should be able to log onto the system and be validated as either a user or administrator."

While use cases are wonderful for determining requirements for the application and for communicating with clients, they're too general to be of much use to developers. For this I rely on the skill of interface designers who understand how to translate the client's requirements into actual pages that show how they'll do it. This is the prototype I spoke of above. It's an iterative process; at each step we hopefully come closer to finding exactly what the client needs. Once all participants have agreed that the application is fully defined, we arrive at a prototype freeze. Now it's my job to match the use cases (as interpreted in the prototype) with one or more fuseactions.

Fuseactions, remember, define what the application is actively involved in; at any point there's only one fuseaction operating. A fuseaction is a request for action that's sent only to the fusebox (usually named index.cfm). It's fundamental to Fusebox that all requests for action go through the fusebox, not to individual fuses. Without this we're on a slippery slope where one fuse calls another and that fuse calls yet another until we end up with a tangled mess of intricate dependencies between fuses, defeating our goals of readability and reusability.

Once the request for action (the fuseaction) is sent to the fusebox, the fusebox calls on fuses to carry out the action. So the development process goes like this: use case ...> prototype ...> fuseaction(s) ...> fuse(s). By creating a table that shows the associations between use cases, fuses and fuseactions, I can see how complete my application architecture is. Table 1 is the table for this application.

As Dennis Miller says, "I don't want to get off on a rant here...," but let me say a word about naming fuses. The Fusebox.org site suggests naming prefixes for fuses based on the fuse's job: dsp_fusename for display-type fuses and so forth. I've heard heated debate over the "correct" naming scheme and I think this misses the key point - Fusebox is a development methodology, not a naming convention. My position is, if you find the naming scheme to be helpful, by all means use it. If you have another naming scheme - possibly already a standard within your company - then use that. The power of Fusebox doesn't depend on how a fuse is named, but on its clarity, conciseness and precision.

This method relies on some ColdFusion code running alongside the designer's prototype work. Since designers typically aren't coders, we ask only that they save the Web files with a .cfm extension and append the following code onto each of these pages:

<cfinclude template="devnotes/index.cfm">

At runtime this code calls a small Fusebox application at the bottom of the page that produces something similar to Figure 1.

This allows us to preserve the history of the development of the application while providing a map for its continued evolution. I'm going to show you how I approached building this Fusebox-based mini-app, which I hope will make the process of creating a Fusebox application clearer than a mere reading of the rules.

I start off application development - even of small apps - by creating "use cases" to identify requirements for the application. These are natural language statements that require no technical background and are ideal for communicating between client and developer. At this point, use cases form the basis of our understanding of what the application should do. A sample use case might look like this:

"User should be able to log onto the system and be validated as either a user or administrator."

While use cases are wonderful for determining requirements for the application and for communicating with clients, they're too general to be of much use to developers. For this I rely on the skill of interface designers who understand how to translate the client's requirements into actual pages that show how they'll do it. This is the prototype I spoke of above. It's an iterative process; at each step we hopefully come closer to finding exactly what the client needs. Once all participants have agreed that the application is fully defined, we arrive at a prototype freeze. Now it's my job to match the use cases (as interpreted in the prototype) with one or more fuseactions.

Fuseactions, remember, define what the application is actively involved in; at any point there's only one fuseaction operating. A fuseaction is a request for action that's sent only to the fusebox (usually named index.cfm). It's fundamental to Fusebox that all requests for action go through the fusebox, not to individual fuses. Without this we're on a slippery slope where one fuse calls another and that fuse calls yet another until we end up with a tangled mess of intricate dependencies between fuses, defeating our goals of readability and reusability.

Once the request for action (the fuseaction) is sent to the fusebox, the fusebox calls on fuses to carry out the action. So the development process goes like this: use case ...> prototype ...> fuseaction(s) ...> fuse(s). By creating a table that shows the associations between use cases, fuses and fuseactions, I can see how complete my application architecture is. Table 1 is the table for this application.

As Dennis Miller says, "I don't want to get off on a rant here...," but let me say a word about naming fuses. The Fusebox.org site suggests naming prefixes for fuses based on the fuse's job: dsp_fusename for display-type fuses and so forth. I've heard heated debate over the "correct" naming scheme and I think this misses the key point - Fusebox is a development methodology, not a naming convention. My position is, if you find the naming scheme to be helpful, by all means use it. If you have another naming scheme - possibly already a standard within your company - then use that. The power of Fusebox doesn't depend on how a fuse is named, but on its clarity, conciseness and precision.

More Stories By Hal Helms

Hal Helms is a well-known speaker/writer/strategist on software development issues. He holds training sessions on Java, ColdFusion, and software development processes. He authors a popular monthly newsletter series. For more information, contact him at hal (at) halhelms.com or see his website, www.halhelms.com.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@ThingsExpo Stories
"delaPlex is a software development company. We do team-based outsourcing development," explained Mark Rivers, COO and Co-founder of delaPlex Software, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
We all know the latest numbers: Gartner, Inc. forecasts that 6.4 billion connected things will be in use worldwide in 2016, up 30 percent from last year, and will reach 20.8 billion by 2020. We're rapidly approaching a data production of 40 zettabytes a day – more than we can every physically store, and exabytes and yottabytes are just around the corner. For many that’s a good sign, as data has been proven to equal money – IF it’s ingested, integrated, and analyzed fast enough. Without real-ti...
"There's a growing demand from users for things to be faster. When you think about all the transactions or interactions users will have with your product and everything that is between those transactions and interactions - what drives us at Catchpoint Systems is the idea to measure that and to analyze it," explained Leo Vasiliou, Director of Web Performance Engineering at Catchpoint Systems, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York Ci...
I wanted to gather all of my Internet of Things (IOT) blogs into a single blog (that I could later use with my University of San Francisco (USF) Big Data “MBA” course). However as I started to pull these blogs together, I realized that my IOT discussion lacked a vision; it lacked an end point towards which an organization could drive their IOT envisioning, proof of value, app dev, data engineering and data science efforts. And I think that the IOT end point is really quite simple…
A critical component of any IoT project is what to do with all the data being generated. This data needs to be captured, processed, structured, and stored in a way to facilitate different kinds of queries. Traditional data warehouse and analytical systems are mature technologies that can be used to handle certain kinds of queries, but they are not always well suited to many problems, particularly when there is a need for real-time insights.
Big Data, cloud, analytics, contextual information, wearable tech, sensors, mobility, and WebRTC: together, these advances have created a perfect storm of technologies that are disrupting and transforming classic communications models and ecosystems. In his session at @ThingsExpo, Erik Perotti, Senior Manager of New Ventures on Plantronics’ Innovation team, provided an overview of this technological shift, including associated business and consumer communications impacts, and opportunities it ...
You think you know what’s in your data. But do you? Most organizations are now aware of the business intelligence represented by their data. Data science stands to take this to a level you never thought of – literally. The techniques of data science, when used with the capabilities of Big Data technologies, can make connections you had not yet imagined, helping you discover new insights and ask new questions of your data. In his session at @ThingsExpo, Sarbjit Sarkaria, data science team lead ...
Extracting business value from Internet of Things (IoT) data doesn’t happen overnight. There are several requirements that must be satisfied, including IoT device enablement, data analysis, real-time detection of complex events and automated orchestration of actions. Unfortunately, too many companies fall short in achieving their business goals by implementing incomplete solutions or not focusing on tangible use cases. In his general session at @ThingsExpo, Dave McCarthy, Director of Products...
Is your aging software platform suffering from technical debt while the market changes and demands new solutions at a faster clip? It’s a bold move, but you might consider walking away from your core platform and starting fresh. ReadyTalk did exactly that. In his General Session at 19th Cloud Expo, Michael Chambliss, Head of Engineering at ReadyTalk, will discuss why and how ReadyTalk diverted from healthy revenue and over a decade of audio conferencing product development to start an innovati...
WebRTC is bringing significant change to the communications landscape that will bridge the worlds of web and telephony, making the Internet the new standard for communications. Cloud9 took the road less traveled and used WebRTC to create a downloadable enterprise-grade communications platform that is changing the communication dynamic in the financial sector. In his session at @ThingsExpo, Leo Papadopoulos, CTO of Cloud9, discussed the importance of WebRTC and how it enables companies to focus...
SYS-CON Events announced today that 910Telecom will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Housed in the classic Denver Gas & Electric Building, 910 15th St., 910Telecom is a carrier-neutral telecom hotel located in the heart of Denver. Adjacent to CenturyLink, AT&T, and Denver Main, 910Telecom offers connectivity to all major carriers, Internet service providers, Internet backbones and ...
SYS-CON Events announced today that LeaseWeb USA, a cloud Infrastructure-as-a-Service (IaaS) provider, will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. LeaseWeb is one of the world's largest hosting brands. The company helps customers define, develop and deploy IT infrastructure tailored to their exact business needs, by combining various kinds cloud solutions.
Manufacturers are embracing the Industrial Internet the same way consumers are leveraging Fitbits – to improve overall health and wellness. Both can provide consistent measurement, visibility, and suggest performance improvements customized to help reach goals. Fitbit users can view real-time data and make adjustments to increase their activity. In his session at @ThingsExpo, Mark Bernardo Professional Services Leader, Americas, at GE Digital, discussed how leveraging the Industrial Internet a...
The cloud market growth today is largely in public clouds. While there is a lot of spend in IT departments in virtualization, these aren’t yet translating into a true “cloud” experience within the enterprise. What is stopping the growth of the “private cloud” market? In his general session at 18th Cloud Expo, Nara Rajagopalan, CEO of Accelerite, explored the challenges in deploying, managing, and getting adoption for a private cloud within an enterprise. What are the key differences between wh...
SYS-CON Events announced today that Venafi, the Immune System for the Internet™ and the leading provider of Next Generation Trust Protection, will exhibit at @DevOpsSummit at 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Venafi is the Immune System for the Internet™ that protects the foundation of all cybersecurity – cryptographic keys and digital certificates – so they can’t be misused by bad guys in attacks...
The best-practices for building IoT applications with Go Code that attendees can use to build their own IoT applications. In his session at @ThingsExpo, Indraneel Mitra, Senior Solutions Architect & Technology Evangelist at Cognizant, provided valuable information and resources for both novice and experienced developers on how to get started with IoT and Golang in a day. He also provided information on how to use Intel Arduino Kit, Go Robotics API and AWS IoT stack to build an application tha...
Amazon has gradually rolled out parts of its IoT offerings in the last year, but these are just the tip of the iceberg. In addition to optimizing their back-end AWS offerings, Amazon is laying the ground work to be a major force in IoT – especially in the connected home and office. Amazon is extending its reach by building on its dominant Cloud IoT platform, its Dash Button strategy, recently announced Replenishment Services, the Echo/Alexa voice recognition control platform, the 6-7 strategic...
For basic one-to-one voice or video calling solutions, WebRTC has proven to be a very powerful technology. Although WebRTC’s core functionality is to provide secure, real-time p2p media streaming, leveraging native platform features and server-side components brings up new communication capabilities for web and native mobile applications, allowing for advanced multi-user use cases such as video broadcasting, conferencing, and media recording.
IoT generates lots of temporal data. But how do you unlock its value? You need to discover patterns that are repeatable in vast quantities of data, understand their meaning, and implement scalable monitoring across multiple data streams in order to monetize the discoveries and insights. Motif discovery and deep learning platforms are emerging to visualize sensor data, to search for patterns and to build application that can monitor real time streams efficiently. In his session at @ThingsExpo, ...
Verizon Communications Inc. (NYSE, Nasdaq: VZ) and Yahoo! Inc. (Nasdaq: YHOO) have entered into a definitive agreement under which Verizon will acquire Yahoo's operating business for approximately $4.83 billion in cash, subject to customary closing adjustments. Yahoo informs, connects and entertains a global audience of more than 1 billion monthly active users** -- including 600 million monthly active mobile users*** through its search, communications and digital content products. Yahoo also co...