Case Study: Mylyn Reviews for Software Development in Air Traffic Management
•
1 like•706 views
This document summarizes a case study on the use of Mylyn Reviews, a code review plugin for Eclipse, at Frequentis AG. Frequentis is a safety-critical systems developer located in Vienna that adopted Mylyn Reviews' task-based review (TBR) implementation. TBR allows reviews to be performed per development task and stored as sub-tasks in a bug tracker without extra server infrastructure. Frequentis created custom plugins for TBR to recommend reviewers, track review and changeset status, and generate reports on review coverage required by their software development standard. A demo of the TBR implementation at Frequentis is available online.
Report
Share
Report
Share
Download to read offline
Recommended
poster_3.0
This study aimed to identify commit categories in large open source projects that have a high chance of introducing software bugs and to build prediction models to identify risky commits. The researchers categorized commits, extracted metrics like developer experience and lines of code changed, and used those to create models that predicted risky commits with reasonable recall and precision, varying by commit category.
Software metrics
Software metrics are quantitative measurements used to highlight areas of code that need improvement and provide an overall assessment of code quality. They can measure aspects like lines of code, complexity, and test coverage. However, metrics can be difficult to calculate precisely and may not provide a full picture, especially for code early in development. Examples of common metrics include lines of code, classes and interfaces, code to comment ratio, and bugs to lines of code.
Robustness testing
The document discusses robustness testing of flight software using fault injection. It describes preparing and executing tests, analyzing logs and documenting results. Tests of VxWorks APIs and directives were conducted on over 300 functions and 70 routines. Automation tools were used to generate test cases and scripts to save time and money. The research aimed to transition robustness testing tools and lessons learned to NASA and contractors.
Integration testing overview
Upon finishing device testing, the models or segments are to be incorporated which gives raise to integration testing. The objective of integration testing is to ensure the effective, efficiency, and stability between the segments that are incorporated.
Beyond Static Analysis: Integrating .NET Static Analysis with Unit Testing a...
Learn the strengths and weaknesses of .NET static analysis—and how a comprehensive development testing strategy that also includes unit testing, code review, and runtime error detection can pick up where development testing leaves off.
Introduction to Software Engineering 1
This document discusses software testing strategies. It begins by defining software testing as executing a software system to find errors prior to delivery. It then outlines different testing approaches including unit testing, integration testing, validation testing, and system testing. Unit testing focuses on exercising individual software components to detect errors. The document emphasizes that developers and independent test groups must work together throughout a project to ensure thorough testing. It provides examples of what unit testing should evaluate like module interfaces and data integrity. The overall strategies aim to verify proper integration and that requirements are met across the full system.
Testing throughout the software life cycle
1. The document discusses software development models and testing levels. It describes the waterfall model as one of the earliest models and its sequential process.
2. It then discusses iterative life cycles and characteristics of good testing including having corresponding testing activities for each development activity.
3. The document also outlines different testing levels from component and integration testing to system and acceptance testing. It provides details on the focus and goals of each testing level.
Run time Verification using formal methods
Runtime verification is a technique to check if a system satisfies given correctness properties by monitoring its execution. It involves lightweight monitoring of a system at runtime to identify incorrect behavior. There are three main types of verification: theorem proving, model checking, and testing. Runtime verification monitors systems to check if the actual behavior matches the expected behavior according to contracts or specifications. It can identify failures and additional code can then react, such as displaying error messages.
Recommended
poster_3.0
This study aimed to identify commit categories in large open source projects that have a high chance of introducing software bugs and to build prediction models to identify risky commits. The researchers categorized commits, extracted metrics like developer experience and lines of code changed, and used those to create models that predicted risky commits with reasonable recall and precision, varying by commit category.
Software metrics
Software metrics are quantitative measurements used to highlight areas of code that need improvement and provide an overall assessment of code quality. They can measure aspects like lines of code, complexity, and test coverage. However, metrics can be difficult to calculate precisely and may not provide a full picture, especially for code early in development. Examples of common metrics include lines of code, classes and interfaces, code to comment ratio, and bugs to lines of code.
Robustness testing
The document discusses robustness testing of flight software using fault injection. It describes preparing and executing tests, analyzing logs and documenting results. Tests of VxWorks APIs and directives were conducted on over 300 functions and 70 routines. Automation tools were used to generate test cases and scripts to save time and money. The research aimed to transition robustness testing tools and lessons learned to NASA and contractors.
Integration testing overview
Upon finishing device testing, the models or segments are to be incorporated which gives raise to integration testing. The objective of integration testing is to ensure the effective, efficiency, and stability between the segments that are incorporated.
Beyond Static Analysis: Integrating .NET Static Analysis with Unit Testing a...
Learn the strengths and weaknesses of .NET static analysis—and how a comprehensive development testing strategy that also includes unit testing, code review, and runtime error detection can pick up where development testing leaves off.
Introduction to Software Engineering 1
This document discusses software testing strategies. It begins by defining software testing as executing a software system to find errors prior to delivery. It then outlines different testing approaches including unit testing, integration testing, validation testing, and system testing. Unit testing focuses on exercising individual software components to detect errors. The document emphasizes that developers and independent test groups must work together throughout a project to ensure thorough testing. It provides examples of what unit testing should evaluate like module interfaces and data integrity. The overall strategies aim to verify proper integration and that requirements are met across the full system.
Testing throughout the software life cycle
1. The document discusses software development models and testing levels. It describes the waterfall model as one of the earliest models and its sequential process.
2. It then discusses iterative life cycles and characteristics of good testing including having corresponding testing activities for each development activity.
3. The document also outlines different testing levels from component and integration testing to system and acceptance testing. It provides details on the focus and goals of each testing level.
Run time Verification using formal methods
Runtime verification is a technique to check if a system satisfies given correctness properties by monitoring its execution. It involves lightweight monitoring of a system at runtime to identify incorrect behavior. There are three main types of verification: theorem proving, model checking, and testing. Runtime verification monitors systems to check if the actual behavior matches the expected behavior according to contracts or specifications. It can identify failures and additional code can then react, such as displaying error messages.
Fostering MBSE in Engineering Culture
Thales has been deploying Arcadia and Capella MBSE methods and tools for the past 15 years. As for any journey, there have been many joys and not less difficulties.
During this webinar, Thales presents the foundations of their MBSE approach, how their engineering practices have been improved with the use of models, and what are they doing now to sustain and drive this model-based transformation.
---------
This webinar was driven by Juan Navas (from Thales)
Juan Navas is a Systems Architect with +10 years’ experience on performing and implementing Systems Engineering practices in industrial organizations. He accompanies systems engineering managers and systems architects implement Model-Based Systems Engineering and Product Line Engineering approaches in operational projects, helping them defining their engineering strategies, objectives and practices.
Supporting Change Impact Analysis Using a Recommendation System - An Industri...
Journal first presentation at ICSE'17 in Buenos Aires, Argentina.
M. Borg, K. Wnuk, B. Regnell, and P. Runeson. Supporting Change Impact Analysis Using a Recommendation System: An Industrial Case Study in a Safety-Critical Context, IEEE Transactions on Software Engineering, 43(6), pp. 675-700, 2017.
Splitting the Check on Compliance and Security
1) Developers prioritize speed and innovation while auditors focus on compliance and predictability. The resolution is adopting tools like Spinnaker that provide traceability in development pipelines to satisfy both groups.
2) Tools like Penguin allow continuous monitoring of application security risks across microservices rather than one-time assessments.
3) Compartmentalization through practices like tokenization and microservices limits the impact of breaches by restricting access on a need-to-know basis.
Splitting The Check On Compliance and Security
Often times, developers and auditors can be at odds. The agile, fast-moving environments that developers enjoy will typically give auditors heartburn. The more controlled and stable environments that auditors prefer to demonstrate and maintain compliance are traditionally not friendly to developers or innovation. We'll walk through how Netflix moved its PCI and SOX environments to the cloud and how we were able to leverage the benefits of the cloud and agile development to satisfy both auditors and developers.
Sa 009 add
This document discusses Attribute Driven Design (ADD), which is an approach for designing software architectures based on quality attributes. It covers the following key points:
1. ADD is a recursive design process that involves identifying architectural drivers, choosing design concepts to satisfy the drivers, and instantiating architectural elements.
2. The ADD process has 7 steps: requirements information, element selection, identifying architectural drivers, choosing design concepts, instantiating elements, defining interfaces, and verification.
3. An example of applying ADD to design an automotive platform architecture is provided to illustrate the steps. Modifiability is identified as a key driver, and the model-view-controller pattern is chosen to support it. Elements are then instantiated
Simplify and Scale Enterprise Spring Apps in the Cloud | March 23, 2023
- Azure Spring Apps is a fully managed service for deploying and managing Spring Boot apps in the cloud without having to learn or manage Kubernetes. It provides auto-scaling, security, high availability, and auto-patching capabilities.
- Managing software updates and security patches across multiple components like apps, dependencies, JDKs, OSes, Kubernetes, etc. is challenging due to the large volume of updates and need for testing and approvals. Azure Spring Apps reduces this burden through auto-patching which applies critical security updates automatically during scheduled maintenance windows.
- Auto-patching helps customers stay ahead of security threats and vulnerabilities by proactively applying patches for exposed issues like Log4j, OpenSSL vulnerabilities,
Energy and engineering services leverages growth
Hexaware provided comprehensive testing and automation services to help a leading global provider of energy and engineering services achieve its business objectives. This included implementing a life cycle model, tracking metrics and service level agreements, and planning test automation. Hexaware analyzed the client's energy and engineering applications, prepared test cases, and conducted defect management using Microsoft Visual Studio Team Services. This helped the client maintain quality standards, provide transparency, and have resources available during critical releases.
Spm unit 3
The document discusses the four phases of the software development lifecycle: inception, elaboration, construction, and transition. It provides details on the objectives and essential activities of each phase. The inception phase focuses on establishing scope and demonstrating architecture. The elaboration phase builds prototypes and baselines requirements, architecture, and plans. Construction integrates components and tests features. Transition deploys the software to end users through activities like beta testing and training. The document also discusses engineering artifact sets for managing development, including management, requirements, design, implementation, and deployment artifacts.
In-kernel Analytics and Tracing with eBPF for OpenStack Clouds
As the movement of applications from bare metal to the cloud continues, considerations around analytics and tracing are becoming more prevalent for security, monitoring, and accounting. As an open source project under the Linux Foundation, the IO Visor Project is working with the kernel community on extending BPF (eBPF) and is being used by many companies for security, tracing, and analytics. This talk will describe how an OpenStack micro-segmentation framework using eBPF can be utilized for analytics and tracing to secure application workloads. Use cases around application security, intrusion detection using service insertion, identity will be described. While networking is one piece of the solution, sandboxing applications to avoid attacks is also important. We will also touch upon how eBPF technology and a unified policy framework can secure application workloads in areas beyond networking.
Case Study - AMR Test Automation
The client is a leading security technology company that develops an anti-malware product (AMR) to protect against malware and rootkits. With over 1600 manual test cases across operating systems, regression testing was challenging. The client sought to automate testing and create a reusable framework. iFocus Systec developed a Perl-based framework using Selenium for browser tests and AutoIT for GUI tests. This automated over 70% of test cases and reduced test cycles by 55%, providing a maintainable and reusable solution.
Optimizing Monitorability of Multi-cloud Applications
This document proposes an approach to optimize the monitorability of applications deployed across multiple cloud providers. It aims to maximize the number of application metrics that can be monitored while minimizing costs, based on each cloud provider's monitoring capabilities. A matchmaking algorithm finds the best deployment by considering users' monitoring requirements, providers' offered metrics and costs, and estimating metrics that are not directly measurable. The approach was validated on a sample deployment and showed response times around 19 seconds for optimizing monitoring of 4 VMs with 7 metrics each across 7 cloud providers.
Software Process Model
This document discusses three software process models: the waterfall model, incremental development, and reuse-oriented software engineering. The waterfall model represents the software development process as sequential phases such as requirements, design, implementation, testing, and maintenance. Incremental development interleaves these phases and develops the system in a series of versions that add new functionality. Reuse-oriented engineering focuses on integrating existing reusable components rather than developing everything from scratch.
OSSF 2018 - Brandon Jung of GitLab - Is Your DevOps 'Tool Tax' Weighing You D...
The document discusses how a single application that handles the entire software development lifecycle can help alleviate the "DevOps tool tax" caused by managing and integrating multiple point solutions. It provides an overview of GitLab's Auto DevOps feature which automates the build, test, security, deployment, and monitoring pipelines in a single system. By consolidating tools and processes, Auto DevOps helps reduce integration complexity and accelerate development cycles.
DevSecOps
Security Automation by integrating SAST(Static Application Security Testing),DAST(Dynamic Application Secuirty Testing) and SIEM (Security Information and Event Management) tools with Jenkins.
By automating Security(SAST,DAST,SIEM) developers can them selves perform VA and monitor on application without going to IT and Security team
Below Tools are used to Automate everything:
SAST - Fortify,CheckMarx
DAST - IBM App Scan,OWASP ZAP,HP Web Inspect
SIEM - Alien Vault
V-Empower Services And Solutions
V-Empower is a global security solutions and services company established in 2000 that provides state-of-the-art security solutions and consulting services through in-depth research and analysis. It offers comprehensive penetration testing, application security assessments, security program development, and training services. V-Empower saw a 206% increase in revenue in 2006 and its security team consists of over 27 consultants worldwide who have been featured in publications and by clients such as Microsoft.
V-Empower Services And Solutions
V-Empower is a global security solutions and services company established in 2000 that provides state-of-the-art security solutions and services through in-depth research, analysis, and knowledge sharing. It offers comprehensive penetration testing, application security assessments, security program development, and training services. V-Empower has experienced significant revenue growth and its security team consists of highly talented experts that provide services to some of the world's largest companies.
Web Application Security for Continuous Delivery Pipelines
Watch on-demand webinar: https://info.avinetworks.com/webinars/web-application-security-continuous-delivery-pipelines
Applications today have evolved into containers and microservices deployed in fully automated and distributed environments across data centers and clouds. Application services such as load balancing, security, and analytics become critical for continuous delivery.
To secure modern web applications, security policies including SSL/TLS, ACLs, IP Reputation, and WAF need to be applied quickly. We will share a reference implementation from Avi Networks.
Join this webinar to learn:
- CI/CD in the web application security context
- Challenges and solutions integrating a modern web application firewall (WAF) into the application development pipeline
- How to create processes that support both security and development requirements
Netflow analyzer- Datasheet
This product brochure summarizes ManageEngine NetFlow Analyzer, a network traffic analysis and security tool. It provides unparalleled network visibility [1] and supports various flow technologies. [2] The tool helps monitor network performance, security threats, and application usage to ensure business critical services run optimally. [3]
Sa 006 modifiability
The document discusses the concept of modifiability in software architecture. It defines modifiability as the ease with which a software system can be modified to changes in requirements, environment, or specifications. It describes aspects that impact modifiability such as what can change, when changes are required, who implements changes, and the cost of changes. It also discusses business concerns related to modifiability and provides examples of modifiability scenarios and quality attribute scenarios. Finally, it outlines tactics to improve modifiability such as reducing module size, increasing cohesion, reducing coupling, and deferring binding time.
Ragha Deepika_Exp_4+
Ragha Deepika has over 4 years of experience in software testing. She has expertise in manual and automation testing using tools like Quality Centre and QTP. She has worked on several projects for Tata Consultancy Services and Aviva testing applications involving technologies like .NET, Oracle, and IBM Mainframes.
More Related Content
Similar to Case Study: Mylyn Reviews for Software Development in Air Traffic Management
Fostering MBSE in Engineering Culture
Thales has been deploying Arcadia and Capella MBSE methods and tools for the past 15 years. As for any journey, there have been many joys and not less difficulties.
During this webinar, Thales presents the foundations of their MBSE approach, how their engineering practices have been improved with the use of models, and what are they doing now to sustain and drive this model-based transformation.
---------
This webinar was driven by Juan Navas (from Thales)
Juan Navas is a Systems Architect with +10 years’ experience on performing and implementing Systems Engineering practices in industrial organizations. He accompanies systems engineering managers and systems architects implement Model-Based Systems Engineering and Product Line Engineering approaches in operational projects, helping them defining their engineering strategies, objectives and practices.
Supporting Change Impact Analysis Using a Recommendation System - An Industri...
Journal first presentation at ICSE'17 in Buenos Aires, Argentina.
M. Borg, K. Wnuk, B. Regnell, and P. Runeson. Supporting Change Impact Analysis Using a Recommendation System: An Industrial Case Study in a Safety-Critical Context, IEEE Transactions on Software Engineering, 43(6), pp. 675-700, 2017.
Splitting the Check on Compliance and Security
1) Developers prioritize speed and innovation while auditors focus on compliance and predictability. The resolution is adopting tools like Spinnaker that provide traceability in development pipelines to satisfy both groups.
2) Tools like Penguin allow continuous monitoring of application security risks across microservices rather than one-time assessments.
3) Compartmentalization through practices like tokenization and microservices limits the impact of breaches by restricting access on a need-to-know basis.
Splitting The Check On Compliance and Security
Often times, developers and auditors can be at odds. The agile, fast-moving environments that developers enjoy will typically give auditors heartburn. The more controlled and stable environments that auditors prefer to demonstrate and maintain compliance are traditionally not friendly to developers or innovation. We'll walk through how Netflix moved its PCI and SOX environments to the cloud and how we were able to leverage the benefits of the cloud and agile development to satisfy both auditors and developers.
Sa 009 add
This document discusses Attribute Driven Design (ADD), which is an approach for designing software architectures based on quality attributes. It covers the following key points:
1. ADD is a recursive design process that involves identifying architectural drivers, choosing design concepts to satisfy the drivers, and instantiating architectural elements.
2. The ADD process has 7 steps: requirements information, element selection, identifying architectural drivers, choosing design concepts, instantiating elements, defining interfaces, and verification.
3. An example of applying ADD to design an automotive platform architecture is provided to illustrate the steps. Modifiability is identified as a key driver, and the model-view-controller pattern is chosen to support it. Elements are then instantiated
Simplify and Scale Enterprise Spring Apps in the Cloud | March 23, 2023
- Azure Spring Apps is a fully managed service for deploying and managing Spring Boot apps in the cloud without having to learn or manage Kubernetes. It provides auto-scaling, security, high availability, and auto-patching capabilities.
- Managing software updates and security patches across multiple components like apps, dependencies, JDKs, OSes, Kubernetes, etc. is challenging due to the large volume of updates and need for testing and approvals. Azure Spring Apps reduces this burden through auto-patching which applies critical security updates automatically during scheduled maintenance windows.
- Auto-patching helps customers stay ahead of security threats and vulnerabilities by proactively applying patches for exposed issues like Log4j, OpenSSL vulnerabilities,
Energy and engineering services leverages growth
Hexaware provided comprehensive testing and automation services to help a leading global provider of energy and engineering services achieve its business objectives. This included implementing a life cycle model, tracking metrics and service level agreements, and planning test automation. Hexaware analyzed the client's energy and engineering applications, prepared test cases, and conducted defect management using Microsoft Visual Studio Team Services. This helped the client maintain quality standards, provide transparency, and have resources available during critical releases.
Spm unit 3
The document discusses the four phases of the software development lifecycle: inception, elaboration, construction, and transition. It provides details on the objectives and essential activities of each phase. The inception phase focuses on establishing scope and demonstrating architecture. The elaboration phase builds prototypes and baselines requirements, architecture, and plans. Construction integrates components and tests features. Transition deploys the software to end users through activities like beta testing and training. The document also discusses engineering artifact sets for managing development, including management, requirements, design, implementation, and deployment artifacts.
In-kernel Analytics and Tracing with eBPF for OpenStack Clouds
As the movement of applications from bare metal to the cloud continues, considerations around analytics and tracing are becoming more prevalent for security, monitoring, and accounting. As an open source project under the Linux Foundation, the IO Visor Project is working with the kernel community on extending BPF (eBPF) and is being used by many companies for security, tracing, and analytics. This talk will describe how an OpenStack micro-segmentation framework using eBPF can be utilized for analytics and tracing to secure application workloads. Use cases around application security, intrusion detection using service insertion, identity will be described. While networking is one piece of the solution, sandboxing applications to avoid attacks is also important. We will also touch upon how eBPF technology and a unified policy framework can secure application workloads in areas beyond networking.
Case Study - AMR Test Automation
The client is a leading security technology company that develops an anti-malware product (AMR) to protect against malware and rootkits. With over 1600 manual test cases across operating systems, regression testing was challenging. The client sought to automate testing and create a reusable framework. iFocus Systec developed a Perl-based framework using Selenium for browser tests and AutoIT for GUI tests. This automated over 70% of test cases and reduced test cycles by 55%, providing a maintainable and reusable solution.
Optimizing Monitorability of Multi-cloud Applications
This document proposes an approach to optimize the monitorability of applications deployed across multiple cloud providers. It aims to maximize the number of application metrics that can be monitored while minimizing costs, based on each cloud provider's monitoring capabilities. A matchmaking algorithm finds the best deployment by considering users' monitoring requirements, providers' offered metrics and costs, and estimating metrics that are not directly measurable. The approach was validated on a sample deployment and showed response times around 19 seconds for optimizing monitoring of 4 VMs with 7 metrics each across 7 cloud providers.
Software Process Model
This document discusses three software process models: the waterfall model, incremental development, and reuse-oriented software engineering. The waterfall model represents the software development process as sequential phases such as requirements, design, implementation, testing, and maintenance. Incremental development interleaves these phases and develops the system in a series of versions that add new functionality. Reuse-oriented engineering focuses on integrating existing reusable components rather than developing everything from scratch.
OSSF 2018 - Brandon Jung of GitLab - Is Your DevOps 'Tool Tax' Weighing You D...
The document discusses how a single application that handles the entire software development lifecycle can help alleviate the "DevOps tool tax" caused by managing and integrating multiple point solutions. It provides an overview of GitLab's Auto DevOps feature which automates the build, test, security, deployment, and monitoring pipelines in a single system. By consolidating tools and processes, Auto DevOps helps reduce integration complexity and accelerate development cycles.
DevSecOps
Security Automation by integrating SAST(Static Application Security Testing),DAST(Dynamic Application Secuirty Testing) and SIEM (Security Information and Event Management) tools with Jenkins.
By automating Security(SAST,DAST,SIEM) developers can them selves perform VA and monitor on application without going to IT and Security team
Below Tools are used to Automate everything:
SAST - Fortify,CheckMarx
DAST - IBM App Scan,OWASP ZAP,HP Web Inspect
SIEM - Alien Vault
V-Empower Services And Solutions
V-Empower is a global security solutions and services company established in 2000 that provides state-of-the-art security solutions and consulting services through in-depth research and analysis. It offers comprehensive penetration testing, application security assessments, security program development, and training services. V-Empower saw a 206% increase in revenue in 2006 and its security team consists of over 27 consultants worldwide who have been featured in publications and by clients such as Microsoft.
V-Empower Services And Solutions
V-Empower is a global security solutions and services company established in 2000 that provides state-of-the-art security solutions and services through in-depth research, analysis, and knowledge sharing. It offers comprehensive penetration testing, application security assessments, security program development, and training services. V-Empower has experienced significant revenue growth and its security team consists of highly talented experts that provide services to some of the world's largest companies.
Web Application Security for Continuous Delivery Pipelines
Watch on-demand webinar: https://info.avinetworks.com/webinars/web-application-security-continuous-delivery-pipelines
Applications today have evolved into containers and microservices deployed in fully automated and distributed environments across data centers and clouds. Application services such as load balancing, security, and analytics become critical for continuous delivery.
To secure modern web applications, security policies including SSL/TLS, ACLs, IP Reputation, and WAF need to be applied quickly. We will share a reference implementation from Avi Networks.
Join this webinar to learn:
- CI/CD in the web application security context
- Challenges and solutions integrating a modern web application firewall (WAF) into the application development pipeline
- How to create processes that support both security and development requirements
Netflow analyzer- Datasheet
This product brochure summarizes ManageEngine NetFlow Analyzer, a network traffic analysis and security tool. It provides unparalleled network visibility [1] and supports various flow technologies. [2] The tool helps monitor network performance, security threats, and application usage to ensure business critical services run optimally. [3]
Sa 006 modifiability
The document discusses the concept of modifiability in software architecture. It defines modifiability as the ease with which a software system can be modified to changes in requirements, environment, or specifications. It describes aspects that impact modifiability such as what can change, when changes are required, who implements changes, and the cost of changes. It also discusses business concerns related to modifiability and provides examples of modifiability scenarios and quality attribute scenarios. Finally, it outlines tactics to improve modifiability such as reducing module size, increasing cohesion, reducing coupling, and deferring binding time.
Ragha Deepika_Exp_4+
Ragha Deepika has over 4 years of experience in software testing. She has expertise in manual and automation testing using tools like Quality Centre and QTP. She has worked on several projects for Tata Consultancy Services and Aviva testing applications involving technologies like .NET, Oracle, and IBM Mainframes.
Similar to Case Study: Mylyn Reviews for Software Development in Air Traffic Management (20)
Supporting Change Impact Analysis Using a Recommendation System - An Industri...
Supporting Change Impact Analysis Using a Recommendation System - An Industri...
Simplify and Scale Enterprise Spring Apps in the Cloud | March 23, 2023
Simplify and Scale Enterprise Spring Apps in the Cloud | March 23, 2023
In-kernel Analytics and Tracing with eBPF for OpenStack Clouds
In-kernel Analytics and Tracing with eBPF for OpenStack Clouds
Optimizing Monitorability of Multi-cloud Applications
Optimizing Monitorability of Multi-cloud Applications
OSSF 2018 - Brandon Jung of GitLab - Is Your DevOps 'Tool Tax' Weighing You D...
OSSF 2018 - Brandon Jung of GitLab - Is Your DevOps 'Tool Tax' Weighing You D...
Web Application Security for Continuous Delivery Pipelines
Web Application Security for Continuous Delivery Pipelines
Case Study: Mylyn Reviews for Software Development in Air Traffic Management
- 1. Mario Bernhart, Kilian Matt, Stefan Reiterer Vienna University of Technology, Vienna/Austria Research Group for Industrial Software www.inso.tuwien.ac.at
- 2. Mylyn Reviews Overview Mylyn Reviews Mylyn subproject for code reviews 3 implementations: Gerrit, R4E (IEEE) and Task Based Reviews (TBR) www.eclipse.org/reviews Case study is based on TBR Lightweight: Stores review tasks on Bugtracker, no extra server infrastructure needed.
- 3. Frequentis AG Located in Vienna/Austria, 800+ employees Development of safety-critical Communication- & Information-Systems Main market areas Civil Air Traffic Management Defence and Maritime Public Safety and Transport Adoption of Mylyn Reviews for Dev-Unit www.frequentis.com
- 4. Company Requirements Software Development Standard ED109 100% Code Review Coverage Reporting for compliance List of qualified reviewers per Repository Task-centered development process task-changeset traceability
- 5. Task-based reviews Reviews are performed per-task based on the related SVN changesets Reviews are rendered as sub-tasks of the task under review One review is assigned to one reviewer For one review, multiple changesets are reviewed
- 6. Custom Plug-ins Planning Plug-in Reporting Planning Mantis Recommendation of reviewers for a review- task Reporting Plug-in Review state of each review and changeset TBR overall coverage Mantis Mylyn Task-Changeset information
- 7. Demo See: http://web.student.tuwien.ac.at/~e0525940/mylyn_reviews_demo.mp4 7
- 8. Mario Bernhart, Kilian Matt, Stefan Reiterer Vienna University of Technology, Vienna/Austria Research Group for Industrial Software www.inso.tuwien.ac.at