Ed Seidewitz

@seidewitz

Enterprise & software architect, coder, UML geek, SysML v2 co-lead. Amateur (but serious) theoretical physicist. (For the latter, see .)

Washington, DC
Vrijeme pridruživanja: kolovoz 2009.

Tweetovi

Blokirali ste korisnika/cu @seidewitz

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @seidewitz

  1. 29. sij

    Landed at BWI.

    Poništi
  2. 29. sij

    Boarding at ATL.

    Poništi
  3. 29. sij

    Connecting at ATL.

    Poništi
  4. 29. sij

    Boarding at LAX.

    Poništi
  5. 29. sij

    Heading home on an early flight. Thanks for a great ! See you next year in Seville with more v2.

    Poništi
  6. 26. sij

    Are you at ? Do you want to know more about v2? Come to the open session this afternoon! and I will demo the language and API pilot implementations. Demos will be repeated before and after the afternoon break.

    Poništi
  7. 26. sij

    Progress on v2 since 2019, as presented by Sandy Friedenthal.

    Poništi
  8. 26. sij
    Poništi
  9. 26. sij

    Example of the v2 textual notation. (This really is the notation we will be proposing, along with a graphical notation still under development.)

    Poništi
  10. 26. sij

    v2 supports a usage-focused modeling approach. Colloquially “modeling on the IBD”. (This is just a notional graphical mock up, not actual proposed SysML v2 notation.) Sandy Friedenthal

    Poništi
  11. 26. sij

    Key elements of v2, as presented by Sandy Friedenthal. .

    Poništi
  12. proslijedio/la je Tweet
    26. sij

    Sandy Friedenthal sharing the latest updates on SysML 2.0 at . This is a game changer for MBSE. Today afternoon and I will be doing demos of SysML 2.0 pilot implementation. Join us!

    Poništi
  13. 26. sij

    Sandy Friedenthal presenting the status of the v2 submission effort at .

    Poništi
  14. 25. sij

    Mantras from Stephane Bonnet.

    Poništi
  15. 25. sij

    “Three different kinds of purposes for models: share, secure, automate. More is not necessarily better.” Stephane Bonnet

    Poništi
  16. 25. sij

    Given textual/modeled requirements and a solution at one level, the tooling generates the requirements models (“engineering contracts”) for the downstream engineering teams at the next level. Textual requirements generated for what can’t be modeled. Stephane Bonnet

    Poništi
  17. 25. sij

    “Models add rigor to need expression/solution description. Models Enable automated processing.” Stephane Bonnet

    Poništi
  18. 25. sij

    Stephane Bonnet of Thales giving the keynote for the Model Based Systems Engineerin Initiative session at .

    Poništi
  19. proslijedio/la je Tweet
    24. sij

    unplugged at and workshop this weekend. Enroute to what will be a great event with demos, OpenMBEE poster session, and lots of chat about the future of systems engineering.

    Poništi
  20. 24. sij

    Landed at LAX.

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·