Socialig/Use Case TF/Profile Use Cases/Social Profile Deletion

Use Case Title

Social Profile Deletion

The use case

Kim wants to delete the single, comprehensive profile from her provider service.
Prior to deletion, Kim is provided an opportunity to download/archive a copy of her profile before it is deleted
Deleting the profile on the profile providers server severs the connections with other federated profiles.
The profile information is permanently wiped from the profile providers servers.

Narrative

Kim wants to delete the single, comprehensive profile that has been previously created and federated across multiple public social networking sites and private business systems. Kim is given the option by the profile provider to download a copy of the profile before it is deleted. Once the comprehensive profile is removed from the profile providers server(s), connections with other federated profiles are permanently broken.

Alternatively, Kim may decide to quit a public social network or may change employers. Upon taking that action, Kim's profile on that service or system is disconnected from all other federated profiles, including Kim's comprehensive profile, and the profile information housed in that service or system is permanently wiped from its server(s).

Actors

The principal actors in this use case include:

Profile owner: The individual about whom profile data is being deleted from a network or system
Profile provider: The entity that stores profile data on its server(s). This may be an organization or the profile owner, who may choose to self-host their profile.
Profile federators: Other public social networks or business systems that have been connected to the profile owner's other profile instances.

Goals of Actors

Profile owner: Seeks to permanently remove information about themselves from a profile provider or federator.
Profile provider: Wants to remove all profile data related to the profile owner from its server(s).
Profile federator: Wants to retain its own profile data related to the profile owner when it is removed from a profile provider's server(s).

Success Scenario

The profile owner is able to delete information about themselves on a public social network or business system without effecting other federated profiles. If the comprehensive profile is deleted, the connections to other networks and systems are terminated without loss of profile information they store.

Success Criteria

The profile owner's information is permanently removed from the profile provider, social network or business system that s/he is quitting.

Failure Criteria

Some or all of the profile data is not completely or permanently deleted from the profile provider.
Some or all of the profile data is removed from a federated profile.
Connections with federated profiles are not terminated.

Graphic Illustration(s) [optional]

Provide a graphical representation of the social use case (formalism is not required - any format or approach is acceptable, from hand drawn stick figures/systems to UML

Comments

Please use this space to comment on the above use case.