%0 Conference Paper %1 finkelstein90 %A Finkelstein, A. %A Kramer, J. %A Goedicke, M. %B International Workshop on Software Engineering and Its Applications %D 1990 %K viewpoints requirements %T ViewPoint Oriented Software Development %U http://citeseer.ist.psu.edu/finkelstein90viewpoint.html %X In this paper we propose a new approach to software development which explicitly avoids the use of a single representation scheme or common schema. Instead, multiple ViewPoints are utilised to partition the domain information, the development method and the formal representations used to express software specifications. System specifications and methods are then described as configurations of related ViewPoints. This partitioning of knowledge facilitates distributed development, the use of...

@inproceedings{finkelstein90, abstract = {In this paper we propose a new approach to software development which explicitly avoids the use of a single representation scheme or common schema. Instead, multiple ViewPoints are utilised to partition the domain information, the development method and the formal representations used to express software specifications. System specifications and methods are then described as configurations of related ViewPoints. This partitioning of knowledge facilitates distributed development, the use of...}, added-at = {2006-03-24T16:34:33.000+0100}, author = {Finkelstein, A. and Kramer, J. and Goedicke, M.}, biburl = {https://www.bibsonomy.org/bibtex/26f95eca17b4e7c9acaa11d97217cb36e/neilernst}, booktitle = {International Workshop on Software Engineering and Its Applications}, citeulike-article-id = {248001}, comment = {- A language for modeling fragments of knowledge expressed in various syntaxes (UML, i* etc), rather than forcing everyone to use one specific expressive language - "..if a representation scheme is made more expressive the task of elicitation and specification should, in theory, become easier." - why not: learning overhead; difficulty in creating a scheme that is sound; different than those used in practice; richness -> unreadable and baroque; practical validation is difficult - "a viewpoint is a loosely coupled, locally managed object which encapsulates partial knowledge about the application domain, specified in a particular, suitable formal representation, and partial knowledge of the process of software development" - partial ordering of elements in s/w eng is essentially specifying pre/post conditions, which allow for multiple traversals through the graph of nodes. - can we map a viewpoint to an AH template?}, description = {sdasda}, interhash = {fd15135c2f26cb7255c41b550c6f1bfa}, intrahash = {6f95eca17b4e7c9acaa11d97217cb36e}, keywords = {viewpoints requirements}, month = {December}, priority = {0}, timestamp = {2006-03-24T16:34:33.000+0100}, title = {ViewPoint Oriented Software Development}, url = {http://citeseer.ist.psu.edu/finkelstein90viewpoint.html}, year = 1990 }