SysMLv1 (or v2): CHALLENGE EXERCISE: Simplified Parsing Analysis breakdown of 'Build an Airport' with variations

Dr Darren of Webel IT Australia says:

For this one you can just use the SysML ElementGroup and its list of /member if you wish, you don't have to use the full  Webel Parsing Analysis recipe for SysML^® or the Webel «snippet». You don't have to display the /member once you've related each ElementGroup to the elicited model elements.

Identify some Requirements, Blocks, ValueTypes, some associated properties, maybe some Constraints, Use Cases if you are into them, Activities, States. Try using a SysMLv1 ElementGroup to capture each high level text "snippet" and relate it to some elicited model elements using the dashed-line "handle". Start with Block Definition Diagrams and Requirements Diagrams:

• 'Build an Airport.'
• 'Build an Airport meeting IEEE SE spec ABC.'
• 'Build an Airport for military planes.'
• 'Build an Airport for passenger aircraft.'
• 'Build an Airport with access for medical helicopters for a nearby Hospital.'
• 'Build an Airport for under $XYZ total.'
• 'Build an Airport in under 10 years.'
• 'Build an Airport with high level security to prevent bad people doing horrible stuff.'
• 'Build an Airport on reclaimed land with toxicity challenges.'
• 'Build an Airport with EV and Hydrogen fueling stations.'
• 'Build an Airport with kickbacks for a corrupt politician who shall remain nameless.'

And yes, the brief statements are all incomplete, part of the challenge is getting the levels of abstraction right so that you could drill down (Refine, Derive) as more specific info is provided (hypothetically of course).

Note how to get your model flexible across multiple statements, you'll need to get your inheritance hierarchy right, starting with an abstract Airport block; however, you also want to avoid inheritance hierarchy "explosion". Think carefully about how you can use redefined Properties.

By using some Satisfy relationships you should be able to get a nice Requirements table too with a SatisfiedBy columns. Note how different kinds of elements Satisfy the Requirements. Note how this can be tricky when there is a Block hierarchy (something that SysMLv2 now handles better than SysMLv1).