共查询到20条相似文献,搜索用时 328 毫秒
1.
Emelie Engström 《Information and Software Technology》2011,53(1):2-13
Context
Software product lines (SPL) are used in industry to achieve more efficient software development. However, the testing side of SPL is underdeveloped.Objective
This study aims at surveying existing research on SPL testing in order to identify useful approaches and needs for future research.Method
A systematic mapping study is launched to find as much literature as possible, and the 64 papers found are classified with respect to focus, research type and contribution type.Results
A majority of the papers are of proposal research types (64%). System testing is the largest group with respect to research focus (40%), followed by management (23%). Method contributions are in majority.Conclusions
More validation and evaluation research is needed to provide a better foundation for SPL testing. 相似文献2.
Ákos Sz?ke 《Information and Software Technology》2011,53(6):574-591
Context
Release scheduling deals with the selection and assignment of deliverable features to a sequence of consecutive product deliveries while several constraints are fulfilled. Although agile software development represents a major approach to software engineering, there is no well-established conceptual definition and sound methodological support of agile release scheduling.Objective
To propose a solution, we present, (1) a conceptual model for agile scheduling, and (2) a novel multiple knapsack-based optimization model with (3) a branch-and-bound optimization algorithm for agile release scheduling.Method
To evaluate our model simulations were carried out seven real life and several generated data sets.Results
The developed algorithm strives to prevent resource overload and resource underload, and mitigates risks of delivery slippage.Conclusion
The results of the experiment suggest that this approach can provide optimized semi-automatic release schedule generations and more informed and established decisions utilizing what-if-analysis on the fly to tailor the best schedule for the specific project context. 相似文献3.
Context
Although agile software development methods such as SCRUM and DSDM are gaining popularity, the consequences of applying agile principles to software product management have received little attention until now.Objective
In this paper, this gap is filled by the introduction of a method for the application of SCRUM principles to software product management.Method
A case study research approach is employed to describe and evaluate this method.Results
This has resulted in the ‘agile requirements refinery’, an extension to the SCRUM process that enables product managers to cope with complex requirements in an agile development environment. A case study is presented to illustrate how agile methods can be applied to software product management.Conclusions
The experiences of the case study company are provided as a set of lessons learned that will help others to apply agile principles to their software product management process. 相似文献4.
《Datenschutz und Datensicherheit - DuD》2011,35(2):155-155
DuD Report
Veranstaltungskalender 2 / 2011 相似文献5.
Alessandra Di Pierro Chris Hankin Herbert Wiklicky 《International Journal of Information Security》2011,10(2):61-61
Preface
Preface 相似文献6.
7.
8.
Sherry Chen Jane Coughlan Steve Love Robert Macredie Frankie Wilson 《User Modeling and User-Adapted Interaction》2005,15(5):505-505
Announcement
Announcement 相似文献9.
Kenneth Boness 《Information and Software Technology》2011,53(10):1084-1096
Context
During development managers, analysts and designers often need to know whether enough requirements analysis work has been done and whether or not it is safe to proceed to the design stage.Objective
This paper describes a new, simple and practical method for assessing our confidence in a set of requirements.Method
We identified four confidence factors and used a goal oriented framework with a simple ordinal scale to develop a method for assessing confidence. We illustrate the method and show how it has been applied to a real systems development project.Results
We show how assessing confidence in the requirements could have revealed problems in this project earlier and so saved both time and money.Conclusion
Our meta-level assessment of requirements provides a practical and pragmatic method that can prove useful to managers, analysts and designers who need to know when sufficient requirements analysis has been performed. 相似文献10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
Ninja Marnau Norbert Schirmer Eva Schlehahn Matthias Schunter 《Datenschutz und Datensicherheit - DuD》2011,35(2):145-152