tor stålhane - Academia.edu (original) (raw)

Papers by tor stålhane

Research paper thumbnail of Requirements Engineering

CESAR - Cost-efficient Methods and Processes for Safety-relevant Embedded Systems, 2012

Research paper thumbnail of The Many Faces of Safety Cases

Proceeding of the 33rd European Safety and Reliability Conference

Research paper thumbnail of Course Improvement the TQM way

Norsk Informatikkonferanse, Nov 1, 2012

Research paper thumbnail of The Agile RAMSS lifecycle for the future

Research paper thumbnail of Trust Case and the Link to Safety Case

WIT Transactions on The Built Environment

The TrustMe project develops a safety case for autonomous buses. A safety case is mostly based on... more The TrustMe project develops a safety case for autonomous buses. A safety case is mostly based on information from the developers and refers to one or more relevant safety standards. The bases for a safety case are the defined safety standards and proof of compliance, based on the paper trails left by each required activity. A trust case is different and trust and safety assessments are not necessarily correlated. In order to make self-driving buses a success they need to be considered trustworthy. Thus, we need a "Trust case". To ensure that the vehicles are safe and to inform the public, we have developed both a developer safety case and safety case for the public. To take care of the remaining factors we have developed a "Trust case". The trust case has been developed as part of literature studies, surveys and interviews. We have made a survey of 311 passengers and interviewed 18 autonomous bus passengers. Based on literature studies, surveys and interviews, we have proposed a set of issues that should be included into a "Trust case". By providing the public with a "Trust case" together with a "safety case for the public" we will help manufacturers of autonomous vehicles and operators to gain public trust.

Research paper thumbnail of Functional Safety and Proof of Compliance

The use of general descriptive names, registered names, trademarks, service marks, etc. in this p... more The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use.

Research paper thumbnail of Safety Analysis Methods Applied to Software

Functional Safety and Proof of Compliance

Research paper thumbnail of Safety and Risk Documents

Functional Safety and Proof of Compliance, 2021

Research paper thumbnail of Generic Documents

Functional Safety and Proof of Compliance, 2021

Research paper thumbnail of Plans and Functional Safety Management

Functional Safety and Proof of Compliance, 2021

Research paper thumbnail of Tools

Research paper thumbnail of Test, Analysis, and V&V

Functional Safety and Proof of Compliance, 2021

Research paper thumbnail of Safety, security and resilience of critical software ecosystems

Research paper thumbnail of Roles, Assessment and Authorisation

What This Chapter Is About Most of the relevant roles when developing signalling systems Assessme... more What This Chapter Is About Most of the relevant roles when developing signalling systems Assessment performed by the assessor The accreditation system and notification of bodies Authorisation performed by the safety authority

Research paper thumbnail of The SafeScrum® Process: Activities

This chapter present the main Scrum activities, re-casted into SafeScrum ® . We discuss important... more This chapter present the main Scrum activities, re-casted into SafeScrum ® . We discuss important activities such as: Sprint planning, workflow, review meetings and retrospectives. The daily stand-ups. Backlog refinement—an important part of Scrum. Explicit quality assurance—a necessary addendum to Scrum.

Research paper thumbnail of Trust Me, We Have a Safety Case for the Public

Proceedings of the 31st European Safety and Reliability Conference (ESREL 2021), 2021

Research paper thumbnail of What competence do software companies want from university graduates?

Nordic Journal of STEM Education, 2020

An important concern for study program design is the employability of candidates. This paper seek... more An important concern for study program design is the employability of candidates. This paper seeks to establish what competence is sought by employers of IT candidates, based on interviews with representatives from 120 Norwegian companies working with IT. The results have been analysed to identify what the IT industry expect from university candidates. For the whole sample, the most frequently mentioned characteristics were programming knowledge, adaptability, the willingness to learn new things and problem-solving skills. If we only consider the companies that develop software, the most frequently mentioned characteristics were programming knowledge, the willingness to learn new things and communication skills. The interviewees were also asked which characteristics that they were missing from university candidates. The most mentioned shortcomings were practical experience with coding and maintenance, adaptability and communication skills when relating to clients. Towards the end o...

Research paper thumbnail of Proceedings on the 1st Workshop on Agile Methods Applied to Development and Certification of Safety-critical Software

ACM SIGSOFT Software Engineering Notes, 2016

The first international workshop on agile methods applied to development and certification of saf... more The first international workshop on agile methods applied to development and certification of safety-critical software (ASCS) was organized as part of the XP 2015 conference on May 25th 2015. The workshop gathered 17 experts from industry and academia to share recent industrial experience and research on applications of agile methods in the safety critical software domain. The workshop was organized as a series of talks and discussions to share experience and ideas. The workshop audience also provided guidelines for future research needed to advance the field.

Research paper thumbnail of Presenting a traceability based approach for safety argumentation

Research paper thumbnail of A component-based reference model for web-based systems

IASTED Conference on Software Engineering and Applications, 2004

Short time-to-market is an important requirement for developing web-based systems. Software archi... more Short time-to-market is an important requirement for developing web-based systems. Software architecture plays a critical role for time-to-market objective to be satisfied since it forms a blueprint for the system structure, indicating the principle loci of later activities such as detailed design and implementation. In particular, we need a novel way for system decomposition to achieve reduced complexity, encapsulated change, and maximized reuse possibility. In this paper we address these problems by separation of concerns, applying patterns, and forming components. We firstly present a component-based reference model for web-based systems. The main interest here is to capture early design decisions associated with short time-to-market concern and provide guidelines for system decomposition and architecture construction. We then discuss issues concerning component development within the reference model. Three component patterns are identified to achieve flexible and efficient reuse.

Research paper thumbnail of Requirements Engineering

CESAR - Cost-efficient Methods and Processes for Safety-relevant Embedded Systems, 2012

Research paper thumbnail of The Many Faces of Safety Cases

Proceeding of the 33rd European Safety and Reliability Conference

Research paper thumbnail of Course Improvement the TQM way

Norsk Informatikkonferanse, Nov 1, 2012

Research paper thumbnail of The Agile RAMSS lifecycle for the future

Research paper thumbnail of Trust Case and the Link to Safety Case

WIT Transactions on The Built Environment

The TrustMe project develops a safety case for autonomous buses. A safety case is mostly based on... more The TrustMe project develops a safety case for autonomous buses. A safety case is mostly based on information from the developers and refers to one or more relevant safety standards. The bases for a safety case are the defined safety standards and proof of compliance, based on the paper trails left by each required activity. A trust case is different and trust and safety assessments are not necessarily correlated. In order to make self-driving buses a success they need to be considered trustworthy. Thus, we need a "Trust case". To ensure that the vehicles are safe and to inform the public, we have developed both a developer safety case and safety case for the public. To take care of the remaining factors we have developed a "Trust case". The trust case has been developed as part of literature studies, surveys and interviews. We have made a survey of 311 passengers and interviewed 18 autonomous bus passengers. Based on literature studies, surveys and interviews, we have proposed a set of issues that should be included into a "Trust case". By providing the public with a "Trust case" together with a "safety case for the public" we will help manufacturers of autonomous vehicles and operators to gain public trust.

Research paper thumbnail of Functional Safety and Proof of Compliance

The use of general descriptive names, registered names, trademarks, service marks, etc. in this p... more The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use.

Research paper thumbnail of Safety Analysis Methods Applied to Software

Functional Safety and Proof of Compliance

Research paper thumbnail of Safety and Risk Documents

Functional Safety and Proof of Compliance, 2021

Research paper thumbnail of Generic Documents

Functional Safety and Proof of Compliance, 2021

Research paper thumbnail of Plans and Functional Safety Management

Functional Safety and Proof of Compliance, 2021

Research paper thumbnail of Tools

Research paper thumbnail of Test, Analysis, and V&V

Functional Safety and Proof of Compliance, 2021

Research paper thumbnail of Safety, security and resilience of critical software ecosystems

Research paper thumbnail of Roles, Assessment and Authorisation

What This Chapter Is About Most of the relevant roles when developing signalling systems Assessme... more What This Chapter Is About Most of the relevant roles when developing signalling systems Assessment performed by the assessor The accreditation system and notification of bodies Authorisation performed by the safety authority

Research paper thumbnail of The SafeScrum® Process: Activities

This chapter present the main Scrum activities, re-casted into SafeScrum ® . We discuss important... more This chapter present the main Scrum activities, re-casted into SafeScrum ® . We discuss important activities such as: Sprint planning, workflow, review meetings and retrospectives. The daily stand-ups. Backlog refinement—an important part of Scrum. Explicit quality assurance—a necessary addendum to Scrum.

Research paper thumbnail of Trust Me, We Have a Safety Case for the Public

Proceedings of the 31st European Safety and Reliability Conference (ESREL 2021), 2021

Research paper thumbnail of What competence do software companies want from university graduates?

Nordic Journal of STEM Education, 2020

An important concern for study program design is the employability of candidates. This paper seek... more An important concern for study program design is the employability of candidates. This paper seeks to establish what competence is sought by employers of IT candidates, based on interviews with representatives from 120 Norwegian companies working with IT. The results have been analysed to identify what the IT industry expect from university candidates. For the whole sample, the most frequently mentioned characteristics were programming knowledge, adaptability, the willingness to learn new things and problem-solving skills. If we only consider the companies that develop software, the most frequently mentioned characteristics were programming knowledge, the willingness to learn new things and communication skills. The interviewees were also asked which characteristics that they were missing from university candidates. The most mentioned shortcomings were practical experience with coding and maintenance, adaptability and communication skills when relating to clients. Towards the end o...

Research paper thumbnail of Proceedings on the 1st Workshop on Agile Methods Applied to Development and Certification of Safety-critical Software

ACM SIGSOFT Software Engineering Notes, 2016

The first international workshop on agile methods applied to development and certification of saf... more The first international workshop on agile methods applied to development and certification of safety-critical software (ASCS) was organized as part of the XP 2015 conference on May 25th 2015. The workshop gathered 17 experts from industry and academia to share recent industrial experience and research on applications of agile methods in the safety critical software domain. The workshop was organized as a series of talks and discussions to share experience and ideas. The workshop audience also provided guidelines for future research needed to advance the field.

Research paper thumbnail of Presenting a traceability based approach for safety argumentation

Research paper thumbnail of A component-based reference model for web-based systems

IASTED Conference on Software Engineering and Applications, 2004

Short time-to-market is an important requirement for developing web-based systems. Software archi... more Short time-to-market is an important requirement for developing web-based systems. Software architecture plays a critical role for time-to-market objective to be satisfied since it forms a blueprint for the system structure, indicating the principle loci of later activities such as detailed design and implementation. In particular, we need a novel way for system decomposition to achieve reduced complexity, encapsulated change, and maximized reuse possibility. In this paper we address these problems by separation of concerns, applying patterns, and forming components. We firstly present a component-based reference model for web-based systems. The main interest here is to capture early design decisions associated with short time-to-market concern and provide guidelines for system decomposition and architecture construction. We then discuss issues concerning component development within the reference model. Three component patterns are identified to achieve flexible and efficient reuse.