ODRES (output driven requirements engineering)method, which is being developed in the department of information systems comprises the following stages: separating out the context, specification of function results, specification of data sources, specification of data source processing, modelling, automatic projectionof interface of information system and prototype. While creating requirement specification, there arises a need to evaluate the quality of it. In every stage of creating requirement specification an analyst does not know if he or she has got enough information in order to do produce a working prototype of the system. Therefore, in this study the problem of information system is analysed, namely, the problem of how to hallmark the quality of ISRS? How to measure this quality? What must the IS be, so that it is of good quality? While seeking to evaluate the quality of RS, it is necessary to understant and analyse what is quality on the whole, how it is defined, how it is measured and if it is possible to measure it at all. In this study methods which are used to measure the quality and the possibilities of CASE tools to evaluate specification quality are analyzed. In the research requirements to evaluate the RS quality have also been established and the experiment that realizes the RS quality evaluation has been done.

The specification of requirements is one of the most important stages in the development of information system. The correct description is one of the principle goals in preparation of specification of requirements. Well-done specification of information system is a significant support to create software with high functionality, low maintenance and adaptation costs. Filled in document forms play an important role in the analysis of user requirements. This analysis helps to reduce the gap between the user and the system analyst. The methods of form analysis are oriented in creation of an entity relationship scheme. Information system department offering user requirements specification process of functional requirements specification method is similar to natural requirements analysis proceeding. This process begins from specification of users' requirements to incoming and out coming information. This work presents the model and prototype for specification of users' requirements to incoming and out coming information. The model is based on analysis of documents forms given by user. Method is divided into three phases: 1) user incoming and out coming information, 2) data structure analysis, 3) conceptual schema generation. The meta-model repository of requirements specification is presented. The specification process and prototype of specification of incoming and out coming information of user’s requirements are described.

Context. The requirements analysis phase, as the very beginning of software development process, has been identified as a quite important phase in the software development lifecycle. Software Requirement Specification (SRS) is the output of requirements analysis phase, whose quality factors play an important role in the evaluation work. Readability is a quite important SRS quality factor, but there are few available automated approaches for readability measurement, because of the tight dependency on readers' perceptions. Low readability of SRS documents has a serious impact on the whole process of software development. Therefore, it's extremely urgent to propose effective automated approaches for SRS documents readability measurement. Using traditional readability indexes to analyze readability of SRS documents automatically is a potentially feasible approach. However, the effectiveness of this approach is not systematically evaluated before. Objectives. In this study, firstly, we aim to understand the readability of texts and investigate approaches to score texts readability manually. Then investigate existing automated readability approaches for texts with their working theories. Next, evaluate the effectiveness of measuring the readability of SRS documents by using these automated readability approaches. Finally, rank these automated approaches by their effectiveness. Methods. In order to find out the way how human score the readability of texts manually and investigate existing automated readability approaches for texts, systematic literature review is chosen as the research methodology. Experiment is chosen to explore the effectiveness of automated readability approaches. Results. We find 67 articles after performing systematic literature review. According to systematic literature review, human judging the readability of texts through reading is the most common way of scoring texts readability manually. Additionally, we find four available automated readability assessments tools and seven available automated readability assessments formulas. After executing the experiment, we find the actual value of effectiveness of all selected approaches are not high and Coh-Metrix presents the highest actual value of effectiveness of automated readability approach among the selected approaches. Conclusions. Coh-Metrix is the most effective automated readability approach, but the feasibility in directly applying Coh-Metrix in SRS documents readability assessments cannot be permitted. Since the actual value of evaluated effectiveness is not high enough. In addition, all selected approaches are based on metrics of readability measures, but no semantic factors are blended in readability assessments. Hence studying more on human perception quantifying and adding semantic analysis in SRS documents readability assessment could be two research directions in future.

This diploma thesis deals with the areas of requirements management in large organizations, especially banks. Bank projects have their own characteristics, as well as the banking environment as such. The paper will analyze the problem of requirements management in general and during description of best practices and methodological procedures attention will be drawn to the peculiar characteristics of the banking environment. This thesis focuses mainly on methodological and personal aspects of requirements management - the role of the analyst and the requirements management methodology. One of the main goals is selection of requiremets management methodology suitable for use in banks. Other important objectives are the description of best practices and mapping of the description of requirements management in the most widely used software development methodologies. The paper can serve as a textbook for junior analysts and other team members, or as a reference guide. Well-educated analyst and knowledgeable project team members enhance probability of a successful completion of the project and objectives achievement within set deadlines, budget and to everyone's satisfaction.

There are many Information System requirement specification methods, but not much of them are related with goals. This work presents analysis of methods related with goal modelling and requirement specification. The field of this work is specification methods of goals and requirements. The object of this work is goal driven requirement specification process. The problem of the work is alignment of requirements to business goals and tracing the compliance of goals, requirements and design artefacts during development process. The main result of analysis is revealing of perspectives for extending requirement specification method with goal modelling and analysis, relating and tracing goals to requirements and software artefacts, and integration of these steps into standard unified development process. For this purpose, a UML profile was created and implemented in CASE tool “Magic Draw”. Experimental investigation of created means by applying them to IS development demonstrated the suitability of the approach. / Daugelyje organizacijų aktuali informacinių technologijų atitikimo veiklos poreikiams problema. Vienas iš būdų ją spręsti – susieti informacinių sistemų programinės įrangos reikalavimų specifikacijas su veiklos tikslais. Dėl reikiamų modeliavimo priemonių CASE įrankiuose nebuvimo tikslų modeliavimas praktiniuose kūrimo procesuose yra neatliekamas arba atliekamas tik dalinai. Planuojant informacinių sistemų projektus, tikslinga analizuoti tikslus, nes taip galima padidinti informacinių sistemų tinkamumą veiklos poreikiams. Todėl tikslais grindžiamo reikalavimų specifikavimo metodo sukūrimas yra aktuali ir novatoriška problema. Šio darbo tyrimo sritis yra tikslų ir reikalavimų specifikavimo metodai. Darbo tyrimo objektas yra tikslais grindžiamas reikalavimų specifikavimo procesas. Šio darbo tyrimo problema yra reikalavimų suderinamumas su veiklos tikslais, taip pat tikslų, reikalavimų ir juos realizuojančių artefaktų atitikimo sekimas projektavimo metu. Darbo tikslas yra sudaryti reikalavimų specifikacijos modelį, kuriame specifikacijų elementai būtų susieti tarpusavyje ir turėtų ryšį su organizacijos tikslais. Taip pat reikia pateikti priemones tikslų, reikalavimų ir artefaktų atitikimui sekti projektavimo metu. Sukurtas tikslais grindžiamų reikalavimų metamodelis ir UML profilis, realizuotas UML CASE įrankio Magic Draw DSL kūrimo priemonėmis, leidžia vaizduoti tikslus, su jais susijusius panaudojimo atvejus ir detalizuotus reikalavimus. Taikydami sudarytą metodiką... [toliau žr. visą tekstą]

Darbe pristatomas reikalavimų specifikavimo šablonais modelis. Aptariama aukštos kokybės reikalavimų proceso nauda kuriamoms sistemoms. Pateikiami išanalizuotų reikalavimų specifikacijos dokumento standartų ir reikalavimų inžinerijos programinių įrankių detalios analizės rezultatai. Pristatoma koncepcija geriau užtikrinanti reikalavimų identifikavimo ir specifikavimo kokybę - sumodeliuotas reikalavimų specifikacijos modelis, panaudojantis Volere reikalavimų surinkimo šabloną, pritaikant reikalavimų specifikavimo programinės įrangos įrankį Telelogic Doors. Sukurto prototipo pagalba, sistema automatizuoja reikalavimų surinkimo procesą, sumažindama 30 % vartotojo veiksmų, taip sudarydama didesnį vartotojo darbo našumą ir efektyvumą reikalavimų specifikavimo procese. / The main object of this thesis is to analyze requirements specification templates and requirements management tools and realize model prototype using requirements specification templates. There are analyze of requirements templates and requirements managing tools results in considering about a gain of high quality requirements process. To introduce a conception witch supports clearly requirement specification process – the model of Volere requirements specification template adopting Telelogic Doors requirements managing tool. Model realized in Doors using DXL - Doors eXtension Language. Created prototype reduce 30% of users activities and lets user to get more efficiency and productivity in requirements specification process.

This diploma thesis defines the issue of software requirements engineering and the implementation of software requirement into IS/ICT projects. One of the aims is to highlight the importance of systematic requirements management to successful IS/ICT projects. The theoretical part of thesis includes requirements definition, requirements typology and qualitative parameters of good requirement and actors, that are involved into the process of requirements management. The practical part of this thesis defines the process of requirements management general accepted methodologies of as it is specified in the internationally recognizable methodologies. Author's own contribution is the definition of a methodological process for managing requirements specifications, based on rigorous methodologies and extended to reflect author's practical experience. Methodological approach is tailored to the needs of smaller software companies and small to medium scale IS / ICT projects, and, if necessary, is further extendable. Another practical benefit of this thesis is the recommended methodology for change management requirements. Proposal process is based on the ITIL set of best practices; sub-threads are adapted to be able to meet the change management requirements and the broader business environment infrastructure. This methodology emphasizes an individual approach to the requirement. There is a recommendation of appropriate software tools for development and management requirements support divided into partial ITIL processes.

Automating test processes is becoming more and more up-to-date and one of the reasons is that manual tests are time-consuming and complicated. The aim of the study is to identify the manual test process in integration systems to see if there can be a value in automating them and which requirements can then form the basis of an automation. Pros and cons of both manual and automated tests are highlighted in the study in order to make a fair comparison between them. The advantages of the automation that has been highlighted have since, together with collected empirical data at the company Pulsen Integration, been used to produce a requirement list for automation. The study addresses whether it is worth automating all processes or whether some of the test activities work better as manual. By looking at Pulsen Integration's testing processes, one could see that some flexible processes are better as manual, while more general activities can be more easily automated. The study has had a qualitative approach and the chosen respondents from Pulsen Integration contributed with information to be able to produce a relevant list of requirements. We believe that the result presented can be generalized to companies in similar context.

Packaging have become an environmental problem since mishandling causes pollution, and end-of-life treatments contribute to climate change. Even so, packaging is still necessary in our market system as they protect, distribute and prolong the life of various products. Policy-makers, companies, and the scientific community, are therefore working on different ways to combat the negative impacts of packaging, creating frameworks and strategies to facilitate a sustainable development. However, there seems to be a misalignment in the process of developing packaging with sustainable characteristics, since the realization of sustainable packaging is limited. The aim of this study is therefore to explain the limitation of realized sustainable packaging, by exploring the misalignment in the realization process through a single case study. The empirical data was collected from a company with the ambition of realizing sustainable packaging. Primary data was gathered through open-ended interviews with employees, and through internal and public documents. Furthermore, secondary data regarding the context of sustainable packaging and also scientific studies about packaging, sustainability and product development were reviewed and analyzed. The process of realizing sustainable packaging is regarded as a system that is dependent on outputs from different levels: i) its surrounding environment- the context, ii) the system goal- the strategy, and iii) the internal rules- operational aspects. The study results in three propositions that explain how a misalignment of the different levels causes a limitation of realized sustainable packaging. P1) A misalignment between the sustainable packaging context, and the sustainability strategy, results in a strategy that points in the wrong direction, P2) a misalignment between the sustainability strategy and the requirement specification, might result in greenwashed packaging, and P3) qualitatively ill formulated sustainability requirements might result in a missed target. This study argues that in order to increase the capability of the realization process the levels need to be aligned. Also, that creating qualitatively well formulated requirements might be seen as a tool in the process of realizing sustainable packaging.

Utilization of waste as fuel for heat and power production is commonplace in Sweden, and the fossil emissions from the incineration of waste is primarily derived from the share of plastics in the fuel. Reducing the share of fossil material in the fuel should therefore lead to diminished local emissions. Alternatively, district heating with waste incineration have potential for implementation of CCS technology, that have the possibility to create negative emissions. The purpose of this study is to evaluate the potential of emission reduction and cost efficiency for three different measures that can be applied for waste incineration: sorting of waste, requirement specification and implementation of CCS technology. This was made with the case of Stockholm Exergi, a district heating actor in the Stockholm region with a desire to achieve emission reduction sufficient to offset additional emissions from a new waste incineration facility in development. The measures were compared by constructing distinct scenarios where the emissions and costs of the scenarios could be found in comparison to a reference case where no measures had been applied. For this, modelling of the properties of the waste streams used as fuel was necessary. The results showed that the capacity for sorting is not sufficient to achieve the desired levels of emission reduction on its own, while it is a cost-efficient measure. Requirement specification together with sorting can reduce the emissions to desired levels, but the required reduction of plastics in the fuel is significant. The additional quantities of waste required to produce energy at the same level as before limiting the shares of plastic results in an income from gate fees that mitigate the potential decrease in value of the gate fees brought on by requirement specification. Implementation of CCS technology would create significant negative emissions and yield overall net negative emissions for the studied facilities, but the cost of the technology would create a dependency of external incentives to keep it profitable.