CaseComplete Community

Hi Im new here, just testing casecomplete right now.

1 - I was wondering How can I use casecomplete to define the interface requirements? such thing as forms, fields, etc..is this even possible?

 2 - also is there any plans to have case complete follow IEEE 830 standards? (or can I do this myself via output to template??)

Hi Robert,

Hope you're enjoying CaseComplete and find it useful.

In answer to your first question: While not directly supported, there are several ways you could define interface requirements:

1 - Use the glossary.  For example, you might want to create an entry called "customer data" and define it as specific as you need, such as, consists of First Name (20 characters), Last Name (30 characters), address1, address2, etc.  Then when you type "customer data" in your use case steps CaseComplete will automatically create a hyperlink to it.

2 - Create a UI mockup by creating a diagram.  Note diagrams can be owned by any package, actor, use case or requirement.  You can see an example of a mockup of the CaseComplete website being edited in CaseComplete here:
http://www.casecomplete.com/Images/ccmockup.png

3 - Create requirements and attach them to the appropriate use case(s).  Attach them either via drag/drop between the main list and the model browser, or via the details tab a of use case.  Note that the "Type" field for requirements is customizable via Tools/Predefined fields.  So you could create a new requirement type called Interface if you wanted.

Regarding your 2nd question, there aren't immediate plans to support IEEE 830, but I'll add it to our feature requests database for consideration in a future release.  CaseComplete Word reports are easy to customize, so you might want to try it yourself.  Please see Custom Word Reports user's guide available from the help menu.  If you give it a try, let me know how it goes.

---

Doug
Serlio Software

Thanks for your informative dresponse doug.

Im trying to create a template for case complete, but it does not properly.

Our SRS documents have been formated to conform with IEEE 830 standard.
In the document we have the following headings, and in case complete I put them in packages/sub packages as described below.


1. External interfaces  <--- parent package
2. Functions <--- parent package    
3. Performance Requirements <--- parent package     
4. Logical Database Requirements <--- parent package
5. Design Constraints <--- parent package
5.1    Standards Compliance <-- sub package under Design Constraints
5.2    Software System Attributes <-- sub package under Design Constraints
5.3    Reliability <-- sub package under Design Constraints
5.4    Availability <-- sub package under Design Constraints
5.5    Security <-- sub package under Design Constraints
5.6    Maintainability <-- sub package under Design Constraints
5.7    Portability <-- sub package under Design Constraints


Each requirements are contained under the allocated parent packages and sub package.

What I would like to do now is have case complete generate a report to display all the requirements under the correct packages heading.

But it does not work properly...with the following template
It displays all the requirements under the correct sub packages. But the parent package is not being displayed., I might need to nest the package??

$groupRequirementsByPackage
1.    $Package [this is the parent package heading]
1.1    $Package [this is the sub package heading]
$groupCurrentGroupByID

-----table starts here--->

ID    Name
$tableCurrentGroupSortID $ID    $Name
$Description $DeleteEmptyLine
Details   
Type: $Type    Group: $Package
Related Documents
$tableRelatedDocuments $Name
Use cases that reference this requirement   
$tableUseCasesSortName $Name    $ID

-----table ends here--->

$endgroupCurrentGroupByID
$Break
$endgroupRequirements

My first recommendation is that instead of using $groupRequirementsByPackage you should use $outlinePackages or $repeatPackages instead.  $outlinePackages is especially useful if you want to use hierarchical auto-numbering in Word, but it's tricky since the report template requires custom numbering.  Your best bet is to start with an existing report that uses $outlinePackages (such as CompleteByPackageFull) and then either modifying that report and doing a Save As to your new report template, or copying the line that contains "1 $Name" which represents the package name and pasting that into your custom report.  If you don't care about the numbering, then you can use $repeatPackages instead.  The advantage of using $repeat or $outline instead of $group is that the packages will be shown in the same order that the appear in the model browser.  With $group, they will be in alphabetic order.

So here is the rough outline of how your report will look.  I use a $repeat for the requirements for simplicity here, but you could  also use a $table.

$outlinePackages
1 $Name <-- copy/paste this line from CompleteByPackageFull

$repeatRequirementsSortID
$ID $Name
$Description $DeleteEmptyLine

$endrepeatRequirements

$endoutlinePackages  <-- blank line above this keyword required

 

---

Doug
Serlio Software

Solution provided above, did not work?

Can you give more details as to what didn't work?  Feel free to send your report template to the support email address (@serlio.com).  That may be the easiest way to diagnose the problem.

---

Doug
Serlio Software

This works (see below).

question,

1- can I select the parent package -- branch?

2- can I not list empty packages?

 

-----------------------------------

Normal 0 false false false EN-AU X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";}

$outlinePackages

1.1     $Name

$Description $DeleteEmptyLine

 

$repeatRequirementsSortID

ID	Name
$ID	$Name
$Description $DeleteEmptyLine
Details
Type: $Type		Group: $Package

 

 

 

 

Related Documents

$tableRelatedDocuments $Name

 

Use cases that reference this requirement
$tableUseCasesSortName $Name	$ID

 

$endrepeatRequirements

 

$endoutlinePackages

Hi Robert,

If you're using $outlinePackages, I think the answer is "no" to both questions. Our resident Word report guru is out on vacation until next Thursday so I could be wrong. I will update this post with a definite answer late next week.

---

Jeff
Serlio Software

ok

Hi Robert,

I'm still not sure if I completely understand your first question but you can select the parent package in the Exported Items section of the Generate Word Report dialog page.

In answer to your second questions, you could use $outlinePackages where Requirements Exist to skip over empty packages.

---

Jeff
Serlio Software