User Tools

Site Tools


mbse:methodology:iw2015_agenda

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
mbse:methodology:iw2015_agenda [2015/01/16 12:59]
jcwatson
mbse:methodology:iw2015_agenda [2015/01/27 12:00] (current)
jcwatson
Line 25: Line 25:
  
 Based on your input we will select the use cases with the most interest and post them in the "​Reserved Meeting Rooms Table"​. Based on your input we will select the use cases with the most interest and post them in the "​Reserved Meeting Rooms Table"​.
 +
 +
 +===== Meeting Documentation =====
 +{{:​mbse:​methodology:​se_use_cases_incose_introrev2.pdf|Meeting Introduction Slides}}
 +
 +{{:​mbse:​methodology:​se_use_cases_incose_introrev2.pdf|Meeting Working Document}}
  
 ==== Reserved Meeting Rooms Table ==== ==== Reserved Meeting Rooms Table ====
 ^ Date ^ Time ^ Location ^ Use Cases Selected ^ ^ Date ^ Time ^ Location ^ Use Cases Selected ^
-| Tuesday, 1/27/2015 | 9 AM PT | Executive Suite 1635 | | +| Tuesday, 1/27/2015 | 9:00 - 11:00 AM PT   Executive Suite 1635  | | 
-| Tuesday, 1/27/2015 | 1 PM PT | Executive Suite 1635 | |+| Tuesday, 1/27/2015 | 1:00 -  2:30 PM PT   Executive Suite 1635  | | 
 + 
 +==== Remote Access - PARTICIPANT GlobalMeet Join Details ==== 
 +== Meeting Web Address: == 
 +[[https://​incose.pgimeet.com/​GlobalmeetFifteen|https://​incose.pgimeet.com/​GlobalmeetFifteen]] 
 + 
 +== Dial-in Number: == 
 +Access Number: ​ 1-719-325-2630 
 + 
 +Guest Passcode: 827 509 8579 
 + 
  
 ==== Initial Use Cases Table ==== ==== Initial Use Cases Table ====
 ^Use Case Name ^ Use Case Goal^ ^Use Case Name ^ Use Case Goal^
 |1. Analyze Stakeholders Needs   |The goal of this workflow use case is to identify all stakeholders and better understand and capture their required needs expectations,​ goals, and objectives across the entire product life cycle.| |1. Analyze Stakeholders Needs   |The goal of this workflow use case is to identify all stakeholders and better understand and capture their required needs expectations,​ goals, and objectives across the entire product life cycle.|
-|2. Derive System Requirements ​  |The goal of this workflow use case is to derive a set of system level requirements for the system-of-interest based on the all stakeholder'​s needs requirements. ​ |+|2. Derive System Requirements ​  |The goal of this workflow use case is to derive a set of system level requirements for the system-of-interest based on the stakeholder'​s needs requirements. ​ |
 |3. Derive Product Architecture ​ |The goal of this workflow use case is to evaluate the System Requirements and from them derive the most appropriate architecture to satisfy the customer needs.| |3. Derive Product Architecture ​ |The goal of this workflow use case is to evaluate the System Requirements and from them derive the most appropriate architecture to satisfy the customer needs.|
 |4. Evaluate System Safety |The goal of this workflow use case is to evaluate the system for safety related hazards and derive a plan to mitigate these risks.| |4. Evaluate System Safety |The goal of this workflow use case is to evaluate the system for safety related hazards and derive a plan to mitigate these risks.|
 |5. Collaborate with Implementation Domain Team  - (software, mechanical, electrical)|Goal of this workflow use case is provide an automated capability to effectively share information between Systems Engineering and the component implementation engineering domains, such as the software, electrical, and mechanical domains.| |5. Collaborate with Implementation Domain Team  - (software, mechanical, electrical)|Goal of this workflow use case is provide an automated capability to effectively share information between Systems Engineering and the component implementation engineering domains, such as the software, electrical, and mechanical domains.|
mbse/methodology/iw2015_agenda.1421431193.txt.gz · Last modified: 2015/01/16 12:59 by jcwatson