Citazioni http://blogs.ugidotnet.org/rgm/category/Citazioni.aspx Citazioni it-IT Gian Maria Ricci Subtext Version 2.6.0.0 L&rsquo;importanza dei requisiti http://blogs.ugidotnet.org/rgm/archive/2010/07/24/lrsquoimportanza-dei-requisiti.aspx <p><em>I believe the hard part of building software to be the specification, design, and testing of conceptual construct, not the labor of representing it and testing the fidelity of the representation.</em></p> <p><em>The hardest single part of building a software system is deciding precisely what to build</em></p> <p><strong>The mythical man month.</strong></p> <p>L’esperienza degli anni mi fa sempre di più apprezzare questa citazione, i problemi tecnici si superano, i bug vengono corretti, le tecnologie evolvono ed aiutano, ma se non si capisce cosa si deve costruire… è tutta fatica sprecata. Per questa ragione ritengo che il successo di un progetto non può prescindere da un buon analista, figura che però è quantomeno difficile da trovare. Spendendo i miei due cents penso che un buon analista:</p> <p>1) debba capire quello che serve al cliente e non imporre le proprie scelte <br />2) debba necessariamente dialogare con i futuri utenti e fruitori del prodotto, e chiedere a loro opinioni su come vorrebbero il software <br />3) generare una documentazione molto snella dei requisiti e non generare documenti chilometrici pieni di “Fuffa” per intortare il cliente <br />4) includere il cliente nel ciclo di vita del prodotto <br />5) assumere un atteggiamento socratico “so di non sapere”</p> <p>in particolare il punto 5 è molto importante, nei processi industriali ad esempio, bisogna approcciare l’analisi sapendo di non conoscere nulla del processo, e quindi è necessario fare interviste a tutte le figure, dai manager fino agli operai che lavorano sulla catena, approcciando ogni colloquio con l’attitudine di chi non sa nulla e deve apprendere da chi ha davanti. Spesso invece si adotta un approccio del tipo “arrivo io e ti spiego come devi lavorare”, che è foriero di problemi di ogni tipo.</p> <p>alk.</p><div class="wlWriterHeaderFooter" style="text-align:left; margin:0px; padding:4px 4px 4px 4px;"><a href="http://www.dotnetkicks.com/kick/?url=http://blogs.ugidotnet.org/rgm/archive/2010/07/24/lrsquoimportanza-dei-requisiti.aspx"><img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http://blogs.ugidotnet.org/rgm/archive/2010/07/24/lrsquoimportanza-dei-requisiti.aspx&amp;bgcolor=0080C0&amp;fgcolor=FFFFFF&amp;border=000000&amp;cbgcolor=D4E1ED&amp;cfgcolor=000000" alt="DotNetKicks Image" border="0/" /></a></div><img src="http://blogs.ugidotnet.org/rgm/aggbug/98987.aspx" width="1" height="1" /> Gian Maria Ricci http://blogs.ugidotnet.org/rgm/archive/2010/07/24/lrsquoimportanza-dei-requisiti.aspx Sat, 24 Jul 2010 12:20:08 GMT http://blogs.ugidotnet.org/rgm/archive/2010/07/24/lrsquoimportanza-dei-requisiti.aspx#feedback 13 http://blogs.ugidotnet.org/rgm/comments/commentRss/98987.aspx http://blogs.ugidotnet.org/rgm/services/trackbacks/98987.aspx User Experience http://blogs.ugidotnet.org/rgm/archive/2009/08/07/user-experience.aspx <blockquote> <p>“<em>We far too often rely on developers solving User Experience problems, without thinking of the effects this could have. not many developers are skilled in this area, and the importance and value of this field is included in this capability. Usability should be a higher priority in most cases. I have seen projects that were considered failures because the user experience was too technical. …. The design was not in line with how the end user really worked, so the user interface needed a lot of rework.”</em></p> </blockquote> <p><em>Joachim Rossberg [Pro Visual Studio Team System Application Lifecycle Management]</em></p><img src="http://blogs.ugidotnet.org/rgm/aggbug/96839.aspx" width="1" height="1" /> Gian Maria Ricci http://blogs.ugidotnet.org/rgm/archive/2009/08/07/user-experience.aspx Fri, 07 Aug 2009 17:26:36 GMT http://blogs.ugidotnet.org/rgm/archive/2009/08/07/user-experience.aspx#feedback 1 http://blogs.ugidotnet.org/rgm/comments/commentRss/96839.aspx http://blogs.ugidotnet.org/rgm/services/trackbacks/96839.aspx Why Software sucks http://blogs.ugidotnet.org/rgm/archive/2008/07/29/93553.aspx <p>"...the programmers and architects and managers who develop software don't understand their customers anywhere near as well as they should, as well as designers in other industries have been forced to"</p> <p>"As with many areas of computing, user interface design is a highly specialized skill, of which most programmer knows nothing"</p> <p>"Programmers value control more than ease of use, concentrating on making complex things possible instead of making simple things simple."</p> <p>"User interface design guru Alan Cooper defines a "computer-literate user" as one who has been hurt so many times that the scar tissue is thick enough so he ho longer feels the pain"</p> <p>"The human dimension is the first problem that any security system need to solve, and very few even attempt it".</p> <p>Da <em>Why software sucks</em> di David S.Platt.</p> <p>Debbo dire che è un libro veramente carino che si fa leggere decisamente bene. Sono rimasto sorpreso anche dal fatto che c'è una lunga sessione dedicata alla sicurezza. Sicuramente un libro da leggere.</p> <p>Alk.</p> <p>Tags: <a href="http://technorati.com/tag/Why software sucks" rel="tag">Why software sucks</a> </p> <div class="wlWriterSmartContent" id="scid:C16BAC14-9A3D-4c50-9394-FBFEF7A93539:0c928d68-9fce-4b64-b4dd-3978f2e0a77b" style="padding-right: 0px; display: inline; padding-left: 0px; padding-bottom: 0px; margin: 0px; padding-top: 0px"><!--dotnetkickit--></div><img src="http://blogs.ugidotnet.org/rgm/aggbug/93553.aspx" width="1" height="1" /> Gian Maria Ricci http://blogs.ugidotnet.org/rgm/archive/2008/07/29/93553.aspx Tue, 29 Jul 2008 09:34:44 GMT http://blogs.ugidotnet.org/rgm/archive/2008/07/29/93553.aspx#feedback 2 http://blogs.ugidotnet.org/rgm/comments/commentRss/93553.aspx http://blogs.ugidotnet.org/rgm/services/trackbacks/93553.aspx Il ritmo del processo http://blogs.ugidotnet.org/rgm/archive/2008/04/29/92443.aspx <blockquote> <p>The first step toward process maturity is to define a project's rhythm. Once this rhythm is established, then and only then can the project work to keep improving the beat.</p> </blockquote> <p>Grady Booch - Managing the Object Oriented Project</p><img src="http://blogs.ugidotnet.org/rgm/aggbug/92443.aspx" width="1" height="1" /> Gian Maria Ricci http://blogs.ugidotnet.org/rgm/archive/2008/04/29/92443.aspx Tue, 29 Apr 2008 18:22:51 GMT http://blogs.ugidotnet.org/rgm/archive/2008/04/29/92443.aspx#feedback 2 http://blogs.ugidotnet.org/rgm/comments/commentRss/92443.aspx http://blogs.ugidotnet.org/rgm/services/trackbacks/92443.aspx Citazione sull’architettura http://blogs.ugidotnet.org/rgm/archive/2007/11/03/89379.aspx <p><em>The single most important determinant of the quality of a software system is its architecture. A good architecture keeps concerns of different kinds separate so that a change in one does not affect other parts of the system. ………. The architecture is manifested in an early and critical version of the system, a version that can be made executable, a version we call the <strong>architecture baseline</strong>. </em></p><p style="text-align: right">Aspect Oriented Software Development With Use Cases<br />Ivar Jacobson, Pan-Wei Ng</p><img src="http://blogs.ugidotnet.org/rgm/aggbug/89379.aspx" width="1" height="1" /> Gian Maria Ricci http://blogs.ugidotnet.org/rgm/archive/2007/11/03/89379.aspx Sat, 03 Nov 2007 15:14:19 GMT http://blogs.ugidotnet.org/rgm/archive/2007/11/03/89379.aspx#feedback 1 http://blogs.ugidotnet.org/rgm/comments/commentRss/89379.aspx http://blogs.ugidotnet.org/rgm/services/trackbacks/89379.aspx Gestione dei requisiti http://blogs.ugidotnet.org/rgm/archive/2007/10/27/89239.aspx <p>Esistono libri od articoli che talvolta contengono frasi molto interessanti e che racchiudono in poche righe grandi verità, per questa ragione ho creato nel mio blog una categoria chiamata "citazioni" in cui metterò qualche citazione. Inizio con questa presa da <em>Aspect oriented software developement with use cases </em></p><p><em>"If you want to build the correct system, you have to get the requirements correct. This does not necessarily mean thick and huge volumes of documents. You must understand the motivation behind the stated requirements, the stakeholders' concerns. And that is paramount." </em></p><p>Alk.</p><img src="http://blogs.ugidotnet.org/rgm/aggbug/89239.aspx" width="1" height="1" /> Gian Maria Ricci http://blogs.ugidotnet.org/rgm/archive/2007/10/27/89239.aspx Sat, 27 Oct 2007 10:17:12 GMT http://blogs.ugidotnet.org/rgm/archive/2007/10/27/89239.aspx#feedback http://blogs.ugidotnet.org/rgm/comments/commentRss/89239.aspx http://blogs.ugidotnet.org/rgm/services/trackbacks/89239.aspx