Project Normalization - 2nd Normal Form

In a prior post, I started to discuss project normalization - based on database normalization: http://itprojectguide.blogspot.com/2007/01/normalization.html
I think it's time to look at the second normal form, Second Normal Form described in WikiPedia is: Second normal form (2NF) is a normal form used in database normalization. A table that is in first normal form (1NF) must meet additional criteria if it is to qualify for second normal form. Specifically: a 1NF table is in 2NF if and only if none of its non-prime attributes are functionally dependent on a part (proper subset) of a candidate key. A non-prime attribute is one that does not belong to any candidate key.
What??? Basically it's stating that any tasks defined by the task group and name can not be repeated. So, Environment, Setup Production Server - can only appear once - makes sense. What if you have more then one production server??? then:

1. Environment - Setup Production Server/Database
2. Environment - Setup Production Server/Web Server 1
3. Environment - Setup Production Server/Web Server 2

So far Project Normal Form 1 and 2 have to do with how information is presented in a plan, makes sense, since if the information is not clearly and consistently presented in a plan then the plan itself will lead to confusion. The other part of the second normal form is that the other task attributes (resources, start/end date, etc.) do not impact and are not dependent on the identifying elements - which makes sense, since regardless of who or when of the task the group and task itself should not be affected. So, Environment - Setup Production Server/Database does not change if Joe is performing it as opposed to Sue.