Some Thoughts on Restructuring MembershipApplication

PART ONE: Becoming a Member

At the moment there are three uses of a MembershipApplication:
1. When a user without membership wants to become a member
2. When a user with a membership wants to register with another company (i.e. a second "membership application")
3. When a users membership is renewed (precise business rules unknown(?), but some sort of review has been mentioned)
This leads to two questions:
1. Given that two of the three use cases are not about applying for membership shouldn't we change the name? In want of a better idea I would like to propose to just drop "Membership" and go with "Application".
2. Given that two of the three use cases don't involve the payment process at all, it seems strange to have a "waiting for payment" status on MembershipApplication. I propose we remove it. That would simplify the process for the admin (see next section).
This is how it the proposed changes affect the first scenario as described by Patrick:

Scenario: User becomes Member (first time or after losing membership)
1. User can pay membership fee if there is an accepted Application
2. When User pays membership fee: (advantage: no admin involvement at all) - User is automatically (done by app, not Admin) set to member status
3. Expiration date for new membership set

Coming soon.