CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 5 of 5

Thread: Simple Question

  1. #1
    Join Date
    Jul 2001
    Location
    Pune-India
    Posts
    251

    Simple Question

    Hi Gurus
    I want to know the details of White box reuse and Black box reuse ?....Whts they makes difference in design?

    Regards
    Nagesh

  2. #2
    Join Date
    Sep 2002
    Posts
    1,747

    short answer and link

    Black box reuse ise the distribution of compiled components for implementation into a larger development construction, whereas white box reuse indicate the actual distribution of source code to include into a software project. This article explains in more detail the relative benefits.
    */*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/

    "It's hard to believe in something you don't understand." -- the sidhi X-files episode

    galathaea: prankster, fablist, magician, liar

  3. #3
    Join Date
    Jul 2001
    Location
    Pune-India
    Posts
    251

    Thanx

    Thank you Galathea...
    Actualy I was reading the MSDN, for OOP concept. While reading I Interface based programming , I came through these words...at that time I could not get the clear idea about the meaning of these two.....
    The linked article is more informative to understand the concept...
    Thank you
    Regards
    Nagesh

  4. #4
    Join Date
    Mar 2002
    Location
    St. Petersburg, Florida, USA
    Posts
    12,125
    Slightly longer answer.

    "Black Box".. You have knowledge of WHAT is does, but not HOW it does it. A pure interface class is a decent example.

    "White Box".. You have FULL knowledge about everything. Galathaea example of source code is a good one.

    These terms are used in both reuse and testing methodologies.

    There are also many "Gray Box" issues...You have partial knowledge of "how". This can be as simple as a DLL Vendor stating that "Object X uses a CMap to hold its data". You now have some knowledge of how and can tune your usage to optimize on this. There is a risk as the vendor may later make an internal change (i.e. no public methods change).

    In the testing area, this idealy resolves to:

    "Black Box Testing"..Test every method under all possible conditions.

    "White Box Testing"..Make sure every code path is executed, all variables are tested for over/under flow, etc.

    Hope this helps..
    TheCPUWizard is a registered trademark, all rights reserved. (If this post was helpful, please RATE it!)
    2008, 2009,2010
    In theory, there is no difference between theory and practice; in practice there is.

    * Join the fight, refuse to respond to posts that contain code outside of [code] ... [/code] tags. See here for instructions
    * How NOT to post a question here
    * Of course you read this carefully before you posted
    * Need homework help? Read this first

  5. #5
    Join Date
    Jul 2001
    Location
    Pune-India
    Posts
    251

    Thanx CPU Wizard

    Hi CPUWizard
    Thank you, Actully the small informative para. helped me to clear all those confusions.....you kept the idea in simple words...its more helpful. Even Galthea's example is good...
    Thanx you Guru...
    Reagrds
    Nagesh

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  





Click Here to Expand Forum to Full Width

Featured