background preloader

ITIL France - Le site francophone et gratuit sur ITIL

ITIL France - Le site francophone et gratuit sur ITIL
Related:  Dev (development) Methods

Information Technology Infrastructure Library Un article de Wikipédia, l'encyclopédie libre. Pour l’article homonyme, voir Itil. ITIL (Information Technology Infrastructure Library pour « Bibliothèque pour l'infrastructure des technologies de l'information ») est un ensemble d'ouvrages recensant les bonnes pratiques (« best practices ») du management du système d'information. Rédigée à l'origine par des experts de l'Office public britannique du Commerce (OGC), la bibliothèque ITIL a fait intervenir à partir de sa version 3 des experts issus de plusieurs entreprises de services telles qu'Accenture, Ernst & Young, Hewlett-Packard, Deloitte, BearingPoint ou PriceWaterhouseCoopers. C'est un référentiel très large qui aborde les sujets suivants : Comment organiser un système d'information ? Après un développement essentiellement européen jusqu'à la fin des années 1990, ITIL s'est implanté sur le marché nord-américain via des entreprises de conseil en transformation des systèmes d'information. À quoi sert ITIL ? Sécurité juridique Économies

Ensemble liens vers methodo : The wheel of estimation Tous les dimanches, recevez non seulement les 5 dessins de la semaine, mais également notre sélection de vidéos, de gifs et d’articles qui nous on fait marrer et qui devraient vous faire marrer aussi ! A quoi ça ressemble ? Ça vous donne envie ? Brooks's law Brooks's law is a principle in software development which says that "adding manpower to a late software project makes it later."[1][2] It was coined by Fred Brooks in his 1975 book The Mythical Man-Month. The corollary of Brooks's Law is that there is an incremental person who, when added to a project, makes it take more, not less time. Brooks adds that "Nine women can't make a baby in one month." Explanations[edit] According to Brooks himself, the law is an "outrageous oversimplification",[1] but it captures the general rule. Exceptions and possible solutions[edit] Brooks's law is often cited to justify why projects keep being late, despite management efforts. The first point is to note that Brooks's law often applies to projects that are already late.[6] Projects can be brought back into (or kept in) control if people are added earlier in the process.[7] It is also important to determine if the project is really late, or if the schedule was originally overly optimistic. See also[edit]

Communication orale, conseils, trucs, astuces : des liens pertinents sur Manager GO! Certains ont des facilités pour communiquer à l'oral d'autres moins. Il n'en demeure pas moins que cette capacité s’acquiert en maîtrisant des techniques de base et en adoptant les bonnes stratégies. préparer son message : c'est répondre à la question "pourquoi vais-je dire cela". L' objectif est ainsi clairement défini. se préparer en tant qu'émetteur : prendre de l'assurance et créer un climat propice à l'échange, mettre fin à la communication : conclure par quelque chose de concret (planification d'une nouvelle rencontre, mise en place d'une solution...). établir un suivi : rester en contact, faire des points réguliers... bref toute action dans la continuité de la conclusion faite à l'étape précédente. Ce dossier recense de nombreuses publications traitant de sujet autour de la communication orale. Articles Zut ! Normand Lootzak insiste sur les enjeux de l'efficacité de la communication. Le manager urbainManagers, surveillez vos mots Kolibri CoachingAssertivité : communiquez sans bémol Cours

Loi de Brooks Un article de Wikipédia, l'encyclopédie libre. La loi de Brooks — d'après Frederick Brooks — est une prédiction sur la productivité des projets informatiques : « Ajouter des personnes à un projet en retard accroît son retard » (formulation originale : « Adding manpower to a late software project makes it later »). Le postulat est que la plupart des tâches ne sont pas partitionnables et que les nouveaux arrivants vont faire perdre du temps aux équipes en place en temps de communication. Ce temps perdu étant proportionnel à n(n-1) (où n est le nombre de personnes impliquées).

Le Mythique homme-mois Un article de Wikipédia, l'encyclopédie libre. Le Mythe du mois-homme (titre original : The Mythical Man-Month: Essays on Software Engineering) est un livre de Frederick Brooks considéré comme un classique dans le domaine du génie logiciel. Le titre de l'ouvrage fait référence à une unité de coût de développement : le mois-homme ou plus communément l'homme-mois, c'est-à-dire le travail d'un homme pendant un mois. Bien que certaines remarques proprement techniques de l'ouvrage soient très datées (car portant sur des types de systèmes depuis longtemps dépassés), de nombreux problèmes soulevés par Brooks sont toujours d'actualité au XXIe siècle. Le livre a été publié une première fois en 1975, et réédité en 1995[2]. Résumé[modifier | modifier le code] Brooks y expose son expérience du développement informatique et notamment du développement d'OS/360 chez IBM. La loi de Brooks[modifier | modifier le code] Formule des canaux de communication : En combinatoire, n participants pris 2 à 2 =

Mike Cohn Mike Cohn, 2013 He has served as Vice President of Development at four different companies that successfully employed agile concepts and strategies and been a technology executive in companies of various sizes, from start-up to Fortune 40. Cohn is the author of Agile Estimating and Planning, User Stories Applied for Agile Software Development and Succeeding with Agile: Software Development using Scrum, as well as books on Java and C++ programming[4] and articles for Better Software, IEEE Computer, Software Test and Quality Engineering, Agile Times, Cutter IT Journal, and the C++ Users' Journal. He is also the editor of the Addison-Wesley Mike Cohn Signature Series of books. Cohn was a Keynote Speaker on ADAPTing to Agile for Continued Success at the Agile 2010 Presented by the Agile Alliance.[5] In 2012, Cohn was named #1 in The Top 20 Most Influential Agile People.[6] Publications[edit] Mike Cohn (2004). Online Presentations[edit] References[edit] External links[edit] Mike Cohn's Homepage

popen() -- open a pipe stream and execute command #include <stdio.h> FILE *popen(const char *command, const char *mode); The function executes the specified command. It creates a pipe between the calling program and the executed command, and returns a pointer to a stream that can be used to either read from or write to the pipe. The function passes the command to the host environment so that a command processor can execute it. The command ensures that any streams from a previous call that remain open in the parent process are closed in the new child process. The requested mode string specifies the I/O mode: If the mode is "r", "rt", or "rb", when the child process is started, its stdout is the writable end of the pipe, and the file descriptor of the returned stream is the readable end of the pipe. After returns, both the parent and the child process are capable of executing independently before either terminates. command Points to a null-terminated string consisting of a shell command line. mode If successful, returns a stream pointer.

Kohonen Teuvo Dr. Eng., Emeritus Professor of the Academy of Finland; Academician His research areas are the theory of self-organization, associative memories, neural networks, and pattern recognition, in which he has published over 300 research papers and four monography books. His fifth book is on digital computers. His more recent work is expounded in the third, extended edition (2001) of his book Self-Organizing Maps. Since the 1960s, Professor Kohonen has introduced several new concepts to neural computing: fundamental theories of distributed associative memory and optimal associative mappings, the learning subspace method, the self-organizing feature maps (SOMs), the learning vector quantization (LVQ), novel algorithms for symbol processing like the redundant hash addressing, dynamically expanding context and a special SOM for symbolic data, and a SOM called the Adaptive-Subspace SOM (ASSOM) in which invariant-feature filters emergence.

SOLID principles (plus DRY, YAGNI, KISS and other YAA) ~ Siderite's Blog Intro I want to talk today about principles of software engineering. Just like design patterns, they range from useful to YAA (Yet Another Acronym). Usually, there is some guy or group of people who decide that a set of simple ideas might help software developers write better code. This is great! Some are very simple and not worth exploring too much. If you really want to fill your head with principles for software engineering, take a look at this huge list: ⚓List of software development philosophies. But what I wanted to talk about was SOLID, which is so cool that not only does it sound like something you might want your software project to be, but it's a meta acronym, each letter coming from another: S - SRPO - OCPL - LSPI - ISPD - DIP OK, I was just making it look harder than it actually is. ⚓Single Responsibility The idea is that each of your classes (or modules, units of code, functions, etc) should strive towards only one functionality. Short example: ⚓Open/Closed This one is simple.

Kohonen network Figure 1: The array of nodes in a two-dimensional SOM grid. The Self-Organizing Map (SOM), commonly also known as Kohonen network (Kohonen 1982, Kohonen 2001) is a computational method for the visualization and analysis of high-dimensional data, especially experimentally acquired information. Introduction The Self-Organizing Map defines an ordered mapping, a kind of projection from a set of given data items onto a regular, usually two-dimensional grid. A modelm_i is associated with each grid node ( Figure 1). These models are computed by the SOM algorithm. Like a codebook vector in vector quantization, the model is then usually a certain weighted local average of the given data items in the data space. History The SOM algorithm grew out of early neural network models, especially models of associative memory and adaptive learning (cf. Figure 2: Left image: Models of acoustic spectra of Finnish phonemes, organized on an SOM. Mathematical definition of the SOM Software packages References

Related: