By Topic

IEE Proceedings - Software

Issue 4 • Date 5 Aug. 2005

Filter Results

Displaying Results 1 - 6 of 6
  • Relating software requirements and architectures

    Publication Year: 2005, Page(s):141 - 142
    Cited by:  Papers (1)  |  Patents (1)
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (107 KB)

    Requirements engineering and software architecture have become established areas of software engineering research, education, and practice. Requirements engineering is concerned with discovering the purpose of a software system and the contexts in which it will be used (Nuseibeh and Easterbrook, 2000). Software architecture is concerned with the study of the structure of software, including its to... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Deriving architectural flexibility requirements in safety-critical systems

    Publication Year: 2005, Page(s):143 - 152
    Cited by:  Papers (1)
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (213 KB)

    Safety-critical embedded systems are constrained by safety regulations that require the designers of the system to explain its operation. This includes the operation of any flexibility mechanisms present in the design, and the rationale for their inclusion. The ability to place such flexibility where it is most needed is a crucial factor in reducing the cost and risk of safety-critical system deve... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Designing software architectures to achieve quality attribute requirements

    Publication Year: 2005, Page(s):153 - 165
    Cited by:  Papers (10)
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (718 KB)

    In order to have a software architecture design method that achieves quality attribute requirements several aspects of the method must be in place. First there must be some way to specify quality attribute requirements so that it can be determined whether the designed architecture can achieve them. Secondly, there must be some way for modularising the knowledge associated with quality attributes s... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using real options to select stable middleware-induced software architectures

    Publication Year: 2005, Page(s):167 - 186
    Cited by:  Papers (7)
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (446 KB)

    The requirements that force decisions towards building distributed system architectures are usually of a non-functional nature. Scalability, openness, heterogeneity, and fault-tolerance are examples of such non-functional requirements. The current trend is to build distributed systems with middleware, which provide the application developer with primitives for managing the complexity of distributi... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Global Analysis: moving from software requirements specification to structural views of the software architecture

    Publication Year: 2005, Page(s):187 - 197
    Cited by:  Papers (7)
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (294 KB)

    Software architecture design approaches typically treat architecture as an abstraction of the implemented system. However, doing so means that the concepts, languages, notations, and tools for architecture are much more closely related to those of detailed design and implementation than to those of software requirements. Thus the gap between requirements and architecture represents a paradigm shif... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Architectural patterns for problem frames

    Publication Year: 2005, Page(s):198 - 208
    Cited by:  Papers (4)  |  Patents (25)
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (164 KB)

    Problem frames provide a characterisation and classification of software development problems. Fitting a problem to an appropriate problem frame should not only help to understand it, but also to solve the problem (the idea being that, once the adequate problem frame is identified, then the associated development method should be available). The authors propose software architectural patterns corr... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.