Transferring Experience from Software Engineering Training in Industry to Mass University Education - The Big Picture

Bleek, Wolf-Gideon; Lilienthal, Carola; Schmolitzky, Axel

doi:10.1109/cseet.2005.38

Cited by 5 publications

(6 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The gap can potentially be tackled in several ways: by updating the curriculum via transfer of experience from industry to academia [5]; via training as part of post-employment onboarding of new hires [6]; and by partially relying on certification programs, such as those provided by IEEE [7]. However, Havelsan Academy decided to take a different approach: creation of a summer school to replace postemployment training with pre-employment training and assessment.…”

Section: Introductionmentioning

confidence: 99%

Are computer science and engineering graduates ready for the software industry?

Tüzün

Erdogmus

Özbilgin

2018

Proceedings of the 40th International Conference on Software Engineering: Software Engineering Education and Training

View full text Add to dashboard Cite

It 1 has been 50 years since the term "software engineering" was coined in 1968 at a NATO conference. The field should be relatively mature by now, with most established universities covering core software engineering topics in their Computer Science programs and others offering specialized degrees. However, still many practitioners lament a lack of skills in new software engineering hires. With the growing demand for software engineers from the industry, this apparent gap becomes more and more pronounced. One corporate strategy to address this gap is for the industry to develop supplementary training programs before the hiring process, which could also help companies screen viable candidates. In this paper, we report on our experiences and lessons learned in conducting a summer school program aimed at screening new graduates, introducing them to core skills relevant to the organization and industry, and assessing their attitudes toward mastering those skills before the hiring process begins. Our experience suggests that such initiatives can be mutually beneficial for new hires and companies alike. We support this insight with pre-and post-training data collected from the participants during the first edition of the summer school and a follow-up questionnaire conducted after a year with the participants, 50% of whom were hired by the company shortly after the summer school. CCS CONCEPTS• Social and professional topics→ Computing Education KEYWORDS Software engineering education, software engineering training, software engineering summer school, hiring practices for software professionals

show abstract

Section: Introductionmentioning

confidence: 99%

Are computer science and engineering graduates ready for the software industry?

Tüzün

Erdogmus

Özbilgin

2018

Proceedings of the 40th International Conference on Software Engineering: Software Engineering Education and Training

View full text Add to dashboard Cite

show abstract

“…No contexto industrial,é comum que aulas breves sejam ministradas e trabalhos práticos sejam desenvolvidos por pequenos grupos (Bleek et al, 2005).…”

Section: Concepção De Um Processo Para Projetos De Pesquisa Em Softwareunclassified

“…• Artefatos de entrada: documentos indicando exigências em relação ao treinamento, tema do treinamento Bleek et al (2005) indicaram atividades que estão sendo cumpridas de forma bem sucedida para treinamento em ambiente industrial e que, segundo ele, poderiam ser cumpridas também em universidades. Em resumo, os autores sugerem que (1) sejam apresentadas aulas teóricas intercaladas com aulas práticas em laboratório; (2) sejam realizados pequenos ciclos de produção e feedback em que artefatos de interesse são produzidos pelos participantes, avaliados e comentados pelos responsáveis pelo treinamento; (3) seja desenvolvido um mini-projeto de forma que os participantes possam perceber o uso da tecnologia ou do processo que está em treinamento no contexto do desenvolvimento de um projeto e (4) sejam oferecidas contribuições em um projeto real e não crítico, de forma que os participantes possam experimentar problemas típicos do desenvolvimento de projetos de software em diferentes níveis: sociais, técnicos e organizacionais.…”

Section: Il1 Desenvolver Política Para Treinamentounclassified

“…• Artefatos de saída: diferentes resultados podem ser obtidos com o cumprimento desta tarefa. Quando há uma agência financiando um projeto ou parceria com o setor industrial,é comum que exista um contrato padronizado (Bleek et al, 2005). Em outras situações, o próprio coordenador do projeto pode redigir um contrato.…”

Section: Rm3 Revisar E Aceitar Modificaçãounclassified

“…Outra característica importante que motiva a definição, o uso e a melhoria de processos para o desenvolvimento de pesquisasé o estabelecimento de parcerias entre indústria e academia. Em diversos países da Europa e nos Estados Unidos as contribuições provenientes dessas parcerias têm sido expressivas (Bleek et al, 2005;Kornecki et al, 2003). No Brasil o governo também está incentivando e participando de associações para o desenvolvimento de novas tecnologias.…”

Section: Introductionunclassified

See 2 more Smart Citations

Um processo envolvendo elementos de design rationale para projetos de pesquisa em software

Paiva¹

View full text Add to dashboard Cite

The increasing volume of research projects in the context of software is a motivation for analyzing processes which are used to develop such projects, regarding activities that are carried out, results that are gathered and application of resources. In the Software Engineering area, recently, processes have been considered with the objective to contribute for research projects development in which software is an element. Overall, the main purpose is to help management overtime of artifacts that can be produced, such as, models, code, technical reports and scientific papers. However, research developed in this direction and solutions discussed in the literature are presented in an initial stage. Therefore, the objective of this work was to define a process for development of research projects regarding a set of requirements. It is expected that such process can be useful to contribute for evolution of these projects. To reinforce the aspect of research project evolution, the design rationale approach was studied. The goal was to provide the opportunity of capturing and registering decisions in specific development phases. The documentation process was emphasized, i.e., the design rationale approach was analyzed focusing on the improvement of research projects documentation. As a result, a model for design rationale representation was defined, implemented in a CASE tool and evaluated by means of an experiment.

show abstract