Forgotten Methodology Prototyping Methodology Presenter Vineeth Reddy Lakkadi

Index • • Introduction Types of Prototyping Traditional Framework New Framework Advantages Disadvantages Importance

Introduction • The IEEE defines prototyping as a development approach promoting the implementation of

Types of Prototyping • Rapid throwaway - Developing the prototype with primary requirements. •

Traditional Framework • Identify the Objectives • Gather Business & Stakeholder requirements • Document

New Framework • Identify the Objectives & Main Features • Gather requirements • Develop

Advantages • Easily fits into any software developing methodology • Customer knows what he

Disadvantages • Time taking process for learners • Frequent changes may occur in the

Importance of Activity Diagrams in Prototyping • Easy to understand workflow between users and

How to gather requirements? Need Vs Want Need - Which is a must to

Tools for Prototyping • Axure • Mockplus • In. Vision • Farmer • Marvel

Slides: 13

Download presentation

Forgotten Methodology (Prototyping Methodology) Presenter: Vineeth Reddy Lakkadi (MBA, MSIT, Ph. D. IT (Pursuing)) Email: Vineeth. reddy 5@gmail. com “Learn The Technique Implement in Your Way”

Index • • Introduction Types of Prototyping Traditional Framework New Framework Advantages Disadvantages Importance of Activity Diagrams in Prototyping • How to gather requirements? (Need Vs Want) • Prototype Model • Tools for prototyping

Introduction • The IEEE defines prototyping as a development approach promoting the implementation of a pilot version of the intended product. • Different industries like electronics, automobiles, IT etc. uses prototype to Identify & analyze the issues and defects in the product. • In a software application the prototype helps to find the bugs or issues.

Types of Prototyping • Rapid throwaway - Developing the prototype with primary requirements. • Evolutionary - Refined after each iteration • Incremental - Breaking the concept into modules • Extreme - Used specifically for web development

Traditional Framework • Identify the Objectives • Gather Business & Stakeholder requirements • Document the requirements • Document Use cases & Design Activity Diagrams • Design the prototype • Refine the prototype

New Framework • Identify the Objectives & Main Features • Gather requirements • Develop product backlog • Design Activity Diagrams • Design the prototype • Refine the prototype

Advantages • Easily fits into any software developing methodology • Customer knows what he is going to get • Refinement process is easy • Missing requirements can be fixed • Saving efforts & cost • Developer can understand the needs of the user • Customer satisfaction

Disadvantages • Time taking process for learners • Frequent changes may occur in the requirements • Development stage will be delayed • Customer might think prototype as the actual product • Customer expects the product will be delivered soon

Importance of Activity Diagrams in Prototyping • Easy to understand workflow between users and the system • Used as the guides in designing prototype • Easy for the developer to understand the prototype

How to gather requirements? Need Vs Want Need - Which is a must to the business to run operations. Want - Which a business does not need in its operations.

Tools for Prototyping • Axure • Mockplus • In. Vision • Farmer • Marvel • Origami • Proto. io

Questions & Feedback

Thank you