Explicitly defining a software process model is widely recognized as a good software engineering practice. However, having a defined process does not necessarily mean that this process is good, sound and/or useful. There have been several approaches for software process evaluation including testing, simulation and metrics; the first one requires software process enactment, i.e., an expensive, risky and long process, and the others require high expertise for correctly interpreting their meaning. In this paper we propose a visual approach for software process model evaluation based on three architectural view types, each one focusing on basic process elements: ROLE BLUEPRINT, TASK BLUEPRINT and WORK PRODUCT BLUEPRINT. They enable visual evaluation of different perspectives of a software process, each being relevant for a particular stakeholder. We illustrate the proposed approach by applying it to the software process defined for a real world company that develops software for retail. We show how design errors were identified.

/pdf/software-process-model-blueprints-cyye8zrxvr.pdf

Software process model blueprints

There are many different types of information to be considered when designing an information system, and a wide variety of modelling approaches and notations (or representations) have been developed to describe these different types of information. Some types of information are better expressed by some representations than others, so it is sensible to use multiple representations to describe a real-world phenomenon. Reconciling and integrating descriptions expressed using different representations is therefore an important part of the design process. The objective of this research is to aid this reconciliation and integration within the context of information systems design. That is, to facilitate the use of multiple modelling representations for describing a phenomenon. To achieve this objective, the author has chosen an approach based upon translating descriptions of a phenomenon between different representations. This thesis provides several important contributions in the area of information system design using multiple representations. Related work in the area is reviewed, and from this review is derived a terminology based on viewpoint-oriented methods that provides a consistent framework for the discussion of multiple representations. Previous research into the use of multiple representations has focused on semantic data models. This is extended in this thesis to include diverse modelling representations such as functional dependencies and data flow modelling. The process of translating between different representations is explored in depth, and several important issues identified. Translations are defined by a collection of rules that specify the mappings between constructs of representations. An abstract notation is developed for expressing these translations, and an extended version of Amor’s (1997) View Mapping Language is defined for the purpose of building detailed rule specifications. Heuristics and enrichment are proposed as two methods of improving the quality of translations. A measure for determining the relative quality of translations is developed to show that heuristics do indeed enhance translation quality. In addition, a method is developed for using translations to highlight potential design inconsistencies by translating descriptions expressed using different representations into the same form and comparing them. v

/pdf/using-multiple-representations-within-a-viewpoint-nz7bquany7.pdf

Using multiple representations within a viewpoint

Across a range of software development activities, there is typically no single best way to view the abstractions of interest, where the latter include software objects (such as source code), aspects of program execution, software requirements documentation, models of a software process being followed, and many others. Thus, mechanisms which provide automated support for multiple views have the potential to play an important role in many aspects of software development. This paper describes an approach to supporting multiple views which is based on obtaining these views via the unparsing of a single canonical representation of the abstractions of interest when supporting a particular software engineering activity. The general architecture is described, and its application to supporting two quite different aspects of software development – programming and software process modelling – is discussed. Finally, some recent work is outlined which addresses past limitations on editing mechanisms that can be provided in views derived from canonical representations such as abstract syntax trees.

Multiple views based on unparsing canonical representations—the MultiView architecture

Software development processes are complex. Erplicit software process models can assist in performing, managing, and improving the &velopment of software. But models of large (i.e., long-lasting, many people involved, variety of subprocesses) processes are not easy to handle. Explicit role-spect$c views of the processes promise to be a powetjid mechanism for capturing software development know how (i.e., descriptive software process modeling). This paper presents the idea of multi-view modeling and discusses some first results on building role-specific process models (i.e., views). Relevant issues for future research work are discussed later on. 1 Views of Software Development Processes Software process refers to’all activities performed to develop or maintain a software product or a product line. Software processes are likely to be complex. Process complexity is caused by product complexity, product qualities (e.g., robustness, reliability), and demands on process performance (e.g., meet schedule and stay in budget). Today’s complex processes are characterized by a large number of people involved, a long lasting schedule (i.e., months or even years), and specialized tasks; perhaps the development is distributed. These characteristics mean that people are unable to look at a process as a whole, but rather prefer views or subsets of information presented in an adequate style, oriented to their particular roles (e.g., project manager, quality assurance engineer, tester, coder, analyst). A role is an abstract concept and refers to the responsibility of performing a process in order to achieve specific goals (e.g., review component before end of next week). Software process models are explicit representations of software processes in order to enable human communication, process improvement, analysis, enaction’ and automatic execution of processes [5]. Several industrial projects have demonstrated the 1. In order to’emphasize. that humans interpret he process models the term enaction is used. Execution means interpretation by a machine. Pennlssion to make digital/hard copies of all or part of this material for personal or class-m use is granted without fee provided that the copies a.re not spade or drstnbuted for profit or commercial advantage, the copynght nouce, the title of the publication and its date appear, and notice is given that copyright is by permission of the ACM, Inc. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires specific permission and/or fee. SIGSOFp 96 Workshop, San Francisco CA USA o 1996 ACM O-89791-867-3/96/10 ..%3.50 280 usefulness of software process models [I]. On the one hand process models are used to capture the current software development knowledge and practices in order to improve them (descriptive software process modeling). On the other hand software process models are used to provide automated support; the models are interpreted by a process engine as part of a process-sensitive software engineering environment (prescriptive software process modeling). Many different languages to express software process models have been developed or adapted from the product world (e.g., design languages as well as programming languages) [ 181. For each agent assuming a role in a project, a role-specific process model (i.e., view) might be developed. The role-specific formalization of process models leads to different views of the processes. Because the roles collaborate, some information is common in the views of different roles. Thus the software process models related to several roles should be integrated in order to allow for better coordination on basis of a consistent and less redundant software process model. Such an explicit representation of processes performed by multiple roles is called a comprehensive software process model (see upper part of Figure 1). The integration is analogous to approaches in product world like database schema integration [2], viewpoints [8], or the works about specification integration by Feather [7], Leite [14], or Robinson [ 173. A comprehensive software process model can be used to repre sent all important processes of a software development project, In this case, it serves as a basis of a central information system to guide, coordinate, and support the different roles (see lower part of Figure 1). This is comparable to the works of Estublier and Belkhatir [6], or Jacobs and Marlin [12]. This paper discusses the application of multi-view technology for supporting software development processes. First results of a method for building a comprehensive software process model by integration of role-specific views are presented. Open questions about the integration are’ listed at the end to point out future research directions. 2 A Working Definition of View In both modeling and use, view mechanisms can be helpful by reducing the overall information to manageable parts and providimplicit process in real world and views thereof

About views for modeling software processes in a role-specific manner

Creating Process-Agents incrementally by mining process asset library

Current interest in improving the effectiveness and predictability of software development has led to a recent focus on software process modeling and improvement. Process-centered software development environments (PCSDEs), have been examined as a useful adjunct to software process modeling. A number of PCSDEs have been designed and built; an examination of the range of potential users of such environments reveals a wide range of needs with respect to information about an enacted software process and how this information is presented. This paper describes one aspect of a PCSDE supporting multiple simultaneous views: the design of a representation of enacted software processes which is suitable for the generation of multiple simultaneous views.

/pdf/software-process-representation-to-support-multiple-views-3uxqow0kc4.pdf

Software process representation to support multiple views

Current interest in improving the effectiveness and predictability of software development has led to a recent focus on software process modeling and improvement. Process-centered software development environments (PCSDEs), have been examined as a useful adjunct to software process modeling. A number of PCSDEs have been designed and built; an examination of the range of potential users of such environments reveals a wide range of needs with respect to information about an enacted software process and how this information is presented. The paper describes one aspect of a PCSDE supporting multiple simultaneous views: the design of a representation of enacted software processes which is suitable for the generation of multiple simultaneous views. >

/pdf/software-process-representation-to-support-multiple-views-2ktujou33x.pdf

The use of Process Centred Software Development Environments (PCSDEs) promises much to the software development, community. By allowing software development processes to be defined and followed accurate measurement of the process can be taken. These measurements will allow improvements to be made on the basis of objective evidence rather than subjective feel. Thus, the deployment, and use of PCSDEs will assist in the attainment of process improvement goals, through greater assurance that defined processes are being followed and that the process from which metrics information is being collected is indeed the process which was described. It is clear, though, that there are many classes of users for such PCSDEs, ranging from project, managers to individual software engineers. Each of these potential users will have a different perspective of the software development process and hence will need to be presented with different views of this process as it is enacted. This paper describes progress towards a multiple view PCSDE designed using the MultiView architecture. Particular attention is paid to the canonical representation of process employed and the derivation of views from this representation.

Multiple view software process support using the MultiView architecture

Handle everyday research tasks with reliable, citation-backed results

Your personal Research Agent to handle research tasks with citation-backed results

Popular Tasks used by Researchers

How can I help with your research?

Meet SciSpace

Get more enhanced response by uploading the PDFs you want me to reference.

No relevant PDFs in your library

SciSpace is the AI research assistant for academics. Run systematic literature reviews on 280M+ papers, and write papers with cited sources. Trusted by 1M+ students, PhDs & researchers.

SciSpace | AI for Research

Analyze PDFs

Code & Manuscripts

Funding & Grants

Literature & Patents

Medical & Clinical Data

Systematic Review

Visualize & Present

Web & Data

Build a Google Scholar-like website for your research.

Build a website

Create charts and images for your research

Create a Chart

Write a paper for submission to a journal

Draft a manuscript

Patent Search

Design eye-catching scientific posters in minutes.

Scientific Poster Generation

Systematic Literature Review

One task is running at the moment. Your messages will be shown right after.

Drag and drop or click here to browse

Loved by <highlight>1 million+</highlight> researchers

Extract a list of specific topics and their sources from unstructured text

Topics

Compare and analyze relevant papers that matches with your search

Papers

Get insights from PDFs and bookmarked papers from your library

My library

Recent searches

Try searching for:

Catch AI-generated content in scholarly and non-scholarly content

{ai} Detector

Ai Writer

Get PDF Summaries, highlighted text explanations 

Chat with PDF

Effortlessly create in-text citations and bibliographies in APA and 2,500 other formats

Citation generator

Get explanations, summaries, and answers on academic papers

Ease up your research workflow with {scispace}'s cohort of exciting AI tools

Elevate your academic writing skills and convey your ideas the way you want

Paraphraser

Explore our range of reading and writing tools

Your file is being prepared and should be ready in a few minutes. If it's a large file, it might take a bit longer. You can close this window, and we'll email you the file when it's done.

You have reached a maximum limit of <strong>{limit}</strong> columns in the table. Remove at least <strong>1</strong> column to add or create another one.

David Jacobs

Author Tools

Chat about Author

Papers

Software process representation to support multiple views

Software process representation to support multiple views

Multiple view software process support using the MultiView architecture