• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 16
  • Tagged with
  • 16
  • 13
  • 11
  • 5
  • 4
  • 4
  • 4
  • 3
  • 3
  • 3
  • 3
  • 3
  • 3
  • 3
  • 2
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
1

Formalių metodų panaudojimas, kuriant verslo valdymo sistemas MSBS-Navision terpėje / The use of formal methods in MSBS-Navision

Tauginas, Tadas 31 May 2004 (has links)
This piece of work is dedicated to the use of formal methods in designing ERP systems in MSBS Navision environment capabilities research. Theoretical principles of formal and informal specifications and implementation peculiarities are analyzed re various specifications. UML and Z specification languages were chosen for comparison. Also MSBS Navision C/SIDE ERP system design environment is analyzed. A part of “Fixed assets” domain functionality is specified in different languages. Their clarity, precision, and implementation are compared. Formal methods (same as informal ones) have their advantages and disadvantages. UML specification is fundamentally based on graphic representation. It’s clearer, more readable, but its compatibility can’t be unambiguously verified. Z specification language has a mathematical basis. The compatibility of Z specification can be precisely verified. However, Z specification is difficult to read and learn. It’s impossible to validate the specification unambiguously neither using UML, nor Z. UML language is highly applicable for specification and design of ERP systems, because you can specify object-oriented system models using this language, and C/AL programming language is partially object-oriented. Z language specification is only useful for describing particular, sophisticated parts of the system. Z language can also be used for detailing UML specifications.
2

Veiklos modelio taikymas vartotojo reikalavimų specifikacijos generavime / Enterprise model based generation of user requirements specification

Krūgelis, Edvinas 27 June 2014 (has links)
Veiklos modelio taikymas vartotojo reikalavimų specifikacijos generavime. / Enterprice Model Based Generation of User Requirements Specification.
3

Mazuto perkrovimo proceso naftos terminale imitacinis modelis / The Simulation Model of Reloading of Oil at an Oil Terminal

Kašubienė, Vaida 10 September 2004 (has links)
The purpose of the final work is forming a simulation model of the process of reloading of oil in the oil terminal that would let make a simulation model of accepting oil products by railway to the oil terminal. In order to fulfil the purpose of the final work there were some tasks risen: a conceptual model of reloading process of oil was made, a mathematical model of reloading process of oil was made, too, an aggregate diagram of the simulation model was made an the models of the classes of the program realization were shown as well. The object of the final work is the simulation model of the process of reloading oil created in the oil terminal. Having used an object–oriented simulation system library of simulation modelling JPranas and AgDraw program, the programming realization of simulation model in Java programming system was created. The results of the final work: experiments with the created simulation model of reloading process of oil in order to find out the optimum solution have been created. The created simulation model allows changing these parameters of the model: 1. The intensity of arriving of trains at the railway station. 2. The temperature outside. During modelling the returns got for reloading oil were bring counted and, on the other hand, expenses of oil terminal for reloading oil were being counted as well. The graphic expression of the returns, the expenses and the profits showing the optimum industrial capacity of oil terminal have been presented... [to full text]
4

Sandėlių modeliavimas / Warehouses modelling

Sungaila, Marius 12 June 2008 (has links)
Šiame magistriniame darbe yra aptariama logistikos svarba prekybinėse įmonėse. Atliekamas sandėliavimo ir transportavimo, bei efektyvaus klientų užsakymų tenkinimo naudojant informacines technologijas optimizavimo tyrimas. Panašių programų analizė. Neformaliai ir formaliai Z kalba sandėlių sistemos aprašymas. Bendro prekybos centro ir sandėlio PLA modelio parengimas su agregacine schema ir koncepciniu modeliu, formalia specifikacija. Taip pat išskirtos perėjimų ir išėjimų operacijos. Vėliau bendrojo PLA modelio pritaikymas sandėlių ir prekybos centrų logistikos schemai, agregacinės schemos paruošimas. Formaliųjų Z ir PLA metodų apjungimas kuriant imitacinius modelius, bei imitacinio modelio paruošimas ir jo analizė. Z ir PLA matodų pranašumai ir trūkumai kuriant imitacinius modelius. Išvadose darbo pasiekti rezultatai. / In this graduate work is consideration about logistic importance in commercial companies. Optimization analysis about warehouse and transport functions, effeteness of clients requests using information technologies. The similar programs analysis. Not formally and formally Z language warehouse system descripting. General super market and warehouse PLA model preparation with aggregate scheme and with conceptual model and with formal specification. Also transitions and output operations. Then this general model use for super markets and warehouses and make aggregate scheme. Then integrate efficiency of logistic centres evaluated function. Formal Z and PLA metods coupling to create warehouse imitation model. In conclusion presented analysis work results.
5

Vartotojo reikalavimų specifikavimo įrankio parinkimo būdas / Requirement specification tool selection method

Visockas, Paulius 27 June 2014 (has links)
Kuriant informacines sistemas ir siekiant jas geriau pritaikyti verslui, pastaraisiais metais vis daugiau dėmesio yra skiriama vartotojų reikalavimų specifikacijai. Vartotojų reikalavimus galima specifikuoti pasinaudojus sistemos reikalavimų specifikacijos (SRS) šablonu, tačiau bet kurį SRS šabloną vis tiek reikia pritaikyti kiekvienam individualiam projektui. Šioje reikalavimų inžinerijos stadijoje susiduriama su problema, nes dar nežinant kokie bus vartotojų reikalavimai reikia pasirinkti tinkamą SRS šabloną bei programinę įrangą. Ne visi šablonai yra suderinami su individualiomis programomis ir ne visos programos pasižymi tomis pačiomis savybėmis. Kadangi šiuo metu nėra būdų, kurie padėtų išsirinkti tinkamą projektui vartotojų reikalavimų specifikacijos įrankį, šiame darbe toks būdas bus kuriamas ir aprašomas. Problemos ištyrimo lygis. Šiuo metu visos sukurtos informacinės sistemos (t.y. vartotojų reikalavimų specifikavimo (VRS) įrankiai) yra skirtos reikalavimams specifikuoti žinant specifinio projekto reikalavimus. Įrankio, kuris leistų pasirinkti tinkamą VRS įrankį, nėra. Darbo objektas: vartotojų reikalavimų specifikavimas. Darbo tikslas: sukurti būdą, kuris leistų pasirinkti tinkamą vartotojų reikalavimų specifikavimo įrankį. Siekiant užsibrėžto tikslo, yra sprendžiami tokie uždaviniai: • išnagrinėti sistemos reikalavimų specifikavimo (SRS) šablonų sudėtį; • atlikti SRS šablonų analizę, nustatyti jų savybes, privalumus bei trūkumus; • išnagrinėti vartotojų reikalavimų... [toliau žr. visą tekstą] / VISOCKAS, Paulius (2011) Requirement Specification Tool Selection Method. MBA Graduation Paper. Kaunas: Vilnius University, Kaunas Faculty of Humanities, Department of Informatics. 59 p. S U M M A R Y MBA graduation paper goal is to create a method that would allow consumers to choose the right tool for specifying requirements before knowing them. In order to achieve the goal, following tasks are solved: perform analysis of system requirements specification templates, user requirements specification tools and their compatibility with each other; develop SRS and user requirements specification tools criteria; and investigate a proposed tool with experimental data. Scientific literature, SRS templates and user requirements specification tools summary are used during analysis. The main result of this work is the proposed iVRS tool that solves the problem under investigation, since it allows choosing the exact and correct SRS template and software. This solution differs from existing solutions because it allows users to select the requirements specification tool in the pre-specification stage, where the error price is lowest. This paper also sets out SRS and user requirements specification tool criteria. Paper consists of 59 pages, 14 tables and 19 pictures.
6

Vartotojo sąsajos elementų modeliavimas informacijos srautų specifikacijos pagrindu / User Interface Elements Modeling Based on Information Flow Specification

Subačiūtė, Ieva 24 September 2004 (has links)
The target of this project was to generate a prototype, which would model the elements of the user interface based on the information flow specification. The system is programmed using MS Visual Basic for Applications, its’ graphical environment is MS Visio 2000 and the elements of GUI for modeling are taken from MS Visio 2000 stencil WUI (wui.vss). The created module allows for easy modeling of graphical user interface elements for the data source, which is selected from the database. The processing stages of the data sources are illustrated using MS Visio 2000 documents’ windows, – one window for each stage. In the database, the elements of GUI are associated with the data source processing stages they are related to, i.e. the ones that they are present in. It means, that when working with the system, after selecting the desired data source and its processing stages one wants to model, the system generates the forms with associated GUI elements. This work was being done in the order of the scientific group of Information systems design, which analyses the design of the Information systems in the wide context of requirements engineering, process and data structures specification. This designed and realized model is going to be a part of a CASE tool meant for designing computerized information systems. Once the CASE tool is finished, it is planned to use it for educational purposes in Kaunas University of Technology in the department of Information systems. It is going to... [to full text]
7

Agregatinių specifikacijų interaktyvus redagavimas ir imitacinis modeliavimas / Interactive edit of PLA specifications and simulation modeling

Bakanas, Aivaras 25 May 2005 (has links)
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.
8

Duomenų bazės schemos SQL aprašo generavimas funkcinių reikalavimų specifikacijos pagrindu / Generation SQL Definition of Database Schema Using Functional Requirements Specification

Kekys, Aleksas 27 May 2005 (has links)
The data modeling phase is one of the main phases in automated system development methods. Usually data modeling is separated as independent process which success and robustness depends largely on the intuition and experience of the data analyst. This can become problematic when IS database is being designed for large scale IS. To solve this type of problems it’s proposed to accomplish data modeling phase not as a separate, poorly with the generic modeling process connected part but as one of the fundamental system development phases. Functional Requirements Specification Method is proposed for this matter. This methods main idea is to build database model according to user requirements for the functionality of the system being developed. The purpose of this work is to present a process intended for building a entity relationship diagram from the analysed functional requirements specification metamodel and generation of the SQL DDL script (relational schema) from that model. The presented model will be implemented as one of the CASE tool modules specified for the database modeling and SQL DDL script generation. Implemented tool will be verified and it’s correctness will be experimentally approved.
9

Automatizuotas formalių PLA specifikacijų sudarymas ir interaktyvusis redagavimas / Automated creation and interactive editing of PLA specifications

Šuklevičius, Gediminas 10 July 2008 (has links)
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).
10

Vartotojo sąsajos modeliavimas duomenų srautų specifikacijos pagrindu / User Interface Design Based on the Data Flow Specification

Eidukynaitė, Vilma 29 May 2006 (has links)
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.

Page generated in 0.0393 seconds