Hi, there is a rather large scale undertaking at my work place. There are several applications under the project.
The Managers/Architects of the project want a "wrapper" to be coded to support users' traits and identifiers. Therefore, when a user's; say, name, SSN, etc. are needed, the information can be retrieved from this wrapper.
What are the tasks involved in writing such a wrapper? Are there code examples of writing such a wrapper?
The first task, as always, is "Design". This is where you ask questions like "Do all users have the same traits?" and "Are there groups of users whose members all have the same traits?" and "Can people create arbitrary traits?" and "Can a trait be applied to one user and no others?" and "What is going to be done with these traits?"
But you said you had architects. It would have been their responsibility to ask such questions and to produce a design which is considerably larger than your two-sentence description of the requirement. Have they done that yet? It's too early to be asking about programming if you don't have some kind of a design available.
Natalie Kopple wrote:What are the tasks involved in writing such a wrapper? Are there code examples of writing such a wrapper?
Well a standard wrapper is exactly that: a class that "wraps" another, viz:Normally, forwarders have identical signatures to the methods they call, but you only have to define whatever ones are required for the wrapper. In this case, that probably means methods that have something to do with 'traits'.
However, since presumably they're already available through the User class itself, I don't really see the point.
Maybe you could explain.
Joined: May 06, 2003
Some one on the team is currently writing the User Story/ Use Case/ Technical Story. Nevertheless, I already known that I am going to be the one code this wrapper class.