Slicing the V-Model -- Reduced Effort, Higher Flexibility

@article{Deuter2013SlicingTV,
  title={Slicing the V-Model -- Reduced Effort, Higher Flexibility},
  author={A. Deuter},
  journal={2013 IEEE 8th International Conference on Global Software Engineering},
  year={2013},
  pages={1-10}
}
  • A. Deuter
  • Published 2013
  • Engineering, Computer Science
  • 2013 IEEE 8th International Conference on Global Software Engineering
Companies requiring a formal software process model tend to choose the V-model. Having its advantages in a strong focus on verification and validation, the main drawbacks of the V-model are the need to create a large amount of documentation, to keep this documentation continuously updated and to manage trace ability of requirements implementation and testing. As it is based on the waterfall process model the timing behavior of the V-model is considered to be stiff. Additional complexity arises… Expand
Measuring the Software Size of Sliced V-Model Projects
  • A. Deuter, G. Engels
  • Computer Science
  • 2014 Joint Conference of the International Workshop on Software Measurement and the International Conference on Software Process and Product Measurement
  • 2014
TLDR
This article extends source code-based metrics, namely the size of code changes which is called churn, by the counting of work items representing the design and test documentation belonging to that churn by proposing a novel automated way on software quantity measurement. Expand
Developing the Requirements of a PLM/ALM Integration: An Industrial Case Study
TLDR
Application Lifecycle Management (ALM) covers many of the above-mentioned issues and has become widely used by software companies in the same manner as PLM solutions belong to the standard enterprise IT environment of companies developing physical products. Expand
Visualizing Functional Verification in Adaptive AUTOSAR
TLDR
This paper presents an approach to functionally verify software through visualization, in the scope of Adaptive AUTOSAR stack, which is very relevant in agile development practices which require sprint-based demonstrations. Expand
Reporting Empirical Evidence in Distributed Software Development: An Extended Taxonomy
TLDR
An extended taxonomy to classify empirical DSD evidence is presented and preliminary evaluation of the proposed taxonomy suggests that it can be used to synthesize existing knowledge, to identify gaps in literature, to identifies related work and to help researchers who will publish or review further empirical work, as well as practitioners who are interested in published empirical studies. Expand
The Integration Development Platform and Application of the Avionics System Based on the Model-Driven
TLDR
This platform used the model-driven design to solve the problems of avionics system development, such as the long development cycle, heavy maintenance work, the complicated connection of all the development phases and the no reuse of design results. Expand
Applying Manufacturing Performance Figures to Measure Software Development Excellence
TLDR
Producing companies monitor their manufacturing excellence related to these products by evaluating manufacturing performance figures such as delivery time and yield, but for the time being, no figures for the software inside are measured with similar means. Expand
Specification and Design of Safety Functions for the Prevention of Ship-to-Ship Collisions on the High Seas
TLDR
A new approach to Collision Avoidance Systems (CAS) is brought and the earliest stages in the development of safety functions for the reduction of ship-to-ship collision risk on the high seas are presented. Expand
Simulation based verification for LIN/CAN application layer

References

SHOWING 1-10 OF 24 REFERENCES
Comparative Analysis of Software Development Life Cycle Models
The trends of increasing technical complexity of the systems coupled with the need for repeatable and predictable process methodologies have driven system developers to establish system developmentExpand
Agile Development of Safety-Critical Software
TLDR
This paper analyses the agile principles and processes and gives guidance on how organizations could change their processes to a more agile way without risking the safety or marketability of the products or causing increased product and liability risks. Expand
Scrum-based Methodology for Distributed Software Development
TLDR
A methodology based on the integration of RUP and Scrum is presented, called scrum UP, which has been so designed as to be appropriate in a distributed environment. Expand
A survey of traceability in requirements engineering and model-driven development
TLDR
An overview of the current state of traceability research and practice in requirements engineering and model-driven developers is provided, identifying commonalities and differences in these areas and uncover several unresolved challenges which affect both domains. Expand
An analysis of the requirements traceability problem
  • O. Gotel, A. Finkelstein
  • Engineering, Computer Science
  • Proceedings of IEEE International Conference on Requirements Engineering
  • 1994
TLDR
The distinction between pre-requirements specification (pre-RS) traceability and post-RS traceability is introduced to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework to understand its multifaceted nature. Expand
Distributed Agile Software Development: A Review
TLDR
The challenges faced by geographically distributed agile teams and proven practices to address these issues, which will help in building a successful distributed team are discussed. Expand
An Empirical Study of Speed and Communication in Globally Distributed Software Development
TLDR
This work uses both data from the source code change management system and survey data to model the extent of delay in a distributed software development organization and explores several possible mechanisms for this delay. Expand
Collaboration in Distributed Software Development
TLDR
This chapter summarizes research activities aimed to build an evidence-based model of task-technology fit for communication-intensive activities such as distributed requirements workshops, and introduces computer-mediated communication theories which reveal some patterns of tool usage to overcome the challenges of distance. Expand
Analogy based prediction of work item flow in software projects: a case study
  • A. Mockus
  • Engineering, Computer Science
  • 2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings.
  • 2003
TLDR
This work modeling the flow of work items and using information on historic projects to predict the work flow of an ongoing project and presents the workflow model, and briefly describes project prediction of a large software project for customer relationship management (CRM). Expand
Group awareness in distributed software development
TLDR
This paper interviewed developers, read project communication, and looked at project artifacts from three successful open source projects to find that distributed developers do need to maintain awareness of one another, and that they maintain both a general awareness of the entire team and more detailed knowledge of people that they plan to work with. Expand
...
1
2
3
...