Nuseibeh, B.: "Weaving the Software Development Process between Requirements and Architectures". First International Workshop From Software Requirements to Architectures (STRAW'01). May, 2001.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....with CoCons. In order to reveal conflicting requirements and to detect problems early on, they should be written down in models. Fixing them during implementation is much more expensive. The benefits of considering both requirements and architecture throughout the modelling level are discussed in [42]. During configuration, a CoCon aware configuration file checker can . at Deployment automatically protect requirements. For instance, deployment descriptors of Enterprise Java Bean Systems can be checked for compliance with CoCons. Likewise, the notion of contextual diagrams is introduced in ....

Bashar Nuseibeh. Weaving the software development process between requirements and architecture. In Proceedings of ICSE-2001.

....of the domains. The phenomena visible at the machine domain s interfaces drive much of the analysis process. The existence of certain phenomena can be predetermined by purchased products to be used in the system [1] or by considering architectural implications early in the requirements cycle [6, 7]. Hall et al. [2] argued for extending Problem Frames to take architectural considerations within the machine domain into account, thus incorporating domain knowledge into the analysis. This paper takes the argument one step further, arguing that there are architectural considerations that affect ....

B. Nuseibeh, "Weaving the Software Development Process Between Requirements and Architecture," in From Software Requirements to Architectures (STRAW '01). 23rd International Conference on Software Engineering, ICSE 2001. Toronto, Ontario, Canada, 12-19 May, 2001.

....context properties and CoCons. Currently a CCL aware method for requirements analysis is being developed at the Technical University (TU) of Berlin in cooperation with Eurocontrol, Paris. The benefits of considering both requirements and architecture throughout the design phase are discussed in [13]. The application of CLL during design is currently being evaluated in a case study being carried out in cooperation with the ISST Fraunhofer Institute, the TU Berlin and the insurance company Schwabisch Hall. In winter term 2001 02 a CCL plugin for the open source UML editor ArgoUML has been ....

Bashar Nuseibeh. Weaving the software development process between requirements and architecture. In Proceedings of ICSE-2001 International Workshop: From Software Requirements to Architectures (STRAW-01) Toronto, Canada, 2001.

....not How when giving the requirements specification for a CBS. Specifying only What allows the implementers the greatest freedom to choose an implementation, a How. However, several have noted that sometimes it is necessary to give some details of the How, usually what is now termed Architecture [36, 4, 30, 29]. One example described by Berry [4] is that of Knuth s exposure of the linebreaking algorithm for T E XinThe T E Xbook [26] which serves as both the requirements specification and the user s manual. Knuth described the algorithm in the specification and user s manual for two main reasons: 1. to ....

Nuseibeh, B.A., "Weaving the Software Development Process Between Requirements and Architecture," in Proceedings of the ICSE2001 Workshop: From Software Requirements to Architectures (STRAW-01), Toronto, ON, Canada (May 2001).

....describes how construction of each system progressed, with particular attention to how the principles of Twin Peaks were used. Section V revisits the research questions, and section VI presents conclusions. II. BACKGROUND AND GOALS A. Twin Peaks Although the description of the Twin Peaks model [5] [6] was published after the project began, the model so completely captured the project s spirit that there is significant advantage in using the model and its terminology to describe the project. The model proposes a partial development methodology wherein requirements and architecture (where ....

B. Nuseibeh, "Weaving the Software Development Process Between Requirements and Architecture," in From Software Requirements to Architectures (STRAW 'OO. 23rd International Conference on Software Engineering, ICSE 2001.

....describes how construction of each system progressed, with particular attention to how the principles of Twin Peaks were used. Section V revisits the research questions, and section VI presents conclusions. II. BACKGROUND AND GOALS A. Twin Peaks Although the description of the Twin Peaks model [5] [6] was published after the project began, the model so completely captured the project s spirit that there is significant advantage in using the model and its terminology to describe the project. The model proposes a partial development methodology wherein requirements and architecture (where ....

B. Nuseibeh, "Weaving the Software Development Process Between Requirements and Architecture," in From Software Requirements to Architectures (STRAW '0. 23rd International Conference on Software Engineering, ICSE 2001.

No context found.

Nuseibeh, B.: "Weaving the Software Development Process between Requirements and Architectures". First International Workshop From Software Requirements to Architectures (STRAW'01). May, 2001.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC