Name
Abstract | ||
|---|---|---|
Architecture based refinement is an importanttechnique for ensuring efficiency, effectiveness andcorrectness in the practical design of complex computerbased systems. With a few exceptions, current methods ofarchitectural refinement focus on functional behaviourand fail to address non-functional requirementsthroughout the refinement process. A best practicesapproach to refinement would address both functionaland non-functional requirements such that the refinementof an abstract into a concrete (implementation)architecture ensures that both sets of requirements aremet.We propose a method that focuses on the non-functionalrequirements while still addressing thefunctional requirements throughout refinement. Themethod has a formal underpinning in abstract data types(based on term rewriting) which are used to represent thearchitectures throughout the refinement process and toplace pre and post conditions on the refinements. Inaddition to this, the method uses non-functionalrequirement calculators to check the non-functionalqualities of the architecture as refinement proceeds.Reflection on the practice of the method suggests that itmay be possible to extend the architectural style idea toprovide reusable refinement schema for the design ofcertain non-functional qualities into architecturalpatterns. The example considers reliability andperformance in the refinement of a client serverarchitectural pattern.The method does not aim to replace or fully automatethe work of the designer. It aims to augment the designprocess and aid the designer in performing their tasks. Itseeks to provide certain guidance for the designer thatwill help them make the right design decisions, andcorrect certain classes of errors. |
Year | DOI | Venue |
|---|---|---|
2004 | 10.1109/ECBS.2004.1316696 | ECBS |
Keywords | Field | DocType |
requirements aremet,refinement focus,non-functional refinement,practical design,functionaland non-functional requirement,refinement process,systems architecture,design ofcertain non-functional quality,refinement proceed,current method,non-functional requirementsthroughout,reusable refinement schema,client server architecture,best practices,best practice,switches,computer architecture,abstract data types,abstract data type,open systems,functional requirement,architectural pattern,history,formal specification,reflection,system architecture,formal verification,communications technology,transducers,file servers,design process | Functional requirement,Programming language,Software engineering,Computer science,Correctness,Formal specification,Real-time computing,Systems architecture,Architectural pattern,Architectural style,Non-functional requirement,Formal verification | Conference |
ISBN | Citations | PageRank |
0-7695-2125-8 | 7 | 0.69 |
References | Authors | |
13 | 3 | |
Name | Order | Citations | PageRank |
|---|---|---|---|
| mark denford | 1 | 41 | 4.17 |
| John Leaney | 2 | 186 | 25.20 |
| Tim O'Neill | 3 | 74 | 11.50 |