Made available in DSpace on 2014-06-12T15:52:27Z (GMT). No. of bitstreams: 2 arquivo3299_1.pdf: 8413271 bytes, checksum: f7e2f7602fa26d4744d748c1d3ff2002 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2009 / Conselho Nacional de Desenvolvimento Científico e Tecnológico / Documentos de requisitos tendem a ser inundados por requisitos tais como: descrições sem semântica, desnecessariamente longas e confusas, informações duplicadas, entre outros problemas. Estes problemas sintáticos diminuem a facilidade de entendimento de todo o documento de requisitos e podem prejudicar outras fases do processo de desenvolvimento do software. Avaliações de qualidade não ajudam muito se somente são baseadas em listas com qualidades desejadas. Elas devem também incorporar diretrizes para auxiliar na avaliação e melhoria dos documentos de requisitos. O processo AIRDoc surge como uma solução para avaliar e melhorar documentos de requisitos que foram descritos usando casos de uso. O processo proposto é baseado na definição de objetivos e questões que devem ser avaliadas por métricas. A qualidade dos modelos de casos de uso é melhorada com a utilização de refatorações

<p>Software metrics are a useful tool for assessing software quality and for making predictions. But currently the interpretation of the measured values is based on personal experience and gut feeling. Not much information is available about thresholds and possible ranges of the metric values. In order to be able to define thresholds on which general recommendations could be based, quantitative data has to be obtain for allowing statistical evaluations and further investigations. So far the collection of test projects requires significant manual interaction for downloading and describing metadata.</p><p>This thesis describes a process for automatically obtaining, storing and maintaining a large number of open software projects from SourceForge.NET [1]. The projects are stored in a local folder structure; the meta-data is stored in a local database. The process is automated as far as possible, repeatable, transparent, extendible and flexible.</p>

Mūsų dienomis informacinės sistemos tampa vis sudėtingesnės ir verslo procesams aprašyti seniai nebeužtenka paprastų tekstų ar schemų. Kompiuterizuotų IS reikalavimams aprašyti ir modeliuoti geriausiai tinka specialiai tam skirti modeliai. Modeliavimas tapo būtinas kuriant dideles, sudėtingas ar su kitomis sistemomis sąveikaujančias informacines sistemas, nors daugelis programuotojų siekia minimizuoti modeliavimo pastangas. Modeliuojami ne tik vartotojo poreikiai, dalykinė sritis, programinė įranga, bet ir organizacijos veikla - pastaraisiais metais ši modeliavimo fazė tapo daugelio projektavimo procesų dalimi. Todėl specialūs kompiuterizuoti modeliavimo įrankiai tapo neatskiriama sudėtingų IS kūrimo ir projektavimo dalimi. Modernėjant technologijoms vis labiau orientuojamasi į reikalavimų specifikavimo fazę IS kūrimo projektuose – reikalavimai turi lemiamą reikšmę projektuojant modernias ir sudėtingas informacines sistemas. Todėl vis didėja projektavimo įrankių įtaka IS kūrimo procese, jų pagalba kartais generuojant ir kodą. Taigi, kad tinkamai būtų sukurta ir vystoma nauja sistema, būtina tinkamai apsibrėžti viziją, veiklos modelį ir tiksliai specifikuoti reikalavimus. Šis procesas, bei veiklos modelio transformavimas į vartotojo reikalavimų sistemai modelį aptariamas šiame darbe. / In nowadays information systems are becoming more and more sophisticated and for business process definition it is not enough to use simple schemas and text. For information systems requirements there are created special models. Systems modeling became a must for creating big, sophisticated, difficult systems. User’s requirements, subject matter and specialty domain, software architecture and even organizations activities are being modeled in modern software development companies during systems design process. Special modeling tools are used to create information systems. During last few years software and business developers are focusing more to requirements specification phase. In information systems development projects strict and simply understandable requirements have critical meaning creating big sophisticated information systems. So usage of design and modeling tools is more and more popular. Using such tools sometimes program code is generated to. To develop stable system is crucial to have a vision, make good activity model and specify requirements for future system. This work covers the method of the formation of transformation between activity and use-case models. This transformation is based developing business vision and requirements to future system. The algorithm of transformation described is this work, formally defines the described models elements relations between each other. Solution, based on described algorithm was made on MagicDraw UML tool platform... [to full text]

Software metrics are a useful tool for assessing software quality and for making predictions. But currently the interpretation of the measured values is based on personal experience and gut feeling. Not much information is available about thresholds and possible ranges of the metric values. In order to be able to define thresholds on which general recommendations could be based, quantitative data has to be obtain for allowing statistical evaluations and further investigations. So far the collection of test projects requires significant manual interaction for downloading and describing metadata. This thesis describes a process for automatically obtaining, storing and maintaining a large number of open software projects from SourceForge.NET [1]. The projects are stored in a local folder structure; the meta-data is stored in a local database. The process is automated as far as possible, repeatable, transparent, extendible and flexible.

Summary Subject of this paper is workplace of employee of municipal department of economy. Main product of this paper is informational system (IS) intended for long term control of property of municipality and is related to preparation of documents concerning use of that property. Analysis and specifications concerning informational needs of municipal department of economy has been carried out. Similar systems (Sistema “BIUDŽETAS”, “Turtas”, “DEBETAS”, “ForFUND/Gov”) and methods of creating IS (creation of IS using cycle of existence of “waterfall”, method of prothotypes, JAD method, creating of IS using means of CASE) were analysed. Product was designed and realized using the following means: 1. MS Visio 2003 – designing 2. ProVision Workbench TM V 3.1 – designing 3. MS Access 2000 – DBMS for keeping data of property and use Product was introduced to employees of municipal department of economy.