Take the 2-minute tour ×  What advice/suggestions/guidance would
you provide for designing a class that has upwards of 100
properties?     • The class describes an invoice. An invoice can
have upwards of 100 attributes describing it, i.e. date, amount,
code, etc...   • The system we are submitting the invoice to
uses each of the 100 attributes and is submitted as a single
entity (as opposed to various parts being submitted at different
times).   • The attributes describing the invoice are required
as part of the business process. The business process can not be
changed.     • What have others done when faced with designing a
class that has 100 attributes? i.e., create the class with each
of the 100 properties?   • Somehow break it up (if so, how)?   •
Or is this a fairly normal occurrence in your experience?  EDIT
After reading through some great responses and thinking about
this further, I don't think there really is any single answer
for this question. However, since we ended up modeling our
design along th