Product Focused Software Process Improvement: 6th International Conference, PROFES 2005, Oulu, Finland, June 13-18, 2005, ProceedingsFrank Bomarius, Seija Komi-Sirviö Springer, 2005. gada 20. jūn. - 588 lappuses On behalf of the PROFES Organizing Committee we are proud to present to you the proceedings of the 6th International Conference on Product Focused Software Process Improvement (PROFES 2005), held in Oulu, Finland. Since 1999, PROFES has established itself as one of the recognized inter- tional software process improvement conferences. Thepurposeoftheconferenceistobringtolightthemostrecent?ndingsand results in the area and to stimulate discussion between researchers, experienced professionals,andtechnologyproviders.Thelargenumberofparticipantscoming from industry con?rms that the conference provides a variety of up-to-date t- ics and tackles industry problems. The main theme of PROFES is professional software process improvement (SPI) motivated by product and service quality needs. SPI is facilitated by software process assessment, software measurement, process modeling, and technology transfer. It has become a practical tool for quality software engineering and management. The conference addresses both the solutions found in practice and the relevant research results from academia. This is re?ected in the 42 full papers, which are – as in the years before – a well-balanced mix of academic papers as well as industrial experience reports. The business of developing new applications like mobile and Internet services orenhancingthefunctionalityofavarietyofproductsusingembeddedsoftwareis rapidlygrowing,maturingandmeetingtheharshbusinessrealities.Theaccepted papers focusing on wireless and the Internet are grouped into a special “mobile and wireless” session. WewishtothankVTTElectronics,theUniversityofOuluincludingInfotech, and Fraunhofer IESE for supporting the conference. We are also grateful to the authors for high-quality papers, the Program Committee for their hard work in reviewing the papers, the Organizing Committee for making the event possible, and all the numerous supporters who helped in organizing this conference. |
No grāmatas satura
1.–5. rezultāts no 83.
17. lappuse
... selected starting point for the process improvement is a bottom-up approach. The bottom-up approach assumes that the organisation must first understand its process, products, characteristics and goals before it can improve its processes ...
... selected starting point for the process improvement is a bottom-up approach. The bottom-up approach assumes that the organisation must first understand its process, products, characteristics and goals before it can improve its processes ...
21. lappuse
... Selected Work Products Technical Solution (TS) SG1 - Select Product-Component solutions SG2 - Develop the Design SG3 - Implement the Product Design Validation (VAL) SG1 - Prepare for Validation SG2 - Validate Product or Product ...
... Selected Work Products Technical Solution (TS) SG1 - Select Product-Component solutions SG2 - Develop the Design SG3 - Implement the Product Design Validation (VAL) SG1 - Prepare for Validation SG2 - Validate Product or Product ...
30. lappuse
... selected from each domain two life-cycle models which seem representative (e.g. extensively documented and referred to by others). The change domains we have selected life-cycle models from for our comparison are: − Software Process ...
... selected from each domain two life-cycle models which seem representative (e.g. extensively documented and referred to by others). The change domains we have selected life-cycle models from for our comparison are: − Software Process ...
31. lappuse
... selected for our analysis of models in this domain: − INTRo [14] − Cooper & Zmud [1] INTRo [14] is the result of the continuing efforts of the Software Engineering Institute (SEI) in the SPI domain, which have lead to the definition ...
... selected for our analysis of models in this domain: − INTRo [14] − Cooper & Zmud [1] INTRo [14] is the result of the continuing efforts of the Software Engineering Institute (SEI) in the SPI domain, which have lead to the definition ...
33. lappuse
... selected for analysis). It seems as if BPR models are more interested in planning the implementation than executing the plans. The SPI models mention rollout and use, but do not make an effort in describing how. They assume that this ...
... selected for analysis). It seems as if BPR models are more interested in planning the implementation than executing the plans. The SPI models mention rollout and use, but do not make an effort in describing how. They assume that this ...
Saturs
1 | |
16 | |
29 | |
An Empirical Study on OfftheShelf Component Usage in Industrial | 54 |
A Rendezvous of Content Adaptable Service and Product Line Modeling | 69 |
A Framework for Linking Projects and Project Management Methods | 84 |
Software Defect Analysis of a Multirelease Telecommunications System | 98 |
Performance Rather han Capability Problems Insights from Timo Jokela t | 115 |
Process Modeling | 314 |
Acquisition of a ProjectSpecific Process | 328 |
SPI Methods and Tools | 343 |
Improved Control of Automotive Software Suppliers | 358 |
EnterpriseOriented Software Development Environments to Support | 370 |
Experimental Software Engineering | 385 |
Mega Software Engineering | 399 |
Software Development and Experimentation in an Academic | 414 |
Mobile and Wireless Applications | 128 |
Design Patterns and Organisational Memory in Mobile Application | 143 |
Specifying Pattern for Mobile Application Domain Using General Oleksiy Mazhelis Jouni Markkula Markus Jakobsson s | 157 |
Requirements Engineering and Usability | 173 |
Functional and Nonfunctional Requirements Specification | 189 |
Framework for Integrating Usability Practices into the Software Process | 202 |
Industrial Experiences | 216 |
Comprehensive Documentation Made Agile Experiments with | 224 |
Coordination Practices in Global Software Development | 234 |
A Study of a Mentoring Program for Knowledge Transfer in a Small | 245 |
Impacts of Software Deployment in the Coffee Agribusiness of Brazil | 257 |
Software Product Integration Practices | 272 |
Process Analysis | 286 |
Relation Analysis Among Patterns on Software Development Process | 299 |
Validation and Verification | 429 |
RiskBased TradeOff Between Verification and Validation | 443 |
Investigating the Impact of Active Guidance on Design Inspection | 458 |
Agile Methods | 474 |
Views from an Organization on How Agile Development Affects | 487 |
An Industry Experience | 502 |
Teaching XP Skills to Students and IT Professionals | 517 |
Measurement | 530 |
Tool Support for Personal Software Process | 545 |
299 | 559 |
An Experience Factory to Improve Software Development Effort | 560 |
An Instrument for Measuring the Maturity of Requirements Engineering | 574 |
Author Index | 587 |
Citi izdevumi - Skatīt visu
Product Focused Software Process Improvement: 6th International Conference ... Frank Bomarius Ierobežota priekšskatīšana - 2005 |
Bieži izmantoti vārdi un frāzes
7DED active guidance adaptation Agile Hours agile methods agile process analysis application approach architecture assessment Capability Maturity Model CBR-tc checklist CMMI collaboration components Computer context customer representatives defects defined described development process document effort environment estimate evaluation experience Extreme Programming files framework FreeBSD functionality goals identified IEEE impact implementation inspection inspectors integration interviews introduced issues iteration Knowledge Management Lego Mega Software Engineering mentor meta-model metric mobile NetBSD OpenBSD organization organizational pair programming paper participants patterns performance phase PPDs practices problems PROFES project managers prototyping reading technique requirements roles Section selected similar Sline software development process Software Inspection Software Process Improvement software products software systems source code specific story cards Table tailoring task Technology test-first tool usability usability engineering user stories validation variables