2. DVD Swap Shop Prototype To start with we will look at the functionality for the DVD Swap Shop Prototype Notice how the functionality is all “smoke and mirrors” Note also that it still looks like a finished site!

3. Planning a System There are three tools that may be used in planning a web based system. 1. The paper based design / storyboards 2. The use cases 3. Prototyping

4. Paper Based Designs Drawn up quickly and at low cost Allow the developer to plan out the screens and the flow of the pages Pen and paper is fast and cheap Once the individual screens have been designed they may be built up into a story board of the system If your design is way off the mark of the client’s expectations then it isn’t too painful to change it

5. Use Cases Use cases allow us to describe the steps that a user must go through to interact with the interface So for example the following use case describes a credit card validation process

6. Prototyping A software prototype is a mock up of the finished system. It often looks like it works as intended however the functionality is a trick. The finished code is not in place. One big benefit of prototyping is that you are able to show your system design to your client to see if it is what they are looking for. A prototype may be created very quickly and easily modified to suit the needs of your client. The prototype should look like a professional piece of software however the functionality is just an illusion. Once you know that your prototype design is suitable then you may get on with the harder job of making the code work.

7. Tools for Creating the Illusion Response.Redirect Used to navigate from one page in the site to another

8. Tools for Creating the Illusion.Visible.Enabled &.Text Properties Here you can see how the visible and enabled properties are being manipulated to control the interface. Also see how the message is displayed in the label control.