Page 1 of 6Free preview · 1–5

About this document

This paper introduces ßMACH (Systematic Software Management Approaches Characterization Helper), a protocol for systematically describing and comparing software artifact management strategies. It illustrates a performance-focused subset of the protocol using Scrum and the V-model, organizing their descriptions around product knowledge, demanded knowledge, roles, and process knowledge. The comparison highlights differences in requirements, artifacts, knowledge transformations, and management responsibilities. The paper presents an early discussion of the approach rather than a completed evaluation.

Free preview text

The first 5 pages, shown as text so search engines and readers can find this document.

Page 1

ßMACH — A Software Management Guidance Marcus Hilbrich1, Fabian Lehmann1 1Humboldt-Universität zu Berlin, Unter den Linden 6, 10099 Berlin, Germany Abstract Creating, maintaining, and operating software artifacts is a long ongoing challenge. Various manage- ment strategies have been developed and are frequently used. Nevertheless, a unification of describing the management strategies to compare them is an open question. We present ßMACH as an answer. ßMACH allows systematic descriptions and checks independently from the management strategy. In this paper, we test parts of ßMACH on the example of performance requirements. So we applied ßMACH to V-Model and Scrum. Keywords ßMACH, software management, software process model, software artifact, software engineering 1. Introduction From a software engineer’s perspective, software artifacts like source code, executable, and documentation need an active management. How to achieve this is an open, but frequently discussed question [1, 2]. Software process models are commonly used to manage software artifacts, as well as the software life cycle [3, 4]. Well-known examples for software process models are the V-model [5, 6] and Scrum [7]. Thus, the need to manage software artifacts is known for a long time, and different strategies have evolved [8, 9]. Never the less much is unclear: 1) The software life cycle demands that software artifacts are, e.g., changed, and maintained. The V-model aims to deliver the software to the buyer, so it does not include maintenance or later changes. Scrum describes the management of a software project. A project is limited in time, so ongoing maintenance or changing the software is not directly covered. Some DevOps [10, 11] strategies use Scrum like proceedings to overcome these limitations, so it seems to be an open demand. As a result, it is unclear which phases of the software life cycle need to be covered or when the management of software artifacts should be started or ended. 2) The demanded performance of a system or a component should be adequate to use the system [9]. To use the V-model, we have to specify the performance before starting the software development. Therefore, we use, e.g., requirement engineering to find out the needed performance and a usable description. We can test the demands later on. In SSP’21: Symposium on Software Performance, November 09–10, 2021, Leipzig, Germany £ marcus.hilbrich@informatik.hu-berlin.de (M. Hilbrich); fabian.lehmann@informatik.hu-berlin.de (F. Lehmann) DZ 0000-0003-3717-9449 (M. Hilbrich); 0000-0003-0520-0792 (F. Lehmann) © 2021 Copyright for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).CEUR Workshop Proceedings http://ceur-ws.org ISSN 1613-0073 CEUR Workshop Proceedings (CEUR-WS.org)

Page 2

Scrum, we define the system by user stories (in the backlog). However, an office user will not specify the time he can wait for a request to finish, the acceptable probability of requests taking longer, and the hardware infrastructure a cloud operator has to provide. Accordingly, it is uncommon to have a performance definition in the backlog. So, the performance needs to be estimated during the Scrum process, discussed with the buyer, or other roles. As a result, it is not clear how to describe the product or its performance. Luckily, various ideas on how to manage software artifacts exist. While V-model, Scrum, and Software life cycle are just basic examples, change management [12, 13], mi- croservices [14], usage of best practices as given by Martin [15], or the use of results from Human Resource Management [16] are additional and well-known strategies. However, it is unclear how to describe the management in a uniform language, compare management proceedings based on standards, or survey a management method. We propose the Systematic Software Management Approaches Characterization Helper (ßMACH), it is at least a partial answer to the ongoing challenges of software artifacts’ management. ßMACH groups key aspects for software management based on an ontol- ogy to describe a software management proceeding systematically. Thereby, ßMACH defines a uniform description/language and starting point for future comparisons and analysis of management strategies. This paper uses (parts of) ßMACH to look into performance management exemplarily for the V-model and Scrum. We describe the fill- ing of the ßMACH protocol to introduce it and better understand the software process models. This paper serve as an early discussion point on ßMACH and its capabilities. 2. The ßMACH Protocol ßMACH is a guidance protocol throughout the software development process or other software artifact management strategies. It offers the key aspects of management in a protocol and connects them. Therefore, ßMACH uses specific wording-terms mostly based on knowledge management to bring different management approaches to a com- mon denominator. This enables the ßMACH method to work with various software development frameworks, software process models, agile management strategies, artifact based proceedings, etc. In particular, the ßMACH protocol consists of three parts: 1) A section of metadata to describe and identify the management proceeding based on the team involved, the product, the company, date of filling the protocol, etc. 2) A short description of the management framework used and how it works. Probably by the tailoring of well-known strategies. 3) A table of aspects that have to be handled by any proceeding filled with answers. The ßMACH protocol guides the filling person through asking different predefined ques- tions concerning all possible software artifacts. Thereby, the ßMACH protocol ensures that all key aspects of the software artifact management process are considered. In this paper, we take a deeper look at the abilities of the ßMACH protocol to de- scribe and explain performance characteristics, requirements, and solutions in a software development process. To underline the generality of ßMACH, we look at Scrum as a rep- resentative for agile and the V-model for non-agile development processes. Accordingly,

Page 3

we only discuss a small subset of the ßMACH protocol focusing on performance. An excerpt of the ßMACH protocol is depicted in Fig. 1. The protocol itself does not prescribe the table’s filling order. In the following, we discuss four of the five columns of ßMACH, to distinguish different origins of knowledge. In general, the ßMACH method gives five columns to describe all key aspects within a software development process, where it is mandatory to fill all cells. We start with a discussion of Scrum, in concrete we start with a description of artifacts, this knowledge is given by ßMACH in the row Product Properties (see Fig. 1). The first column is Product Knowledge. It contains all knowledge that is needed to describe software artifacts. E.g., for Scrum, this is the Sprint Backlog, as knowledge of the Sprint Backlog is enough to complete a Sprint and get the software artifact in a more complete state. The next column in ßMACH is Demanded Knowledge. As Sprint Backlogs are not ini- tially available, they are Demanded Knowledge by ßMACH’s definition, which indicates that this knowledge must be defined over time. Next, ßMACH offers a column for the Roles. Here, all roles are named that provide knowledge to a process of the software artifact lifecycle. Within the development process, these are the developers, as they know how to extend the product. Furthermore, ßMACH names the Process Knowledge. This knowledge comprises all information to perform the process that realizes the product properties. For example, in Scrum, we have to define where the Sprint Backlog comes from. It is developed based on the Product Backlog, thus it is based on the Product Knowledge, which we have to describe, too. The product backlog is not directly a description of the product (even if used to create the Sprint Backlog). Instead, it is a list of items we have confirmed to realize. Thus, it is a responsibility in terms of ßMACH. The Product Backlog is not a stable artifact. It is developed by the complete Scrum team based on discussions – this gives the Demanded Knowledge, the Roles, and the Process. The missing link is how to get from the Product Backlog to the Sprint Backlog. The Scrum team creates the Sprint Backlog in a discussion, where it defines Processes, Roles, Product Knowledge, and Demanded Knowledge. In the following, we describe performance in the ßMACH protocol: The column where performance is defined varies with the paradigm used. Since performance definition is part of the discussion in Scrum, it is defined as an important aspect of an item in the Sprint Backlog, or it can be a more general demand as an item of the Product Backlog. Accordingly, performance is Product Knowledge but can be Demanded Knowledge, too. Contrary to Scrum, the V-model immediately starts with a Requirements Document. Based on the document, Software Designs are created (by different phases of the V- model), and the last Software Design is fine enough to start programming. Tests are defined parallelly based on Software Designs and Requirements. Moreover, a team is responsible for fulfilling the requirements in the Requirements Document. The V-model’s requirements, and thus the performance, are initially defined and can- not be changed over time. So, this is the definition of the product to deliver. Accordingly, it is Product Knowledge of the Outside Responsibilities. As the document is present initially, no Demanded Knowledge is required for Product Properties. The respected knowledge is addressed in the rows for Product Properties in the table of ßMACH. The

Page 4

Product Knowledge Demanded Knowledge Roles Process Knowledge Explanation for Aspects the Team is Responsible for: Inside Product Proper- ties No other team exists in the ex- ample, so nothing to know. No product knowledge, so no demanded knowledge No product knowledge, so no roles needed No product knowledge, so no process needed Outside Product Prop- erties Software Designs Software Designs needs to be developed Each phases can use a own team, capable of performing the process Refinement of the Require- ments Document or a Software Design from phase before Programming Testing based on Software De- signs Inside Responsibilities No other team exists in the ex- ample, so nothing to know. No product knowledge, so no demanded knowledge No product knowledge, so no roles needed No product knowledge, so no process needed Outside Responsibili- ties Requirements Document The knowledge/requirements is known in before nothing to do, requirements are fixed nothing to process, require- ments are fixed Page 1(a) Description of the V-model.Product Knowledge Demanded Knowledge Roles Process Knowledge Explanation for Aspects the Team is Responsible for: Inside Product Proper- ties Sprint Backlog Sprint Backlog, new for each sprint Developer, Scrum Team Developers process items of Sprint Backlog, Discussion of Sprint Backlog based on Product Backlog (also perfor- mance) Outside Product Prop- erties All stakeholder are part of the team, so nothing to know. No product knowledge, so no demanded knowledge No product knowledge, so no roles needed No product knowledge, so no process needed Inside Responsibilities No other team exists in the ex- ample, so nothing to know. No product knowledge, so no demanded knowledge Scrum Team Discussion (also performance) Outside Responsibili- ties Product Backlog Product Backlog needs to be created and can change No product knowledge, so no roles needed No product knowledge, so no process needed Page 1 (b) Description of Scrum. Figure 1: Given are descriptions of software process models based on a subset of the ßMACH protocol. ßMACH defines a set of key aspects to describe. Each cell of the table represents an aspect. ßMACH defines a coloring. Based on the management proceeding, light green is used for aspects that do not need active management (the aspect is realized without a need for actions). Darker green indicates an aspect that is provided by another aspect without a need for active management. Violet is used for aspects that are used or require by additional aspects. Such an aspect is likely of special interest. Arrows with a peak-end describe based on which other aspect an aspect is provided. An arrow with a round-end gives a demand relation. The other aspect needs the aspect at the round-end. The aspects in the tables are described in the paper, the filling of the aspects, too. protocol contains these rows for Inside and Outside Product Properties, where Inside means a joined work of teams on the same project, while outside describes a product dealing with an external party. The requirements are then tested by the buyer, so we do not need to process the responsibilities and do not need a special role to do so. The design phases of the V-model produce Software Designs, and these are Product Knowledge of the Product Properties. It needs to be created by performing the V-model, so it is also Demanded Knowledge based on a refinement of the Requirements Document or a Software Design (see Fig. 1). 3. Observations Due to the focus on performance, we only had a minimal look at ßMACH in the last section. Thus, many aspects of ßMACH are ignored, like interfaces, dependencies, in- formation recording, maintenance, and product improvement. Nevertheless, we got a comparison of Scrum and the V-model, and we can obtain the following observations:

Page 5

First, the V-model defines performance based on the initial requirements document that is not changed later on. In Fig. 1a the requirements document is a direct or indirect knowledge source for many aspects/cells in ßMACH. As a result, refining the design process, programming, and testing has to consider the performance-based requirements. Contrary, Scrum discusses the performance aspects within the Scrum team, including, e.g., buyers, and users. The product backlog is demanded by a process in Fig. 1b. Second, different rows are filled within the ßMACH protocol to describe the manage- ment (see Fig. 1a and 1b). While the V-model uses the rows marked as outside, Scrum uses the rows marked as inside. This is a direct representation of different management philosophies. Scrum includes buyers, users, etc., while the V-model does not. Third, while the Scrum process (Process Knowledge) is mainly based on discussions, the V-model relies on refinement and testing. Despite these differences, both software process models provide a set of artifacts to represent the product knowledge. While this was expected for an artifact-based software process model like the V-model, it also applies to Scrum using the Backlogs. However, Scrum has less of such artifacts, but the artifacts seem to be an essential part. Forth, we can identify shortcomings of the management strategies or the representation of the strategies in this paper. The principle description of the V-model does not give a detailed description of the roles and the proceeding in the phases. In Scrum, processes are based on discussions, or the team knows how to do them. This describes a lack of information about the concrete process and problems of knowledge persistence, e.g., to compensate changes in the team. The presented observations are neither new findings nor unexpected. The important aspect is, the findings are directly based on the ßMACH protocol. Thus, we can exemplify that the ßMACH protocol helps to represent and understand management strategies. Also, a comparison is enabled by the aspects/cells of the ßMACH protocol and the knowledge transformations described in Fig. 1a and 1b. 4. Conclusion This paper gives only a coarse introduction to ßMACH. It does not yet provide findings for a customized software management process, tool-based management of performance, or a model-based development. Therefore, a detailed introduction to ßMACH and the ac- cording discussion of software management principles are in progress. A first evaluation of ßMACH is prepared, too. As an immediate step, we collect additional input. Based on the observations we have provided, ßMACH can explain how knowledge is transformed and represented by software management strategies. Furthermore, ßMACH can clearly distinguish between different management strategies. Even if knowledge sources or representation artifacts are not described as a major part of a management process, by the idea of process-centric management, the importance of such artifacts and shortcomings in management are identified by the ßMACH protocol. Even if the used examples are well understood and the observations are nothing new, we can state the representation of the findings by ßMACH. Furthermore, we expect

Tags

Doxxly editorial guide

ßMACH - A Software Management Guidance: summary, contents and background

This guide helps you understand the scope of ßMACH - A Software Management Guidance before or alongside reading the original document. It is based on the catalogue record, credited creator, source, classification and topics shown on this page. It does not replace the original work and does not invent claims about passages that Doxxly cannot verify.

Summary and overview

ßMACH - A Software Management Guidance is a 6-page documentcredited to Wren N. Lannister. This paper introduces ßMACH (Systematic Software Management Approaches Characterization Helper), a protocol for systematically describing and comparing software artifact management strategies. It illustrates a performance-focused subset of the protocol using Scrum and the V-model, organizing their descriptions around product knowledge, demanded knowledge, roles, and process knowledge. The comparison highlights differences in requirements, artifacts, knowledge transformations, and management responsibilities. The paper presents an early discussion of the approach rather than a completed evaluation. It appears in the Technology & Security collection, which groups it with other material that readers may use for comparison and further study.

The item can be approached in several ways. A reader looking for a quick orientation can begin with the free five-page preview, inspect the page structure and use the metadata to judge relevance. Someone undertaking deeper research can work through the complete file, search its indexed text, record useful page references and compare its treatment of ßMACH, software management, software process models, software artifacts, software engineering, performance requirements, Scrum, V-model, knowledge management with the related resources linked below.

Rather than reducing the work to a single claim, this page treats it as a source that should be read in context. The title, creator, publication source, licence and format all help explain what kind of evidence it may offer. Readers should distinguish the original author's statements from Doxxly's catalogue description, and should cite the original edition when using the material in academic, professional or published work.

Key topics and reader takeaways

The catalogue connects this document with ßMACH, software management, software process models, software artifacts, software engineering, performance requirements, Scrum, V-model, knowledge management. These terms offer practical entry points rather than a substitute for close reading. Start by identifying the definitions, examples, arguments, tables or visual explanations attached to each topic. Then note where the creator draws connections, makes distinctions or moves from background material to a conclusion, recommendation, calculation or narrative development.

A useful reading method is to separate description from interpretation. First record what the item actually presents: names, headings, figures, formulas, quotations or stated propositions. Next consider why those details matter within the whole work. Finally compare them with another source from the same subject area. This process helps turn a long digital file into evidence that can be evaluated rather than merely skimmed.

Table of contents and reading guide

The following is an editorial content guide based on the verified catalogue topics. It is not represented as the original author's formal table of contents. Use it to organise notes while moving through the 6 pages in the player.

  1. Part 1

    ßMACH

    Use this section of the reading guide to identify how ßMACH appears in ßMACH - A Software Management Guidance, note important terms, and connect the subject to the wider purpose of the work.

  2. Part 2

    software management

    Use this section of the reading guide to identify how software management appears in ßMACH - A Software Management Guidance, note important terms, and connect the subject to the wider purpose of the work.

  3. Part 3

    software process models

    Use this section of the reading guide to identify how software process models appears in ßMACH - A Software Management Guidance, note important terms, and connect the subject to the wider purpose of the work.

  4. Part 4

    software artifacts

    Use this section of the reading guide to identify how software artifacts appears in ßMACH - A Software Management Guidance, note important terms, and connect the subject to the wider purpose of the work.

  5. Part 5

    software engineering

    Use this section of the reading guide to identify how software engineering appears in ßMACH - A Software Management Guidance, note important terms, and connect the subject to the wider purpose of the work.

  6. Part 6

    performance requirements

    Use this section of the reading guide to identify how performance requirements appears in ßMACH - A Software Management Guidance, note important terms, and connect the subject to the wider purpose of the work.

  7. Part 7

    Scrum

    Use this section of the reading guide to identify how Scrum appears in ßMACH - A Software Management Guidance, note important terms, and connect the subject to the wider purpose of the work.

  8. Part 8

    V-model

    Use this section of the reading guide to identify how V-model appears in ßMACH - A Software Management Guidance, note important terms, and connect the subject to the wider purpose of the work.

When a heading in the original differs from this guide, follow the original heading in your citation. Page numbers can also vary between editions. Doxxly's direct page field is useful for navigation, but formal references should include the title, creator, source and edition details available in the file itself.

About Wren N. Lannister

Doxxly credits Wren N. Lannister as the author or creator of ßMACH - A Software Management Guidance. This page does not add an unverified biography, job title or institutional affiliation. The attribution is preserved so readers can distinguish the creator from the hosting library and follow the original record when an external author link is available.

Author context matters because a work reflects a particular purpose, audience and point of view. Before relying on the material, consider what the creator set out to explain, when the source was produced and whether later research or revised guidance should also be consulted. For literature and philosophy, compare translations and editions; for technical material, check whether a newer version has superseded the one shown here.

About the source organisation

The recorded source for this item is ceur-ws.org. Doxxly provides access and discovery tools but does not claim to be the original publisher unless explicitly stated. Source links, creator attribution and the recorded Publicly available file collected for editorial review licence are displayed to help readers assess provenance and permitted use.

Provenance is especially important for reports, standards, presentations and working spreadsheets. Check the original source for amendments, supporting files and current policy. A trustworthy research workflow keeps the source URL with any notes or downloaded copy, verifies important figures against the original, and avoids treating an archived document as automatically current.

Visit ceur-ws.org

How to read and use this document

Begin with the title and opening pages, then use the guide above to decide whether to read sequentially or move to a particular topic. The Doxxly player provides previous and next navigation, a direct page field, zoom steps, fit-to-width and fit-to-page modes, rotation and fullscreen. These controls are useful when a page contains small type, a wide table, an image, a scanned layout or a dense sequence of notes.

The first five pages are open to every visitor. A plan unlocks the complete item and full-document search. Search is best used for distinctive names, technical terms or short phrases; broad words can produce too many possible contexts. When you find a useful passage, read the surrounding pages so that a sentence, chart or formula is not separated from its explanation.

If downloading is enabled, members can obtain the original PDF file. Keep the original format when formulas, slide sequencing, pagination or layout carries meaning. Respect the Publicly available file collected for editorial review terms displayed on this page, and use the rights-report link if you believe the attribution or availability needs review.

Research questions to consider

As you read ßMACH - A Software Management Guidance, ask which audience the creator addresses, what problem or idea organises the work, what evidence is presented, and which assumptions remain unstated. Note whether important terms are defined consistently and whether examples represent a broader pattern or a narrow case. For quantitative material, record units, time periods, formulas and data sources. For interpretive material, separate the creator's language from your own summary.

A second set of questions concerns relevance today. Which parts remain durable, which depend on their historical or institutional setting, and what would need confirmation from a newer source? Following the tags and the Technology & Security collection can reveal useful comparisons. Agreement between sources can strengthen confidence, while disagreement can point to changing definitions, methods, evidence or priorities.

Finally, decide what you need from the item: background knowledge, a quotation, a worked example, a model, a visual explanation or a starting bibliography. That purpose should guide the depth of reading and the notes you keep. Doxxly helps locate and navigate the source; careful interpretation remains the reader's responsibility.

Explore more Technology & Security resources

Frequently asked questions about ßMACH - A Software Management Guidance

Practical answers about reading, downloading and understanding this document on Doxxly.

More in Technology & Security