21 research outputs found
TTCN-3 : de testtaal van de toekomst
No full textNaarmate de hoeveelheid te testen software en het belang van goed geteste software toenemen, neemt de vraag naar testautomatisering toe. De praktijk van outsourcing en offshoring voegt hier nog extra uitdagingen aan toe. Voor testautomatisering is sinds kort een specifiek gestandaardiseerde programmeertaal beschikbaar: TTCN-3.
Door de toenemende vraag naar testautomatisering en de huidige praktijk van outsourcing en offshoring is een gestandaardiseerde testtaal onontbeerlijk. Sinds kort is een specifiek voor testautomatisering gestandaardiseerde programmeertaal beschikbaar: TTCN-3. De taal en tools voor TTCN-3 zijn intensief in de praktijk getoetst. Hieruit blijkt dat TTCN-3 waarschijnlijk de toekomst van testautomatisering gaat bepalen
Achieving software quality by GQM measurement
No full textSoftware development is a discipline with specific management difficulties.
Collecting relevant data during development is a way to overcome these
difficulties. Such data collection for sqftware development is termed Software
Measurement . Software measurement is a powerful aid to quality improvement
of products and processes. A well-known and popular software measurement
approach is the Goal/Question/Metric approach (GQM). This chapter presents
available techniques for GQM measurement and a research road map to enhance
GQM into a mature measurement approach. The main conclusion is that GQM
promises to become the international standard for software measurement.
However, the emphasis of the method must be focused on the interpretation
process of measurement data and tools must become available that support this
interpretation process. Organisations should start to recognise that improved
understanding by developers is the only way to continuous improvement. Only
bottom-up approaches, such as GQM, provide this understanding. Bottom-up
improvement must be applied in practice. It is recommended to apply top-down
improvement approaches, such as the Capability Maturity Model, in parallel with
software measurement
Improvement by GQM measurement
No full textSoftware development is a discipline with specific management difficulties. Collecting relevant data during development is a way to overcome these difficulties. Such data collectionfor software development is termed ‘Software Measurement’. Software measurement is a poweiful aid to quality improvement ofproducts and processes. A well-known andpopular software measurement approach is the Goal! Question/Metric approach (GQM). This chapter presents available techniques for GQM measurement and a research road-map to enhance GQM into a mature measurement approach. The main conclusion is that GQM promises to become the international standard for software measurement. Howevem the emphasis of the method must be focused on the interpretation process of measurement data and tools must become available that support this interpretation process. Organisations should start to recognise that improved understanding by developers is the only way to continuous improvement. Only bottom-up approaches, such as GQM, provide this understanding. Bottom-up improvement must be applied in practice. It is recommended to apply top-down improvement approaches, such as the Capability Maturity Model, in parallel with software measurement
The goal/question/metric method:a practical guide for quality improvement of software development
No full textNot available
Product focused process improvement in the embedded systems industry : experiences on PROFES methodology application in Dräger, Ericsson and Tokheim
No full textPartnership with customers in product improvement: Testing embedded software products in the field
No full textThe features of electrotechnical products are increasingly provided by software instead of hardware. Software is the keyfactor in creating products that are ‘better’ than those from competitors, with respect to quality, price, functionality, reliability and performance. During embedded software development, testing products is a major task, like it is for non-embedded software development. Real-life is the best testing environment. Therefore a testing approach widely applied for embedded products is a method termed ‘Field Testing’. This is the release of a small number of products to customers. The objective of a field test is to make sure that faults and failures are reported and taken out of the product, before normal distribution can start. Schlumberger RPS applies field tests to its products for that purpose.\u3cbr/\u3e\u3cbr/\u3eThe actual number of failures reported from field tests is lower than expected. However, failures are found later that should have been reported from field test. Therefore, the effectiveness of the field tests must be improved. Our research concluded the need to emphasise two aspects. Firstly, the need to motivate people to detect and report failures by assigning responsibility for field test results. Secondly, the need to include functionality in the product to enable automatic detection, recording, and communication of failures.\u3cbr/\u3
Assessing feedback of measurement data: Relating Schlumberger practices learning to theory
No full textSchlumberger RPS successfully applies software measurement to support their software development projects. It is proposed that the success of their measurement practices is mainly based on the organization of the interpretation process. This interpretation of the measurement data by the project team members is performed in so-called 'feedback sessions'. Many researchers identify the feedback process of measurement data as crucial to the success of a quality improvement program. However, few guidelines exist about the organization of feedback sessions. For instance, with what frequency should feedback sessions be held, how much information should be presented in a single session, and what amount of user involvement is advisable? Within the Schlumberger RPS search to improve feedback sessions, the authors explored learning theories to provide guidelines to these type of questions. After all, what is feedback more than learning?
