Proposta de Processo Ãgil de Desenvolvimento de Software para a Critical Software
Authors
Abstract
Unstable software requirements, caused by today's fast-paced business environment, call for flexibility in the development process. On the other hand, the increased need to outsource that development, combined with concerns regarding the capability of contractors spread around the globe, leads Customers into demanding them to be certified according to highly formal quality management standards. Some examples are ISO's 9001:2000 generic quality guidelines, its TickIT interpretation for IT companies; ISO's 12207 for project life cycle management (PLCM); the Capability Maturity Model (CMM) framework or its European counterpart SPICE ; plus AQAP 150 and AQAP 2110 if the Customer is a military institution such as NATO; plus ECSS or NASA-SEL if the Space sector is involved.This thesis tries to reconcile these contradicting needs ' more flexibility and, at the same time, more formality ' in a software development process for a company called Critical Software. The findings can provide insights to others facing similar challenges.