Please enable JavaScript.
Coggle requires JavaScript to display documents.
Ensaio - Coggle Diagram
Ensaio
Introdução
PEMAER
Macroprocesso
Objetivo estratégico M181200
Argumento 1
Argumento 2
Tese
Desenvolvimento
Carência de recursos
Contigenciamento de recursos financeiros
humanos
mercado aquecido
Dificuldade de contratação
a sistematização do processo aquisitivo de software acrescenta eficiência ao processo
Temos e-PING, e-MAG, e padrões de adoção de dados abertos, mas nada na área da modalide de aquisição
Não é preciso reinventar a roda
A utilização do método AHP simplificará o processo decisório de aquisição de software.
contextualização e aplicaçao do método AHP
Citar que AHP já foi usado para solucionar problemas de TI e referenciar
a decomposiçao de um problema complexo em problemas menores facilidade a compreensão, análise e resolução da demanda
É possível verificar a consistência dos pesos atribuídos
“A simplicidade é o último grau da sofisticação”(Leonardo da Vinci)
modalidades de aquisição de software
COTS
Acquiring COTS software has become an economic necessity because it shortens the implementation timeline and lessens the unpredictability associated with developing custom applications.
While this alternative might appear risk-free, over half of all enterprise systems implementations fail.
implementing the package usually requires organizational changes to adapt business processes to fit the software
With organizational change comes resistance.
The decision to acquire more can be made in two ways: whether to buy the entire solution or just a few components. Modifiable
off-the-shelf (MoTS) and Commercial off-the-shelf (COTS) solutions are available (CoTS)
In his opinion, the organizations, while making a build versus
buy decision, find themselves in one of the three possible
scenarios that include: buy a package solution and customize
it to fit, buy a package and change the organizational needs
to fit the package, or develop a customized in-house software solution that has its own advantages and disadvantages.
Desenvolver
In his opinion, the in-house development should be adopted if there is an ad-hoc single business process to address, the problem to address is unique, the problem is isolated, and the staff to develop software is available.
On the other hand, the cons of the in-house development
include: constant staff engagement, lower functionality, and updates are hard to make as a complete iteration of development is required for this purpose which causes expensive
time, cost, and human resource commitments.
One of the advantages is the complete
control over the application code and development schedule.
Conclusão
Retomar argumentos
retomar a tese
Alinhar ao PEMAER