It seems like the more views we create, the more jobs we create. Perhaps we should be grouping views into skill sets, interests, or organizational roles. What kinds of capabilities are required for each view and which type of people does the organization want manipulating the capabilities? That is, does our design of views determine organizational structure, or vica versa? Should the use cases be different for each organization? Is the acceptance of the software dependent on organizational use cases? What will make an organization succeed using FoNC?
John _______________________________________________ fonc mailing list fonc@vpri.org http://vpri.org/mailman/listinfo/fonc
