What follows is the client registration use case for the ABIEE™ (Alliance of Bankruptcy Information and Expert Exchange). If you were following the previous related post, you will see that the client registration use case specifically builds upon the global client use case. Before the client can access any major features of the application, he/she must register an account. Although it is possible to allow anonymous browsing and functionality, up front registration makes the most sense.
The Registration Process Overview
Basically, a client will complete a brief and painless registration form. When they click submit, pertinent data will be entered into a database table. Next, the client and the site administrator will receive notification of the event.
Developer's Perspective
The programming portion of the registration use case is fairly straight forward. Once the client enters information on the form and clicks submit, logic will be written to add that information to a database table. Additional code will be written to confirm the registration with the client. Finally, code will be written to notify the site administrator that a new user has in fact registered an account.
Designer's Perspective
The eventual graphic design of this input form will reflect the overall look and feel of the application (the graphic design will come much later in the process). The focus should be on modern design techniques with an emphasis on usability.
Marketing Perspective
At this point, it is important to realize that the client has an open mind and may be interested in additional services/offers. One thing that I will add here is an opportunity to opt-in to marketing communications such as newsletters and special offers. One more marketing feature that I will add here is an opt-in for a printed information packet of some kind.
Conclusion
Once the client is registered we will have non personally-identifying identity parameters to use for future programming, design, and marketing implementations.
Client_Reg_UseCase.pdf (143.40 kb)