.Click the “Share” command (top right of screen) .On project share window, enter the email address of user that you would like to share with and set their editing rights for the project (Owner, Read, Write) .Click “Share”. The person’s Name and Email Address should pop-up under the list of users. Click “Done” .When the person comes online; you should see a notification under the “Online Users” section (bottom-right corner). .Click on “Online Users”. You should see the person in the list, and if he/she is online & available to chat. .Click on the person’s name. A separate chat window should open, which allows you to chat with the person online user, while both parties are able to view the shared project Table . Database Viewer Test Case Requirement Viewer Test Case Number Description Expected Result RQ-001 Creating, Saving, and Viewing Requirement Entities: NOTE: In Innoslate, Requirements can be created in two ways – either from Database view by clicking ‘Create Entity’ or from ‘Requirements’ view by clicking ‘Create Requirement’. .Sign in into Innoslate .Click on the “Create Entity” icon .Select “Requirement” from the popup .Fill in the Name, Number, and Description .Click on the “Save and Close” icon .Follow the above steps to create all of the requirements for MEEPAS project After doing a “Save and Close” for the last requirement that you have created, make sure that all of the created requirements are visible from the Database View and Requirements view. RQ-002 Establishing Relationship with an Action: .From the Database view, click on the “Create Entity” icon .Select “Action” from the popup .Fill in the Name, Number, and Description .On the right side click ‘Add’ on ‘traced from Statement’ row .From the popup select the requirement that this Action is satisfying .Click on the “Save and Close” icon After completing the Add operation you should be able to see the Requirement on the right side. You should be able to switch to the Requirement from Action screen and vice versa. RQ-003 Editing Requirements: From the Requirements view, Click ‘Edit’ on the row of the requirement that you want to edit. Modify Name, Number, and/or Description The requirements view should reflect the change that you applied
described in user manual The Innsolate™ shall store Requirement Report templates within the tool. RG-001 Pass The Innoslate™ shall export Requirement Reports in Microsoft Word. RG-005 Pass F-4.1.2 The Innoslate™ shall generate a Concept of Operations (CONOPS). RG-002 Pass The Innoslate™ shall generate a CONOPS template. RG-002 Pass The Innoslate™ shall allow users to assign existing entities to sections within the CONOPS template. RG-002 Fail (refere to Req. results) The Innoslate™ shall store the CONOPS template and associated content within the tool. RG-002 Pass The Innoslate™ shall export the CONOPS in Microsoft Word. RG-005 Pass F-4.1.3 The Innoslate™ shall enable users to generate an enterprise architecture report, i.e., Department of Defense Architecture Framework (DODAF). RG-003 Fail – Not implemented yet F-4.1.4 The Innoslate™ shall enable users to generate Project Management Plans. RG-001 Fail – Not offered F-4.1.5 The Innoslate shall enable users to generate Risk Management Plans. RG-001 Fail – Not offered F-4.1.6 The Innsolate™ shall enable users to generate Test and Evaluation Master Plans (TEMP). RG-001 Fail – Not offered F-4.1.7 The Innsolate™ shall enable users to generate Implementation Plans. RG-001 Fail – Not offered F-4.2 The Innsolate™ shall store exported reports in Microsoft Word in the tool. RG-005 Pass F-5 Collaboration F-5.1 The Innoslate™ shall enable users to share projects. DB-010 Pass F-5.1.1 The Innsolate™ shall allow users to search for other Innoslate™ users/project members. DB-010 Fail – Currently have to know members emails addresses and manually enter F-5.1.2 The Innoslate™ shall allow users to assign user roles to projects, i.e., Read Only, Read/Write, Owner. DB-010 Pass Users with Owner permissions shall have full control of the shared project. DB-010 Pass
Users with Read/Write permissions shall have the ability to add, modify, and delete project content. DB-010 Pass F-5.1.2 The Innsolate shall notify Read/Write users of project changes (e.g., modifications, deletions, additions). DB-010 Fail – Feature currently not available F-5.1.3 The Innoslate™ shall notify the Owner users of project changes (e.g., modifications, deletions, additions). DB-010 Fail – Feature currently not available F-5.1.4 Users with Read Only permissions shall only read content. DB-010 Pass Appendix C: Requirements Traceability – Non-Functional UID Requirements Test Case Pass/Fail NF-1 Accessibility NF-1.1 The Innoslate™ shall be accessible on multiple browser platforms. N/A Fail – Not accessible to IE 8 and older users NF-1.2 The Innoslate™ shall be accessible on Google Chrome. N/A Pass NF-1.3 The Innoslate™ shall be accessible on Mozilla Firefox. N/A Pass NF-1.4 The Innoslate™ shall be accessible on Internet Explorer version 8 and newer. N/A Fail – Only accessible to IE 9 users. NF-2 Response Time NF-2.1 The Innoslate™ shall enable users to add and remove large batches of entities into/from the database. Large bacth is defined as at least 100 entities. DB-008 Fail NF-2.2 The Innoslate™ shall enable users to import and export documents in less than 30 seconds. DB-009, DA-001, RG-005 Pass NF-2.3 The Innolsate™ shall generate report templates and documents in less than 30 seconds. RG-001, RG-002 Pass NF-3 Robustness NF-3.1 In cases where inputs are invalid, the Innolsate™ shall not terminate, but display an error message describing the problem and troubleshooting solution. DB-001, DB-008, DB-009, RQ-001, Fail
RQ-004, DA-001, DA-002, RG-001, RG-002, NF-4 Usability NF-4.1 Users of Innoslate™ shall require minimal training or experience in using systems engineering management tools to operate the Innoslate™. N/A Pass NF-4.2 Users shall be able to complete the following systems engineering activities within the Innoslate™: Project Management, Requirements Elicitation and Management, Concept Development, System Design and Architecture. RQ-001, RQ-003, RQ-004, RG-001, RG-002, RG-004 Pass – Only activities that cannot be completed is PM activities Appendix D: Test Case Results – Database Viewer Detailed Procedure Steps Step # Step Description Expected Results/Method of Recording Actual Results (Firefox) Actual Results (Chrome) DB-001 Creating, Saving, and Viewing Class Entities: .Sign in into Innoslate .Click on the “Create Entity” icon .Select an entity to create (example, “Action”) .Fill in the Name, Number, and Description .Click on the “Save and Close” icon .Follow the above steps to create all of the other available entities . After doing a “Save and Close” for the last entity that you have created, make sure that all of the created entities are visible from the Database View. .Namely, you should see the following class entities in the Database View: Action, Artifact, Asset, Characteristic, Cost, Decision, Input/Output, Link, Measure, Physical, Requirement, Resource, Risk, Software Interface, Statement, and Time Was able to successfully create, save, and view all of the aforementioned class entities I entered many artifact and statement entities associated with the MEEPAS project Concept of Operations. I entered many artifact entities associated with the MEEPAS
architecture diagrams (OV-2, OV-5, OV-6). I was able successfully create, save and view these entities within the Database view. DB-002 Searching the Database .From the Database view, locate the Search textbox (Top-Right corner of screen) .Type in the Full-Name of one of the entities you created during step DB-001 .Click on the Search Icon (the Blue Square icon with magnifying lens) .Do the above step by only typing-in part of a name of an entity (example, if the Full Name is “My First Action”, type in only one of the words: “Action” or “My” or “First” or a combination of these Should be able to search entities that are contained in the Database using both the Full-Name as we Part of the Name of the entity Was able to search the existing entities using both their Full Names as well as Parts of their Names I was able to search on entities created as part of step DB-001 and successfully returned the expected entity results. DB-003 Sorting Search Results from Database .From the Database View, Click on each of the Attribute Columns (Number, Name, Class, Modified) The search results are expected to be sorted by each respective attribute type that has been clicked for sorting (Number, Name, Class, Modified) Was able to sort the search results using Number and Modified attributes, but can only sort in one direction. For example, cannot sort “Earliest to Latest” on the Modified field (Can only sort “Latest to I sorted the Database View list using the column headings number, name, class and modified. The order of
Earliest”). Cannot sort at all using the other 2 attributes (Name and Class) entities was displayed as expected in ascending and descending order. DB-004 Filtering the Database View .From the Database view, click on the “Filter Classes” command area of view) .From the drop-down list, click on each entity types that appears For each of the that has been clicked, all of the created entities for that specific type need to be returned by the database. For example, if you happen to have 2 Action entities previously created, both of these Action entities should be returned when selecting an Action entity from the list Was able to filter the Database View for selected entities, as expected I filtered the Database view by selecting the relevant entity types of artifact, statement, and requirement. The resulting list of entities was displayed based on the filter criteria as expected. DB-005 Scrolling the Database View’s Window .Make sure that you have more than 30 entities created in your test project .Scroll up and down the Database window a few times While scrolling down the Database window, once you reach the 30th entity, the remaining entities (the 31st and up) need to be added to the window’s view for viewing Was able to view the 31st and over entities while browsing the DB window Scrolling the database view interface when more than 30 entities exist/have been saved returns additional rows until the end of the list is reached. It would appear this limit is 50 rows at a time. DB-006 Deleting Entities from Database View .From the Database view, click on the The selected entities are expected to be deleted from the Database View Was able to delete a set of entities from the Database view Selected one and many entities to be
Number, and Description .Click on the “Save and Close” icon .Follow the above steps to create all of the requirements for MEEPAS project RQ-002 Establishing Relationship with an Action: .From the Database view, click on the “Create Entity” icon .Select “Action” from the popup .Fill in the Name, Number, and Description .On the right side click ‘Add’ on ‘traced from Statement’ row .From the popup select the requirement that this Action is satisfying .Click on the “Save and Close” icon . After completing the Add operation you should be able to see the Requirement on the right side. You should be able to switch to the Requirement from Action screen and vice versa. Was able to trace from a requirement to an Action and vice versa Performed requirements validation, the process took approximately 30 seconds the first run through and then less than 5 seconds on subsequent runs; Validate requirements scoring is inconsistent, as two requirements that were almost identical were given very different scores. RQ-003 Editing Requirements: .From the Requirements view, Click ‘Edit’ on the row of the requirement that you want to edit .Modify Name, Number, and/or Description .Click ‘Save and Close’. The requirements view should reflect the change that you applied The Requirements view was updated to reflect the change applied on the Edit screen Edit requirements saved data as expected. The data was stored and reflected in both the requirements view and the requirement entry screen. RQ-004 Obtaining Quality Scores for 1. Innoslate should calculate the quality score for each Innoslate did the Quality Score computation and
Requirements: 1.From the Requirements view, click on the “Validate Requirements” 2.From Requirements view select the requirement that you want to view/edit the quality score for and manually edit one or more of the nine quality score parameters (Clear, Complete, Consistent, Correct, etc.) requirement based on a nine point quality check 2. Innoslate should automatically recalculate the quality score for the requirement and display it displayed the result RQ-005 Create a requirement hierarchy: .Create a top level requirement by following steps in RG-001 .Using the same steps create a few child level requirements (decomposing the top level requirement) .Edit the top level requirement and select ‘Add’ on ‘decomposed by Children’ at the right side .Select the child The child level requirements should added at the right side under the section ‘decomposed by Children’ Clicking ‘View’ on any of the child requirements should switch to the child requirement and should show the parent requirement under ‘decomposes Parent’ section The child requirements were shown under ‘decomposed by Children’ section on parent screen and on the child screen, the parent requirement was shown under ‘decomposes Parent’ section
requirements Appendix F: Test Case Results – Document Analyzer Detailed Procedure Steps Step # Step Description Expected Results/Method of Recording Actual Results (Firefox) Actual Results (Chrome) DA-001 Uploading Documents using the Automated parser .Make sure you have a DOCX and a PDF file on your local computer ready to upload .From Database View, click on the drop-down next to the “Import” menu .Choose “Analyzer” .Click on “Upload Document” (Right Panel) .Select the document to upload(either the PDF or the DOCX file) .When prompted “Would you like to Auto parse this Document using Analyzer?”, choose a Starting Number (example 1.0) and click YES .Once uploading completes, list of the created entities shows. The uploaded documents are expected to be broken-down into separate paragraphs, with Names and relationships created based on the documents’ Titles and Numbering Schemes For large DOCX as well as PDF samples (example, a 600 KB docx file with 24 pages, or a 2000KB PDF file with 300 pages), the upload progress bar runs indefinitely, not completing even after 30 minutes. If user goes back to the Database view while the upload bar is still pending, it turns out that the document has in fact been uploaded, which indicates that the issue is with the Upload Progress bar’s design. Overall: With minimal use of the User Guide, the tool is fairly intuitive about how to import a document. The “Import” button was easy to find on the DB view. Once in the import portion of the tool, it’s easy to upload the document. It is unclear as to what class a user should select for their document. Other fields used to label the imported document seem straightforward. Tool seems to get hung when saving uploaded document. PDF: Imported the MEEPAS Project Report using a PDF and labeled it under the class “Statement”. Once uploaded, the analyzer did not import the entire document. It only imported three parts of the document and seems to parse those parts randomly. Innoslate does store the
selecting ‘Requirements Class Entity Report’ and ‘Requirement Class Selected Entity Report’ at step 4. into an error when trying to develop the stakeholder table. Doesn’t seem that anything gets saved in the database, so I am not sure what the result of adding a stakeholder is. Overall, I can’t add anything to the CONOPs framework using the Wizard without receiving an error. I can’t seem to find anything that I’ve added in the database view, so I can’t see how the tool is handling my input. RG-002 General Reports: 1. In Database View click ‘Reports’. 2.From the ‘Generate Report’ dialog select ‘General Report’ 3.From the ‘General Report’ list, select ‘CONOPS’ NOTE: If Concept of Operations has not been defined yet, Innoslate will invoke the CONOPS Data Entry Wizard. The report generation will continue after you finish the CONOPS data entry 4. Select Generate CONOPS from the dropdown 5. Click ‘Submit’ Must be able to generate, download, and view general reports Was able to generate, download, and view CONOPS report Was unable to generate a CONOPS report. It was not offered as an option in the version being used. RG-003 DODAF Reports: 1. In Database View click ‘Reports’. 2.From the ‘Generate Report’ dialog select ‘DoDAF Reports’ 3. Select ‘DoDAF 4. Click Submit Must be able to generate, download, and view DoDAF reports Received confirmation dialog saying the report is complete. But could not find the report under ‘Database’ view Attempted several times to create an OV-1 and OV-5 report based on existing entities, however nothing was generated.