add-memberalign-toparrow-leftarrow-rightbellblockcalendarcamerachatchevron-leftchevron-rightchevron-small-downchevron-upcircle-with-crosscomposecrossfacebookflagfolderglobegoogleimagesinstagramkeylocation-pinmedalmoremuplabelShape 3 + Rectangle 1pagepersonpluspollsImported LayersImported LayersImported LayersshieldstartwitterwinbackClosewinbackCompletewinbackDiscountyahoo

casual code collaboration

  • Oct 29, 2013 · 7:00 PM
  • This location is shown only to members

Very informal, sitting around a table, and working thru some sv code examples.

Join or login to comment.

  • LK J.

    I think that as design/verification gets more complex, OOP makes building things and communication with others simpler. Coupled with UVM (a methodology and OOP base class), we have** common terminology and division of functionality.
    Imagine if you're building a car and didn't have words like "door", "engine", "tire", "carburetor", and when you wanted to tell someone else that you wanted a different type of door, you needed to explain to them the basics about what a door is and what its functionality means.

    **however 'work-in-progress' it may be

    I think a better place to ask such questions is verificationacademy or
    Our group is small. You'll get much richer answers there.

    October 29, 2013

  • man

    cont'd the conversation with X / the group. I am always wondering why OOP ? and why now ? Can the OOP problem-solving paradigm can help solving the verification problems ? OR it is just making it more complex.

    What problems in verification that OOP/SV/UVM are trying to solve ?

    October 28, 2013

4 went

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy