This article from Jason Moccia of OneSpring examines the issues with traditional textual requirements and how simulation helps solves these issues.

Jason has over ten years of experience in the software development field and is a co-founder and managing partner of OneSpring (www.onespring.net).

This is an article by Catalyze blogger Laurie Gray.  Laurie works for OneSpring and has lived in the world of user experience since 1995.

"Interactive, dynamic web experiences are becoming more popular, but it's possible to build them in a way that prevents users from being successful. This article discusses best practices in designing for and building the dynamic web, and gives the reader suggestions and tips for building a successful dynamic web experience."

From Softwaremag.com - an IT Journal

"Understanding the extent of the current issues with an application and determining the potential business impact of solving those issues will help you plan the scale of a redesign"

In this article, Meryl looks at the issues around redesigning your web application or eCommerce website and offers suggestions for a reasonable approach.

This is a copy of a presentation that Garret gave at Web Visions conference in Portland in May 2007. 

Here are Garrett's 10 steps for improving interface design:

1. Understand design
2. Cultivate the culture
3. Think critically
4. Ignore users
5. Document and code better
6. Avoid specialization
7. Cut features
8. Deliver the basics
9. Balance context and consistency
10. Fail fast.  Iterate.  Explore.

View the entire presentation for the details.

In this article, Linda discusses how to transform concepts of design education to the the business world in three applications:

1. Front end: Testing products & services before budget is spent on development; getting data early while there is still mobility to hypothesize and change approaches.
2. Teams: Forming cohesive teams quickly (within and across disciplines); make information understandable and accessible in cross-disciplined teams; facilitate facilitation: deepen transparency, effectiveness, trust and alignment.
3. Clients and Customer Relationship: Creating process framed case studies to showcase successes; design compelling presentations.

Top 10 tools for UI designers, information architects and usability specialists. Below is the complete list of tools which help the UI designers in their difficult work.

Eric Ellis explores wireframing options in this blog post.  He provides pros and cons for iRise, Axure and Powerpoint as wireframing tools.  Originally published in March 2007.

Scott Ambler of Ambysoft wrote a great article with some tips and techniques on prototyping user interfaces.

The quick overview of the tips are:

 1.  Work with real users
 2.  Get stakeholders to work with the prototype
 3.  Understand the underlying business
 4.  You should only prototype features you can build
 5.  You cannot make everything simple
 6.  It's about what you need
 7.  Get a user interface expert to help you design it
 8.  Explain what a prototype is
 9.  Consistency is critical
10. Avoid implementation decisions for as long as possible
11. Small details can make or break your user interface 

This article from InformationWeek discusses innovation with WaMu's e-commerce team.  "Every executive, every leader recognizes that in order to be successful, our technology has to be very, very strong," says Debora Horvath, executive VP and CIO.

They do it by working with customers and technology vendors to spec out projects, build prototypes in as little as 48 hours, then pushing forward into development and testing.

This article presents techniques and tools used to create requirements with a team composed of the different participants of agile projects.

This is an e-book on "How to Make Software - An Introduction to Software Development" by Nick Jenkins that was uploaded to Archive.org. 

From the introduction -- "Processes do exist, work and help make thing better.  Generally they are simple, easy to use and understand and assist rather than impede your work.  This book is an attempt to describe some simple processes for software development that worked for me and I hope will work for you."

Software requirements documentation was supposed to itemize everything that the application required. But the project was late, the users were unhappy, and the budget spun out of control. Why? Just ask the developers. 

In this article from CIO.com, Esther Schindler identifies the 5 things that CIOs should know about software requirements:

1. The Inconvenient Checkbox: Understand the Role of Requirements

2. Don't Throw It Over The Wall: The Right People Should Define the Requirements

3. Superficially Complete: Define Requirements With "Enough" Detail

4. Working from Ignorance: Recognize that Requirements Change

5. Carpet Yanking: Pay Attention to the People on the Front Line

Keeping all of Oakley's R&D and design work in one place offers tremendous advantages, Baden believes. "We use a lot of rapid prototyping equipment. I am a firm believer in sketching and hand models, but I also am driven to get that into the digital world so we can really craft the product and test its functionality." While Oakley's creative process may take months, once the design has been determined, the company can create a model and prototype inhouse in less than a week.