Introduction

This is a simple solution that you can use as the starting point for implementing stakeholder management requirements using Microsoft Visual Studio LightSwitch.

In this particular code sample solution, you'll learn how to;

Building the Sample

You need Microsoft Visual Studio LightSwitch (Beta 2).

Download and extract the .zip file. Open the .sln file in Visual Studio 2010 and build the solution.

Description

Be it a customer, supplier, user, employee, or whatever, every solution I have worked on has requirements for managing business entities that can be abastracted into a high-level type of stakeholder. Yes, each type of stakeholder entity may have different roles and responsibilities however at its root, a stakeholder is a stakeholder.

First off, and for sake of clarity, a definition…

Stakeholder: a person, group, organization, or system who affects or can be affected by an organization`s actions. (Thank you Wikipedia!) 

Be it a customer, supplier, user, employee, or whatever, every solution I have worked on has requirements for managing business entities that can be abastracted into a high-level type of stakeholder. Yes, each type of stakeholder entity may have different roles and responsibilities however at its root, a stakeholder is a stakeholder.

So, back to what I have learned over the years. Stakeholder management is arguably the most critical piece of the line of business solution pie. Everything that happens in a solution resolves around how a stakeholder is managed. This includes how the processes, both system and business, mitigate stakeholder information. Stakeholder inputs and outputs are key to almost every process.

Here is how I have engineered stakeholder information management, in the context of a solution.

Most stakeholder business types can be generalized into a Stakeholder entity. For example, let`s say we have a requirement to mitigate customer, supplier, and manufacturer information for an application that will be used for a service based company. A customer, supplier, and manufacturer can each be considered a type of stakeholder.

Here is an example generlization of each of the customer, supplier, and manufacturer stakeholder…

 

Just to make things interesting, let's throw in a couple more entities that will better show how this stakeholder abstraction works. Address information is a great entity to use because what system does not require some information about a stakeholder’s address. I am also going to throw contacts into the mixer too. Oh, how about if a contact has addresses of their own too.

The objective of this sample is have you learn a little bit more about LightSwitch. The outcome of which will then provide you a framework to managing stakeholders. Using the sample project, you should be able to extend this solution and craft your own specialized tool for managing the various types of stakeholders that you need to keep track of.

More Information

For more information, check out the blog article http://www.paulspatterson.com/technology/lightswitch/microsoft-lightswitch-simple-stakeholder-management/.