-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
conops template #116
conops template #116
Conversation
- TODO: generate box in plantuml
- replaced plantuml link with code embedded directly in source
d53f31d
to
792da38
Compare
|
||
=== Organization | ||
|
||
_Describe the organization unit that is responsible for the governance, and describe policies on organizational structure and human resource in system development._ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test comment
|
||
===== Attribution | ||
|
||
This document is adapted from the ISO/IEC/IEEE 29148:2011 _International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering_, available at https://standards.ieee.org/standard/29148-2011.html. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great link
|
||
== Scope | ||
|
||
_Describe the scope of this document by specifying the organization's business domains to which it applies._ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@capsulecorplab this Conops seems much more focused on the people running the operation than the engineering and mechanical operations of the payload itself. This is in contrast to John Paterson's ConOps which is much more focused on the latter.
Should we add another section that's more narrowly focused on the engineering/mechanical processes, or is that meant to be embedded in the bigger context that's outline here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that too. We can either deviate from the original ISO/IEC/IEEE 29148:2011 spec and rewrite the template to be more engineering focused, or we can try to refactor John's ConOps doc to fit into the bigger context as you suggest. I don't have a strong preference toward either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
John had actually written the OpsCon, where as Sean has focused on Conops. They are slightly different. Check this source for a quick difference: https://plus.google.com/104099794938550497171/posts/D51e89gh4RR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Document type in this case is Mission Concept and ConOps is the document name
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the rest of the document seems fine. However, we can start investigating to determine each points mentioned in the table of content
ef0f29a
to
b0b7170
Compare
6a4eb23
to
09a0f74
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to start.
|
||
== Scope | ||
|
||
_Describe the scope of this document by specifying the organization's business domains to which it applies._ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Document type in this case is Mission Concept and ConOps is the document name
|
||
== Scope | ||
|
||
_Describe the scope of this document by specifying the organization's business domains to which it applies._ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the rest of the document seems fine. However, we can start investigating to determine each points mentioned in the table of content
Draft template for conops of #97
Preview of conops template available here