• Nenhum resultado encontrado

Software and systems engineering

N/A
N/A
Protected

Academic year: 2022

Share "Software and systems engineering"

Copied!
22
0
0

Texto

(1)

Software and systems engineering

Paulo Borba

Informatics Center

Federal University of Pernambuco

phmb@cin.ufpe.br ◈ twitter.com/pauloborba

(2)
(3)

Evaluation of the requirements class

• Only 9 answers (17 for the first class)!

• "Talvez uma especificação mais explícita dos conceitos mais importantes”

• “…Se puder verificar equipes incompletas no início da próxima aula seria uma mão na

roda”

(4)

Class structure

• Check previous activities

• Log into google with your CIn account

• Access and answer today’s questions (…)

• Discuss class material

• what haven’t you understood? what don’t you agree?

what haven’t you liked? what are you missing to perform the project task?

• Hands-on scenario review, and configuration

management plan and use session

(5)

Configuration

management

(6)

Software and system development is often

done in teams!

(7)

Team members

contribute to the same

artifacts

(8)

Productivity and quality

problems sharing requirements, source code, etc. via...

email

dropbox

• google docs

(9)

Source code (artifact) control systems

• Versions and commits

• Releases and builds

Branches

• Feature or component development

• Bug fixing in previous releases

• Customer specific variants

• Integration, merges and conflicts

• Repositories

• Centralized vs distributed

(10)

Forking and cloning

From http://www.eqqon.com/index.php/Collaborative_Github_Workflow

(11)

Committing early and often

From http://marklodato.github.com/visual-git-guide/index-en.html

(12)

Continuous integration,

continuous deployment

(13)

Pushing, requesting pulling, and merging

From http://www.eqqon.com/index.php/Collaborative_Github_Workflow

(14)

Branches, merging,

rebasing and squashing

(15)

RGMS history

(16)

RGMS at Github

(17)

Git at

IntelliJ

(18)

Before integrating…

• Review scenarios and features, or write scenarios in pairs

• Make sure they follow style and quality criteria; otherwise, clearly comment

• Organize review procedures and meetings

(19)

Change requests,

change managements, and other aspects are

discussed latter

(20)

Checklist

• Clear commit messages, exactly

corresponding to what has changed

• no language errors

• Commit early and often

• avoid tangled commits

• Rules and details at the website

(21)

CM research at CIn

• Advanced merging tools: Paulo

• Collaboration conflicts characteristics:

Paulo

(22)

Software and systems engineering

Paulo Borba

Informatics Center

Federal University of Pernambuco

phmb@cin.ufpe.br ◈ twitter.com/pauloborba

Referências

Documentos relacionados

O tema da maturidade dos processos de desenvolvimento de software foi ganhando força na comunidade da engenharia de software, em conseqüência dos resultados práticos obtidos

Atesto para os devidos fins e a pedido do interessado que ANA CAROLINA TOLEDO ROCHA, participou do “Encontro Universidade Empreendedora – Maio de 2010”, registrada

Little reuse and agility, high costs.. Even

To control scope, we need to manage a list of tasks... To control time, we need to manage

Little modularity and agility, more deffects,   high costs..

“As a large program is continuously changed, its complexity, which reflects deteriorating. structure, increases unless work is done to maintain or

Scenario: export multiple members link not enabled when there are no member selected Given I am at the member list page. And the system has no

Congestão nasal e coriza PGs e Leucotrienos Secreção glandular Colinérgico e Histaminérgico Resposta Sistema Rinite alérgica • Sintomas - Rinorréia - Congestão nasal -