We're Getting Some Where

Mock-up 3: I'm going to use her unique ethnic heritage of being half Indian and half Scottish as part of her identity so people will realise she has a connection to both the Asian and Western world in terms of documentary photography. I think the Indian and English title needs to be integrated more. I think the black background works well to make the photo's stand out.

Mock-up 4: I have used the Indian within the banners edges to make the page less segmented and it leads the eye to the navigation to the photo gallery. I am going to experiment with different colours to make the title 'pop' (red or green). I am going to start designing an animated banner and navigation for my interactive flash pages involving a cartoon tripod and camera.

Form doing the mock ups I need the navigation to have some interesting interaction that is simple and easy to use so I'm thinking about navigation that is coming out form the use of the photo and have a camera symbol next to it. You will only see the the text when you hover over the camera symbol. Also the photo gallery will be the home page for the site so the audience will go straight to the photos in minimal time, which will help the client grab the attention of possible 'fans,' clients etc.

'Waterfall' vs 'Whirlpool' Software Development Models

The waterfall software development model is the simplest of it's type as it states that the design and creation process of a website can be of a linear order. The order is very strict

e.g. once the analysis is done only then can the requirements specification be done, then once the requirements specification is done then the design can begin and so on.

Through following the waterfall so strictly it can lead to a project being completed within its time limit every time. However it does have it downfalls. The waterfall allows you to establish a solution early by effectively freezing off each section before starting another. However this creates a problem when system requirements, user needs or design purpose change as you can't go back a stage to change the design. The waterfall can lead to the ultimate disaster- the system might become irrelevant.

To make the waterfall work for you you need highly skilled designers that are gifted with foresight to enhance the system but it will reach a point when it won't be able to be enhanced any longer. In my opinion the waterfall would be better suited to building a structure because it will have clearer objectives and and relatively stable architecture whereas the purpose of a website could change instantaneously.

(puffin,2009)

http://www.puffinonline.com/Tecademy/003%20Waterfall%20vs%20Whirlpool.pdf

In comparison the whirlpool is better design as it keeps in mind that the system requirements may change without warning so it focuses on a select few, important set of requirements in order to provide a basis for the project. The riskiest and most convenient hurdles are tackled first so that it can be predicted whether the project will become to expensive or threatening. This leads to more stable structures.

The most useful part of this model is that it allows you to work on more than one section at once, such as design and analysing or coding and maintenance.

(puffin,2009)

The whirlpool can be a useful strategy when it comes to website design because it allows you to come back to areas of the design process to make modification whereas the waterfall will only allow you time to go through once.