Towards a process for architectural modelling in agile software development

Durdik, Zoya

doi:10.1145/2000259.2000291

Cited by 10 publications

(15 citation statements)

References 41 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A more completed knowledge about software architecture please refers to [11]. Here we do not discuss software architecture more than is needed, but literature [8] is worth having an attention because it shows a primitive solution for building software architecture in agile scope. Though the idea of his is coarse-grained and does not focus on the coalition of software architecture and agile, it still sheds the light on this aspect.…”

Section: Related Workmentioning

confidence: 99%

“…Our proposal embodies the strength of rapidly building software frame and the ability of faster implementation. A comparison to [8] is illustrated in Table 2, and the explanation for the comparison is summarized below. Fig 6. Design the IGame to meet new requirements 1.…”

Section: Analysis and Comparison To Previous Workmentioning

confidence: 99%

“…Fig 6. Design the IGame to meet new requirements 1. We don't believe that selecting pattern prior to component definition in [8] is rational for building architecture. In fact, pattern can't live without interface, because we can't evaluate the pattern whether it is appropriate when there are no interface declarations for comment.…”

Section: Analysis and Comparison To Previous Workmentioning

confidence: 99%

“…Zoya Durdik [8] has made a primitive discussion at this aspect and proposed a process to address the agile's limitation by introducing SA modeling. Their proposal mainly concerns about rapidly building SA in an iterative manner.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Supporting the combination of agile manner and architecture based development method

Yao¹

2016

Proceedings of the 2016 International Forum on Management, Education and Information Technology Application

View full text Add to dashboard Cite

Abstract. Architecture based development methodology has its strength in organizing requirements as well as has the limitation of slowly responding to the requirements changing; while Agile manner is good at rapidly implementing components and building test scripts, but it is incapable of getting a comprehensive requirement frame. To our knowledge, there are short of related research evidences for the success combination of these two methods. In the paper we propose an approach for their coalition with one purpose: to leverage both strengths existing in these two methods for quickly responding to the changed requirements as well as speeding up the realization progress. The proposal in the paper specifies the combination steps and the communication way; meanwhile, the proposal points out the software frame should be the rendezvous point for these two methods. By a case study and the comparison to previous work the advantage of our proposal could be proven.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Analysis and Comparison To Previous Workmentioning

confidence: 99%

Section: Analysis and Comparison To Previous Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Supporting the combination of agile manner and architecture based development method

Yao¹

2016

Proceedings of the 2016 International Forum on Management, Education and Information Technology Application

View full text Add to dashboard Cite

show abstract

“…The process builds upon Scrum, extendible and relatively lightweight agile method of software development [20], and a process proposed by me in [3], [4], and summarized in [5] (this earlier proposed process was targeting agile architecture modelling). For definition and modelling of software architectures I build upon the Palladio Component Modelling approach (PCM) that is a component-based architecture model approach and tool-chain [1].…”

Section: Proposed Approachmentioning

confidence: 99%

An architecture-centric approach for goal-driven requirements elicitation

Durdik

2011

Proceedings of the 19th ACM SIGSOFT Symposium and the 13th European Conference on Foundations of Software Engineering

Self Cite

View full text Add to dashboard Cite

Software system development typically starts from a requirement specification followed by stepwise refinement of available requirements while transferring them into the system architecture. However, the granularity and the amount of requirements to be elicited for a successful architectural design are not well understood. This paper proposes a process concept to support system development with the help of an architecture-centric approach for goal-driven requirements elicitation. The process focuses on multiple quality dimensions, such as performance, reliability and scalability, and at the same time shall reduce costs and risks through early decision evaluation. The main contribution of this paper is a novel process where not only requirements can drive architectural design, but also architectural design can selectively drive requirement elicitation with the help of hypotheses connected to the selected architectural solutions. The paper concludes with a discussion on its possible empirical validation.

show abstract