We wrote our book "Client vs. Developer Wars" after discovering how radically grayscreen prototyping changed the dynamics of the web development process.
Tutorial Details:
"Grayscreen" prototyping (building a simple HTML model of a website) provides an extremely effective way of communicating a website's content, structure, and functionality before design and programming begin. Prototyping overcomes many other difficulties commonly associated with web development, such as managing expectations, communicating effectively, working through the design process, and creating and delivering content.
Almost every development project has at least some aspects of these frustrations. Any developer can share many horror stories about these kinds of projects. The rest of the book goes on to describe how we achieved peace in our time.
BRIAN SLAMMED THE CAR DOOR a little harder than was necessary as he returned from the client meeting late in the day. Nobody saw the gesture, but it felt good nonetheless. He was fed up with this client, with this project, and maybe this career choice. Being a project manager for Electron Cowboys, a web development company, had its benefits - like only having to wear a tie when he had client meetings. But after this project, he seriously considered throwing in the towel and finding a job with less stress.
The most frustrating part was that the project had started off so well...
Sitting around OmniTechCorp's conference table, they discussed the goals and objectives for the new website. The client group was made up of the Vice President, the Human Resources director, the head of Information Technology, and John, the Director of Marketing and primary lead for the project. Brian and a few others from Electron Cowboys had begun to gather background information, inquiring about the client's goals and objectives. Everyone at OmniTechCorp agreed that the site needed a "new look," one that would be more "cutting edge" and "interactive." It was difficult to fully define the project because each person had his or her own idea of what the site should include. By the end of the meeting they had nailed down about 80% of their needs. The remaining 20% would be worked out later or added in a second phase of development. Armed with a basic understanding of the client's business, and a fleshed out site map, they returned to the studio to put together a proposal for the project.
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: Client vs. Developer Wars
View Tutorial: Client vs. Developer Wars
Related
Tutorials:
 JavaWorld Developer
Tools Table
JavaWorld Developer
Tools Table
|
Results of
first-ever JVM server benchmark revealed - JavaWorld - December 1997
Results of
first-ever JVM server benchmark revealed - JavaWorld - December 1997
|
3D graphics programming in
Java, Part 3: OpenGL
3D graphics programming in
Java, Part 3: OpenGL
|
JavaWorld Developer
Tools Guide: IDE
JavaWorld Developer
Tools Guide: IDE
|
JavaWorld Developer
Tools Guide: Testing Tools
JavaWorld Developer
Tools Guide: Testing Tools
|
JavaWorld Developer
Tools Guide: Compiler, Code Management
JavaWorld Developer
Tools Guide: Compiler, Code Management
|
JavaWorld Developer
Tools Guide
JavaWorld Developer
Tools Guide
|
JavaWorld Developer
Tools Guide: Virtual Machine
JavaWorld Developer
Tools Guide: Virtual Machine
|
Validation with Java and XML schema, Part 4 - JavaWorld December 2000
Validation with Java and XML schema, Part 4 - JavaWorld December 2000
|
Get the app out - JavaWorld January 2001
Get the app out - JavaWorld January 2001
|
Servlets in Apache Tomcat and BEA Systems' WebLogic Server - JavaWorld February 2001
Servlets in Apache Tomcat and BEA Systems' WebLogic Server - JavaWorld February 2001
|
Reflection
vs. code generation
Reflection
vs. code generation
|
Will Big Blue
eclipse the Java
tools market?
Will Big Blue
eclipse the Java
tools market?
|
Protect Web
application
control flow
Protect Web
application
control flow
|
Wi.Ser (WidgetServer) unified rich client framework
Wi.Ser is a Java/XML server-side GUI-framework which enables an application to run as either a monolithic Swing application, a thin-client/server Swing application, or as a Web application without any change!
|
JLAN Server v3.3
JLAN Server v3.3
JLAN Server is a high performance JavaTM based file server supporting Windows file sharing (SMB/CIFS), NFS and FTP protocols.
Write your own virtual filesystems with the core server handling all protocol exchanges with the client.
Incl
|
Leverage JNLP and SOAP for Java Thick-client Development
Leverage JNLP and SOAP for Java Thick-client Development
The hype during the mid-to-late 1990's over Java's utility to run swarms of autonomous applets was greatly exaggerated. This early enthusiasm (and marketing) for Java as a language with which devel
|
Complete Webhosting Guide, Search Web hosts, Find Plans
Complete Webhosting Guide, Search Web hosts, Find Plans
The Complete Web Hosting Guide
RoseIndia.net is the complete beginner's guide to finding a web hosting company.
Introduction to Web Hosting
What is Web Hosting? Linux vs. Windows
|
Creating EJB clients using the Eclipse Rich Client Platform
This article shows how to build a sample EJB client using the Eclipse Rich Client Platform (RCP), which has become increasingly popularity due to its extensible nature.
|
Easy Emulation With New NetBeans Mobility Pack 4.0
With the click of a button, switch back and forth between different emulation environments while developing one set of code. It's never been this easy to take advantage of Java technology's cross-platform capabilities.
|
|
|
|
