REcognizing.ch

Category: Uncategorized

  • Where am I writing from

    Here where I am writing from – what I’ve done and what I know.

    PlantUML Syntax: @startmindmap <style> node {MaximumWidth 280} </style> + Discipline ++_ Requirements Engineering ++_ Systems Engineering +++ in the “INCOSE” sense, not MS365 or Azure Cloud… @endmindmap ” usemap=”#plantuml_map”></p> <h2 class=

    PlantUML Syntax: @startmindmap <style> node {MaximumWidth 280} </style> + Product\ntypology ++_ Market driven software intensive ecosystems ++_ One\n by\n one +++_ Market\nDriven ++++ Where future clients are not aware of the product at the time it is engineered. +++_ Software\nintensive ++++ Where software accounts for a major part of the R&D costs +++_ Eco\nsystems ++++ Where the engineered **Machine** interacts with other machines. ++++_ Machine +++++ An engineered object with a purpose in the world. Does not need to have hardware, but the actual interface with humans is tangible. Machines are often part of **Product families** ++++_ Product\nfamilies +++++_ where\n variability\n is involved ++++++ variability in time, with successive **versions** released over time ++++++ variability in space, with (possibly simultaneous) **variants** of the machine @endmindmap ” usemap=”#plantuml_map”></p> <h2 class=

    PlantUML Syntax: @startmindmap <style> node {MaximumWidth 280} </style> + Business domain ++_ Medical Devices – hearing devices & their ecosystem +++ Sonova AG ++_ Mobile phone industry +++ Motorola +++ Mitsubishi Electrics ++_ Telecommunications +++ Alcatel ++_ Various customers e.g. +++ Renault’s Techno centre +++ SNCF +++ Ecole Centrale Paris +++ Univesite Paris 1 Pantheon Sorbonne +++ Polarion @endmindmap ” usemap=”#plantuml_map”></p> <h2 class=

    PlantUML Syntax: @startmindmap <style> node {MaximumWidth 280} </style> + Activity ++_ engineering +++_ doing ++++ that is – requirements engineering +++_ leading ++++_ people ++++_ discipline ++++_ platform roadmap ++_ consulting +++_ coaching +++_ training @endmindmap ” usemap=”#plantuml_map”></p> </div> <div style=

  • Why REcognizing.ch

    In this blog I explore sensemaking and conceptual modelling in Requirements Engineering – in the context of market driven software intensive product engineering.

    What ?

    • sensemaking is the process of representing knowledge about the candidate problem and solution so that engineers can think, understand each others, agree, verify… so that they can engineer.
    • conceptual modelling is the toolbox which enables sensemaking

    Why ?

    • Because I believe the mission of cognitively enabling the engineering teams is the core purpose of requirements engineering (RE). “Cognitively enabling” means here “delivering the concepts with which people think together”
    • Because sensemaking is where Requirements Engineers maximize the value they deliver. This is the part of the job which “makes sense” (in various dimensions here). This is the part that is fun.
    • For employers and RE team managers, sensemaking is attractiveness, motivation and retention. This is investing in the future.
    • Because, although good conceptual models ultimately look simple and obvious, I have observed they are often poorly realized and therefore disregarded. Conceptual modelling is “an art [..] which requires apprenticeship” [Bernhard Thalheim].
    • Because, as automation (Knowledge Graphs, ML, AI, ..) is freeing (human) software engineers from repetitive tasks towards higher level of abstractions, from writing code towards model-driven engineering, conceptual modelling will play a key role interfacing humans and machine while they make sense of “what we do want to build, and why”. This is me being excited.
    • Because conceptual models, with both their formality and their quality of being grasped in a short glimpse, may become handy when exchanging knowledge with machines – not only in the context of engineering.

    In short, a bunch of topics I feel delighted to dive into.

    Another why ?

    • Because, after twelve years leading Requirements Engineering at Sonova (see my LinkedIn page), I am looking for my next occupation, and I feel like exploring what matters to me is both fulfilling, “sense-making” :-), and likely to increases my chances of reaching out to organizations which will need my services .

    I hope you’ll enjoy, feel free to contact me and react.