User Characteristics - Edge-Locksmith-Services/Locksmith-website GitHub Wiki

Stakeholders

• President- Final Approval
• Accounting- Supply Money
• Service Providers- Able to keep track of appointments that are scheduled.
• Customers- Would benefit from the website showing information about the company and be able to schedule appointments.
• Your team- Working on the software development.
• Prospective Customers- Able to review information about the company if they want to schedule an appointment for services.

User Characteristics

The primary users are customers who have little to no knowledge of the industry, have varying levels of technical capabilities, and can sometimes be under important time constraints.

Website operators are another group of users. They have significant knowledge of the industry, but likely also have varying levels of technical capabilities.

Neither of these groups are not particularly predisposed to disabilities that would require accommodation, but plans should still be made to accommodate any users that may have disabilities.

Elicitation Plan

Interviews of multiple stakeholders.

• What problem are you trying to solve?
• What’s the motivation for solving this problem?
• What would a highly successful solution do for you?
• What’s a successful solution worth?
• Who could influence this project?
• Who could be influenced by this project?
• Are there any related projects to this one?
• Which activities should be included in the scope?
• Could there be any unintended consequences of the new system?
• What policies must the product conform to?
• What goals could this product help you accomplish?
• What problems do you expect this product to solve?
• What words would you use to describe the product?
• What aspect of the product excites you?
• What aspects are most/least valuable to the users?
• What qualities (e.g., efficiency, security, reliability, etc.) are critical for the specific parts of the product?
• What events must the product respond to?
• Can you describe the environment in which the product will be used?
• Would anyone ever want to ...?
• Could ... ever occur?
• What should happen if …?
• What is most important to you about the product?
• How would you judge whether the product is a success?
• How should the product be different from the way things are done now?
• Is there anything else we should be asking you?

Prototypes.

• Create a mockup showcasing more details and a possible version of the website.
• Create a dynamic prototype showing a clickable version of the website.

Use Case

• User stories will be gathered from interviews with stakeholders as well as with questionnaires to elicit information that is needed for the software.