Requirements Capture
Capture, organize, manage and realize requirements with SysML Requirement Diagram. Build or customize your own requirement types.
Requirement diagram
Requirement specifies capability or condition that must be delivered in the subject (target system). Capability usually refers to the function that the system must support and we call it functional requirement. Condition usually means that the system should be able to run or produce the result in specific constraint, and we call it non-functional requirement. Smart Development Environment for Eclipse provides a SysML requirement diagram for specifying and analyzing requirements. The following movie shows how to draw requirements, input detail of requirement (e.g. kind, verify method...), derive requirement and relate requirement with test case. The movie also shows how to switch between diagram view and tabular view. Finally, the movie demonstrates how to create or customize requirement types for your team.
Requirement grid
Requirements gird provides a tabular view of all requirements in the project. You can create requirements in grid.
Glossary grid
Capture domain specific terms by glossary grid. Describe domain terms with textual description or voice documentation. Smart Development Environment for Eclipse supports adding multiple aliases to single glossary term. In the latest release, export and import glossary to Excel is supported. The following movie demonstrates the usage of glossary grid.
Test case editor
Requirement diagram visualizes relationships between requirements and test cases. By connecting requirement to multiple test cases with <verify> relationships. Smart Development Environment for Eclipse provides a easy-to-use test case editor for testing team to write test case. Testing team can define steps, procedures and expected result in the test case editor.
Textual analysis
Smart Development Environment for Eclipse supports textual analysis for extracting candidate model elements from text document. The normal textual analysis process is to collect or prepare (noted in meeting) text document, paste the text document in textual analysis pane, read through the document, highlight and drag domain related nouns to workspace, write description in data dictionary, select good set of candidate item and then create model elements from candidate items. Textual analysis supports extracting use case, actor, class, action, task, sub-process and event. The following movie shows how to use textual analysis to identify use cases and actors.
CRC cards
Class-Responsibility Collaborator (CRC) card is designed for identifying classes and operations in object-oriented approach. Smart Development Environment for Eclipse provides a CRC Card diagram for software team to brainstorm, records, analyze and maintain CRC cards in systematic and collaborative way.
User interface designer
During requirement capturing and design stage, system analyst may need to illustrate and document the screen designs to customer or among team members. Traditional screen designers usually tie up with specific programming language that inherits a lot of constraints when designing and annotating screens in early development stage. Smart Development Environment for Eclipse provides a full featured screen designer for system analyst to illustrate and annotate screen designs without limitation. The following movie shows how to use user interface designer to design form-based application with text field, menu, table and tree.
Web screen mock up
Smart Development Environment for Eclipse provides a full featured web page designer for system analyst to illustrate and annotate screen designs without limitation. The following movie shows how to use user interface designer to design web application user interface.
