• Things To Consider

    1. Server Side

      1. Slow query log

      2. Telephony logs

      3. Webserver logs

      4. Firebug

    2. Browsers

      1. IE

        1. 6

        2. 7

        3. 8

        4. 9

      2. Firefox

      3. Chrome

      4. Safari

        1. Mac

        2. PC

    3. Diagnostics

      1. Tracing

        1. Audit

        2. Billing

      2. Are there reports from the system?

        1. Are they accurate?

          1. Required

          2. Simple to understand

          3. Relevant

      3. Is the diagnostics system even testable?

      4. Is it intrusive to the operating of the system?

      5. Permissions and access to it

    4. Performance

      1. Speed and general performance

      2. Are there known weaknesses?

        1. Avoid them or take advantage?

      3. What if everything else around it is slow?

        1. Is it impacted?

          1. Does it cause issues?

        2. Interface issues around speedy messages

      4. What if everything else around it is fast

        1. Is it impacted?

          1. Does it cause issues?

        2. Interface issues around speedy messages

      5. Load / Performance Testing

        1. Spike

        2. Stress

        3. Reliable

        4. Load

        5. Scenario based

        6. Benchmark

        7. Peak Testing

          1. What is the max?

          2. When does it happen?

    5. Multi-user

      1. One user

      2. Two Users

        1. Concurrent

        2. Same browsers

        3. Different browser

      3. Many Users

    6. Security

      1. OWASP Top Ten

      2. Security Testing

        1. BurpSuite

        2. SQL Inject Me

        3. Other tools

    7. Upgrade

      1. Is an upgrade process?

      2. Is the system backward compatible?

        1. Database

        2. Web Servers

      3. Is there a roll back?

    8. Look and Feel

      1. Consistency

      2. Expectations?

      3. Image conveyed

        1. Is it accurate?

        2. Is it what we want?

      4. Refinement

        1. Is it slick

        2. UX High

          1. HUGE area

        3. Clean, simple and fast

        4. Easy to read / understand / use

    9. Comparison

      1. How does it compare to previous versions?

      2. How does it compare to the competition?

        1. Does it matter?

      3. How does it compare with Oracles (specs, designs, whiteboard sessions)?

      4. How does it compare with your expectations?

        1. What about others in the business?

          1. Ask them

    10. Safety and Security

      1. Is it secure?

        1. From whom? (Threat Profiling)

      2. Is it safe (data integrity, data protection)

        1. Type of data stored?

      3. Is it trustworthy?

        1. Is the company trustworthy?

          1. How can we prove it?

      4. Is it easily clonable?

        1. Is that a good thing?

      5. Encryption and other security methods

    11. Practicality

      1. Is it usable?

      2. Does it do what we say it does?

        1. Claims testing

        2. Expectations

      3. Is it accessible?

        1. W3C?

        2. Elmer guidelines

        3. Does it need to meet any standards?

        4. Via what devices?

      4. Is it practical with small data?

        1. What about now with big data?

      5. Is it portable?

        1. Does it need to be?

        2. Is it accessbile on other devices?

      6. Is it localised?

        1. Centralised?

          1. Glocalised

    12. Documentation and Help

      1. Help?

        1. Is there any?

          1. If not, why not?

        2. Easy to understand

          1. Useful?

          2. Relevant?

        3. Support mechanisms

          1. Who, where, why, when?

      2. Documentation

        1. Living or Dead or Partially Alive

        2. Who owns it?

        3. What medium and why?

    13. Ownership

      1. How can we do updates / patches / upgrades?

      2. Are there any current customer complaints?

      3. Is there a mechanism for reporting issues from the field?

        1. Decent error codes?

        2. Good public showing messages for reporting?

      4. What is the error tracking like?

      5. Is it a self healing system?

        1. In what circumstances?

        2. Can you find a scenario where it wouldn't be appropriate?

      6. How often is there a new version?

        1. How is this managed?

        2. How is this communicated?

      7. Are there multiple versions?

        1. How is this managed?

          1. Is this managed?

      8. What underlying tech does it rely on?

        1. How are you going to upgrade that tech?

        2. Is that tech still relevant?

        3. What are the known limitations with this tech?

      9. Is it future proof?

        1. Is this even possible?

          1. Yes, with some care and consideration for growth

      10. What happens to the system during any downtime?

      11. Cancellations / Closing

        1. What happens when someone closes an account?

          1. Is the process easy?

            1. Does it have dire consequences in the database?

        2. How do you manage legacy data?

        3. Can you provide assurances the data has been removed?

          1. Who owns the data?

          2. Can it be removed?

    14. Compliance and Claims

      1. Claims

        1. Marketing / Product Claims

        2. Minimum spec

        3. Capabilities

      2. Compliance

        1. Standards

        2. Law

    15. Supporting Business Processes

      1. What is the release mechanism?

        1. Is it suitable?

        2. Is it testable?

        3. Is it relevant

      2. What is the Sales Model?

        1. Is this in line with the development model?

        2. What are the constraints?

        3. What is being sold?

  • All Comments ( 1 )
    Biggerplate said at 2012-01-30 17:07:38
    These are really interesting maps Rob. It would be great to see them added to the mind map library at http://www.Biggerplate.com for our users to see too!

    Things To Consider

    Added: 2011-11-28 20:45:06

    From: rob_lambert (Joined 2011-11-23 11:27:09)

    57 views |0 downloads

    Things To Consider

    More From: rob_lambert

    Things To Consider
    Things To Consider
    2011-11-28 20:45:06|57 views
    ATD > MEETUP
    ATD > MEETUP
    2011-11-27 14:14:21|6 views
    10 Disruptive Techs
    10 Disruptive Techs
    2011-11-24 11:40:22|63 views
    Create Customer Value with Agile Testing
    Create Customer Value with Agile Testing
    2011-11-24 09:34:15|18 views
    Crowdsourcing - power to the people
    Crowdsourcing - power to the people
    2011-11-23 17:37:58|24 views
    Motivation
    Motivation
    2011-11-23 14:39:22|21 views
    Life's too short
    Life's too short
    2011-11-23 11:29:54|129 views