In response to the intense business competition, rapid changes in the response to be non-stop demand for and use information systems to support business operations. Information systems development life cycle, requirements analysis phase is the most difficult to plan with the audit steps, so the effective demand analysis software project outputs will be the key to success. This study for the business information systems requirements analysis and validation process improvement studies to the case company information systems requirements analysis approach for analysis. To explore the requirements process often face the problem of the current situation and to cause analysis, and choose to CMMI Requirements Development and Requirements Management flow field as a guide, the recommended reference to CMMI specific goals and specific implementation method is proposed for the case company information system requirements process improvement recommendations aimed at improving the information system needs of the case company to work quality and output of current problems, and to provide general enterprise information system requirements into CMMI process improvement reference. For enterprises want to import the CMMI, but also needs to provide their requirements management process development and implementation of the field of reference.

Ever since the early 90¡¦s the global software market has been growing at a rapid speed. Along with the development of Internet and electronic commerce, the demands for software have been increased dramatically and Taiwanese software firms are encountered serious global competition too. To stay competitive, the Taiwan software industry has to improve the quality of its software products in order to compete in the international IT arena. The present best option is for the Taiwanese software firms to achieve the Software Engineering Institute¡¦s Capability Maturity Model certification. This study compares the major differences on the requirement management process between CMMI level II and level III. The differences include key process¡¦s purpose, activity, and artifact. Two real-word cases were used to illustrate the example and concept. These results provide a practical bases and better understanding for the Taiwanese software firms when they implement CMMI level II or III.

Background: Technical debt(TD) is incurred when developers accept compromises in a system in one dimension to meet urgent demand in some other dimensions (e.g., a deadline). If technical debt is not managed correctly, it will cause hidden danger to software’s long term success. It does not get enough attention when TD applies to the requirements engineering. Objectives: In this study, we investigate the current state of requirements debt(ReD). We aim to give a precise definition of ReD. We also focus on the factors that can induce ReD in the requirement engineering and requirement management process. Moreover, we want to summarize the measurement tools to detect and locate the ReD. Finally, we try to find approaches and ideas to manage ReD. Methods: We conducted a systematic mapping study (SMS) and a survey for all of the objectives. When performing the systematic mapping study, we applied snow- balling method to ensure we find related and enough papers. Results: According to the analysis and results of SMS and the survey, we concluded the definition of requirements debt. We also presented and classified 54 ReD induced factors into 8 categories. 10 ReD measurement techniques searched from literatures were listed with a brief description for each one, suggestions from software practi- tioners on ReD detection also gathered and displayed. The management techniques and theoretical suggestions were presented based on related factors. Conclusions: From research result, we find academia and industry lay different emphasises on how to manage ReD. To stimulate Industry pay more attention on control and manage ReD effectively, this paper calls for the two sides to work on the same point.

Várias ferramentas de desenvolvimento utilizam mecanismos para centralizar/gerenciar código compartilhado entre diferentes desenvolvedores ou equipes de desenvolvimento. Estes repositórios geralmente deixam muito a desejar em relação aos serviços que oferecem, não só aos desenvolvedores, mas também aos usuários de sistemas já desenvolvidos, que desejam ter atualizações e correções constantes em seus aplicativos. Surge então a necessidade de disponibilizar esses recursos em um ambiente de trabalho realmente cooperado. Este trabalho propõe a modelagem de um repositório de componentes de software, formado por uma área de armazenamento centralizada comum aos desenvolvedores, e com capacidade de gerenciar componentes e agregar serviços extras, administrando seu ciclo de vida de modo integrado. Para tal, várias tecnologias baseadas em Java foram integradas, tais como as seguintes API's: Enterprise Java Beans (EJB), Java Naming and Directory Interface (JNDI), Remote Method Invocation (RMI), Java Messaging Service (JMS), Java Transaction (JTA), Java Transaction Service (JTS) e Java Database Connection (JDBC).Para que o modelo aqui proposto possua um nível de funcionalidade adequado, são fornecidos vários serviços pelo repositório, atendendo assim às expectativas tanto de desenvolvedores, como dos usuários finais. Dentre outros, são providos os seguintes serviços: Serviço de Descrição, Serviço de Histórico, Serviço de Controle de Versões, Serviço de Teste OO, Serviço de Padrões de Projeto e Serviço de Invalidação de Componentes. / Software development tools commonly use mechanisms for storing/managing code shared among different developers or development teams. These repositories generally are very poor in relation to the services they provide to developers and also to the users of already developed systems which need to make constant updates and corrections on their applications. There is a need to supply supporting services to software integration through a really cooperated development environment. This work considers the modeling of a software component repository comprising a common storage area to be accessed by developers, possessing capacity to manage components and to add extra services, and managing the development life cycle in an integrated mode. To accomplish this model, some technologies based on Java have been integrated, namely: Enterprise Java Beans (EJB), Java Naming and Directory Interface (JNDI), Remote Method Invocation (RMI), Java Messaging Service (JMS), Java Transaction (JTA), Java Transaction Service (JTS) and Java Database Connection (JDBC). For the model considered here to have an adjusted level of functionality, some repository services are supplied so assuring the expectations of developers and final users. Among the services provided, the following must be mentioned: Description Service, History Service, Version Control Service, OO Test Service, Design Patterns Service and Components Invalidation Service.

Várias ferramentas de desenvolvimento utilizam mecanismos para centralizar/gerenciar código compartilhado entre diferentes desenvolvedores ou equipes de desenvolvimento. Estes repositórios geralmente deixam muito a desejar em relação aos serviços que oferecem, não só aos desenvolvedores, mas também aos usuários de sistemas já desenvolvidos, que desejam ter atualizações e correções constantes em seus aplicativos. Surge então a necessidade de disponibilizar esses recursos em um ambiente de trabalho realmente cooperado. Este trabalho propõe a modelagem de um repositório de componentes de software, formado por uma área de armazenamento centralizada comum aos desenvolvedores, e com capacidade de gerenciar componentes e agregar serviços extras, administrando seu ciclo de vida de modo integrado. Para tal, várias tecnologias baseadas em Java foram integradas, tais como as seguintes API's: Enterprise Java Beans (EJB), Java Naming and Directory Interface (JNDI), Remote Method Invocation (RMI), Java Messaging Service (JMS), Java Transaction (JTA), Java Transaction Service (JTS) e Java Database Connection (JDBC).Para que o modelo aqui proposto possua um nível de funcionalidade adequado, são fornecidos vários serviços pelo repositório, atendendo assim às expectativas tanto de desenvolvedores, como dos usuários finais. Dentre outros, são providos os seguintes serviços: Serviço de Descrição, Serviço de Histórico, Serviço de Controle de Versões, Serviço de Teste OO, Serviço de Padrões de Projeto e Serviço de Invalidação de Componentes. / Software development tools commonly use mechanisms for storing/managing code shared among different developers or development teams. These repositories generally are very poor in relation to the services they provide to developers and also to the users of already developed systems which need to make constant updates and corrections on their applications. There is a need to supply supporting services to software integration through a really cooperated development environment. This work considers the modeling of a software component repository comprising a common storage area to be accessed by developers, possessing capacity to manage components and to add extra services, and managing the development life cycle in an integrated mode. To accomplish this model, some technologies based on Java have been integrated, namely: Enterprise Java Beans (EJB), Java Naming and Directory Interface (JNDI), Remote Method Invocation (RMI), Java Messaging Service (JMS), Java Transaction (JTA), Java Transaction Service (JTS) and Java Database Connection (JDBC). For the model considered here to have an adjusted level of functionality, some repository services are supplied so assuring the expectations of developers and final users. Among the services provided, the following must be mentioned: Description Service, History Service, Version Control Service, OO Test Service, Design Patterns Service and Components Invalidation Service.

Várias ferramentas de desenvolvimento utilizam mecanismos para centralizar/gerenciar código compartilhado entre diferentes desenvolvedores ou equipes de desenvolvimento. Estes repositórios geralmente deixam muito a desejar em relação aos serviços que oferecem, não só aos desenvolvedores, mas também aos usuários de sistemas já desenvolvidos, que desejam ter atualizações e correções constantes em seus aplicativos. Surge então a necessidade de disponibilizar esses recursos em um ambiente de trabalho realmente cooperado. Este trabalho propõe a modelagem de um repositório de componentes de software, formado por uma área de armazenamento centralizada comum aos desenvolvedores, e com capacidade de gerenciar componentes e agregar serviços extras, administrando seu ciclo de vida de modo integrado. Para tal, várias tecnologias baseadas em Java foram integradas, tais como as seguintes API's: Enterprise Java Beans (EJB), Java Naming and Directory Interface (JNDI), Remote Method Invocation (RMI), Java Messaging Service (JMS), Java Transaction (JTA), Java Transaction Service (JTS) e Java Database Connection (JDBC).Para que o modelo aqui proposto possua um nível de funcionalidade adequado, são fornecidos vários serviços pelo repositório, atendendo assim às expectativas tanto de desenvolvedores, como dos usuários finais. Dentre outros, são providos os seguintes serviços: Serviço de Descrição, Serviço de Histórico, Serviço de Controle de Versões, Serviço de Teste OO, Serviço de Padrões de Projeto e Serviço de Invalidação de Componentes. / Software development tools commonly use mechanisms for storing/managing code shared among different developers or development teams. These repositories generally are very poor in relation to the services they provide to developers and also to the users of already developed systems which need to make constant updates and corrections on their applications. There is a need to supply supporting services to software integration through a really cooperated development environment. This work considers the modeling of a software component repository comprising a common storage area to be accessed by developers, possessing capacity to manage components and to add extra services, and managing the development life cycle in an integrated mode. To accomplish this model, some technologies based on Java have been integrated, namely: Enterprise Java Beans (EJB), Java Naming and Directory Interface (JNDI), Remote Method Invocation (RMI), Java Messaging Service (JMS), Java Transaction (JTA), Java Transaction Service (JTS) and Java Database Connection (JDBC). For the model considered here to have an adjusted level of functionality, some repository services are supplied so assuring the expectations of developers and final users. Among the services provided, the following must be mentioned: Description Service, History Service, Version Control Service, OO Test Service, Design Patterns Service and Components Invalidation Service.

Software development is an iterative process which is based on teamwork and information exchange. In order to keep this process running, proper informational flow control techniques in a software development company have to be applied. As number of employees grows, manual control of this process becomes inaffective and automated solutions takes over this task. The most common informational units in the software development process are defects, new features and requirements. This paper addresses problems that occur during software development process and intents to create techniques and methodologies for software defect, feature and requirement management. Following tasks are performed while automating mentioned process: a) Analysis of software development company workflow; b) Design and documentation of software defect, feature and requirement management method, which would ease information exchange in design, implementation and quality assurance stages of software development process; c) Analysis and comparision of existing similar solutions. Identification of most attaractive and useful features; d) Design and implementation of software defect, feature and requirement management system which covers newly designed information flow control method. Practical task includes designing, programming, installing and testing newly created system. Design and development is based on reusable component approach which results in several layers of reusable code.

Reikalavimų inžinerija yra bene svarbiausias etapas informacinės sistemos kūrime. Tik tikslus reikalavimų specifikavimo proceso valdymas leis sėkmingai projektuoti, realizuoti ir įdiegti informacines sistemas kompiuterizuojamose srityse. Dažnai neefektyvus reikalavimų rinkimo procesas tampa projekto nesėkmės ar programinės įrangos defekto pagrindu. Be to, aptiktų netikslumų pašalinimo kaina kyla eksponentiškai, kai jie atrandami vėlyvosiose projekto stadijose. Todėl įmonės ar asmenys, siekiantys pagerinti projekto kokybę ir produktyvumą, turėtų ypatingai atkreipti dėmesį į reikalavimų valdymo procesą. Pastebėta, jog reikalavimų specifikavimo procesas vis labiau kompiuterizuojamas, o reikalavimų valdymo įrankių bei šablonų naudojimas gerina reikalavimų specifikacijos ir būsimo produkto kokybę. Šis magistrinis darbas yra skirtas reikalavimų specifikavimo šablonų pagrindu eksperimentiniam tyrimui ir jo vertinimui. / The usage of computers takes more important place in our modern life. It was noticed that more and more enterprises use requirement management tools and specification templates to increase quality of requirement specification and projects. Very often ineffective requirements-gathering processes are the source of project failures and software defects. In addition, the cost of fixing defects rises exponentially as their discovery occurs later in the development process. However, a solid requirements process is fundamental to an effective overall process, and companies seeking increased quality and productivity should start with the requirements process. The intention of this work is to make the experimental research of requirements specification using templates and evaluate it.

Product development is affected by uncertainties due to changing customer requirements, changing regulations, technological developments, long lead times, high product complexities, and geopolitical issues. Automation, increased flexibility of production, and reduced lead times are drivers that allow product development to be competitive in this scenario. Design engineers should be aware of production capabilities to facilitate early producibility assessments and to avoid late changes. Production preparation is identified as an important activity in the product development process, whereby the producibility of a product is assessed. In this thesis, the current state of production preparation during product development is investigated and a method is introduced supporting production preparation using production requirements. The work was carried out using the design research methodology framework and comprised four studies based on the four steps of the framework. The research clarification and descriptive study 1 phases aimed at developing understanding and were done by means of data collection at the companies through interviews and document studies. The next two steps were prescriptive study and descriptive study 2, which aimed at developing and evaluating the support. This was done through observation, workshops, and solution development. The production preparation process is supported by Design for Manufacturing and Assembly, failure mode and effects analysis, lesson-learnt documents, and computer-aided design, and the efficiency of the process is dependent on individual skills and knowledge. Tools to support common understanding, remove ambiguity in requirements, and enable collaboration between design and production engineers are needed. The developed method allows for the identification, definition, structuring, and sharing of production requirements, aligning with varying maturities of product and production systems during product development. This helps improve the collaboration between design and production engineers for production preparation.

Hållbarhet är ett brett begrepp som kan definieras på många olika sätt. I denna rapporten undersöks hållbarhet utifrån produktens perspektiv, med avseende på produktutvecklingsprocessen. Mer specifikt är det sättet som man arbetar och tar beslut på i produktutvecklingsprojekt med avseende på produktens hållbarhet som står i centrum. Två företag som sysslar med farkoster analyseras i rapporten, där det ena företaget arbetar med utveckling av vägfordon och det andra med komponenter till flygplansmotorer. Metodiken bakom arbetet består av en litteraturstudie samt en intervjustudie där två respondenter från respektive företag intervjuas med hjälp av en förberedd intervjuguide.  Resultatet av intervjustudien presenteras sedan, uppdelat i olika teman som är relaterade till hållbarhet. Dessa teman diskuteras sedan i relation till den teoretiska referensramen. Resultaten av rapporten var till stor del överensstämmande med litteraturstudien och då båda företagen är involverade med farkoster som använder fossila bränslen uppstod flera likheter i deras hållbarhetskravshantering. Ett exempel på detta är bland annat när i produktutvecklingsprocessen identifiering av hållbarhetskrav sker. Aspekter som beslutsprocessen, hanteringen, ansvaret och utvärderingen av hållbarhetskrav visade sig vara komplicerade, och även fast teorin gick att applicera på mycket var det inte ovanligt att frågor kring dessa områden inte hade något definit svar. För vidare forskning föreslås exempelvis en djupare analys av produktutveckling av produkter med lång livslängd och hur detta samspelar med hållbarhet för produkten. Även återkommande begrepp i rapporten som livscykelperspektiv är rekommenderade aspekter av hållbarhet för vidare forskning kring, då detta framstod som relativt nytt i respektive betraktat företag. / Sustainability is a broad concept that can be defined in many different ways. In this report sustainability is examined from the product's perspective, with respect to the product development process. Specifically, it is the way that companies work and make decisions in product development projects in regards to the product's sustainability that is the central subject. Two companies that work with vehicles were analyzed in the report, where the first company works with the development of road vehicles and the second company works with the development of components for jet engines. The method behind this report consists of a literature study and an interview study where two respondents from each company are interviewed with the help of a prepared interview guide. The results of the interview study were then presented, and divided into different categories related to sustainability. These  categories were then discussed in relation to the literature study. The results of the report were in large part in agreement with the literature study, and because both companies are involved in the development of different types of vehicles that use fossil fuel there were several similarities related to their sustainability requirement management. One example of this is the identification process of requirements and at what point identification occurs. Aspects such as decision making, the handling, the responsibility and evaluation of sustainability requirements proved to be complicated, and even though the established literature study was applicable it was common that questions regarding these topics did not have definite answers. For further research it is recommended that for example a deeper analysis of long product development cycles is made and how this relates to the sustainability work in the development process. Also, recurring terms as "life cycle assessment" are recommended for further research since this was something that was relatively new to both companies.