|SAT Home||About Us||Contact||CassBeth Products||
The following survey will help the user understand how SAT fits into an existing requirement management tool.
|1. Capturing Requirements / Identification||SAT is an automation aid to help organizations write clean useful
specifications that contain clear, complete, consistent, and testable requirement
The need for clear consistent testable specifications has been apparent for over 2 decades. The approaches have been to create formal specification methods or to manage informal written words, which represent requirements. The latter has become the primary method of creating specifications for most organizations. The System Requirements Database (SRDB) has been introduced to help manage requirement statements, however the SRDB, though effective at showing parent child relationships and managing attributes does not address the fundamental problem of creating a clear consistent testable requirement object. Different organizations have unique ad hoc solutions to this dilemma. What has surfaced is the potential need for a method and tool to analyze a specification and provide guidance in corrective actions early in the life cycle, prior to next level decomposition, and long before test.
SAT is a method and tool that allows you to codify your own 'working' specification analysis rules. Embedded within SAT is the principal of layered services. This principal allows SAT to immediately provide results as rules mature and SAT mining techniques are refined in your organization. In the end the services allow mining of potential key requirements from analysis documents and comparison with the actual key requirements in the baseline - your specifications.
A typical use case is to submit preliminary requirements into SAT prior to importing into the SRDB. Once the requirements are in the SRDB, as they continue to evolve, perform periodic exports from the SRDB to SAT to clean up the new requirements. Prior to even developing the initial set of requirements, use SAT to mine related documents for key requirements. The related documents can be analysis documents, from the current program or other programs. Compare the key requirements mined from related documents with the key requirements exported from your SRDB into SAT.
|1.2 Automatic parsing of requirements||SAT will parse a Microsoft Word document and create an object based on sentences and list items. SAT will accept any text format file. SAT will also accept exports from other tools in Microsoft Excel .csv format.|
|1.3 Interactive/semi-automatic requirement identification||SAT uses regular expression patterns to search for user defined imperatives (requirements). For example the user can enter "shall" or "shall|will|must" to identify the requirements in the SAT analysis set. The requirements are reported in color, based on sat display filter settings.|
|1.6 Requirement classification||SAT is a document-mining tool. As such it will accept user-defined rules and capture requirements and objects based on the rules. SAT will then provide various displays and metrics of the results. For example the service that supports key requirements analysis will mine the specification for items such as EMI, TEMPEST, Environment, Security, Flight Data Processing, etc.|
|2. Capture System Element structure||SAT can be used to mine the results of requirement allocation. For example, if the requirements have been allocated to various HWCI's and CSCI's, SAT will selectively report on each object allocation and provide a metrics summary of all the allocations. The best way to view the service is as a multidimensional filter. To do this, export from your SRDB using the .csv format (excel), establish your services and rules in SAT, and run SAT reports as the SRDB is populated and matures. Think of it as a super charged search engine that can be used to process and visualize your SRDB contents via periodic exports.|
|2.1 Graphically capture systems structure||SAT is able to identify and count child requirements in a document based on user defined rules such as paragraph level, or paragraph names. This information is presented in a metrics table that shows the number of child requirements for each defined parent, and graphically where the document structure is presented in terms of document shapes (pyramid, inverted pyramid, rectangle, random, etc.)|
|2.2 Textual capture of system structure||SAT can be used to mine the results of requirement allocation. For example, if the requirements have been allocated to various segments, subsystems, HW, SW, functions, threads, use cases, HWCI's, CSCIs, etc, SAT will selectively report on each object allocation and provide a metrics summary of all the allocations. It will also show the missing allocations.|
|6.6.3 Other ad hoc queries & searches||Visualization of a database is very hard. There are extremely powerful other vendor SRDB tools and for the most part the filters satisfy may user needs. However, using SAT to process and visualize an SRDB export view is extremely powerful because the "filters" are replaced with SAT services and rules that translate to very complex multidimensional queries. That is why SAT is able to process requirement text and help the user to write clear, consistent, testable requirements. It is also why SAT is able to process the requirement text and offer an automated key requirements service. In general a valid use of SAT is to process the initial document with SAT prior to importing into the SRDB, then periodically process the "exported document" with SAT as the SRDB matures. Each time using the SAT Requirement Text Analysis service and the SAT higher level services as they are added and matured by the staff. Keep in mind that SAT can be used to process documents of previous and similar systems to help identify the key requirements of your system before you have even started to create your baseline requirements.|
|7. Groupware||SAT generates HTML reports. The SAT engine is not needed to view and navigate the static HTML reports. The reports can be placed anywhere on the user network and users can access and view the reports. SAT is licensed to operate on a single computer so if multiple users need to operate the SAT engine, multiple licenses will need to be purchased.|
|7.1 Support of concurrent review, markup, & comment||If there are multiple SAT installations, each licensed installation can access the same data and perform analysis in parallel. The users save the reports and the resulting file names are at the discretion of the users. If a report is saved it can be subsequently accessed and viewed by anyone on the network. If they have a SAT engine, they can reprocess the same report with the same data, new data, same settings, new settings, in any combination.|
|8. Interfaces to Other Tools||SAT must work closely with other tools that house requirements. The interface is via an export from those other tools in either text format or spreadsheet format. The nature of SAT rule processing is such that the user can filter on any exported attributes regardless of how a user names the attribute, such as "IsReq", "Allocation", "Test", "PUI preface", etc. SAT will accept ASCI .txt, Excel .csv, Word .doc file formats. Because of the mining nature of SAT, the .doc file import does not filter control characters, it treats the input as ASIC and shows everything.|
|8.1 Inter-tool communications||SAT must work closely with other tools that house requirements. The interface is via an export from those other tools in either text format or spreadsheet format.|
|8.1.4 Import of existing data from various standard file formats||SAT must work closely with other tools that house requirements. The interface is via an export from those other tools in either text format or spreadsheet format. The nature of SAT rule processing is such that the user can filter on any exported attributes regardless of how a user names the attribute, such as "IsReq", "Allocation", "Test", "PUI preface", etc.|
|8.2 Intra-tool communications||SAT reports can become templates and templates can become reports. In all cases they are HTML format. The HTML files can be transported and shared across networks.|
|8.2.1 Exchange of information between same-tool different installations||SAT reports can become templates and templates can become reports. In all cases they are HTML format. The HTML files can be transported and shared across networks.|
|9. System Environment||SAT is currently a single user application that runs on Windows (95, NT, 98, XP, 2000). Server multi platform (UNIX) versions will be available in the future. This is a marketing decision. SAT has been tested on a platform as small as Win95 266Mhz 3GB Hard drive. The SAT program is approximately 20 MB.|
|10. User Interfaces||The SAT GUI is HTML and uses the computer default browser (Netscape, IE, etc). All other applications can continue to operate. The user can move between applications as needed. At anytime the browser can be minimized. The interface look and feel is that of an Internet application rather than Windows. The interface combines the tool settings and user output all in one HTML report. The user starts SAT by clicking on a shortcut from the Start menu or the desktop. When SAT starts it opens to the default template. The user can then access a previous analysis run, another template, or start working with the default template. Multiple SAT browsers or tabs can be open and operating. SAT templates containing rules and services can be saved and re-executed on the same data or new data.|
|10.1 Doing one thing while you are looking at another||The SAT GUI is HTML and uses the computer default browser (Netscape, IE, etc). All other applications can continue to operate. The user can move between applications as needed. At anytime the browser can be minimized. The interface look and feel is that of an Internet application rather than Windows. Multiple browsers can be open at the same time running reports, examining previous reports, templates, and specifications / documents submitted or to be submitted to SAT for analysis.|
|10.4 Which window standard do you follow?||The SAT GUI is HTML and uses the computer default browser (Netscape, IE, etc).|
|10.5 Executable via scripts or macros||This is the heart of SAT, the ability to create templates from reports and reports from templates, so that a user can analyze new data or the same data using a template or a modified template. The template is the HTML web page, which is saved by the user, as desired.|
|10.6 Web browser interface?||The SAT GUI is HTML and uses the computer default browser (Netscape, IE, etc).|
|12. Support and Maintenance||There is no warranty. Please see license for details. Basically no liability is assumed. Demo versions are available upon request. There is no network License. SAT is sold with an annual license that must be renewed. Minor releases will be made available without cost, major releases will require a fee. It is expected that the basic SAT services can be learned via OJT in 1-2 days. More complex services will require more time. SAT includes HTML based help that has typical use cases. There is also an embedded power point presentation on the theory of SAT. An audio version of the SAT theory presentation is packaged separately. We do have a web site and the SAT page is at www.cassbeth.com/sat.|
|12.5 Internet access / Website||There is an Internet web site. www.cassbeth.com/sat|
|13. Training||It is expected that the basic SAT services can be learned via OJT in 1-2 days. More complex services will require more time. SAT includes HTML based help that has typical use cases. There is also an embedded power point presentation on the theory of SAT. An audio version of the SAT theory presentation is packaged separately.|
|13.4 Software installation with only basic training||SAT uses a standard install shield. No special knowledge is needed for installation. To activate the full features of SAT the user will need to enter the licenes keys provided at the time of purchase.|