Spelling suggestions: "subject:"founctional requirements"" "subject:"5functional requirements""
71 |
Vytvoření funkčních požadavků na IS na základě analýzy organizace / Creation of Functional Requirements for IS from Process Analysis of an OrganizationMařík, Ondřej January 2017 (has links)
The thesis focuses on the creation of functional requirements for an information system based on process analysis of an organization. In the theoretical part introduces the reader to the basic concepts related to business processes, their modeling and relationship with the company information system. Then, two approaches to analysing the functioning of the organization are presented, namely the approach of consultancy company Logio and the MMABP methodology. The practical part describes a real project of process analysis and creation of functional requirements for IS of a trading company. The MMABP approach is then applied to the same company. In conclusion, suitability of both approaches is evaluated and observed differences between them are identified.
|
72 |
Das neue Zusammenrücken von Formal- und Sacherschließung: FRBR, RDA, GNDWiesenmüller, Heidrun 24 January 2011 (has links)
Während Formal- und Sacherschließung in der angloamerikanischen Tradition als etwas Zusammengehöriges betrachtet werden, besteht im deutschen Bibliothekswesen eine klare, zumeist auch personelle Trennung zwischen den beiden Bereichen. Jüngere Entwicklungen der internationalen Standardisierung könnten hier zu einem Umdenken führen: Das theoretische Modell "Functional Requirements for Bibliographic Records" (FRBR) hat eine neue Sicht auf das so genannte "bibliographische Universum" eingeläutet, das auch die Sacherschließung mit einbezieht. Auch "Resource Description and Access" (RDA), der Nachfolger von AACR2, versteht sich nicht mehr nur als ein Regelwerk für die Formalerschließung. Ganz konkrete Schritte für ein stärkeres Miteinander bringt das Projekt "Gemeinsame Normdatei" (GND) mit der Zusammenführung der Schlagwortnormdatei (SWD), der Personennamendatei (PND) und der Gemeinsamen Körperschaftsdate (GKD). Im Vortrag werden diese Entwicklungen näher beleuchtet und Überlegungen zu den damit verbundenen Chancen und Problemen angestellt.
|
73 |
Sustainable Software Engineering : An Investigation Into the Technical Sustainability DimensionHYGERTH, HENRIK January 2016 (has links)
is study has focused on the technical sustainability dimension of sustainable soware engineering. Sustainabilitywithin soware engineering is something that has recently started to gain traction, where most of theresearch has focused on the environmental dimension.e purpose of this study was to investigate the technicalsustainability dimension, and contribute by continuing to build upon previous research which has suggestedsustainability as a part of non-functional requirements and as a part of soware quality.is study was conducted with a qualitative approach. is approach used interviews with people withexperience of working in soware development to collect data. e interviews were used to gain in-depthinformation of the dierent aspects in soware development, e.g. development processes.e results, based on the interviews, showed that from a technical sustainability perspective there are issueswith where the focus of the work is in soware development and also problems related to how timemanagementis used.e results also showed that there was some lacking in understanding the benets and tradeos ofdecisions made in the project, for example regarding the soware design, which can result in unnecessarycomplexity is acquired.e study found that the culture within soware development projects and companies needs to be changedtowards a culture which promotes the development of high quality soware. Because non-functional requirementsand soware quality are components of technical sustainability, therefore is the technical sustainabilityhigher if the quality is high. It was further found that this culture would be possible if changes were made tothe way prioritisations are made, and the way testing is performed should be extended. Finally it was foundthat the understanding of the benets and tradeos of decisions and ideas needs to be increased and extendedcollectively.e study concluded that the technical sustainability dimension can be achieved through these changes andthat the problem and solution therefore are not small and local but rather a big and complex issue where thesolution spans several solutions that encompasses dierent aspects and perspectives.
|
74 |
An application portfolio management method - for implementation at SCANIA CV ABNylén, Erik January 2011 (has links)
Information Technology (IT) has become a vital tool for most industrial businesses and Scania CV AB is no exception. As the importance of IT generally has increased, the usage and number of applications has grown as well. Applications are substantial assets for an organization that is heavily supported by IT. Consequently, a way of managing applications efficiently and sustaining the costs of applications rather low ? doing more with less ? is required. In addition it is also important, from a business perspective, that applications as part of IT are aligned with business strategies and goals. Application Portfolio Management (APM) is a practice and a business-centric activity aimed to allocate IT resources to support business objectives and strategies; it helps determining the impact of applications and the relative importance of each application in the portfolio to the business. APM attempts to justify and measure the financial benefits of each application relative to the costs of the applications? maintenance and operations. Performing APM successfully is nevertheless a complicated issue, and something that many businesses are challenged with on a daily basis. New applications are constantly and regularly added, downloaded, purchased or selfdeveloped ? too often without any further control. In order to regain the control of the software that automates the business, and ensuring that the applications adds value and reliability to the company, Scania CV AB requires a rigorous and comprehensive method for an APM approach. In this master thesis together with Camilla Palomeques?s thesis1, such a method is provided. These two theses also offer a suggestion on how to proceed with the APM effort at Scania CV AB.
|
75 |
Requirements Engineering and Response Time : A study about the Requirements Engineering and the Response Time of a Highly Interactive Web-based Application.Ibrahim Bacha, Faisal January 2021 (has links)
Low response time is an important factor for any interactive system. However, web-based applications suffer sometimes from bad response times. This fact is not always important but for services depending on a high degree of interactivity it can be severe. This thesis attempts to give an answer to the question whichi s the requirements engineering for best response time on a highly interactive Web-based application? The research approach is deductive based on a single-case study and using qualitative method. The case system is a web-based system that supports an experimental technique called Wizard-of-Oz. To tackle the research question an extensive review of literature on requirements engineering was made, and, for the case study itself, system requirements documents and interviews were included. The results include information about the specific requirements engineering process for the case system, response time, and quality attributes.The conclusion indicates the importance of response time requirements, hardware and software requirements, testing, but also a demonstration phase for desired interactive behaviour including response time. The latter is not previously identified as a major step in the general literature on requirements engineering but should definitively be noted by researchers and practitioner alike.
|
76 |
Exploring non-functional requirements in Digital Product-Service System design : Challenges for manufacturing firmsToller Melén, Carl Nils Konrad January 2023 (has links)
The increased sophistication of customer needs pushes manufacturers toward integrated offerings where physical products and intangible services collaboratively generate value, also known as Product-Service Systems (PSS). This shifts the focal point from product performance to overall system functionality. However, this naturally increases the importance of requirements linked to the operation and the system's behavior, e.g., reliability, safety, and flexibility. These kinds of requirements that dictate how a system should behave and operate in its context are called non-functional requirements. However, most manufacturing firms have a legacy of focusing mainly on functional requirements. Alongside this trend, there has been an increasing affordability and availability of data. However, how this data can be utilized for value creation remains a question for the industry. Operational data can serve as a vital source of information about the PSS behavior and value delivery process. Since non-functional requirements depend on the operational context for measuring their performance, operational data can thus provide new insights. This thesis aims to study the motivation for and challenges of working with non-functional requirements and value within Digital PSS design by manufacturing firms. Firstly, the management of non-functional requirements in the design process is studied. The empirical research determined that there are six challenges that a design team and organization face when working with non-functional requirements. The challenges highlight that non-functional requirements’ fuzzy and intangible aspects make them easy to neglect and hard to include in design and decision-making. A state-of-the-art review is conducted to identify possible remedies. Onward, the intersection between data and value is explored. An overarching classification of operational data and how these can contribute to different forms of value creation is presented based on previous literature. Further, the analysis shows what kind of operational data can be collected using three levels of granularity. Experiences and reflections from multiple companies at different stages in their servitization journey are gathered to complement and expand the perspective on operational data and value.
|
77 |
[en] ALIGNING DEVELOPER QUALITY CONCERNS, REFACTORING APPLICATIONS, AND THEIR EFFECTS / [pt] ALINHANDO PREOCUPAÇÕES DE QUALIDADE DE DESENVOLVEDORES A APLICAÇÕES DE REFATORAÇÕES E SEUS EFEITOSVINICIUS PASSOS DE OLIVEIRA SOARES 25 November 2021 (has links)
[pt] Mesmo com o processo de refatoração sendo investigado cada vez mais
nos últimos anos, muitas de suas características se mantém pouco compreendidas.
Refatoração de software é o processo de melhorar a manutenibilidade
de um sistema por meio de mudanças estruturais que não alteram seu comportamento.
Estudos recentes revelaram que projetos de software frequentemente
recebem refatorações compostas. Em tais refatorações, desenvolvedores aplicam
uma série de transformações únicas em conjunção e em um único commit,
e se espera que estas refatorações tenham um efeito maior e mais positivo do
que refatorações singulares. Porém, refatorações frequentemente causam mudanças
que ou mantém a qualidade do software da mesma forma, ou causam
a piora do mesmo, levando trabalhos recentes a procurar causas em potencial
para este comportamento. Porém, o porquê da complexidade destas mudanças
compostas frequentemente afetarem seus resultados de alguma forma positiva
ou (inesperadamente) negativa continua não investigado. O mesmo ocorre com
o potencial efeito das preocupações dos desenvolvedores durante a aplicação
de refatorações. Sobre estas preocupações, alguns trabalhos anteriores foram
desenvolvidos em torno da caracterização e detecção de discussões de desenvolvedores
relacionadas a refatorações. Porém, não se sabe se e como estas
preocupações de desenvolvedores com refatorações, tornando-se explícitas em
tais discussões, podem influenciar os efeitos de refatorações em um sistema.
Portanto, este trabalho apresenta dois estudos com o objetivo de preencher a
lacuna no conhecimento de que causas levam aos efeitos não-positivos frequentemente
encontrados em refatorações, procurando entender: (i) se refatorações
mais complexas realmente são mais efetivas do que refatorações simples, como
esperado; (ii) em que situações desenvolvedores tendem a explicitar suas preocupações
com refatoração do código; e (iii) qual é o impacto de tais preocupações
na efetividade de uma refatoração em melhorar a qualidade estrutural
do código. Nós analisamos estas características e atingimos os seguintes
resultados: Primeiro, conforme a complexidade das refatorações aumenta, a
efetividade das mesmas aumenta conjuntamente. Segundo, há uma relação entre
a efetividade de refatorações e preocupações explícitas com refatorações,
onde a possibilidade de efeitos negativos é menor quando desenvolvedores estão
explicitamente preocupados com refatoração. Finalmente, desenvolvedores
tendem a explicitar mais frequentemente suas preocupações com o processo de
refatoração quando deparados com tarefas de refatoração mais complexas. / [en] Even though the refactoring process has been increasingly investigated
in the last years, many of its characteristics remain poorly understood. Software
refactoring is the process of improving the maintainability of a system
through structural changes that do not alter its behaviour. Recent studies revealed
that software projects frequently have to undergo composite refactorings.
In such refactorings, developers perform a series of single transformations in
conjunction and in a single commit, which are expected to have a larger and
more positive impact than single refactorings. However, refactorings frequently
cause changes that either keep the software quality the same, or cause it
to worsen, which lead recent works to look for potential causes of this behavior.
However, the complexity of these composite changes often affecting their
outcomes in some positive or (unexpectedly) negative way remains not investigated,
much like the developers concerns while performing refactoring. For
the latter, some previous work was performed around characterizing and detecting
refactoring-related developer discussions. However, it is unknown whether
and how developers refactoring concerns made explicit in such discussions can
influence the refactorings effects on a system. Thus, this work reports two
studies aimed at bridging some of those gaps in knowledge in which causes
lead to the non-positive effects frequently found in refactoring, by understanding:
(i) if more complex refactorings are indeed more effective than simple
refactorings, as one would expect; (ii) in which situations developers tend to
have explicit concerns while refactoring the code; and (iii) what is the impact
of such concerns on the effectiveness of a refactoring to improve structural
quality. We analyze these characteristics and reach the following results: First,
as refactoring complexity increases, the effectiveness of such refactorings increases
as well. Second, there is a relationship between refactoring effectiveness
and explicit refactoring concerns, in which the possibility of negative effects
is lower when developers are explicitly concerned about refactoring. Finally,
developers tend to be more explicit about their concerns on the refactoring
process when they are faced with more complex refactoring tasks.
|
78 |
Разработка функциональных требований к информационной системе «ООО «НПО Атмосфера» : магистерская диссертация / Development of functional requirements for the information system "NPO Atmosphere"Фаттахов, Д. Р., Fattakhov, D. R. January 2020 (has links)
Актуальность темы магистерской диссертации обусловлена применением методик к организации, занимающейся инновациями в отраслевом секторе и при этом, имеющей потенциал для оптимизации трудозатрат. Цель данной работы – проектирование новой информационной системы для реализации инновационных технологий предприятия. Результаты работы: Представлен план по модернизации ИС с использованием информационных технологий, внедрение которых способно оптимизировать трудозатраты. / The relevance of the topic of the master's thesis is due to the application of methods to an organization that is engaged in innovation in the industry sector and, at the same time, has the potential to optimize labor costs. The purpose of this work is to design a new information system for the implementation of innovative technologies of the enterprise. Results of the work: A plan for the modernization of IS using information technologies was presented, the implementation of which can optimize labor costs.
|
79 |
THE IMPACT OF USER INVOLVEMENT ON INFORMATION SYSTEM PROJECTSEichhorn, Bradford Reese 26 September 2014 (has links)
No description available.
|
80 |
[pt] O USO DA LINGUAGEM INTENCIONAL PARA APOIAR A GESTÃO DE RISCOS EMPRESARIAL / [en] USING INTENTIONAL MODELING TO ENHANCE ENTERPRISE RISK MANAGEMENTRAFAEL DE SIQUEIRA T CAVALCANTI 19 May 2021 (has links)
[pt] Em função do ritmo acelerado com que tem surgido inovações de mercado, com as incertezas econômicas, a ascensão de mídias sociais, violações cibernéticas, e diversos outros fatores, os riscos organizacionais tem se tornado cada vez mais complexos e difíceis de serem geridos. É necessário que pensemos em modelos mais completos de representação de informações que possam interpretar os riscos aos quais as empresas estão expostas da maneira mais clara e detalhada possível. A modelagem i-estrela permite que informações sejam representadas sem que sejam excluídos detalhes relevantes para a gestão de riscos das organizações. Este artigo propõe uma modelagem de gestão de riscos por meio do modelo i-estrela, de forma a atender a necessidade de representação de informações complexas no atual ambiente de negócios empresarial. / [en] Due to the accelerated pace with which market innovations have emerged, with economic uncertainties, the rise of social media, security issues, and many other factors, organizational risks have become increasingly complex and challenging to manage. It is essential to think about more complete models of information representation that can interpret the risks to which companies are exposed, as clearly, and detailed as possible. The intentional modeling approach allows information to be represented without excluding details relevant to organizations risk management. This paper proposes a risk management modeling strategy using the iStar language to address the need for enhanced information representation in today s enterprise business environment.
|
Page generated in 0.138 seconds