See this document in CiteSeerX!

Architecture-driven Problem Decomposition (2004)  (Make Corrections)  (1 citation)
Lucia Rapanotti, Jon G. Hall, Michael Jackson, Bashar Nuseibeh
Proceedings of the 12th IEEE International Requirements Engineering Conference (RE'04)



  Home/Search   Context   Related

 
View or download:
mcs.open.ac.uk/ban...re04.rapanotti.pdf
Cached:  PS.gz  PS  PDF   Image  Update  Help

From:  mcs.open.ac.uk/ban25/papers/ (more)
(Enter author homepages)

Rate this article: (best)
  Comment on this article  
(Enter summary)

Abstract: Jackson's Problem Frames provide a means of analysing and decomposing problems. They emphasise the world outside the computer helping the developer to focus on the problem domain instead of drifting into inventing solutions. The intention is to delay consideration of the solution space until a good understanding of the problem is gained. (Update)

Similar documents based on text:   More   All
0.5:   Composing Requirements Using Problem Frames - Robin Laney Leonor (2004)   (Correct)
0.4:   Relating Software Requirements and Architectures.. - Hall, Jackson.. (2002)   (Correct)
0.4:   Making Inconsistency Respectable in Software Development - Nuseibeh (2001)   (Correct)

BibTeX entry:   (Update)

Lucia Rapanotti, Jon G. Hall, Michael Jackson, and Bashar Nuseibeh. Architecture-driven problem decomposition. In Proceedings of the 2004. http://citeseer.ist.psu.edu/rapanotti04architecturedriven.html   More

@inproceedings{ rapanotti2004,
  author = {Lucia Rapanotti and Jon G. Hall and Michael A. Jackson and Nuseibeh, Bashar},
  title = {Architecture-driven Problem Decomposition},
  booktitle = {Proceedings of the 12th IEEE International Requirements Engineering Conference (RE'04)},
  year = {2004},
  address = {Kyoto, Japan},
  publisher = {IEEE},
  abstract = {Jackson”Ēs Problem Frames
	 provide a means of analysing and decomposing problems. They emphasise
	 the world outside of the computer helping the developer to focus on
	 the problem domain instead of drifting into inventing solutions.
	 The intention is to delay consideration of the solution space until
	 a good understanding of the problem is gained. In contrast, early
	 consideration of a solution architecture is common practice in software
	 development. Software is usually developed by including existing components
	 and/or reusing existing frameworks and architectures. This has the
	 advantage of shortening development time though reuse, and increasing the
	 robustness of a system through the application of tried and tested
	 solutions. In this paper, we show how these two views can be reconciled
	 and demonstrate how a choice of architecture can facilitate problem
	 analysis, decomposition and subsequent recomposition, within the
	 Problem Frames framework. In particular, we introduce Architectural
	 Frames - combinations of architectural styles and Problem Frames - and
	 illustrate their use by applying them to two problems from the literature.},
  url = {citeseer.ist.psu.edu/rapanotti04architecturedriven.html} }
Citations (may not include all citations):
579   Software Architecture: Perspectives on an emerging disciplin.. (context) - Shaw, Garlan - 1996
427   the criteria to be used in decomposing systems into modules (context) - Parnas - 1972
406   Design Patterns (context) - Gamma, Helm et al. - 1995
291   Software Architecture in Practice (context) - Bass, Clements et al. - 1998
159   Nonfunctional Requirements in Software Engineering (context) - Chung, Nixon et al. - 2000
119   Automated Consistency Checking of Requirements Specification.. - Heitmeyer, Jeffords et al. - 1996
56   Software Architecture (context) - Shaw, Garlan - 1996
55   Specifications: a Lexicon of Practice (context) - Jackson, Requirements - 1995
48   An investigation of the Therac25 accidents (context) - Leveson, Turner - 1993
46   Mastering the Requirements Process (context) - Robertson, Robertson - 1999
42   Goal-Oriented requirements Engineering: A Guided Tour - van Lamsweerde - 2001
40   Functional Documentation for Computer Systems (context) - Parnas, Madey - 1995
29   UML Components: A Simple Process for Specifying Component-Ba.. (context) - Cheesman, Daniels - 2000
28   Attribute-based architectural styles - Klein, Kazman - 1999
28   Attribute-based architectural styles - Klein, Kazman et al. - 1999

[Article contains additional citations not shown here]

Documents on the same site (http://mcs.open.ac.uk/ban25/papers/):   More
Composing Requirements Using Problem Frames - Robin Laney Leonor (2004)   (Correct)
Problem Frames: - Coordination   (Correct)
Introducing Abuse Frames for Analysing Security Requirements - Luncheng Lin Bashar   (Correct)

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