Extending Failure Modes and Effects Analysis Approach for Reliability Analysis at the Software Architecture Design Level

A process for the production of branched polymers of arylene sulfide in which a reaction mixture of (1) at least one p-dihalobenzene, (2) at least one alkali metal sulfide, (3) at least one organic amide, (4) water in an amount of about 1.0 mole to about 2.4 moles per mole of alkali metal sulfide, and (5) at least one alkali metal carboxylate is contacted under polymerization conditions for a time sufficient to form arylene sulfide polymer and the arylene sulfide polymer formed in said reaction mixture is contacted under polymerization conditions with a polyhaloaromatic compound having more than two halogen substituents per molecule for a time having a range of up to about 75 minutes before entering upon termination of the polymerization process. An embodiment of the process in which the alkali metal sulfide is produced in situ by the reaction of an excess of alkali metal hydroxide with alkali metal hydrosulfide. An embodiment in which carbon dioxide is contacted with arylene sulfide polymer formed in the reaction mixture to stabilize the polymer. A melt spun fiber that is the product of this reaction.

[1]  Michael R. Lyu,et al.  Dependability Modeling for Fault-Tolerant Software and Systems , 1995 .

[2]  Paul Clements,et al.  Documenting Software Architectures in an Agile World , 2003 .

[3]  Felix Redmill Exploring subjectivity in hazard analysis , 2002 .

[4]  Kosuke Ishii,et al.  ADVANCED FAILURE MODES AND EFFECTS ANALYSIS USING BEHAVIOR MODELING , 1997 .

[5]  Carl E. Landwehr,et al.  Basic concepts and taxonomy of dependable and secure computing , 2004, IEEE Transactions on Dependable and Secure Computing.

[6]  David Garlan,et al.  Documenting software architectures: views and beyond , 2002, 25th International Conference on Software Engineering, 2003. Proceedings..

[7]  Yiannis Papadopoulos,et al.  Automating the failure modes and effects analysis of safety critical systems , 2004, Eighth IEEE International Symposium on High Assurance Systems Engineering, 2004. Proceedings..

[8]  Malcolm Wallace,et al.  Modular Architectural Representation and Analysis of Fault Propagation and Transformation , 2005, FESCA@ETAPS.

[9]  Joanne Bechta Dugan Software system analysis using fault trees , 1996 .

[10]  Felix Redmill,et al.  System Safety: HAZOP and Software HAZOP , 1999 .

[11]  Nancy G. Leveson,et al.  Safety verification of Ada programs using software fault trees , 1991, IEEE Software.

[12]  Eila Niemelä,et al.  A Survey on Software Architecture Analysis Methods , 2002, IEEE Trans. Software Eng..

[13]  Clifton A. Ericson,et al.  Failure Mode and Effects Analysis , 2005 .

[14]  Felix Bachmann,et al.  Deriving Architectural Tactics: A Step Toward Methodical Architectural Design , 2003 .

[15]  Felix Redmill,et al.  Towards System Safety , 1999, Springer London.

[16]  Donald J. Reifer,et al.  Software Failure Modes and Effects Analysis , 1979, IEEE Transactions on Reliability.

[17]  Vyacheslav S. Kharchenko,et al.  F(I)MEA-Technique of Web Services Analysis and Dependability Ensuring , 2006, RODIN Book.

[18]  Hany H. Ammar,et al.  Scenario-based reliability analysis of component-based software , 1999, Proceedings 10th International Symposium on Software Reliability Engineering (Cat. No.PR00443).

[19]  Jonathan P. Bowen,et al.  System and Software Safety in Critical Systems , 1996 .

[20]  Doug Rosenberg,et al.  Use case driven object modeling with UML: a practical approach , 1999 .

[21]  Jianyun Zhou,et al.  Using FMEA for early robustness analysis of Web-based systems , 2004, Proceedings of the 28th Annual International Computer Software and Applications Conference, 2004. COMPSAC 2004..