14,918 research outputs found
Boundary Objects and their Use in Agile Systems Engineering
Agile methods are increasingly introduced in automotive companies in the
attempt to become more efficient and flexible in the system development. The
adoption of agile practices influences communication between stakeholders, but
also makes companies rethink the management of artifacts and documentation like
requirements, safety compliance documents, and architecture models.
Practitioners aim to reduce irrelevant documentation, but face a lack of
guidance to determine what artifacts are needed and how they should be managed.
This paper presents artifacts, challenges, guidelines, and practices for the
continuous management of systems engineering artifacts in automotive based on a
theoretical and empirical understanding of the topic. In collaboration with 53
practitioners from six automotive companies, we conducted a design-science
study involving interviews, a questionnaire, focus groups, and practical data
analysis of a systems engineering tool. The guidelines suggest the distinction
between artifacts that are shared among different actors in a company (boundary
objects) and those that are used within a team (locally relevant artifacts). We
propose an analysis approach to identify boundary objects and three practices
to manage systems engineering artifacts in industry
Scaling agile on large enterprise level – systematic bundling and application of state of the art approaches for lasting agile transitions
International audienceOrganizations are looking for ways of establishing agile and lean process for delivery. Many approaches exist in the form of frameworks, methods and tools to setup an individual composition for a best fit. The challenge is that large organizations are heterogeneous and diverse, and hence there is no "one size fits all" approach. To facilitate a systematic implementation of agile and lean, this article proposes a transition kit based on abstraction. This kit scouts and bundles state of the art methods and tools from the agile and lean community to align them with governance and compliance aspects of the specific enterprise. Coaching of the application of the transition kit ensures an adequate instantiation. The instantiation handles business domain specific aspects and standards. A coaching governance ensures continuous improvement. An example of the systematic application of the transition approach as well as its scaling is demonstrated through its application in the Volkswagen Group IT
Naming the Pain in Requirements Engineering: A Design for a Global Family of Surveys and First Results from Germany
For many years, we have observed industry struggling in defining a high
quality requirements engineering (RE) and researchers trying to understand
industrial expectations and problems. Although we are investigating the
discipline with a plethora of empirical studies, they still do not allow for
empirical generalisations. To lay an empirical and externally valid foundation
about the state of the practice in RE, we aim at a series of open and
reproducible surveys that allow us to steer future research in a problem-driven
manner. We designed a globally distributed family of surveys in joint
collaborations with different researchers and completed the first run in
Germany. The instrument is based on a theory in the form of a set of hypotheses
inferred from our experiences and available studies. We test each hypothesis in
our theory and identify further candidates to extend the theory by correlation
and Grounded Theory analysis. In this article, we report on the design of the
family of surveys, its underlying theory, and the full results obtained from
Germany with participants from 58 companies. The results reveal, for example, a
tendency to improve RE via internally defined qualitative methods rather than
relying on normative approaches like CMMI. We also discovered various RE
problems that are statistically significant in practice. For instance, we could
corroborate communication flaws or moving targets as problems in practice. Our
results are not yet fully representative but already give first insights into
current practices and problems in RE, and they allow us to draw lessons learnt
for future replications. Our results obtained from this first run in Germany
make us confident that the survey design and instrument are well-suited to be
replicated and, thereby, to create a generalisable empirical basis of RE in
practice
Adaptation of enterprise architecture efforts to an agile environment
Agile ways of working have become mainstream, with many organisations practising a form of agile. Agile maturity among those organisations differs. In a research conducted by VersionOne Inc. (2016), 82% of the participating organisations stated to be at or below the level of ‘still maturing’. Existing agile and architecture methods have begun to incorporate some aspects of each other, with agile methods including architecting, such as the Scaled Agile Framework (SAFe), and architecture frameworks such as TOGAF (the Open Group Architecture Framework), adding agile elements (Poort, 2014). This study addresses the question how to shape the architecture function to effectively achieve compliance with architecture regulations, of solutions realised in an agile environment. To answer this question a multiple-case study was done, studying three different organisations. The findings are translated into seven propositions
Web Engineering Security (WES) Methodology
The impact of the World Wide Web on basic operational economical components in global information-rich civilizations is significant. The repercussions force organizations to provide justification for security from a business-case perspective and to focus on security from a Web application development environment standpoint. The need for clarity promoted an investigation through the acquisition of empirical evidence from a high level Web survey and a more detailed industry survey to analyze security in the Web application development environment ultimately contributing to the proposal of the Essential Elements (EE) and the Security Criteria for Web Application Development (SCWAD). The synthesis of information provided was used to develop the Web Engineering Security (WES) methodology. WES is a proactive, flexible, process neutral security methodology with customizable components that is based on empirical evidence and used to explicitly integrate security throughout an organization’s chosen application development process
A Study of Quality Assurance and Testing in Software Development Life Cycle
The objective of this document is to specify a Software Quality Life Cycle (SQLC) that will be used in the development of high quality software. The goal is to create streamlined usable process that supports the SQLC so that the activities related to software quality can be integrated into the existing software development processes. In addition, it is important that we create these processes so they will: Not inhibit the flow of work Not inhibit the creativity of the people Not fail immediately because of the time or resources required Not fail in the long run because the process or life cycle is unsupportable or inflexible.
This document will: Outline the Software Quality Life Cycle (SQLC) and the steps in that life cycle. Focus on a framework and guidelines, not step by step instructions. Define software quality and testing terms that may be unfamiliar or used inconsistently.
Benefits for the users of this document: Provide a repeatable process where the user don\u27t have to reinvent the wheel. Decrease the learning curve of those new to software quality assurance. Aid communication and eliminate confusion with the use of consistent terminology. Contribute to a higher degree of accuracy for project estimates.
SCOPE OF THIS DOCUMENT
The Software Quality Life Cycle testing involves continuous testing of the system during the development process. At predetermined points, the results of the development process are inspected to determine the correctness of the implementation. These inspections identify defects at the earliest possible point. This document will explain the Software Quality Life Cycle (SQLC) process and how it relates to the Software Development Life Cycle (SDLC).
This document will: Encompass the full life cycle of quality assurance and testing an application. Include main levels of testing (unit, system, user acceptance, and installation). Provide an overview of all types of testing. Focus on web and client/ server applications. Address maintenance testing
A Manual for Project Governance and Asset Management
Students, practitioners, and businesses will all benefit from this free eBook, which focuses on project governance and asset management. Documenting best practices from design to implementation, including a review of existing frameworks, this eBook provides direction in the field of governance and asset management. Here, the ideas of assets and governance are brought together, and an agile governance framework is introduced. We hope to examine how these ideas may be used in project management in order to discover beneficial methodologies and approaches.
If you’re looking to build trust and transparency in decision-making processes, this eBook is a must-read. It is intended for individuals who wish to create an atmosphere that accelerates strategy execution and the attainment of organisational objectives while offering good advice. Everyone in the organisation, including project managers and stakeholders from outside the company, can have an influence on the governance framework of projects and the management of the business’s assets to capture value and strengthen the strategic direction. By providing the necessary leadership, direction, and protocols, an organisation’s asset management and project governance frameworks may assist to guarantee that its strategy and execution are in sync
- …