I like this part
created to maintain address book entries for both businesses and people
and then there isn't any significant differences in the rest of the description to warrant such a distinction. That alone makes the data structures on one side of the brain fight against the data structures from the other side of the brain. Frustration over non-sense.
Each business must have exactly one primary address and, optionally, one or more secondary addresses.
Reading this reminded me of English class where the teacher stressed the avoidance of double negatives. This isn't a double negative but it sure could have been written in a clearer manner.
A person has exactly one primary address only.
This just drives me batty. What about folks who don't currently have a primary address. What about persons who had a primary address initially but do not any more? Why can't a person have a secondary address? What about my farmhouse is Switzerland? My vacation home in Rome? The yacht docked at the South American pier? This is a bad rule. More frustration over non-sense.
A business may have zero or more associated people.
Again more frustration. Why can't a business be associated with another business. Why the hard coded structure?
A person may be associated with no more than (i'm guessing the number "1" was here and was lost in the paste) business.
Now person is starting to sound more like an employee. But gone are the days of an employee ONLY working for one company at a time. More frustration over non-sense.
I spent about 1 hour so far deciphering the assigned task, creating the database structure, roughing out the website GUI, and roughing out the WPF maintentance GUI. The frustration of the business rules told me it was time to stop and take a vacation.
something representative of four to eight hours worth of work
Who said those hours had to be contiguous.
More feedback later.