Spelling suggestions: "subject:"komponentinis modelisation"" "subject:"komponentinės modelisation""
1 |
Komponentinio modelio sudarymas ir naudojimas projektuojant informacijos sistemas / Creation and usage of component model in projecting information systemsUrbonas, Paulius 01 June 2004 (has links)
The purpose of this project was to create the information system, using component model. Making new information systems, often the same models are building. Realizing system with component model in creating new system it‘s possible to use the old components. To describe advantages of component model information system was created for company “Vilseda”. If the created components used in future, they have been projected according to theirs types(grafical user interface, data and function requests). In analysis and synthesis information method explored UAB “Vilseda” activity, analyse outside and inside flows, according to them created data flow diagram . In project part represented inserted and derivebled information specifications. Created system DFD, and ER diagram. Information system realized in MS Access enviroment. Formed software and hardware projects. In the project prepared and presented programme‘s user‘s and programmer‘s instructions.
|
2 |
Komponentinio IS modelio transformavimo sistema / Component - based model transformation systemAlšauskas, Žydrūnas, Kozlovskis, Linas, Mačionis, Raimondas 28 January 2008 (has links)
Kuriant informacines sistemas, tenka kurti tuos pačius sistemos komponentus, o sistemą realizuojant komponentinio modeliavimo principu, galima panaudoti jau sukurtus komponentus juos papildant, susiaurinant bei pagal poreikius koreguojant. Pagrindinis darbo tikslas - integruoti veiklos modelį ir detalų IS projekto modelį, panaudojant komponentinį sistemos projektavimo metodą. Darbe išanalizuotos Magic Draw UML 12.5 galimybės, sukurtas profailas, skirtas nubraižyti komponentinį IS modelį. Realizuota komponentinio modelio transformacijos į klasių modelį programinė įranga, sukurta MS Visual Studio .NET 2005, kuri sugeba atlikti komponentinio IS modelio transformavimą į UML klasių modelį. Atliktas eksperimentas, palygintas sukurta programine įranga sugeneruotų komponentų programinis kodas su „Magic Draw UML 12.5“ programine įranga generuotais klasių aprašais. / Presented work covers an approach to applications development based on the principles of the model-driven architecture and using the component-based system model (CBSM). The CBSM helps to refine main components and interfaces of the application at the design stage. The information system’s architecture is structured considering a business system as a set of different domains (Business, Data, Information process) with definite types of components, and with interfaces between the components of different types. Presented work is topical, when creates the same information system’s components. These components can be used and they can be modified or changed. Component - based model transformation system is created and tested with special project.
|
3 |
Komponentinio modelio taikymas gamybos apskaitos sistemos projektavime / Implementation of the component model for design of production accounting systemPetrošiūtė, Martyna 16 August 2007 (has links)
Šiame darbe ištirta ir patikslinta komponentnio modelio taikymo informacinės sistemos projektavime technologija. Esamos veiklos modelio transformavimo taisyklės papildytos naujomis taisyklėmis. Komponentinis modelis palygintas su kitu reikalavimų specifikacijos modeliu (UML notacijos Use Case modeliu) ir nustatyta, kad komponentinis modelis labiau detalizuoja architektūrinį sistemos aprašymą. Eksperimentiškai įrodyta, kad komponentinio sistemos modelio (informacinės sistemos architektūros projekto) komponentai atitinka sukurtos gamybos apskaitos sistemos programinės įrangos komponentus ir duomenų bazės objektus. / In this work was detail analysed component model and implemented for design of production accounting system. For the formation component model was appended new rules to the existing rules. Component model was compared with use case model and found, that component model is more detailed, than use case model. After detail analyse was found, that components of component model matches components of developed system and objects of database.
|
Page generated in 0.062 seconds