Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Requirement binded to a part def and verified against usage

Open
#1,125 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
18/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
go
Domain
tooling

Research direction

The issue is a modeling question, not a defined code change. Start with the attached lifecycle.zip and its three files: reqrmnt.sysml, definition.sysml and product.sysml. Check the SysML v2 specification for requirement binding and verification, then see whether this Go implementation parses those constructs. Done means a maintainer confirms what is supported and what change, if any, is needed.

Written by the indexing model from the issue text.

Description

bug spec compliance

lifecycle.zip

  • reqrmnt.sysml : requirements are defined (it could be a standard or specification from Customer)
  • definition.sysml : product manager has analyzed requirement can selected what has to be respected.
  • product.sysml : engineering team design something and check conformity.

Does SysML support binding requirements to part def and verify them against usage ?

Dominant language
Go
Stars
39
Forks
12
Avg merge
14h 14m
Merged PRs (30d)
759

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Open-MBEE/OpenSysML

All issues in Open-MBEE/OpenSysML

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.