Spelling suggestions: "subject:"[een] REQUIREMENTS VERIFICATION"" "subject:"[enn] REQUIREMENTS VERIFICATION""
1 |
Formální vertifikace textových use casů / Verification of Textual Use-CasesVinárek, Jiří January 2013 (has links)
The aim of this thesis is to create a tool for formal verification of systems specified using textual use- cases. The tool should allow for automated verification of temporal invariants specified in temporal logic (CTL and LTL formulae). The textual specification is transformed to a formal model that is verified using the NuSMV symbolic model-checker. Potential errors are shown to the user in the form of an HTML report. Using this feedback, the user is able to iteratively develop valid textual use-case specifications. The tool's architecture should be focused on reusability of its components and extensibility. Powered by TCPDF (www.tcpdf.org)
|
2 |
Software Requirements Elicitation, Verification, And Documentation: an Ontology Based ApproachElliott, Robert A 15 December 2012 (has links)
Software intensive systems are developed to provide solutions in some problem domain and software engineering principles are employed to develop and implement that system. Software engineering principles should enhance the development and production of software artifacts and yet the artifacts often lack in quality. Crucial in the development process are requirements engineering activities and methods for software documentation. This research focused on requirements engineering activities, software requirements documentation and employed a new approach in these activities that incorporated ontology engineering principles. Ontology engineering refers to the set of activities concerned with the ontology development process, the ontology life cycle, the methods for building ontologies, and the tool suites and languages that support them. Ontologies facilitate domain knowledge reuse and sharing and provides a common vocabulary to system developers. The motivation of this research came from Ambr´osio and Kaiya, advocating the definition of the Software Requirements Knowledge Area of the Software Engineering Body of Knowledge (SWEBOK ) within an ontology system. The resulting system utilized the benefits of intelligent reasoning to elicit, automatically verify, extract and document software requirements. The requirements engineering process was modeled in an ontology. An ontology is a machine-readable data structure that distinctly defines concepts and describes relationships among those concepts. The requirements engineering process and ontology were the focal points in this research. A baseline ontology for software requirements engineering was created. The following are contributions of this research. A methodology was designed to enhance the software documentation production process. An initial ontology model of SWEBOK recommended data items was created. A method was provided to verify software requirements as they were elicited, entered and maintained in an ontology. A method was created that electronically provided provenance of software requirements. Software was created to automatically extract the software requirements from within an ontology.
|
3 |
[en] REQUIREMENTS VERIFICATION AND VALIDATION: NATURAL LANGUAGE PROCESSING AND SOFTWARE AGENTS / [pt] VERIFICAÇÃO E VALIDAÇÃO EM REQUISITOS: PROCESSAMENTO DA LINGUAGEM NATURAL E AGENTESMIRIAM SAYAO 30 November 2007 (has links)
[pt] No processo de desenvolvimento do software, atividades
relacionadas ao
Processo de Requisitos envolvem elicitação, modelagem,
verificação e validação
dos requisitos. O uso da linguagem natural no registro dos
requisitos facilita a
comunicação entre os participantes do processo, além de
possibilitar que clientes e
usuários validem requisitos sem necessitar de conhecimento
extra. Por outro lado,
na economia globalizada atual, o desenvolvimento de
software por equipes
geograficamente distribuídas está se tornando uma norma.
Nesse cenário,
atividades de verificação e validação de requisitos para um
software de média ou
alta complexidade podem envolver o tratamento de centenas
ou milhares de
requisitos. Com essa ordem de complexidade é importante que
o engenheiro de
software tenha apoio computacional para o desempenho
adequado das atividades
de aferição de qualidade. Neste trabalho estamos propondo
uma estratégia que
combina técnicas de processamento da linguagem natural
(PLN) e agentes de
software para apoiar as atividades de análise dos
requisitos. Geramos visões
textuais ou gráficas de grupos de requisitos relacionados;
visões apóiam a análise
de completude, a identificação de duplicidades e de
dependências entre requisitos.
Utilizamos técnicas de análise de conteúdo para apoiar a
identificação de
omissões em requisitos não funcionais. Também propomos uma
estratégia para a
construção ou atualização do léxico da aplicação,
utilizando técnicas de PLN.
Utilizamos agentes de software para implementar serviços
que incorporam as
estratégias referidas, e também para atuar como
representantes dos participantes
do projeto em desenvolvimento. / [en] In software development process, initial activities can
involve requirements elicitation, modeling and analysis
(verification and validation). The use of natural language
in the register of the requirements facilitates the
communication among stakeholders, besides offering
possibilities to customers and users to validate
requirements without extra knowledge. On the other hand, in
the current global economy, software development for teams
geographically distributed is becoming a rule. In this
scenario, requirements verification and validation for
medium or high complexity software can involve the
treatment of hundreds or even thousand requirements. With
this complexity order it is important to provide
computational support for the software engineer execute
quality activities. In this work we propose a strategy
which combines natural language processing (NLP) techniques
and software agents to support analysis activities. We have
generated textual or graphical visions from groups of
related requirements; visions help completeness analysis,
identification of duplicities and dependences among
requirements. We use content analysis techniques to support
the identification of omissions in nonfunctional
requirements. Also, we propose a strategy to construct the
lexicon, using NLP techniques. We use software agents to
implement web services that incorporate the related
strategies, and also agents to act as personal assistants
for stakeholders of the software project.
|
4 |
[en] ANALYSIS OF NATURAL LANGUAGE SCENARIOS / [pt] ANÁLISE DE CENÁRIOS EM LINGUAGEM NATURALEDGAR SARMIENTO CALISAYA 28 November 2016 (has links)
[pt] A análise de requisitos desempenha um papel fundamental no processo de
desenvolvimento de software. Neste sentido, representações de cenários baseados
em linguagem natural são muitas vezes utilizados para descrever especificações
de requisitos de software (SRS). Cenários descritos usando linguagem natural
podem ser ambíguos e, às vezes, imprecisos. Este problema é parcialmente devido
ao fato de que os relacionamentos entre os cenários são raramente representados
explicitamente. Como os cenários são utilizados como entrada para as actividades
subsequentes do processo de desenvolvimento de software (SD), é muito
importante facilitar a sua análise; especialmente para detectar defeitos devido a
informações erradas ou falta de informação. Este trabalho propõe uma abordagem
baseada em Redes de Petri e técnicas de Processamento de Linguagem Natural
como uma forma eficaz para analisar os cenários adquiridos, e que toma
descrições textuais de cenários (em conformidade com um metamodelo definido
neste trabalho) como entrada e gera um relatório de análise como saída. Para
facilitar a análise automática, os cenários são transformados em Redes de Petri
(Lugar/Transição) equivalentes. Os cenários e suas Redes de Petri resultantes
podem ser analisados automaticamente para avaliar algumas propriedades
relacionadas à desambiguidade, completeza, consistência e corretude. Os defeitos
identificados podem ser rastreados até os cenários, permitindo a sua revisão. Nós
também discutimos como desambiguidade, completeza, consistência e corretude
das SRSs baseadas em cenários podem ser decompostas em propriedades
relacionadas, e definimos heurísticas para encontrar indicadores de defeitos que
prejudicam estas propriedades. Avaliamos nosso trabalho, aplicando a nossa
abordagem de análise em quatro estudos de caso. Essa avaliação compara os
resultados obtidos pela nossa abordagem automatizada contra os resultados
obtidos por um processo de inspeção e com trabalhos relacionados. / [en] Requirements analysis plays a key role in the software development process.
Natural language-based scenario representations are often used for writing
software requirements specifications (SRS). Scenarios written using natural
language may be ambiguous, and, sometimes, inaccurate. This problem is
partially due to the fact that relationships among scenarios are rarely represented
explicitly. As scenarios are used as input to subsequent activities of the software
development process (SD), it is very important to enable their analysis; especially
to detect defects due to wrong information or missing information. This work
proposes a Petri-Net and Natural Language Processing (NLP) based approach as
an effective way to analyze the acquired scenarios, which takes textual description
of scenarios (conform to a metamodel defined in this work) as input and generates
an analysis report as output. To enable the automated analysis, scenarios are
translated into equivalent Place/Transition Petri-Nets. Scenarios and their
resulting Petri-Nets can be automatically analyzed to evaluate some properties
related to unambiguity, completeness, consistency and correctness. The identified
defects can be traced back to the scenarios, allowing their revision. We also
discuss how unambiguity, completeness, consistency and correctness of scenario-based SRSs can be decomposed in related properties, and define heuristics for
searching defect indicators that hurt these properties. We evaluate our work by
applying our analysis approach to four case studies. The evaluation compares the
results achieved by our tool-supported approach, with an inspection based
approach and with related work.
|
Page generated in 0.0245 seconds