REQUIREMENTS CONFLICTS AND ARCHITECTURAL DESIGN

[1]  Nenad Medvidovic,et al.  Reconciling software requirements and architectures: the CBSP approach , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[2]  Dianxiang Xu,et al.  Threat-Driven Architectural Design of Secure Information Systems , 2018, ICEIS.

[3]  Jung-Won Park.  Supporting Distributed Collaborative Prioritization for WinWin Requirements Capture and Negotiations , 1999 .

[4]  Francisca Losavio,et al.  Quality Models to Design Software Architecture , 2002, J. Object Technol..

[5]  Stanley M. Sutton,et al.  N degrees of separation: multi-dimensional separation of concerns , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[6]  Michael Jackson,et al.  Conjunction as composition , 1993, TSEM.

[7]  Barbara Paech,et al.  Task-Driven Requirements in Object-Oriented Development , 2004 .

[8]  Stefan Biffl,et al.  Repeatable quality assurance techniques for requirements negotiations , 2003, 36th Annual Hawaii International Conference on System Sciences, 2003. Proceedings of the.

[9]  Eila Niemelä,et al.  A Survey on Software Architecture Analysis Methods , 2002, IEEE Trans. Software Eng..

[10]  Leonard J. Bass,et al.  SAAM: a method for analyzing the properties of software architectures , 1994, Proceedings of 16th International Conference on Software Engineering.

[11]  Alexander Egyed,et al.  A Scenario-Driven Approach to Trace Dependency Analysis , 2003, IEEE Trans. Software Eng..

[12]  Zhixiong Liu,et al.  Towards Modeling Non-Functional Requirements in Software Architecture , 2005 .

[13]  Alexander Egyed,et al.  Identifying requirements conflicts and cooperation: how quality attributes and automated traceability can help , 2004, IEEE Software.

[14]  Barry W. Boehm,et al.  Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach , 1995, 1995 17th International Conference on Software Engineering.

[15]  Tyson R. Browning,et al.  Applying the design structure matrix to system decomposition and integration problems: a review and new directions , 2001, IEEE Trans. Engineering Management.

[16]  Raymond J. A. Buhr,et al.  Use Case Maps as Architectural Entities for Complex Systems , 1998, IEEE Trans. Software Eng..

[17]  Bashar Nuseibeh,et al.  Weaving Together Requirements and Architectures , 2001, Computer.

[18]  George R. Ribeiro-Justo,et al.  A framework for building non-functional software architectures , 2001, SAC.

[19]  Bedir Tekinerdogan,et al.  ASAAM: aspectual software architecture analysis method , 2003, Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004).

[20]  Rick Kazman,et al.  The architecture tradeoff analysis method , 1998, Proceedings. Fourth IEEE International Conference on Engineering of Complex Computer Systems (Cat. No.98EX193).

[21]  Rick Kazman,et al.  From requirements negotiation to software architecture decisions , 2005, Inf. Softw. Technol..

[22]  Nenad Medvidovic,et al.  Dimensions of Concerns in Requirements Negotiation and Architecture Modeling 1 , 2000 .

[23]  Leonard J. Bass,et al.  Scenario-Based Analysis of Software Architecture , 1996, IEEE Softw..

[24]  Axel van Lamsweerde,et al.  Managing Conflicts in Goal-Driven Requirements Engineering , 1998, IEEE Trans. Software Eng..

[25]  Bashar Nuseibeh,et al.  Expressing the relationships between multiple views in requirements specification , 1993, ICSE '93.

[26]  Steve M. Easterbrook,et al.  Using ViewPoints for inconsistency management , 1996, Softw. Eng. J..

[27]  Amar Ramdane-Cherif,et al.  Quality Characteristics for Software Architecture , 2003, J. Object Technol..

[28]  Dietmar Pfahl,et al.  Trade-off Analysis for Requirements Selection , 2003, Int. J. Softw. Eng. Knowl. Eng..

[29]  Thomas A. Alspaugh,et al.  An architectural pattern for non-functional dependability requirements , 2005, ACM SIGSOFT Softw. Eng. Notes.

[30]  Oliver Laitenberger,et al.  An encompassing life cycle centric survey of software inspection , 2000, J. Syst. Softw..

[31]  Daniel Gross,et al.  Architectural Design to Meet Stakeholder Requirements , 1999, WICSA.

[32]  Jan Bosch,et al.  Software architecture design: evaluation and transformation , 1999, Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems.

[33]  Daniel Gross,et al.  Evolving system architecture to meet changing business goals: an agent and goal-oriented approach , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[34]  Hoh Peter In,et al.  Visualization issues for software requirements negotiation , 2001, 25th Annual International Computer Software and Applications Conference. COMPSAC 2001.

[35]  Paul Clements,et al.  ATAM: Method for Architecture Evaluation , 2000 .

[36]  Paul Clements,et al.  Capturing and Using Rationale for a Software Architecture , 2006 .

[37]  Shailey Minocha,et al.  Scenario-based Analysis of Non-Functional Requirements , 1998, REFSQ.

[38]  Axel van Lamsweerde,et al.  From System Goals to Software Architecture , 2003, SFM.

[39]  N. H. Lassing,et al.  On software architecture analysis of flexibility, Complexity of changes: Size isn't everything , 1999 .

[40]  William N. Robinson,et al.  Requirements interaction management , 2003, CSUR.

[41]  Xavier Franch,et al.  Putting non-functional requirements into software architecture , 1998, Proceedings Ninth International Workshop on Software Specification and Design.