Engineering and Managing Software Requirements
暂无分享,去创建一个
[1] Michael E. Fagan. Design and Code Inspections to Reduce Errors in Program Development , 1976, IBM Syst. J..
[2] Neil A. M. Maiden,et al. Bridging the requirements gap: policies, goals and domains , 1993, Proceedings of 1993 IEEE 7th International Workshop on Software Specification and Design.
[3] Dorothy R. Graham,et al. Requirements and Testing: Seven Missing-Link Myths , 2002, IEEE Softw..
[4] Cliff B. Jones,et al. Systematic software development using VDM , 1986, Prentice Hall International Series in Computer Science.
[5] Colette Rolland,et al. Eliciting gaps in requirements change , 2004, Requirements Engineering.
[6] Stefania Gnesi,et al. Applications of linguistic techniques for use case analysis , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.
[7] Nicolas Prat,et al. Goal Formalisation and Classification for Requirements Engineering , 1996 .
[8] Balasubramaniam Ramesh,et al. Implementing requirements traceability: a case study , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).
[9] Adam A. Porter,et al. Comparing Detection Methods For Software Requirements Inspections: A Replication Using Professional Subjects , 1998, Empirical Software Engineering.
[10] Suzanne Robertson,et al. Mastering the Requirements Process , 1999 .
[11] William N. Robinson,et al. Supporting the negotiation life cycle , 1998, CACM.
[12] Klaus Pohl,et al. Modelling Contextual Information about Scenarios , 1999 .
[13] Forrest Shull,et al. How perspective-based reading can improve requirements inspections , 2000, Computer.
[14] Colette Rolland,et al. Bridging the Gap Between Organisational Needs and ERP Functionality , 2000, Requirements Engineering.
[15] Barry W. Boehm,et al. What we have learned about fighting defects , 2002, Proceedings Eighth IEEE Symposium on Software Metrics.
[16] Colette Rolland,et al. Experience with goal-scenario coupling in requirements engineering , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).
[17] Jack Mostow,et al. Toward Better Models of the Design Process , 1985, AI Mag..
[18] Klaus Pohl,et al. Process-Centered Requirements Engineering , 1996 .
[19] Eric S. K. Yu,et al. Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.
[20] Claes Wohlin,et al. State‐of‐the‐art: software inspections after 25 years , 2002, Softw. Test. Verification Reliab..
[21] Douglas T. Ross,et al. Structured Analysis for Requirements Definition , 1977, IEEE Transactions on Software Engineering.
[22] Barry W. Boehm,et al. Prototyping Versus Specifying: A Multiproject Experiment , 1984, IEEE Transactions on Software Engineering.
[23] Pankaj Jalote,et al. Testing the Completeness of Specifications , 1989, IEEE Trans. Software Eng..
[24] Andreas L. Opdahl,et al. Templates for Misuse Case Description , 2001 .
[25] Marc J. Balcer,et al. The category-partition method for specifying and generating fuctional tests , 1988, CACM.
[26] K. Beck,et al. Extreme Programming Explained , 2002 .
[27] Karl E. Wiegers,et al. Writing quality requirements , 1999 .
[28] Andy Huber,et al. Peer reviews in software: a practical guide , 2002, SOEN.
[29] Colette Rolland,et al. Guiding the Participative Design Process , 1997 .
[30] P. Liggesmeyer. Modultest und Modulverifikation – State of the Art , 1990 .
[31] Shari Lawrence Pfleeger,et al. Software Quality: The Elusive Target , 1996, IEEE Softw..
[32] Gerard Le Lann. The Ariane 5 Flight 501 Failure - A Case Study in System Engineering for Computing Systems , 1996 .
[33] William N. Robinson,et al. Conflict-Oriented Requirements Restructuring , 2007 .
[34] Colin Potts,et al. Using schematic scenarios to understand user needs , 1995, Symposium on Designing Interactive Systems.
[35] Jilles van Gurp. Variability in Software Systems , 2000 .
[36] Philippe Massonet,et al. Analogical reuse of requirements frameworks , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.
[37] John D. Musa,et al. Operational profiles in software-reliability engineering , 1993, IEEE Software.
[38] Jan Bosch,et al. On the notion of variability in software product lines , 2001, Proceedings Working IEEE/IFIP Conference on Software Architecture.
[39] John Mylopoulos,et al. From object-oriented to goal-oriented requirements analysis , 1999, CACM.
[40] Barbara Paech,et al. An Integrated Quality Assurance Approach for Use Case Based Requirements , 2004, Modellierung.
[41] Barry W. Boehm,et al. Software Defect Reduction Top 10 List , 2001, Computer.
[42] Jens Rasmussen,et al. Mental models and the control of action in complex environments , 1987, Informatics and Psychology Workshop.
[43] Forrest Shull,et al. The empirical investigation of Perspective-Based Reading , 1995, Empirical Software Engineering.
[44] Frank Moisiadis,et al. The fundamentals of prioritising requirements , 2002 .
[45] Jeffrey C. Carver,et al. Evolving a Set of Techniques for OO Inspections , 1999 .
[46] Alistair Cockburn,et al. Writing Effective Use Cases , 2000 .
[47] Kurt Bittner,et al. Use Case Modeling , 2002 .
[48] John Mylopoulos,et al. Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..
[49] Steve Easterbrook,et al. Resolving requirements conflicts with computer-supported negotiation , 1994 .
[50] Robert V. Binder,et al. Testing Object-Oriented Systems: Models, Patterns, and Tools , 1999 .
[51] Oliver Laitenberger,et al. Cost-effective Detection of Software Defects through Perspective-based Inspections , 2001, Empirical Software Engineering.
[52] C. Rolland,et al. GUIDING GOAL MODELLING USING SCENARIOS , 1998 .
[53] Constance L. Heitmeyer,et al. Automated consistency checking of requirements specifications , 1996, TSEM.
[54] Shailey Minocha,et al. Supporting Scenario-Based Requirements Engineering , 1998, IEEE Trans. Software Eng..
[55] Claes Wohlin,et al. An Experimental Comparison of Usage-Based and Checklist-Based Reading , 2003, IEEE Trans. Software Eng..
[56] Klaus Pohl,et al. Szenario-basiertes Systemtesten von Software-Produktfamilien mit ScenTED , 2004, Modellierung.
[57] W. N. Robinson,et al. Integrating multiple specifications using domain goals , 1989, IWSSD '89.
[58] Dean Leffingwell,et al. Managing software requirements: a unified approach , 1999 .
[59] Kim J. Vicente,et al. Ecological interface design: theoretical foundations , 1992, IEEE Trans. Syst. Man Cybern..
[60] Albert Endres,et al. A handbook of software and systems engineering - empirical observations, laws and theories , 2003, The Fraunhofer IESE series on software engineering.
[61] Bashar Nuseibeh,et al. Expressing the relationships between multiple views in requirements specification , 1993, ICSE '93.
[62] Lionel C. Briand,et al. Assessing the cost-effectiveness of inspections by combining project data and expert opinion , 2000, Proceedings 11th International Symposium on Software Reliability Engineering. ISSRE 2000.
[63] Shailey Minocha,et al. Human errors and system requirements , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).