I am also a newbie to this forum, but I think what you mentioned is the proper order. But, I usually start creating test case summaries and my test plan when the requirements are published. It differs from organization to organization as far as I know. We have an SRD (System requirements definition). Then, we don't have FS b/c our software is a package. So, I don't know if my answer helps, but I didn't want you to have no answers <font color="purple"> </font> [img]/images/graemlins/smile.gif[/img]
welcome to SQAForums. Please realize that this forum is staffed by volunteers residing around the world. Volunteers will and do answer questions when they have the time or interest and your urgency is not theirs, so please be patient.
As to your question what is the name/definition of RS and FS that you are talking about - acronyms and abbreviations tend to man different thongs to different people.
Usually the sequence of actions and the resulting documents are directly related to the SD LC in place. There are many variations that can happen but also some general guidelines that usually do happen.
This is not absolute but a general guideline
Requirements (if produced) are done first
Technical specifications and/or design
Test Strategy can be done at any time but for me always before Test Plan
Test Plan started after requirements
Test Cases can be started after requirements