This document contains a questionnaire for a product team working on the MPASS website. It includes questions about the objectives and critical success factors of the website, intended users and how they will use the site. It also asks for clarification on various aspects of managing master data, integrating with manufacturing processes, generating and authenticating serialized codes, required use cases, and the branding and market positioning of the existing product. The questionnaire seeks to understand key details about the functionality and user experience of the MPASS website.

1. Questionnaire for
Product Team: MPASS
Authors:
Vishal Juneja, Sandeep Supal
Date:
2- Jan-2012
Version:
1.0

2. Objectives
o
What are the top objectives/goals of MPASS website?
o
What are the critical success factors? How are these measured?
Users and Tasks
o
Who are the possible users for the app? (e.g., end-users, admin, business
executives)?
o
How do you see them using this website?
o
Intended user-experience, journeys
1. Master data
o Is this the data that a user needs to maintain and manage using the MPass
website?
o
We need a better understanding of the flow of the master data.
a) Company Master
o How is Company ID generated? What do you mean by the term autogenerated?
o
If the user is required to click on a button to generate company ID, then:
What all information a user is required to fill in to generate Company
ID?
Can a user create more than one Company IDs?
o
Need clarification on “Encryption key”.
Is the archived data accessible to the end user?
o
Need clarification on “Number of validation attempts permitted for a serialized
code”
Design Lab

3. o
Need further clarification on “Serialized validation response”.
b) Product Master
Is there a limit on how many Product IDs can be generated for a given
Company ID?
c) Package Master
Need more clarity on “The serialized validation response”.
Is this same as in Company master?
d) Lot level information
o Need further clarification on Lot number generation.
o
Point from the MPass – Product Spec document
 The following information is mandatory – company ID, lot number, Number
of unique codes generated everything else is optional.
 Need further clarification on this.
o
Need clarity on:
Random number
Number of unique codes
2. Integration with manufacturing process
o Scenario 1(Real time integration with manufacturing process with direct printing
of codes): The scope of website in this case is limited to management of master
database. ERP integration is not in the current scope. Is this correct?
o
Scenario 2 (Real time integration with manufacturing process without unique
code generation): In this case the scope is limited to uploading serialized codes
manually through an excel or a csv. Is this correct?
On the uploaded information what all tasks a user can perform?
Need clarity on Step 2.
o
Scenario 3:
Need detailed (step by step) description on how a particular company can
order scratch stickers using MPASS website.
o
ERP integration and Label printing software integration is out of scope for the
website phase. Is this correct?
Design Lab

4. 3. Generation of serialized codes
o Need clarification on the process of code generation.
4. Authentication of serialized codes
o What all information a user needs to put in for authenticating a code?
o
How many codes a user can authenticate at any given point of time?
5. Website
o We will need a set of use cases for the website.
Branding & Market position
o
What is the brand promise of the existing product? What is the unique about the
brand?
o
What are the desired values or personality of brand (e.g. industry leader,
trustworthy, secure, efficient etc)?
o
What keywords describe the MPASS brand? What is the branding strategy?
o
Are there any special needs to change brand perception? If yes, what would you
like to change?
Closing
o
What absolutely must be done well to be successful?
Design Lab