Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 15 :Risk reduction through prototyping (:question:Prototyping…
CHAPTER 15 :Risk reduction through
prototyping
:question:Prototyping
WHAT ?
A software prototype is a partial, possible, or preliminary implementation of a proposed new product.
l
à một triển khai một phần, có thể hoặc sơ bộ của một sản phẩm mới được đề xuất.
WHY ?
Clarify, complete, and validate requirements
Explore design alternatives
Create a subset that will grow into the ultimate product
The primary reason for creating a prototype is to
resolve uncertainties
early in the development
process. You don’t need to prototype the entire product. Focus on
high-risk areas
Scope
A
mock-up prototype
focuses on the
user experience
; a proof-of-concept prototype (tập trung vào tính trải nghiệm của người dùng như là một bằng chứng nguyên mẫu)
Future use
A
throwaway prototype
is
discarded
after it has been used to generate feedback (Nó sẽ bị vứt bỏ sau khi đã có sự phản hồi của customer)
Form
paper prototype
whiteboard
drawing
tool
:question:Mock-ups
WHAT Mock - ups?
Is "
software prototyp
e"
possible
user interface
also called a
horizontal prototype
WHY Mock - up?
explore some specific behaviors of the intended system
refining the requirements.
let the users judge whether any functionality is missing, wrong, or
unnecessary
:question:Throwaway and evolutionary prototypes
WHY ?
Build a throwaway prototype to answer questions, resolve uncertainties, and improve requirements quality
when the team faces uncertainty, ambiguity, incompleteness, or vagueness in the requirements, or when they have difficulty envisioning the system from the requirements alone.
(khi team đối mặt với sự không chắc chắn, mơ hồ hoặc không đầy đủ của các requirement)
WHAT
non releasable prototype.
wireframe
:question:Paper prototype
low-fidelity prototype)