It is important to evaluate and understand the state-of-art technologies to position our research and invest our energy and resources in more effective ways. Unfortunately, no systematic approach has been introduced to evaluate the maturity of technologies except a few models such as Redwine/Riddle's model (Redwine and Riddle, 1985), which does not contain a significant concept, "goals" of technologies. A new goal-oriented, technology maturity evaluation model has been proposed in this present study. The model aids to measure how a technology meets the goal of the technology along with a well-defined procedure. The model has applied to evaluate the maturity of the requirements specification technology as a case study. The results showed that this approach promoted effectiveness of measuring the technology maturity and understanding the state-of-art technology.

A system requirements specification (SyRS) defines a set of functionalities that a system is expected to fulfil. A requirement may be “it is always the case that actualFuelLevel is greater than or equal to 0” for an industrial system. Inconsistencies in a SyRS may require the system to be redesigned or reimplemented, which can drastically increase costs. With the increased size and complexity of SyRS it is important to assess new methods for verifying their correctness with respect to some criteria such as consistency. PROPAS is a tool for automated consistency checking of SyRS developed within the VeriSpec project, a cooperation between Mälardalen University, Scania and Volvo GTT. The tool is based on satisfiability modulo theories (SMT) techniques and operates on SyRS encoded in formal notation, that is timed computation tree logic (TCTL). In this thesis we extend the functionality of the PROPAS tool by implementing a type-inferencing mechanism such that variable types in SyRS can be automatically inferred. For validation, we apply the extended PROPAS tool on a set of industrial requirements. The results show that the type-inferencing mechanism can correctly infer the types of the variables from the set of requirements in most cases, while in the same time not introducing significant computational overhead to the existing solution.

Purpose: An exploration into the application of pre-requirements specification traceability (pre-RST) practices in Information Systems (IS) projects within a retail setting. Research Design/methodology: A qualitative study in the interpretivist tradition applied within a single case study setting was selected. Findings: Awareness and value-perception emerged as the most significant challenge to overcome with recommendations for a well-considered organisational change management programme to address this. The potential impact on the trust relationship amongst requirements practitioners and participants is a factor to be addressed. More readily accessible requirements engineering guides that include pre-RST as a prominent aspect is required to raise awareness levels amongst practitioners. Practical implications: The research points to a need to raise awareness amongst practitioners through improved and more readily accessible requirements engineering guides that include pre-RST as a prominent aspect. It also highlights what to consider when embarking upon pre-RST, most prominently the need for carefully considered change management programme to tackle value-perception. Originality/value: Addressing the paucity in case study insights, this research provides an understanding of practice, awareness, value-perception and perceived challenges to pre-RST. Considerations for pre-RST implementation, including careful consideration for the trust relationship amongst requirements practitioners and participants is highlighted. Limitations: The case study was limited to eleven interviews in the retail industry and therefore may not be generalisable to other industries or general practice.

Žiniomis grindžiami vartotojo reikalavimų modelių generavimas tapo vienas iš pagrindinių informacinių sistemų plėtojimo procesų. Reikalavimų specifikavimas atlieka svarbiausią vaidmenį kuriant programinę įrangą. Darbe aptariama žiniomis grindžiamas vartotojo poreikių modelio generavimo metodas. Aptarta žiniomis grindžiama sistemos architektūra. Reikalavimų modelio generavimui naudojama veiklos modelis, laikomas kaip žinių šaltinis, integruotas su reikalavimų specifikavimo modeliu sukurtu remiantis Volere šablono pagrindu. Šio darbo tikslas išanalizuoti esamų vartotojo reikalavimų įrankių privalumus ir trūkumus, bei pasiūlyti technologinį sprendimą vartotojo reikalavimų specifikacijos generavimui. Šio darbo objektas yra vartotojo reikalavimų specifikacija Darbo problema – vartotojo reikalavimų specifikavimas šiuo metu nėra grindžiamas formalizuotais kriterijais. Jeigu nesiremsime šia ideologija, tai neturėsime informacijos pilnumo, todėl reikia taikyti pasirinkto modelio struktūrą informacijos surinkimui iš vartotojo, bei kuo labiau formalizuoti Sukurtas programinis prototipas integruojant pakeistą veiklos modelį su Volere šablonu. Šis įrankis leidžia specifikuoti vartotojo reikalavimus priimant tai, kad veiklos modelis jau yra užpildytas konkrečios dalykinės srities žiniomis. Atlikus reikalavimų specifikavimą, sugeneruojama vartotojo reikalavimų specifikacija. / Knowledge based user requirements models generation became one of the basis information systems development proceses. The specification of requirements make the essential role developing the software. This paper analises knowledge based user models generation method. Also discuss knowledge based system architekture. The enterprise model is used for requirements model generation and is reputed as the knowledge source which is integrated with requirements specification model made in conformity with Volere template basis. The aim of this work is to analyse the advantages and disadvantages of existing user requirements specification tools and suggest the best technological method for the generation of user reguirements specification model. The object of this work is user requirements specification. The problem of the work is that user requirements specification is not based on formalized criterion, so in such a way we lose the fullness of information. That’s why we have to choose the model to have a structure for the information collecting from the user. The programme prototype was developed using Volere tempalate basis integrated with changed enterprise model. This tool allows to specify user requirements considering that enterprise model is filled with knowledge about exact object domain. Report is generated after requirements specification.

This work is dedicated to the requierements specification process automation issues. Main goal of the paper is to specify a conceptual model of the multy-user software requirements specification system and create a working prototype of this model. Analysis part of the work focuses on requirement specification templates and existing requirements specification software investigation. A detailed analysis of most popular templates Volere and IEEE STD 830-1998 is followed by existing software requirements specification software analysis : AnalystPRO and RequisitePRO. Requirements and tasks for the system prototype are raised on the basis of main features and weknesses of analysed requirements specification templates and software. This work presents a complete conceptual model of the software requirements specification automation. System model is based on the Volere template. Main features of the system prototype are as follows: complete independence from operating system and working environment, no any client software installation is needed, server part does not require any special components installation and is based on popular free software: Apache and MySQL Servers. System architecture is based on JAVA Applets technology. Working prototype is an implementation of main system protoype features. This is a multy-user software requirements specification environment with all main collaboration fetures: version control, document locking, presence awareness. Usability of system... [to full text]

In the early stage of building a new informational system requirement engineering involves all the processes related to the requirement system and research of problems emerged during this process. In this stage the requirements specification of corresponding information system are built. Many different notations serve for this purpose, selection of which is dependant on available resources and project goals. Requirements specification must be of good quality. It is evaluated by characteristics of quality. Specifications could be analyzed and improved by using various tools including CASE tools. The specification is developed and its quality is improved by making analysis of requirements. Well done specification is basis for creating high leveled functionality system.

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.

Context. Public procurement is an important economic factor. To protect against corruption government organizations are required to apply principles of non-discrimination and transparency for the procurement of goods such as software and of services such as software development. As a consequence, communicating requirements in software procurement has become challenging from the perspective of fairness and transparency, and also from the perspectives of system value and acceptance. Objectives. This study investigates requirements communication techniques which are being practiced in WTO-regulated tenders. The study also identifies challenges and determines the efficiency, effectiveness, and legal compliances of these techniques Methods. A systematic literature review is used to determine requirements communication approaches used in public procurement projects and the difficulties identified. This is followed by a case study to research the known requirements communication techniques used in the selected case through conducting interviews and artifact analysis. Results. The contributions are guidelines for stakeholders to select suitable techniques to communicate requirements during the procurement process. Challenges and recommendations are presented to be taken into consideration while planning software procurements. Conclusions. This study concluded that from a total of 17 requirements communication techniques, 14 have been used in the project analyzed in the case study. It is also stated by the interviewees that all of the techniques are legal to use in public procurement with the exception of one, and this is Interview. From both the literature review and the case study conducted in this research, balanced communication techniques are concluded to be most recommended since they will lead to more interaction between customers and suppliers to communicate requirements.

The main aim of this thesis is IT support of logistics in sugar refinery Cukrovary a lihovary TTD, a.s. In the first part is an introduction of the company and sugar refinery industry. The goal of second part of thesis was achieved thorough application of optimization methods of Operation research. The third part describes requirements on the new designed system. This system will support transport supervisor in his activities. The aim of this part was achieved thorough application of Unified Process methodic.

Software projects with a larger code base can be hard to maintain, and testing could therefore be a necessity. But how would one prioritize tests in their existing software project, if their project never had any tests? The purpose of this study is to find concrete steps of how to prioritize tests in a software project, independent of project type and development language. Said steps were found through two iterations of the Action Learning method. The results were found without any requirements specification, which lead to using intuition, together with code complexity, to prioritize test cases, after breaking down the project into its modules. As the study was conducted on only one specific software project, the result is limited to that specific software project until further research is conducted.