It is notoriously difficult to define, or even to understand, the behavior of a system of interacting asynchronous processes. Improbable sequences of events that lead to errors are easily overlooked by a protocol designer. If such errors occur in practice, they will be virtually irreproducible and very hard to fix. A distinct advantage of an automated validator is that it has no preconceived notions about what is meant or what is likely in a protocol definition: it examines possibilities not probabilities. It can patiently perform the analysis for millions of cases, faster and more accurately than could ever be done by hand. An automated analysis of all reachable states in a distributed system can be used to trace obscure logical errors that would be very hard to find manually. This type of validation is traditionally performed by the symbolic execution of a finite state machine model of the system studied. The author presents an overview of existing validation techniques and methods. The implementation of Aggregate specification safety and livenes is also presented: described safety and livenes properties, algorithms and implementation. Described experiments with system, and results compared with world-famous validation system SPIN. Performance of implemented algorithms evaluated. Given some suggestions for further development of automated aggregate specification validation system.

PLA method can be used to formally specify systems. Systems specifications are written as text, what is exhaustive and understandable, but unfortunately are not visual, and user can’t quickly acquaintance with the formalized system. This article presents a way to represent aggregates specifications visually, which eases an acquaintance with specification. This article also presents a software tool to visually design formal specifications.

PLA (Atkarpomis tiesinių agregatų) formalizavimo metodas gali būti naudojamas sistemų formalių specifikacijų sudarinėjimui. Sistemų formalios specifikacijos gali būti užrašomos tekstiniu pavidalu, tačiau tai yra labai varginantis procesas, ko pasėkoje gautas rezultatas yra vaizdiniai neinformatyvus ir vartotojai negali lengvai perprasti sistemos specifikacijos. Šiame dokumente pateikiamas būdas vizualiai ir pakankamai lengvai užrašyti sistemų formalias specifikacijas naudojant PLA formalizavimo metodą. Šiame dokumente taip pat pristatomas grafinis redaktorius – sudėtingų formalių specifikacijų integruotos analizės automatizavimo sistemos posistemė, skirta agregatinių specifikacij�� kūrimui ir redagavimui. / PLA method can be used to formally specify systems. Systems specifications are written as text, what is exhaustive and understandable, but unfortunately are not visual, and user can’t quickly acquaintance with the formalized system. This article presents a way to visually and quite easily write systems specifications using PLA formalization method. This article also presents a software tool to accomplish this task. That’s graphical editor – a subsystem of a formal complex systems integrated analysis automatization system (FSA).

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ą]

The purpose of the research is to create enterprise model design method and enterprise model based method of functional user requirements acquisition, analysis and specification.

The user interface is the direct mediator between the user and the system. It is one of main factors which influences how fluently and with what time resources system could be integrated into business process and how fast systems deployment could be performed. User interface is one of the most important points in software design, because it determines quality and rate of project implementation. Software design methodologies, based on Unified Modeling Language (UML), Oracle CASE, introduced by C. Finkelstein, D. J. Anderson, V. Balasubramanian, A. Granlund, D. Lafreniere, D. Carr are analyzed in this paper. The user interface modeling method based on data flow specification is presented in this work; the software prototype of modeling user interface based on this method is implemented.

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.

In this thesis, we analyse the relationship between the hedging activities and return on equity, and the relationship between profit on hedging and other factors. Fully conditional specification is used to impute the missing values. Instrumental variable estimation and finite mixture of regression models are then used to predict the return on equity and hedging gain. We find the instrumental variable estimation is better than the OLS estimation to deal with the hedging data since it eliminates the endogeneity. By finite mixture of regression models, we show that different firms have different hedging strategies, which cause different profits in hedging. We also find the companies with large total assets prefer to hedge.

Darbo tikslas – atlikti literatūroje pateikiamų reikalavimų surinkimo ir specifikavimo metodų analizę. Pasirinkti ir pritaikyti juos CRM sistemos kūrimo procese. Pateikti kaip vyko CRM sistemos kūrimo procesas, naudojant pasirinktus metodus. Apibendrinti kaip pasirinkti metodai įtakojo sistemos funkcionalumą ir galutinius reikalavimus. Darbo pradžioje iškelta ir aprašyta problema susidariusi įmonėje, kuriančioje informacines sistemas. Pateikta, kodėl buvo priimtas sprendimas kurti naują produktą. Remiantis statistiniais duomenimis ir atliktais tyrimais aprašyta, kodėl tinkamas reikalavimų specifikavimas prisideda prie sėkmingo projekto įgyvendinimo. Literatūroje apžvelgti ir praktikoje pritaikyti reikalavimų surinkimo ir specifikavimo metodai. Aprašyti CRM sistemos kūrimo proceso etapai. Pateikta kokie metodai, kokiems funkcionalumams specifikuoti buvo naudoti projekto eigoje. Pateikta CRM sistemos reikalavimų kitimo statistika. / The aim of this work – to review the techniques of the requirements gathering and specification methods presented in the literature, to choose and adapt them to the development process of the CRM system. To show how the development process was implemented by using the selected methods and how it affected the functionality of the CRM system. At the beginning of this work there was described and analyzed the problem that arises in the company which creates information systems. It is represented a decision why a new product is chosen to establish. According to the statistical data and studies, it is described why right requirements specification contributes to the successful implementation of the project. The development process stages of the CRM system are described. Furthermore, the methods, which have been used during the project, are described in this work. The requirements change statistics of the CRM system are represented.

Följs kravspecifikationerna? I följande uppsats analyseras och granskas om producenter följer kraven i kravspecifikationen, som modeföretaget skickar med orderbeställningen. Med syfte att, genom en kvalitativ samt experimentell undersökning, komma fram till om kraven som gäller tunna trikåtröjor av mörk kulör, i modeföretagets kravspecifikation, uppfylls vid produktion. Genom kvalitativa intervjuer med kunniga inom områdena, kvalitettester, trikåmaterial, produktion utomlands och kravspecifikationer, kunde författarna få svar på om det sker att producenter bortser från krav i kravspecifikationen och varför dem troligtvis gör det. Genom en experimentell undersökning har författarna utgått från standarder i kravspecifikationen samt testat och analyserat två tröjor från 2014 års säsong med två tröjor från 2015 års säsong, för att bedöma om de skiljde sig åt, då de skall vara producerade utifrån samma kravspecifikation. I resultatet presenteras den experimentella undersökningen; hur författarna gick tillväga för att få fram det mest sanningsenliga resultatet samt citat från de kvalitativa intervjuerna. Citaten styrker författarnas spekulationer och teorier om att somliga producenter bortser från krav i kravspecifikationen. Vidare i diskussion- och analyskapitlet analyseras och diskuteras resultat med teorier och citat. De slutsatser som författarna kan dra utifrån de kvalitativa intervjuerna och den experimentella undersökningen är, att det är vanligt förekommande, att producenter medvetet väljer att bortse från vissa krav i kravspecifikationen. Dock görs det inte endast för att tjäna pengar, utan det handlar likaså om att hålla deadlines och att hålla sin kund nöjd, för att på så vis behålla relationen. Det kan också handla om olika kulturskillnader och språksvårigheter i kommunikationen där kravspecifikationerna inte är tillräckligt tydligt förklarande, vilket resulterar i att producenten får vidta åtgärder och uppskatta själv vad kunden efterfrågar. / Do the producers follow the specifications? This study analyses and reviews if producers follow the requirements of the fashion company’s specification. The purpose was to, through a qualitative and experimental research, decide if all the requirements that involve dark coloured thin knitted t-shirts, of the company's specifications are applied during the production. Through interviews with people with great knowledge within the subjects; quality controls, knitted materials, production abroad and specifications, the authors’ got answers to whether producers ignore the requirements in the specification, as well as why. Through an experimental study, following the standards in the specifications, two shirts from season 2014 and two shirts from season 2015 were examined and compared, to see if they differed. All shirts were supposed to be produced by the same specifications. In the result, the experimental study presents; how the authors proceeded to truthful results. Quotes from the qualitative interviews are also presented. The quotations prove the authors' speculations and theories, regarding the issue of some manufacturers ignoring requirements in the specifications. Furthermore, in the discussion- and analysis chapter, results are analysed together with theories and quotes. The conclusions that can be drawn from the qualitative interviews and the experimental study, is that it is a common problem. Producers deliberately choose to overlook certain requirements in the specifications. However, it is not only in order to make more money, but it is also about managing deadlines and keeping customers satisfied, in order to maintain relationships. The problem is also based on cultural differences and language difficulties in communication, where the specifications are not sufficiently clear enough, resulting in the producer must take action and appreciate what the customer wants.