Titlebook: Software Process Improvement; 12th European Confer Ita Richardson,Pekka Abrahamsson,Richard Messnarz Conference proceedings 2005 Springer-V

唤醒

Pair Programming vs. Side-by-Side Programmingare two styles of pair programming: XP-like and side-by-side (the latter comes from Crystal Clear). In the paper an experiment is described that aimed at comparison of those two styles. The subjects were 25 students of Computer Science of 4. and 5. year of study. They worked for 6 days at the univer

从属

habile

anaphylaxis

钝剑

PSA-velocity

Customer-Oriented Specification and Evaluation of IT Service Level AgreementsA definitions are based on technical performance criteria that may be captured easily such as ‘system availability’; the specific needs of the IT system are not considered explicitly. Hence, high system performance does not lead to high customer satisfaction in practice. A methodology based on Quali

LUCY

Safety Methods in Software Process Improvementin a safe way during the lifetime of the software. We define a system as safe if the risks related to its use are judged to be acceptable [1]. Safety must not be confused with security which broadly is defined as keeping the system unavailable for people who should not be able to access it. In this

Lipoprotein

RAMALA: A Knowledge Base for Software Process Improvement improvement program within such organizations is very difficult, due to its high cost and small ROI percentage that could be obtained. RAMALA is a knowledge base, supported by a software tool called also RAMALA, that contains a software process framework, which is mainly based on the PMBOK process

擦掉

我不死扛

Reference Model for Software Process Improvement: A Brazilian ExperienceBrazil, there is an urge to enhance software processes performance aiming to improve the quality of software products and to increase Brazilian organizations competitive advantages both in the national and international markets. This work describes an approach developed to establish the base for Bra