Requirements management process

Vaatimustenhallinnan alue on hyvin kompleksinen. Sen terminologia on moninaista ja samat termit voivat tarkoittaa eri asioita eri ihmisille. Tämän työn tarkoituksena on selkeyttää vaatimustenhallinnan aluetta. Se vastaa kysymyksiin kuten, mitä vaatimustenhallinta on ja miten sitä voidaan tehdä. Työ keskittyy vaatimusten analysoinnin ja validoinnin alueisiin, joten tältä osin se vastaa myös tarkempiin kysymyksiin kuten, miten koottujen vaatimusten jäljitettävyyttä, dokumentointia, analysointia ja validointia voidaan tehdä. Tämän työn kautta vaatimustenhallinta voidaan esitellä yritykselle ja sen eri osat voivat saada saman käsityksen vaatimustenhallinnasta. Tutkimus esittelee vaatimustenhallinnan prosessina, joka pitää sisällään vaatimusten jäljitettävyyden, vaatimusten dokumentoinnin, vaatimusten muutoksenhallinnan ja vaatimusmäärityksen. Vaatimusmääritys voidaan edelleen jakaa vaatimusten koostamiseen, analysointiin ja neuvotteluun sekä validointiin. Työssä esitellään geneerinen vaatimustenhallinnan prosessimalli. Mallin avulla näytetään, että vaatimustenhallinta on jatkuva prosessi, jossa kaikki aktiviteetit ovat kytköksissä toisiinsa. Näitä aktiviteettejä suoritetaan enemmän tai vähemmän samanaikaisesti. Malli esitetään geneerisessä muodossa, jotta se olisi hyödynnettävissä systeemi- ja tuotekehitys projekteissa sekä sisäisissä kehitysprojekteissa. Se kertoo, että vaatimukset tulisi jalostaa niin aikaisin, kuin mahdollista, jotta muutoksien määrä kehitystyön myöhemmissä vaiheissa voitaisiin minimoida. Jotkin muutokset eivät ole vältettävissä, joten muutoksenhallinnan tueksi tulisi kehittää jäljitettävyyskäsikirja ja jäljitettävyyskäytännöt. Vaatimustenhallintaa tarkastellaan meneillään olevassa kehitysprojektissa. Tarkastelussa tutkitaan, mitä vaatimustenhallinnan toimintatapoja sekä analysointi- ja validointimetodeja käytetään ja mitä voitaisiin tehdä vaatimustenhallinnan parantamiseksi projektissa.

A Bridge Builder or a Raconteur? How Japan Manoeuvres the Global Development Discourse within the TICAD Process

Japan has been a major actor in the field of development cooperation for five decades, even holding the title of largest donor of Official Development Assistance (ODA) during the 1990s. Financial flows, however, are subject to pre-existing paradigms that dictate both donor and recipient behaviour. In this respect Japan has been left wanting for more recognition. The dominance of the so called ‘Washington Consensus’ embodied in the International Monetary Fund (IMF) and the World Bank has long circumvented any indigenous approaches to development problems. The Tokyo International Conference on African Development (TICAD) is a development cooperation conference that Japan has hosted since 1993 every five years. As the main organizer of the conference Japan has opted for the leading position of African development. This has come in the wake of success in the Asian region where Japan has called attention to its role in the so called ‘Asian Miracle’ of fast growing economies. These aspirations have enabled Japan to try asserting itself as a major player in directing the course of global development discourse using historical narratives from both Asia and Africa. Over the years TICAD has evolved into a continuous process with ministerial and follow-up meetings in between conferences. Each conference has produced a declaration that stipulates the way the participants approach the question of African development. Although a multilateral framework, Japan has over the years made its presence more and more felt within the process. This research examines the way Japan approaches the paradigms of international development cooperation and tries to direct them in the context of the TICAD process. Supplementing these questions are inquiries concerning Japan’s foreign policy aspirations. The research shows that Japan has utilized the conference platform to contest other development actors and especially the dominant forces of the IMF and the World Bank in development discourse debate. Japan’s dominance of the process is evident in the narratives found in the conference documents. Relative success has come about by remaining consistent as shown by the acceptance of items from the TICAD agenda in other forums, such as the G8. But the emergence of new players such as China has changed the playing field, as they are engaging other developing countries from a more equal level.

Project Master Document adaption in order fulfillment process

This thesis discusses adaption of new project management tool at ABB Oy Motors and Generators business unit, Synchronous Machines profit centre. Thesis studies project modeling in general and buries in the Gate Model used at ABB Synchronous Machines. It is essential to understand Gate Model because this new project management tool, called Project Master Document, is created on the base of the existing project model. Thesis also analyzes goals and structure of Project Master Document in order to ease implementation of this new tool. Project Master Document aims to improved customer order fulfillment by clearing order handover interface. Office process, especially responsibilities and target dates, become also clearer after Master Document implementation. The document is built to be frame for whole order fulfillment process including check points for each gate of project model and updated memos from all project meetings. Furthermore, project progress will be clearly stated by status markings and visualized with colors.

Software Development Process Modeling. Developers Perspective to Contemporary Modeling Techniques

Formal software development processes and well-defined development methodologies are nowadays seen as the definite way to produce high-quality software within time-limits and budgets. The variety of such high-level methodologies is huge ranging from rigorous process frameworks like CMMI and RUP to more lightweight agile methodologies. The need for managing this variety and the fact that practically every software development organization has its own unique set of development processes and methods have created a profession of software process engineers. Different kinds of informal and formal software process modeling languages are essential tools for process engineers. These are used to define processes in a way which allows easy management of processes, for example process dissemination, process tailoring and process enactment. The process modeling languages are usually used as a tool for process engineering where the main focus is on the processes themselves. This dissertation has a different emphasis. The dissertation analyses modern software development process modeling from the software developers’ point of view. The goal of the dissertation is to investigate whether the software process modeling and the software process models aid software developers in their day-to-day work and what are the main mechanisms for this. The focus of the work is on the Software Process Engineering Metamodel (SPEM) framework which is currently one of the most influential process modeling notations in software engineering. The research theme is elaborated through six scientific articles which represent the dissertation research done with process modeling during an approximately five year period. The research follows the classical engineering research discipline where the current situation is analyzed, a potentially better solution is developed and finally its implications are analyzed. The research applies a variety of different research techniques ranging from literature surveys to qualitative studies done amongst software practitioners. The key finding of the dissertation is that software process modeling notations and techniques are usually developed in process engineering terms. As a consequence the connection between the process models and actual development work is loose. In addition, the modeling standards like SPEM are partially incomplete when it comes to pragmatic process modeling needs, like light-weight modeling and combining pre-defined process components. This leads to a situation, where the full potential of process modeling techniques for aiding the daily development activities can not be achieved. Despite these difficulties the dissertation shows that it is possible to use modeling standards like SPEM to aid software developers in their work. The dissertation presents a light-weight modeling technique, which software development teams can use to quickly analyze their work practices in a more objective manner. The dissertation also shows how process modeling can be used to more easily compare different software development situations and to analyze their differences in a systematic way. Models also help to share this knowledge with others. A qualitative study done amongst Finnish software practitioners verifies the conclusions of other studies in the dissertation. Although processes and development methodologies are seen as an essential part of software development, the process modeling techniques are rarely used during the daily development work. However, the potential of these techniques intrigues the practitioners. As a conclusion the dissertation shows that process modeling techniques, most commonly used as tools for process engineers, can also be used as tools for organizing the daily software development work. This work presents theoretical solutions for bringing the process modeling closer to the ground-level software development activities. These theories are proven feasible by presenting several case studies where the modeling techniques are used e.g. to find differences in the work methods of the members of a software team and to share the process knowledge to a wider audience.

Benefits and challenges of supply chain finance business process automation : A case study in ING Bank

Supply chain finance, a financial product provided by the bank, has gained increasing attention and popularity over the last few years. Supply chain finance helps the corporate clients to optimize their financial flows along the supply chain. One characteristic of supply chain finance is that it aims to provide automated solutions. Therefore, the business process automation of supply chain finance is a very interesting and important topic for study. In this study, the business process automation of supply chain finance within the case organization, ING, is analysed. The purpose is to: (1) Identify the benefits to understand the importance to automate supply chain finance business process; (2) Find out the existing automation degree in the supply chain finance business process within the case bank to see what’s the situation now and how to improve in the future; (3) Discover the challenges in the further automation of supply chain finance business process. Firstly, the study finds out that supply chain finance business process automation can bring many benefits to the bank. Automation can improve productivity by using less time and human labour in the business process, and by providing scalable solutions. Automation can also improve quality of the service by reducing the human errors. Last but not least, automation can improve internal governance by providing enhanced visibility of the business process. Because of these potential benefits, many banks are actively seeking solutions to automate their supply chain finance business process. Then, the current automation situation with the case bank is analysed with the help of business process modelling. The supply chain finance business process within the case bank can be further divided into several sub processes: daily transaction, buyer sales and setup, supplier onboarding, contract management, customer services and supports, and contract termination. The study finds out that the daily transaction process is already a highly automated, which is carried out through the web-based trading platform. However, for other business the automation degree is relatively low. Among these business processes, supplier onboarding is most needed for further automation. Then, some solutions are also suggested to automate the supplier onboarding business process. In the end, the study also foresees some challenges during the further automation of supply chain finance business process in the case bank. Some suggestions are also given to deal with these challenges.