Can ALISA requirements help me write better and more structured requirements?

[Carlos Ramos]

I noticed that I can write a requirement and use the “for” clause to reference a feature on the system boundary. That helps me capture the interfaces and ensure I have requirements because OSATE flags missing features. What else can I do out of the box with OSATE to help me out? I. Know there was once some research with “assume / guarantee” constructs but I want to avoid additional plug ins for now and just get the basics down.