Frequently, my dreams are filled with never-ending math problems floating alongside fine art forms even Dali could envy.
I have yet to decide if this is a gift or a curse.
When a project is initiated, I like start with storyboarding with an intent to refine high level requirements. This provides the stakeholder a visualization of the data's flow. The hope here is to have a set of prioritized features we can later iterate through in design and development.
Wireframes are an extension to our storyboards. The key here is that everything is visual. This is a skeletal framework with page flows. I typically start with the highest priority features and work my way down as time and budget allows.
Once the wireframes are refined and the requirements are solidified, I like to create rapid prototypes of the pages within the application. This helps the user further visualize the end result. Colors, images, and overall styling is added here; however, it's still as generic as possible from a programming perspective.
As soon as the primary features are identified and refined, I will work with a development team (which usually includes myself) to begin development tasks. Beginning with the highest priority, each feature loops through a somewhat agile process and is fully tested and demoed to the stakeholder before the next feature is begun. My experience is primarily in Open Source technologies so that is usually the realm I like to stay and play in.
Dis my favorite part. As soon as the overall framework and functionality is in place, I will then jump in and combine the prototypes with the back end code. Though it is my strongest skill, this is not a very cut and dry process as there is a lot of finagling that goes on to make sure the two sides of the house cooperate.
Test cases are created as requirements are refined. Testing occurs during all stages of development. Ideally, at each feature release, the code is handed off to QA. Through the years, and sometimes the hard way, I've learned that skimping in your test practices can ruin a beautiful, new, innovative application in about 5 minutes.
I love this part just as much. A big piece of unveiling new functionality or software in an enterprise is making sure it is effectively communicated amongst all of the business units. Considering you are required to speak not only to the technical groups, but also to end users, I've found creating visual walkthroughs via video or animated presentations of which highlight noteworthy items to be the best way to communicate to all parties.
Feedback is important. I love getting right in there with the primary end users and watching them use the new application. They navigate in ways sometimes you might have least expected. These moments can prove to be invaluable in the successful delivery and future maintenance of your application.
Internationalization with JSF 2.0,
July 9, 2013
Material Design, Like Whoa
August 26, 2014
ui:repeat: Using varStatus to Display the Row Value
January 1, 2013
Adding Outer Glow to an Object in Illustrator
September 9, 2013
JSF Select Menu Auto Submit on Value Change
November 4, 2013
That Pesky Compability Mode Button in IE
July 31, 2014
April 2, 2014
Customizing Ping® Federation Login Page
September 23, 2013