Architecting Software Intensive Systems

Lattanze, Anthony J.

doi:10.1201/9781420045703

Cited by 41 publications

(16 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…As mentioned in Section 2.1, Archinotes allows building models based on the viewpoints proposed by Rozanski [11] through the Archinotes Modeler component. This component is inspired on the Lattanze model template [8], which belongs to the Architecture Centric Design Method (ACDM). Archinotes Modeler provides architects to design and coordinate despite geographical and temporal differences.…”

Section: Supporting Collaboration Through Social Mediamentioning

confidence: 99%

Archinotes: A tool for assisting software architecture courses

Urrego

Correal

2013

2013 26th International Conference on Software Engineering Education and Training (CSEE&T)

View full text Add to dashboard Cite

During the last years, software architecture has become an increasingly necessary subject in IT education. At Universidad de los Andes, a software architecture course is taught midway through the Systems and Computer Engineering degree and aims to create skills within the student to identify quality requirements as well as designing software architectures for middle-sized systems. However, based on statistics over the last 8 years of our Software Architecture course, we've noticed that correctly identifying quality requirements seems to be a recurring issue among students. One of the course's objectives comprehends the construction of an architecture document during the semester, which must be done in groups who tend to find it difficult to get together and work as a team. This paper present Archinotes, a collaboration tool to support the teaching of software architectures by facilitating collaboration workload and providing useful information on the difficulties and progress of the students to the course's teacher. The conclusions of the paper prove Archinotes effective in helping students learn critical concepts and artifacts during the software architecture course.

show abstract

Section: Supporting Collaboration Through Social Mediamentioning

confidence: 99%

Archinotes: A tool for assisting software architecture courses

Urrego

Correal

2013

2013 26th International Conference on Software Engineering Education and Training (CSEE&T)

View full text Add to dashboard Cite

show abstract

“…Lattanze [31] classies architecture documentation strategies into horizontal and vertical ones, emphasizing that both require SAD planning as well as identication of stakeholders and their information needs. In a vertical strategy, custom documents are created for specic stakeholders.…”

Section: Related Workmentioning

confidence: 99%

Producing Just Enough Documentation: An Optimization Approach Applied to the Software Architecture Domain

et al. 2015

View full text Add to dashboard Cite

The Software Architecture is an important asset in a software development process, which serves to share and discuss the main design concerns among the project stakeholders. The architecture must be properly documented (e.g., via a Wiki environment) in order to be eectively used by these stakeholders. However, the process of producing architecture documentation often fails to deliver contents that address the stakeholders' information needs.To address the problem, we argue for a knowledge management strategy in which: (i) architecture documentation is created incrementally; and (ii) its contents are driven by a model of stakeholder preferences. In this work, we present an information optimization approach applied to the architecture documentation domain, derived from an existing documentation method called Views & Beyond. To do so, we dene the Next SAD Version Problem (NSVP) and then provide tool support to assist architects in producing cost-eective documentation. Based on prior work, we perform a sensitivity analysis of the optimization model and develop a robust formulation that takes into account uncertainty in the parameter estimations for NSVP instances, thus improving the outcomes of our documentation assistant.

show abstract

“…In this research, ASR term is used to specify the key requirements. Only a few high-level functional requirements, all the QARs, technical and business constraints are the ASR that influence the architecture design decision [12]. High-level functional requirements specify a general description of functionality.…”

Section: Kumarmentioning

confidence: 99%

“…According to Lattanze [12] "while functional requirements describe what the system must do, QARs describe how the system must do it." In general, QAR and functional requirements are always combined.…”

Section: Kumarmentioning

confidence: 99%

“…ASR consists of high-level functional requirements, quality attribute requirements (QAR), technical and business constraints. According to Lattanze [12] "while functional requirements describe what the system must do, QAR describe how the system must do it." A technical constraint instructs the preference of the particular hardware, software, standards, operating systems and other constraints.…”

Section: Kumarmentioning

confidence: 99%

See 1 more Smart Citation

Evaluation of Capturing Architecturally Significant Requirements

Kumar

2017

Asian J Pharm Clin Res

View full text Add to dashboard Cite

Every software development organization strives for customer satisfaction. It is universally accepted that the success of software development lies in the clear understanding of the client requirements. During requirement elicitation and analysis stage, the system analyst identifies the functional and nonfunctional requirements from the customer. Security, usability, reliability, performance, scalability, and supportability are the significant quality attributes of a software system. These quality attributes are also referred as non-functional requirements. Only a few functional and quality attributes requirement help to identify and shape the software architecture. A software system's architecture is the set of prime design decisions made about the system. If the requirement influences the architectural design decision then, it is referred as architecturally significant requirement (ASR). Identifying and specifying all the possible ASR are important tasks in the requirement elicitation and analysis stage. In this research, general problems that are faced while capturing and specifying ASR in requirement elicitation and analysis is studied. Among the different requirement elicitation techniques, use case diagram has been identified and enhanced to solve the problem of capturing and specifying ASR during the requirement elicitation and analysis phase.

show abstract

Architecting Software Intensive Systems

Cited by 41 publications

References 0 publications

Archinotes: A tool for assisting software architecture courses

Archinotes: A tool for assisting software architecture courses

Producing Just Enough Documentation: An Optimization Approach Applied to the Software Architecture Domain

Evaluation of Capturing Architecturally Significant Requirements

Contact Info

Product

Resources

About