I.6.1 Present concept representation to customers.
Intent: The intent of this task is to present the concept model and the marketing representation to potential customers and to solicit feedback from them.
Mechanics: Individual meeting with potential customers or a "focus group" meeting in which multiple customers participate.
Do's & Don'ts
Do: Get help from experts who are well-versed in the technology or business area that underlies the concept.
Do: Recognize that luke-warm sponsorship leads to very high risk projects.
Don't: Undertake a project with poor or inadequate sponsorship, unless there are significant extenuating circumstances.
Deliverables: Notes from customer meetings
I.6.2 If there are multiple potential customers, develop means for standardizing feedback.
Intent: The intent of this task is to develop a means for standardized feedback when there a multiple potential customers.
Important Note: Some developers feel that there should be only a single "major" customer or class of customers, with others playing a supporting role. If there are multiple "major customers" or classes of major customers it may be more difficult to derive a set of consistent requirements for the software.
Mechanics: Individual meeting with potential customers or a "focus group" meeting in which multiple customers participate.
Application of Formal Methods: none or QFD meeting format
Application of CASE Tools: t.b.d.
Deliverables: Notes from customer meetings
I.6.3 Record and analyze customer feedback.
Intent: The intent of this task is to develop a systematic approach for recording, representing and analyzing customer feedback on system data, function, and behavior. In addition, special customer requirements for the technology concept are recorded and addressed as part of this task.
Mechanics: The specific mechanisms used for recording, representing and analyzing customer feedback will vary with the technology. It may be appropriate for a software group to develop a standardized form or computer-based model for this task.
Application of Formal Methods: none
Application of CASE Tools: t.b.d.
Deliverables: Analysis report based on customer meetings
Use Browser "back" arrow or return to APM Process Design Language Description