Artifact questions - types, visibility, data types, link typ
Artifact Type
Is it possible to create Artifact type for Model, Use Case, Table, picture so looking at the artifact you would not know what format it is. As Rich Text you can create the format text or table?
For the format picture with Insert Image is it limited in the search within the project. If you have a GUI picture that comes from Customer, how would you introduce this in the specification?
After creating the artifact (rich text update) and you hit the Save you do not automatically go to create the next artifact
Visibility of Artifact format
If the format of the artifact is Table since this is in the rich text, is therea way way to know what type?? In ReqPro you can create requirement type Use Case and it is obvious this is a Use Case
Is it possible to create Artifact type for Model, Use Case, Table, picture so looking at the artifact you would not know what format it is. As Rich Text you can create the format text or table?
For the format picture with Insert Image is it limited in the search within the project. If you have a GUI picture that comes from Customer, how would you introduce this in the specification?
After creating the artifact (rich text update) and you hit the Save you do not automatically go to create the next artifact
Visibility of Artifact format
If the format of the artifact is Table since this is in the rich text, is therea way way to know what type?? In ReqPro you can create requirement type Use Case and it is obvious this is a Use Case
2 answers
Hi Sabrina,
Let me try to answer your first and last questions together first.
First, I want to clarify artifact "type" vs "format" to make sure we're talking about the same thing. "Format" is basically what editor the artifact will open in. It is how the artifact looks. For now, there are only 3 formats: (1) text (opens in rich text editor), (2) collection (opens in collections editor), and (3) uploaded artifact (which is currently labeld "WrapperResource"; this applies to all uploaded artifacts and they open in the OS-defined editor). The system defines the available formats, and you cannot customize them.
When viewing the artifacts list, you can add a column to show the format of each artifact, but it will only be 1 of those 3 things, which isn't terribly useful. For example, Use Case specifications, non-functional requirements, features, UI specifications, etc. are all likely to be text artifacts, so you can't differentiate them by looking at the format.
Artifact "type" is how you provide meaning to the artifacts and differentiate them. "Types" are customizable by the user. So you can define artifact types called "Use case specifications", "Non-functional requirements", etc. You can add a column to the artifacts list that shows artifact type, and that will help you differentiate them. In the future, you will be able to assign a different icon to each type. (Note that you can also assign different sets of attributes to each artifact type).
As a format, there's no difference between "table" and "text", there's only "text". The text format uses the rich text editor which allows the creation of tables, so any text artifact can include a mix of tables and text. If it is important to identify which artifacts are table-based, you could create an artifact type that had "table" in the name and use the "text" format (but it would still be up to the user to add the tables in the text editor).
Does that answer your questions? Does that work for you?
For your other questions...
You have to upload the image first. In the artifacts list, click Create Artifact, and then choose Upload Artifact. That will add the image to the project (it's format is set automatically to "uploaded artifact", but you can assign any artifact type). There are already work items to improve this workflow in the future.
Can you describe more what you're looking for here? I'm not sure if this is in beta1, but you will be able to create a new artifact w/o having to return to the project page (using the Artifacts menu). Is this what you are looking for? Or do you want a quick way to say "create another artifact like this one"?
Let me try to answer your first and last questions together first.
Artifact Type
Is it possible to create Artifact type for Model, Use Case, Table, picture so looking at the artifact you would not know what format it is. As Rich Text you can create the format text or table?
Visibility of Artifact format
If the format of the artifact is Table since this is in the rich text, is therea way way to know what type?? In ReqPro you can create requirement type Use Case and it is obvious this is a Use Case
First, I want to clarify artifact "type" vs "format" to make sure we're talking about the same thing. "Format" is basically what editor the artifact will open in. It is how the artifact looks. For now, there are only 3 formats: (1) text (opens in rich text editor), (2) collection (opens in collections editor), and (3) uploaded artifact (which is currently labeld "WrapperResource"; this applies to all uploaded artifacts and they open in the OS-defined editor). The system defines the available formats, and you cannot customize them.
When viewing the artifacts list, you can add a column to show the format of each artifact, but it will only be 1 of those 3 things, which isn't terribly useful. For example, Use Case specifications, non-functional requirements, features, UI specifications, etc. are all likely to be text artifacts, so you can't differentiate them by looking at the format.
Artifact "type" is how you provide meaning to the artifacts and differentiate them. "Types" are customizable by the user. So you can define artifact types called "Use case specifications", "Non-functional requirements", etc. You can add a column to the artifacts list that shows artifact type, and that will help you differentiate them. In the future, you will be able to assign a different icon to each type. (Note that you can also assign different sets of attributes to each artifact type).
As a format, there's no difference between "table" and "text", there's only "text". The text format uses the rich text editor which allows the creation of tables, so any text artifact can include a mix of tables and text. If it is important to identify which artifacts are table-based, you could create an artifact type that had "table" in the name and use the "text" format (but it would still be up to the user to add the tables in the text editor).
Does that answer your questions? Does that work for you?
For your other questions...
For the format picture with Insert Image is it limited in the search within the project. If you have a GUI picture that comes from Customer, how would you introduce this in the specification?
You have to upload the image first. In the artifacts list, click Create Artifact, and then choose Upload Artifact. That will add the image to the project (it's format is set automatically to "uploaded artifact", but you can assign any artifact type). There are already work items to improve this workflow in the future.
After creating the artifact (rich text update) and you hit the Save you do not automatically go to create the next artifact
Can you describe more what you're looking for here? I'm not sure if this is in beta1, but you will be able to create a new artifact w/o having to return to the project page (using the Artifacts menu). Is this what you are looking for? Or do you want a quick way to say "create another artifact like this one"?
Hi Sabrina,
Let me try to answer your first and last questions together first.
Artifact Type
Is it possible to create Artifact type for Model, Use Case, Table, picture so looking at the artifact you would not know what format it is. As Rich Text you can create the format text or table?
Visibility of Artifact format
If the format of the artifact is Table since this is in the rich text, is therea way way to know what type?? In ReqPro you can create requirement type Use Case and it is obvious this is a Use Case
First, I want to clarify artifact "type" vs "format" to make sure we're talking about the same thing. "Format" is basically what editor the artifact will open in. It is how the artifact looks. For now, there are only 3 formats: (1) text (opens in rich text editor), (2) collection (opens in collections editor), and (3) uploaded artifact (which is currently labeld "WrapperResource"; this applies to all uploaded artifacts and they open in the OS-defined editor). The system defines the available formats, and you cannot customize them.
When viewing the artifacts list, you can add a column to show the format of each artifact, but it will only be 1 of those 3 things, which isn't terribly useful. For example, Use Case specifications, non-functional requirements, features, UI specifications, etc. are all likely to be text artifacts, so you can't differentiate them by looking at the format.
Artifact "type" is how you provide meaning to the artifacts and differentiate them. "Types" are customizable by the user. So you can define artifact types called "Use case specifications", "Non-functional requirements", etc. You can add a column to the artifacts list that shows artifact type, and that will help you differentiate them. In the future, you will be able to assign a different icon to each type. (Note that you can also assign different sets of attributes to each artifact type).
As a format, there's no difference between "table" and "text", there's only "text". The text format uses the rich text editor which allows the creation of tables, so any text artifact can include a mix of tables and text. If it is important to identify which artifacts are table-based, you could create an artifact type that had "table" in the name and use the "text" format (but it would still be up to the user to add the tables in the text editor).
Does that answer your questions? Does that work for you?
I can understand from a Tool Developer perspective you ar focussing on the Editor to OPEN. From a System Designer perspective the format could be important.
What you are proposing is a workaround. Would it then be possible to have a prefix for the Requirement ID?
For your other questions...
For the format picture with Insert Image is it limited in the search within the project. If you have a GUI picture that comes from Customer, how would you introduce this in the specification?
You have to upload the image first. In the artifacts list, click Create Artifact, and then choose Upload Artifact. That will add the image to the project (it's format is set automatically to "uploaded artifact", but you can assign any artifact type). There are already work items to improve this workflow in the future.
But the artifact by itself may not be the whole requirement and I need to add more info to finish writing the full requirement.
After creating the artifact (rich text update) and you hit the Save you do not automatically go to create the next artifact
Can you describe more what you're looking for here? I'm not sure if this is in beta1, but you will be able to create a new artifact w/o having to return to the project page (using the Artifacts menu). Is this what you are looking for? Or do you want a quick way to say "create another artifact like this one"?
The Beta at this time makes you use the Browser Bac button to get back and start with create artifct again, not user friendly at all and these additional navigation impacts the productivity of the person