Proceedings of the 12th ACM SIGSOFT Twelfth International Symposium on Foundations of Software Engineering 2004
DOI: 10.1145/1029894.1029897
|View full text |Cite
|
Sign up to set email alerts
|

Making embedded software reuse practical and safe

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2007
2007
2013
2013

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 16 publications
(9 citation statements)
references
References 11 publications
0
9
0
Order By: Relevance
“…In the IT context, program management is used in software and application development (Caudill, 1977;Leveson and Weiss, 2004;Mäntyniemi et al, 2004), ERP implementation (Ribbers and Schoo, 2002) and IT infrastructure management (AlMashari and Zairi, 2000). For technology product and service companies, greater program and project management capabilities are required to address competence risks, especially when they become custom solution providers for their clients (Sawhney, 2004).…”
Section: Information Technology Programsmentioning
confidence: 99%
“…In the IT context, program management is used in software and application development (Caudill, 1977;Leveson and Weiss, 2004;Mäntyniemi et al, 2004), ERP implementation (Ribbers and Schoo, 2002) and IT infrastructure management (AlMashari and Zairi, 2000). For technology product and service companies, greater program and project management capabilities are required to address competence risks, especially when they become custom solution providers for their clients (Sawhney, 2004).…”
Section: Information Technology Programsmentioning
confidence: 99%
“…Prior work in software safety [8] and in reuse for safety-critical systems [9] has not dealt directly with SPLE safety analyses. On the other hand, prior work in SPLE has not addressed the additional, high-assurance needs of safety-critical SPLs [1] [13].…”
Section: Related Workmentioning
confidence: 99%
“…Despite the firm position taken by Redmill and Leveson with regard to the impact of software reuse, they both acknowledge the importance of getting "the benefits of reuse without the drawbacks" [3] through "an increasing need for care (and guidance)" [5]. We believe that reuse can be more systematic if it is planned from early development stages.…”
Section: Software Reuse and Dependabilitymentioning
confidence: 99%
“…Establishing a traceable link between the requirements, design, and the reusable code can enable the deployment of the reusable software in an effective and analysable way. Therefore, reuse should be addressed holistically, rather than being limited to the code, where most reuse attempts have failed [3].…”
Section: Software Reuse and Dependabilitymentioning
confidence: 99%