Software architects in practice

Lakshminarayanan, Vidya; Liu, WenQian; Chen, Charles L.; Easterbrook, Steve; Perry, Dewayne E.

doi:10.1145/1188966.1189000

Cited by 18 publications

(10 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Lakshminarayanan et al argue that it is impossible to create a tool to reason about all the issues that an architect would normally need to consider. 29 In addition, we should be aware of the fact that a lot of the available knowledge cannot be made explicit at all, but instead remains tacit in the minds of people. 18 Sharing such tacit knowledge is very hard.…”

mentioning

confidence: 99%

Eagle: Effective Tool Support for Sharing Architectural Knowledge

Farenhorst

Lago

Vliet

2007

Int. J. Coop. Info. Syst.

View full text Add to dashboard Cite

Knowledge management plays an important role in the software architecting process. Recently, this role has become more apparent by a paradigm shift that views a software architecture as the set of architectural design decisions it embodies. This shift has sparked the discussion in both research and practice on how to best facilitate sharing of so-called architectural knowledge, and how tools can best be employed. In order to design successful tool support for architectural knowledge sharing it is important to take into account what software architecting really entails. In this paper, we define the main characteristics of architecting, based on observations in a large software development organization, and state-of-the-art literature in software architecture. Based on the defined characteristics, we determine how best practices known from knowledge management could be used to improve architectural knowledge sharing. This results in the definition of a set of desired properties of architectural knowledge sharing tools. Finally, we highlight the design and implementation of EAGLE, an architectural knowledge sharing portal that implements those properties.

show abstract

mentioning

confidence: 99%

Eagle: Effective Tool Support for Sharing Architectural Knowledge

Farenhorst

Lago

Vliet

2007

Int. J. Coop. Info. Syst.

View full text Add to dashboard Cite

show abstract

“…The conventional view of requirements definition is that this phase of systems development begins with an informal description of "what" the system is expected to do [5], [6]. As has been explained by [13], one of the major tasks in designing systems development is the systematic elaboration of system requirements.…”

Section: A System Requirement Concept and Typesmentioning

confidence: 99%

“…Even though that the NFR are often underestimated or ignored [22] there is a common consensus that NFR are essential and can be critical for the success of a system project [6], [10], [19], [23]- [25]. Furthermore, to achieve a high quality software system, both FR and NFR should be addressed [12], [26].…”

Section: A System Requirement Concept and Typesmentioning

confidence: 99%

The Most Important Functional and Non-Functional Requirements of Knowledge Sharing System at Public Academic Institutions: A Case Study

Alsaleh¹,

Haron²

2016

LNSE

View full text Add to dashboard Cite

Abstract-This qualitative study aims to explore and describe the most important functional requirements (FR) and non-functional requirements (NFR) of knowledge sharing system (KSS) used at a Malaysian public academic institution. The strategy used is a single case study which aims to gather deeper insights on the requirements of the KSS. Data were collected through semi-structured interviews. A total of fifteen renowned academicians were interviewed. Content analysis method was used to extract the requirements from the qualitative data. The study identified twelve FR and NFR that academicians as an end users believe should be included in the KSS. The FR include alert user about new added; be able to categorize contents, have an efficient search process; offer information about experts; offer a consultation service; and provide interconnections among disciplines. The NFR include support multi-media, ensure accessibility; provide interactivity; be reliable; easy to use; and multi-level. The research comprehensive analysis and findings would expand an area of systems FR and NFR being used for knowledge sharing in academic institutions which may still theoretically and empirically not sufficiently covered.Index Terms-Academicians, functional requirement, non-functional requirement, knowledge sharing system.

show abstract

“…Another warning is that it is infeasible to strive for completeness. In [20] it is noted that it is impossible to create a tool to reason about all the issues that an architect would normally need to consider. Finally, we should be aware of the fact that a lot of the available knowledge cannot be made explicit at all, but instead remains tacit in the minds of people [21].…”

Section: Related Workmentioning

confidence: 99%