Main areas: lifecycle, processes, artefacts, roles
Based on ISO/IEC/IEEE 29148:2011
Not much of requirements engineering yet in openSE
Presentation of the purpose of the Task Forces and the deliverable
Requirements/ Discussion
Requirements connected to procurement, purchasing, quality management, NPD, software engineering, SE
Engineering specifications should be systematic
At CERN a technical officer is usually responsible for writing the requirements
More regulatory role, complying to the standards and after passing not too concerned. Departmental level more pragmatic solutions
Key deliverables: something like an excel based business case, in the end evaluating the benefits and who is going to be the owner. At CERN business cases are not so... The corresponding business case should be modified and roadmap updated to accommodate something that is feasible.
Technical spesification shall be aligned with engineering spect. However in engineering spect there is nothing to say how to work on the CERN site, especially for external constructors.
Best practices: Name responsibilities, define stakeholder, collect the needs by involving the relevant stakeholders. Systematic consideration.
Does every product need an engineering spect?
Depends on the project at hand
Also those components that are outsourced have engineering spect as prequisity, but those produced in CERN usually don't have
How to address the treshold of the project leader not being able to check all the engineering spects of the project. When there are constrains, these need to be acknowledged and addressed.
Next steps:
Pierre will share them in his CERN box (behind his password), not available
Everybody gathers material for Task Force input
Reading and evaluating the materials
Next meetings
Friday 14th of September 10:30-12
Friday 28th, from 14-15
There are minutes attached to this event.
Show them.