SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 5 of 5
  1. #1
    SQA Knight
    Join Date
    Aug 2000
    Location
    Elanora Heights, NSW, Australia
    Posts
    3,271
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Model Office Experiences

    KBEE01

    This is basically what you do when you implement RUP. What you seem to be doing (correct me if I am wrong) is doing a generic (call centre) model. In RUP you do a specific model.

    My only advice is that OO and RUP (despite the marketing hype) is not the complete solution and will not save time and/or money. With such methodologies its easy to fall into the trap of operating in helicopter mode (hovering), instead of actually doing the "hard yards" and properly defining the user requirements. In other words, don't miss the basics.
    Robert Tehve
    rtehve@bigpond.com

  2. #2
    Senior Member
    Join Date
    Oct 2002
    Location
    New Zealand
    Posts
    749
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Model Office Experiences

    We produce specialist software aimed at an Office based type of client.
    As part of our existing testing, we have defined user roles and have a phase of Role Based testing. However, in the main this consists of individual testers running their role tests in relative isolation (i.e. not specifically coordinated with the other roles).
    In the past, e.g. with call centre software, I have had experience of running a Model Office for this type of testing.
    I now want to look at such an approach here and am gathering information in advance of our discussions.
    I would love feedback from anyone that has experience of this approach - the pro's, con's, gotchas etc.

  3. #3
    Senior Member
    Join Date
    Oct 2002
    Location
    New Zealand
    Posts
    749
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Model Office Experiences

    Hi Robert,
    ah how I hate terminology. I have not communicated well!
    Our deveopment model is a mix of Feature Driven, Unified Process (not pure Rational), modified V-Model and Test Driven development.
    Along side that, we do formal Feature Testing (Function Testing) and System Testing.
    For User Acceptance Testing, we have definied typical business user roles - not of the Use Case type - more of the life in the day of user X, Y, Z etc in the office/business. Within each role, we have a suite of tests that excercise the system.
    The Model Office I am thinking off is literally that, a typical client office, with staff. We run it as a business out to make a "paper" profit.
    It can operate 7 days a week, 52 weeks a year, mainly as a background task, but going full time for the UAT phase.
    Some of the benefits I would hope to see are:
    1. Real life data that naturally ages (over each release as well as during the release).
    2. A natural flow through the application, not isolated pockets of coverage
    3. Not restricted to the Test team. Everyone can play a role, including designers and developers and support staff.
    4. It will bring us all closer to the user experience. Instead of guaging what users may feel about the way things work, we will have to live with our decissions. And with the frustrations. We will therefore start to address usability.
    5. It will test roll out. We will have to apply each new release over an existing (and working) release.
    6. I believe that we will gain more coverage in less time than the old role-based approach achieves.
    7. It does not have to be restricted to a specific time/phase in the project life cycle, it is something we can keep running all year.
    8. It will be FUN.
    On the con side
    1. COST! (though this may be a Chinese Wall cost).

  4. #4
    Member
    Join Date
    Sep 2003
    Location
    New Zealand
    Posts
    61
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Model Office Experiences

    KBBE01,

    Rather than implementing a model office with all the associated issues of cost, lack of resource etc. Why don't you take a snapshop of a client database and use that as your working model. After all this is a true representation of an actual client rather than a conceptual one.

    The only drawback would be if the client data is sensitive - confidentiality issues may arise. On the plus side, you can use this client database for performance testing.

  5. #5
    Senior Member
    Join Date
    Oct 2002
    Location
    New Zealand
    Posts
    749
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Model Office Experiences

    Originally posted by Titus:
    KBBE01,
    Rather than implementing a model office with all the associated issues of cost, lack of resource etc. Why don't you take a snapshop of a client database ........The only drawback would be if the client data is sensitive - confidentiality issues may arise.
    <font size="2" face="Verdana, Arial, Helvetica">Confidentiality of data is definitely one issue, and especially so with us.
    That said, using client data is always a good way of getting a mix of "clean" and "dirty" data and can be facilitated by partial encryption, however my focus is on what we do with the data.
    Comprehensive "Live" data is especially good for giving you a full range of "business entity life states", especially if good trawling methods are available.
    Something I am very keen on in our other test phases.
    However, I repeat that my current focus is on what we do with any data during UAT.
    (Sorry for all the quotes around phrases, just indicating terms that may need defining! [img]images/icons/smile.gif[/img] )

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.40 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 11.54%
vBulletin Optimisation provided by vB Optimise v2.7.1 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.3.0 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 04:21 PM.

Copyright BetaSoft Inc.