[Music] hello and welcome to the roof funny webinars my name is Cecilia and I will be hosting today's webinar and we have with us my colleague host Aventis and he will talk about how to write requirements the spacing industry using a knowledge library based on a CSS standards you will be new to the right during the webinar but if you have any questions or comments you can use the chat box but please address your comments to the youths company and not to the presenter if you have any technical issues please use the chat box or you can also send a mage to support at reuse company comm the webinar will be recorded and in today's will send you the link to the recording this is agenda the webinar first we will have a description of the company and the presenter then how to make an introduction to the e CSS standards and show how to use the knowledge library followed by a demonstration finally we will have some time for questions and answers first let me say some words about the reuse company it was created in 1999 as a spinoff from a university in madrid by system and software engineers our headquarters is in Madrid but we also have offices in London and in Stockholm our mission is to offer knowledge centric approach to leverage it Imagineering activities to our customers the reduced company or TRC we like to say that it's easy to remember if you think of tea like in traceability or like in reuse and C or in the case Q like in quality and since the company peanuts from the chorus third University of Madrid research and innovation is in our DNA and about 10% of our revenues are dedicated to research and development the reuse company is also actively involved in several large European research projects like a crystal a mess and revamped - so who is using our technology here you can see some companies that are users of our system they come from quite different industries like aerospace and defense energy automation and healthcare and now we'll introduce you to the presenter Jose he's chief operating officer at the reused company and has been the product manager our requirements called the suite tools for more than five years he has the inkosi csepp certification and is a member of the board of the spanish chapter of inkosi he is also an active contributor to the encaustic guide for writing requirements so let's start them with a presentation we hope this topic will be a real interest Thank You Cecilia thank you everybody for attending this webinar the winner will be aiming to so what is know--let's library on top of our tools for knowledge management and a dedicated to enhancing the way you write requirements but in this case using the e CSS standard if you assess for those of you who already don't know what this is this is the European corporation for his business and patient education it was funded in 1996 as an initiative established to develop a coherent single set of user-friendly standards for use in all European space activities those provided here being a space community with an integrated set of spaces specific standards so this is the definition of these CSS and now as part of the CSS you can find a larger largest space National Space Agency and agencies in Europe together with the European Space Agency itself this standard is is including or describing a set of all that this CSS is including a set of standards handbooks and technical memoranda mainly covering this for branches or disciplines by starting with project management product assurance engineering of space in general and sustainability so for all these we can find a large number of standards and some handbooks and memoranda and of course as a cross-discipline approach we have also find a glossary describing the most widely used terms in this industry so what we have done is we have created a knowledge library on top of our till knowledge manager coping with all the information or some of the information covered in this is standard during this presentation I will mention more specifically width of the standards has been covered in this knowledge library but before that let me show you what is the idea behind knowledge library so this library this kind of libraries is just a combination of knowledge items of different nature at different levels of abstraction so sorry for this many less definition I will try to give you some ideas and some some details so these nurseries are representing a specific knowledge area in this case the the rich area covered by the CSS standards with the aim of improving the ways project are managed including the promotion of the principle of quality right the first time so including the early detection of the feds in your indie projects and mainly focused on on requirements enabling semantic search portals to archive for rotary facets providing in this way a reuse of assets at a different level of instruction so a traditional with that release in time to market and the mainly improving the way engineers are generating new assets as I mentioned especially focused in these libraries as a city stay focused on on requirement and enhancing the way these requirements are inspected and verified also our north lover is promoting interoperability mechanisms and services across different disciplines in your project reducing time to elaborate the documents and systems and projects as well right so this in this picture you can you can find the five different layers that we like to classify our knowledge libraries you're starting with the right hand side another one we can find a vocabulary and glossary so remember that our approach is pretty much based on knowledge management and improving the way you write requirements or text and terms in a glossary are key to to have a consistent way of writing requirement and writing or naming other entities and accuracy projects so this is the first layer word where you have the vocabulary second layer is we humans we like to to organize items or ideas in our brain not having isolated ideas but on the contrary linking this together so this is what we do in this system conceptual model this second layer where what we do is we link terms together terms coming from the previous layer are linked together in this conceptual model and in other cases as you will see in the following slide in my example we can classify or cluster together these terms based on the meaning of the terms or based on the nature of the terms then since our approach in this presentation is to help you write a bit requirements we have the idea of patterns for us this this pattern is just a representation of the agreed-upon template or grammar living you to have a complete and consistent way of writing requires so let me tell you that this this right-hand side of the screen layers from one to three is more let's say close to the humans while now four or five are more close to the computer so all this is about having a computer helping you the engineer writing better requirements so we first we have to manage our tools to understand what is written in a text or requirement this is done by means of the formalization layer we're starting with the with the patent over starting with the patterns that are my by a specific requirement what we do in this realization is we transform this natural language in in our tools this can be this is normally English but if this committee English Spanish French Italian German Swedish Japanese I don't know if I'm forgetting any of the languages that we support and what we have to do is with the slit between this and natural language and into machine language in this case it is a somatic graph what we do this is the fourth layer and finally on top of this we provide some sort of reasoning reasoning the main focus of this presentation today is reasoning in terms of helping people writing better requirements but the reason it could be of many other different nature right so this will be converting in any further presentations so as an example of this kind of libraries we can find these with the five layers that I was mentioning before I started with vocabulary where we have a just list of the different damage that could be of use in a particular domain then the second concept or model is just linking together saying something like operation or operate and work are both pretty much close together within with the meaning of operation temperature and pressure are both environmental variables or system could have let's say a child which is aircraft and these two specific types of aircraft that are this AC 2 2 3 3 or AC 2 2 4 4 invented by by me I'd say and then the last relationship on the top of this conceptual model is just a relationship where describing a constraint in the system saying something like the system celebrate between 100 and 60 below and have 160 above right so this is the constraint then the third layer is just the definition of them of the pattern itself so this could be a possible template or grammar for a well written requirement so a particular system name cell operates at the minimum then the environmental labels if you see here is just to represent temperature or pressure or any other example of environmental variable variable and then a number and then a measurement unit so that in the fourth layer what we do is we take an actual requirement write written in English in this case and by means of our semantic search or a semantic indexing engine we transform first we match this this requirement into the pattern the pattern the previous layer and then we transform this into a semantic grass this semantic graph is the input for the fifth layer which is the reasoning in this case just comparing by the way there is a mistake in this slide this 70 that you can see here is hundred seventy as represented in in the in the textual requirement so that the reasoning part could say okay this requirement is not fitting there is not in the limits that are described in this constraint right so this is just an example of the kind of consistency checking that we can provide with our tools and especially on top of one of these and knowledge libraries so just to be more specific on what is the content from the ECSC CSS standards that have been put into our notice library let me start with the first layer the glossary as I mentioned before there is a complete document in the CSS which is the a CSS sta-1 theme this is just the the glossary of terms a large amount of terms at thousands of terms together with a definition for each of these terms so all these terms are having these terms on top of or included in our tools provides a consistent way of naming and understanding the concepts across different players in the industry and of course the system can highlighted a link references to these entries in your in your requirements or in your documents in general so these are two screenshots of our tool nor its manager showing some contents of them of the CCSS glossary then as I mentioned before the second layer is is putting this with a kind of folder linking things together so this knowledge manager is now so in some relationship between terms right so that we can say that we have the template and within phase we have the Dell definition disposal facility and so on so forth or we can have the term segment and below segment we can find let's say the children of segments in this case ground segment launch recommend space segment support and user segment right so all these with the proper definition this way of linking things together provides means to propagate queries in the reduced stages of our systems or just providing advanced information retrieval on top of our short changes support also of this system conceptual model we have the clustering idea of putting terms together just based on them on the nature or the definition or the meaning of these concepts in this case you can see a cluster called system grouping together all the entries from the glossary that are named as a system so you can you can find an altitude an orbit control system the control system is self coordinate system and so on so forth this clustering of terms provided us with means to feed the textile patterns with actual requirements and help the authors of the requirements while while they are writing the requirements on top of our requirements offering tools for stance then following now attending now from these previously blase standard to other standards we can find that the easiest standard for technical document specification the 10 OC co6 this standard provides an overview of the process and position of the technical requirement specifications defines the different types of requirements and defines requirements on the technical specifications and on itself grams so what we have done is we have mapped all these different types of requirements as a taxonomy of types of requirements in our tool knowledge manager which in turn will be linking to our tools to write requirements versification studio or the common authoring tool so that for those users are creating new requirements with with our tools they will be prompt for which type of requirements they are dealing with in for each specific case but so all these these types will be appeared in from in front of the user just to pick one of these instead of coming up with new types as they create the documents using again this similar approach what we have done is in this the very same standard we can find it not only this definition of the different types of requirements and the intended use of these different types but also we can find one or many examples for each of the types what we have done is we have created specific buttons text all patterns requirements buttons for dealing with all these examples these patterns will provide the users with a reference during the recommends authoring phase will allow an automatic portion of textual and an execute document and some of this set of patterns will be could be used for consistency checking or for the automatic generation of models out of the textual requirement in our case we are dealing with sysml models mainly generating system and models automatically from text requirements and we are now studying the possibility to also generate object role modeling over m as as is described in some of the standards in the in the ESA as well as an example of a button you can find this by zone this is live entity mullah verb communication verb entity operation and entity this is just an example of what an abstract external presentation of what an interface requirement could be so this is the screen we define it the definition in pieces standard of what an interface requirement is and that this is just the transformation between between this scripture and in this presence light and our to knowledge manager so this is the representation in knowledge familiar of all the different building blocks conforming a well-written interface requirement all this will be will be in later stages when when a user is in fact actually writing a requirement this the structure of this pattern appears for the user when they are writing requirements in this case I am focusing on doors because doors is the preferred to the Constituent tool sofa in them in the e CSS however we can also interface with plenty of all the different requirement management tools in the market so when when we provide a plugin for for one a specific tool as in this case this is the plugin for doors first you can see here on the top that the user is capable of picking one of the different types of requirements as described in the previous slide then together with the requirement we have we have a pattern you will see all these in the live demo in a minute and then once you pick the pattern you can see in front of you the definition of the pattern you can follow them you can of course move the mouse and click on the pattern so that you can find the definition the intended use examples of further comments following this pattern and of course the structure in front of you this is no longer they knowledge management tool which is now the tool with good on top of doors to help the authors of the requirements so that you can see what is the what is the structure of the pattern and of course as you are typing this tool is also connected to the glossary so that you can see here a drop-down list showing you the key concepts from the glossary in this case I am writing my requirement now this is the final block adjuster on telling me which is or I have to select which component or subsystem should be connected to the product described in my document so that all these in the screen are the the name of the subsystems or parts in the glossary of course I have already typed G R so only those starting with G R will appear so that I can just pick one and finish my my requirement now hopefully using the temp from the gloss ideas to have consistence in terms of the keywords that the I use and consistency in terms of the structure based on the pattern so this is what you get when you write The Cramps right then another important block of these this very same standard is the definition of the quality rules chapter 8 is defining a number of quality let's say quality characteristics 10 different quality characteristics starting with performance justification configuration management ambiguity uniqueness identify ability similarity completeness verification and tolerance I will have to describe each of these in more detail in the next slide and also all these tendrils are together with the three recommendations for warding including the format of the requirements which is covered by our patterns the verbal form included the definition of the of the main model works that should be used in Uruguay means and including a section 8 3 3 our set of keywords that should not be used in the requirement so the restrictions in terms of keywords so let me go into a little bit of detail for this for these rules because mainly what you find in this standard is that all these quality characteristics are of course all of them are very nice to have our lovely quality characteristics but somehow we find that this is a little bit very high level or very still absurd definition as a clear example of that is what you find in this this small [Music] piece of information coming from the standard which is section 8 - for ambiguity there's the only description you can find is the Technicolor comments would be abused so what we have done is when we found that these quality characteristics are so abstract we complemented this this quanta characteristics with a set of different different groups some of them are coming from the Inca see guide for writing requirements which is some of our references in terms of of quality rules for requirements but order are coming from from our own rules or from from literature on how to write or what not to do or to do when when it comes to writer Graham so as a result we have created this library including more specific rules for for each of those quality characteristics I will describe briefly what are the rules that we have created for these characteristics for performance we have implemented two rules one is to avoid and precise quantifies so the way of avoiding something like there shall be many of these or it has to be quick or something like that these are emphasized quantifiers and of course forcing the detection of of performance attribute together with each object in indoors second is a justification this this justification is based on two of our rules first is similar to the previous step just checking the value in a justification attribute indoors and second is the detection of the entity responsible for the responsible for the technical requirements so we are we will be forcing its requirement to identify clearly identify as a subject of the requirement one of the entities as described in the in our system right then we have the third quality characteristic of relation management what we do is with the deck we detect backward and forward traces for the requirements for ambiguity as I mentioned this is this is described in a very absurd way so we have we have come up with a list of different rules like detection of ambiguous words and expressions detection of passive voice because normally passive voice is prone to missing sub the is prompt to missing the information in this passive voice detection of conditional voice detection of active voice I have to mention that some of these rules are let's say somehow in contradiction with the actual requirement that we have found in the in the in some or many of them of the stand ECA system as in many of these you can find a passive voice or you can find conditional requirements or you can find for stanza I'm also mentioning this is like the use of pronouns I don't like to find pronounce in my requirements but pronounce are are used in some of the standards that I have check out so detection of inconsistent measurement units for forcing that each number has to be followed by am assuming unit or by the name of an entity readability incorporation misspelling pronounced as I said detection of terms or special acronyms that are not fully or well represented in the in the common law science and social so this is the kind of read rules we have created for ambiguity for uniqueness we have we have a metric special metric based on identifying overlap requirements to avoid the same requirement of the same need expressed two times that same in your document so let me show you just briefly which way the tool of behaves so these are just two examples of two requirements just because of the length of the requirement up because of the main keywords product you can think that these two requirements are different but as soon as you read it in more details you find that these two requirements are many pretty much the same so what we need is for our tool to identify that these two require requirements are overlap or this requirements are not unique let's say so what we do is we thanks to to the idea and the finishing of patterns that I was introducing before we transform this into a kind of semantic graph but in order the semantic graph generated out of these two requirements to be considered as similar semantic rod what we need is some sort of information beforehand in our knowledge library and this is what we have done with this knowledge library so in this case we have an end vital we have said in our library that there is an equivalence between a target and hit let's say that in this domain and they are considered according to the information of this ontology they are considered as synonyms very similar with the idea of actions like identify discover detect fine so all these are having a common let's say somehow common meaning and also we have implemented a taxonomy including terms like rudder as a special type of electromagnetic sensor in turn in turn as an a special type of electromagnetic device and finally this device is a kind of system right so provided that all this information is stored beforehand in the ontology it is very easy for our tool to say well these two requirements are the same so these requirements are not unique so this is what we have implemented to cope with this quality characteristic then identifiability the subject limit is that we have implemented is that just to check that the subject of the requirement expression is a function a product or a system as defining the in the glossary we are also forcing for a unique identifier for the requirements and we are also checking that the content of this identifier attribute is what we expect or contains what we expect by means of second list with a reverse pressure so these are the kind of rules that we have implemented for singularity we will be implementing rules just to force a single expression in the intercom and based on patterns ensuring that the requirements have the proper length avoiding connectors and combinators and or as well as and so on avoiding open-ended the expressions like sutra and so on and others about the enumerations about in too much detail in the in the comics prescience avoiding even using parentheses and avoiding let's say that or detecting where when you are using or you are stating the rationale together with requirements normally this has to be done in a separated attribute in indoors right completeness would we provide this conformance with the suggested patterns because the idea that all these patterns are complete the patterns include all the different blocks that are requested so that if you conform with the patterns your requirement will be complete then checking verification our only metric is just the detection of verification attribute linked to each requirement and while for the tolerance what we are doing is for some specific parameters that you can identify in the library we force that whenever you provide a value for this parameter this value is followed by the body tolerance historians could be expressed as let's say as a whole number or an absolute number as in the first example 30 plus minus 2 kilo while in the second is it is represented as a percentage of the previous amount right so these two options are valid if one of the good points of this library is that first it is available for you to download and to play around with this library with our tools and second even if some of these rules could be included in the library you can enable disable you can adapt you can tailor so you can adapt all these rules and parties and everything to the specific needs or the specific way you like to write your request so this is just an example of our tool verification student I will I will focus on this tool in the live demo so I I skip all this even better if you see it in them in the demo this is just the evolution of the quality on the time and so quite so what are the next steps before I start with the live demo first a glossary is normally a div identity plus I will will include any attempts in in the future and also we will be implementing more and more relationships and clustering in this in this gloss I second we have found other standards not only the the current specification standard but we will also like to focus in our next version in the standards and based on verification so we have found a one standard and one a handbook so we would like to implement in our library the definition of the main entities as proposed in these in these standards and handbooks the verification approach the method deliver the stages or all these entities described in this document we would like to support the verification process in our to verification studio just following the process as defined in these standards so the typical planning execution reporting control a closeout and since this handbook is also including a set of typical reports we are now implementing these reports on toggle heart but other of those capabilities that we could be implementing related to the EC SS is the semantic search of requirements based on on this ontology and the patterns of an advanced traceability and generation of models especially all our M as I mentioned before right so now I will start with a live demo remember that if you have any questions so far you can still use the chatting box just to write down your question and all these questions will be addressed when I finish this live demo prepared a video just to show the demo so in in here in here with what you can find is this verification studio here these children occasionally studio is showing you the different connectors to different that a requirement databases some of them are or doors of the basis or it could be doors next generation PTC Excel XML these requirements and some others so once you establish the connection the connection is already available for you so that connecting to this document with our tool is just as simple as a double-click on them on the connector so let me now connect to to this to this project this project the pre time connecting to just have one form of modeling on it it is a very small one just for the purpose of this demo so these are all the requirements in this module only 25 to have a very quick quality assessment of these of these documents in fact all these documents are mainly there what are the examples in the in the a CSS standard for technical document specification so this is mainly the tool verification a studio that may start from the from the end from the Quality Assurance just to show you what what you can do with with the tool so these are the three main blocks I start with the Quality Assurance and this is where you can define the set of rules to be applied to your documents right provided that the glossary is already work out in order to knowledge manager so in this particular case I have only one set of rules you can come up with different set of rules and you can apply different set of rules to different documents but the library only includes one one set of rules so these are the thirty five rules that I have identified as described in the previous slides right you can you can follow all these in performance justification visibility ambiguities or all these ten different blocks that I was mentioning before plus they're the three blocks more related on on the warden of the author requirements right so all these are just correctness we can implement the rules for consistency and completeness but mainly this standard is focus on on on correctness as you can see in this 35 rows type consistency I create I have graded only one rule and I will create during the demo I will create another one and completeness there is no metaphor for specification completeness we can analyze requirement completeness but not the completeness of the specification as a whole right so let me go back head to correctness these are all the rules and for each of the rules you can you can find out that you can provide a weight for the rules you can enable/disable the rule it is very easy to come up with your with your own tailored set of rules for each rule you have a rationale behind the rule as you can see here right of course you can you can change the values if you wish provided yet you just download them the library you can change all these names you can enable/disable and more specifically you can provide what is called the quality function so normally for each of our rule for each of our metric we'll have a quality function just trying to translate the quantitative value as obtained for each of the rules into into a qualitative value right so this is the acronym the unknown acronyms so I am expecting to have zero unknown acronyms so this is why this binary equality function is zero is okay one or more is not okay so most of our rules are just like this one our binary binary rules but some others are a little bit more complex but very easy to understand so for standard text length I can say that if the requirement is is very short it is less than four words that product is very difficult to write a requirement is less than three words if it is from four to thirty-five it is a valid requirement 25 to 60 this minimum quality of toxicity on it is a poor quality requirement right so this is the idea behind this quality functions even if as I said most of the rules that you can see here in the list are just binary and there is no need to deal with this kind of complex quality function but anyway editing any of this limit is very easy if you want to allow larger requirements it is as easy as as extending this value so the second block of the tool once you have created that or just let me go back just to mention on the point here which is the definition of the of the patterns I was mentioning these twelve different types of requirements so you can decide for each button for its symmetric configuration which of the different types of requirements you can you can you want to use right so do you have these twelve options available for you as you will see you seen in a minute so now yes let me provide us more information about the tools so I click on create configuration in here I can I can assign a specific set of rules to my documents I have only one document and on one set of rules so this it is a various type for what decision so I assign this de set of rules to my to my document and now let me show you some additional details on that you can you can see a lot of information for the configuration but I will just focus on the most important ones so first of all we can we can save the results of the quality assessment not only in our database but also in doors click on the first option the second is a kind of trigger to have automatic quality analysis even if you are not using our tool you could have the results of the quality assessment this is the trigger of course if you allow the triggers in the in to be created it is not that you just disable the option the rest of information is less important probably the only piece of information which is also important here is the way to filter out which objects in your doors module are actual requirements just to filter out comments headings and all this that is not set up and so I close here and then and also from from here from this from this second block here you can also configure additional metrics so in this case let me show you how to deal with an additional consistency metric so I click on consistency add a new metric and I will be adding the overlapping method that I was mentioning before in my slide right so you can change the name of the metric if you wish and you can provide some additional configuration in my case what I want to do is I want to analyze this document against the requirements in the very same document so I click both source and target as the same this limit below is is just how similar I want to be alerted let's say that something which is over 90% of similarity is that there are pretty much at the same requirement so I put it in 90 and then I accept and click ok so the rule is the metric is already created so now I have two metrics for for consistency together with the rest of 35 rules for correctness of course so now I like on on quality control now I have a new metric so I assign again this new metric to this to this document and I click on the quality control metric so these are now my 35 requirements now I can very quickly analyze these certified requirements against this is 35 certain my 25 comments against the 35 rules so it takes it is very quickly equality analysis for this a small document in fact most most of the time is devoted to store the results in doors so now we got it I just click OK and then I can see a lot of stars here in my document so this starts at representing these two columns correctness and consistency so that I can I can now sort or filter based on the on the results of this quality assessment right so now let me just filter and focused on those requirements with poor quality with let's say 1 star so I click in here and I have the requirement with say one star so these are my 9 requirements rate as poor quality so just hovering the mouse over one of these stars you can see the details why this Department is considered as spore quality of course TVC it's an awful requirement but some of these that are plenty of the same mistakes and in most of the cases the mistake is just that the requirements are lacking this brief verification attribute or of the proper rational attribute or and so on I can double click on on my requirement just to have some some additional detail so when I double click here the requirement opens info to make the actual text of the requirement and in here in the right hand side of the screen what you can see is a red frame meaning the quality level for this equipment is low and we can find the detail of which are the rules out of these 35 rules which are the rules correctness this is grenades focus on correctness which are the correctness rules that are not met by my requirement so I can click on any of them and the tool will be will be highlighting this defect in the screen so that if you wish you can fix this defect and provide a better content or better with the wording for your requirement so in this case the requirement is using is using shoot shooting instead of shell so first answer you could you could highlight this as conditional as I mentioned some of the requirements in the standards are using suit so you can disable this this rule is you don't like visual I like using always shout with additional attributes but it's not that you can you can remove the or disable the road right so of course in this case once you fix this defect if you have the rights to a store back indoors you can just click on save and this requirement will be safe indoors because of course the tool is fully connected to doors right let me exit without saving and let me let me show you some details of the tool we can now focus not on the requirements but the rather on the metrics so you can see how many documents you have with high medium low quality and these are my 35 metrics and I can find how many of my requirements are meeting or not these rules I can see what are the most frequent mistakes the least frequent mistakes so this is a statistical information that should allow you to to improve the level of quality of your requirement let's say as a whole right so these are the met the rules that I have never broken let's say so you can you can see this information in a kind of timeline so this is the quality pollution as you can see the quality is going down which is not normally the case when you use our tool normally the quality is going up but in this case I was adding more and more and more metrics along the time so this is why because of these auditing new rules the quality seems to be going down and down but the record the quality of the comments itself it was the same but more quality or more quality rules or let's say less level of quality this is the reason why it is going down a side of this chart in we can we can provide other advanced reporting in the tool so we have two main reports one of the full report providing a lot of information the second short report is a more concise report that we can generate in PDF and Excel in Word and you can even create your own custom report including exactly the information you wish right so this is very briefly speaking all the information and all the features of verification studio now let me jump or change into into doors just to show you the second of our tools the recommends authoring tool so this is the same project and the same module that I was using in the previous verification studio tool so these are my 25 requirements and now because of because I store the results of the quality assessment back in doors you have all this information here that I'm showing you we have just created an additional view the quality view and this quality view is containing all this information right so level of quality and mainly the main results of after the analysis of each of the requirements right so of course in here you can still write a new requirement as I am doing now following the typical doors mechanism to write a new requirement and remember that I have a trigger so I can write something like the product shall fly I hope and as soon as I store this requirement in the doors database the tool will will be analyzing business telling me ok the level of quality is medium because of this and this condition is you could you could follow this and and uncheck why this just a medium and not high quality right so even if we provide this capability normally the best way to come up with a new requirement is by using our menu or using the contextual menu or using even using the shortcut just to create a new requirement using using in this case I press ctrl-a you can set up shortcuts for the different actions of the authoring tool so ctrl a and now the authoring tool is is opening first time it takes some seconds and after that it is very quick so I have my screen to create any requirement so I have a blank box on the left to right and on the right you have the red frame in this case with the set of rules that I am breaking yeah yes I didn't even start writing but I have I am breaking some rules there is no shell there is no main verb there is no entity as a subject of my requirement and so on so forth of course all the attributes for performance information justification are empty so this is why the level quality of my requirement is red even if even if I didn't even making a mistake in the in the writing of my requirement so let me show you now the second capability which is which is the patterns so I have here all my different types of requirements available they remember the definition in the previous to do education studio and now for each for this interface requirement I have only a one button this is the information about this pattern the description the examples the intended use and of course the structure itself so I have to name an entity model verb a communication verb and so on so I start typing and as you can see that there is a kind of a drug drop-down list showing up information coming from the glossary so only those terms coming from the glossary that are suitable for each specific block of the requirement according to the pattern will appear in front of me so that I can pick a term instead of having to come up with new names right so let me write a product or the four options and that are open in the standard brother cell and now a verb with the semantics of communication of interface dialogue so you can see how quick is to write a requirement because I can once I have the keyword I can just press the tab key and and on the keyboard appears so the producer dialogue with the ground segment using telemetry right so now you can see that this yellow frame surrounding my requirement now it turns into brain meaning that the scripture of this requirement is is okay is fitting with the content of the of the pattern and of course in the right hand side this green is meaning that only the method dealing with with the empty attributes have been detected for the rest of the matrix everything is or seems to be okay right so this is my my requirement of course I could save this requirement indoors because this is cream is on top of doors or I can if I wish I can provide I can get relief additional information so I can I can select one of the terms in my requirement and I can check whether or not it is coming from there from the glossary so I can see what is the definition in the glossary I can see the sources in the glossary I can I can see the clusters the scope note or I can see or even their relationship right and let me just show you how or a different day use case where suppose that instead of using the terms from the glossary I have to come up with a new term I can still create this requirement even if I invent and we'd say this new term of course successive AAA is not valid remedies in fact misspelled a key word so this is why as soon as I have changed this everything is red I can click on the incorrect spelling metric and then the tool highlight that this term is not part of the glossary however what I can do is I can communicate with the glossary manager and say okay please consider the possibility to add this new term in the gloss I so I can write down the description or my request so please do this for me and then this suggestion will be centered to the knowledge manager so that he or she could decide whether or not to put this new term in the glossary so I save with a low or still with the local area of course when when the manager of the ontology could say yes this term is now part of a below sorry this will turn into green let me show you a second requirement created with the authoring tool now let me change the the pattern that we change the type of requirement so a configuration requirement I have two oxygens so let me pick one of these two available patterns to write this requirement so this is the concise way of writing this configuration requirement so I start typing similarly following the content of the of the glossary and following the pattern so the product shall now this is our configuration requirement only two verbs as option container up so let me pick one of these so in this particular case I will say the prompt cell contain then a number of parts so so I'll contain six power motors power model is also coming from the dictionary so this is why I have now the green frame surrounding my requirements this is a bias requirement according to the structure and let me show you some additional capabilities in here which is first and all these advanced quality tabs right so from here you can see not only correctness but consistency completeness and some additional information like finding similar requirements remember the the metric I was mentioning before so this allows you to say that well I wrote the processor contains six per module what I already have another comment saying the product should contain six pm with two power outlets fire engine in my ontology PM is synonym of power module so this is why the level of similarity assessed by the tool is hundred percent so since this requirement seems to be already existing already duplicated this is not a unique requirement then for this time let me just exit without saving so let me just with the semi screen let me create my final requirement I will pick another different type of button physical requirement just to demonstrate the last consistency topic in here and pick my pattern and write their product shall half Oh [Music] wait so that the the parameter variables appear in front of me a weight of two bands but so this requirement is fitting with the standard but probably this could be in on consistency with all the requirements in my document so let me check a consistency remember that I had this metric to check the consistency in terms of the measurement units that you are using and the tool what is the same is from the correctness point of view everything is okay this brain however from the consistency point of view is an issue because there are some other requirements that are not using the British imperial system but on the contrary they are using the international metric Bismol metric system right so I click on the details and then the tool is telling me sixty-three percent of the elements are okay but you have thirty something that are wrong and then I can I can find which ones are use in the imperial system and which ones are using the international system right so that very quickly the tool will not say okay use this or use the order but it will is just highlighting the possibility of mismatch in terms of the measurement units so that's all from for this demo and now let me go back to them to the slide so just to say thank you and now I think that Cecilia is nice you baby take it away and thank you very much for faith if you have any comments or questions you can serve them just through the checkbox to the US company we have a comment here about where you can find these three standards and they are available after the CSS AML yeah yes mm oh yes how to conclude to register - Treecko we just register in the SPSS dot NL and all this kind of available including the secretary and understand under standard on how to write the other plans okay thank you I have another question I have you wanted to analyze three ETFs and that's when your tools okay this is a nicer question I have to tell you that no we haven't analyzed the ideate all these large another crystal that's just for a couple of main reasons or three reasons first because the number system that this is forgot but of course they are all available in indoors format so that it would be very quick for us to do it but the main reasons is second because we have identify them some are common content in in most of these standards that are not following them they're our basic approach on how to ride the planet so forces passive voice is repeated over and over and over again in these standards and pronouns when and mixing in the text of the report mixing the specific need together with the rationale so this is why I decided not to show you a real requirement document or a real standard on the screen right so these are the main the main reasons is our ala yeah this is this is our city representation language is the formal language based on semantic graph that we use to represent in our system and text on the planet so once we take text requirement as written in English and what I said in this is because Lisa standardise is known in English but you can also be with French German Spanish Italian through this and Japanese so what we do is we take the reporting link and we transform into something that the tool can understand and deal with and this this language is our srl which is a kind of semantics that you have directed on that is an email and I can I can send you additional information on this because you don't have much information about going our website for this is RL so please second email and I will provide you with a visual information and you find you have an own language for formalization is this the proprietary language this this is our srl and is done by us so this proprietary language it is an open language so we have papers already published describing what is the literature shape of this language so you can see what we take up then the structure of what we get and so forth so and this is the basic flow of the rest of the quality assessment or generation of models or translation of deployments or generation of test cases so all these properties we have only covered today their quality assessment but all these are based on based on on the idea of transform learning with text into this a sparkle and how effective would the analysis be is an organization is not using photo patents for the crime and time the prophetís is just one of the blocks that allows us to write the requirements the second block is the identification of the quality rules so you can you can use both together to have a more powerful approach or you can use just the set of quality rules apply even if you don't follow the pocket so you can apply just there let's say the items after was sown in our tool in the right hand side of the screen in web so the other was the effect that they were found this can be used without buttons thank you very much again to the all the participant and thank you very much open and believe it it will send you the cannon upon exchange within us and you can also find this information on our web use company comm slash webinar you have any further questions or want to learn more information don't hesitate to contact us by email to contact actually use company comm or through our website we use company comm thank you very much but again thank you everyone good bye