747 resultados para Infrastructure Projects
Resumo:
Russian corrugated board market is rapidly developing. Owing to that Russia becomes more and more attractive to the companies ¿ world leaders in corrugated board production. Thus, in order to strengthen or even to maintain its market position the firm should uninterruptedly develop improving volume and quality of the products. At the same time operations in the Russian market are commonlyassociated with various types of risks which should be avoided. Unfortunately, the information of the Russian corrugated board market is not systematized yet there is almost no theoretical background in this areaand, therefore, the thesis is mainly based on the practical experience of the managers of Stora Enso. The goal of the paper is to define and describe the main particularities of Russian corrugated board market which are lying in different areas and to concentrate on the difficultieswith which a corrugated board factory may face while functioning in the Russian market. The contribution of the thesis consists of forming general requirements and principles while establishing a corrugated boardproduction facility and maintaining its operations in order to avoid risks, to save time and financial resources and as a result to operate in the Russian market obtaining higher profits.
Resumo:
Spain’s transport infrastructure policy has become a paradigmatic case of oversupply and of mismatch with demand. The massive expansion of the country’s transport infrastructure over the last decade has not been a response to demand bottlenecks or previously identified needs. For this reason, the intensity of use today on all interurban modes of transport in Spain falls well below that of other EU countries. This paper analyzes the institutional and regulatory factors that have permitted this policy, allowing us to draw lessons from the Spanish case that should help other countries avoid the pitfalls and shortcomings of Spanish policy.
Resumo:
Spain’s transport infrastructure policy has become a paradigmatic case of oversupply and of mismatch with demand. The massive expansion of the country’s transport infrastructure over the last decade has not been a response to demand bottlenecks or previously identified needs. For this reason, the intensity of use today on all interurban modes of transport in Spain falls well below that of other EU countries. This paper analyzes the institutional and regulatory factors that have permitted this policy, allowing us to draw lessons from the Spanish case that should help other countries avoid the pitfalls and shortcomings of Spanish policy.
Resumo:
Ohjelmistotuotteen hallinta (SCM)on tärkeä osa ohjelmistoprojekteja. Se koostuu ohjelmistotuotteen hallinnan suunnittelusta, muutoksen hallinnasta, version hallinnasta, kääntämisestä, paketoinnista, kokoonpanon tilanteen seurannasta ja sen tarkistuksesta. Ohjelmistotuotteen hallintatietokanta (SCM DB) on tarkoitettu SCM:n liittyvändatan tallettamiseen yhteen paikkaan, jossa data on kaikkien löydettävissä. SCMDB on relaatiotietokanta ja WWW-käyttöliittymä sille. Tietokantaan talletetaan SCM - infrastruktuuri, SCM -resurssit, SCM -työskentelypaikat, integrointisuunnitteludata, paketoinnin raportit ja ohjeistukset, muutoksenhallintadata ja työkalujen hallintadata. Tietokannalla on monta käyttäjää. SCM managerit tallettavat tietokantaa yleiset tiedot, Integrointimanagerit tallettavat kantaan integrointisuunnitelmaa varten julkaisua koskevat tiedot. Paketointivastuulliset tallettavat kantaan paketointiraportit. Ohj elmistosuunnittelijat tekevät muutosvaatimuksia tietokantaan, jotka muutoksenhallintaelin käsittelee. He näkevät kannan kautta myös virheraportit. Työkalujen koordinointi tapahtuu myös kantaan talletettujen tietojen avulla. Lukemiseen tietokantaa voivat käyttää kaikki testauksesta suunnittelijoihin aikataulujen osalta. Tietokannasta voidaan lukea myös paketointityökalujen tallettamia tietoja ohjelmalohkoista eri pakettiversioissa. Paketointityökalut tai paketointivastuulliset saavat kannasta myös suoraan lähdetiedon paketointityökaluille.
Resumo:
Tutkimuksen tarkoituksena on kuvata ja ymmärtää kuinka sisäisiä kehityshankkeita voidaan hallita onnistuneesti kun toimitaan nopeasti muuttuvassa ympäristössä. Tutkimus kuvailee etenkin projekteille tärkeitä menestymistekijöitä, kuten suunnittelu, kontrollointi ja päätöksenteko. Tutkimus selvittää yleisimmät ongelma-alueet case-organisaation sisäisten kehityshankkeiden hallinnassa. Tutkimus on luonteeltaan laadullinen tutkimus, jossa tutkimusmenetelmänä on käytetty tapaustutkimusta. Empiirisessa osassa käsittellään case-organisaation sisäisiä informaatioteknologia-hankkeita (IT) ja uusien konseptien kehityshankkeita (NCD). iSisäisten kehityshankkeiden erilaisuuden ymmärtäminen oli tutkimuksen tärkein tulos. Tutkimuksen empiirinen osio osoitti sen, että epävarmuudella on erittäin suuri vaikutus projektihallintaan sekä projektin kontrollointiin. Case-organisaation IT-projektien onnistuminen riippuu organisaatiomuu-toksen onnistumisesta. Asiakkaisiin ja markkinoihin liittyvät epävarmuudet ovat vaikuttavimmat NCD projektien epävarmuuksista. Näillä epävarmuuk-silla on vaikutusta projektihallintaan jonka myötä NCD projektit juuttuvat useimmiten noidankehiin tai ne lopetetaan jo aikaisessa vaiheessa.
Resumo:
Tutkielman tavoitteena on selvittää, mitkä tekijät vaikuttavat tiedon jakamiseen heterogeenisessa projektiverkostossa. Tutkielma sisältää sekä teoreettisen että empiirisen osan. Teoriaosassa käsitellään kahta pääaihetta: tiedon jakamisen verkostomaista kontekstia ja projektiverkostoon sekä sen toimijoihin liittyviä, tiedon jakamiseen vaikuttavia tekijöitä. Empiirinen osuus sisältää kvalitatiivisen haastattelututkimuksen, missä on kerätty case-projektin toimijoiden mielipiteitä niistä seikoista, jotka vaikuttavat tiedon jakamiseen projektiverkostossa. Tutkielman lopuksi kirjallisuuskatsauksen ja haastattelujen tuloksia on verrattu toisiinsa. Tutkielman tulosten perusteella voidaan todeta, että tiedon jakamiseen vaikuttavat projektiverkoston rakenne, projektikumppaneiden motivaatio, osaaminen ja resurssit, projektintarjoama tiedon jakamisen infrastruktuuri, projektin päämäärän selkeys, projektin toimintaa varten laaditut pelisäännöt, sekä projektikoordinaattorin kyky johtaa ja ohjata projektin toimintaa.
Resumo:
Integration of biological data of various types and the development of adapted bioinformatics tools represent critical objectives to enable research at the systems level. The European Network of Excellence ENFIN is engaged in developing an adapted infrastructure to connect databases, and platforms to enable both the generation of new bioinformatics tools and the experimental validation of computational predictions. With the aim of bridging the gap existing between standard wet laboratories and bioinformatics, the ENFIN Network runs integrative research projects to bring the latest computational techniques to bear directly on questions dedicated to systems biology in the wet laboratory environment. The Network maintains internally close collaboration between experimental and computational research, enabling a permanent cycling of experimental validation and improvement of computational prediction methods. The computational work includes the development of a database infrastructure (EnCORE), bioinformatics analysis methods and a novel platform for protein function analysis FuncNet.
Resumo:
Résumé: Les gouvernements des pays occidentaux ont dépensé des sommes importantes pour faciliter l'intégration des technologies de l'information et de la communication dans l'enseignement espérant trouver une solution économique à l'épineuse équation que l'on pourrait résumer par la célèbre formule " faire plus et mieux avec moins ". Cependant force est de constater que, malgré ces efforts et la très nette amélioration de la qualité de service des infrastructures, cet objectif est loin d'être atteint. Si nous pensons qu'il est illusoire d'attendre et d'espérer que la technologie peut et va, à elle seule, résoudre les problèmes de qualité de l'enseignement, nous croyons néanmoins qu'elle peut contribuer à améliorer les conditions d'apprentissage et participer de la réflexion pédagogique que tout enseignant devrait conduire avant de dispenser ses enseignements. Dans cette optique, et convaincu que la formation à distance offre des avantages non négligeables à condition de penser " autrement " l'enseignement, nous nous sommes intéressé à la problématique du développement de ce type d'applications qui se situent à la frontière entre les sciences didactiques, les sciences cognitives, et l'informatique. Ainsi, et afin de proposer une solution réaliste et simple permettant de faciliter le développement, la mise-à-jour, l'insertion et la pérennisation des applications de formation à distance, nous nous sommes impliqué dans des projets concrets. Au fil de notre expérience de terrain nous avons fait le constat que (i)la qualité des modules de formation flexible et à distance reste encore très décevante, entre autres parce que la valeur ajoutée que peut apporter l'utilisation des technologies n'est, à notre avis, pas suffisamment exploitée et que (ii)pour réussir tout projet doit, outre le fait d'apporter une réponse utile à un besoin réel, être conduit efficacement avec le soutien d'un " champion ". Dans l'idée de proposer une démarche de gestion de projet adaptée aux besoins de la formation flexible et à distance, nous nous sommes tout d'abord penché sur les caractéristiques de ce type de projet. Nous avons ensuite analysé les méthodologies de projet existantes dans l'espoir de pouvoir utiliser l'une, l'autre ou un panachage adéquat de celles qui seraient les plus proches de nos besoins. Nous avons ensuite, de manière empirique et par itérations successives, défini une démarche pragmatique de gestion de projet et contribué à l'élaboration de fiches d'aide à la décision facilitant sa mise en oeuvre. Nous décrivons certains de ses acteurs en insistant particulièrement sur l'ingénieur pédagogique que nous considérons comme l'un des facteurs clé de succès de notre démarche et dont la vocation est de l'orchestrer. Enfin, nous avons validé a posteriori notre démarche en revenant sur le déroulement de quatre projets de FFD auxquels nous avons participé et qui sont représentatifs des projets que l'on peut rencontrer dans le milieu universitaire. En conclusion nous pensons que la mise en oeuvre de notre démarche, accompagnée de la mise à disposition de fiches d'aide à la décision informatisées, constitue un atout important et devrait permettre notamment de mesurer plus aisément les impacts réels des technologies (i) sur l'évolution de la pratique des enseignants, (ii) sur l'organisation et (iii) sur la qualité de l'enseignement. Notre démarche peut aussi servir de tremplin à la mise en place d'une démarche qualité propre à la FFD. D'autres recherches liées à la réelle flexibilisation des apprentissages et aux apports des technologies pour les apprenants pourront alors être conduites sur la base de métriques qui restent à définir. Abstract: Western countries have spent substantial amount of monies to facilitate the integration of the Information and Communication Technologies (ICT) into Education hoping to find a solution to the touchy equation that can be summarized by the famous statement "do more and better with less". Despite these efforts, and notwithstanding the real improvements due to the undeniable betterment of the infrastructure and of the quality of service, this goal is far from reached. Although we think it illusive to expect technology, all by itself, to solve our economical and educational problems, we firmly take the view that it can greatly contribute not only to ameliorate learning conditions but participate to rethinking the pedagogical approach as well. Every member of our community could hence take advantage of this opportunity to reflect upon his or her strategy. In this framework, and convinced that integrating ICT into education opens a number of very interesting avenues provided we think teaching "out of the box", we got ourself interested in courseware development positioned at the intersection of didactics and pedagogical sciences, cognitive sciences and computing. Hence, and hoping to bring a realistic and simple solution that could help develop, update, integrate and sustain courseware we got involved in concrete projects. As ze gained field experience we noticed that (i)The quality of courseware is still disappointing, amongst others, because the added value that the technology can bring is not made the most of, as it could or should be and (ii)A project requires, besides bringing a useful answer to a real problem, to be efficiently managed and be "championed". Having in mind to propose a pragmatic and practical project management approach we first looked into open and distance learning characteristics. We then analyzed existing methodologies in the hope of being able to utilize one or the other or a combination to best fit our needs. In an empiric manner and proceeding by successive iterations and refinements, we defined a simple methodology and contributed to build descriptive "cards" attached to each of its phases to help decision making. We describe the different actors involved in the process insisting specifically on the pedagogical engineer, viewed as an orchestra conductor, whom we consider to be critical to ensure the success of our approach. Last but not least, we have validated a posteriori our methodology by reviewing four of the projects we participated to and that we think emblematic of the university reality. We believe that the implementation of our methodology, along with the availability of computerized cards to help project managers to take decisions, could constitute a great asset and contribute to measure the technologies' real impacts on (i) the evolution of teaching practices (ii) the organization and (iii) the quality of pedagogical approaches. Our methodology could hence be of use to help put in place an open and distance learning quality assessment. Research on the impact of technologies to learning adaptability and flexibilization could rely on adequate metrics.
Resumo:
Requirements-relatedissues have been found the third most important risk factor in software projects and as the biggest reason for software project failures. This is not a surprise since; requirements engineering (RE) practices have been reported deficient inmore than 75% of all; enterprises. A problem analysis on small and low maturitysoftware organizations revealed two; central reasons for not starting process improvement efforts: lack of resources and uncertainty; about process improvementeffort paybacks.; In the constructive part of the study a basic RE method, BaRE, was developed to provide an; easy to adopt way to introduce basic systematic RE practices in small and low maturity; organizations. Based on diffusion of innovations literature, thirteen desirable characteristics; were identified for the solution and the method was implemented in five key components:; requirements document template, requirements development practices, requirements; management practices, tool support for requirements management, and training.; The empirical evaluation of the BaRE method was conducted in three industrial case studies. In; this evaluation, two companies established a completely new RE infrastructure following the; suggested practices while the third company conducted continued requirements document; template development based on the provided template and used it extensively in practice. The; real benefits of the adoption of the method were visible in the companies in four to six months; from the start of the evaluation project, and the two small companies in the project completed; their improvement efforts with an input equal to about one person month. The collected dataon; the case studies indicates that the companies implemented new practices with little adaptations; and little effort. Thus it can be concluded that the constructed BaRE method is indeed easy to; adopt and it can help introduce basic systematic RE practices in small organizations.
Resumo:
Software engineering is criticized as not being engineering or 'well-developed' science at all. Software engineers seem not to know exactly how long their projects will last, what they will cost, and will the software work properly after release. Measurements have to be taken in software projects to improve this situation. It is of limited use to only collect metrics afterwards. The values of the relevant metrics have to be predicted, too. The predictions (i.e. estimates) form the basis for proper project management. One of the most painful problems in software projects is effort estimation. It has a clear and central effect on other project attributes like cost and schedule, and to product attributes like size and quality. Effort estimation can be used for several purposes. In this thesis only the effort estimation in software projects for project management purposes is discussed. There is a short introduction to the measurement issues, and some metrics relevantin estimation context are presented. Effort estimation methods are covered quite broadly. The main new contribution in this thesis is the new estimation model that has been created. It takes use of the basic concepts of Function Point Analysis, but avoids the problems and pitfalls found in the method. It is relativelyeasy to use and learn. Effort estimation accuracy has significantly improved after taking this model into use. A major innovation related to the new estimationmodel is the identified need for hierarchical software size measurement. The author of this thesis has developed a three level solution for the estimation model. All currently used size metrics are static in nature, but this new proposed metric is dynamic. It takes use of the increased understanding of the nature of the work as specification and design work proceeds. It thus 'grows up' along with software projects. The effort estimation model development is not possible without gathering and analyzing history data. However, there are many problems with data in software engineering. A major roadblock is the amount and quality of data available. This thesis shows some useful techniques that have been successful in gathering and analyzing the data needed. An estimation process is needed to ensure that methods are used in a proper way, estimates are stored, reported and analyzed properly, and they are used for project management activities. A higher mechanism called measurement framework is also introduced shortly. The purpose of the framework is to define and maintain a measurement or estimationprocess. Without a proper framework, the estimation capability of an organization declines. It requires effort even to maintain an achieved level of estimationaccuracy. Estimation results in several successive releases are analyzed. It isclearly seen that the new estimation model works and the estimation improvementactions have been successful. The calibration of the hierarchical model is a critical activity. An example is shown to shed more light on the calibration and the model itself. There are also remarks about the sensitivity of the model. Finally, an example of usage is shown.
Resumo:
Quality management has become a strategic issue for organisations and is very valuable to produce quality software. However, quality management systems (QMS) are not easy to implement and maintain. The authors' experience shows the benefits of developing a QMS by first formalising it using semantic web ontologies and then putting them into practice through a semantic wiki. The QMS ontology that has been developed captures the core concepts of a traditional QMS and combines them with concepts coming from the MPIu'a development process model, which is geared towards obtaining usable and accessible software products. Then, the ontology semantics is directly put into play by a semantics-aware tool, the Semantic MediaWiki. The developed QMS tool is being used for 2 years by the GRIHO research group, where it has manages almost 50 software development projects taking into account the quality management issues. It has also been externally audited by a quality certification organisation. Its users are very satisfied with their daily work with the tool, which manages all the documents created during project development and also allows them to collaborate, thanks to the wiki features.
Resumo:
The use of contextual information in mobile devices is receiving increasing attention in mobile and ubiquitous computing research. An important requirement for mobile development today is that devices should be able to interact with the context. In this paper we present a series of contributions regarding previous work on context-awareness. In the first place, we describe a client-server architecture that provides a mechanism for preparing target non context-aware applications in order to be delivered as context-aware applications in a semi-automatic way. Secondly, the framework used in the server to instantiate specific components for context-awareness, the Implicit Plasticity Framework, provides independence from the underlying mobile technology used in client device, as it is shown in the case studies presented. Finally, proposed infrastructure deals with the interaction among different context constraints provided by diverse sensors. All of these contributions are extensions to the infrastructure based on the Dichotomic View of plasticity, which now offers multi-purpose support.
Resumo:
Agile software development methods are attempting to provide an answer to the software development industry's need of lighter weight, more agile processes that offer the possibility to react to changes during the software development process. The objective of this thesis is to analyze and experiment the possibility of using agile methods or practices also in small software projects, even in projects containing only one developer. In the practical part of the thesis a small software project was executed with some agile methods and practices that in the theoretical part of the thesis were found possible to be applied to the project. In the project a Bluetooth proxy application that is run in the S60 smartphone platform and PC was developed further to contain some new features. As a result it was found that certain agile practices can be useful even in the very small projects. The selection of the suitable practices depends on the project and the size of the project team.
Resumo:
Diplomityön tavoitteena oli tutkia yksityisrahoitusmallin soveltuvuutta julkisen sektorin palvelutuotantoon sekä kuvata yksityisrahoitteisen aluerakentamishankkeen sisältö ja liiketoimintaprosessin eteneminen hankkeen ideasta konsessiosopimuksen päättymiseen asti.Huoltosuhteen muuttumisen lisäksi muuttoliike kasvukeskuksiin lisää julkisen sektorin paineita tuottaa skandinaavisen hyvinvointiyhteiskuntamme vaatimusten mukaisia palveluita. Julkinen sektori onkin ajautunut tilanteeseen, jossa vaihtoehtoina ovat sen tuottamien palveluiden supistaminen ja maksullistaminen tai tuotantomuotojen kehittäminen.Työssä esitetty yksityisrahoitteinen aluerakentamismalli mahdollistaa laadukkaiden julkisten palveluiden tuottamisen oikea-aikaisesti ja kustannustehokkaasti. Tässä uudessa aluerakentamisen mallissa yksityinen sektori rahoittaisi, rakentaisi sekä operoisi ja ylläpitäisi määräajan perinteisesti kunnalle kuuluneita infrastruktuuri- ja palveluhankkeita.Tutkimuksen keskeinen tulos on yksityisrahoitteisen aluerakentamisen liiketoimintaprosessikaavio. Liiketoimintaprosessin kuvaus edesauttaa monimutkaisen prosessin ymmärtämistä ja mahdollistaa yksityisrahoitteisen aluerakentamismallin edelleen kehittämisen sekä sen markkinoinnin julkiselle ja yksityiselle sektorille. Liiketoimintaprosessikaaviossa kuvataan prosessin osapuolet ja prosessin eteneminen julkisen ja yksityisen sektorin tarpeesta ja YIT:n liikeideasta aina alueen rakentamiseen, operointiin, ylläpitoon ja palvelutuotannon siirtoon julkiselle ja yksityiselle sektorille