Selected Aspects Related to Pre-development Stages of International Software projects. Case of Finland and Russia

The question of Pilot Project creation, due to support pre-development stage of software product elaboration, nowadays might be used as an approach, which allows improving the whole scheme of information technology project running. This subject is not new, but till now no model has been presented, which gives deep description of this important stage on the early phase of project. This Master's Thesis represents the research's results and findings concerning the pre-development study from the Software Engineering point of view. The aspects of feasibility study, pilot prototype developments are analyzed in this paper. As the result, the technique of Pilot Project is formulated and scheme has been presented. The experimental part is focused on particular area Pilot Project scheme's implementation- Internationally Distributed Software projects. The specific characteristic, aspects, obstacles, advantages and disadvantages are considered on the example of cross border region of Russia and Finland. The real case of Pilot Project technique implementation is given.

Clean development mechanism and joint implementation in China and Russia as related to industrial energy projects

Being highly discussed the problem of climate change and global warming has been keeping importance for several of decades. As a response to the world’s need in solution for climate change disasters, the United Nations Framework Convention on Climate Change was adopted in 1992 and supplemented with the Kyoto protocol in 1997. This work is aimed to give better understanding of the Convention, Kyoto Protocol with its mechanisms and their function, related to energy projects in such case countries, as Russia and China, in order to assist evaluation of projects cost-effectiveness. It provides basic information about the Convention and the Protocol with their regulations, overview of present situation and future post-Kyoto forecasts, while the most attention is concentrated on the clean development mechanism and joint implementation step-by-step project cycles and specific regulations in given countries. The current study disclosed that CDM and JI project cycles are resulting in a complicated process. By the moment it requires step-by-step following of a number of methodologies, spending time and finance to particular project development. Uncertainties about post-Kyoto period bring additional risk to the projects and complicate any business decision concerning Kyoto Protocol.

Mapping the translation needs and practices in development co-operation projects of NGOs

Tämän pro gradu -tutkielman aiheena on kääntäminen ja viestintä vieraalla kielellä Suomen ulkoasiainministeriön rahoittamissa kansalaisjärjestöjen kehitysyhteistyöhankkeissa. Tutkielman on tarkoitus kartoittaa kyseisten kehitysyhteistyöhankkeiden kääntämiseen ja vieraskieliseen viestintään liittyviä tarpeita ja -käytäntöjä. Aihetta ei ole tutkittu laajasti muutoin, joten empiirinen osuus on erityisen merkittävässä roolissa. Tutkielman alussa esitellään ulkoasiainministeriön laatimia suomalaisten kansalaisjärjestöjen kehitysyhteistyöhankkeiden ehtoja ja ohjeita, jotka ovat kyseiselle tutkimukselle olennaisia. Tutkielman teoreettinen osuus koostuu lähinnä metodologisesta pohdinnasta, koska aiempaa tutkimustietoa on vähän. Tutkimusmetodien analysointia on painotettu myös siksi, että empiirisellä osuudella on niin suuri merkitys. Tutkielman empiirinen aineisto on yhtäältä peräisin tutkijan havainnoista, jotka saatiin omia varhaisempia hankehallinnointikokemuksia hyödyntäen sekä osallistuvan havainnoinnin menetelmää käyttäen kahden opiskelijajärjestön kehitysyhteistyöhankkeista vuosien 2009 ja 2012 välisenä aikana. Toisaalta aineisto on kerätty kyselytutkimuksen vastauksista. Kysely lähetettiin 35 suomalaiselle kansalaisjärjestölle, joiden kehitysyhteistyöhankkeita Suomen ulkoasiainministeriö rahoittaa. Järjestöt valittiin satunnaisotannalla. Empiirisen aineiston analyysistä ilmeni muun muassa, että tutkijan alkuperäinen hypoteesi kehitysyhteistyöhön liittyvien tekstien kääntämisen yleisyydestä pitää osittain paikkansa, vaikka tekstejä käännettiinkin kansalaisjärjestöissä vähemmän kuin tutkija odotti. Tutkimusaineisto ei ole kuitenkaan tarpeeksi laaja, jotta tuloksia voitaisiin yleistää, sillä kansalaisjärjestöt, niiden hankkeet, käännöstarpeet ja asiantuntemus osoittautuivat odotetusti hyvin erilaisiksi. Tulokset sisältävät asiaa myös esimerkiksi järjestöissä kääntävien ja vieraalla kielellä viestivien taustoista. Jatkotutkimukset ovat kuitenkin tarpeen, ja mahdollisia tutkimusaiheita on runsaasti.

Development of Piping Stress Analysis Guideline for Neste Jacobs' Projects

The aim of this research was to develop a piping stress analysis guideline to be widely used in Neste Jacobs Oy’s domestic and foreign projects. The company’s former guideline to performing stress analysis was partial and lacked important features, which were to be fixed through this research. The development of the guideline was based on literature research and gathering of existing knowledge from the experts in piping engineering. Case study method was utilized by performing stress analysis on an existing project with help of the new guideline. Piping components, piping engineering in process industry, and piping stress analysis were studied in the theory section of this research. Also, the existing piping standards were studied and compared with one another. By utilizing the theory found in literature and the vast experience and know-how collected from the company’s employees, a new guideline for stress analysis was developed. The guideline would be widely used in various projects. The purpose of the guideline was to clarify certain issues such as which of the piping would have to be analyzed, how are different material values determined and how will the results be reported. As a result, an extensive and comprehensive guideline for stress analysis was created. The new guideline more clearly defines formerly unclear points and creates clear parameters to performing calculations. The guideline is meant to be used by both new and experienced analysts and with its aid, the calculation process was unified throughout the whole company’s organization. Case study was used to exhibit how the guideline is utilized in practice, and how it benefits the calculation process.

Development of Project Logistics in Engineering, Procurement and Construction Projects

The aim of this Master’s Thesis is to develop project logistics functions in large scale en-gineering, procurement and construction projects. The background of the research topic is compounded from two separate subjects; OPAL Program and case study of an actual EPC project. The purpose is to examine Project Logistics process in accordance with OPAL Program as well as logistics process in focus EPC project. Both entities are researched by using the case study research methodology. Logistics process of the focus EPC project is described as well as presented and in addi-tion, logistics related findings and observations are introduced. Significant findings and observations are found from logistics costs as well as shipment volume estimations in the early phase of the focus ECP project. A notable finding is also that because goods were transported as readily assembled as possible it caused expensive oversized cargo deliveries. From findings and observation of the focus EPC project it can be derived that logistics has to be involved in the early sales phase in order to receive more accurate logistics cost esti-mations for project deliveries. It is also noticed that in order to obtain savings in logistics costs, oversized deliveries must be avoided.

The Development of Weak Signal Concept

Tämän hetken trendit kuten globalisoituminen, ympäristömme turbulenttisuus, elintason nousu, turvallisuuden tarpeen kasvu ja teknologian kehitysnopeus korostavatmuutosten ennakoinnin tarpeellisuutta. Pysyäkseen kilpailukykyisenä yritysten tulee kerätä, analysoida ja hyödyntää liiketoimintatietoa, jokatukee niiden toimintaa viranomaisten, kilpailijoiden ja asiakkaiden toimenpiteiden ennakoinnissa. Innovoinnin ja uusien konseptien kehittäminen, kilpailijoiden toiminnan arviointi, asiakkaiden tarpeet muun muassa vaativatennakoivaa arviointia. Heikot signaalit ovat keskeisessä osassa organisaatioiden valmistautumisessa tulevaisuuden tapahtumiin. Opinnäytetyön tarkoitus on luoda ja kehittää heikkojen signaalien ymmärrystä ja hallintaa sekäkehittää konseptuaalinen ja käytännöllinen lähestymistapa ennakoivan toiminnan edistämiselle. Heikkojen signaalien tyyppien luokittelu perustuu ominaisuuksiin ajan, voimakkuuden ja liiketoimintaan integroinnin suhteen. Erityyppiset heikot signaalit piirteineen luovat reunaehdot laatutekijöiden keräämiselle ja siitä edelleen laatujärjestelmän ja matemaattiseen malliin perustuvan työvälineen kehittämiselle. Heikkojen signaalien laatutekijät on kerätty yhteen kaikista heikkojen signaalien konseptin alueista. Analysoidut ja kohdistetut laatumuuttujat antavat mahdollisuuden kehittää esianalyysiä ja ICT - työvälineitä perustuen matemaattisen mallin käyttöön. Opinnäytetyön tavoitteiden saavuttamiseksi tehtiin ensin Business Intelligence -kirjallisuustutkimus. Hiekkojen signaalien prosessi ja systeemi perustuvat koottuun Business Intelligence - systeemiin. Keskeisinä kehitysalueina tarkasteltiin liiketoiminnan integraatiota ja systemaattisen menetelmän kehitysaluetta. Heikkojen signaalien menetelmien ja määritelmien kerääminen sekä integrointi määriteltyyn prosessiin luovat uuden konseptin perustan, johon tyypitys ja laatutekijät kytkeytyvät. Käytännöllisen toiminnan tarkastelun ja käyttöönoton mahdollistamiseksi toteutettiin Business Intelligence markkinatutkimus (n=156) sekä yhteenveto muihin saatavilla oleviin markkinatutkimuksiin. Syvähaastatteluilla (n=21) varmennettiin laadullisen tarkastelun oikeellisuus. Lisäksi analysoitiin neljä käytännön projektia, joiden yhteenvedot kytkettiin uuden konseptin kehittämiseen. Prosessi voidaan jakaa kahteen luokkaan: yritysten markkinasignaalit vuoden ennakoinnilla ja julkisen sektorin verkostoprojektit kehittäen ennakoinnin struktuurin luonnin 7-15 vuoden ennakoivalle toiminnalle. Tutkimus rajattiin koskemaan pääasiassa ulkoisen tiedon aluetta. IT työvälineet ja lopullisen laatusysteemin kehittäminen jätettiin tutkimuksen ulkopuolelle. Opinnäytetyön tavoitteena ollut heikkojen signaalien konseptin kehittäminen toteutti sille asetetut odotusarvot. Heikkojen signaalien systemaattista tarkastelua ja kehittämistyötä on mahdollista edistää Business Intelligence - systematiikan hyödyntämisellä. Business Intelligence - systematiikkaa käytetään isojen yritysten liiketoiminnan suunnittelun tukena.Organisaatioiden toiminnassa ei ole kuitenkaan yleisesti hyödynnetty laadulliseen analyysiin tukeutuvaa ennakoinnin weak signals - toimintaa. Ulkoisenja sisäisen tiedon integroinnin ja systematiikan hyödyt PK -yritysten tukena vaativat merkittävää panostusta julkishallinnon rahoituksen ja kehitystoiminnan tukimuotoina. Ennakointi onkin tuottanut lukuisia julkishallinnon raportteja, mutta ei käytännön toteutuksia. Toisaalta analysoitujen case-tapausten tuloksena voidaan nähdä, ettei organisaatioissa välttämättä tarvita omaa projektipäällikköä liiketoiminnan tuen kehittämiseksi. Business vastuun ottamiseksi ja asiaan sitoutumiseen on kuitenkin löydyttävä oikea henkilö

New Product Development (NPD) Success Factors: A Review of the Literature

This paper reviews the literature on managerially actionable new product development success factors and summarises the field in a classic managerial framework. Because of the varying quality, breadth and scope of the field, the review only contains post-1980 studies of tangible product development that are of a rigorous scientific standard. Success is interpreted as a commercial success. The field has gained insight into a broad set of factors that vary in scope, abstraction and context. Main areas that contribute to NPD success are top management support exhibited through resource allocation and communicating the strategic importance of NPD in the organisation. The right projects need to be selected for investment at the beginning of the process and should be aligned to the organisation's internal competencies and the external environment. The NPD process should use cross-functional teams and a competent project champions. Marketing research competency is crucial, as an understanding of the market, customers and competitors is repeatedly highlighted. Product launch competency was also consistently shown to be important. In terms of controlling the NPD process, strict project gates are required to maintain control.

On Effort Estimation in Software Projects

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.

Agile Methods in Small Software Projects

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.

Business Process Modeling in Software Requirements Engineering for Small and Medium Software Projects

Vaatimusmäärittelyn tavoitteena on luoda halutun järjestelmän kokonaisen, yhtenäisen vaatimusluettelon vaatimusten määrittämiseksi käsitteellisellä tasolla. Liiketoimintaprosessien mallintaminen on varsin hyödyllinen vaatimusmäärittelyn varhaisissa vaiheissa. Tämä työ tutkii liiketoimintaprosessien mallintamista tietojärjestelmien kehittämistä varten. Nykyään on olemassa erilaisia liiketoimintaprosessien mallintamiseen tarkoitettuja tekniikoita. Tämä työ tarkastaa liiketoimintaprosessien mallintamisen periaatteet ja näkökohdat sekä eri mallinnustekniikoita. Uusi menetelmä, joka on suunniteltu erityisesti pienille ja keskisuurille ohjelmistoprojekteille, on kehitetty prosessinäkökohtien ja UML-kaavioiden perusteella.

Maintenance process development for remote administration of network servers

Maintenance is a part of system development and it is possible to develop operation models for accomplishing maintenance tasks. These models can be applied to individual maintenance tasks, maintenance projects and version management. Beneficial operation models makes maintenance more effective and they assist in managing various changes. The purpose of this thesis was to develop a maintenance process which can be used to remote administer network servers. This consisted of defining those operation models and technical specifications which enable to set up, manage changes, maintain and monitor resources of information systems that are located in several different sites. At first in this thesis the needs of the process were determined and requirements were defined based on those needs. The meaning of processes in maintenance of information systems, maintenance workflows and challenges were studied. Then current practical problems and disadvantages of maintenance work were analyzed in order to focus the development to proper issues. Because available operation models did not cover all the recent needs, new maintenance process which fulfilled the requirements was developed.

Sähkösuunnittelun projektityön hallinta ja kehittäminen - Management and development of project work in electrical

Työssä on tutkittu sähkösuunnittelun projektityön hallintaa ja kehittämistä. Tavoitteena oli löytää ongelmia ja pyrkiä korjaamaan niitä, jotta suunnittelu olisi mahdollisimman toimivaa. Tutkimus perustuu kirjallisuuteen ja haastatteluihin. Työssä perehdytään kirjallisuuden avulla projektin peruskäsitteisiin ja hallintaan sekä sähkösuunnittelun projektin yleiseen toteutukseen. Haastattelujen avulla on selvitetty tämän hetkistä tilannetta sähkösuunnitteluprojektin hallinnasta ja siihen liittyvistä ongelmista Pöyryn Kouvolan konttorissa. Työn tuloksena on selvitetty merkittävimpiä ongelmia, jotka esiintyvät sähkösuunnitteluprojektissa. Työ keskittyy pääosin sähkösuunnitteluprojektin hallinnallisiin ongelmiin ja niiden toteutukseen. Kirjallisuuden ja haastattelujen pohjalta on koottu ohjeita sähkösuunnittelun projektinhallintaan

Implementing Agile Software Development Methods in a Small Organization

Currently there is a vogue for Agile Software Development methods and many software development organizations have already implemented or they are planning to implement agile methods. Objective of this thesis is to define how agile software development methods are implemented in a small organization. Agile methods covered in this thesis are Scrum and XP. From both methods the key practices are analysed and compared to waterfall method. This thesis also defines implementation strategy and actions how agile methods are implemented in a small organization. In practice organization must prepare well and all needed meters are defined before the implementation starts. In this work three different sample projects are introduced where agile methods were implemented. Experiences from these projects were encouraging although sample set of projects were too small to get trustworthy results.

Development of Collaborative Product Structure Management

The purpose of this thesis is to develop an environment or network that enables effective collaborative product structure management among stakeholders in each unit, throughout the entire product lifecycle and product data management. This thesis uses framework models as an approach to the problem. Framework model methods for development of collaborative product structure management are proposed in this study, there are three unique models depicted to support collaborative product structure management: organization model, process model and product model. In the organization model, the formation of product data management system (eDSTAT) key user network is specified. In the process model, development is based on the case company’s product development matrix. In the product model framework, product model management, product knowledge management and design knowledge management are defined as development tools and collaboration is based on web-based product structure management. Collaborative management is executed using all these approaches. A case study from an actual project at the case company is presented as an implementation; this is to verify the models’ applicability. A computer assisted design tool and the web-based product structure manager, have been used as tools of this collaboration with the support of the key user. The current PDM system, eDSTAT, is used as a piloting case for key user role. The result of this development is that the role of key user as a collaboration channel is defined and established. The key user is able to provide one on one support for the elevator projects. Also the management activities are improved through the application of process workflow by following criteria for each project milestone. The development shows effectiveness of product structure management in product lifecycle, improved production process by eliminating barriers (e.g. improvement of two-way communication) during design phase and production phase. The key user role is applicable on a global scale in the company.