教程說明庫卡

1、KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specificationUser expectations as basis for program planning:What does the program do?What inputs does the program require?What outputs does

2、 the program supply?How must the program be operated?How does the program react to a fault/malfunction?Operator specification or requirements specificationKUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning

3、- Requirements specificationDefinition:Requirements specificationA requirements specification is the organizational and technical specification for program creation.KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and

4、 planning - Requirements specificationAdvantages of a requirements specification: Description of the application Definitions of inputs/outputs/parameters and program sequences Transparent breakdown Project familiarization significantly easierKUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.:

5、 +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specificationCreating a requirements specification:Outline sequence descriptionSub-sequence descriptionDetailed sequence descriptionOutline sequence descriptionSub-sequence descriptionDetailed seque

6、nce descriptionKUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specification1. Outline sequence description:Representation of the entire concept covered by the requirements specification.T

7、he ratio of text to diagrams should be roughly 90% diagrams to 10% text. Preferably, text should be avoided altogether. Where possible, the following should be taken into consideration:Managers do not have thumbs!People without thumbs cannot leaf through thick documents.For this reason, no more than

8、 one page for the outline sequence description.KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specification2. Sub-sequence description:Detailed representation of the information contained

9、 in the outline sequence description.The outline sequence description only skims very superficially over the individual sub-sequences. For this reason, the representation of the sub-sequences must go into much greater detail. It is important here to maintain the link with the outline sequence descri

10、ption. It must be possible to identify each sub-sequence from the outline sequence description.KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specification3. Detailed sequence description

11、:Detailed representation of the procedures and sequences covered by the requirements specification.The detailed sequence description constitutes the major section of the requirements specification. The outline and sub-sequence descriptions merely provide an overview of the sequences. The amount of p

12、reparation that goes into the detailed sequence description is decisive in determining the quality of the program implementation. KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specificat

13、ionSubdivision of more complex tasks: Outline sequence descriptionSub-sequence ASub-sequence BSub-sequence CDetailed description ADetailed description BDetailed description CVisualization of a complex detailKUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (

14、0) 8 21/7 97-412340, Conceptualization and planning - Requirements specificationStructure of the requirements specification What is it all about?In the interests of standardization and better organization of the documentation, all requirements specifications should have the same structure. The follo

15、wing structure has proved its worth in our work.What are the advantages?In the case of a second project, the customer recognizes the structure of the first requirements specification and can familiarize himself with the document more quickly. When working on new projects, the author of the requireme

16、nts specification can refer quickly to information from old projects. This can significantly reduce the effort involved in working out solutions for similar problems. KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Cover Table of cont

17、ents Meetings relating to this project Unresolved issues Glossary Initial situation Objective Technical requirements/descriptionConceptualization and planning - Requirements specificationStructure of a requirements specification:In the interests of standardization and better organization of the docu

18、mentation, all requirements specifications should have the same structure. The following structure has proved its worth:KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specificationCompone

19、nts: CoverWhat is it all about?The job of the cover is to convey information about the origins and contents of the requirements specification at a glance. What are the advantages?The cover of a requirements specification is essentially the first part of the business card of the company producing thi

20、s document. A good impression on the very first page never does any harm.KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specificationComponents: CoverThe following information should be i

21、ncluded on the cover:Logo:If the company has a logo, it should appear here.Company:Name and address of the company.Name of the project: A short and concise description of the project.Version :Version of the requirements specification.Short description:Brief sentence, if applicable, explaining the ti

22、tle of the project.Created by:Name of the author(s) of the requirements specification.Contact details:Telephone number and/or e-mail address.Date:Date of the last time the document was saved.Copyright details: All rights reserved.KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 2

23、1/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specificationComponents: ContentsWhat is it all about?The contents page should provide a brief overview of the topics covered in the document. What are the advantages?The contents page helps the reader to find

24、the corresponding topic quickly. For this reason, every requirements specification should have a contents page. Avoid having too many heading levels in the contents page. A contents page with a maximum of three or four heading levels should be sufficient even for large projects. Further subdivision

25、can then be carried out in the document itself. KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specificationComponents: Meetings relating to this projectWhat is it all about?A requirement

26、s specification gradually evolves over a period of time. Various meetings will thus be necessary to work out all aspects of the topic(s) covered. The meetings that were held while working on this requirements specification are recorded in the following table. What are the advantages?Listing all the

27、meetings is a useful way of recording how often meetings were held in conjunction with this requirements specification. The list of dates makes it possible to determine the intervals between the meetings and who was present. It is helpful if a highlight of the discussion is listed for each date (thi

28、s is useful when trying to remember what was discussed when).KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specificationComponents: Meetings relating to this projectSuggested layout:.Her

29、r Schneider Muster GmbHHerr Lehmann Muster GmbHHerr Maier KUKA RoboterSmith & Co.Room M1010:00-13:00 13.03.1999Project kick-off meetingPresentLocationTimeMeeting onKUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and

30、planning - Requirements specificationComponents: Unresolved issuesWhat is it all about?When working on a requirements specification, issues may arise which need to be discussed in greater detail at a later date. Throughout the time work is in progress on the requirements specification, a list should

31、 be kept of these unresolved issues so that they are not forgotten. What are the advantages?Keeping a list of unresolved issues while creating requirements specifications has proved to be a valuable exercise in many respects, as topics requiring further clarification are recorded here during complet

32、ion of the documentation. These could be design issues, for example, which arose at a time when this topic was not yet due for discussion.KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements sp

33、ecificationComponents: Glossary (if required)What is it all about?Requirements specifications mainly deal with highly technical issues. For this reason, a glossary must be created in order to enable all those involved in the project to understand the terms used in the requirements specification. Wha

34、t are the advantages?The glossary helps to prevent misunderstandings. It should be positioned at the start, and not the end, of the requirements specification. In this way, even those who were not involved in collating the information can see at once that specific terms refer to specific concepts. T

35、his is useful for the correct interpretation of the descriptions on the following pages. KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and planning - Requirements specificationComponents: Initial situationWhat is i

36、t all about?At the start of each requirements specification there should be a brief description of the initial situation. By this, the considerations at the time of starting the requirements specification are meant. It is a brief representation of the current situation with a view to the desired fut

37、ure situation. The description of the initial situation should answer the following questions:What is the situation now?Wo has initiated the drafting of this requirements specification?What are the advantages?The description of the initial situation is useful for understanding the reason(s) behind t

38、he drafting of the requirements specification. The description of the initial situation also provides a complete picture for the whole requirements specification. KUKA Roboter GmbH, Blcherstr. 144, D-86165 Augsburg, Tel.: +49 (0) 8 21/7 97-1906, Fax: +49 (0) 8 21/7 97-412340, Conceptualization and p

39、lanning - Requirements specificationComponents: ObjectiveWhat is it all about?The following question arises when formulating the task and objective:What is to be achieved and how?The basis for this part of the requirements specification is the customer request. The customer request provides the author of the requirements specification with fixed general requirements which are binding f