Design method and device of function specification document, electronic equipment and storage medium

Abstract

The embodiment of the invention relates to the technical field of document processing, and discloses a function specification document design method and device, electronic equipment and a storage medium. The method comprises the following steps: after a function model is debugged, decomposing a model structure and a logical relationship of the function model to determine a chapter structure of a function specification document; designing a cover template, and obtaining data source information of the functional model; compiling files corresponding to the cover template and the functional structure based on the data source information and the chapter structure; and compiling and generating a function specification document based on all files. According to the method and the device, the problems of low efficiency and high error rate of a mode of manually compiling the function specification document are at least solved, the compiling efficiency of the function specification document is favorably improved, and the design error risk is reduced.

Description

Technical Field

[0001] This invention relates to the field of document processing technology, and in particular to a design method, apparatus, electronic device, and storage medium for functional specification documents. Background Technology

[0002] With the arrival of the "new four modernizations" era of automobiles, user demands are increasing daily. Abundant application scenarios and personalized driving experiences are driving rapid iteration and innovation in vehicle E / E functions. The complexity and diversity of intelligent connected vehicle (ICV) functional configurations have triggered a revolution in E / E architecture design theories and methods. Model-driven systems engineering-based automotive E / E architecture design and development methods are gradually gaining attention from OEMs.

[0003] Model-based E / E architecture design and development can improve development efficiency, identify and mitigate potential risks early, reduce development and later maintenance costs, and lower the difficulty of developing complete vehicle products. However, as the number of model design deliverables continues to increase, the high complexity and large data volume of the models present challenges when transmitting requirements downstream, hindering the rapid transmission of requirements. Furthermore, downstream development processes require clearly defined, itemized requirements, making this approach inconvenient for function maintenance and iterative use. Although some E / E function development and design still rely on manually written documentation specifications, this method is inefficient and prone to errors. Summary of the Invention

[0004] The purpose of this invention is to provide a design method, apparatus, electronic device, and storage medium for functional specification documents, so as to at least solve the problems of low efficiency and high error rate of manually writing functional specification documents, thereby improving the efficiency of writing functional specification documents and reducing the risk of design errors.

[0005] To address the aforementioned technical problems, in a first aspect, the present invention provides a method for designing a functional specification document, comprising at least:

[0006] After the functional model is debugged, the model structure and logical relationships of the functional model are decomposed to determine the chapter structure of the functional specification document;

[0007] Design a cover template and obtain the data source information of the functional model;

[0008] Based on the data source information and the chapter structure, complete the compilation of the cover template and the corresponding documents for each functional structure;

[0009] Based on all the aforementioned documents, a functional specification document was compiled and generated.

[0010] Optionally, the step of completing the cover template and the corresponding document compilation for each functional structure based on the data source information and the chapter structure specifically includes:

[0011] Based on the aforementioned chapter structure, determine all the functional structures required for the functional specification document;

[0012] Extract the cover template and element data required for each functional structure from the data source information using a preset processing method;

[0013] Write the element data into the cover template and the template file corresponding to each of the functional structures;

[0014] Format design is performed on each template file to complete the compilation of the cover template and the corresponding documents for the functional structure.

[0015] Optionally, the step of generating a functional specification document based on all the aforementioned documents specifically includes:

[0016] All the aforementioned documents should be compiled and stored in a unified folder, and a new master template file for design specifications should be created.

[0017] The functional specification document is generated by referencing the corresponding files in the unified folder within the master template file of the design specifications, according to preset rules.

[0018] Optionally, the step of compiling the functional specification document by referencing the corresponding files in the unified folder within the overall design specification template file according to preset rules, specifically includes:

[0019] Create a file directory within the master template file of the design specifications;

[0020] The functional specification document is generated by using the file directory and referencing the corresponding files through the unified folder.

[0021] Optionally, the step of using the file directory to reference the corresponding files through the unified folder to generate the functional specification document specifically includes:

[0022] Using the file directory and referencing the corresponding files through the unified folder, an initial functional specification document is generated.

[0023] Perform verification tests on the initial functional specification document;

[0024] If the verification test passes, the initial functional specification document will be identified as the functional specification document.

[0025] Optionally, after performing verification testing on the initial functional specification document, the method further includes:

[0026] If the verification test fails, the initial functional specification document shall be adjusted and the adjusted initial functional specification document shall be re-verified.

[0027] At least after the revised initial functional specification document passes the verification test, the revised initial functional specification document will be determined as the functional specification document.

[0028] Optionally, the functional structure includes at least one of the following: revision record structure, preface structure, functional overview structure, entry / exit condition structure, functional interface structure, bus communication structure, timing diagram structure, state diagram structure, human-machine interface structure, and performance requirement structure.

[0029] Secondly, the present invention also provides a design apparatus for a functional specification document, comprising at least:

[0030] The chapter structure module is used to obtain the model structure and logical relationships of the functional model after the functional model debugging is completed, so as to determine the chapter structure of the functional specification document;

[0031] The design acquisition module is used to design the cover template and acquire the data source information of the functional model;

[0032] The document compilation module is used to complete the document compilation corresponding to the cover template and functional structure based on the data source information and the chapter structure.

[0033] The functional specification module is used to compile and generate functional specification documents based on all the aforementioned documents.

[0034] Thirdly, the present invention also provides an electronic device, including a memory and a processor, the memory storing a computer program executable on the processor, the processor executing the program to implement the steps in the design method of the functional specification document of any one of the first aspects.

[0035] Fourthly, the present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps in the design method of the functional specification document described in any one of the first aspects.

[0036] The technical solution provided by this invention firstly involves decomposing the model structure and logical relationships of the functional model after debugging to determine the chapter structure of the functional specification document; secondly, designing a cover template and obtaining the data source information of the functional model; then, completing the compilation of the cover template and the corresponding documents of the functional structure based on the data source information and the chapter structure; and finally, generating the functional specification document based on all the documents.

[0037] Therefore, this invention, on the one hand, by decomposing the model structure and logical relationships of the functional model after debugging, and converting the model structure and logical relationships into the chapter structure of the functional specification document, can automatically complete the planning of the overall architecture of the functional specification document. On the other hand, by acquiring data source information and storing it in a specified path, this invention completes the compilation of the cover template and the corresponding files for each functional structure, enabling the automatic generation of functional specification documents based on the element content of the model. Based on this, this invention at least solves the problems of low efficiency and high error rate of manually writing functional specification documents, improving the efficiency of writing functional specification documents, reducing the risk of design errors, and realizing the platformization, customization, flexibility, and intelligence of product research and development design. Attached Figure Description

[0038] Figure 1 This is a flowchart illustrating a design method for a functional specification document provided in an embodiment of the present invention;

[0039] Figure 2 This is a flowchart of another design method for functional specification documents provided in an embodiment of the present invention;

[0040] Figure 3 This is a flowchart of another functional specification document design method provided by an embodiment of the present invention;

[0041] Figure 4 This is a sub-flowchart of a design method for a functional specification document provided in an embodiment of the present invention;

[0042] Figure 5 This is a schematic diagram of the structure of a design device for a functional specification document provided in an embodiment of the present invention;

[0043] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention;

[0044] Figure 7 This is a flowchart of another functional specification document design method provided by an embodiment of the present invention;

[0045] Figure 8 This is a flowchart of another functional specification document design method provided by an embodiment of the present invention. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0047] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “said,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, and “multiple” generally includes at least two unless the context clearly indicates otherwise.

[0048] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0049] It should be understood that although the terms first, second, third, etc., may be used in the embodiments of this application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, first may also be referred to as second without departing from the scope of the embodiments of this application, and similarly, second may also be referred to as first.

[0050] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0051] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that an article or device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such an article or device. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the article or device that includes said element.

[0052] It should be noted that any symbols and / or numbers present in the specification that are not marked in the accompanying drawings are not reference numerals.

[0053] Figure 1 This is a flowchart illustrating a design method for a functional specification document provided by an embodiment of the present invention. This embodiment is applicable to at least various functional model functional specification document writing scenarios. The design method for this functional specification document can be, but is not limited to, executed by the functional specification document design device in this embodiment of the present invention. This execution entity can be implemented using software and / or hardware. Figure 1 As shown, the design methodology of this functional specification document includes at least the following steps:

[0054] S1. After the functional model is debugged, decompose the model structure and logical relationships of the functional model to determine the chapter structure of the functional specification document.

[0055] The functional model can be a model of the vehicle's electronic / electrical functions, such as a sunroof control function model. This can be understood as using tools like Rhapsody to model the vehicle's electronic / electrical functions. Debugging can verify the correctness of the functional model's logic, such as whether the sunroof in the sunroof control model can open normally. The model structure can be understood as the structural relationships between the various functional modules of the functional model. Logical relationships can be the reference / call relationships between the various functional modules. The chapter structure can be understood as the outline of the functional specification document.

[0056] S2. Design the cover template and obtain the data source information for the functional model.

[0057] The cover template is used to design the cover of the functional specification document. The cover template can be a new model created in DocumentStudio and named CoverPage. Data source information can include elements, packages, blocks, names, tags, values, strings, specifications, descriptions, etc., from the functional model. After obtaining the data source information, it can be stored according to a specified path. When needed, the Rhapsody tool can be used to automatically extract these elements from a predefined template.

[0058] S3. Based on the data source information and chapter structure, complete the compilation of the cover template and the corresponding functional structure documents.

[0059] The document compilation can be done using a .dta file. The document compilation method for the cover template can be as follows: select appropriate elements, structures, lists, and data (i.e., data source information) in the Document Studio palette window, edit the attribute content in the template, and, referring to the structure view in the Rhapsody functional model, use methods such as indexing, scripting filtering, and operand operator assignment definitions in the data source to locate the position of the model elements, thereby completing the .dta file compilation of the document cover template. Similarly, based on the data source information in the functional model, it is also necessary to complete the .dta file compilation for each functional structure. In one specific implementation, optionally, the functional structure includes at least one of the following: revision record structure, preface structure, functional overview structure, entry / exit condition structure, functional interface structure, bus communication structure, sequence diagram structure, state diagram structure, human-computer interface structure, and performance requirement structure.

[0060] S4. Generate functional specification documents based on all files.

[0061] The functional specification document can be a Word document of the functional specification design.

[0062] The technical solution provided in this embodiment firstly decomposes the model structure and logical relationships of the functional model after the functional model is debugged in order to determine the chapter structure of the functional specification document; secondly, it designs a cover template and obtains the data source information of the functional model; then, it completes the compilation of the cover template and the corresponding documents of the functional structure based on the data source information and the chapter structure; finally, it generates the functional specification document based on all the documents.

[0063] Therefore, this embodiment, on the one hand, after the functional model is debugged, decomposes the model structure and logical relationships of the functional model, and converts the model structure and logical relationships into the chapter structure of the functional specification document, thus automatically completing the overall architecture planning of the functional specification document. On the other hand, this embodiment obtains data source information and can store the data source information to a specified path to complete the compilation of the cover template and the corresponding files for each functional structure, realizing the automatic generation of functional specification documents based on the element content of the model. Based on this, this embodiment at least solves the problems of low efficiency and high error rate of manually writing functional specification documents, which helps to improve the writing efficiency of functional specification documents, reduce the risk of design errors, and realize the platformization, customization, flexibility, and intelligence of product research and development design.

[0064] Based on the above embodiments or implementation methods Figure 2 This is a flowchart illustrating another design method for functional specification documents provided in this embodiment of the invention. Figure 7This is a flowchart illustrating another design method for a functional specification document provided in this embodiment of the invention. This embodiment is based on the above embodiments and includes additional steps. Figure 2 and Figure 7 As shown, the design methodology of this functional specification document includes at least the following steps:

[0065] S1. After the functional model is debugged, decompose the model structure and logical relationship of the functional model to determine the chapter structure of the functional specification document.

[0066] S2. Design the cover template and obtain the data source information for the functional model.

[0067] S31. Determine all the functional structures required for the functional specification document based on the chapter structure.

[0068] It is evident that the chapter structure also dictates the layout order of the functional structure.

[0069] S32. Extract the cover template and element data required for each functional structure from the data source information using a preset processing method.

[0070] One of the default processing methods is to select the appropriate element data in the Document Studio palette window.

[0071] S33. Write the element data into the cover template and the template file corresponding to each functional structure.

[0072] S34. Perform format design for each template file to complete the compilation of the cover template and the corresponding functional structure.

[0073] In this context, the format design can involve editing the attribute content in the template, referring to the structural view in the Rhapsody functional model, and using methods such as indexing, scripting filtering, and operand operator assignment definition in the data source to lock the position of the model element. This embodiment does not limit the locking method.

[0074] S41. Compile all files and store them in a unified folder, and create a new master template file for the design specifications.

[0075] The master template file for the design specifications can be a .dta file.

[0076] S42. Within the overall design specification template file, compile the corresponding files by referencing a unified folder according to preset rules to generate the functional specification document.

[0077] The preset rules can be to create file directories and use directories to reference the corresponding files.

[0078] Therefore, this embodiment, on the one hand, after the functional model is debugged, decomposes the model structure and logical relationships of the functional model, and converts the model structure and logical relationships into the chapter structure of the functional specification document, thus automatically completing the overall architecture planning of the functional specification document. On the other hand, this embodiment obtains data source information and can store the data source information to a specified path to complete the compilation of the cover template and the corresponding files for each functional structure, realizing the automatic generation of functional specification documents based on the element content of the model. Based on this, this embodiment at least solves the problems of low efficiency and high error rate of manually writing functional specification documents, which helps to improve the writing efficiency of functional specification documents, reduce the risk of design errors, and realize the platformization, customization, flexibility, and intelligence of product research and development design.

[0079] Based on the above embodiments or implementation methods Figure 3 This is a flowchart illustrating another design method for functional specification documents provided in this embodiment of the invention. Figure 8 This is a flowchart illustrating another design method for a functional specification document provided in this embodiment of the invention. This embodiment is based on the above embodiments and includes additional steps. Figure 3 and Figure 8 As shown, the design methodology of this functional specification document includes at least the following steps:

[0080] S1. After the functional model is debugged, decompose the model structure and logical relationship of the functional model to determine the chapter structure of the functional specification document.

[0081] S2. Design the cover template and obtain the data source information for the functional model.

[0082] S3 completes the compilation of cover templates and corresponding functional structures based on data source information and chapter structure.

[0083] S41. Compile all files and store them in a unified folder, and create a new master template file for the design specifications.

[0084] S421. Create a file directory within the overall design specification template file.

[0085] The table of contents can be inserted between the revision history and the preface.

[0086] S422. Use file directories to reference corresponding files through a unified folder to generate functional specification documents.

[0087] In another specific implementation, optionally, Figure 4 This is a sub-flowchart of a design method for a functional specification document provided in an embodiment of the present invention, used to add to and refine step S422, such as... Figure 4 As shown, the sub-processes of the design methodology for this functional specification document include at least the following steps:

[0088] S422-1. Use the file directory to compile the corresponding files through a unified folder and generate the initial functional specification document.

[0089] S422-2, Perform verification tests on the initial functional specification document.

[0090] The verification operation can involve using the Rhapsody tool to export the initial functional specification document as a Word delivery document, and then determining whether the content of the delivery document meets expectations.

[0091] S422-3. If the verification test passes, the initial functional specification document shall be designated as the functional specification document.

[0092] S422-4. If the verification test fails, adjust the initial functional specification document and re-verify the adjusted initial functional specification document.

[0093] Among these adjustments, the changes can include modifying the content, layout, and structure of the initial functional specification document.

[0094] S422-5. At least after the revised initial functional specification document passes the verification test, the revised initial functional specification document shall be determined as the functional specification document.

[0095] In another specific implementation, this embodiment can be executed using the Rhapsody tool. Taking the sunroof control function as an example, the sunroof control function is designed and developed using the Rhapsody tool. The technical solution provided by the above embodiment can be specifically as follows:

[0096] Step 1: Build a model for the sunroof function and perform simulation tests to test the logical feasibility of the designed function and determine the chapter structure of the functional specification document. This determines the functional structure required for editing the functional specification document. The functional structure in this embodiment includes a revision record structure, a preface structure, a functional overview structure, an entry / exit condition structure, a functional interface structure, a bus communication structure, a timing diagram structure, a state diagram structure, a human-machine interface structure, and a performance requirement structure.

[0097] Step 2: Based on the sunroof control function model, design the cover template exported according to the specifications.

[0098] First, design the cover template file and name it "CoverPage". Open the Rhapsody model, import the data source, select the container element in the palette window, and drag the template annotation element from the palette into the container, naming it "CoverPage". Insert a paragraph below the container by selecting the "Paragraph" element from the palette and adding it below the template container. Simultaneously, add the "Table" element to the "Paragraph" section of the template content. The cover template should have one row and one column. Selecting the table allows you to adjust its properties in the template content's properties, including font, border, color, cell border, positioning, and alignment. In the cover template, select white for the border color (color code "FFFFFF") and set the positioning and alignment options to "center" for table alignment. In the template content, select seven "Paragraphs" from the palette and add them to the template in sequence. Next, select a "Container" from the palette and add it to the template. Then add the "Table" element to the container, selecting one row and one column for each cell. Insert "Paragraphs" within the cells and insert "Text" within each paragraph.

[0099] Furthermore, in the roof control function model, the function name is located in the "blocks" tag under "FunctionalAnalysisPkg". Therefore, it is necessary to first filter the Block level to find the location of the corresponding function name in the model. It is determined to be the Package (FunctionalAnalysisPkg) under the first level package under Project, and the second level is RoofControl_Functional under Blocks. The location of the roof control element is: Projects / Project / Packages / Package / Blocks / Block. Find the element at this location in the data source on the left side of Document Studio, add it to the cell of the template content on the right, and then adjust the filter in the cell properties. Use script-based filtering, with "_Functional" as the filter condition, the left operand is the name of the location "name", the right operand is "_Functional", and the operator is "indexOf".

[0100] Further, clicking "Add" will display the filter statements below. Clicking "OK" completes the filtering, and the filtered cell path locations will be displayed. To enter the label within the text of a paragraph, find the label for that level in the data source on the left, drag it from the data source to the text, select "Use as query" in the pop-up window, confirm the context location, and click "OK." Then drag the value under "label" into the text to output it as the value. Finally, insert a new text on the right side of the original text, double-click to edit it as "Functional Requirements Specification," and then adjust the cell properties: set the table alignment to "center" and the border color to white.

[0101] Further, after completing the previous design, insert 16 "segments" sequentially from the selection panel in the template, and insert a "table" in the last segment. The model includes 5 parts: design, proofreading, review, approval, and countersigning. Therefore, a 5-row, 2-column table is selected for design. Adjust the table properties, design the border and cell border color to white FFFFFF, and set the positioning and alignment to center.

[0102] Furthermore, after the table design is completed, the text is inserted into the table cells. Then, the location or level of the package containing the design information in the model is found. The docinfo package of the model stores information such as "Design", "Proofreading", "Review", "Approval", and "Countersigning". Taking "Design" as an example, a filter operation is performed in the cell. The tag in the model is located at the path Projects / Project / Packages / Package / Packages / Package / Tags / Tag. The tag in the data source mode is inserted into the row and filtered. The scripted filter selects "name" as the left operand, "equals" as the operator, and "Design" as the right operand, which is the "name" value of the design package. Similarly, the modified version still has an arrow icon.

[0103] Further, locate the label element under the path Projects / Project / Packages / Packages / Packages / Packages / Tags / Tag, insert it into a cell, and in the pop-up context selection window, select "Use as query" for the corresponding context position. Then, drag the value under the label element in the data source mode into the text field as the output value. The second column of the table contains the content related to the Design value. Therefore, in the original model, locate the element under Projects / Project / Packages / Packages / Packages / Packages / Tags / Tags / Tag, insert the Tag into the second column cell, and filter it using the scripted filter. Select "name" as the left operand, "equals" as the operator, and "Design" as the right operand, which is the "name" value of the design package. Similarly, the modified version still has an arrow icon.

[0104] Finally, drag the value element from the Data Source Tag level into the text and select it as the value. The compilation principle for the other lines is similar to the first line "Design". Simply replace the right operand of the filter with the corresponding name in the model, and drag in 7 to 8 "segments" at the end to fill the blanks in the template.

[0105] Step 3: Based on the sunroof control function model, design the revision record structure exported from the specifications.

[0106] First, design the revision record template, changing the template comments to "Revisionrecord". In the palette, select "Container" and add it to the template content. Then, insert a "Segment" within the container, and then insert a "Table" within the segment. Design the table to have 1 row and 1 column, with white cell borders and a width of 1. Set the table alignment parameter to "center" in the positioning and alignment settings. Next, add text to the table cells, double-click the text content, modify it to "Revision Record", and use the default font "Simultaneous, Small Four".

[0107] Further, add a "container" to the template content, add a "segment" to the container, and then add a "table" to the "segment". Set the pop-up window to 2 rows and 4 columns. Drag "text" into each cell in the first row of the table and edit the text in sequence as: date, version, description, and design. Similarly, add "text" to the cells in the second row. Determine the location of the revision record package in the model, under Projects / Project / Packages / Package / Packages / Package. It needs to be filtered by package name. Drag the "package" path from the data source into the table. The script filter's left operand is "name", the operator is "equals", and the right operand is "RevisionRecord" (the package name).

[0108] In the second row of the table, extract the paths for date, version, description, and design sequentially from the next level of packages in the model. Therefore, the second row needs to be used as the query value after filtering at the previous level. Drag the third-level package from the data source into the second row for querying. Each cell in this row needs to be filtered; the extracted value will differ depending on the tag value in the model. The data source tag path at this level is: Projects / Project / Packages / Package / Packages / Package / Packages / Package / Tags / Tag. The cell scripted filter uses "name" as the left operand, "equal to," and "Date" as the right operand. Drag the value "value" from the label in the data source into the text to extract the date information from the model. Filter the version, description, and design sequentially, using the same method as for "Date," replacing the right operand value with the corresponding "name" to complete the creation of the revisable record structure.

[0109] Step 4: Based on the sunroof control function model, design the preface structure derived from the specifications.

[0110] First, design the preface template, changing the template annotation to "Introduction". The preface design includes four parts: Scope of Application, References, Abbreviations and Terminology, and Illustrations. In the palette, select a "Container" and drag it into the template editor. Simultaneously, drag a "Paragraph" into the "Container", then drag "Text" into the "Paragraph", edit the text to "1. Preface", and save. Right-click the text box and select "Style", setting the heading style to "1". Next, add another "Paragraph" from the palette, add "Text" within the paragraph, edit the text to "1.1 Scope of Application", and set the heading style to "2". Finally, drag a "Paragraph" from the palette into the template content editor, and simultaneously drag "Text" into that "Paragraph".

[0111] Further, locate the storage location of "Application Scope" in the model, and determine the data source path as: Projects / Project / Packages / Package / Packages / Package / Tags / Tag. Drag the Tag from the data source view into the paragraph, and set up scripted filtering in the property editor, using the Tag name "ApplicationScope" as the filter, with "name" as the left operand, "ApplicationScope" as the right operand, and "equals" as the operator. Confirm to complete the filtering. Add the "descriptionText" element from the data source to the "Text" field, select "Use as Value," and confirm. The second subsection is "1.2 Reference Documents." Similarly, select "Paragraph" from the palette and add it to the container. Add "Text" to the "Paragraph," edit the text, and select "Style 2," the same as in section 1.1. Select "Paragraph" from the palette, place the "Table" within the "Paragraph," design it as a 1x2 cell, and add "Text" to each cell. The model's reference document is identified as being located under the `docinfo` package. Therefore, the initial data source path is determined as: Projects / Project / Packages / Package / Packages / Package. Drag the package into the table according to this path. Similarly, a data script filter is needed to filter this data by package level. The left operand is "name", the operator is "equals", and the right operand is changed to "ReferenceDoc". Add a "Package" element for the data source to the "Rows" of the table. The content to be exported by the model is under the third package level. Therefore, add a "Tag" package under the third package level to the cell, and perform script filtering. The first column's "Left Operand" is "name", the operator is "equals", and the right operand is "Number". The second column's "Left Operand" is "name", the operator is "equals", and the right operand is "Filename". Use the value under the Tag as text, dragging it from the left data source into the first column text box of the table. Similarly, the second column is also used as the value, completing the reference document data extraction.

[0112] Further, format the table, setting the color to "FFFFF", white, width to "1", and the border to white around the edges. The third section is Abbreviations and Terminology. Add the "Segment" palette to the template editor, add "Text" to the "Segment" section, edit the text to "1.3 Abbreviations and Terminology", and set the heading style to "Style 2". Select "Segment" from the palette, and then insert a "Table" from the palette. Place the "Table" inside the "Segment", select a 2-row, 2-column table, and ensure the initial position of "Abbreviations and Terminology" in the model is under the second package level, specifically: Projects / Project / Packages / Package / Packages / Package. A scripted filter is needed to lock the element position. Select "Text" from the palette and add it to the "Cells", dragging all four "Cells" in. Write "Abbreviations" in the first column of the first row, and "Description" in the second column. For the second row, determine the element model position. First, find the filtered tags from the data source and drag them into the second row for querying.

[0113] Furthermore, the cell needs to include the name "name" and description "descriptionText" for the next level tag. Enter the values ​​"name_value" and "descriptionText_value" in the text fields respectively. The fourth section is the legend. Select "Segment" from the palette, drag "Text" into the "Segment," and edit the "Text" to "1.4 Legend," applying the title style "Style 2." In the template editor, add "Segments" in sequence, and then add "Legend" within each segment. The legend location in the model is a controlled file, so determine the file location as: Projects / Project / Packages / Package / ControlledFiles / ControlledFile. Drag this file path from the data source. Add the image within the segment. The image's specific path is: Projects / Project / Packages / Package / ControlledFiles / ControlledFile / fileFullPath. Drag it from the data source to the image location to complete the creation of the introduction structure.

[0114] Step 5: Based on the sunroof control function model, design the functional overview structure derived from the specifications.

[0115] First, design the functional overview template, modifying the template comments to "FunctionalOverview". The functional overview is divided into two parts: functional scenarios and activity diagrams. Add a "segment" in the template editor, and add "text" within each segment, editing the text to "2. Functional Overview", and designing the application format style to "Style 1". Continue adding "segments", adding "text" within each segment, and locating the description information of the functional overview from the model. Determine that the element location path of the data source is within the "Block" under the first package level, so add the "Block" path to the "segment". To filter the Block name (name), add a scripted filter with the left operand being "name" and the right operand being "RoofControl_Functional", using the equals operator. Drag the description text under the Block into the text box; find the descriptionText in the data source and drag the text in as the value.

[0116] Further, continue adding "segments" in the template editor. The image described is located in the controlled file of the model. Determine the path in the data source, select it from the data source, and add it to the "segment". In the "segment", add an "image", apply formatting settings to the image, adjust it to "center", and add the image path to the image box. Add another "segment" in the editor, add "text" to the "segment", edit the "text" to "2.1 Functional Scenario", and set the title format to "Style 2". Continue adding "segments", adding "text" within each "segment". Here, the description of the functional scenario is located in the description of the activity diagram in the model. Determine the model's location in the data source as: Projects / Project / Packages / Package / Blocks / Block / Activities / ActivityDiagram, add it to the "segment", and let the text store the description value of the next level. Add another "segment" in the editor, add "text" to the "segment", edit the "text" to "2.2 Activity Diagram", and set the title format to "Style 2". Continue adding "segments," and within each "segment," add an "image." Here, the activity diagram is located within the image of the activity diagram in the model. The specific data source path is: Projects / Project / Packages / Package / Blocks / Block / Activities / ActivityDiagram / Pictures / Picture. Add this to the "segment" editor. Add the image's specific path to the image editor, adjust the image format, and thus complete the construction of the functional overview structure.

[0117] Step 6: Based on the sunroof control function model, design the entry / exit condition structure derived from the specifications.

[0118] First, design the entry / exit condition template, modifying the template comments to "EntryandExitConditions". In the palette, select "Container" and add it to the template editor. Add a "Segment" to the "Container", and then add "Text" to the "Segment". Edit the text "3. Entry / Exit Conditions" and set the title style to "Style 1". Continue adding "Segments" to the template editor, and then adding more "Segments" within them, and finally adding "Text" to each "Segment". Next, determine the location of the entry / exit condition information elements in the model. In the first segment, determine the package level as a sub-package "EntryandExitConditions" under "RequirementsAnalysisPkg". Therefore, select it from the data source schema and add it to the first segment. Simultaneously, perform a scripted filter operation, with the left operand being "name" and the right operand being "EntryandExitConditions", using the "Contains" operator. Further, in the second segment, select the "Requirement" package from the data source schema, and add the specification text "specification" under "Requirement" to the text box as the value. This completes the creation of the entry / exit condition structure.

[0119] Step 7: Based on the sunroof control function model, design the functional interface structure exported from the specifications.

[0120] First, design the functional interface template, and change the template comment to "FunctionalInterface". In the palette, select "Container" and add it to the template editor. Add "Segment" to the container, add "Text" to the segment, edit the text in the text, enter "4 Functional Interface", and set the style to "Style 1".

[0121] Next, select "Segment" from the palette, add an "Image" to the segment, and set the image format to "Image Indent: center". Locate the path to the controlled file in the model; the path corresponding to the data source mode is: Projects / Project / Packages / Package / Block_Definition_Diagrams / Block_Definition_Diagram / ControlledFiles / ControlledFile. The image path is fileFullPath under the controlled file. Drag the two paths from the data source into the paragraph and image respectively. Insert two "Segments" in the template editor. Insert text into the first paragraph, edit the text box, and set the content to "4.1 Interface Description". Design the title style to "Style 2".

[0122] Further, insert a table in the second paragraph, selecting 1 row and 2 columns. Add text to the cells, and set the table properties to autofit to window. Set the cell border color to white with the corresponding color code FFFFF, and select "center" for table alignment. In the model, the description information of the functional interfaces is located in the descriptions of each Block under PhysicalArchitecturePkg. In the first paragraph, filtering needs to be done down to the physical architecture package level. The left operand in the filter is "name", the right operand is "PhysicalArchitecturePkg", and the operator is equal. The rows of the table are used to query the Block level under this package. The content of the first cell in the first row and first column is the title "name", and the second column is the description "descriptionText", also used for querying. The text content is the value of "name" and the value of "descriptionText".

[0123] Further, insert two "segments" sequentially in the template editor. In the first segment, insert text and edit the text box to read "4.2 Connected Sensors / Actuators," with the title style set to "Style 2." In the second segment, insert a table with 2 rows and 2 columns. Add text to the cells, with the first row containing "Sensor / Actuator Name" and "Connected Controller." Set the table properties to autofit to window, black cell borders (color code 000000), and "center" for alignment. In the second segment, filter down to the physical architecture package level. The left operand in the filter should be "name," the right operand "PhysicalArchitecturePkg," and the operator "equals." The content of the second row of the table is similar to that of the "4.1 Interface Description" table, both being Blocks under the first Package. However, the first column of the second row contains Tag values, and the second column contains name values. Select Block, Tag, and name for querying to complete the creation of the functional interface structure.

[0124] Step 8: Based on the sunroof control function model, design the bus communication signal structure derived from the specifications.

[0125] First, design the bus communication signal template, renaming the template annotation to "BusCommunicationSignal". In the palette, select "Container" and add it to the template editor. Add "Segments" to the "Container", and then add "Text" to each "Segment". Edit the text to "5. Bus Communication Signal" and design the style as "Style 1". Next, select two more "Segments". In the first "Segment", insert a text box and edit it to "5.1 High-end and Deluxe Network" with the style "Style 2". Add an "Image" to the second "Segment" and adjust its position to "center". Determine the element's location in the model as: Projects / Project / Packages / Package / Packages / Package / ControlledFiles / ControlledFile. Finally, add the path from the data source to the second segment and the specific location path from the data source image to the image. This completes the creation of the bus communication signal structure.

[0126] Step 9: Based on the sunroof control function model, design the timing diagram structure derived from the specifications.

[0127] First, design a sequence diagram template, renaming the template annotation to "SequenceDiagram". In the palette, select "Container" and add it to the template editor. Insert a "Segment" within the "Container", then insert "Text" within the "Segment", and edit the "Text" to "6. Sequence Diagram". Apply the title style "Style 1". Further, continue selecting "Container" in the palette and adding it to the template editor. Add another "Segment" within the "Container", then another "Segment" within the "Segment", and finally, add an "Image" within the "Segment".

[0128] Further, determine the location of the sequence diagram in the model. The data source path is: Projects / Project / Packages / Package / Packages / Package / SequenceDiagrams / SequenceDiagram. Select the sequence diagram under this path in the data source, drag it into the container, and perform scripted filtering on it. The left operand is "name", the right operand is "SD", and the operator is "start content is".

[0129] Next, insert the Picture from the right-hand data source into the second paragraph. Drag the path under Picture into the image in the template editor. Insert a new "container" into the template editor, and add it to the "container" by selecting "text". Locate the sequence diagram description in the model, and simultaneously determine the path in the data source: Projects / Project / Packages / Package / Packages / Package / SequenceDiagrams / SequenceDiagram / descriptionText. Insert the sequence diagram path into the text, and then insert the description below the text to be used as a value display, thus completing the creation of the sequence diagram structure.

[0130] Step 10: Based on the sunroof control function model, design the state diagram structure derived from the specifications.

[0131] First, design the state diagram template, renaming the template annotation to "StateDiagram". In the palette, select "Container", "Segment", and "Text" and add them to the template editor. Edit the text to "7. State Diagram" and set the text style; the title style is "Style 1". Expand the model and determine the location of the main control ECU's state diagram. In the palette, reselect "Container" and add it to the template editor. Add "Segments" within the "Container", and add "Images" within the "Segments". Further, since the main control ECU's state diagram is located under the first package's Block, select the data source path and add it to the container. A scripted filter is needed, with the left operand being "name", the operator being equal, and the right operand being "Roof", which is the name of the main control ECU to be generated. Add the storage package for the main control ECU's state diagram's image location within the segment, and add the image path within the image. This completes the creation of the state diagram structure.

[0132] Step 11: Based on the sunroof control function model, design the human-machine interface structure derived from the specifications.

[0133] First, design the Human-Machine Interface (HMI) template, modifying the template comments to "HumanMachineInterface". Next, add a "Container" to the palette, then add a "Segment" within the "Container", and then add "Text" within the "Segment". Edit the text content to "8. Human-Machine Interface (HMI)" and apply a title style, setting it to "Style 1". Further, continue adding segments in the editor, adding text within each segment, and editing the text to "TBD". This completes the creation of the HMI structure.

[0134] Step 12: Based on the sunroof control function model, design the performance requirement structure derived from the specifications.

[0135] First, design the performance requirements template, renaming the template comments to "PerformanceRequirements". Add a "Container" to the palette, then add a "Section" within the "Container", and then add "Text" within the "Section". Edit the text to "9. Performance Requirements" and set the title style to "Style 1". Add another "Section" in the editor, and then add "Text" within that section to determine the location of the performance requirements in the model. Next, drag the hierarchy of the second Package from the data source into the "Section", filtering the package name as "PerformanceRequirement", setting the left operand to "name", the right operand to "PerformanceRequirement", and the operator to "equals". Drag the requirement package from the previous level into the text field of the template editor. Finally, add requirement specifications under this text requirement package; these will be used as values ​​to complete the creation of the performance requirements structure.

[0136] Step 13: Save all the completed functional structures and cover designs into a single folder for easy dynamic referencing. For example, consider a cover template design:

[0137] First, design the overall document template. Add a "container" to this template, and within the "container," add a "template comment," editing the comment to "cover." Add another "container" under the "template comment." Use the "container" to select "import template," open a local or remote file, select the locally saved cover template design file, and choose "dynamic reference." This will successfully dynamically reference the cover design's sub-template files. Add the remaining sub-templates to this newly created overall document template and reference them dynamically. Further, insert table of contents information between the revision history and the preface. Add the container from the palette to the template editor, add text in the template editor, and change the text content to "Table of Contents," editing the font to bold. Further, add the table of contents from the left palette to the template editor to complete the table of contents creation. After all sub-templates are dynamically referenced, the overall automatic export of the specification document design can be achieved.

[0138] Step 14: Use Rhapsody to open the sunroof and control the model.

[0139] First, open the Rhapsody tool options, select "Use User-Specified Report to Export Model Functional Specification Document" in the "Publish" section, open the overall template .dta file from step 13 using the Rhapsody report generator, select Word as the exported file report type, and realize the automatic export of the functional specification document corresponding to the model based on the skylight control model.

[0140] Therefore, this embodiment, on the one hand, after the functional model is debugged, decomposes the model structure and logical relationships of the functional model, and converts the model structure and logical relationships into the chapter structure of the functional specification document, thus automatically completing the overall architecture planning of the functional specification document. On the other hand, this embodiment obtains data source information and can store the data source information to a specified path to complete the compilation of the cover template and the corresponding files for each functional structure, realizing the automatic generation of functional specification documents based on the element content of the model. Based on this, this embodiment at least solves the problems of low efficiency and high error rate of manually writing functional specification documents, which helps to improve the writing efficiency of functional specification documents, reduce the risk of design errors, and realize the platformization, customization, flexibility, and intelligence of product research and development design.

[0141] Figure 5 This is a schematic diagram of a design device for a functional specification document provided in an embodiment of the present invention. This embodiment is applicable to at least various functional model functional specification document writing scenarios. The design device for the functional specification document can be implemented in software and / or hardware. Figure 5 As shown, the design apparatus for this functional specification document includes at least:

[0142] Chapter structure module 110 is used to obtain the model structure and logical relationship of the functional model after the functional model debugging is completed, so as to determine the chapter structure of the functional specification document;

[0143] The design acquisition module 120 is used to design the cover template and acquire the data source information of the functional model;

[0144] Document preparation module 130 is used to complete the document preparation corresponding to the cover template and functional structure based on data source information and chapter structure;

[0145] Functional Specification Module 140 is used to generate functional specification documents based on the compilation and chapter structure of all documents.

[0146] Optionally, the document preparation module 130 is specifically used for:

[0147] Based on the chapter structure, determine all the functional structures required for the functional specification document; and extract the element data required for the cover template and each functional structure from the data source information through preset processing methods; and write the element data into the cover template and the template file corresponding to each functional structure; and perform format design on each template file to complete the compilation of the cover template and the document corresponding to the functional structure.

[0148] Optionally, functional specification module 140 is specifically used for:

[0149] All documents are compiled and stored in a unified folder, and a new master template file for design specifications is created. In addition, within the master template file for design specifications, corresponding documents are compiled by referencing the unified folder according to preset rules to generate functional specification documents.

[0150] Optionally, the functional specification module 140 is also specifically used for:

[0151] A file directory is constructed within the overall template file of the design specifications; and the corresponding files are compiled by referencing the file directory through a unified folder to generate functional specification documents.

[0152] Optionally, the functional specification module 140 is also specifically used for:

[0153] The system utilizes a file directory to reference corresponding files in a unified folder to generate an initial functional specification document; performs verification tests on the initial functional specification document; and, if the verification tests pass, confirms the initial functional specification document as the functional specification document.

[0154] Optionally, the functional specification module 140 is also specifically used for:

[0155] If the verification test fails, the initial functional specification document shall be adjusted and the adjusted initial functional specification document shall be re-verified; and, at least after the verification test of the adjusted initial functional specification document passes, the adjusted initial functional specification document shall be determined as the functional specification document.

[0156] Optionally, the functional structure includes at least one of the following: revision record structure, preface structure, functional overview structure, entry / exit condition structure, functional interface structure, bus communication structure, timing diagram structure, state diagram structure, human-machine interface structure, and performance requirement structure.

[0157] The technical solution provided in this embodiment firstly, after the functional model is debugged, obtains the model structure and logical relationships of the functional model through the chapter structure module to determine the chapter structure of the functional specification document. Further, a cover template is designed through the design acquisition module, and the data source information of the functional model is obtained. Further still, the document compilation module completes the document compilation corresponding to the cover template and functional structure based on the data source information and chapter structure. Finally, the functional specification module generates the functional specification document based on all the documents.

[0158] Therefore, this embodiment, on the one hand, after the functional model is debugged, decomposes the model structure and logical relationships of the functional model, and converts the model structure and logical relationships into the chapter structure of the functional specification document, thus automatically completing the overall architecture planning of the functional specification document. On the other hand, this embodiment obtains data source information and can store the data source information to a specified path to complete the compilation of the cover template and the corresponding files for each functional structure, realizing the automatic generation of functional specification documents based on the element content of the model. Based on this, this embodiment at least solves the problems of low efficiency and high error rate of manually writing functional specification documents, which helps to improve the writing efficiency of functional specification documents, reduce the risk of design errors, and realize the platformization, customization, flexibility, and intelligence of product research and development design.

[0159] This embodiment provides an electronic device. Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. See also: Figure 6 The electronic device 1000 includes a processor 1001 and a memory 1002. The memory 1002 stores computer-readable instructions. When the computer-readable instructions are executed by the processor 1001, the steps in the design method of any of the above-mentioned functional specification documents are performed. Through the above technical solution, the processor 1001 and the memory 1002 are interconnected and communicate with each other through a communication bus and / or other forms of connection mechanism (not shown). The memory 1002 stores a computer program that can be executed by the processor. When the electronic device 1000 is running, the processor 1001 executes the computer program to perform the design method of the functional specification document in any of the optional implementations of the above embodiments, so as to at least achieve the following functions: after the functional model is debugged, decompose the model structure and logical relationship of the functional model to determine the chapter structure of the functional specification document; design a cover template and obtain the data source information of the functional model; complete the compilation of the cover template and the corresponding documents of the functional structure based on the data source information and the chapter structure; and generate the functional specification document based on all the documents.

[0160] This embodiment provides a computer-readable storage medium storing a computer program. When executed by a processor, the program implements the design method for functional specification documents as provided in all embodiments of this application: after the functional model is debugged, the model structure and logical relationships of the functional model are decomposed to determine the chapter structure of the functional specification document; a cover template is designed, and the data source information of the functional model is obtained; based on the data source information and chapter structure, the corresponding documents for the cover template and functional structure are compiled; and a functional specification document is generated based on all the documents.

[0161] Any combination of one or more computer-readable media may be used. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.

[0162] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including—but not limited to—electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of transmitting, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0163] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0164] Computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—as well as conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0165] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for designing functional specification documents, characterized in that, At least including: After the functional model is debugged, the model structure and logical relationships of the functional model are decomposed to determine the chapter structure of the functional specification document; Design a cover template and obtain the data source information of the functional model; Based on the data source information and the chapter structure, complete the document compilation corresponding to the cover template and functional structure; Based on all the aforementioned documents, a functional specification document was compiled and generated.

2. The design method for functional specification documents according to claim 1, characterized in that, The process of creating the cover template and corresponding functional structure documents based on the data source information and the chapter structure specifically includes: Based on the aforementioned chapter structure, determine all the functional structures required for the functional specification document; Extract the cover template and element data required for each functional structure from the data source information using a preset processing method; Write the element data into the cover template and the template file corresponding to each of the functional structures; Format design is performed on each template file to complete the compilation of the cover template and the corresponding documents for the functional structure.

3. The design method for functional specification documents according to claim 1, characterized in that, The process of compiling and generating a functional specification document based on all the aforementioned documents specifically includes: All the aforementioned documents should be compiled and stored in a unified folder, and a new master template file for design specifications should be created. The functional specification document is generated by referencing the corresponding files in the unified folder within the master template file of the design specifications, according to preset rules.

4. The design method for functional specification documents according to claim 3, characterized in that, The process of compiling the functional specification document within the overall design specification template file, according to preset rules and referencing the corresponding files through the unified folder, specifically includes: Create a file directory within the master template file of the design specifications; The functional specification document is generated by using the file directory and referencing the corresponding files through the unified folder.

5. The design method for functional specification documents according to claim 4, characterized in that, The process of using the file directory to reference the corresponding files through the unified folder to generate the functional specification document specifically includes: Using the file directory and referencing the corresponding files through the unified folder, an initial functional specification document is generated. Perform verification tests on the initial functional specification document; If the verification test passes, the initial functional specification document will be identified as the functional specification document.

6. The design method for functional specification documents according to claim 5, characterized in that, After performing verification testing on the initial functional specification document, the method further includes: If the verification test fails, the initial functional specification document shall be adjusted and the adjusted initial functional specification document shall be re-verified. At least after the revised initial functional specification document passes the verification test, the revised initial functional specification document will be determined as the functional specification document.

7. The design method for functional specification documents according to claim 1, characterized in that, The functional structure includes at least one of the following: revision record structure, preface structure, functional overview structure, entry / exit condition structure, functional interface structure, bus communication structure, timing diagram structure, state diagram structure, human-machine interface structure, and performance requirement structure.

8. A design apparatus for functional specification documents, characterized in that, At least including: The chapter structure module is used to obtain the model structure and logical relationships of the functional model after the functional model debugging is completed, so as to determine the chapter structure of the functional specification document; The design acquisition module is used to design the cover template and acquire the data source information of the functional model; The document compilation module is used to complete the document compilation corresponding to the cover template and functional structure based on the data source information and the chapter structure. The functional specification module is used to compile and generate functional specification documents based on all the aforementioned documents.

9. An electronic device comprising a memory and a processor, the memory storing a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the steps in the design method of the functional specification document according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps in the design method of the functional specification document according to any one of claims 1 to 7.

Images