ANN_284 ANN_278 ANN_14 ANN_280 ANN_285 ANN_279 ANN_6 ANN_124 ANN_283 ANN_281 ANN_282 ANN_277 ANN_276 ANN_275 The automated assistant is part of the system, but interacts with the requirements part of the system like a project user adding issues and notes during analysis. The automated assistant will be a stakeholder on all projects. Automated Assistant ANN_289 ANN_286 ANN_14 ANN_288 ANN_290 ANN_287 This is a placeholder for an interactive user Interactive User ANN_295 ANN_291 ANN_14 ANN_293 ANN_296 ANN_292 ANN_294 ANN_25 ANN_6 Project users use the system to create Requirements in projects. Project User ANN_302 ANN_297 ANN_14 ANN_299 ANN_303 ANN_298 ANN_301 ANN_131 ANN_300 System administrator users create other users and manage the system level user permissions. System Admin ANN_393 ANN_112 ANN_14 ANN_113 ANN_394 ANN_392 ANN_395 collect the underpants ANN_385 ANN_389 ANN_14 ANN_387 ANN_386 ANN_390 ANN_392 ANN_388 ANN_391 this is a test of the top level (in the project UI) test top level scenario SCN_18 Yuck Pee Pee Snow Cone Don't eat it Yellow Snow ANN_12 ANN_3 ANN_14 ANN_5 ANN_13 ANN_4 ANN_15 ANN_6 ANN_8 ANN_9 ANN_7 ANN_10 ANN_11 The system analyzes the requirements as they are added to a project and makes suggestions by adding issues to the elements. Automatted Assistance ANN_22 ANN_18 ANN_14 ANN_20 ANN_19 ANN_23 ANN_21 ANN_24 ANN_25 ANN_6 ANN_17 ANN_16 A team of technical and business stakeholders can use the system to create accurate, precise and unambiguous system requirements. Collaborative Elicitation of Requirements ANN_35 ANN_26 ANN_14 ANN_28 ANN_27 ANN_36 ANN_25 ANN_6 ANN_32 ANN_33 ANN_29 ANN_30 ANN_34 ANN_31 ANN_7 The system supports integrated discussion of the requirements such that stakeholders can identify issues with the project elements, state multiple solutions to each issue, and pros and cons of each solution. Discussion of Requirements ANN_45 ANN_38 ANN_14 ANN_40 ANN_39 ANN_46 ANN_6 ANN_41 ANN_43 ANN_42 ANN_7 ANN_44 ANN_37 The system is easy to use so that non-technical users can contribute to the requirements without the need for specialized skills or training. Easy to Use ANN_53 ANN_47 ANN_14 ANN_49 ANN_54 ANN_48 ANN_55 ANN_6 ANN_52 ANN_50 ANN_51 The system does not force a specific requirements elicitation process on the stakeholders. The system does not require the stakeholders to use all the features of the system. Flexible Process and Deliverables ANN_65 ANN_60 ANN_14 ANN_66 ANN_61 ANN_67 ANN_6 ANN_63 ANN_64 ANN_62 ANN_7 ANN_57 ANN_58 ANN_56 ANN_59 Using the system improves understanding of the requirements by all the stakeholders compared to non-integrated tools such as emails and spreadsheets. Improved Understanding ANN_78 ANN_68 ANN_14 ANN_70 ANN_69 ANN_79 ANN_81 ANN_80 ANN_6 ANN_75 ANN_73 ANN_74 ANN_72 ANN_76 ANN_71 ANN_51 ANN_77 The system notifies the stakeholders of changes to the project. The user can customize how the notifications occur: every time a change is made, or a periodic summary. Notification of Project Changes ANN_83 ANN_89 ANN_91 ANN_85 ANN_90 ANN_84 ANN_87 ANN_41 ANN_86 ANN_7 ANN_88 ANN_82 The requirements are defined in natural language such that non-technical users do not need specialized skills to understand the requirements. Requirements defined in Natural Language ANN_99 ANN_93 ANN_14 ANN_95 ANN_100 ANN_94 ANN_101 ANN_98 ANN_97 ANN_96 ANN_92 The system secures project content from unauthorized access by users not assigned to a project or non-users of the system. Secure data access ANN_103 ANN_108 ANN_14 ANN_110 ANN_104 ANN_109 ANN_105 ANN_111 ANN_107 ANN_106 ANN_102 The work done on the thesis is exclusively done by the student. Work is your own Requel <?xml version="1.0" encoding="UTF-8"?>  <xsl:stylesheet version="1.0" xmlns="http://www.w3.org/1999/xhtml" xmlns:rp="http://www.rreganjr.com/requel" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xi="http://www.w3.org/2001/XInclude" exclude-result-prefixes="xs xsi rp xsl xi"> <xsl:output method="xml" encoding="UTF-8" indent="yes" /> <xsl:template match="/rp:project"> <html> <head> <title> <xsl:value-of select="rp:name" /> </title> <xsl:call-template name="css"/> </head> <body> <div class="project"> <h1>Requirements for "<xsl:value-of select="rp:name" />"</h1> <h5>Client: <xsl:value-of select="rp:organization/@name" /></h5> <h5>Revision: <xsl:value-of select="@revision" /></h5> <h4>Table of Contents</h4> <div class="toc"> <ul> <xsl:if test="count(rp:stakeholders/rp:stakeholder) > 0"> <li><a href="#stakeholders">Stakeholders</a> <ol> <xsl:apply-templates select="rp:stakeholders/rp:stakeholder" mode="summary"/> </ol> </li> </xsl:if> <xsl:if test="count(rp:teams/rp:team) > 0"> <li><a href="#teams">Teams</a> <ol> <xsl:apply-templates select="rp:teams/rp:team" mode="summary"/> </ol> </li> </xsl:if> <xsl:if test="count(rp:actors/rp:actor) > 0"> <li><a href="#actors">Actors</a> <ol> <xsl:apply-templates select="rp:actors/rp:actor" mode="summary"/> </ol> </li> </xsl:if> <xsl:if test="count(rp:goals/rp:goal) > 0"> <li><a href="#goals">Goals</a> <ol> <xsl:apply-templates select="rp:goals/rp:goal" mode="summary"/> </ol> </li> </xsl:if> <xsl:if test="count(rp:stories/rp:story) > 0"> <li><a href="#stories">Stories</a> <ol> <xsl:apply-templates select="rp:stories/rp:story" mode="summary"/> </ol> </li> </xsl:if> <xsl:if test="count(rp:usecases/rp:usecase) > 0"> <li><a href="#usecases">Use Cases</a> <ol> <xsl:apply-templates select="rp:usecases/rp:usecase" mode="summary"/> </ol> </li> </xsl:if> <xsl:if test="count(rp:scenarios/rp:scenario) > 0"> <li><a href="#scenarios">Scenarios</a> <ol> <xsl:apply-templates select="rp:scenarios/rp:scenario" mode="summary"/> </ol> </li> </xsl:if> <xsl:if test="count(rp:glossary/rp:term) > 0"> <li><a href="#glossary">Glossary</a> <ol> <xsl:apply-templates select="rp:glossary/rp:term" mode="summary"/> </ol> </li> </xsl:if> </ul> </div> <div class="body"> <xsl:apply-templates select="rp:stakeholders" /> <xsl:apply-templates select="rp:teams" /> <xsl:apply-templates select="rp:actors" /> <xsl:apply-templates select="rp:goals" /> <xsl:apply-templates select="rp:stories" /> <xsl:apply-templates select="rp:usecases" /> <xsl:apply-templates select="rp:scenarios" /> <xsl:apply-templates select="rp:glossary" /> </div> </div> </body> </html> </xsl:template> <xsl:template match="rp:stakeholder[count(rp:user/rp:username) = 0]|rp:team|rp:actor|rp:goal|rp:story|rp:usecase|rp:scenario|rp:term" mode="summary"> <li> <a href="#{generate-id(.)}"> <xsl:value-of select="rp:name" /> </a> </li> </xsl:template> <xsl:template match="rp:stakeholder[count(rp:user/rp:username) > 0]" mode="summary"> <li> <a href="#{generate-id(.)}"> <xsl:value-of select="rp:user/rp:name" /> [<xsl:value-of select="rp:user/rp:username" />] </a> </li> </xsl:template>  <xsl:template match="rp:stakeholders"> <xsl:if test="count(rp:stakeholder) > 0"> <div class="stakeholders"> <a name="stakeholders"></a> <h2>Stakeholders</h2> <table class="stakeholders"> <thead> <tr> <th>User?</th> <th>Name</th> <th>Organization</th> <th>Email</th> <th>Phone</th> </tr> </thead> <tbody> <xsl:apply-templates select="rp:stakeholder" /> </tbody> </table> </div> </xsl:if> </xsl:template> <xsl:template match="rp:stakeholder[count(rp:user/rp:username) > 0]"> <tr> <td> Yes </td> <td> <a name="{generate-id(.)}"> <xsl:value-of select="rp:user/rp:name" /> (<xsl:value-of select="rp:user/rp:username" />) </a> </td> <td> <xsl:apply-templates select="rp:user/rp:organization/@name" /> </td> <td> <xsl:apply-templates select="rp:user/rp:emailAddress" /> </td> <td> <xsl:apply-templates select="rp:user/rp:phoneNumber" /> </td> </tr> <xsl:if test="count(rp:goals/*) > 0"> <tr> <td></td> <td colspan="4"> <xsl:apply-templates select="rp:goals" /> </td> </tr> </xsl:if> <xsl:if test="count(rp:annotations/*) > 0"> <tr> <td></td> <td colspan="4"> <xsl:apply-templates select="rp:annotations" /> </td> </tr> </xsl:if> </xsl:template> <xsl:template match="rp:stakeholder"> <tr> <td> No </td> <td> <a name="{generate-id(.)}"> <xsl:value-of select="rp:name" /> </a> </td> <td> <xsl:apply-templates select="rp:organization/@name" /> </td> <td> </td> <td> </td> </tr> <xsl:if test="count(rp:goals/*) > 0"> <tr> <td></td> <td colspan="4"> <xsl:apply-templates select="rp:goals" /> </td> </tr> </xsl:if> <xsl:if test="count(rp:annotations/*) > 0"> <tr> <td></td> <td colspan="4"> <xsl:apply-templates select="rp:annotations" /> </td> </tr> </xsl:if> </xsl:template> <xsl:template match="rp:stakeholderRef"> <xsl:variable name="ref-id" select="." /> <li class="stakeholder"> <span class="body"> <a href="#{generate-id(//rp:stakeholder[@id = $ref-id])}"> <xsl:apply-templates select="//rp:stakeholder[@id = $ref-id]/rp:name" /> </a> </span> </li> </xsl:template>  <xsl:template match="rp:teams"> <xsl:if test="count(rp:team) > 0"> <a name="teams"></a> <h2>Teams</h2> <div class="body"> <xsl:apply-templates select="*"/> </div> </xsl:if> </xsl:template> <xsl:template match="rp:team"> <h2><xsl:value-of select="rp:name"/></h2> <div class="body"> <xsl:apply-templates select="rp:members"/> <xsl:apply-templates select="rp:annotations" /> </div> </xsl:template>  <xsl:template match="rp:project/rp:actors"> <xsl:if test="count(rp:actor) > 0"> <a name="actors"></a> <h2>Actors</h2> <div class="body"> <xsl:apply-templates select="*" /> </div> </xsl:if> </xsl:template> <xsl:template match="rp:actors"> <xsl:if test="count(*) > 0"> <h4>Actors</h4> <div class="body"> <xsl:apply-templates select="*" /> </div> </xsl:if> </xsl:template> <xsl:template match="rp:actor"> <div class="actor"> <h4> <a name="{generate-id(.)}"> <xsl:value-of select="rp:name" /> </a> </h4> <div class="body"> <xsl:apply-templates select="rp:text" /> <xsl:apply-templates select="rp:goals" /> <xsl:apply-templates select="rp:annotations" /> </div> </div> </xsl:template> <xsl:template match="rp:actorRef"> <xsl:variable name="ref-id" select="." /> <li class="actor"> <span class="body"> <a href="#{generate-id(//rp:actor[@id = $ref-id])}"> <xsl:apply-templates select="//rp:actor[@id = $ref-id]/rp:name" /> </a> </span> </li> </xsl:template> <xsl:template match="rp:primaryActorRef"> <xsl:variable name="ref-id" select="." /> <a href="#{generate-id(//rp:actor[@id = $ref-id])}"> <xsl:apply-templates select="//rp:actor[@id = $ref-id]/rp:name" /> </a> </xsl:template>  <xsl:template match="rp:project/rp:goals"> <xsl:if test="count(rp:goal) > 0"> <div class="goals"> <a name="goals"></a> <h2>Goals</h2> <ul class="goals"> <xsl:apply-templates select="*" /> </ul> </div> </xsl:if> </xsl:template> <xsl:template match="rp:goals"> <xsl:if test="count(*) > 0"> <h4>Goals</h4> <ul class="goals"> <xsl:apply-templates select="*" /> </ul> </xsl:if> </xsl:template> <xsl:template match="rp:goal"> <li class="goal"> <div class="goal"> <h4> <a name="{generate-id(.)}"> <xsl:value-of select="rp:name" /> </a> </h4> <div class="body"> <div> <xsl:value-of select="rp:text" /> </div> <xsl:apply-templates select="rp:goalRelations" /> <xsl:apply-templates select="rp:annotations" /> </div> </div> </li> </xsl:template> <xsl:template match="rp:goalRef"> <xsl:variable name="ref-id" select="." /> <li class="goal"> <span class="body"> <a href="#{generate-id(//rp:goal[@id = $ref-id])}"> <xsl:apply-templates select="//rp:goal[@id = $ref-id]/rp:name" /> </a> </span> </li> </xsl:template> <xsl:template match="rp:goalRelations"> <xsl:if test="count(rp:goalRelation) > 0"> <h4>Goal Relations</h4> <ul> <xsl:apply-templates select="rp:goalRelation" /> </ul> </xsl:if> </xsl:template> <xsl:template match="rp:goalRelation"> <xsl:variable name="ref-id" select="@toGoal" /> <li class="goal"> <div> <xsl:value-of select="@relationType" /> - <a href="#{generate-id(//rp:goal[@id = $ref-id])}"> <xsl:apply-templates select="//rp:goal[@id = $ref-id]/rp:name" /> </a> </div> <xsl:apply-templates select="rp:annotations" /> </li> </xsl:template>  <xsl:template match="rp:project/rp:stories"> <xsl:if test="count(rp:story) > 0"> <a name="stories"></a> <h2>Stories</h2> <div class="body"> <xsl:apply-templates select="*" /> </div> </xsl:if> </xsl:template> <xsl:template match="rp:stories"> <xsl:if test="count(*) > 0"> <h4>Stories</h4> <xsl:choose> <xsl:when test="count(rp:story) > 0"> <div class="body"> <xsl:apply-templates select="rp:story" /> </div> </xsl:when> <xsl:when test="count(rp:storyRef) > 0"> <div class="body"> <ul> <xsl:for-each select="rp:storyRef"> <li><xsl:apply-templates select="." /></li> </xsl:for-each> </ul> </div> </xsl:when> </xsl:choose> </xsl:if> </xsl:template> <xsl:template match="rp:story"> <div class="story"> <h4> <a name="{generate-id(.)}"> <xsl:value-of select="@storyType" /> Story - <xsl:value-of select="rp:name" /> </a> </h4> <div class="body"> <xsl:apply-templates select="rp:text" /> </div> <xsl:apply-templates select="rp:actors" /> <xsl:apply-templates select="rp:goals" /> <xsl:apply-templates select="rp:annotations" /> </div> </xsl:template> <xsl:template match="rp:storyRef"> <xsl:variable name="ref-id" select="." /> <a href="#{generate-id(//rp:story[@id = $ref-id])}"> <xsl:apply-templates select="//rp:story[@id = $ref-id]/rp:name" /> </a> </xsl:template>  <xsl:template match="rp:project/rp:usecases"> <xsl:if test="count(rp:usecase) > 0"> <a name="usecases"></a> <h2>Use Cases</h2> <div class="body"> <xsl:apply-templates select="*" /> </div> </xsl:if> </xsl:template> <xsl:template match="rp:usecases"> <xsl:if test="count(*) > 0"> <h4>Use Cases</h4> <div class="body"> <xsl:apply-templates select="rp:usecase" /> </div> </xsl:if> </xsl:template> <xsl:template match="rp:usecaseRef"> <xsl:variable name="ref-id" select="." /> <a href="#{generate-id(//rp:usecase[@id = $ref-id])}"> <xsl:apply-templates select="//rp:usecase[@id = $ref-id]/rp:name" /> </a> </xsl:template> <xsl:template match="rp:usecase"> <div class="usecase"> <h4> <a name="{generate-id(.)}"> <xsl:value-of select="rp:name" /> </a> </h4> <div class="body"> <xsl:if test="string-length(rp:text) > 0"> <h4>Description</h4> <xsl:apply-templates select="rp:text" /> </xsl:if> <xsl:apply-templates select="rp:goals" /> <xsl:apply-templates select="rp:stories" /> <h4>Primary Actor: <xsl:apply-templates select="rp:primaryActorRef" /></h4> <xsl:apply-templates select="rp:actors" /> <h4>Scenario</h4> <xsl:variable name="scenarioRef" select="string(rp:scenarioRef)" /> <xsl:apply-templates select="//rp:scenario[@id = $scenarioRef]" mode="usecase" /> <xsl:apply-templates select="rp:annotations" /> </div> </div> </xsl:template>  <xsl:template match="rp:project/rp:scenarios"> <xsl:variable name="rootScenariosExist"> <xsl:for-each select="rp:scenario"> <xsl:variable name="scenarioId" select="@id"/> <xsl:choose> <xsl:when test="count(//rp:scenarioRef[string(text()) = $scenarioId]) = 0 and count(//rp:stepRef[string(text()) = $scenarioId]) = 0"><xsl:value-of select="concat(./@id,' ')"/></xsl:when> </xsl:choose> </xsl:for-each> </xsl:variable> <xsl:comment> <xsl:value-of select="$rootScenariosExist"/> </xsl:comment> <xsl:if test="string-length($rootScenariosExist) > 0"> <a name="scenarios"></a> <h2>Scenarios (not used else where)</h2> <div class="body"> <xsl:for-each select="rp:scenario"> <xsl:variable name="scenarioId" select="@id"/> <xsl:if test="count(//rp:scenarioRef[string(text()) = $scenarioId]) = 0 and count(//rp:stepRef[string(text()) = $scenarioId]) = 0"> <xsl:apply-templates select="." /> </xsl:if> </xsl:for-each> </div> </xsl:if> </xsl:template> <xsl:template match="rp:scenarios"> <xsl:if test="count(*) > 0"> <h4>Scenarios</h4> <div class="body"> <xsl:apply-templates select="rp:scenario" /> </div> </xsl:if> </xsl:template> <xsl:template match="rp:scenario" mode="usecase"> <div class="scenario"> <xsl:apply-templates select="rp:steps" /> </div> </xsl:template> <xsl:template match="rp:scenario"> <div class="scenario"> <h4> <a name="{generate-id(.)}"> <xsl:value-of select="@scenarioType" /> - <xsl:value-of select="rp:name" /> </a> </h4> <xsl:if test="string-length(rp:text) > 0"> <h4>Description</h4> <xsl:apply-templates select="rp:text" /> </xsl:if> <xsl:apply-templates select="rp:steps" /> <xsl:apply-templates select="rp:annotations" /> </div> </xsl:template> <xsl:template match="rp:steps"> <ol class="scenario"> <xsl:for-each select="rp:stepRef"> <li class="step"><xsl:apply-templates select="."/></li> </xsl:for-each> </ol> </xsl:template> <xsl:template match="rp:stepRef"> <xsl:variable name="stepRefId" select="text()" /> <xsl:apply-templates select="//rp:scenario[@id = $stepRefId]|//rp:step[@id = $stepRefId]" mode="steps"/> </xsl:template>  <xsl:template match="rp:scenario" mode="steps"> <xsl:value-of select="@scenarioType" /> - <xsl:value-of select="rp:name" /> <xsl:apply-templates select="rp:steps" /> </xsl:template> <xsl:template match="rp:step" mode="steps"> <xsl:value-of select="@scenarioType" /> - <xsl:value-of select="rp:name" /> </xsl:template>  <xsl:template match="rp:project/rp:glossary"> <xsl:if test="count(rp:term) > 0"> <a name="glossary"></a> <h2>Glossary</h2> <div class="body"> <table class="stakeholders"> <thead> <tr> <th>Term</th> <th>Definition</th> </tr> </thead> <tbody> <xsl:apply-templates select="rp:term" /> </tbody> </table> </div> </xsl:if> </xsl:template> <xsl:template match="rp:term"> <tr> <td><xsl:value-of select="rp:name" /></td> <td><xsl:value-of select="rp:text" /></td> </tr> </xsl:template>  <xsl:template match="rp:annotations">  </xsl:template> <xsl:template match="rp:note"> <li class="note"> <xsl:apply-templates select="rp:text" /> </li> </xsl:template> <xsl:template match="rp:issue|rp:lexicalIssue"> <li class="issue"> <xsl:apply-templates select="rp:text" /> <xsl:apply-templates select="rp:positions" /> </li> </xsl:template> <xsl:template match="rp:positions"> <xsl:if test="count(*) > 0"> <h4>Solutions</h4> <div class="body"> <ul> <xsl:apply-templates select="*" /> </ul> </div> </xsl:if> </xsl:template> <xsl:template match="rp:position|rp:addWordToDictionaryPosition|rp:changeSpellingPosition|rp:addGlossaryTermPosition|rp:addActorPosition"> <li class="position"> <xsl:apply-templates select="rp:text" /> <xsl:apply-templates select="rp:arguments" /> </li> </xsl:template> <xsl:template match="rp:arguments"> <xsl:if test="count(*) > 0"> <h4>Arguments</h4> <div class="body"> <h5>Strongly For</h5> <xsl:apply-templates select="rp:argument[@supportLevel = 'StronglyFor']" /> <h5>For</h5> <xsl:apply-templates select="rp:argument[@supportLevel = 'For']" /> <h5>Neutral</h5> <xsl:apply-templates select="rp:argument[@supportLevel = 'Neutral']" /> <h5>Against</h5> <xsl:apply-templates select="rp:argument[@supportLevel = 'Against']" /> <h5>Strongly Against</h5> <xsl:apply-templates select="rp:argument[@supportLevel = 'StronglyAgainst']" /> </div> </xsl:if> </xsl:template> <xsl:template match="rp:argument"> <div class="argument"> <xsl:apply-templates select="rp:text" /> </div> </xsl:template>  <xsl:template name="css"> <style type="text/css"> html { height: 100%; } body { height: 100%; font-family: Arial; font-size: 10pt; margin-top: .5in; margin-left: .5in; margin-right: .5in; margin-bottom: .5in; } h1 { text-align: center; font-family: Arial; font-size: 14pt; } h2 { text-align: left; font-family: Arial; font-size: 12pt; } h3, h4, h5, h6 { text-align: left; font-family: Arial; font-size: 11pt; } table { border: solid 1pt black; border-collapse: collapse; empty-cells: show; } td { padding: 5pt; border: solid 1pt black; border-collapse: collapse; font-family: Arial; font-size: 10pt; vertical-align: top; text-align: left; font-weight: normal; } div .project .body { margin: 0; } div .body { margin-top: .25in; margin-left: .25in; margin-right: .25in; margin-bottom: .25in; } .stakeholders table { margin-top: .25in; margin-left: .25in; margin-right: .25in; margin-bottom: .25in; } th { padding: 4pt; border: solid 1pt black; border-collapse: collapse; font-family: Arial; font-size: 10pt; vertical-align: bottom; text-align: left; font-weight: bold; } .issue { } .note { } .p { padding-bottom: 10pt; } </style> </xsl:template> </xsl:stylesheet> HTML Specification

assistant f549cd73f694aa6f5541b4ae30894eea Analysis Assistant rreganjr@users.sourceforge.net false

project 46f86faa6bbf9ac94a7e459509a20ed0 Builtin Project User rreganjr@users.sourceforge.net true

GOL_10 Harvard University

admin 21232f297a57a5a743894a0e4a801fc3 System Administrator rreganjr@users.sourceforge.net true

ANN_114 ANN_112 ANN_14 ANN_113 ANN_115 ANN_116 ANN_25 ANN_1 Buddy the controller of Bailey Pet Supply has a problem; it takes over a month to close the books each quarter. Due to new disclosure requirements, Alex the CFO needs to submit quarterly results to the board of directors one week after the end of the quarter. Buddy tells Theresa, the accounting manager, that they need to close the books each quarter in less than a week. Theresa tells Buddy that the problem stems from the order processing system not being integrated with the accounting package and at the end of each month data must be entered into both systems to reconcile them manually. Buddy decides that the systems must be integrated before the end of the next quarter so that the one week turn-around for reporting can be met. Buddy meets with Dave the IT manager to discuss the work. Dave assigns Tim, one of the IT project managers, to work with Buddy to determine the requirements and estimate the work. Tim meets with Buddy and they generate a list of high level requirements. Tim gives the requirements and a rough estimate of two months to Dave, who in turn gives them to Ron, an MIS programmer, to design and develop. Ron reviews the requirements and goes back to Dave and tells him there are a lot of vague areas and he needs to get clarification from Tim and Buddy. Ron and Tim have a meeting to discuss the requirements. Ron asks Tim "What is a purchase order?" Tim response "It’s a record in the purchase system that Linda enters based on information from a sales person." Ron asks "What information is in the purchase order?" Tim doesn’t know and tells Ron he will ask Buddy and get back to him. Tim sends an email to Buddy and calls it a day. Buddy replies to Tim’s email that he should talk to Linda to get the details of a purchase order. Tim has a meeting with Linda and gets the details on the data for a purchase order. Tim sends Ron an email with the information. Ron replies to Tim’s email "Is there a database with data that I can look at for a sample?" Poor Communication in Requirements ANN_137 ANN_119 ANN_139 ANN_121 ANN_138 ANN_120 ANN_134 ANN_132 ANN_140 ANN_127 ANN_125 ANN_122 ANN_124 ANN_130 ANN_129 ANN_131 ANN_128 ANN_123 ANN_126 ANN_133 ANN_135 ANN_136 ANN_117 ANN_118 Rich logs in to the system and it displays a list of his active projects and the option to create a new project. Rich chooses to create a new project and the system displays the new project interface. Rich enters "Mobile Media Portal" for the project name and enters a short description. Rich looks over the list of existing customers and doesn't see what he's looking for and enters "Virile Mobile". The system creates the new project and adds Rich as a stakeholder with permission to edit all project entities and grant permission to other users to edit entities. The system closes the new project interface and adds the new project in the project navigation interface. Rich creates a new project ANN_157 ANN_145 ANN_159 ANN_147 ANN_158 ANN_146 ANN_140 ANN_6 ANN_127 ANN_151 ANN_149 ANN_155 ANN_150 ANN_154 ANN_148 ANN_152 ANN_153 ANN_156 ANN_141 ANN_143 ANN_142 ANN_144 Rich opens a web browser to the Requel system address. The system doesn’t detect an existing user session and presents the login screen. Rich enters his username and password. The system verifies the username and password combination is correct. The system logs that Rich has successfully logged into the system and shows him a list of his open projects and an overview of recent project changes. Rich logs in to the system ANN_215 ANN_201 ANN_203 ANN_217 ANN_216 ANN_202 ANN_218 ANN_6 ANN_75 ANN_210 ANN_204 ANN_207 ANN_212 ANN_209 ANN_208 ANN_151 ANN_149 ANN_148 ANN_213 ANN_152 ANN_214 ANN_176 ANN_200 ANN_177 Ron opens a web browser to the Requel system address. The system doesn’t detect an existing user session and presents the login screen. Ron doesn’t have a username and password yet so he chooses the help option. The system displays a message that the system requires a distinct username and password and that the user should contact Dave at extension 500 or via email to dave@requel if they need a new account or are having a problem connecting. The system also displays a help message describing what to do if the user forgot their account information. Ron sends Dave an email to create him a new account. Ron fails to log in to the system ANN_245 ANN_234 ANN_247 ANN_236 ANN_246 ANN_235 ANN_239 ANN_238 ANN_248 ANN_125 ANN_124 ANN_130 ANN_131 ANN_240 ANN_242 ANN_237 ANN_123 ANN_126 ANN_133 ANN_243 ANN_241 ANN_244 When Theresa logs in, the system determines that she has permission to create projects and displays the "Create Project" option in the system interface. Theresa chooses to create a new project and the system displays the new project interface. Theresa enters "Purchase Order System" for the project name, leaves the description blank, and leaves "Bailey Pet Supply", her default automatically supplied, as the customer. The system creates the new project and adds Theresa as a stakeholder with permission to edit all project entities and grant permission to other users to edit entities. The system closes the new project interface and displays the project navigation interface to add and edit the project's entities. Theresa creates a new project ANN_252 ANN_272 ANN_254 ANN_274 ANN_253 ANN_273 ANN_265 ANN_6 ANN_248 ANN_257 ANN_263 ANN_259 ANN_260 ANN_151 ANN_267 ANN_258 ANN_266 ANN_261 ANN_256 ANN_255 ANN_270 ANN_152 ANN_262 ANN_269 ANN_268 ANN_264 ANN_271 ANN_249 ANN_250 ANN_251 Theresa connects to the Requel system via a web browser from a link in an email message sent by the Requel system when Dave the system administrator created an account for her. The system displays the new user setup interface, prompting Theresa to confirm the personal information Dave entered about her and filling in any missing information, such as name, phone number, email address, a username and a password. When Theresa completes entering the information the system forwards her to the login screen. Theresa enters her username and password, and the system verifies it as correct. The system logs that Theresa has successfully logged into the system, and because Theresa is a novice user, the system displays the novice user interface to help her get started. Theresa logs in to the system A collaborative system for the elicitation and analysis of requirements facilitated by automated assistants. ANN_304 ANN_112 ANN_14 ANN_306 ANN_113 ANN_305 ANN_307 ANN_125 A user creates a new project ACT_4 SCN_19 STRY_2 STRY_5 ANN_343 ANN_112 ANN_14 ANN_345 ANN_113 ANN_344 ANN_2 ANN_307 ANN_6 GOL_9 GOL_10 A user logs in to the system ACT_2 SCN_19 STRY_3 STRY_4 STRY_6 hello Cleveland POS_1 hi there Phrase Structure: (ROOT (S (NP (DT The) (NN system#1)) (VP (VBZ analyzes#1) (NP (DT the) (NNS requirements#1)) (SBAR (IN as) (S (NP (PRP they)) (VP (VP (VBP are) (VP (VBN added#1) (PP (IN to) (NP (DT a) (NN project#1))))) (CC and) (VP (VBZ makes#1) (NP (NNS suggestions#1)) (PP (IN by) (S (VP (VBG adding#1) (NP (NNS issues#1)) (PP (IN to) (NP (DT the) (NNS elements#1))))))))))) (. .))) Syntax Dependencies: [dep] The-0 is the determiner of system-1 [dep] system-1 is the nominal subject of analyzes-2 [dep] the-3 is the determiner of requirements-4 [dep] requirements-4 is the object of analyzes-2 [dep] as-5 is the marker of added-8 [dep] they-6 is the nominal subject of makes-13 [dep] added-8 is the adverbial clause modifier of analyzes-2 [dep] to-9 is the case marker of project-11 [dep] a-10 is the determiner of project-11 [dep] and-12 is the coordination of makes-13 [dep] makes-13 is the adverbial clause modifier of analyzes-2 [dep] makes-13 is the conjunct of added-8 [dep] suggestions-14 is the object of makes-13 [dep] by-15 is the marker of adding-16 [dep] adding-16 is the adverbial clause modifier of makes-13 [dep] issues-17 is the object of adding-16 [dep] to-18 is the case marker of elements-20 [dep] the-19 is the determiner of elements-20 Semantic Roles: makes[AGENT]The system The phrase "The system" is a potential glossary term, actor, or domain object/property POS_2 POS_4 POS_3 The phrase "the requirements" is a potential glossary term, actor, or domain object/property POS_2 POS_5 POS_6 The phrase "a project" is a potential glossary term, actor, or domain object/property POS_2 POS_7 POS_8 The phrase "the elements" is a potential glossary term, actor, or domain object/property POS_2 POS_9 POS_10 The text "The system analyzes the requirements as they are added to a project and makes suggestions by adding issues to the elements." in the Text is complex and may be hard to understand. POS_11 POS_12 The word "Automatted" in the Name is not recognized and may be spelled incorrectly. POS_12 POS_13 POS_14 POS_16 POS_15 Phrase Structure: (ROOT (NP (NNP Automatted#1) (NNP Assistance#1))) Syntax Dependencies: [dep] Automatted-0 is the compound modifier of Assistance-1 Semantic Roles: The phrase "Automatted Assistance" is a potential glossary term, actor, or domain object/property POS_2 POS_18 POS_17 The word "stakeholders" in the Text is not recognized and may be spelled incorrectly. POS_12 POS_21 POS_19 POS_22 POS_20 The word "create" in the Text is vague and may lead to ambiguity. POS_12 POS_23 POS_27 POS_25 POS_24 POS_26 Phrase Structure: (ROOT (S (NP (NP (DT A) (NN team#1)) (PP (IN of) (NP (UCP (JJ technical#1) (CC and) (NN business#1)) (NNS stakeholders#1)))) (VP (MD can) (VP (VB use#1) (NP (DT the) (NN system#1)) (S (VP (TO to) (VP (VB create#1) (NP (ADJP (JJ accurate#1) (, ,) (JJ precise#1) (CC and) (JJ unambiguous#1)) (NN system#1) (NNS requirements#1))))))) (. .))) Syntax Dependencies: [dep] A-0 is the determiner of team-1 [dep] team-1 is the nominal subject of use-8 [dep] of-2 is the case marker of stakeholders-6 [dep] technical-3 is the adjectival modifier of stakeholders-6 [dep] and-4 is the coordination of business-5 [dep] business-5 is the conjunct of technical-3 [dep] business-5 is the adjectival modifier of stakeholders-6 [dep] stakeholders-6 is the nominal modifier of team-1 [dep] can-7 is the auxiliary of use-8 [dep] the-9 is the determiner of system-10 [dep] system-10 is the object of use-8 [dep] to-11 is the marker of create-12 [dep] create-12 is the adverbial clause modifier of use-8 [dep] accurate-13 is the adjectival modifier of requirements-19 [dep] precise-15 is the conjunct of accurate-13 [dep] precise-15 is the adjectival modifier of requirements-19 [dep] and-16 is the coordination of unambiguous-17 [dep] unambiguous-17 is the conjunct of accurate-13 [dep] unambiguous-17 is the adjectival modifier of requirements-19 [dep] system-18 is the compound modifier of requirements-19 [dep] requirements-19 is the object of create-12 Semantic Roles: use[AGENT]A team The phrase "A team" is a potential glossary term, actor, or domain object/property POS_2 POS_29 POS_28 Phrase Structure: (ROOT (NP (NP (NNP Collaborative#1) (NNP Elicitation#1)) (PP (IN of) (NP (NNP Requirements#1))))) Syntax Dependencies: [dep] Collaborative-0 is the compound modifier of Elicitation-1 [dep] of-2 is the case marker of Requirements-3 [dep] Requirements-3 is the nominal modifier of Elicitation-1 The phrase "Collaborative Elicitation" is a potential glossary term, actor, or domain object/property POS_2 POS_30 POS_31 The phrase "Requirements" is a potential glossary term, actor, or domain object/property POS_2 POS_33 POS_32 Phrase Structure: (ROOT (S (NP (DT The) (NN system#1)) (VP (VBZ supports#1) (NP (NP (JJ integrated#1) (NN discussion#1)) (PP (IN of) (NP (DT the) (NNS requirements#1)))) (SBAR (JJ such#1) (IN that) (S (NP (NNS stakeholders#1)) (VP (MD can) (VP (VB identify#1) (NP (NP (NP (NNS issues#1)) (PP (IN with) (NP (DT the) (NN project#1) (NNS elements#1)))) (, ,) (NP (NP (NN state#1) (JJ multiple#1) (NNS solutions#1)) (PP (IN to) (NP (DT each) (NN issue#1)))) (, ,) (CC and) (NP (NP (NNS pros#1) (CC and) (NNS cons#1)) (PP (IN of) (NP (DT each) (NN solution#1)))))))))) (. .))) Syntax Dependencies: [dep] The-0 is the determiner of system-1 [dep] system-1 is the nominal subject of supports-2 [dep] integrated-3 is the adjectival modifier of discussion-4 [dep] discussion-4 is the object of supports-2 [dep] of-5 is the case marker of requirements-7 [dep] the-6 is the determiner of requirements-7 [dep] requirements-7 is the nominal modifier of discussion-4 [dep] such-8 is the dependent of identify-12 [dep] that-9 is the marker of identify-12 [dep] stakeholders-10 is the nominal subject of identify-12 [dep] can-11 is the auxiliary of identify-12 [dep] identify-12 is the dependent of supports-2 [dep] issues-13 is the object of identify-12 [dep] with-14 is the case marker of elements-17 [dep] the-15 is the determiner of elements-17 [dep] project-16 is the compound modifier of elements-17 [dep] elements-17 is the nominal modifier of issues-13 [dep] state-19 is the compound modifier of solutions-21 [dep] multiple-20 is the adjectival modifier of solutions-21 [dep] solutions-21 is the object of identify-12 [dep] solutions-21 is the conjunct of issues-13 [dep] to-22 is the case marker of issue-24 [dep] each-23 is the determiner of issue-24 [dep] issue-24 is the nominal modifier of solutions-21 [dep] and-26 is the coordination of pros-27 [dep] pros-27 is the object of identify-12 [dep] pros-27 is the conjunct of issues-13 [dep] and-28 is the coordination of cons-29 [dep] cons-29 is the conjunct of issues-13 [dep] cons-29 is the conjunct of pros-27 [dep] of-30 is the case marker of solution-32 [dep] each-31 is the determiner of solution-32 [dep] solution-32 is the nominal modifier of pros-27 Semantic Roles: identify[AGENT]The system The phrase "integrated discussion" is a potential glossary term, actor, or domain object/property POS_34 POS_2 POS_35 The phrase "pros and cons" is a potential glossary term, actor, or domain object/property POS_36 POS_2 POS_37 The phrase "the project elements" is a potential glossary term, actor, or domain object/property POS_38 POS_2 POS_39 The phrase "each issue" is a potential glossary term, actor, or domain object/property POS_2 POS_41 POS_40 The phrase "each solution" is a potential glossary term, actor, or domain object/property POS_43 POS_2 POS_42 The phrase "state multiple solutions" is a potential glossary term, actor, or domain object/property POS_2 POS_45 POS_44 Phrase Structure: (ROOT (NP (NP (NN Discussion#1)) (PP (IN of) (NP (NNP Requirements#1))))) Syntax Dependencies: [dep] of-1 is the case marker of Requirements-2 [dep] Requirements-2 is the nominal modifier of Discussion-0 The word "non-technical" in the Text is not recognized and may be spelled incorrectly. POS_12 POS_49 POS_46 POS_47 POS_48 Phrase Structure: (ROOT (S (NP (DT The) (NN system#1)) (VP (VBZ is) (ADJP (JJ easy#1) (S (VP (TO to) (VP (VB use#1) (ADVP (RB so#1)) (SBAR (IN that) (S (NP (JJ non-technical) (NNS users#1)) (VP (MD can) (VP (VB contribute#1) (PP (IN to) (NP (DT the) (NNS requirements#1))) (PP (IN without) (NP (NP (DT the) (NN need#1)) (PP (IN for) (NP (JJ specialized#1) (NNS skills#1) (CC or) (NN training#1)))))))))))))) (. .))) Syntax Dependencies: [dep] The-0 is the determiner of system-1 [dep] system-1 is the nominal subject of easy-3 [dep] system-1 is the controlling nominal subject of use-5 [dep] is-2 is the copula of easy-3 [dep] to-4 is the marker of use-5 [dep] use-5 is the xclausal complement of easy-3 [dep] so-6 is the adverbial modifier of use-5 [dep] that-7 is the marker of contribute-11 [dep] non-technical-8 is the adjectival modifier of users-9 [dep] users-9 is the nominal subject of contribute-11 [dep] can-10 is the auxiliary of contribute-11 [dep] contribute-11 is the clausal complement of use-5 [dep] to-12 is the case marker of requirements-14 [dep] the-13 is the determiner of requirements-14 [dep] without-15 is the case marker of need-17 [dep] the-16 is the determiner of need-17 [dep] for-18 is the case marker of skills-20 [dep] specialized-19 is the adjectival modifier of skills-20 [dep] skills-20 is the nominal modifier of need-17 [dep] or-21 is the coordination of training-22 [dep] training-22 is the nominal modifier of need-17 [dep] training-22 is the conjunct of skills-20 Semantic Roles: contribute[AGENT]The system The phrase "non-technical users" is a potential glossary term, actor, or domain object/property POS_50 POS_2 POS_51 The phrase "the need" is a potential glossary term, actor, or domain object/property POS_53 POS_2 POS_52 The phrase "specialized skills or training" is a potential glossary term, actor, or domain object/property POS_2 POS_55 POS_54 The text "The system is easy to use so that non-technical users can contribute to the requirements without the need for specialized skills or training." in the Text is complex and may be hard to understand. POS_12 POS_56 Phrase Structure: (ROOT (FRAG (ADJP (JJ Easy#1) (S (VP (TO to) (VP (VB Use#1))))))) Syntax Dependencies: [dep] to-1 is the marker of Use-2 [dep] Use-2 is the xclausal complement of Easy-0 Phrase Structure: (ROOT (S (S (NP (DT The) (NN system#1)) (VP (VBZ does#1) (RB not#1) (VP (VB force#1) (NP (DT a) (JJ specific#1) (NNS requirements#1) (NN elicitation#1) (NN process#1)) (PP (IN on) (NP (DT the) (NNS stakeholders#1)))))) (. .) (S (NP (DT The) (NN system#1)) (VP (VBZ does#1) (RB not#1) (VP (VB require#1) (NP (DT the) (NNS stakeholders#1)) (S (VP (TO to) (VP (VB use#1) (NP (NP (PDT all) (DT the) (NNS features#1)) (PP (IN of) (NP (DT the) (NN system#1)))))))))) (. .))) Syntax Dependencies: [dep] The-0 is the determiner of system-1 [dep] system-1 is the nominal subject of force-4 [dep] does-2 is the auxiliary of force-4 [dep] not-3 is the adverbial modifier of force-4 [dep] a-5 is the determiner of process-9 [dep] specific-6 is the adjectival modifier of process-9 [dep] requirements-7 is the compound modifier of process-9 [dep] elicitation-8 is the compound modifier of process-9 [dep] process-9 is the object of force-4 [dep] on-10 is the case marker of stakeholders-12 [dep] the-11 is the determiner of stakeholders-12 [dep] The-14 is the determiner of system-15 [dep] system-15 is the nominal subject of require-18 [dep] does-16 is the auxiliary of require-18 [dep] not-17 is the adverbial modifier of require-18 [dep] require-18 is the parataxis of force-4 [dep] the-19 is the determiner of stakeholders-20 [dep] stakeholders-20 is the object of require-18 [dep] stakeholders-20 is the controlling nominal subject of use-22 [dep] to-21 is the marker of use-22 [dep] use-22 is the xclausal complement of require-18 [dep] all-23 is the predeterminer of features-25 [dep] the-24 is the determiner of features-25 [dep] features-25 is the object of use-22 [dep] of-26 is the case marker of system-28 [dep] the-27 is the determiner of system-28 [dep] system-28 is the nominal modifier of features-25 Semantic Roles: require[AGENT]the stakeholders The phrase "all the features" is a potential glossary term, actor, or domain object/property POS_57 POS_2 POS_58 The phrase "the stakeholders" is a potential glossary term, actor, or domain object/property POS_59 POS_2 POS_60 The phrase "a specific requirements elicitation process" is a potential glossary term, actor, or domain object/property POS_2 POS_61 POS_62 Phrase Structure: (ROOT (NP (JJ Flexible#1) (NN Process#1) (CC and) (NN Deliverables#1))) Syntax Dependencies: [dep] Flexible-0 is the adjectival modifier of Process-1 [dep] and-2 is the coordination of Deliverables-3 [dep] Deliverables-3 is the conjunct of Process-1 The phrase "Flexible Process and Deliverables" is a potential glossary term, actor, or domain object/property POS_2 POS_64 POS_63 The word "non-integrated" in the Text is not recognized and may be spelled incorrectly. POS_65 POS_68 POS_12 POS_67 POS_66 The word "emails" in the Text is not recognized and may be spelled incorrectly. POS_69 POS_72 POS_74 POS_73 POS_12 POS_71 POS_70 The word "improves" in the Text is vague and may lead to ambiguity. POS_12 POS_76 POS_77 POS_78 POS_79 POS_75 The word "tools" in the Text is vague and may lead to ambiguity. POS_83 POS_12 POS_84 POS_82 POS_80 POS_81 Phrase Structure: (ROOT (S (S (VP (VBG Using#1) (NP (DT the) (NN system#1)))) (VP (VBZ improves#1) (NP (NP (NN understanding#1)) (PP (IN of) (NP (DT the) (NNS requirements#3)))) (PP (IN by) (NP (NP (PDT all) (DT the) (NNS stakeholders#1)) (PP (VBN compared#1) (PP (IN to) (NP (NP (JJ non-integrated) (NNS tools#1)) (PP (JJ such#1) (IN as) (NP (NNS emails#1) (CC and) (NNS spreadsheets#1))))))))) (. .))) Syntax Dependencies: [dep] Using-0 is the clausal subject of improves-3 [dep] the-1 is the determiner of system-2 [dep] system-2 is the object of Using-0 [dep] understanding-4 is the object of improves-3 [dep] of-5 is the case marker of requirements-7 [dep] the-6 is the determiner of requirements-7 [dep] requirements-7 is the nominal modifier of understanding-4 [dep] by-8 is the case marker of stakeholders-11 [dep] all-9 is the predeterminer of stakeholders-11 [dep] the-10 is the determiner of stakeholders-11 [dep] compared-12 is the case marker of tools-15 [dep] non-integrated-14 is the adjectival modifier of tools-15 [dep] tools-15 is the nominal modifier of stakeholders-11 [dep] such-16 is the case marker of emails-18 [dep] emails-18 is the nominal modifier of tools-15 [dep] and-19 is the coordination of spreadsheets-20 [dep] spreadsheets-20 is the nominal modifier of tools-15 [dep] spreadsheets-20 is the conjunct of emails-18 The phrase "non-integrated tools" is a potential glossary term, actor, or domain object/property POS_85 POS_2 POS_86 The phrase "all the stakeholders" is a potential glossary term, actor, or domain object/property POS_88 POS_2 POS_87 The phrase "emails and spreadsheets" is a potential glossary term, actor, or domain object/property POS_2 POS_90 POS_89 Phrase Structure: (ROOT (NP (NNP Improved#1) (NNP Understanding#1))) Syntax Dependencies: [dep] Improved-0 is the compound modifier of Understanding-1 The phrase "Improved Understanding" is a potential glossary term, actor, or domain object/property POS_92 POS_2 POS_91 Phrase Structure: (ROOT (S (S (NP (DT The) (NN system#1)) (VP (VBZ notifies#1) (NP (NP (DT the) (NNS stakeholders#1)) (PP (IN of) (NP (NNS changes#7)))) (PP (IN to) (NP (DT the) (NN project#1))))) (. .) (S (NP (DT The) (NN user#1)) (VP (MD can) (VP (VB customize#1) (SBAR (X (WRB how)) (S (NP (DT the) (NNS notifications#1)) (VP (VBP occur#1) (X) (NP (NP (NP (DT every) (NN time#1)) (SBAR (S (NP (DT a) (NN change#7)) (VP (VBZ is) (VP (VBN made)))))) (, ,) (CC or) (NP (DT a) (JJ periodic#1) (NN summary#1))))))))) (. .))) Syntax Dependencies: [dep] The-0 is the determiner of system-1 [dep] system-1 is the nominal subject of notifies-2 [dep] the-3 is the determiner of stakeholders-4 [dep] stakeholders-4 is the object of notifies-2 [dep] of-5 is the case marker of changes-6 [dep] changes-6 is the nominal modifier of stakeholders-4 [dep] to-7 is the case marker of project-9 [dep] the-8 is the determiner of project-9 [dep] The-11 is the determiner of user-12 [dep] user-12 is the nominal subject of customize-14 [dep] can-13 is the auxiliary of customize-14 [dep] customize-14 is the parataxis of notifies-2 [dep] how-15 is the adverbial modifier of occur-18 [dep] the-16 is the determiner of notifications-17 [dep] notifications-17 is the nominal subject of occur-18 [dep] occur-18 is the clausal complement of customize-14 [dep] every-20 is the determiner of time-21 [dep] time-21 is the object of occur-18 [dep] a-22 is the determiner of change-23 [dep] made-25 is the relative clause modifier of time-21 [dep] or-27 is the coordination of summary-30 [dep] a-28 is the determiner of summary-30 [dep] periodic-29 is the adjectival modifier of summary-30 [dep] summary-30 is the object of occur-18 [dep] summary-30 is the conjunct of time-21 Semantic Roles: occur[THEME]The system occur[AGENT]The user The phrase "the project" is a potential glossary term, actor, or domain object/property POS_93 POS_2 POS_94 The phrase "every time" is a potential glossary term, actor, or domain object/property POS_2 POS_95 POS_96 The phrase "a change" is a potential glossary term, actor, or domain object/property POS_2 POS_98 POS_97 The phrase "a periodic summary" is a potential glossary term, actor, or domain object/property POS_2 POS_100 POS_99 The phrase "The user" is a potential glossary term, actor, or domain object/property POS_102 POS_2 POS_101 The phrase "the notifications" is a potential glossary term, actor, or domain object/property POS_2 POS_104 POS_103 The text "The system notifies the stakeholders of changes to the project. The user can customize how the notifications occur: every time a change is made, or a periodic summary." in the Text is complex and may be hard to understand. POS_105 POS_12 Phrase Structure: (ROOT (NP (NP (NNP Notification#1)) (PP (IN of) (NP (NNP Project#1) (NNPS Changes#1))))) Syntax Dependencies: [dep] of-1 is the case marker of Changes-3 [dep] Project-2 is the compound modifier of Changes-3 [dep] Changes-3 is the nominal modifier of Notification-0 The phrase "Project Changes" is a potential glossary term, actor, or domain object/property POS_2 POS_106 POS_107 The phrase "Notification" is a potential glossary term, actor, or domain object/property POS_2 POS_108 POS_109 The word "language" in the Text is vague and may lead to ambiguity. POS_110 POS_111 POS_12 POS_114 POS_113 POS_112 Phrase Structure: (ROOT (S (NP (DT The) (NNS requirements#1)) (VP (VBP are) (VP (VBN defined#1) (PP (IN in) (NP (JJ natural#1) (NN language#1))) (SBAR (JJ such#1) (IN that) (S (NP (JJ non-technical) (NNS users#1)) (VP (VBP do#1) (RB not#1) (VP (VB need#1) (NP (JJ specialized#1) (NNS skills#1)) (S (VP (TO to) (VP (VB understand#1) (NP (DT the) (NNS requirements#1))))))))))) (. .))) Syntax Dependencies: [dep] The-0 is the determiner of requirements-1 [dep] in-4 is the case marker of language-6 [dep] natural-5 is the adjectival modifier of language-6 [dep] such-7 is the dependent of need-13 [dep] that-8 is the marker of need-13 [dep] non-technical-9 is the adjectival modifier of users-10 [dep] users-10 is the nominal subject of need-13 [dep] do-11 is the auxiliary of need-13 [dep] not-12 is the adverbial modifier of need-13 [dep] need-13 is the clausal complement of defined-3 [dep] specialized-14 is the adjectival modifier of skills-15 [dep] skills-15 is the object of need-13 [dep] to-16 is the marker of understand-17 [dep] understand-17 is the adverbial clause modifier of need-13 [dep] the-18 is the determiner of requirements-19 [dep] requirements-19 is the object of understand-17 Semantic Roles: need[AGENT]non-technical users The phrase "specialized skills" is a potential glossary term, actor, or domain object/property POS_2 POS_115 POS_116 The phrase "natural language" is a potential glossary term, actor, or domain object/property POS_2 POS_117 POS_118 The text "The requirements are defined in natural language such that non-technical users do not need specialized skills to understand the requirements." in the Text is complex and may be hard to understand. POS_12 POS_119 Phrase Structure: (ROOT (S (NP (NNS Requirements#1)) (VP (VBN defined#1) (PP (IN in) (NP (NNP Natural#1) (NNP Language#1)))))) Syntax Dependencies: [dep] Requirements-0 is the nominal subject of defined-1 [dep] in-2 is the case marker of Language-4 [dep] Natural-3 is the compound modifier of Language-4 Semantic Roles: defined[AGENT]Requirements The word "non-users" in the Text is not recognized and may be spelled incorrectly. POS_12 POS_123 POS_122 POS_120 POS_121 Phrase Structure: (ROOT (S (NP (DT The) (NN system#1)) (VP (VBZ secures#1) (NP (NN project#1) (NN content#1)) (PP (IN from) (NP (JJ unauthorized#1) (NN access#1))) (PP (IN by) (NP (NP (NNS users#1)) (VP (RB not#1) (VBN assigned#1) (PP (IN to) (NP (NP (DT a) (NN project#1) (CC or) (NNS non-users)) (PP (IN of) (NP (DT the) (NN system#1))))))))) (. .))) Syntax Dependencies: [dep] The-0 is the determiner of system-1 [dep] system-1 is the nominal subject of secures-2 [dep] project-3 is the compound modifier of content-4 [dep] content-4 is the object of secures-2 [dep] from-5 is the case marker of access-7 [dep] unauthorized-6 is the adjectival modifier of access-7 [dep] by-8 is the case marker of users-9 [dep] not-10 is the adverbial modifier of assigned-11 [dep] assigned-11 is the clausal modifier of noun of users-9 [dep] to-12 is the case marker of project-14 [dep] a-13 is the determiner of project-14 [dep] or-15 is the coordination of non-users-16 [dep] non-users-16 is the conjunct of project-14 [dep] of-17 is the case marker of system-19 [dep] the-18 is the determiner of system-19 [dep] system-19 is the nominal modifier of project-14 Semantic Roles: secures[AGENT]The system secures[THEME]project content The phrase "unauthorized access" is a potential glossary term, actor, or domain object/property POS_124 POS_2 POS_125 The phrase "project content" is a potential glossary term, actor, or domain object/property POS_2 POS_127 POS_126 The phrase "a project or non-users" is a potential glossary term, actor, or domain object/property POS_2 POS_129 POS_128 Phrase Structure: (ROOT (NP (JJ Secure#1) (NN data#1) (NN access#1))) Syntax Dependencies: [dep] Secure-0 is the adjectival modifier of access-2 [dep] data-1 is the compound modifier of access-2 The phrase "Secure data access" is a potential glossary term, actor, or domain object/property POS_131 POS_2 POS_130 The word "work" in the Text is vague and may lead to ambiguity. POS_133 POS_12 POS_132 POS_135 POS_136 POS_134 Phrase Structure: (ROOT (S (NP (NP (DT The) (NN work#1)) (VP (VBN done) (PP (IN on) (NP (DT the) (NN thesis#1))))) (VP (VBZ is) (ADVP (RB exclusively#1)) (VP (VBN done) (PP (IN by) (NP (DT the) (NN student#1))))) (. .))) Syntax Dependencies: [dep] The-0 is the determiner of work-1 [dep] done-2 is the clausal modifier of noun of work-1 [dep] on-3 is the case marker of thesis-5 [dep] the-4 is the determiner of thesis-5 [dep] exclusively-7 is the adverbial modifier of done-8 [dep] by-9 is the case marker of student-11 [dep] the-10 is the determiner of student-11 The phrase "The work" is a potential glossary term, actor, or domain object/property POS_137 POS_2 POS_138 The phrase "the thesis" is a potential glossary term, actor, or domain object/property POS_2 POS_139 POS_140 The phrase "the student" is a potential glossary term, actor, or domain object/property POS_141 POS_2 POS_142 Phrase Structure: (ROOT (S (NP (NNP Work#1)) (VP (VBZ is) (VP (PRP$ your) (VB own#1))))) Syntax Dependencies: [dep] Work-0 is the nominal subject of own-3 [dep] is-1 is the copula of own-3 [dep] your-2 is the possession modifier of own-3 Semantic Roles: own[AGENT]Work The phrase "Work" is a potential glossary term, actor, or domain object/property POS_2 POS_143 POS_144 Phrase Structure: (X) Syntax Dependencies: Phrase Structure: (ROOT (NP (NP (NNP Poor#1) (NNP Communication#1)) (PP (IN in) (NP (NNP Requirements#1))))) Syntax Dependencies: [dep] Poor-0 is the compound modifier of Communication-1 [dep] in-2 is the case marker of Requirements-3 [dep] Requirements-3 is the nominal modifier of Communication-1 The phrase "Poor Communication" is a potential glossary term, actor, or domain object/property POS_145 POS_2 POS_146 The word "creates" in the Text is vague and may lead to ambiguity. POS_12 POS_23 POS_27 POS_25 POS_24 POS_26 The word "entities" in the Text is vague and may lead to ambiguity. POS_150 POS_12 POS_148 POS_149 POS_147 Phrase Structure: (ROOT (S (S (NP (NNP Rich#1)) (VP (VBZ logs#1) (PRT (RP in#1)) (PP (IN to) (NP (DT the) (NN system#1))))) (CC and) (S (NP (PRP it)) (VP (VBZ displays#1) (NP (NP (NP (DT a) (NN list#1)) (PP (IN of) (NP (PRP$ his) (JJ active#1) (NNS projects#1)))) (CC and) (NP (DT the) (NN option#1) (S (VP (TO to) (VP (VB create#1) (NP (DT a) (JJ new#1) (NN project#1))))))))) (. .) (S (S (NP (NNP Rich#1)) (VP (VBZ chooses#1) (S (VP (TO to) (VP (VB create#1) (NP (DT a) (JJ new#1) (NN project#1))))))) (CC and) (S (NP (DT the) (NN system#1)) (VP (VBZ displays#1) (NP (DT the) (JJ new#1) (NN project#1) (NN interface#1))))) (. .) (S (NP (NNP Rich#1)) (VP (VP (VBZ enters#1) (NP (X) (NP (NNP Mobile#1) (NNP Media#1) (NNP Portal#1)) (X) (PP (IN for) (NP (DT the) (NN project#1) (NN name#1))))) (CC and) (VP (VBZ enters#1) (NP (DT a) (JJ short#1) (NN description#1))))) (. .) (S (NP (NNP Rich#1)) (VP (VP (VBZ looks#1) (PP (IN over) (NP (NP (DT the) (NN list#1)) (PP (IN of) (NP (VBG existing#1) (NNS customers#1)))))) (CC and) (VP (VBZ does#1) (RB n't) (VP (VB see#1) (SBAR (WHNP (WP what)) (S (NP (PRP he)) (VP (VP (VBZ 's) (VP (VBG looking#1) (PP (IN for)))) (CC and) (VP (VBZ enters#1) (NP (X) (NNP Virile#1) (NNP Mobile#1) (X)))))))))) (. .) (S (NP (DT The) (NN system#1)) (VP (VP (VBZ creates#1) (NP (DT the) (JJ new#1) (NN project#1))) (CC and) (VP (VBZ adds#1) (NP (NNP Rich#1)) (PP (IN as) (NP (NP (DT a) (NN stakeholder#1)) (PP (IN with) (NP (NN permission#1) (S (VP (TO to) (VP (VP (VB edit#1) (NP (DT all) (NN project#1) (NNS entities#1))) (CC and) (VP (VB grant#1) (NP (NN permission#1)) (PP (IN to) (NP (JJ other#1) (NNS users#1))) (S (VP (TO to) (VP (VB edit#1) (NP (NNS entities#1)))))))))))))))) (. .) (S (NP (DT The) (NN system#1)) (VP (VP (VBZ closes#1) (NP (DT the) (JJ new#1) (NN project#1) (NN interface#1))) (CC and) (VP (VBZ adds#1) (NP (DT the) (JJ new#1) (NN project#1)) (PP (IN in) (NP (DT the) (NN project#1) (NN navigation#1) (NN interface#1)))))) (. .))) Syntax Dependencies: [dep] Rich-0 is the nominal subject of logs-1 [dep] in-2 is the phrasal verb particle of logs-1 [dep] to-3 is the case marker of system-5 [dep] the-4 is the determiner of system-5 [dep] and-6 is the coordination of displays-8 [dep] it-7 is the nominal subject of displays-8 [dep] displays-8 is the conjunct of logs-1 [dep] a-9 is the determiner of list-10 [dep] list-10 is the object of displays-8 [dep] of-11 is the case marker of projects-14 [dep] his-12 is the possession modifier of projects-14 [dep] active-13 is the adjectival modifier of projects-14 [dep] projects-14 is the nominal modifier of list-10 [dep] and-15 is the coordination of option-17 [dep] the-16 is the determiner of option-17 [dep] option-17 is the object of displays-8 [dep] option-17 is the conjunct of list-10 [dep] to-18 is the marker of create-19 [dep] create-19 is the clausal modifier of noun of option-17 [dep] a-20 is the determiner of project-22 [dep] new-21 is the adjectival modifier of project-22 [dep] project-22 is the object of create-19 [dep] Rich-24 is the nominal subject of chooses-25 [dep] Rich-24 is the controlling nominal subject of create-27 [dep] chooses-25 is the conjunct of logs-1 [dep] to-26 is the marker of create-27 [dep] create-27 is the xclausal complement of chooses-25 [dep] a-28 is the determiner of project-30 [dep] new-29 is the adjectival modifier of project-30 [dep] project-30 is the object of create-27 [dep] and-31 is the coordination of displays-34 [dep] the-32 is the determiner of system-33 [dep] system-33 is the nominal subject of displays-34 [dep] displays-34 is the conjunct of logs-1 [dep] displays-34 is the conjunct of chooses-25 [dep] the-35 is the determiner of interface-38 [dep] new-36 is the adjectival modifier of interface-38 [dep] project-37 is the compound modifier of interface-38 [dep] interface-38 is the object of displays-34 [dep] Rich-40 is the nominal subject of enters-41 [dep] Rich-40 is the nominal subject of enters-52 [dep] enters-41 is the conjunct of logs-1 [dep] Mobile-43 is the compound modifier of Portal-45 [dep] Media-44 is the compound modifier of Portal-45 [dep] Portal-45 is the object of enters-41 [dep] for-47 is the case marker of name-50 [dep] the-48 is the determiner of name-50 [dep] project-49 is the compound modifier of name-50 [dep] name-50 is the nominal modifier of Portal-45 [dep] and-51 is the coordination of enters-52 [dep] enters-52 is the conjunct of logs-1 [dep] enters-52 is the conjunct of enters-41 [dep] a-53 is the determiner of description-55 [dep] short-54 is the adjectival modifier of description-55 [dep] description-55 is the object of enters-52 [dep] Rich-57 is the nominal subject of looks-58 [dep] Rich-57 is the nominal subject of see-68 [dep] looks-58 is the conjunct of logs-1 [dep] over-59 is the case marker of list-61 [dep] the-60 is the determiner of list-61 [dep] of-62 is the case marker of customers-64 [dep] existing-63 is the adjectival modifier of customers-64 [dep] customers-64 is the nominal modifier of list-61 [dep] and-65 is the coordination of see-68 [dep] does-66 is the auxiliary of see-68 [dep] n't-67 is the adverbial modifier of see-68 [dep] see-68 is the conjunct of logs-1 [dep] see-68 is the conjunct of looks-58 [dep] he-70 is the nominal subject of looking-72 [dep] he-70 is the nominal subject of enters-75 [dep] 's-71 is the auxiliary of looking-72 [dep] looking-72 is the clausal complement of see-68 [dep] for-73 is the case marker of what-69 [dep] and-74 is the coordination of enters-75 [dep] enters-75 is the clausal complement of see-68 [dep] enters-75 is the conjunct of looking-72 [dep] Virile-77 is the compound modifier of Mobile-78 [dep] Mobile-78 is the object of enters-75 [dep] The-81 is the determiner of system-82 [dep] system-82 is the nominal subject of creates-83 [dep] system-82 is the nominal subject of adds-88 [dep] creates-83 is the conjunct of logs-1 [dep] the-84 is the determiner of project-86 [dep] new-85 is the adjectival modifier of project-86 [dep] project-86 is the object of creates-83 [dep] and-87 is the coordination of adds-88 [dep] adds-88 is the conjunct of logs-1 [dep] adds-88 is the conjunct of creates-83 [dep] Rich-89 is the object of adds-88 [dep] as-90 is the case marker of stakeholder-92 [dep] a-91 is the determiner of stakeholder-92 [dep] with-93 is the case marker of permission-94 [dep] permission-94 is the nominal modifier of stakeholder-92 [dep] to-95 is the marker of edit-96 [dep] edit-96 is the clausal modifier of noun of permission-94 [dep] all-97 is the determiner of entities-99 [dep] project-98 is the compound modifier of entities-99 [dep] entities-99 is the object of edit-96 [dep] and-100 is the coordination of grant-101 [dep] grant-101 is the clausal modifier of noun of permission-94 [dep] grant-101 is the conjunct of edit-96 [dep] permission-102 is the object of grant-101 [dep] to-103 is the case marker of users-105 [dep] other-104 is the adjectival modifier of users-105 [dep] to-106 is the marker of edit-107 [dep] edit-107 is the adverbial clause modifier of grant-101 [dep] entities-108 is the object of edit-107 [dep] The-110 is the determiner of system-111 [dep] system-111 is the nominal subject of closes-112 [dep] system-111 is the nominal subject of adds-118 [dep] closes-112 is the conjunct of logs-1 [dep] the-113 is the determiner of interface-116 [dep] new-114 is the adjectival modifier of interface-116 [dep] project-115 is the compound modifier of interface-116 [dep] interface-116 is the object of closes-112 [dep] and-117 is the coordination of adds-118 [dep] adds-118 is the conjunct of logs-1 [dep] adds-118 is the conjunct of closes-112 [dep] the-119 is the determiner of project-121 [dep] new-120 is the adjectival modifier of project-121 [dep] project-121 is the object of adds-118 [dep] in-122 is the case marker of interface-126 [dep] the-123 is the determiner of interface-126 [dep] project-124 is the compound modifier of interface-126 [dep] navigation-125 is the compound modifier of interface-126 Semantic Roles: enters[THEME]Rich enters[AGENT]Rich The phrase "a short description" is a potential glossary term, actor, or domain object/property POS_2 POS_152 POS_151 The phrase "the new project interface" is a potential glossary term, actor, or domain object/property POS_2 POS_154 POS_153 The phrase "a stakeholder" is a potential glossary term, actor, or domain object/property POS_156 POS_2 POS_155 The phrase "a new project" is a potential glossary term, actor, or domain object/property POS_158 POS_2 POS_157 The phrase "the project name" is a potential glossary term, actor, or domain object/property POS_2 POS_160 POS_159 The phrase "a list" is a potential glossary term, actor, or domain object/property POS_2 POS_161 POS_162 The phrase "the list" is a potential glossary term, actor, or domain object/property POS_2 POS_163 POS_164 The phrase "existing customers" is a potential glossary term, actor, or domain object/property POS_166 POS_2 POS_165 The phrase "all project entities" is a potential glossary term, actor, or domain object/property POS_2 POS_168 POS_167 The phrase "other users" is a potential glossary term, actor, or domain object/property POS_170 POS_2 POS_169 The phrase "Mobile Media Portal" is a potential glossary term, actor, or domain object/property POS_2 POS_172 POS_171 The phrase "the project navigation interface" is a potential glossary term, actor, or domain object/property POS_174 POS_2 POS_173 The phrase "" Virile Mobile "" is a potential glossary term, actor, or domain object/property POS_175 POS_2 POS_176 The text "Rich logs in to the system and it displays a list of his active projects and the option to create a new project. Rich chooses to create a new project and the system displays the new project interface. Rich enters "Mobile Media Portal" for the project name and enters a short description. Rich looks over the list of existing customers and doesn't see what he's looking for and enters "Virile Mobile". The system creates the new project and adds Rich as a stakeholder with permission to edit all project entities and grant permission to other users to edit entities. The system closes the new project interface and adds the new project in the project navigation interface." in the Text is complex and may be hard to understand. POS_12 POS_177 The word "creates" in the Name is vague and may lead to ambiguity. POS_12 POS_23 POS_27 POS_25 POS_24 POS_26 Phrase Structure: (ROOT (S (NP (NNP Rich#1)) (VP (VBZ creates#1) (NP (DT a) (JJ new#1) (NN project#1))))) Syntax Dependencies: [dep] Rich-0 is the nominal subject of creates-1 [dep] a-2 is the determiner of project-4 [dep] new-3 is the adjectival modifier of project-4 [dep] project-4 is the object of creates-1 Semantic Roles: creates[AGENT]Rich The phrase "Rich" is a potential glossary term, actor, or domain object/property POS_178 POS_2 POS_179 The word "Requel" in the Text is not recognized and may be spelled incorrectly. POS_180 POS_181 POS_12 POS_184 POS_185 POS_182 POS_183 The word "n’t" in the Text is not recognized and may be spelled incorrectly. POS_186 POS_189 POS_187 POS_12 POS_193 POS_188 POS_192 POS_190 POS_191 The word "login" in the Text is not recognized and may be spelled incorrectly. POS_204 POS_198 POS_196 POS_202 POS_199 POS_194 POS_12 POS_200 POS_201 POS_197 POS_203 POS_195 The word "username" in the Text is not recognized and may be spelled incorrectly. POS_206 POS_12 POS_207 POS_205 Phrase Structure: (ROOT (S (S (NP (NNP Rich#1)) (VP (VBZ opens#1) (NP (DT a) (NN web#1) (NN browser#1)) (PP (IN to) (NP (DT the) (NNP Requel#1) (NN system#1) (NN address#1))) (. .) (PRN (S (NP (DT The) (NN system#1)) (VP (VP (VBZ does#1) (RB n’t) (VP (VB detect#1) (NP (DT an) (VBG existing#1) (NN user#1) (NN session#1)))) (CC and) (VP (VBZ presents#1) (NP (DT the) (JJ login) (NN screen#1)))))))) (. .) (S (NP (NNP Rich#1)) (VP (VBZ enters#1) (NP (PRP$ his) (NN username) (CC and) (NN password#1)))) (, .) (S (NP (DT The) (NN system#1)) (VP (VBZ verifies#1) (NP (DT the) (NN username)))) (CC and) (S (NP (NN password#1) (NN combination#1)) (VP (VBZ is) (ADJP (JJ correct#1)) (. .) (PRN (S (NP (DT The) (NN system#1)) (VP (VBZ logs#1) (SBAR (IN that) (S (NP (NNP Rich#1)) (VP (VP (VBZ has) (ADVP (RB successfully#1)) (VP (VBN logged) (PP (IN into) (NP (DT the) (NN system#1))))) (CC and) (VP (VBZ shows#1) (NP (PRP him)) (NP (NP (NP (DT a) (NN list#1)) (PP (IN of) (NP (PRP$ his) (JJ open#1) (NNS projects#1)))) (CC and) (NP (NP (DT an) (NN overview#1)) (PP (IN of) (NP (JJ recent#1) (NN project#1) (NNS changes#1)))))))))))))) (. .))) Syntax Dependencies: [dep] Rich-0 is the nominal subject of opens-1 [dep] a-2 is the determiner of browser-4 [dep] web-3 is the compound modifier of browser-4 [dep] browser-4 is the object of opens-1 [dep] to-5 is the case marker of address-9 [dep] the-6 is the determiner of address-9 [dep] Requel-7 is the compound modifier of address-9 [dep] system-8 is the compound modifier of address-9 [dep] The-11 is the determiner of system-12 [dep] system-12 is the nominal subject of detect-15 [dep] system-12 is the nominal subject of presents-21 [dep] does-13 is the auxiliary of detect-15 [dep] n’t-14 is the adverbial modifier of detect-15 [dep] detect-15 is the parataxis of opens-1 [dep] an-16 is the determiner of session-19 [dep] existing-17 is the adjectival modifier of session-19 [dep] user-18 is the compound modifier of session-19 [dep] session-19 is the object of detect-15 [dep] and-20 is the coordination of presents-21 [dep] presents-21 is the parataxis of opens-1 [dep] presents-21 is the conjunct of detect-15 [dep] the-22 is the determiner of screen-24 [dep] login-23 is the adjectival modifier of screen-24 [dep] screen-24 is the object of presents-21 [dep] Rich-26 is the nominal subject of enters-27 [dep] enters-27 is the clausal complement of opens-1 [dep] his-28 is the possession modifier of username-29 [dep] username-29 is the object of enters-27 [dep] and-30 is the coordination of password-31 [dep] password-31 is the object of enters-27 [dep] password-31 is the conjunct of username-29 [dep] The-33 is the determiner of system-34 [dep] system-34 is the nominal subject of verifies-35 [dep] verifies-35 is the conjunct of opens-1 [dep] the-36 is the determiner of username-37 [dep] username-37 is the object of verifies-35 [dep] and-38 is the coordination of correct-42 [dep] password-39 is the compound modifier of combination-40 [dep] combination-40 is the nominal subject of correct-42 [dep] is-41 is the copula of correct-42 [dep] correct-42 is the conjunct of opens-1 [dep] The-44 is the determiner of system-45 [dep] system-45 is the nominal subject of logs-46 [dep] logs-46 is the parataxis of correct-42 [dep] that-47 is the marker of logged-51 [dep] Rich-48 is the nominal subject of logged-51 [dep] Rich-48 is the nominal subject of shows-56 [dep] has-49 is the auxiliary of logged-51 [dep] successfully-50 is the adverbial modifier of logged-51 [dep] logged-51 is the clausal complement of logs-46 [dep] into-52 is the case marker of system-54 [dep] the-53 is the determiner of system-54 [dep] and-55 is the coordination of shows-56 [dep] shows-56 is the clausal complement of logs-46 [dep] shows-56 is the conjunct of logged-51 [dep] him-57 is the indirect object of shows-56 [dep] a-58 is the determiner of list-59 [dep] list-59 is the object of shows-56 [dep] of-60 is the case marker of projects-63 [dep] his-61 is the possession modifier of projects-63 [dep] open-62 is the adjectival modifier of projects-63 [dep] projects-63 is the nominal modifier of list-59 [dep] and-64 is the coordination of overview-66 [dep] an-65 is the determiner of overview-66 [dep] overview-66 is the object of shows-56 [dep] overview-66 is the conjunct of list-59 [dep] of-67 is the case marker of changes-70 [dep] recent-68 is the adjectival modifier of changes-70 [dep] project-69 is the compound modifier of changes-70 [dep] changes-70 is the nominal modifier of overview-66 Semantic Roles: logs[AGENT]The system The phrase "the Requel system address" is a potential glossary term, actor, or domain object/property POS_2 POS_208 POS_209 The phrase "an existing user session" is a potential glossary term, actor, or domain object/property POS_2 POS_211 POS_210 The phrase "password combination" is a potential glossary term, actor, or domain object/property POS_2 POS_212 POS_213 The phrase "a web browser" is a potential glossary term, actor, or domain object/property POS_215 POS_2 POS_214 The phrase "the login screen" is a potential glossary term, actor, or domain object/property POS_217 POS_2 POS_216 The phrase "the username" is a potential glossary term, actor, or domain object/property POS_2 POS_218 POS_219 The phrase "recent project changes" is a potential glossary term, actor, or domain object/property POS_2 POS_220 POS_221 The phrase "an overview" is a potential glossary term, actor, or domain object/property POS_2 POS_223 POS_222 The text "Rich opens a web browser to the Requel system address. The system doesn’t detect an existing user session and presents the login screen. Rich enters his username and password. The system verifies the username and password combination is correct. The system logs that Rich has successfully logged into the system and shows him a list of his open projects and an overview of recent project changes." in the Text is complex and may be hard to understand. POS_12 POS_224 Phrase Structure: (ROOT (S (NP (NNP Rich#1)) (VP (VBZ logs#1) (PRT (RP in#1)) (PP (IN to) (NP (DT the) (NN system#1)))))) Syntax Dependencies: [dep] Rich-0 is the nominal subject of logs-1 [dep] in-2 is the phrasal verb particle of logs-1 [dep] to-3 is the case marker of system-5 [dep] the-4 is the determiner of system-5 Semantic Roles: logs[AGENT]Rich The word "Dave" in the Text is not recognized and may be spelled incorrectly. POS_243 POS_236 POS_238 POS_12 POS_252 POS_246 POS_245 POS_251 POS_239 POS_253 POS_260 POS_237 POS_241 POS_259 POS_256 POS_255 POS_249 POS_242 POS_257 POS_250 POS_240 POS_248 POS_258 POS_244 POS_247 POS_254 The word "dave@requel" in the Text is not recognized and may be spelled incorrectly. POS_262 POS_261 POS_12 POS_263 The word "connecting" in the Text is vague and may lead to ambiguity. POS_12 POS_280 POS_277 POS_276 POS_279 POS_278 Phrase Structure: (ROOT (S (S (NP (NNP Ron#1)) (VP (VBZ opens#1) (NP (DT a) (NN web#1) (NN browser#1)) (PP (IN to) (NP (DT the) (NNP Requel#1) (NN system#1) (NN address#1))))) (, .) (S (NP (DT The) (NN system#1)) (VP (VP (VBZ does#1) (RB n’t) (VP (VB detect#1) (NP (DT an) (VBG existing#1) (NN user#1) (NN session#1)))) (CC and) (VP (VBZ presents#1) (NP (DT the) (JJ login) (NN screen#1))))) (. .) (S (NP (NNP Ron#1)) (VP (VBZ does#1) (RB n’t) (VP (VB have#12) (NP (DT a) (NN username) (CC and) (NN password#1)) (ADVP (RB yet#1)) (SBAR (IN so) (S (NP (PRP he)) (VP (VBZ chooses#1) (NP (DT the) (NN help#1) (NN option#1)))))))) (. .) (S (NP (DT The) (NN system#1)) (VP (VBZ displays#1) (NP (NP (DT a) (NN message#1)) (SBAR (SBAR (IN that) (S (NP (DT the) (NN system#1)) (VP (VBZ requires#1) (NP (DT a) (JJ distinct#1) (NN username) (CC and) (NN password#1))))) (CC and) (SBAR (IN that) (S (NP (DT the) (NN user#1)) (VP (MD should) (VP (VB contact#1) (NP (NNP Dave#1)) (PP (PP (IN at) (NP (NN extension#1) (CD 500))) (CC or) (PP (IN via) (NP (NN email#1) (S (VP (TO to) (VP (VB dave@requel) (SBAR (IN if) (S (NP (PRP they)) (VP (VP (VBP need#1) (NP (DT a) (JJ new#1) (NN account#1))) (CC or) (VP (VBP are) (VP (VBG having#12) (NP (DT a) (NN problem#1) (VBG connecting#1))))))))))))))))))))) (. .) (S (NP (DT The) (NN system#1)) (ADVP (RB also#1)) (VP (VBZ displays#1) (NP (DT a) (NN help#1) (NN message#1)) (S (VP (VBG describing#1) (SBAR (WHNP (WP what)) (S (VP (TO to) (VP (VB do#1) (SBAR (IN if) (S (NP (DT the) (NN user#1)) (VP (VBD forgot) (NP (PRP$ their) (NN account#1) (NN information#1))))))))))) (. .) (PRN (S (NP (NNP Ron#1)) (VP (VBZ sends#1) (NP (NNP Dave#1)) (NP (DT an) (NN email#1) (S (VP (TO to) (VP (VB create#1) (S (NP (PRP him)) (NP (DT a) (JJ new#1) (NN account#1)))))))))))) (. .))) Syntax Dependencies: [dep] Ron-0 is the nominal subject of opens-1 [dep] a-2 is the determiner of browser-4 [dep] web-3 is the compound modifier of browser-4 [dep] browser-4 is the object of opens-1 [dep] to-5 is the case marker of address-9 [dep] the-6 is the determiner of address-9 [dep] Requel-7 is the compound modifier of address-9 [dep] system-8 is the compound modifier of address-9 [dep] The-11 is the determiner of system-12 [dep] system-12 is the nominal subject of detect-15 [dep] system-12 is the nominal subject of presents-21 [dep] does-13 is the auxiliary of detect-15 [dep] n’t-14 is the adverbial modifier of detect-15 [dep] detect-15 is the parataxis of opens-1 [dep] an-16 is the determiner of session-19 [dep] existing-17 is the adjectival modifier of session-19 [dep] user-18 is the compound modifier of session-19 [dep] session-19 is the object of detect-15 [dep] and-20 is the coordination of presents-21 [dep] presents-21 is the parataxis of opens-1 [dep] presents-21 is the conjunct of detect-15 [dep] the-22 is the determiner of screen-24 [dep] login-23 is the adjectival modifier of screen-24 [dep] screen-24 is the object of presents-21 [dep] Ron-26 is the nominal subject of have-29 [dep] does-27 is the auxiliary of have-29 [dep] n’t-28 is the adverbial modifier of have-29 [dep] have-29 is the parataxis of opens-1 [dep] a-30 is the determiner of username-31 [dep] username-31 is the object of have-29 [dep] and-32 is the coordination of password-33 [dep] password-33 is the object of have-29 [dep] password-33 is the conjunct of username-31 [dep] yet-34 is the adverbial modifier of have-29 [dep] so-35 is the marker of chooses-37 [dep] he-36 is the nominal subject of chooses-37 [dep] chooses-37 is the adverbial clause modifier of have-29 [dep] the-38 is the determiner of option-40 [dep] help-39 is the compound modifier of option-40 [dep] option-40 is the object of chooses-37 [dep] The-42 is the determiner of system-43 [dep] system-43 is the nominal subject of displays-44 [dep] displays-44 is the parataxis of opens-1 [dep] a-45 is the determiner of message-46 [dep] message-46 is the object of displays-44 [dep] that-47 is the marker of requires-50 [dep] the-48 is the determiner of system-49 [dep] system-49 is the nominal subject of requires-50 [dep] requires-50 is the dependent of message-46 [dep] a-51 is the determiner of username-53 [dep] distinct-52 is the adjectival modifier of username-53 [dep] username-53 is the object of requires-50 [dep] and-54 is the coordination of password-55 [dep] password-55 is the object of requires-50 [dep] password-55 is the conjunct of username-53 [dep] and-56 is the coordination of contact-61 [dep] that-57 is the marker of contact-61 [dep] the-58 is the determiner of user-59 [dep] user-59 is the nominal subject of contact-61 [dep] should-60 is the auxiliary of contact-61 [dep] contact-61 is the dependent of message-46 [dep] contact-61 is the conjunct of requires-50 [dep] contact-61 is the conjunct of contact-61 [dep] Dave-62 is the object of contact-61 [dep] at-63 is the case marker of extension-64 [dep] 500-65 is the numeric modifier of extension-64 [dep] or-66 is the coordination of contact-61 [dep] via-67 is the case marker of email-68 [dep] to-69 is the marker of dave@requel-70 [dep] dave@requel-70 is the clausal modifier of noun of email-68 [dep] if-71 is the marker of need-73 [dep] they-72 is the nominal subject of need-73 [dep] they-72 is the nominal subject of having-79 [dep] need-73 is the adverbial clause modifier of dave@requel-70 [dep] a-74 is the determiner of account-76 [dep] new-75 is the adjectival modifier of account-76 [dep] account-76 is the object of need-73 [dep] or-77 is the coordination of having-79 [dep] are-78 is the auxiliary of having-79 [dep] having-79 is the adverbial clause modifier of dave@requel-70 [dep] having-79 is the conjunct of need-73 [dep] a-80 is the determiner of problem-81 [dep] problem-81 is the object of having-79 [dep] connecting-82 is the adjectival modifier of problem-81 [dep] The-84 is the determiner of system-85 [dep] system-85 is the nominal subject of displays-87 [dep] also-86 is the adverbial modifier of displays-87 [dep] displays-87 is the parataxis of opens-1 [dep] a-88 is the determiner of message-90 [dep] help-89 is the compound modifier of message-90 [dep] message-90 is the object of displays-87 [dep] describing-91 is the xclausal complement of displays-87 [dep] what-92 is the nominal subject of do-94 [dep] to-93 is the marker of do-94 [dep] do-94 is the clausal complement of describing-91 [dep] if-95 is the marker of forgot-98 [dep] the-96 is the determiner of user-97 [dep] user-97 is the nominal subject of forgot-98 [dep] forgot-98 is the adverbial clause modifier of do-94 [dep] their-99 is the possession modifier of information-101 [dep] account-100 is the compound modifier of information-101 [dep] information-101 is the object of forgot-98 [dep] Ron-103 is the nominal subject of sends-104 [dep] sends-104 is the parataxis of displays-87 [dep] Dave-105 is the indirect object of sends-104 [dep] an-106 is the determiner of email-107 [dep] email-107 is the object of sends-104 [dep] to-108 is the marker of create-109 [dep] create-109 is the clausal modifier of noun of email-107 [dep] him-110 is the nominal subject of account-113 [dep] a-111 is the determiner of account-113 [dep] new-112 is the adjectival modifier of account-113 [dep] account-113 is the xclausal complement of create-109 Semantic Roles: chooses[AGENT]Ron The phrase "a help message" is a potential glossary term, actor, or domain object/property POS_2 POS_281 POS_282 The phrase "a message" is a potential glossary term, actor, or domain object/property POS_2 POS_284 POS_283 The phrase "a username and password" is a potential glossary term, actor, or domain object/property POS_2 POS_285 POS_286 The phrase "a problem connecting" is a potential glossary term, actor, or domain object/property POS_2 POS_287 POS_288 The phrase "a distinct username and password" is a potential glossary term, actor, or domain object/property POS_2 POS_289 POS_290 The phrase "a new account" is a potential glossary term, actor, or domain object/property POS_2 POS_291 POS_292 The phrase "the help option" is a potential glossary term, actor, or domain object/property POS_2 POS_294 POS_293 The text "Ron opens a web browser to the Requel system address. The system doesn’t detect an existing user session and presents the login screen. Ron doesn’t have a username and password yet so he chooses the help option. The system displays a message that the system requires a distinct username and password and that the user should contact Dave at extension 500 or via email to dave@requel if they need a new account or are having a problem connecting. The system also displays a help message describing what to do if the user forgot their account information. Ron sends Dave an email to create him a new account." in the Text is complex and may be hard to understand. POS_12 POS_295 Phrase Structure: (ROOT (S (NP (NNP Ron#1)) (VP (VBZ fails#1) (S (VP (TO to) (VP (VB log#1) (PRT (RP in#1)) (PP (IN to) (NP (DT the) (NN system#1))))))))) Syntax Dependencies: [dep] Ron-0 is the nominal subject of fails-1 [dep] Ron-0 is the controlling nominal subject of log-3 [dep] to-2 is the marker of log-3 [dep] log-3 is the xclausal complement of fails-1 [dep] in-4 is the phrasal verb particle of log-3 [dep] to-5 is the case marker of system-7 [dep] the-6 is the determiner of system-7 Semantic Roles: fails[AGENT]Ron The phrase "Ron" is a potential glossary term, actor, or domain object/property POS_2 POS_296 POS_297 Phrase Structure: (ROOT (S (S (SBAR (X (WRB When)) (S (S (NP (NNP Theresa#2)) (VP (VBZ logs#1) (PRT (RP in#1)))) (, ,) (S (NP (DT the) (NN system#1)) (VP (VBZ determines#1) (SBAR (IN that) (S (NP (PRP she)) (VP (VP (VBZ has) (NP (NN permission#1) (S (VP (TO to) (VP (VB create#1) (NP (NNS projects#1))))))) (CC and) (VP (VBZ displays#1) (NP (DT the) (X) (X (NNP Create#1) (NNP Project#1)) (X) (NN option#1)) (PP (IN in) (NP (DT the) (NN system#1) (NN interface#1))))))))) (, .) (S (NP (NNP Theresa#2)) (VP (VBZ chooses#1) (S (VP (TO to) (VP (VB create#1) (NP (DT a) (JJ new#1) (NN project#1))))))) (CC and) (S (NP (DT the) (NN system#1)) (VP (VBZ displays#1) (NP (DT the) (JJ new#1) (NN project#1) (NN interface#1)))) (. .))) (S (NP (NNP Theresa#2)) (VP (VP (VBZ enters#1) (NP (X) (NP (NNP Purchase#1) (NNP Order#1) (NNP System#1)) (X) (PP (IN for) (NP (DT the) (NN project#1) (NN name#1))))) (, ,) (VP (VBZ leaves#1) (NP (DT the) (NN description#1)) (S (ADJP (JJ blank#1)))) (, ,) (CC and) (VP (VBZ leaves#1) (NP (X) (NNP Bailey#1) (NNP Pet#1) (NNP Supply#1) (X))))) (, ,) (S (NP (PRP$ her) (NN default#1)) (ADVP (RB automatically#1)) (VP (VBD supplied))) (, ,) (S (PP (IN as) (NP (DT the) (NN customer#1))) (, .) (NP (DT The) (NN system#1)) (VP (VP (VBZ creates#1) (NP (DT the) (JJ new#1) (NN project#1))) (CC and) (VP (VBZ adds#1) (NP (NNP Theresa#2)) (PP (IN as) (NP (NP (DT a) (NN stakeholder#1)) (PP (IN with) (NP (NN permission#1)))))))) (S (VP (TO to) (VP (VP (VB edit#1) (NP (DT all) (NN project#1) (NNS entities#1))) (CC and) (VP (VB grant#1) (NP (NN permission#1)) (PP (IN to) (NP (JJ other#1) (NNS users#1))) (S (VP (TO to) (VP (VB edit#1) (NP (NNS entities#1)))))))))) (. .) (S (NP (DT The) (NN system#1)) (VP (VP (VBZ closes#1) (NP (DT the) (JJ new#1) (NN project#1) (NN interface#1))) (CC and) (VP (VBZ displays#1) (NP (DT the) (NN project#1) (NN navigation#1) (NN interface#1)) (S (VP (TO to) (VP (VB add#1) (CC and) (VB edit#1) (NP (NP (DT the) (NN project#1) (POS 's)) (NNS entities#1)))))))) (. .))) Syntax Dependencies: [dep] When-0 is the adverbial modifier of logs-2 [dep] Theresa-1 is the nominal subject of logs-2 [dep] logs-2 is the adverbial clause modifier of enters-45 [dep] in-3 is the phrasal verb particle of logs-2 [dep] the-5 is the determiner of system-6 [dep] system-6 is the nominal subject of determines-7 [dep] determines-7 is the clausal complement of logs-2 [dep] that-8 is the marker of has-10 [dep] she-9 is the nominal subject of has-10 [dep] she-9 is the nominal subject of displays-16 [dep] has-10 is the clausal complement of determines-7 [dep] permission-11 is the object of has-10 [dep] to-12 is the marker of create-13 [dep] create-13 is the clausal modifier of noun of permission-11 [dep] projects-14 is the object of create-13 [dep] and-15 is the coordination of displays-16 [dep] displays-16 is the clausal complement of determines-7 [dep] displays-16 is the conjunct of has-10 [dep] the-17 is the determiner of option-22 [dep] Create-19 is the compound modifier of Project-20 [dep] Project-20 is the compound modifier of option-22 [dep] option-22 is the object of displays-16 [dep] in-23 is the case marker of interface-26 [dep] the-24 is the determiner of interface-26 [dep] system-25 is the compound modifier of interface-26 [dep] Theresa-28 is the nominal subject of chooses-29 [dep] Theresa-28 is the controlling nominal subject of create-31 [dep] chooses-29 is the conjunct of logs-2 [dep] chooses-29 is the adverbial clause modifier of enters-45 [dep] to-30 is the marker of create-31 [dep] create-31 is the xclausal complement of chooses-29 [dep] a-32 is the determiner of project-34 [dep] new-33 is the adjectival modifier of project-34 [dep] project-34 is the object of create-31 [dep] and-35 is the coordination of displays-38 [dep] the-36 is the determiner of system-37 [dep] system-37 is the nominal subject of displays-38 [dep] displays-38 is the conjunct of logs-2 [dep] displays-38 is the adverbial clause modifier of enters-45 [dep] the-39 is the determiner of interface-42 [dep] new-40 is the adjectival modifier of interface-42 [dep] project-41 is the compound modifier of interface-42 [dep] interface-42 is the object of displays-38 [dep] Theresa-44 is the nominal subject of enters-45 [dep] Theresa-44 is the nominal subject of leaves-56 [dep] Theresa-44 is the nominal subject of leaves-62 [dep] Purchase-47 is the compound modifier of System-49 [dep] Order-48 is the compound modifier of System-49 [dep] System-49 is the object of enters-45 [dep] for-51 is the case marker of name-54 [dep] the-52 is the determiner of name-54 [dep] project-53 is the compound modifier of name-54 [dep] name-54 is the nominal modifier of System-49 [dep] leaves-56 is the conjunct of enters-45 [dep] the-57 is the determiner of description-58 [dep] description-58 is the object of leaves-56 [dep] blank-59 is the xclausal complement of leaves-56 [dep] and-61 is the coordination of leaves-62 [dep] leaves-62 is the conjunct of enters-45 [dep] Bailey-64 is the compound modifier of Supply-66 [dep] Pet-65 is the compound modifier of Supply-66 [dep] Supply-66 is the object of leaves-62 [dep] her-69 is the possession modifier of default-70 [dep] default-70 is the nominal subject of supplied-72 [dep] automatically-71 is the adverbial modifier of supplied-72 [dep] supplied-72 is the parataxis of enters-45 [dep] as-74 is the case marker of customer-76 [dep] the-75 is the determiner of customer-76 [dep] The-78 is the determiner of system-79 [dep] system-79 is the nominal subject of creates-80 [dep] system-79 is the nominal subject of adds-85 [dep] creates-80 is the parataxis of enters-45 [dep] the-81 is the determiner of project-83 [dep] new-82 is the adjectival modifier of project-83 [dep] project-83 is the object of creates-80 [dep] and-84 is the coordination of adds-85 [dep] adds-85 is the parataxis of enters-45 [dep] adds-85 is the conjunct of creates-80 [dep] Theresa-86 is the object of adds-85 [dep] as-87 is the case marker of stakeholder-89 [dep] a-88 is the determiner of stakeholder-89 [dep] with-90 is the case marker of permission-91 [dep] permission-91 is the nominal modifier of stakeholder-89 [dep] to-92 is the marker of edit-93 [dep] edit-93 is the parataxis of enters-45 [dep] all-94 is the determiner of entities-96 [dep] project-95 is the compound modifier of entities-96 [dep] entities-96 is the object of edit-93 [dep] and-97 is the coordination of grant-98 [dep] grant-98 is the parataxis of enters-45 [dep] grant-98 is the conjunct of edit-93 [dep] permission-99 is the object of grant-98 [dep] to-100 is the case marker of users-102 [dep] other-101 is the adjectival modifier of users-102 [dep] to-103 is the marker of edit-104 [dep] edit-104 is the adverbial clause modifier of grant-98 [dep] entities-105 is the object of edit-104 [dep] The-107 is the determiner of system-108 [dep] system-108 is the nominal subject of closes-109 [dep] system-108 is the nominal subject of displays-115 [dep] closes-109 is the parataxis of enters-45 [dep] the-110 is the determiner of interface-113 [dep] new-111 is the adjectival modifier of interface-113 [dep] project-112 is the compound modifier of interface-113 [dep] interface-113 is the object of closes-109 [dep] and-114 is the coordination of displays-115 [dep] displays-115 is the parataxis of enters-45 [dep] displays-115 is the conjunct of closes-109 [dep] the-116 is the determiner of interface-119 [dep] project-117 is the compound modifier of interface-119 [dep] navigation-118 is the compound modifier of interface-119 [dep] interface-119 is the object of displays-115 [dep] to-120 is the marker of add-121 [dep] add-121 is the adverbial clause modifier of displays-115 [dep] and-122 is the coordination of edit-123 [dep] edit-123 is the adverbial clause modifier of displays-115 [dep] edit-123 is the conjunct of add-121 [dep] the-124 is the determiner of project-125 [dep] project-125 is the possession modifier of entities-127 [dep] 's-126 is the case marker of project-125 [dep] entities-127 is the object of add-121 Semantic Roles: creates[AGENT]the system The phrase "the description" is a potential glossary term, actor, or domain object/property POS_2 POS_308 POS_309 The phrase "Purchase Order System" is a potential glossary term, actor, or domain object/property POS_2 POS_311 POS_310 The phrase "" Bailey Pet Supply "" is a potential glossary term, actor, or domain object/property POS_2 POS_312 POS_313 The phrase "the " Create Project " option" is a potential glossary term, actor, or domain object/property POS_2 POS_315 POS_314 The phrase "the system interface" is a potential glossary term, actor, or domain object/property POS_2 POS_317 POS_316 The phrase "the customer" is a potential glossary term, actor, or domain object/property POS_2 POS_319 POS_318 The phrase "the project's entities" is a potential glossary term, actor, or domain object/property POS_2 POS_320 POS_321 The text "When Theresa logs in, the system determines that she has permission to create projects and displays the "Create Project" option in the system interface. Theresa chooses to create a new project and the system displays the new project interface. Theresa enters "Purchase Order System" for the project name, leaves the description blank, and leaves "Bailey Pet Supply", her default automatically supplied, as the customer. The system creates the new project and adds Theresa as a stakeholder with permission to edit all project entities and grant permission to other users to edit entities. The system closes the new project interface and displays the project navigation interface to add and edit the project's entities." in the Text is complex and may be hard to understand. POS_12 POS_322 Phrase Structure: (ROOT (S (NP (NNP Theresa#1)) (VP (VBZ creates#1) (NP (DT a) (JJ new#1) (NN project#1))))) Syntax Dependencies: [dep] Theresa-0 is the nominal subject of creates-1 [dep] a-2 is the determiner of project-4 [dep] new-3 is the adjectival modifier of project-4 [dep] project-4 is the object of creates-1 Semantic Roles: creates[AGENT]Theresa creates[PRODUCT]a new project The phrase "Theresa" is a potential glossary term, actor, or domain object/property POS_323 POS_324 POS_2 The word "connects" in the Text is vague and may lead to ambiguity. POS_12 POS_280 POS_277 POS_276 POS_279 POS_278 The word "created" in the Text is vague and may lead to ambiguity. POS_12 POS_23 POS_27 POS_25 POS_24 POS_26 The word "get" in the Text is vague and may lead to ambiguity. POS_326 POS_328 POS_329 POS_12 POS_325 POS_327 Phrase Structure: (ROOT (S (NP (S (S (NP (NNP Theresa#1)) (VP (VBZ connects#1) (PP (IN to) (NP (NP (DT the) (NNP Requel#1) (NN system#1)) (PP (IN via) (NP (DT a) (NN web#1) (NN browser#1))))) (PP (IN from) (NP (NP (DT a) (NN link#1)) (PP (IN in) (NP (NP (DT an) (NN email#1) (NN message#1)) (VP (VBN sent) (PP (IN by) (NP (DT the) (NNP Requel#1) (NN system#1))) (SBAR (X (WRB when)) (S (NP (NP (NNP Dave#1)) (NP (DT the) (NN system#1) (NN administrator#1))) (VP (VBD created#1) (NP (DT an) (NN account#1)) (PP (IN for) (NP (PRP her))))))))))))) (. .) (S (NP (DT The) (NN system#1)) (VP (VBZ displays#1) (NP (DT the) (JJ new#1) (NN user#1) (NN setup#1) (NN interface#1)) (, ,) (S (VP (VP (VBG prompting#1) (NP (NNP Theresa#1)) (S (VP (TO to) (VP (VB confirm#1) (NP (NP (DT the) (X (JJ personal#1) (NN information#1)) (NNP Dave#1)) (VP (VBN entered#1) (PP (IN about) (NP (PRP her))))))))) (CC and) (VP (VBG filling#1) (PP (IN in) (NP (DT any) (VBG missing#1) (NN information#1))))))))) (, ,) (S (S (PP (JJ such#1) (PP (IN as) (NP (NP (NN name#1)) (, ,) (NP (NN phone#1) (NN number#1)) (, ,) (NP (NN email#1) (NN address#1)) (, ,) (NP (DT a) (NN username)) (CC and) (NP (DT a) (NN password#1))))) (, .) (SBAR (X (WRB When)) (S (NP (NNP Theresa#1)) (VP (VBZ completes#1) (S (VP (VBG entering#1) (NP (DT the) (NN information#1))))))) (NP (DT the) (NN system#1)) (VP (VBD forwards#1) (NP (PRP her)) (PP (IN to) (NP (DT the) (NN login) (NN screen#1))))) (. .) (S (NP (NNP Theresa#1)) (VP (VBZ enters#1) (NP (PRP$ her) (NN username) (CC and) (NN password#1))))) (, ,) (CC and) (S (S (NP (DT the) (NN system#1)) (VP (VBZ verifies#1) (S (NP (PRP it)) (ADJP (RB as#1) (JJ correct#1))))) (. .) (S (S (NP (DT The) (NN system#1)) (VP (VBZ logs#1) (SBAR (IN that) (S (NP (NNP Theresa#1)) (VP (VBZ has) (ADVP (RB successfully#1)) (VP (VBN logged) (PP (IN into) (NP (DT the) (NN system#1))))))))) (, ,) (CC and) (S (SBAR (IN because) (S (NP (NNP Theresa#1)) (VP (VBZ is) (NP (DT a) (NN novice#1) (NN user#1))))) (, ,) (NP (DT the) (NN system#1)) (VP (VBZ displays#1) (NP (DT the) (NN novice#1) (NN user#1) (NN interface#1)) (S (VP (TO to) (VP (VB help#1) (S (NP (PRP her)) (VP (VB get#1))))))))))) (VP (VBD started#1)) (. .))) Syntax Dependencies: [dep] Theresa-0 is the nominal subject of connects-1 [dep] connects-1 is the nominal subject of started-137 [dep] to-2 is the case marker of system-5 [dep] the-3 is the determiner of system-5 [dep] Requel-4 is the compound modifier of system-5 [dep] via-6 is the case marker of browser-9 [dep] a-7 is the determiner of browser-9 [dep] web-8 is the compound modifier of browser-9 [dep] browser-9 is the nominal modifier of system-5 [dep] from-10 is the case marker of link-12 [dep] a-11 is the determiner of link-12 [dep] in-13 is the case marker of message-16 [dep] an-14 is the determiner of message-16 [dep] email-15 is the compound modifier of message-16 [dep] message-16 is the nominal modifier of link-12 [dep] sent-17 is the clausal modifier of noun of message-16 [dep] by-18 is the case marker of system-21 [dep] the-19 is the determiner of system-21 [dep] Requel-20 is the compound modifier of system-21 [dep] when-22 is the adverbial modifier of created-27 [dep] Dave-23 is the nominal subject of created-27 [dep] the-24 is the determiner of administrator-26 [dep] system-25 is the compound modifier of administrator-26 [dep] administrator-26 is the dependent of Dave-23 [dep] created-27 is the adverbial clause modifier of sent-17 [dep] an-28 is the determiner of account-29 [dep] account-29 is the object of created-27 [dep] for-30 is the case marker of her-31 [dep] The-33 is the determiner of system-34 [dep] system-34 is the nominal subject of displays-35 [dep] displays-35 is the parataxis of connects-1 [dep] the-36 is the determiner of interface-40 [dep] new-37 is the adjectival modifier of interface-40 [dep] user-38 is the compound modifier of interface-40 [dep] setup-39 is the compound modifier of interface-40 [dep] interface-40 is the object of displays-35 [dep] prompting-42 is the dependent of displays-35 [dep] Theresa-43 is the object of prompting-42 [dep] Theresa-43 is the controlling nominal subject of confirm-45 [dep] to-44 is the marker of confirm-45 [dep] confirm-45 is the xclausal complement of prompting-42 [dep] the-46 is the determiner of Dave-49 [dep] personal-47 is the adjectival modifier of information-48 [dep] information-48 is the compound modifier of Dave-49 [dep] Dave-49 is the object of confirm-45 [dep] entered-50 is the clausal modifier of noun of Dave-49 [dep] about-51 is the case marker of her-52 [dep] and-53 is the coordination of filling-54 [dep] filling-54 is the dependent of displays-35 [dep] filling-54 is the conjunct of prompting-42 [dep] in-55 is the case marker of information-58 [dep] any-56 is the determiner of information-58 [dep] missing-57 is the adjectival modifier of information-58 [dep] such-60 is the case marker of name-62 [dep] as-61 is the case marker of name-62 [dep] name-62 is the adverbial clause modifier of forwards-84 [dep] phone-64 is the compound modifier of number-65 [dep] number-65 is the conjunct of name-62 [dep] number-65 is the adverbial clause modifier of forwards-84 [dep] email-67 is the compound modifier of address-68 [dep] address-68 is the conjunct of name-62 [dep] address-68 is the adverbial clause modifier of forwards-84 [dep] a-70 is the determiner of username-71 [dep] username-71 is the conjunct of name-62 [dep] username-71 is the adverbial clause modifier of forwards-84 [dep] and-72 is the coordination of password-74 [dep] a-73 is the determiner of password-74 [dep] password-74 is the conjunct of name-62 [dep] password-74 is the adverbial clause modifier of forwards-84 [dep] When-76 is the adverbial modifier of completes-78 [dep] Theresa-77 is the nominal subject of completes-78 [dep] completes-78 is the adverbial clause modifier of forwards-84 [dep] entering-79 is the xclausal complement of completes-78 [dep] the-80 is the determiner of information-81 [dep] information-81 is the object of entering-79 [dep] the-82 is the determiner of system-83 [dep] system-83 is the nominal subject of forwards-84 [dep] forwards-84 is the conjunct of connects-1 [dep] forwards-84 is the nominal subject of started-137 [dep] her-85 is the object of forwards-84 [dep] to-86 is the case marker of screen-89 [dep] the-87 is the determiner of screen-89 [dep] login-88 is the compound modifier of screen-89 [dep] Theresa-91 is the nominal subject of enters-92 [dep] enters-92 is the parataxis of forwards-84 [dep] her-93 is the possession modifier of username-94 [dep] username-94 is the object of enters-92 [dep] and-95 is the coordination of password-96 [dep] password-96 is the object of enters-92 [dep] password-96 is the conjunct of username-94 [dep] and-98 is the coordination of verifies-101 [dep] the-99 is the determiner of system-100 [dep] system-100 is the nominal subject of verifies-101 [dep] verifies-101 is the conjunct of connects-1 [dep] verifies-101 is the nominal subject of started-137 [dep] it-102 is the nominal subject of correct-104 [dep] as-103 is the adverbial modifier of correct-104 [dep] correct-104 is the xclausal complement of verifies-101 [dep] The-106 is the determiner of system-107 [dep] system-107 is the nominal subject of logs-108 [dep] logs-108 is the parataxis of verifies-101 [dep] that-109 is the marker of logged-113 [dep] Theresa-110 is the nominal subject of logged-113 [dep] has-111 is the auxiliary of logged-113 [dep] successfully-112 is the adverbial modifier of logged-113 [dep] logged-113 is the clausal complement of logs-108 [dep] into-114 is the case marker of system-116 [dep] the-115 is the determiner of system-116 [dep] and-118 is the coordination of displays-128 [dep] because-119 is the marker of user-124 [dep] Theresa-120 is the nominal subject of user-124 [dep] is-121 is the copula of user-124 [dep] a-122 is the determiner of user-124 [dep] novice-123 is the compound modifier of user-124 [dep] user-124 is the adverbial clause modifier of displays-128 [dep] the-126 is the determiner of system-127 [dep] system-127 is the nominal subject of displays-128 [dep] displays-128 is the parataxis of verifies-101 [dep] displays-128 is the conjunct of logs-108 [dep] the-129 is the determiner of interface-132 [dep] novice-130 is the compound modifier of interface-132 [dep] user-131 is the compound modifier of interface-132 [dep] interface-132 is the object of displays-128 [dep] to-133 is the marker of help-134 [dep] help-134 is the adverbial clause modifier of displays-128 [dep] her-135 is the nominal subject of get-136 [dep] get-136 is the clausal complement of help-134 Semantic Roles: created[AGENT]the system The phrase "the Requel system" is a potential glossary term, actor, or domain object/property POS_330 POS_2 POS_331 The phrase "phone number" is a potential glossary term, actor, or domain object/property POS_2 POS_333 POS_332 The phrase "a link" is a potential glossary term, actor, or domain object/property POS_2 POS_334 POS_335 The phrase "an email message" is a potential glossary term, actor, or domain object/property POS_2 POS_337 POS_336 The phrase "a password" is a potential glossary term, actor, or domain object/property POS_2 POS_338 POS_339 The phrase "a username" is a potential glossary term, actor, or domain object/property POS_340 POS_2 POS_341 The phrase "email address" is a potential glossary term, actor, or domain object/property POS_2 POS_343 POS_342 The phrase "the new user setup interface" is a potential glossary term, actor, or domain object/property POS_2 POS_344 POS_345 The phrase "a novice user" is a potential glossary term, actor, or domain object/property POS_2 POS_346 POS_347 The phrase "the system administrator" is a potential glossary term, actor, or domain object/property POS_2 POS_348 POS_349 The phrase "Dave the system administrator" is a potential glossary term, actor, or domain object/property POS_2 POS_351 POS_350 The phrase "any missing information" is a potential glossary term, actor, or domain object/property POS_352 POS_2 POS_353 The phrase "an account" is a potential glossary term, actor, or domain object/property POS_354 POS_2 POS_355 The phrase "the personal information Dave" is a potential glossary term, actor, or domain object/property POS_2 POS_356 POS_357 The phrase "the novice user interface" is a potential glossary term, actor, or domain object/property POS_2 POS_358 POS_359 The phrase "the information" is a potential glossary term, actor, or domain object/property POS_2 POS_361 POS_360 The text "Theresa connects to the Requel system via a web browser from a link in an email message sent by the Requel system when Dave the system administrator created an account for her. The system displays the new user setup interface, prompting Theresa to confirm the personal information Dave entered about her and filling in any missing information, such as name, phone number, email address, a username and a password. When Theresa completes entering the information the system forwards her to the login screen. Theresa enters her username and password, and the system verifies it as correct. The system logs that Theresa has successfully logged into the system, and because Theresa is a novice user, the system displays the novice user interface to help her get started." in the Text is complex and may be hard to understand. POS_12 POS_362 Phrase Structure: (ROOT (S (NP (NNP Theresa#1)) (VP (VBZ logs#1) (PRT (RP in#1)) (PP (IN to) (NP (DT the) (NN system#1)))))) Syntax Dependencies: [dep] Theresa-0 is the nominal subject of logs-1 [dep] in-2 is the phrasal verb particle of logs-1 [dep] to-3 is the case marker of system-5 [dep] the-4 is the determiner of system-5 Semantic Roles: logs[AGENT]Theresa The word "part" in the Text is vague and may lead to ambiguity. POS_12 POS_365 POS_364 POS_367 POS_363 POS_366 The word "interacts" in the Text is vague and may lead to ambiguity. POS_12 POS_369 POS_372 POS_371 POS_370 POS_368 The word "be" in the Text is vague and may lead to ambiguity. POS_375 POS_12 POS_373 POS_374 POS_376 POS_377 Phrase Structure: (ROOT (S (S (NP (DT The) (VBN automated#1) (NN assistant#1)) (VP (VP (VBZ is) (NP (NP (NN part#1)) (PP (IN of) (NP (DT the) (NN system#1))))) (, ,) (CC but) (VP (VBZ interacts#1) (PP (IN with) (NP (NP (DT the) (NNS requirements#1) (NN part#1)) (PP (IN of) (NP (NP (DT the) (NN system#1)) (PP (IN like) (NP (DT a) (NN project#2) (NN user#1))))))) (S (VP (VBG adding#1) (NP (NNS issues#1) (CC and) (NNS notes#1)) (PP (IN during) (NP (NN analysis#1)))))))) (. .) (S (NP (DT The) (VBN automated#1) (NN assistant#1)) (VP (MD will) (VP (VB be#1) (NP (NP (DT a) (NN stakeholder#1)) (PP (IN on) (NP (DT all) (NNS projects#2))))))) (. .))) Syntax Dependencies: [dep] The-0 is the determiner of assistant-2 [dep] automated-1 is the adjectival modifier of assistant-2 [dep] assistant-2 is the nominal subject of part-4 [dep] assistant-2 is the nominal subject of interacts-10 [dep] is-3 is the copula of part-4 [dep] of-5 is the case marker of system-7 [dep] the-6 is the determiner of system-7 [dep] system-7 is the nominal modifier of part-4 [dep] but-9 is the coordination of interacts-10 [dep] interacts-10 is the conjunct of part-4 [dep] with-11 is the case marker of part-14 [dep] the-12 is the determiner of part-14 [dep] requirements-13 is the compound modifier of part-14 [dep] of-15 is the case marker of system-17 [dep] the-16 is the determiner of system-17 [dep] system-17 is the nominal modifier of part-14 [dep] like-18 is the case marker of user-21 [dep] a-19 is the determiner of user-21 [dep] project-20 is the compound modifier of user-21 [dep] user-21 is the nominal modifier of system-17 [dep] adding-22 is the xclausal complement of interacts-10 [dep] issues-23 is the object of adding-22 [dep] and-24 is the coordination of notes-25 [dep] notes-25 is the object of adding-22 [dep] notes-25 is the conjunct of issues-23 [dep] during-26 is the case marker of analysis-27 [dep] The-29 is the determiner of assistant-31 [dep] automated-30 is the adjectival modifier of assistant-31 [dep] assistant-31 is the nominal subject of stakeholder-35 [dep] will-32 is the auxiliary of stakeholder-35 [dep] be-33 is the copula of stakeholder-35 [dep] a-34 is the determiner of stakeholder-35 [dep] stakeholder-35 is the parataxis of part-4 [dep] on-36 is the case marker of projects-38 [dep] all-37 is the determiner of projects-38 [dep] projects-38 is the nominal modifier of stakeholder-35 Semantic Roles: interacts[AGENT]The automated assistant The phrase "issues and notes" is a potential glossary term, actor, or domain object/property POS_2 POS_379 POS_378 The phrase "the requirements part" is a potential glossary term, actor, or domain object/property POS_2 POS_380 POS_381 The phrase "all projects" is a potential glossary term, actor, or domain object/property POS_2 POS_382 POS_383 Phrase Structure: (ROOT (NP (NNP Automated#1) (NNP Assistant#1))) Syntax Dependencies: [dep] Automated-0 is the compound modifier of Assistant-1 Phrase Structure: (ROOT (S (NP (DT This)) (VP (VBZ is) (NP (VP (DT a) (VB placeholder)) (PP (IN for) (NP (DT an) (JJ interactive#1) (NN user#1))))))) Syntax Dependencies: [dep] This-0 is the nominal subject of placeholder-3 [dep] is-1 is the copula of placeholder-3 [dep] a-2 is the determiner of placeholder-3 [dep] for-4 is the case marker of user-7 [dep] an-5 is the determiner of user-7 [dep] interactive-6 is the adjectival modifier of user-7 [dep] user-7 is the nominal modifier of placeholder-3 Semantic Roles: placeholder[AGENT]This Phrase Structure: (ROOT (NP (JJ Interactive#1) (NN User#1))) Syntax Dependencies: [dep] Interactive-0 is the adjectival modifier of User-1 Phrase Structure: (ROOT (S (NP (NNP Project#1) (NNS users#1)) (VP (VBP use#1) (NP (DT the) (NN system#1)) (S (VP (TO to) (VP (VB create#1) (NP (NP (NNP Requirements#1)) (PP (IN in) (NP (NNS projects#1)))))))) (. .))) Syntax Dependencies: [dep] Project-0 is the compound modifier of users-1 [dep] users-1 is the nominal subject of use-2 [dep] the-3 is the determiner of system-4 [dep] system-4 is the object of use-2 [dep] to-5 is the marker of create-6 [dep] create-6 is the adverbial clause modifier of use-2 [dep] Requirements-7 is the object of create-6 [dep] in-8 is the case marker of projects-9 [dep] projects-9 is the nominal modifier of Requirements-7 Semantic Roles: use[AGENT]Project users use[VALUE]the system The phrase "Project users" is a potential glossary term, actor, or domain object/property POS_2 POS_384 POS_385 Phrase Structure: (ROOT (NP (NNP Project#1) (NN User#1))) Syntax Dependencies: [dep] Project-0 is the compound modifier of User-1 Phrase Structure: (ROOT (S (NP (NNP System#1) (NN administrator#1) (NNS users#1)) (VP (VP (VBP create#1) (NP (JJ other#1) (NNS users#1))) (CC and) (VP (VBP manage#1) (NP (DT the) (X (NN system#1) (NN level#1)) (NN user#1) (NNS permissions#1)))) (. .))) Syntax Dependencies: [dep] System-0 is the compound modifier of users-2 [dep] administrator-1 is the compound modifier of users-2 [dep] users-2 is the nominal subject of create-3 [dep] users-2 is the nominal subject of manage-7 [dep] other-4 is the adjectival modifier of users-5 [dep] users-5 is the object of create-3 [dep] and-6 is the coordination of manage-7 [dep] manage-7 is the conjunct of create-3 [dep] the-8 is the determiner of permissions-12 [dep] system-9 is the compound modifier of level-10 [dep] level-10 is the compound modifier of permissions-12 [dep] user-11 is the compound modifier of permissions-12 [dep] permissions-12 is the object of manage-7 Semantic Roles: create[AGENT]System administrator users create[PRODUCT]other users The phrase "the system level user permissions" is a potential glossary term, actor, or domain object/property POS_386 POS_2 POS_387 The phrase "System administrator users" is a potential glossary term, actor, or domain object/property POS_388 POS_2 POS_389 Phrase Structure: (ROOT (NP (NNP System#1) (NNP Admin#1))) Syntax Dependencies: [dep] System-0 is the compound modifier of Admin-1 Phrase Structure: (ROOT (S (NP (DT A) (NN user#1)) (VP (VBZ creates#1) (NP (DT a) (JJ new#1) (NN project#1))))) Syntax Dependencies: [dep] A-0 is the determiner of user-1 [dep] user-1 is the nominal subject of creates-2 [dep] a-3 is the determiner of project-5 [dep] new-4 is the adjectival modifier of project-5 [dep] project-5 is the object of creates-2 Semantic Roles: creates[AGENT]A user creates[PRODUCT]a new project The phrase "A user" is a potential glossary term, actor, or domain object/property POS_2 POS_391 POS_390 Phrase Structure: (ROOT (S (NP (DT A) (NN user#1)) (VP (VBZ logs#1) (PRT (RP in#1)) (PP (IN to) (NP (DT the) (NN system#1)))))) Syntax Dependencies: [dep] A-0 is the determiner of user-1 [dep] user-1 is the nominal subject of logs-2 [dep] in-3 is the phrasal verb particle of logs-2 [dep] to-4 is the case marker of system-6 [dep] the-5 is the determiner of system-6 Semantic Roles: logs[AGENT]A user Phrase Structure: (ROOT (S (NP (DT this)) (VP (VBZ is) (NP (VP (DT a) (VB test#1)) (PP (IN of) (NP (DT the) (JJ top#1) (NN level#1))))))) Syntax Dependencies: [dep] this-0 is the nominal subject of test-3 [dep] is-1 is the copula of test-3 [dep] a-2 is the determiner of test-3 [dep] of-4 is the case marker of level-7 [dep] the-5 is the determiner of level-7 [dep] top-6 is the adjectival modifier of level-7 [dep] level-7 is the nominal modifier of test-3 Semantic Roles: test[AGENT]this The phrase "the top level" is a potential glossary term, actor, or domain object/property POS_2 POS_454 POS_455 Phrase Structure: (ROOT (S (VP (VB test#1) (NP (JJ top#1) (NN level#1) (NN scenario#1))))) Syntax Dependencies: [dep] top-1 is the adjectival modifier of scenario-3 [dep] level-2 is the compound modifier of scenario-3 [dep] scenario-3 is the object of test-0 The phrase "top level scenario" is a potential glossary term, actor, or domain object/property POS_2 POS_457 POS_456 The assistant could not analyze the structure of the step text. It may be too complex or didnt have an identifiable syntactic subject. Phrase Structure: (ROOT (S (VP (VB collect#1) (NP (DT the) (NNS underpants#1))))) Syntax Dependencies: [dep] the-1 is the determiner of underpants-2 [dep] underpants-2 is the object of collect-0 The phrase "the underpants" is a potential glossary term, actor, or domain object/property POS_458 POS_2 POS_459 Add "n’t" to the dictionary. Add "the project elements" to the project glossary. Add "Theresa" to the project glossary. Add "Theresa" as an actor to the project. Change the word "improves" to "emend". Add "the thesis" to the project glossary. Add "Project Changes" as an actor to the project. Add "Dave the system administrator" as an actor to the project. Add "n’t" to the project glossary. Add "the login screen" as an actor to the project. Add "n’t" as an actor to the project. Add "the personal information Dave" as an actor to the project. Add "A team" to the project glossary. Add "The user" as an actor to the project. Add "dave@requel" to the dictionary. Add "specialized skills or training" as an actor to the project. Change the word "be" to "be well". Add "any missing information" as an actor to the project. Add "every time" to the project glossary. Change the word "n’t" to "nut". Change the word "n’t" to "nit". Add "other users" as an actor to the project. Change the word "Dave" to "aave". Add "Dave" to the project glossary. Add "the list" as an actor to the project. Add "a password" as an actor to the project. Add "a change" as an actor to the project. Add "null" to the dictionary. Add "Rich" to the project glossary. Add "null" to the dictionary. Add "a username and password" to the project glossary. Add "login" to the project glossary. Add "emails" to the dictionary. Change the word "Dave" to "dame". Change the word "connecting" to "daisy-chain". Add "existing customers" as an actor to the project. Add "an account" as an actor to the project. Add "a distinct username and password" as an actor to the project. Change the word "interacts" to "marginalise". Change the word "be" to "hang around". Add "specialized skills or training" to the project glossary. Add "a list" to the project glossary. Change the word "login" to "logan". Change the word "get" to "come into". Ignore this word. Change the word "entities" to "thing". Add "a short description" as an actor to the project. Add "phone number" as an actor to the project. Add "non-technical" to the dictionary. Change the word "login" to "logion". Add "the system level user permissions" as an actor to the project. Change the word "login" to "log in". Change the word "interacts" to "interact". Add "the username" to the project glossary. Add "The work" to the project glossary. Change the word "non-users" to "nonusers". Add "Purchase Order System" to the project glossary. Add "Automatted Assistance" as an actor to the project. Change the word "Dave" to "gave". Add "the system administrator" to the project glossary. Add "the underpants" as an actor to the project. Add "the student" as an actor to the project. Add "the customer" to the project glossary. Change the word "Dave" to "dale". Add "the description" to the project glossary. Add "email address" to the project glossary. Change the word "interacts" to "keep in line". Change the word "login" to "logia". Add "Secure data access" to the project glossary. Add "existing customers" to the project glossary. Change the word "part" to "language unit". Change the word "login" to "log-in". Add "A user" as an actor to the project. Add "state multiple solutions" as an actor to the project. Change the word "entities" to "physical entity". Change the word "Dave" to "rave". Add "a link" as an actor to the project. Add "the stakeholders" to the project glossary. Change the word "connecting" to "conjoin". Add "the requirements part" as an actor to the project. Add "a periodic summary" to the project glossary. Change the word "work" to "housewifery". Add "a list" as an actor to the project. Change the word "Dave" to "lave". Change the word "interacts" to "collude". Add "" Virile Mobile "" to the project glossary. Add "The system" to the project glossary. Add "Automatted Assistance" to the project glossary. Change the word "language" to "signing". Add "an existing user session" as an actor to the project. Add "a username and password" as an actor to the project. Add "a new account" to the project glossary. Add "the project's entities" as an actor to the project. Change the word "non-technical" to "nontechnical". Add "Ron" as an actor to the project. Add "non-integrated tools" to the project glossary. Add "Automatted" to the dictionary. Change the word "create" to "procreate". Add "pros and cons" as an actor to the project. Change the word "improves" to "fancify". Add "the project's entities" to the project glossary. Change the word "Automatted" to "automated". Add "Requel" as an actor to the project. Add "integrated discussion" to the project glossary. Add "a new project" as an actor to the project. Add "Work" to the project glossary. Add "email address" as an actor to the project. Change the word "language" to "dead language". Add "Requirements" as an actor to the project. Add "Rich" as an actor to the project. Add "the personal information Dave" to the project glossary. Change the word "get" to "luck into". Add "" Virile Mobile "" as an actor to the project. Add "a username" to the project glossary. Add "System administrator users" to the project glossary. Change the word "create" to "beget". Add "the project elements" as an actor to the project. Add "each issue" to the project glossary. Add "the new user setup interface" to the project glossary. Change the word "tools" to "garden tool". Change the word "work" to "lavation". Add "a project" as an actor to the project. Change the word "get" to "enter upon". Change the word "Dave" to "dove". Add "the new user setup interface" as an actor to the project. Add "A user" to the project glossary. Add "a specific requirements elicitation process" as an actor to the project. Add "the stakeholders" as an actor to the project. Change the word "Dave" to "ave". Add "a message" to the project glossary. Add "the student" to the project glossary. Add "a project or non-users" as an actor to the project. Change the word "non-integrated" to "nonintegrated". Add "an account" to the project glossary. Change the word "work" to "polishing". Add "the top level" to the project glossary. Add "the login screen" to the project glossary. Add "non-technical" as an actor to the project. Add "Flexible Process and Deliverables" to the project glossary. Add "pros and cons" to the project glossary. Add "recent project changes" to the project glossary. Add "the system interface" as an actor to the project. Add "Purchase Order System" as an actor to the project. Add "the system administrator" as an actor to the project. Add "the need" as an actor to the project. Add "all the stakeholders" as an actor to the project. Add "the project navigation interface" as an actor to the project. Add "null" to the dictionary. Add "Dave" as an actor to the project. Add "the need" to the project glossary. Add "System administrator users" as an actor to the project. Add "other users" to the project glossary. Add "null" to the dictionary. Add "Flexible Process and Deliverables" as an actor to the project. Change the word "Requel" to "sequel". Add "each solution" as an actor to the project. Change the word "language" to "sign language". Change the word "get" to "purchase". Add "all projects" to the project glossary. Add "project content" to the project glossary. Add "non-technical users" to the project glossary. Change the word "login" to "loin". Add "natural language" as an actor to the project. Add "null" to the dictionary. Change the word "get" to "win back". Add "the Requel system" to the project glossary. Add "an overview" as an actor to the project. Add "all project entities" to the project glossary. Change the word "improves" to "furbish up". Add "the elements" as an actor to the project. Add "non-technical users" as an actor to the project. Add "Collaborative Elicitation" to the project glossary. Add "login" as an actor to the project. Add "" Bailey Pet Supply "" as an actor to the project. Add "null" to the dictionary. Change the word "login" to "logic". Change the word "improves" to "put right". Add "Poor Communication" as an actor to the project. Add "Notification" as an actor to the project. Add "the top level" as an actor to the project. Change the word "work" to "shining". Change the word "Dave" to "dive". Add "Secure data access" as an actor to the project. Change the word "part" to "linguistic unit". Add "each issue" as an actor to the project. Add "every time" as an actor to the project. Add "a project" to the project glossary. Change the word "create" to "spume". Change the word "tools" to "cutting implement". Change the word "part" to "component part". Change the word "tools" to "lawn tool". Add "Requel" to the dictionary. Add "username" to the dictionary. Change the word "language" to "source language". Add "an existing user session" to the project glossary. Change the word "connecting" to "hang together". Ignore this phrase. Add "the novice user interface" to the project glossary. Add "the Requel system" as an actor to the project. Add "phone number" to the project glossary. Add "dave@requel" to the project glossary. Add "a novice user" to the project glossary. Add "Automatted" as an actor to the project. Change the word "language" to "linguistic communication". Change the word "Dave" to "nave". Add "the username" as an actor to the project. Change the word "Dave" to "pave". Change the word "n’t" to "not". Add "password combination" to the project glossary. Add "password combination" as an actor to the project. Change the word "Dave" to "davy". Change the word "Dave" to "date". Add "non-integrated" to the dictionary. Add "a project or non-users" to the project glossary. Add "the " Create Project " option" to the project glossary. Add "non-users" to the dictionary. Add "Dave the system administrator" to the project glossary. Add "a stakeholder" as an actor to the project. Add "state multiple solutions" to the project glossary. Change the word "Dave" to "dare". Add "emails" to the project glossary. Change the word "emails" to "email". Add "the Requel system address" to the project glossary. Add "non-users" as an actor to the project. Add "the help option" to the project glossary. Add "a change" to the project glossary. Add "a web browser" to the project glossary. Add "a username" as an actor to the project. Add "a new project" to the project glossary. Change the word "Dave" to "dace". Add "the new project interface" as an actor to the project. Add "a help message" to the project glossary. Add "the new project interface" to the project glossary. Change the word "n’t" to "nt". Add "Improved Understanding" as an actor to the project. Add "a link" to the project glossary. Add "a help message" as an actor to the project. Add "issues and notes" as an actor to the project. Add "A team" as an actor to the project. Add "emails and spreadsheets" to the project glossary. Change the word "work" to "heavy lifting". Add "a problem connecting" to the project glossary. Add "an overview" to the project glossary. Change the word "be" to "moon about". Add "an email message" as an actor to the project. Add "the information" to the project glossary. Add "stakeholders" as an actor to the project. Add "all the stakeholders" to the project glossary. Add "emails and spreadsheets" as an actor to the project. Add "top level scenario" to the project glossary. Add "username" as an actor to the project. Add "the information" as an actor to the project. Change the word "tools" to "eolith". Change the word "create" to "father". Add "Requirements" to the project glossary. Add "Improved Understanding" to the project glossary. Add "all the features" to the project glossary. Add "unauthorized access" to the project glossary. Add "non-technical" to the project glossary. Change the word "interacts" to "transact". Add "all projects" as an actor to the project. Add "a password" to the project glossary. Change the word "Dave" to "daze". Change the word "Dave" to "dane". Add "an email message" to the project glossary. Add "Poor Communication" to the project glossary. Change the word "emails" to "remails". Add "Notification" to the project glossary. Add "username" to the project glossary. Add "Project Changes" to the project glossary. Change the word "Requel" to "refuel". Add "null" to the dictionary. Add "Automatted" to the project glossary. Add "non-users" to the project glossary. Add "the description" as an actor to the project. Add "Ron" to the project glossary. Change the word "be" to "stick by". Add "Dave" to the dictionary. Add "Work" as an actor to the project. Add "the project name" to the project glossary. Add "the project name" as an actor to the project. Add "all the features" as an actor to the project. Change the word "improves" to "bushel". Add "the " Create Project " option" as an actor to the project. Change the word "tools" to "abrader". Change the word "login" to "logie". Add "integrated discussion" as an actor to the project. Change the word "Dave" to "save". Add "issues and notes" to the project glossary. Add "the project navigation interface" to the project glossary. Add "project content" as an actor to the project. Add "a distinct username and password" to the project glossary. Add "The system" as an actor to the project. Add "the novice user interface" as an actor to the project. Change the word "connecting" to "bring together". Add "the customer" as an actor to the project. Add "Mobile Media Portal" as an actor to the project. Add "a stakeholder" to the project glossary. Change the word "Requel" to "prequel". Add "the system interface" to the project glossary. Change the word "be" to "make sense". Add "null" to the dictionary. Add "emails" as an actor to the project. Add "all project entities" as an actor to the project. Change the word "n’t" to "net". Add "null" to the dictionary. Add "a periodic summary" as an actor to the project. Add "the thesis" as an actor to the project. Add "the Requel system address" as an actor to the project. Add "Collaborative Elicitation" as an actor to the project. Add "dave@requel" as an actor to the project. Change the word "connecting" to "interdepend". Add "the list" to the project glossary. Add "specialized skills" to the project glossary. Change the word "Dave" to "wave". Add "The work" as an actor to the project. Add "the help option" as an actor to the project. Change the word "entities" to "abstract entity". Change the word "part" to "residuum". Add "the notifications" as an actor to the project. Add "stakeholders" to the project glossary. Add "the system level user permissions" to the project glossary. Change the word "Dave" to "eave". Add "a novice user" as an actor to the project. we should be more formal Add "each solution" to the project glossary. Add "" Bailey Pet Supply "" to the project glossary. Change the word "part" to "subpart". Change the word "emails" to "mails". Add "the project" as an actor to the project. Change the word "entities" to "abstraction". Add "a web browser" as an actor to the project. Add "specialized skills" as an actor to the project. Add "a message" as an actor to the project. Add "non-integrated tools" as an actor to the project. Add "the requirements" to the project glossary. Add "the notifications" to the project glossary. Add "non-integrated" to the project glossary. Add "a short description" to the project glossary. Add "Project users" to the project glossary. Add "login" to the dictionary. Add "Mobile Media Portal" to the project glossary. Add "stakeholders" to the dictionary. Add "unauthorized access" as an actor to the project. Add "a problem connecting" as an actor to the project. Add "non-integrated" as an actor to the project. Add "top level scenario" as an actor to the project. Add "a specific requirements elicitation process" to the project glossary. Add "the requirements part" to the project glossary. Add "The user" to the project glossary. Change the word "Dave" to "have". Change the word "Dave" to "cave". Add "any missing information" to the project glossary. Add "a new account" as an actor to the project. Add "Project users" as an actor to the project. Add "the project" to the project glossary. Add "Requel" to the project glossary. Change the word "create" to "sire". Add "the underpants" to the project glossary. Add "the elements" to the project glossary. Add "recent project changes" as an actor to the project. Add "natural language" to the project glossary. Change the word "stakeholders" to "stakeholder". Add "the requirements" as an actor to the project. New