Wireframes

During the semester GAME I had to make an interface and design all the different screens and menu's we would be able to see. As it was only a concept version we did not have to make the final designs that you could fit right into a game but merely the interface including all the positions and buttons that would have to be there.

So for a game concept I had I made different layouts including an inventory. The concept included a rich system with a lot of different items, armour and weapons.

For our CRIA (Create a Rich Internet Application) project we built a comic builder. People could create their own characters by choosing and combining different bodyparts, clothes and skin colour.

Before we could make a working Rich Internet Application we wrote down our goals, requirements and made use cases. Every action and click you would have to make in the use case did need a place in the final layout. We made wireframes to include all the requirements we wrote down and gave those elements numbers so the programmers could built it. The combination of use cases and wireframes allowed us to test and improve our layout before building any of it.

In the end we had wireframes for every single page and pop-up. The numbers in the wireframes are mentioned in the use cases aswell. In the use cases we refer to certain numbers and it allows the reader to both read and see where he or she has to navigate to the next tep.

For our CRIA (Create a Rich Internet Application) project we made requirements and use cases. This is an example of an use case we did make.

Use cases give you a global idea what action will be taken. An extended use case will give you a lot more information, enough information for the programmers to build the system.