Encapsulation

Encapsulation? for Project Management? Encapsulation is defined (at least in regards to Object Oriented programming) as Conceals the exact details of how a particular class works from objects that use its code or send messages to it.
So what does this have to do with PM? How often is a task defined that either is not complete OR does not sufficiently hide minute details to reduce confusion/complexity. For instance: Task 121: Install Web Server in Production - you would assume (ASS-U-ME) that this is the complete installation of a server, unless otherwise defined. But in many cases it refers to the simple connecting of a server to a network, i.e. network and power cable - and not the configuration, testing, etc. that is also required for a complete installation of a server. To the other extreme the installation task could have 20-30 sub tasks painfully explaining every detail. (take server out of box, without dropping place on shelf, look lovingly at server for 5 minutes, etc.). To reduce planning complexity, ensure complete/whole-product delivery, etc. I THINK the simple definition of encapsulation in the PM documents would help set expectations as what a task is, etc. and put in place the understanding of the level of detail required to track. Report at the detail level required based on risk factors, Encapsulation as much as possible to ensure reduced complexity which enhances clear communication.