g063 – prototyping. learning objective: at the end of this topic you should be able to: describe...

30
G063 – Prototyping

Upload: jesse-floyd

Post on 18-Jan-2018

216 views

Category:

Documents


0 download

DESCRIPTION

Prototyping

TRANSCRIPT

Page 1: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

G063 – Prototyping

Page 2: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Learning Objective:At the end of this topic you should be able to:

• describe prototyping as a software development methodology

Page 3: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Prototyping

Page 4: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Prototyping• normal design process involves producing a

requirements specification – in consultation with the end users

Page 5: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Prototyping• normal design process involves producing a

requirements specification – in consultation with the end users

• prototyping involves producing a working system early in the design process– possibly without consultation with the end users

Page 6: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Prototyping• normal design process involves producing a

requirements specification – in consultation with the end users

• prototyping involves producing a working system early in the design process– possibly without consultation with the end users

• prototype system will not necessarily be efficient– because a full analysis has not been done. – will not have all the functionality end user requires.

Page 7: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Prototyping• normal design process involves producing a

requirements specification – in consultation with the end users

• prototyping involves producing a working system early in the design process– possibly without consultation with the end users

• prototype system will not necessarily be efficient– because a full analysis has not been done. – will not have all the functionality end user requires.– will be a step towards what the end user wants.

Page 8: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Steps in Prototyping

Page 9: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Steps in Prototyping1. basic requirements identified

Page 10: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Steps in Prototyping1. basic requirements identified2. prototype developed

Page 11: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Steps in Prototyping1. basic requirements identified2. prototype developed3. prototype tested by end user

– shortcomings in the prototype are identified

Page 12: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Steps in Prototyping1. basic requirements identified2. prototype developed3. prototype tested by end user

– shortcomings in the prototype are identified

4. prototype is improved – production of a further prototype

Page 13: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Steps in Prototyping1. basic requirements identified2. prototype developed3. prototype tested by end user

– shortcomings in the prototype are identified

4. prototype is improved – production of a further prototype

• repeat steps 3&4 – until end user satisfied

Page 14: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Steps in Prototyping1. basic requirements identified2. prototype developed3. prototype tested by end user

– shortcomings in the prototype are identified

4. prototype is improved – production of a further prototype

• repeat steps 3&4 – until end user satisfied

• this process is called Iteration

Page 15: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Steps in PrototypingInitial Investigation Basic requirements for the new

system identified.

Prototype Developed This stage is repeated with each prototype being closer to meeting the end user's needs.

Use the prototype Prototype is tested. Input from end user.

End User's needs met?

Working system The prototype has developed into a working system.

Feedback from End User used to evaluate the effectiveness of the prototype

No

Yes

Page 16: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Advantages of Prototyping

Page 17: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Advantages of Prototyping• a usable system produced early in the process,

– allows the end users to evaluate it

Page 18: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Advantages of Prototyping• a usable system produced early in the process,

– allows the end users to evaluate it • gives end users the opportunity to provide input

– to the next stage of development

Page 19: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Advantages of Prototyping• a usable system produced early in the process,

– allows the end users to evaluate it • gives end users the opportunity to provide input

– to the next stage of development• constant feedback should ensure that the resulting

system really does match their needs

Page 20: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Advantages of Prototyping• a usable system produced early in the process,

– allows the end users to evaluate it • gives end users the opportunity to provide input

– to the next stage of development• constant feedback should ensure that the resulting

system really does match their needs• user becomes comfortable with the HCI

– has been part of the on-going development

Page 21: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Disadvantages of Prototyping• once prototype is working, it may not be modified

– management see early prototype to be working• implement partially complete system too early

– inefficient systems may never be tidied up• early prototypes used instead of fully functional systems

– may cause problems later • if data usage increases • if the system is to be adapted to meet new processing needs.

Page 22: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Examination QuestionA firm is going to introduce on-line ordering of its products.

The user interface for the on-line ordering system will be developed using prototyping.

(a) Describe the process of prototyping. [2]

(b) Explain the process of iteration and why it is used. [4]

January 2007 Q2

Page 23: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Iteration

Page 24: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Iteration• “repeated design and refine”.

Page 25: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Iteration• “repeated design and refine”. • design is reviewed repeatedly

– by the users

Page 26: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Iteration• “repeated design and refine”. • design is reviewed repeatedly

– by the users• users suggestions lead to changes

Page 27: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Why use Iteration?

Page 28: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Why use Iteration?• users feel more confident about the outcome and so

are more likely to use it.

Page 29: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Why use Iteration?• users feel more confident about the outcome and so

are more likely to use it.

• system correctly matches the needs & expectations of the users – because they have had an input in the design.

Page 30: G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Why use Iteration?• users feel more confident about the outcome and so

are more likely to use it.

• system correctly matches the needs & expectations of the users – because they have had an input in the design.

• no waste of waste time & money producing something that’s not right.