8. What are best practices for protecting eCommerce user data?
The first step in protection would be to not collect sensitive customer information if possible. If a third-party, off-site payment gateway can be used, it removes a lot of complexity for the merchant.
The next step in protection occurs during transmission. When transferring sensitive customer information,
Next, if we need to use a gateway such as Authorize.Net that’s built into Magento, we should never store any of the credit card info – no credit card numbers, ccv’s or expiration dates. We can keep the hash that the service sends back to us though.
Lastly, we need to make sure we’re following PCI requirements and only making collected customer is secured and protected both on the server and procedural ends.
9. What are the best usability practices when building an online catalog and checkout system?
We want to set up categories and products that are easy to navigate and give the customers the information they want in a well-organized and easy to navigate format. With the rise in mobile traffic it’s especially important to tailor an experience to these users.
During the checkout process, we want to eliminate as many barriers to purchase as possible. We should allow customers to checkout without creating accounts and entering as minimal information as possible. It’s tempting to get as much demographic information about your customers as you can, but each additional field that they need to fill our or additional checkout step greatly reduces the chance of a conversion.
10. What are the main characteristics of Agile and Waterfall development methodologies?
When building a software product, the Waterfall method is traditionally thought of. In this process, the software development lifecycle moves from one phase into the next, flowing like a waterfall. The requirements phase will dictate the design phase, which is completed before the build phase, then the QA phase and next to release/maintenance.
The major downfall with this method is that the process is meant to be a one-way street – once design is done, and development is in progress, it’s too late to discover and react to missed or changed requirements.
Agile can be thought about as a series of mini-waterfalls. Agile excels in breaking down a project into smaller iterations – typically over a two week period. More general, less well-defined goals are in place at the beginning of the project. As iterations are completed, the project becomes better defined and may veer into a different direction as more requirements and opportunities are discovered during the process.
11. What are SMART requirements?
Wikipedia gives us a definition for SMART.
SMART is an acronym for
- Specific – target a specific area for improvement.
- Measurable – quantify or at least suggest an indicator of progress.
- Assignable – specify who will do it.
- Realistic – state what results can realistically be achieved, given available resources.
- Time-related – specify when the result(s) can be achieved.