Software engineering

Gilb, Tom

doi:10.1145/1012467.1012474

Cited by 44 publications

(59 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Previous experimental work has been done to understand and improve software review and inspection procedures with respect to defect detection [3,16,20,22,23]. Inspections have been shown to be an effective tool for defect detection in software artifacts.…”

Section: Individual Variation Among Inspectorsmentioning

confidence: 99%

Identifying implicit process variables to support future empirical work

Carver¹,

Basili²

2003

J. Braz. Comp. Soc.

View full text Add to dashboard Cite

Section: Individual Variation Among Inspectorsmentioning

confidence: 99%

Identifying implicit process variables to support future empirical work

Carver¹,

Basili²

2003

J. Braz. Comp. Soc.

View full text Add to dashboard Cite

“…Code reviews are widely acknowledged as being a very effective means to find problems in programs written by peers [GG93] [Gla97]. Two important prerequisites have to be met in order to make such reviews costeffective: (a) a checklist must be prepared to help the reviewer focus on the relevant questions and (b) a review session must be kept short because reviewers cannot concentrate for a very long time (2 hours at maximum).…”

Section: Rationalementioning

confidence: 99%

Object-Oriented Reengineering Patterns

Nierstrasz¹,

Demeyer

2003

View full text Add to dashboard Cite

“…a person responsible for the implementation and improvement of a process, was identified. The following processes were developed, tested in pilot projects and implemented: software development, software maintenance, software project planning and tracking, software quality assurance, software configuration management, software subcontractor management, documentation management and document inspection (Gilb 1993). …”

Section: Development Of a Software Engineering Processmentioning

confidence: 99%

Development and Integration of Engineering Processes at Oerlikon Aerospace

Laporte¹,

Papiccio²

1997

INCOSE International Symp

View full text Add to dashboard Cite

In order to reduce cycle time, increase customer satisfaction and lower costs, Oerlikon Aerospace has initiated, in 1992, a project to define and implement software and systems engineering processes. The initiative started by performing a formal assessment of current software engineering practices. An action plan was developed and multi-functional working groups were tasked to define and facilitate the implementation of software processes. A second initiative was started, in 1995, with the objective of defining and implementing a systems engineering process, and integrating to the systems engineering process the software engineering process already in use.

show abstract

Software engineering

Cited by 44 publications

References 0 publications

Identifying implicit process variables to support future empirical work

Identifying implicit process variables to support future empirical work

Object-Oriented Reengineering Patterns

Development and Integration of Engineering Processes at Oerlikon Aerospace

Contact Info

Product

Resources

About