Spelling suggestions: "subject:"[een] REQUIREMENTS SPECIFICATION"" "subject:"[enn] REQUIREMENTS SPECIFICATION""
21 |
Comparative Selection of Requirements Validation Techniques Based on Industrial Survey / Jämförande Val av kravvalidering baserad på Industrial SurveySulehri, Latif January 2010 (has links)
In software engineering the requirements validation has very core importance. The requirements validation very helpful to judge that software requirements specification (SRS) is complete and free of bugs. The requirements validation is a assurance that the software requirements document is free of unwanted requirements and completely consistent. In order to remove inconsistency, detect defects and make the software requirements document fully functional the requirements validation is key factor. All possible requirements validation techniques available in academia such requirements reviews , requirements prototyping, requirements testing and viewpoint-oriented requirements validation are explained properly in this thesis report. In a very readable and understandable way the thesis presents all pros and cons of these requirements validation techniques practiced in different software companies in Sweden and available in academia. This report explains all possible advantages and issues related with these RVTs. In order to judge the best performance of these RVTs and to make their comparison I used a proper channel. I have designed a very effective survey questionnaire with the help of my colleges and literature review. To make creative comparison I conduct interviews and send survey questionnaire to different people working in requirements engineering departments in different software industries in Sweden. Finally the satisfaction levels of different software industries with these requirements validation techniques presents in this thesis report. These variables such as defect detection, time and cost are used to measure the satisfaction levels. / I Software Engineering kraven validering har en mycket central betydelse. Den kravvalidering very helpful att bedöma att Kravspecifikation (SRS) är klar och felfria. Kraven validering är en garanti för att programvaran kravdokument är fri från oönskade krav och helt konsekvent. För att undanröja inkonsekvens, upptäcka brister och göra programvaran kravdokument fullt funktionella kraven validering är viktig faktor. Alla möjliga kravvalidering tekniker inom den akademiska sådana krav recensioner, krav prototyper, provning och synpunkt-orienterade kravvalidering förklaras ordentligt i denna avhandling rapport. I ett mycket lättläst och begripligt sätt avhandling presenterar alla fördelar och nackdelar med dessa krav validera metoder praktiseras i olika mjukvaruföretag i Sverige och finns i den akademiska världen. Denna rapport förklarar alla möjliga fördelar och frågor kring dessa RVTs. För att bedöma de bästa resultaten i dessa RVTs och göra en jämförelse av dem använde jag en riktig kanal. Jag har skapat en mycket effektiv frågeformulär med hjälp av min högskolor och litteraturgenomgång. Skapa kreativa jämförelse jag intervjua och skicka frågeformuläret till olika personer som arbetar inom tekniska kraven för dessa avdelningar i olika programvaruföretag i Sverige. Slutligen tillfredsställande nivåer av olika programvaruföretag med dessa krav validering teknik presenteras i denna avhandling rapport. Dessa variabler såsom Upptäcka, tid och kostnader används för att mäta tillfredsställande nivåer. / Author: Latif Hussain Sulehri E-mail: latifsulehry@hotmail.com Phone: +46 704 917 140
|
22 |
Effektivisering av mjukvaruinstallationer : Genom automatiserad mjukvarudistribution / Making the work of installations of software more efficient : Through automated software distributionAndersson, Daniel, Edman, Glen January 2014 (has links)
Software deployment, eller mjukvarudistribution översatt till svenska kan ses som processen där alla aktiviteter ingår för att göra en mjukvara tillgänglig för användare utan en manuell installation på användarens dator eller annan maskin. Det finns ett flertal software deployment-verktyg, som hanterar automatiska installationer, tillgängliga för företag på marknaden idag. Avdelningen HVDC på ABB i Ludvika har behov att börja använda ett verktyg för automatiserade installationer av mjukvaror då installationer idag utförs manuellt och är tidsödande. Som Microsoftpartners vill ABB se hur Microsofts verktyg för mjukvarudistribution skulle kunna hjälpa för detta behov. Vår studie syftade till att undersöka hur arbetet med installationer av mjukvara ser ut idag, samt hitta förbättringsmöjligheter för installationer som inte kan automatiseras i nuläget. I studien ingick även att ta fram ett generellt ramverk för hur verksamheter kan gå tillväga när de vill börja använda sig utav software deployment-verktyg. I ramverket ingår en utformad kravspecifikation som ska utvärderas mot Microsofts verktyg. För att skapa en uppfattning om hur arbetet i verksamheten ser ut idag har vi utfört enkätundersökning och intervjuer med personal på HVDC. För att utveckla ett ramverk har vi använt oss av insamlade data från de intervjuer, enkätundersökning och gruppintervju som utförts, detta för att identifiera krav och önskemål från personalen hos ett software deployment-verktyg. Litteraturstudier utfördes för att skapa en teoretisk referensram att utgå ifrån vid utvecklande av ramverket och kravspecifikationen. Studien har resulterat i en beskrivning av software deployment, förbättringsmöjligheter i arbetet med installationer av mjukvara samt ett generellt ramverk som beskriver hur verksamheter kan gå tillväga när de ska börja använda ett software deployment-verktyg. Ramverket innehåller också en kravspecifikation som använts för att utvärdera Microsofts verktyg för mjukvarudistribution. I vår studie har vi inte sett att någon tidigare har tagit fram ett generellt ramverk och kravspecifikation som verksamheter kan använda sig av som underlag när de ska börja använda ett software deployment-verktyg. Vårt resultat av studien kan täcka upp detta kunskapsgap. / Software deployment can be seen as the process where all activities are included to make a software available to users without a manual installation on the user’s computer or other machine. There are several software deployment tools that manage automated installations available to enterprises on the market today. The department HVDC at ABB in Ludvika has needs of starting to use a tool for automated installations of software which currently is installed manually and is time consuming. As Microsoft partners ABB wants to see how Microsoft’s tool for software deployment could help for this need. Our study aimed to investigate how the department´s work with installations of software looks like today and to find opportunities for improvement for installations that can’t be automated at this time. The study also includes to develop a general framework for how businesses can proceed when they want to start using a software deployment tool. The framework also includes a designed requirement specification that will be evaluated against Microsoft´s tool. To create an idea of how the work in the business looks like today, we have performed surveys and interviews with staff in HVDC. In order to develop a framework, we have used the data collected from the interviews, questionnaires and group interviews conducted to identify requirements and wishes from the staff of a software deployment tool. Literature studies were also conducted to create a theoretical framework to use when developing the framework and the requirement specification. Our studies have resulted in a description of software deployment, opportunities for improvement in the work of software installations and a general framework that describes how businesses can proceed when they are about to start using a software deployment tool. The framework also provides a set of requirements that have used to evaluate Microsoft's tool for software distribution. In our study we have not seen that anyone before have developed a general framework and requirements specification that businesses can use as a basis when to start using a software deployment tool. Our results of the study can cover up this knowledge gap.
|
23 |
Business process-based requirements specification and object-oriented conceptual modelling of information systemsde la Vara González, José Luis 05 September 2011 (has links)
Two of the main needs when developing an information system for an
organization are that system analysts know and understand the
application domain and that the system properly supports the business
processes of the organization. Consequently, elicitation of system
requirements from business process models has been acknowledged as a
suitable activity to deal with that needs. In addition, system requirements
must be linked to subsequent development stages.
However, system analysts can face many challenges when
performing these activities. They may have problems communicating
with customer stakeholders and may need to analyse and operationalize
the purpose of the information system. Furthermore, system analysts
must bridge the gap between business and system domains for
specification of system requirements, specify different types of system
requirements and guarantee that their specification is precise, consistent
and homogeneous.
In relation to object-oriented conceptual modelling-based
information system development, system analysts must also avoid
potential problems that may arise when a conceptual schema is created
from system requirements as part of their link with subsequent
development stages. For example, a conceptual schema can be
incomplete and/or inconsistent if it is not properly managed.
As a solution, this thesis presents a methodological approach for
business process-based requirements specification and object-oriented
conceptual modelling of information systems. The approach consists of
four stages: organizational modelling, purpose analysis, specification of
system requirements and derivation of object-oriented diagrams.
By following the design research methodology for performing
research in information systems, the methodological approach has been
designed on the basis of many existing ideas and principles in academia
and industry and provides new principles, mechanisms and guidance to
address the challenges presented above. / De La Vara González, JL. (2011). Business process-based requirements specification and object-oriented conceptual modelling of information systems [Tesis doctoral no publicada]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/11445 / Palancia
|
24 |
Detecting Bad Smells in Industrial Requirements Written in Natural LanguagesMarie-Janette, Eriksson, Emma, Brouillette January 2022 (has links)
A key factor in creating software of good quality is that the requirements for the project being developed are as unambiguous and clear as possible, so the developers will be able to develop the product quickly and effectively. So, there is a need for tools that help requirements engineers create quality requirements. The attributes that define a poorly written requirement are called bad smells. In this thesis we investigate the NALABS tools bad smell detecting capabilities when analyzing industrial requirements. First, we performed a literature study to investigate what types of bad smells exist for requirements and how they were specified. After that we used a case study to examine how many smells and of what categories the NALABS tool detects, when it analyzes industrial requirements. Lastly, we used a small experiment to examine how accurately NALABS detects smells, by designing a simple console application that counted instances of bad smell words in a set of keywords that were from the NALABS tool. The results we gathered gave us an indication that NALABS detects bad smells in all the categories of bad smells that are implemented in it, to a varying degree. Through this thesis we hope to extend the knowledge about bad requirements smells, clarify what attributes of a requirement might be a bad smell, and investigate to what degree the NALABS tool can detect bad smells in industrial requirements.
|
25 |
Reikalavimų infomacinei sistemai specifikavimo veiklos taisyklių pagrindu rezultatų saugykla / Repository for the results of business rules based IS requirements specificationVyzas, Donatas 16 January 2006 (has links)
The purpose of this project was to create a requirement repository using a methodology, which is being developed in the department of Information Systems of Kaunas University of Technology. The implementation would raise the methodology to the higher level enabling its use in practice. Using the implementation one could either prove or disprove the main idea behind the methodology - the simplification of the stakeholder-analyst dialogue during the IS requirements specification. For that, the experiment was conducted. The purpose of the experiment was to specify requirements for the real-world IS using implemented requirement repository, and compare the results to other similar software.
|
26 |
Reikalavimų specifikacijos integralumo užtikrinimo metodas / A method for integrity support of requirements specificationČekanauskaitė, Jūratė, Čekanauskaitė, Jolanta 31 August 2011 (has links)
Darbo tikslas yra sukurti reikalavimų specifikavimo integralumą užtikrinantį metodą. Šiam tikslui įgyvendinti sukurtas procesų modelis, kurį sudaro trys pagrindiniai uždaviniai: reikalavimų identifikavimas, specifikavimas ir komponavimas. Pirmi du uždaviniai padeda identifikuoti besikertančius reikalavimus taip sumažinamas reikalavimų išsibarstymas specifikacijoje, nustatomos priklausomybės ir būtini reikalavimai. Komponavimo etapo tikslas yra sukomponuoti reikalavimus ir suteikti kūrėjams visą sistemos vaizdą bei nustatyti ir valdyti konfliktus tarp reikalavimų. Reikalavimų integralumas užtikrinamas visus reikalavimus, laikant vienoje formoje.
Darbe išnagrinėti reikalavimų specifikavimo šablonai, klasifikavimo standartų bei reikalavimų valdymo įrankiai. Analizuojami besikertančių reikalavimų identifikavimo ir išgavimo strategijos. Atlikta funkcinių ir nefunkcinių reikalavimų integralumo metodų ir būdų analizė.
Sukurtas šablonas reikalavimams specifikuoti, kuris apima funkcinius ir nefunkcinius reikalavimus, funkcinius ir nefunkcinius besikertančius reikalavimus. Reikalavimų valdymui sudarytas šablonas RequisitePro aplinkoje.
Sukurtas MagicDraw paketo profilis, siekiant pateikti kūrėjams pilną sistemos vaizdą, atvaizduojant reikalavimų rinkinius panaudos atvejų diagramomis.
Metodas patikrintas sudarant ATM sistemos reikalavimų specifikaciją, reikalavimai specifikuojami apimant funkcinius ir nefunkcinius reikalavimus, būtinus reikalavimus, funkcinius ir... [toliau žr. visą tekstą] / The aim of this work is to create A method for integrity support of requirements specification. For this purpose a process model is developed, which consists of three main tasks: the identification of requirements, specification and composition. The first two tasks helps to identify the crosscutting requirements of the following reduction the requirements dispersal in requirements specification, also identify responsibilities of requirements and identify required requirements. The goal of composition task is to compose the requirements to give the developer a view of the whole system and to identify and manage conflicts between requirements. Integrity of requirements are ensured keeping all requirements in a unique form.
The paper analyzes the identification of crosscutting requirements and gathering strategies. The templates of requirements specification, standards of requirements classification and requirements management tools were analyzed. The methods and techniques of functional and non-functional requirements for the integrity were analyzed.
The unique template for requirements specification was created, which includes functional and non-functional requirements, functional and non-functional crosscutting requirements. The template for requirements management was consisted in RequisitePro environment.
The MagicDraw profile package was created, which provide the developer a view of the whole system, representing set of requirements for use case diagrams.
The method... [to full text]
|
27 |
[en] UNIFYING AGILE REQUIREMENTS SPECIFICATION QUALITY CONTROL AND IMPLEMENTATION CONFORMANCE ASSURANCE / [pt] UNIFICANDO CONTROLE DE QUALIDADE DE ESPECIFICAÇÃO ÁGIL DE REQUISITOS E GARANTIA DE CONFORMIDADE DE IMPLEMENTAÇÃOTHIAGO DELGADO PINTO 14 December 2018 (has links)
[pt] Práticas de engenharia de requisitos ágeis estão se tornando mais comuns em equipes de desenvolvimento de software. Contudo, as práticas relacionadas ao controle de qualidade ainda dependem fortemente do conhecimento, da experiência e do trabalho manual de testadores, em adição as especificações de requisitos produzidas são frequentemente imprecisas e difíceis de verificar estaticamente por interessados ou por algum computador. Essa tese ataca conjuntamente o problema de verificar estaticamente especificações de requisitos ágeis e de gerar casos de teste e scripts de teste automatizados completos a partir delas. Suas contribuições principais incluem: (1) uma nova metalinguagem, chamada Concordia, que permite escrever especificações de requisitos ágeis que podem ser usadas para atividades de verificação e validação (V e V); (2) uma nova abordagem para gerar casos de teste e scripts de teste automatizado completos, a partir de requisitos especificados com a metalinguagem; (3) a medição, em contexto industrial, da capacidade da abordagem em reduzir o risco de defeitos e custos de V e V. / [en] Agile requirements engineering practices are being used more commonly by software development teams. However, practices related to quality control still depend heavily on testers expertise and manual labor, whilst produced require-ments specifications are often imprecise and hard to verify statically by both stake-holders and computers. This thesis jointly tackles the problem of verifying statically agile requirements specifications and generating full-featured test cases and auto-mated test scripts from them. Its main contributions include: (1) a new metalan-guage, called Concordia, for writing agile requirement specifications that can be used for both verification and validation (V and V) activities involving stakeholders; (2) a novel approach to generate full-featured ready to use test cases and automated test scripts from the requirements specified with the metalanguage; (3) the assess-ment in industrial context of the approaches ability to reduce risk of remaining defects and the costs of V and V.
|
28 |
Regras de Mapeamento e Heurísticas: uma estratégia para criar casos de teste a partir de C&LSOUSA, Silvia Pereira de Azevedo 01 August 2016 (has links)
Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-02-21T16:58:53Z
No. of bitstreams: 2
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
Dissertação_SilviaVersaoFinal.pdf: 3562807 bytes, checksum: d273ad6c061161f899cab3d232a82a79 (MD5) / Made available in DSpace on 2017-02-21T16:58:54Z (GMT). No. of bitstreams: 2
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
Dissertação_SilviaVersaoFinal.pdf: 3562807 bytes, checksum: d273ad6c061161f899cab3d232a82a79 (MD5)
Previous issue date: 2016-08-01 / FACEPE / Contexto: A fase de especificação de requisitos é fundamental no processo de
desenvolvimento de software. O uso de cenários é bastante popular para especificar
requisitos, por serem descritos em linguagem natural. No entanto, a linguagem natural
dá margem a requisitos ambíguos, incompletos e inconsistentes, o que vai de encontro
com os objetivos da fase de especificação de requisitos. Nesse sentido, uma técnica
baseada em Cenário & LEL (Language Extended Lexicon), chamada de C&L, pode
ser a solução adequada, pois LEL é um glossário que define um conjunto de palavras
que pertencem a um domínio e que devem ser usadas para descrever os cenários.
Assim, C&L é considerada uma técnica de cenários baseada em linguagem natural
controlada que ajuda a minimizar os problemas previamente mencionados, além de
poder ser utilizada para criar casos de teste de forma mais sistemática. Objetivo:
Neste trabalho, são propostas duas abordagens: a primeira abordagem usa regras de
mapeamento para derivar modelos statechart a partir de C&L visando verificar a
completude e consistência desses cenários e a segunda usa heurísticas para obter
sistematicamente casos de teste a partir de modelos statechart. Método: A pesquisa
apresentada nessa dissertação seguiu a abordagem de Engenharia para definir as
regras de mapeamento e as heurísticas que, por sua vez, foram avaliadas
empiricamente. Resultados: As regras de mapeamento apoiam a derivação de
statechart a partir de C&L. As heurísticas apoiam a derivação de casos de teste a
partir dos modelos statechart. Foi realizado um experimento para comparar o número
de erros de incompletude e inconsistência detectados pelos grupos experimental e
controle e o tempo gasto pelos grupos para detectar esses erros. Também foi
verificado se os statecharts gerados através da aplicação das regras de mapeamento
possuem grau de corretude e semelhança. Foi realizada uma avaliação qualitativa das
heurísticas utilizadas para derivar os casos de teste, com o intuito de saber se as
heurísticas foram utilizadas corretamente, se estão claras e são fáceis de usar.
Conclusões: Os resultados do experimento mostram que o número de erros de
incompletude detectados pelo grupo experimental foi superior ao número obtido pelo
grupo controle e em relação aos erros de inconsistência não houve diferença entre
quantidade de erros detectados pelos dois grupos. Além disso, a média do tempo
gasto para identificar erros de incompletude e inconsistência pelo grupo experimental
foi ligeiramente superior a média do tempo gasto pelo grupo controle. Em relação ao
grau de corretude, dentre os modelos gerados pelo grupo experimental, existe um que
apresenta o maior grau de corretude com 85,7%. No entanto, o grau de semelhança
entre os modelos é considerado de “baixa semelhança”. O resultado da avaliação
qualitativa mostrou que os participantes concordaram que as regras de mapeamento
e as heurísticas são compreensíveis e fáceis de utilizar. Também foi observado que
as heurísticas foram usadas de maneira correta na derivação dos casos de teste. / Context: The requirements specification phase is fundamental in the software
development process. The use of scenarios is quite popular to specify requirements
because they are described in natural language. However, natural language gives rise
to ambiguous, incomplete and inconsistent requirements, jeopardizes the objectives of
the requirements specification phase. In this context, a technique based on Scenarios
and LEL (Language Extended Lexicon), called C&L, may be an appropriate solution
because LEL is a glossary that defines a set of words that belong to a domain and
should be used to describe the scenarios. Thus, C&L is a scenario technique based
on controlled natural language that helps to minimize the problems previously
mentioned, and can be used to create test cases in a more systematic way. Objective:
In this study, two approaches are proposed: the first approach uses mapping rules to
derive statechart models from C & L in order to verify the completeness and
consistency of these scenarios and the second uses heuristics to systematically derive
test cases from statechart models. Method: The research presented in this work
follows the engineering approach to define the mapping rules and heuristics that, in
turn, were empirically evaluated. Results: Mapping rules support the derivation of
statechart from C & L. Heuristics support the derivation of test cases from statechart
models. An experiment was conducted to compare the number of incompleteness and
inconsistency errors detected by the experimental and control the groups and the time
spent by groups to detect these errors. Also it was verified whether the statecharts
generated by the application of the mapping rules have degree of correctness and
likeness. A qualitative evaluation of the heuristics used to derive the test cases was
made, in order to know whether the heuristics were correctly used and if they are clear
and easy to use. Conclusions: The results of the experiment show that the number of
incompleteness errors detected by the experimental group was higher than the number
obtained by the control group, and in relation to inconsistency errors, there was no
difference among the number of errors detected by the two groups. Furthermore, the
average time spent to identify incompleteness and inconsistency errors by the
experimental group was slightly higher than the average time spent by the control
group. In relation to the degree of correctness among the models generated by the
experimental group, there is one that has the highest degree of correctness with
85.7%. However, the degree of similarity between the models is considered "low
similarity”. The result of the qualitative evaluation showed that the participants agreed
that the mapping rules and heuristics are comprehensible and easy to use. It was also
observed that the heuristics were used correctly in the derivation of test cases.
|
29 |
Utilização de Mapas Mentais para Registro de Requisitos / Use of Mind Maps to Record RequirementsNISHI, Luciana 16 September 2009 (has links)
Made available in DSpace on 2014-07-29T14:57:52Z (GMT). No. of bitstreams: 1
Diss LuNishi.pdf: 535052 bytes, checksum: 312e4f56b2249ade58df12ebfe2b4dcb (MD5)
Previous issue date: 2009-09-16 / This work uses mind maps to describe requirements and investigates this not well known application through an experiment. The experiment was based on desirable features
sought by requirements engineers in notations and functions offered by tools. Both provided input to small changes in mind maps before a real specification was produced for the experiment. The results show that mind maps should be considered seriously as an alternative notation to describe software requirements / Este trabalho investiga o uso de mapas mentais na engenharia de requisitos, com destaque para o registro de requisitos. Características e funcionalidades desejáveis por engenheiros
de requisitos foram coletadas e motivaram adaptações nos mapas mentais para uso neste domínio. Um experimento empregou a notação alterada e forneceu indícios positivos e
negativos. O experimento permite, contudo, considerar o uso de mapas mentais como uma alternativa viável para o registro de requisitos e merecedora de pesquisas posteriores
|
30 |
Pattern-based Specification and Formal Analysis of Embedded Systems Requirements and Behavioral ModelsFilipovikj, Predrag January 2017 (has links)
Since the first lines of code were introduced in the automotive domain, vehicles have transitioned from being predominantly mechanical systems to software intensive systems. With the ever-increasing computational power and memory of vehicular embedded systems, a set of new, more powerful and more complex software functions are installed into vehicles to realize core functionalities. This trend impacts all phases of the system development including requirements specification, design and architecture of the system, as well as the integration and testing phases. In such settings, creating and managing different artifacts during the system development process by using traditional, human-intensive techniques becomes increasingly difficult. One problem stems from the high number and intricacy of system requirements that combine functional and possibly timing or other types of constraints. Another problem is related to the fact that industrial development relies on models, e.g. developed in Simulink, from which code may be generated, so the correctness of such models needs to be ensured. A potential way to address of the mentioned problems is by applying computer-aided specification, analysis and verification techniques already at the requirements stage, but also further at later development stages. Despite the high degree of automation, exhaustiveness and rigor of formal specification and analysis techniques, their integration with industrial practice remains a challenge. To address this challenge, in this thesis, we develop the foundation of a framework, tailored for industrial adoption, for formal specification and analysis of system requirements specifications and behavioral system models. First, we study the expressiveness of existing pattern-based techniques for creating formal requirements specifications, on a relevant industrial case study. Next, in order to enable practitioners to create formal system specification by using pattern-based techniques, we propose a tool called SeSAMM Specifier. Further, we provide an automated Satisfiability Modulo Theories (SMT)-based consistency analysis approach for the formally encoded system requirements specifications. The proposed SMT-based approach is suitable for early phases of the development for debugging the specifications. For the formal analysis of behavioral models, we provide an approach for statistical model checking of Simulink models by using the UPPAAL SMC tool. To facilitate the adoption of the approach, we provide the SIMPPAAL tool that automates procedure of generating network of stochastic timed automata for a given Simulink model. For validation, we apply our approach on a complex industrial model, namely the Brake-by-Wire function from Volvo GTT. / VeriSpec
|
Page generated in 0.0846 seconds