MSDN Online Voices - More Or Hess: Demo Analysis
Some of your programmers may be very easy: Sitting in front of the table, writing code according to the pre-design specification. The milestones in front of them have been finely planned, clearly identifying the functional goals of all members of the group. At some stage in the development cycle, you will enter the stage of the so-called "last sprint". The planned risk is heavy, of course, everyone must work late at night, and will work overtime on the weekend to complete the plan. Despite this, the road in front of you is often clear. Everyone is very clear that I have to go, how can I arrive? Other programmers are completely different. These people are designed and developed by the code just as a demonstration, or to showcase the original software solutions that are about to be developed. Not every company is going to develop and need this development. But there is no doubt that this work requires a different type of programmer, and like this programming requires a different type of programming method. The presentation I said is not just a function of demonstrating a completed (or close) application in proverb. What I said is that the design and development of product demonstrations in the case of "actual" products have not yet been developed. This demonstration is used to display the "potential" of applications and technology to managers, partners and investors. In a GUI / Web-based environment, everything depends on what it seems to "look" in the development cycle. And if the purpose of the demonstration is to evoke interest and manufacture, the visual effect of the demo will often become the key to clear the intentions. Imagine how to demonstrate to connect a PC to home automation. There is a button on your application, which is written to "Turn the light". You press the button, the light is off. Yeah, it's really hard. Now, imagine that this demo is made with PocketPC. The top view of the room layout appears, and the position of the lamp is also marked. The presenter uses the "drag and drop" function Selected several lights in the room, dragging them to the virtual switch of the PocketPC screen. Then, the demons are gently pressing the virtual switch on the screen, all selected lights are out. Next, the demons are dragged the virtual switch on the icon representing the switch in the room. He went to the switch and gently pressed the switch, and all the lights were bright. Yes, it is still a simple demonstration, but it is much more impressive than the first. From a technical point of view, this demonstration does not change; changed only the way the demo and the props used by the demo. It is necessary to focus on that such a small automation presentation does not represent the usage of the system in general. I mean, how many people are willing to turn off the lights and turning lights like this? - Have to open PocketPC, check the layout map of the room, select the light, drag them onto the screen, then press the button. In real life, the use time of such a tool is very short: When installing the automation system for the first time, use them to "Set" the physical location of the lamp switch in the room, and then rarely used. However, if you just go to a real switch, gently press, a light is on. Then tell the audience: "I believe me, this lamp is connected to the switch through the home automation system." How can such a demonstration be exciting? To complete such prototypes and demonstrations, there is a need for a number of different programmers and a different way of thinking. Everything begins with a demo script, this script is used to introduce what you think can be used to touch people. Maybe you need to use tools like Adobe Photoshop or Microsoft PowerPoint® to make several interface analog maps. This can drive the process, and other members in the help group will grasp the concepts that need to be conveyed from the overall. Next, you need to write some underlying technology infrastructure - just let you connect some components to work, you can work. Then, start creating the visual interface to use, try to make them eye-catching.
