Requirements Capturing?

Hi,

I am looking into using the Requirements Capturing facilities within the SDE, but can not find any documentation anywhere. What I am looking for is firstly how to use the section within the SDE context, and secondly for any guidance, documentation on usage of the elements with in the section in line with UML.

Hopefully someone will be able to point me in the right direction.

Many Thanks

Muttley :slight_smile:

Dear Muttley,

Thank you for your interest in our products. Requirement capturing can be done with the following features in SDE (the links below are flash movies related to the features).

Use Case Identification with Textual Analysis
The Textual Analysis tool helps you to identify user cases out of textual description of your system. This give you a clear idea on what the user I looking for and what you need to build.
http://www.visual-paradigm.com/product/sde/ec/demos/requirements/textualanalysis.jsp

Use Case Detail Editor
The Use Case Detail Editor allows you to detailing the use case with flow of event. The textual use case description can be transfer to textual analysis tool and perform use case level analysis. This helps you to identify domain classes also test case scenario. The flow of event can further generate into system level sequence diagrams.
http://www.visual-paradigm.com/product/sde/ec/demos/umlsupport/usecasedetail.jsp
http://www.visual-paradigm.com/product/sde/ec/demos/umlsupport/flowofevent.jsp
http://www.visual-paradigm.com/product/sde/ec/demos/umlsupport/foetosequence.jsp

Business Process Diagram
The Business Process Diagram helps you to understand complex business workflow using the OMG’s BPMN. You can have better understand the entire business activities (problem space) and identify use cases (solution space) from which the parts of activities planned to be automated.
http://www.visual-paradigm.com/product/sde/ec/demos/bpmodeling/bpd.jsp

Requirement Diagram
SysML includes a graphical construct called requirement diagram to represent text based requirements and relate them to other model elements. The requirements diagram captures requirements hierarchies and requirements derivation, and the satisfy and verify relationships allow a modeler to relate a requirement to a model element that satisfies or verifies the requirements. The requirement diagram provides a bridge between the typical requirements management tools and the system models
http://www.visual-paradigm.com/product/sde/ec/demos/requirements/requirement.jsp
http://www.visual-paradigm.com/product/sde/ec/demos/requirements/definecusttype.jsp

Model Transitor
The Model Transitor helps you to link up the transition between models thus establish traceability of your analysis and design.
http://www.visual-paradigm.com/product/sde/ec/demos/modeltransitor/transitmodel.jsp
http://www.visual-paradigm.com/product/sde/ec/demos/modeltransitor/tracemodel.jsp

If you require any further information, please feel free to contact me again.

Best regards,
Rain