Academic literature on the topic 'Requirements specification templates'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Requirements specification templates.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Journal articles on the topic "Requirements specification templates"
1
Vallejo, Paola, Raul Mazo, Carlos Jaramillo, and Jhon Medina Medina. "Towards a new template for the specification of requirements in semi-structured natural language." Journal of Software Engineering Research and Development 8 (February 4, 2020): 3. http://dx.doi.org/10.5753/jserd.2020.473.
Full textAbstract:
Requirements engineering is a systematic and disciplined approach for the specification and management of software requirements; one of its objectives is to transform the requirements of the stakeholders into formal spec-ifications in order to analyze and implement a system. These requirements are usually expressed and articulated in natural language, this due to the universality and facility that natural language presents for communicating them. To facilitate the transformation processes and to improve the quality of the resulting requirements, several authors have proposed templates for writing requirements in structured natural language. However, these templates do not allow writing certain functional requirements, non-functional requirements and constraints, and they do not adapt correctly to certain types of systems such as self-adaptive, product line-based and embedded systems. This paper (i) presents evidence of the weaknesses of the template recommended by the IREB® (International Requirements Engineering Institute), and (ii) lays the foundations, through a new template, for facilitating the work of the re-quirements engineers and therefore improving the quality of the products specified with the new template. This new template was built and evaluated through two active research cycles. In each cycle we identified the problems specifying the requirements of the corresponding industrial case with the corresponding base-line template, pro-pose some improvements to address these problems and analyze the results of using the new template to specify the requirements of each case. Thus, the resulting template was able to correctly write all requirements of both industrial cases. Despite the promising results of this new template, it is still preliminary work regarding its cov-erage and the quality level of the requirements that can be written with it.
2
Dobrkovikj Shotarovska, Milena, Hristina Babunovska, and Aneta Dimitrovska. "Data integrity aspects of reporting results for the specification parameter related and degradation products in chromatography data system." Macedonian Pharmaceutical Bulletin 64, no. 01 (2018): 11–23. http://dx.doi.org/10.33320/maced.pharm.bull.2018.64.01.002.
Full textAbstract:
The most convenient way to implement the requirements of Good Manufacturing Practice and the data integrity principles in a control analytical laboratory is to automate the entire analytical process as fully as possible. Obtaining a final reliable result from an analytical testing as part of a formal analysis is one segment of the process of providing Good Manufacturing Practice. In this paper, we describe the steps by which one control analytical laboratory can formalize and automate the entire process of obtaining and issuing analytical results through creating Report Template for calculation of the specification parameter Related and Degradation Products as part of a Chromatography Data System. The process is described in several steps from designing and structuring of the report so that it would respond best to the end-user's requirements, through identifying eventual oversights in the creation phase, to the final phase of validation, which once again confirms the integrity of its content and justifies its use for formal analysis. The use of such validated Report Templates for calculation and reporting of the results from analytical testing eliminates the human error factor and increases the confidence in the issued results as well as in the entire laboratory’s workflow. Their application facilitate compliance with regulations and minimizes manual input of data which in turn meets one of the most crucial requirements of Good Manufacturing Practice. Keywords: data integrity, chromatography data system, report template, related and degradation products
3
Mohd, Haslina, Fauziah Baharom, Norida Muhd Darus, Shafinah Farvin Packeer Mohamed, Zaharin Marzuki, and Muhammad Afdhal Muhammad Robie. "Functional Requirements Specification of E-Tendering Using Natural Language Approach: Towards Innovative Business Transformation." Journal of Computational and Theoretical Nanoscience 16, no. 12 (December 1, 2019): 5003–7. http://dx.doi.org/10.1166/jctn.2019.8555.
Full textAbstract:
Recently, business transformation towards the used of Information and Communication Technology (ICT) is a necessity toward rapid industries and the paradigm shifted to sustain business competitiveness. The holistic electronic approach is one of business innovations, especially in handling a lot of tender documentations and process in an electronic environment namely as e-Tendering. Unfortunately, the existing tender process transformation in the electronic approach is not properly followed certain standard and guideline, especially in establishing a good e-Tendering functional requirements specification to ensure the organizations would be in the best served. This is important to ensure a good e-Tendering system can be developed by e-Tendering developers based on a good e-Tendering functional requirement specifications. The requirements specification is a process of documenting user and system requirements. Commonly, user and system requirements should be clear, unambiguous, easy to understand, complete, and consistent. In practice, this is difficult to achieve due to interpretation of the requirements in different ways by stakeholders, which are often inherent conflicts and inconsistencies of the requirements. The implementation of the existing e-tendering still remains uncertainties, especially in defining the functional requirements of the e-tendering system. Therefore, this study aims to construct the e-Tendering functional requirement model using requirement template in natural language representation approach. Moreover the development of this system requirement model may provide a consistency to the requirements representation. The study uses UN/CEFACT Business Standard of the e-Tendering Business. The identified functional requirements are designed by using Requirement Template to ensure the reliability and understandability of requirements. Besides, the proposed functional requirements is constructed by adapting the natural language and verified by expert review approaches. As a result, this study proposed a functional requirements specification of the e-Tendering that contains detailed description which can be referred by software practitioners in developing a secure e-tendering system effectively.
4
Thronesbery, Carroll, Ayman Qaddumi, Michael Merta, Eugene McMahon, and Mike Monahan. "Autonomy Requirements Tester (ART): Assisting Clear Communications among Stakeholders." Proceedings of the Human Factors and Ergonomics Society Annual Meeting 61, no. 1 (September 2017): 2027–31. http://dx.doi.org/10.1177/1541931213601985.
Full textAbstract:
Autonomy Requirements Tester (ART) is a software tool designed and prototyped in a NASA Phase I Small Business Innovative Research (SBIR) project to address the difficulties of testing autonomy requirements. It supports clear communications among engineers with different by translating requirements terms into software behavioral expectations, which can be used to drive test specifications and the reporting of test results. Also, because it helps translate the requirements into software behavior terms, it addresses some of the difficulties of testing autonomy requirements. Innovations in ART include a clear linking of requirements, expected software behavior, test plans, and test results. They also include the immersion of the Test Runner portion of the ART design within the Core Flight System (cFS) architecture, so that the application under test can be tested as it is intended to fly, even before the remainder of the flight software has been developed. ART also includes a reusable test specification for regression testing and employs a test plan template to ease the specification of multiple, detailed test plans for similarly formatted autonomy requirements.
5
Kumar Nayak, Sandeep, Dr Raees Ahmad Khan, and Dr Md.Rizwan Beg. "A Comparative Template for Reliable Requirement Specification." International Journal of Computer Applications 14, no. 2 (January 12, 2011): 27–30. http://dx.doi.org/10.5120/1815-2361.
Full text
6
Daniel, Mworia, Nderu Lawrence, and Kimwele Michael. "Embedding Quality into Software Product Line Variability Artifacts." International Journal of Software Engineering & Applications 12, no. 3 (May 31, 2021): 11–25. http://dx.doi.org/10.5121/ijsea.2021.12302.
Full textAbstract:
The success of any software product line development project is closely tied to its domain variability management. Whereas a lot of effort has been put into functional variability management by the SPL community, non-functional variability is considered implicit. The result has been dissatisfaction among clients due to resultant poor quality systems. This work presents an integrated requirement specification template for quality and functional requirements at software product line variation points. The implementation of this approach at the analytical description phase increases the visibility of quality requirements obliging developers to implement them. The approach proposes the use of decision tree classification techniques to support the weaving of functional quality attributes at respective variation points. This work, therefore, promotes software product line variability management objectives by proposing new functional quality artifacts during requirements specification phase. The approach is illustrated with an exemplar mobile phone family data storage requirements case study.
7
Kim, DaeSeung. "A Suggestion on a Better Template for Requirements Traceability Matrix of a Requirements Specification." Journal of the Korea Society of Systems Engineering 12, no. 1 (June 30, 2016): 1–5. http://dx.doi.org/10.14248/jkosse.2016.12.1.001.
Full text
8
Alani, Yasir, Nashwan Dawood, João Patacas, Sergio Rodriguez, and Huda Dawood. "A semantic common model for product data in the water industry." Journal of Information Technology in Construction 26 (July 28, 2021): 566–90. http://dx.doi.org/10.36680/j.itcon.2021.030.
Full textAbstract:
The issue of interoperability in the Architecture, Engineering, and Construction (AEC) industry represents a challenge on a scale that spans across the project life cycle. This is predominant in the infrastructure sector that usually comprises a more versatile Operations and Maintenance (O&M) phase in comparison with the buildings sector. To this end, an important stage in the information life cycle is the asset information capture and validation during product procurement at the O&M phase. The water industry in the United Kingdom relies on Product Data Templates (PDTs) to fulfil such task, which is usually an error prone manual process. This paper presents an ongoing research, which investigates the application of Semantic Web Technologies (SWT) for improving product data exchange during product procurement at the O&M phase for the water industry in the United Kingdom (UK). Therefore, focus group sessions with industry experts were held to discuss current inefficiencies and solution requirements. Based on these results, a semantic common model named Asset Specification Ontology (ASO) was developed to capture and validate asset information during product procurement at the O&M phase. The common model (ontology) is based on available technologies, namely Web Ontology Language (OWL) and Shapes Constraint Language (SHACL). This gives the advantage of semantically rich data which can be linked and queried in a meaningful way to facilitate the exchange and validation of water industry assets’ data. The uniqueness of this paper is manifested in the issue it tackles, as efficient product procurement, and hence, data exchange in the water industry is an industrial challenge that is seldom researched. Results from the focus group sessions showed that information exchange within the UK water industry is impeded due to the lack of structured and semantic data. However, for a robust semantic interoperability, there needs to be a robust semantic data infrastructure, which would require semantic mappings from standards to product properties, from standards to other standards, and from standards to dictionaries. These conclusions were further supported by the common model, which was created from existing schemas, standards, and dictionaries. Generally, this paper recommends a common model/product library for phase-specific product data exchange in the water industry.
9
Lu, Xin. "Elastic Fabric Template of Sheath Dress Based on Dynamic Change." Advanced Materials Research 156-157 (October 2010): 1165–69. http://dx.doi.org/10.4028/www.scientific.net/amr.156-157.1165.
Full textAbstract:
The basic theoretical research on sheath dress pattern with elastic fabric has put forward higher requirements. In this paper, based on dressing in dynamic change, combining with the body extend measure, the change of the pattern's control parts' specification and detail parts' specification are studied, and a basic sheath dress pattern with elastic fabric based on dynamic change is established. The human body's dynamic and static data show that the parameter of detail parts specification has great changes, while the parameter of control parts' specification parameter has small changes. For body detail parts' specification and structure, the parts that have not great changes only solve the problem of the fabric elastic utilization to meet the needs of the state of tight dress. According to the positions that produce dynamic increment, combining wearing condition, fabric elastic utilization and dynamic parameter, to design detail specification and pattern to satisfy sheath condition and dynamic demand.
10
He, Dong Qing, and Wei Hua Wu. "Exterior-Template Design for Concrete Engineering in an Arched Structure." Advanced Materials Research 919-921 (April 2014): 284–87. http://dx.doi.org/10.4028/www.scientific.net/amr.919-921.284.
Full textAbstract:
In accordance with the technical specifications of existing concrete structure construction template and an arched structure concrete pouring process, the exterior-template design for concrete of the project has been done, which contents the requirements of the of engineering concrete on construction quality.
Dissertations / Theses on the topic "Requirements specification templates"
1
Morkevičius, Albertas. "Reikalavimų specifikavimo šablonais modelis ir jo programinis prototipas." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2014. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2008~D_20140623_182827-23893.
Full textAbstract:
Darbe pristatomas reikalavimų specifikavimo šablonais modelis. Aptariama aukštos kokybės reikalavimų proceso nauda kuriamoms sistemoms. Pateikiami išanalizuotų reikalavimų specifikacijos dokumento standartų ir reikalavimų inžinerijos programinių įrankių detalios analizės rezultatai. Pristatoma koncepcija geriau užtikrinanti reikalavimų identifikavimo ir specifikavimo kokybę - sumodeliuotas reikalavimų specifikacijos modelis, panaudojantis Volere reikalavimų surinkimo šabloną, pritaikant reikalavimų specifikavimo programinės įrangos įrankį Telelogic Doors. Sukurto prototipo pagalba, sistema automatizuoja reikalavimų surinkimo procesą, sumažindama 30 % vartotojo veiksmų, taip sudarydama didesnį vartotojo darbo našumą ir efektyvumą reikalavimų specifikavimo procese.The main object of this thesis is to analyze requirements specification templates and requirements management tools and realize model prototype using requirements specification templates. There are analyze of requirements templates and requirements managing tools results in considering about a gain of high quality requirements process. To introduce a conception witch supports clearly requirement specification process – the model of Volere requirements specification template adopting Telelogic Doors requirements managing tool. Model realized in Doors using DXL - Doors eXtension Language. Created prototype reduce 30% of users activities and lets user to get more efficiency and productivity in requirements specification process.
2
Del, Gobbo Diego. "Formal specification of requirements for analytical redundancy based fault tolerant flight control systems." Morgantown, W. Va. : [West Virginia University Libraries], 2000. http://etd.wvu.edu/templates/showETD.cfm?recnum=1629.
Full textAbstract:
Thesis (Ph. D.)--West Virginia University, 2000.Title from document title page. Document formatted into pages; contains ix, 185 p. : ill. Includes abstract. Includes bibliographical references (p. 87-91).
3
Zeller, Martin, and Eric Hultgren. "Standardizing Requirements Specification for IT Sourcing." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-203253.
Full textAbstract:
This thesis considers standardizing service requirement specification for IT sourcing. The potential benefits a standardization of service requirements writing combined with Scania IT:s developing strategy have created a need for an investigation about how requirements standardization for IT sourcing could be done. This thesis is built upon three different approaches, requirements engineering, service oriented requirement engineering and best practices. Combined, these different approaches comprise the theory model RSB that will be used in the requirements standardization work. The strategies for collecting data, the authors choose embedded case study. The main problem at Scania IT regarding requirements specification in sourcing is the absence of a standard. The service requirements specifications varies in quality and execution, which causes communication problems. In order to standardize the requirements specification, the authors of this thesis have developed a standardization model consisting of three phases. A template is developed and presented in this thesis, the template is also included in the standardization phases model. The template created in this thesis, based on the RSB-model combined with the empirics, shows how a standard template can be designed. This study also suggests a three-phase model for working with standardization in the future. The standardization model suggest a requirements management software connected to a database.
4
Mazo, Michail. "Reikalavimų specifikavimo pasinaudojant šablonais tyrimas." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2006. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2006~D_20060120_094149-12824.
Full textAbstract:
This work is dedicated to the requierements specification process automation issues. Main goal of the paper is to specify a conceptual model of the multy-user software requirements specification system and create a working prototype of this model.
Analysis part of the work focuses on requirement specification templates and existing requirements specification software investigation. A detailed analysis of most popular templates Volere and IEEE STD 830-1998 is followed by existing software requirements specification software analysis : AnalystPRO and RequisitePRO.
Requirements and tasks for the system prototype are raised on the basis of main features and weknesses of analysed requirements specification templates and software.
This work presents a complete conceptual model of the software requirements specification automation. System model is based on the Volere template. Main features of the system prototype are as follows: complete independence from operating system and working environment, no any client software installation is needed, server part does not require any special components installation and is based on popular free software: Apache and MySQL Servers. System architecture is based on JAVA Applets technology.
Working prototype is an implementation of main system protoype features. This is a multy-user software requirements specification environment with all main collaboration fetures: version control, document locking, presence awareness.
Usability of system... [to full text]
5
Zinkevičius, Egidijus. "Reikalavimų specifikavimo šablonų pagrindu analizė ir programinis prototipas." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2009. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2009~D_20090304_101348-17144.
Full textAbstract:
Reikalavimų inžinerija yra bene svarbiausias etapas informacinės sistemos kūrime. Tik tikslus reikalavimų specifikavimo proceso valdymas leis sėkmingai projektuoti, realizuoti ir įdiegti informacines sistemas kompiuterizuojamose srityse. Dažnai neefektyvus reikalavimų rinkimo procesas tampa projekto nesėkmės ar programinės įrangos defekto pagrindu. Be to, aptiktų netikslumų pašalinimo kaina kyla eksponentiškai, kai jie atrandami vėlyvosiose projekto stadijose. Todėl įmonės ar asmenys, siekiantys pagerinti projekto kokybę ir produktyvumą, turėtų ypatingai atkreipti dėmesį į reikalavimų valdymo procesą. Pastebėta, jog reikalavimų specifikavimo procesas vis labiau kompiuterizuojamas, o reikalavimų valdymo įrankių bei šablonų naudojimas gerina reikalavimų specifikacijos ir būsimo produkto kokybę. Šis magistrinis darbas yra skirtas reikalavimų specifikavimo šablonų pagrindu eksperimentiniam tyrimui ir jo vertinimui.The usage of computers takes more important place in our modern life. It was noticed that more and more enterprises use requirement management tools and specification templates to increase quality of requirement specification and projects. Very often ineffective requirements-gathering processes are the source of project failures and software defects. In addition, the cost of fixing defects rises exponentially as their discovery occurs later in the development process. However, a solid requirements process is fundamental to an effective overall process, and companies seeking increased quality and productivity should start with the requirements process. The intention of this work is to make the experimental research of requirements specification using templates and evaluate it.
6
Irfan, Zeeshan. "Generating Formal Representations of System Specification from Natural Language Requirements." 2019. https://monarch.qucosa.de/id/qucosa%3A72329.
Full textAbstract:
Natural Language (NL) requirements play a significant role in specifying the system design, implementation and testing processes. Nevertheless, NL requirements are generally syntactically ambiguous and semantically inconsistent. Issues with NL
requirements can result into inaccurate and preposterous system design, implementation and testing. Moreover, informal nature of NL is a major hurdle in machine processing of system requirements specifications. To confront this problem, a requirement
template is introduced, based on controlled NL to produce deterministic and consistent representation of the system. The ultimate focus of this thesis is to generate test cases from system specifications driven from requirements communicated
in natural language. Manual software systems testing is a labour intensive, error prone and high cost activity. Traditionally, model-driven test generation approaches are employed for automated testing. However, system models are created
manually for test generation. The test cases generated from system models are not generally deterministic and traceable with individual requirements. This thesis proposes an approach for software system testing based on template-driven
requirements. This systematic approach is applied on the requirements elicited from system stakeholders. For this purpose natural language processing (NLP) methods are used. Using NLP approaches, useful information is extracted from controlled NL
requirements and afterwards the gathered information is processed to generate test scenarios. Our inceptive observation exhibits that this method provides remarkable gains in terms of reducing the cost, time and complexity of requirements based testing.
Book chapters on the topic "Requirements specification templates"
1
Komssi, Marko, Marjo Kauppinen, Kimmo Toro, Raimo Soikkeli, and Eero Uusitalo. "Lessons Learned from Integrating Specification Templates, Collaborative Workshops, and Peer Reviews." In Requirements Engineering: Foundation for Software Quality, 158–72. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-14192-8_16.
Full text
2
Wang, Hao, Yihai Chen, Ridha Khedri, and Alan Wassyng. "Envisioning a Requirements Specification Template for Medical Device Software." In Product-Focused Software Process Improvement, 209–23. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-13835-0_15.
Full text
3
"Template K: Requirements Specification Document." In Implementing Digital Forensic Readiness, 327–34. Elsevier, 2016. http://dx.doi.org/10.1016/b978-0-12-804454-4.15022-1.
Full text
4
Asprey, Len, and Michael Middleton. "Package Selection." In Integrative Document and Content Management, 432–60. IGI Global, 2003. http://dx.doi.org/10.4018/978-1-59140-055-4.ch020.
Full textAbstract:
This chapter covers the typical procurement processes for selecting an IDCM solution and contains useful techniques for validating various solutions against requirements and negotiating a contract with a supplier. Our objectives for this chapter are as follows: • Discuss the requirements for developing a procurement (or contract) strategy and review the various procurement options that enterprises might use to select an IDCM solution. • Discuss the requirement for an Evaluation Strategy as a methodology for reviewing proposals from suppliers, and provide an example Evaluation Plan template. • Discuss the benefits of conducting a Benchmark Assessment as a method of helping to discern the most appropriate IDCM solution for the enterprise, and provide an example Benchmark Specification template. • Consider the types of functional gaps that might be identified between requirements and offered solutions. • Discuss the importance of reference site checks and the added benefits of reference site visits. • Consider the types of issues that may need to be considered when determining final selection, and the submission of a Selection Report. • Discuss the requirement for the development and execution of a comprehensive contract as a strategy to facilitate successful implementation.
Conference papers on the topic "Requirements specification templates"
1
Daniel, Mworia, Nderu Lawrence, and Kimwele Michael. "Integrated Specification of Quality Requirements in Software Product Line Artifacts." In 7th International Conference on Advances in Computer Science and Information Technology (ACSTY 2021). AIRCC Publishing Corporation, 2021. http://dx.doi.org/10.5121/csit.2021.110309.
Full textAbstract:
There are many calls from software engineering scholars to incorporate non-functional requirements as first-class citizens in the software development process. In Software Product Line Engineering emphasis is on explicit definition of functional requirements using feature models while non-functional requirements are considered implicit. In this paper we present an integrated requirements specification template for common quality attributes alongside functional requirements at software product line variation points. This approach implemented at analytical description phase increases the visibility of quality requirements obliging developers to consider them in subsequent phases. The approach achieves weaving of quality requirements into associated functional requirements through higher level feature abstraction method. This work therefore promotes achievement of system quality by elevating nonfunctional requirement specification. The approach is illustrated with an exemplar mobile phone family data storage requirements case study.
2
Silva, Alberto Rodrigues da, Jan Verelst, Herwig Mannaert, David Almeida Ferreira, and Philip Huysmans. "Towards a System Requirements Specification Template that Minimizes Combinatorial Effects." In 2014 9th International Conference on the Quality of Information and Communications Technology (QUATIC). IEEE, 2014. http://dx.doi.org/10.1109/quatic.2014.22.
Full text
3
Nes, Hroar, Birger Etterdal, and Stian Svardal. "Condition Management of HP/HT Pipelines: A New Approach." In ASME 2008 27th International Conference on Offshore Mechanics and Arctic Engineering. ASMEDC, 2008. http://dx.doi.org/10.1115/omae2008-57352.
Full textAbstract:
StatoilHydro operates a large number of High Pressure/High Temperature (HP/HT) pipeline systems in the Norwegian Sea. These lines connect remote subsea templates to floating processing and storage units. Flowlines are designed for a maximum temperature up to 155 °C and a pressure in the range of 390–500 bar. Design pressure for injection lines are in general 500 bar. In addition to high operating loads, the infield lines are exposed to challenging seabed conditions and a potential for interference with on-bottom trawl gear. The objective of this paper is to present the principles and the methodology used for integrity assessment of the HP/HT lines, which provides the basis for specification of optimum maintenance requirements. The risk of integrity failure, associated with any hot-spot location, is consistently estimated based on safety margins predicted for the actual design criterion and as a function of the pre-defined Safety Class. The developed methodology assumes that the pipeline configuration and associated response parameters are accurately determined for relevant operating conditions. This requires finite element models that are calibrated according to survey data and corresponding operating parameters. A cyclic load history is applied to the post-buckled pipeline model in order to simulate actual operating conditions. Design criteria for relevant degradation and failure modes are established for a wide range of operating configurations and conditions. These criteria are used both to identify potential hot-spots and to estimate the relative utilization. The relative utilization may be estimated for an extreme single event, i.e. a design condition, or due to long term degradation. The risk of integrity failure is then determined as a function of the Safety Class and the relative utilisation, expressing the consequences and the probability of failure, respectively. A risk matrix, configured according to design safety principles, determines the risk of integrity failure. A software interface has been developed to compare and to visualize pipeline simulation results, survey data and corresponding design criteria. This information is used for documentation of the pipeline operating condition, and finally, for specification and follow-up of maintenance measures. The new integrity assessment methodology has been implemented as part of the condition management system for more than 30 HP/HT pipelines operated by StatoilHydro.
4
Woods, Kirby, and Kenneth Thomas. "Reconstitution of Reactor Pressure Boundary Components Design Stress Report for License Renewal." In ASME 2010 Pressure Vessels and Piping Division/K-PVP Conference. ASMEDC, 2010. http://dx.doi.org/10.1115/pvp2010-25215.
Full textAbstract:
The majority of United States Commercial Nuclear Power Plants (CNPP) within the next 10 years will reach the end of their license to operate and can be renewed per the “Atomic Energy Act” of 1954. This act allowed the commission to issue commercial electric power nuclear plants a license to operate (“licensed, but not to exceed 40 years, and maybe renewed upon the expiration of such period, (Chapter 10, Sec. 103(c))).” These CNPP licenses are also governed by the NSSS vendor specification requirements and by the American Society of Mechanical Engineers (ASME) design code standards. This connection is in the form of a stress report that defines the “cyclic life” adequacy criteria for this operational limit of 40 years. The license extension subsequently requires a reconstitution of the initial design stress report input parameters per ASME IWA-4120, 4223 & 4311 (e) for the renewal period extension. This requirement can entail an analysis of the operating conditions and cycles to demonstrate the material elasticity is maintained. The proposed approach for this reconstitution effort was a reanalysis in the form of a study of the Nuclear Steam System Supplier (NSSS) vendors’ original methodology to determine the NSSS vendor specification requirement for ASME code compliance and “cyclic life” adequacy. The information acquired from this evaluation has demonstrated the application to be a complex and simplistic approach. This effort to unravel the composite loading (thermal and pressure transients) condition in relation to specific plant and incident cycles provides both an understanding of component end-of-life limits and supports a comprehensive template for future fatigue life management programs. This paper summarizes this reconstituting effort that utilizes the original vessel stress analysis report to support the license renewal effort, provides a template for future fatigue management programs, demonstrates the conservatism of design, and offers an insight into the design philosophy revealing an elegant process that assures against failures.
5
Bajaj, Manas, Russell S. Peak, and Christiaan J. J. Paredis. "Knowledge Composition for Efficient Analysis Problem Formulation: Part 2 — Approach and Analysis Meta-Model." In ASME 2007 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. ASMEDC, 2007. http://dx.doi.org/10.1115/detc2007-35050.
Full textAbstract:
In Part 1 we presented technical background and a gap analysis leading to the identification of five requirements for a methodology for efficient formulation of analysis problems for VTMB design alternatives. These requirements are founded on (a) abstraction of analysis knowledge as modular, reusable, computer-interpretable, analyst-intelligible building blocks, and (b) automated creation, reconfiguration, and verification of analysis models. In this paper (Part 2), we present an example scenario to overview the Knowledge Composition Methodology (KCM) that is aimed at satisfying these requirements. The methodology is founded on analysis knowledge building blocks and a model transformation process based on graph transformations. With KCM an analyst may automatically compose an analysis model from a design model and these building blocks. In this paper, we focus on the analysis knowledge component of this methodology (illustrated for structural and thermal disciplines), and describe four dimensions of analysis knowledge. Using these dimensions, we develop a decision template for analysts to create specifications for analysis models. Analysis models can be automatically created from a given specification using model transformation techniques (not described in this paper). We leverage the notion of choices and decisions to (a) define primitive and complex building blocks of analysis knowledge, and (b) formalize an analysis meta-model that represents the structure of analysis models. We also relate this analysis meta-model to the NIST Core Product Model (CPM2). The envisioned methodology impact is a formal and systems-oriented foundational approach for analysis problem formulation that is time- and cost-effective.
6
Vilela, Jéssyka. "An Empirical Evaluation about Using Models to Improve Preliminary Safety Analysis." In Workshop em Modelagem e Simulação de Sistemas Intensivos em Software. Sociedade Brasileira de Computação - SBC, 2020. http://dx.doi.org/10.5753/mssis.2020.12496.
Full textAbstract:
Context: Safety analysis is an activity of fundamental importance in the development of safety-critical systems (SCS) to ensure that hazardous situations are properly found and mitigated. Such analysis is usually performed after a system requirements specification is available. Therefore, it is then worthwhile to investigate specification techniques to detect their strengths and weaknesses with respect to finding and documenting hazards early in the development process. Objective: In this paper, we investigate similarities and differences in the results of a preliminary safety analysis from requirements specified using Textual Use Cases (TUC) and Business Process Modeling Notation (BPMN). Method: We adopted a controlled experiment as research method using computer engineering students as subjects. Results: The subjects of BPMN group found more accidents, hazards as well as more causes of hazards. Moreover, they have a higher preference for the template used for safety analysis documentation. Conclusions: The use of BPMN to represent the interactions among actors in a system probably lead to the discovery of more accidents and hazards, but more experiments are necessary to test this hypothesis since the results are not statistically significant.
7
Marcelino-Jesus, Elsa, Joao Sarraipa, Francisco Fraile, and Raul Poler. "A Methodology for Virtual Factory Applications Definition, Development and Validation." In ASME 2019 International Mechanical Engineering Congress and Exposition. American Society of Mechanical Engineers, 2019. http://dx.doi.org/10.1115/imece2019-11527.
Full textAbstract:
Abstract The Virtual Factory Open Operating System (vf-OS) aims to become the reference system software for managing factory related computer hardware and software resources and providing common services for factory computational programs. Additionally, it provides a methodology to support the implementation of virtual factory applications to be deployed in industrial scenarios. This paper focuses on this proposed methodology that guides the virtual factory applications definition, development, and validation. It takes into account the industrial application requirements and specifications to technically and business validate its integration in the proposed vf-OS environment and in the real factory production. Thus, this methodology presents the successive steps and interactions that occur in the process, during the following proposed three phases. In the starting phase, the functionality of the application taking into consideration the actors involved in the process e.g. manufacturing and logistics users and software developers is defined. The development and test phase represent the moment in which the applications are developed, deployed and tested inside pilots’ premises. The evaluation phase is when applications are validated by the evaluators to guarantee that they fulfil the needs of the users. In line with these phases, the methodology presents templates and guidelines that both developers and users should fill to create a common understanding of what is desired. This includes a use case definition template, an application questionnaire, and guidelines for the creation of sketches, mock-ups, and workflow diagrams. This paper demonstrates the proposed methodology reporting the evaluation conducted in three different industrial pilots: 1) manufacturing and logistics or automation: applications focused on providing support to maintenance and spare part stock management in automation production equipment; 2) construction or industrialization: applications to improve time and resource utilization in construction projects through advanced collaboration between construction managers and material providers; 3) manufacturing assembly or collaboration: applications to enable collaborative design and manufacturing of complex products.
8
Hong, Lin Cheng, and Lim Tong Ming. "To enable formal verification of semi-formal requirements by using pre-defined template and mapping rules to map to Promela specification to reduce rework." In 2010 International Symposium on Information Technology (ITSim 2010). IEEE, 2010. http://dx.doi.org/10.1109/itsim.2010.5561453.
Full text
9
Briggs, Ted L., Burt Gischner, Pete Lazo, Mike Olson, Jim Vicedomine, and Ken Wolsey. "Enabling Interoperability through the Ship Life Cycle." In SNAME Maritime Convention. SNAME, 2008. http://dx.doi.org/10.5957/smc-2008-p10.
Full textAbstract:
Shipyards are increasingly responsible for the life cycle support of ships, including maintenance and logistics data over the life of the ship. Hence, it has become important for shipyards to efficiently integrate acquisition product model data with the lifecycle support product model data. The use of Integrated Data Environments (IDE) for Navy ship programs has fostered the integration of design, logistics, and production information for the ship. However, it has not been possible to exchange this integrated data set; rather, different data is typically transferred at different times often resulting in inconsistency. The Product Life Cycle Support (PLCS) STEP standard (ISO 10303-239) for logistics data and life cycle support provides the capability to exchange logistics data linked back to design data. The standard was developed and has been implemented by the aerospace and defense industry. The ISE-6 project demonstrated the feasibility of using the PLCS standard for naval shipbuilding. This approach should also enable interoperability of life cycle data with other defense programs. The ISE-6 team mapped naval shipbuilding requirements into PLCS, while preserving compatibility with existing PLCS implementations. A unique feature was the automated mapping via template expansion and identification. The ISE-6 team conducted a demonstration of this capability, exchanging data between two Integrated Data Environments (IDE) and a Knowledge Management tool, which was used to modify and update the data for the receiving IDE. During the next phase of the project, the ISE-6 team will be investigating interoperability using the S1000D Specification for the procurement and production of technical publications.
10
Prasad, Brian, and Jeff Rogers. "A Knowledge-Based System Engineering Process for Obtaining Engineering Design Solutions." In ASME 2005 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. ASMEDC, 2005. http://dx.doi.org/10.1115/detc2005-85561.
Full textAbstract:
Designing and developing highly engineered products requires direct (and more dynamic) associations between customers’ specifications and product characteristics (or its behaviors). In order to meet the specified customer performance, cost, and integrity goals, a multitude of specialized analyses, heuristics, shortcuts, look-up tables, equations, algorithms, finite elements, and material substitution at multiple levels (system, subsystems, components and parts) are ought to be performed. The product geometries of such engineered product are often complex and many parts are designed interactively from scratch using a 3D commercial computer-aided design (CAD) — lately often referred as Product Life-cycle Management (PLM) system. Today, this very “PLM-based” engineered product-design process is often “static”, very “feature or geometry-dependent,” “knowledge-intensive,” and therefore, engineers often takes considerable time (months) to complete this manual process. Today, more and more companies want to quickly reengineer a product from a multitude of family solutions (corresponding to various design trade-off studies). They are interested in some dynamic form of a decision-based system that could automatically filter through a multitude of historical product solutions and quickly reconfigure one that meets the customer requirements with the least cost, weight, and time investment. Such decision-based product automation is not an easy task by any means. Product definitions without knowing specific geometry are hard to conceive, capture generically, and reuse widely (via any generative tool). A typical product development process —by its nature—is highly dynamic, nonlinear, discrete, feature-dependent, and part-dependent. The solution is not easy, since problem formulation is time-bound, has numerous discrete inputs, topologies, and several mathematical discontinuities. This paper discusses the system architecture of the Knowledge-driven Automation (KDA) program — established at Parker in 2002. It addresses many of the above product development issues and problems. In particular, authors describe a Knowledge-based System Engineering Process for Obtaining Engineering Design Solutions in a Commercial PLM Setting. The architecture and solutions use a number of innovative knowledge-based engineering (KBE) concepts and procedures. Through strategic use of generative modeling, spreadsheet tables, part and assembly templates, system engineering concepts, and our proprietary “smart part concepts,” authors were able to engineer-to-configure a family of hydraulic actuators automatically from their customer specifications using a set of PLM (CATIA V5 and its underlying knowledgeware) tools.