Fra InfinIT-seminar om Udviklingsforløb for indlejrede systemer den 22. november 2016

1. 111
Udviklingsforløb for
indlejrede systemer
V0.01/Peder Kristensen
Udvikling igennem
underleverandører

2. Spørgsmål fra Hardi:
- Hvordan afklarer firmaet selv sine behov og krav?
- Hvordan afbalanceres forholdet mellem håndværksmæssig og
procesorienteret tilgang til softwareudvikling?
- Hvordan afklares, om underleverandøren er kvalificeret?
- Hvordan afklares fordeling af opgaver mellem kunde og
underleverandør?
- Hvordan overdrages viden fra fx senioringeniør til nye folk på
vedligeholdelse af den udviklede computer?
V01.01.00/Peder Kristensen

3. V01.01.00/Peder Kristensen
Development overview based on ISO 15504

4. Grundfos
Bjerringbro
Grundfos
Chennai
External
(HCL)
Chennai
Grundfos
Suzhou
External
(e.g. Develco)
Bjerringbro
How is the External providers leaded/managed
Daily coordinationDaily coordination
Management
Daily coordination
Daily coordination
Management
V01.01.00/Peder Kristensen

5. The state of the external provider
5
Questions to the external provider
V01.01.00/Peder Kristensen

6. V01.01.00/mtc
6
The state of the external provider
- Graphical overview
V01.01.00/Peder Kristensen

7. Checklist:
- Management setup
Scope (the overall agreement)
- Frame works for the development (WPA)
- Resources
- Requirements (SRS)
- Documentation
- Definition of Done
- Release plan (SRS)
- Management interface (cooperation)
- Meeting frequency (e.g. every day, time of the meeting)
- Who participate
- Agile development (or plan development)
What is the scope for the development
V01.01.00/Peder Kristensen

8. Cockburn Levels of software method understanding and use
Article: Agility, Provided by: Barry Boehm University of Southern California and Richard Turner George Washington
University ockburn Levels of software method understanding
8
Level Characteristics scheme:
3 Able to revise a method (break its rules) to fit an unprecedented new situation
2 Able to tailor a method to fit a precedented new situation
1A With training, able to perform discretionary method steps (e.g., sizing stories to fit
increments, composing patterns, compound refactoring, complex COTS integration). With
experience can become Level 2.
1B With training, able to perform procedural method steps (e.g. coding a simple method, simple
refactoring, following coding standards and CM procedures, running tests). With experience can
master some Level 1A skills. –
1 May have technical skills, but unable or unwilling to collaborate or follow shared methods.
V01.01.00/Peder Kristensen

9. Cockburn Levels of software method understanding and use
Article: Agility, Provided by: Barry Boehm University of Southern California and Richard Turner George Washington
University Cockburn Levels of software method understanding
10
Traditional development
Level:
- 3 Senior/Architect
- 2 Needed
- 1A Team members
- 1B Team members
-1 Few members
Agile development
Level:
- 3 Senior/Architect
- 2 Needed
- 1A Team members
- 1B Not too many
-1 Problem
V01.01.00/Peder Kristensen

10. Ensure the level of competences/maturity
11
Inspection / Maturity level
 Assessment ISO 15504
Light Assessment
 CMMI - SCAMPI
Process Review
Audit ISO9001?
ISO 15504 Assessment result
Process CL 1 CL 2 CL 3 CL 4 CL 5
Technical Project
Management
  Not assessed
Quality Assurance   Not assessed
Product Design    Not assessed
General strengths & improvement
opportunities
V01.01.00/Peder Kristensen

11. Ensure the level of competences/maturity
12
Process Review
Inspection / Maturity level
Assessment ISO 15504
Light Assessment
CMMI - SCAMPI
 Process Review
Audit ISO9001?
V01.01.00/Peder Kristensen

12. Development activities
13
Development Ready for test DoneReady for development
Backlog
Day-to-day activities
Focus is the criteria of ‘Done’
V01.01.00/Peder Kristensen

13. Ensure the level of competences/maturity
V01.01.00/Peder Kristensen
14
Which Process to comparing to?
• Process’s used by the external provider
• Process’s used in own company
• Compare with standard ISO15504
• Compare with the maturity model CMMI
Agile is one life cycle option

14. Which process to compare with?
V01.01.00/Peder Kristensen
Software requirement
Sepcification
Software Design
Software Construction
Software Integration
Software Testing

15. External management?
V01.01.00/Peder Kristensen
Customer External
Supplier
Customer External
Supplier
One manager
Two managers

16. Interface/knowledge/experience?
V01.01.00/Peder Kristensen
Software Hardware

17.  Management
How is the communication plan between the companies?
Who takes care of what?
 Requirements
How are the requirement managed?
How to follow-up on the delivery plan / release plan?
 Development Process’s
Which process are used during the development (own company/external company)?
How much information / progress can be shared?
Headlines for coorparation
V01.01.00/Peder Kristensen

18.  Resources
Which competences in the team?
How to lead the project?
How to ensure architecture and to maintain the platform?
 Architecture
Do they have competences to create and maintain architecture?
 Level of documentation
Which documentation will delivered?
Are there any restrictions / copyright
 Level of test
What is the kind of tests are done (e.g. unit test, integration test, regretion test)?
What is the criteria of ‘Done’?
Headlines for coorparation
V01.01.00/Peder Kristensen

19. Questions
V01.01.00/Peder Kristensen

20. V01.01.00/Peder Kristensen