{"title":"Review of \"SEMINAR: Structured Requirements Definition, from Ken Orr & Associates.\"","authors":"J. Sitek","doi":"10.1145/1017726.1017732","DOIUrl":null,"url":null,"abstract":"The Ken Orr seminar dealing with Structured Requirements Definition is one which strives to teach the participan t a unique way from the traditional approach systems development . Emphasis is placed on viewing a system from th e required OUTPUTS so that the analyst can understand from the beginning of the study precisely what the system i s supposed to do . A strong case is made for the necessity t o rethink traditional approaches; that discussion is followed by the presentation of the tool of the Warnier/Orr diagra m to accomplish the systems task . This is accomplished in fou r heavily packed days of the combination seminar and work shop format . The seminar is held at various location s around the country and is also available for in-house presentation . The seminar is structured on providing the ground rule s for \"Outthinking,\" and then explaining the necessary tool s with which to accomplish the thinking task . The methodology is based on the traditional structured approach usin g hierarchy, repetition, alternation, and sequence of event s identification and isolation. However, in the process, the analyst begins by looking at the desired output of a system (subsystem) and then decomposes (via Warnier/ Orr diagrams) the components that make up the entity to find th e input requirements . Thus, the output goes to the input in th e process of design . The processing requirements are identified as a natural process of the decomposition . The Orr system tools include: entity diagrams, assembly line diagrams, in-out diagrams, Warnier/Orr diagrams , data dictionary, and logic diagrams . The major problem with the seminar, which is true for many intensive instructional workshops, is the lack of time to adequately develo p an in-depth understanding to both the Orr approach t o requirements definition and all the supporting tools . While this is the beginning seminar, the concepts should be used i n the systems environment on a trial basis with additiona l seminars for depth . Additional seminars are available whic h focus on teaching the tools required to support the methodology. The need for the analyst to be exposed to alternate ways of systems development makes the seminar one wort h attending.","PeriodicalId":152518,"journal":{"name":"ACM Sigmis Database","volume":"78 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1984-07-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"ACM Sigmis Database","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/1017726.1017732","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
Abstract
The Ken Orr seminar dealing with Structured Requirements Definition is one which strives to teach the participan t a unique way from the traditional approach systems development . Emphasis is placed on viewing a system from th e required OUTPUTS so that the analyst can understand from the beginning of the study precisely what the system i s supposed to do . A strong case is made for the necessity t o rethink traditional approaches; that discussion is followed by the presentation of the tool of the Warnier/Orr diagra m to accomplish the systems task . This is accomplished in fou r heavily packed days of the combination seminar and work shop format . The seminar is held at various location s around the country and is also available for in-house presentation . The seminar is structured on providing the ground rule s for "Outthinking," and then explaining the necessary tool s with which to accomplish the thinking task . The methodology is based on the traditional structured approach usin g hierarchy, repetition, alternation, and sequence of event s identification and isolation. However, in the process, the analyst begins by looking at the desired output of a system (subsystem) and then decomposes (via Warnier/ Orr diagrams) the components that make up the entity to find th e input requirements . Thus, the output goes to the input in th e process of design . The processing requirements are identified as a natural process of the decomposition . The Orr system tools include: entity diagrams, assembly line diagrams, in-out diagrams, Warnier/Orr diagrams , data dictionary, and logic diagrams . The major problem with the seminar, which is true for many intensive instructional workshops, is the lack of time to adequately develo p an in-depth understanding to both the Orr approach t o requirements definition and all the supporting tools . While this is the beginning seminar, the concepts should be used i n the systems environment on a trial basis with additiona l seminars for depth . Additional seminars are available whic h focus on teaching the tools required to support the methodology. The need for the analyst to be exposed to alternate ways of systems development makes the seminar one wort h attending.
Ken Orr处理结构化需求定义的研讨会努力向参与者传授一种不同于传统系统开发方法的独特方法。重点放在从所需的输出中查看系统,以便分析人员可以从研究的开始就准确地理解系统应该做什么。有充分理由表明,有必要重新考虑传统方法;讨论之后是瓦尼耶/奥尔图工具的展示,以完成系统任务。这是在四天繁忙的研讨会和工作车间的形式完成的。研讨会在全国各地的不同地点举行,也可在内部进行演示。研讨会的结构是提供“超越思考”的基本规则,然后解释完成思考任务所需的工具。该方法基于传统的结构化方法,使用层次结构、重复、交替和事件识别和隔离的顺序。然而,在此过程中,分析人员首先查看系统(子系统)的期望输出,然后分解(通过Warnier/ Orr图)组成实体的组件,以找到输入需求。因此,在设计过程中,输出变成了输入。处理需求被确定为分解的自然过程。Orr系统工具包括:实体图、装配线图、输入-输出图、Warnier/Orr图、数据字典和逻辑图。研讨会的主要问题是缺乏足够的时间来深入了解Orr方法对需求定义和所有支持工具的理解,这对于许多密集的教学研讨会来说也是如此。虽然这是开始的研讨会,但应该在系统环境中试用这些概念,并进行更多的深入研讨会。另外还有一些研讨会,重点讲授支持该方法所需的工具。分析人员需要了解系统开发的备选方法,因此值得参加这个研讨会。