5. Methods
The methods required for the IS have been the subject of formalization and standardization work to which many experts have contributed.
the profession's vocabulary is emphatic and inappropriate: it likes to say "methodology" for method, "problematics" for problem, "technology" for technique, and so on.
Their authors all warn that these methods are only indicative, and should not be followed to the letter. However, project managers, CIOs and companies are keen to acquire "certifications" which, they believe, will guarantee their efficiency, favour them in the competition and, possibly, provide them with an alibi in the event of failure.
The defensive use of methods encourages sterile formalism: contracts replace cooperation and leadership, useless documents accumulate...
Exclusive to subscribers. 97% yet to be discovered!
You do not have access to this resource.
Click here to request your free trial access!
Already subscribed? Log in!
The Ultimate Scientific and Technical Reference
This article is included in
Software technologies and System architectures
This offer includes:
Knowledge Base
Updated and enriched with articles validated by our scientific committees
Services
A set of exclusive tools to complement the resources
Practical Path
Operational and didactic, to guarantee the acquisition of transversal skills
Doc & Quiz
Interactive articles with quizzes, for constructive reading
Methods
Bibliography
Websites
Information system audit and control association (ISACA) http://www.itgi.org
Object management group (OMG) http://www.omg.org/
Project Management Institute http://www.pmi.org/
...Exclusive to subscribers. 97% yet to be discovered!
You do not have access to this resource.
Click here to request your free trial access!
Already subscribed? Log in!
The Ultimate Scientific and Technical Reference