Design and Architecture

sseth21k wrote:

I have a solution to the problem. But I would like to know other approaches to solve the issue.

class AccountInterface
{
public :
	virtual void CheckAccount() = 0;
};


class Accountant 
{
private:
	AccountInterface * accountDept;
public:
	Accountant():accountDept(NULL){}
	void SetCompanyAccDept(AccountInterface *accDept){accountDept = accDept;}

	void AuditCompany()
	{
		if (accountDept)
			accountDept->CheckAccount();
		else
			printf("Compnay info not set");
	}
};

class company : private AccountInterface
{
private:
	virtual void CheckAccount()
	{
		printf("Only Granted Accountant should have access to this");
	}
public:
	void SetAccuntant(Accountant *accountant)
	{
		//Based on some logic grant access
		accountant->SetCompanyAccDept(this);
	}
};

int main (int argc, char *argv[])
{
	company c1;
	Accountant ac1;
	c1.SetAccuntant(&ac1);
	ac1.AuditCompany();
	
}

SSETH wrote:

Could you please post here your approach(Design) in C++..

sseth21k wrote:

1. The third person should not be able to see the other details of the class!

sseth21k wrote:

the component should be accessible to only that particular third person!

darkliahos wrote:

I would love a few opinions and experiences on people who have battled with this issue.

Gerry Schmitz wrote:

What happens if a user is not logged on? Do they get "synced" when they log on?

Gerry Schmitz wrote:

How "current" does the syncing have to be? Why?

Gerry Schmitz wrote:

Design choices are premature at this point; IMO

Gerry Schmitz wrote:

How can a client be "real-time" when it is off-line (and in effect acting like a "device")?

Gerry Schmitz wrote:

I see nothing in your descriptions that requires a "real-time" solution.