GENESYS: Meeting with Professor Long - lydia-wu/cadence GitHub Wiki
Alloway, Hunter; Last Edited: 2021-09-01
ENGR 481: Guideline When Working in GENESYS
Stakeholder Requirements under the Requirements section in GENESYS is where we will be starting: creating the system requirements from Mr. Stanesell.
Function is behavioural domain-the ability to add and export activity diagram
Physical Domain is Components-Block definition diagrams, FFBD and physical flow diagrams R.2 is system requirements S.1 is stakeholder requirements
Everything that falls under the Wasson Model has to do with the Technical Design, but we are also focusing on management aspects (quality management etc.)
We should be using GENESYS to collect this data for the final report
Decision gate 1 is the approval of stakeholder requirements from the client and Dr. Bae
For Decision gate 2, we might realize that we need to modify the stakeholder/system requirements
If a stakeholder requirement has already been approved but needs to be changed, we need prior approval from Dr. Bae and the client in order to make those changes from decision gate 1
“Concerns” in GENESYS may turn into risks under the Requirements field. When this happens, we will use the SYS ENG handbook to manage this category and alter the information in this
Completing the baseline in Project is the same as making a change in a Decision Gate. We are already starting to talk with the instructor before this happens to proceed along the modified lines we modify this for Decision gate 2 which is the first thing to be introduced during that presentation period
Change, risk, and product requirements are the three main factors that have an impact on each Decision Gate and should be closely monitored