A Cornputer Aided Software Engineering Tool for Scient Ific And

A Cornputer Aided Software Engineering Tool for Scient Ific And

QjXspec: A Cornputer Aided Software Engineering Tool for Scientific and Mathematical Applications BY Stephen E. Oliver A Practicum Report Submitted to the Faculty of Graduate Studies, University of Manitoba in partial fulfillment of the requirernents for the Degree of Master of Mathematical, Computational and Statistical Sciences Institute oE industriai Mathematicd Sciences University of Manitoba FVi-peg, hranitoba @ Stephen E. OIiver, 3001 National Libraiy Bibliothhque nationaie 1*1 of Canada du Canada A uisitions and Acquisitions et ~gio~rn~hicSetvices seMces bibliographiques 395 Weüïngton Street 395. nie WeUington Onawa ON K1A ON4 ûttawa ON Ki A ON4 canada CaMda The author has granted a non- L'auteur a accordé une licence non exclusive licence aiiowing the exclusive permettant à la National Lïbrary of Canada to Bibliothèque nationale du Canada de reproduce, han, distriiute or sell reproduire, prêter, distribuer ou copies of dis thesis in microform, vendre des copies de cette thèse sous paper or electronic formats. la forme de microfichelfilm, de reproduction sur papier ou sur format éiectronique. The author retains ownership of the L'auteur conserve la propriété du copyright in this thesis, Neither the droit d'auteur qui protège cette thèse. thesis nor substantial extracts from it Ni la thèse ni des extraits substantiels rnay be printed or otherwise de celle-ci ne doivent être imprimés reproduced without the author's ou autrement reproduits sans son permission. autorisation. THE UNIVERSïïY OF MANITOBA FACULTY OF GRADUATE STUDIES **** COPYRiGEiT PERMISSION TEXspec: A COMPüTER AIDED SOFTWARE ENGINEERING TOOL FOR SCIENTIF'iC AND MATHEMATICAL APPLICATIONS STEPHEN ElOLIVER A ThesisRracticum submitted to the Faculty of Graduate Studies of The University of Manitoba iïi partiai fflimentof the requirement of the degree of MASTER OF MATEIEMATICAL, COMPZITATIONAL AND STATISTICAL SCENCES STEPHEN E. OLLVER Q 2001 Permission has been granted to the Libnuy of the Univenity of Maoitoba to lend or sel1 copies of this tfiesis/practieum, to the Nationai Libray of Canada to microfilm this thesis and to lend or sen copk of the fdm, and to University Microfdms Inc, to publish an abstract of this thesis/practicum, Tbis reproduction or copy of this thesis bas been made avaüable by authority of the copyright owner solely for the purpose of private study and research, aod may only be reproduced and copied as permitted by copyright laws or with express written authorization fimthe copyright orner, Abstract This report discusees the dewlopment of the '&jbpec Computer Aided Software Engineering (CASE) tool, which assists with the development and documentation of softwate in an environment where software quality is closely monitoted, perhaps by independent reguiators. The tao1 can assist in the development of a broad range of software, but is targeted at the software that imptements mathematical models. Wpec generates rtquirements specificatîons, design specifications and compiiabIe code in a structureri form whiie ensuring consistency between products. The onginai application of wecwas to Bssist devetopers of soRware modeling a repository for Canada's high level nuclear waste to achive compliance with a quality assurance standard ~pecifiedby goverment reguiators. This Iepoh details the form of documentation products produceci by 'QXqec and ai1 required inputs. It discusses the processing that "QXspec uses to convert înput înto finai products. The method of ensuring consistency between products is reviewed. htmction is provideci for operating wpecusing a graphitai user interface. The significance of the work is discdand directions for hiturc! development are suggoited. Some of the requirements of '&Xspec are continuing to evolve, As such, the development is of necessity of a prototype, or spirai mode€, nature, This report acts as a statu report on the development of ï$Jspec and provides a reference for both users and programmers. The author acknowledges the guidance, patience and funding provided by Ontario Power Generation sup porta the development O€ the WpecCASE tool. Paul Gierszewski has acted as project oficer provïding valuable feedback and onginal ideas. May ï$$qtec documentation products have ben reviewed by Teà Melnyk and Chuck Kitson. Their ieedback provided valuable input ta the development process. Maay of the innovative concepts irnplemented by the system, incIudïmg the separation of content from format of documentation, origbate with Terry Andres, who cwmpervised Mpecdevelopment- Some of these concepts were researched initially by Deunis LeNeveu, whose Fortran program mdef inspired WP=- Dr. Sylvanus Ebikioya served 8s -eupervisor at the University of Manitoba. He bas responded to an unknowu *th to be travelied under tight time constrrUnts in an effective and heIphil mannet. The patience and support of Atclmic Energy of Ceneda Ltd. management, in the perçons of All Wikjord and Peter Sargent bas been crucial to the development of mec. The unusd employment situation as the research site in Pinawa is wound dawu hBS been a Wenge to everyone involved. The administration at the Universi~yof Manitoba and the Institute oi Industrial Mathematical Sciences WS)have reacted to the peculiar circumstancw in Pinawa in a highiy ffexibleand patient manner. Pr* fessor John Brewster directs the IIiMS and has led the way, Contents 1 introduction 1 1.1 Problem Definition .......................................... L 1.1.1 Commercial Tools ...................................... 2 1.1.2 Yourdon/DeiMarco Methodology .............................. 2 1.1.3 Design Specifications ..................................... 3 1.1.4 Experienœ with Software Quality Control ......................... 3 1.2 ObjectiveoftheStudy.. ...................................... 4 1.3 Significance of the Study ....................................... 5 1.4 Limitations .............................................. 5 1.5 Related Work ............................................. 5 1.6 Notations ............................................... 6 1.7 Organization of the Report ..................................... 7 2 Spdcation and Design 8 2.1.1 Requirements Specification for i@qec .......................... 8 2.1.2 Architecture of Wpec ................................... 9 2.1.3 Design of QXqec ...................................... 10 2.1.4 impIementation Lenguage .................................. 13 2.2 Application Shared Components .................................. 14 2.2.1 Regnirements Data Dictiomry ............................... L4 i 2.22 Design Data Dictionary ................................... 15 2.2.3 Dictionary Listing ...................................... 17 2.2.4 Equatio m ........................................... 18 2.3 Applicaticn Composite Components ................................ 20 2.3.1 Data Flow Diagratm ..................................... 20 2.3.2 Pmcess Specifications (Mini-Sm) ............................. 25 2.3.3 Design Specifications ..................................... 27 2.3.4 Stnictllie Charts ....................................... 33 2.3.5 Man uais ............................................ 36 3 Graphical User interface 37 3.1 Architecture .............................................. 37 3.2 Con&uration and the Sead List ................................. 38 3.3 Requirements Data Dictionary ................................... 39 3.4 Design Data Dictionary ....................................... 41 3.5 Dictionary Listing .......................................... 41 3.6 Proceas Specifications (Mini-spem) ................................. 42 3.7 Data Flow Diagrams ......................................... 43 3.8 DesignSpecificatiom ......................................... 45 3.9 StnictureCharts ........................................... 4û 3-10 Maauais and Equations ....................................... 49 3.11 Java - Perl interface ........................................ 43 4 Conclusions 52 4.1 Maintenance and hture Development ............................... 52 A Sample Data FIow Diagram 54 B Sample Design Speciûcation 56 B.1 Output ................................................ 56 B.2 Input ........................................... 63 C Sample PERL fim*pt 68 D Sample Java Module (GUI) 77 E Installation 83 E.1 Prerequisite Software ......................................... 83 E.1.1 Perl .............................................. 83 E.1.2 mandm ........................................ 83 EL3 Noweb ............................................. 83 E.1.4 JAVA Runtime Environment ................................ 84 E.2 Wpec Speci6c hdiation .................................. 84 1 Introduction The Deep Geologic Repaeitory Technology Program (DGm), addnistered by Ontario Pawer Generation (OPG) ,is chargeci with developing technology to deal with Canada's high level nuclear waste. Atomic Energy of Canada Ltd (AECL), ns a major contractor to the DGR!I'E', has accumulated considerable expenence developing computer programs to mode1 a deep geologîc repository for used luel [8, 91. These programs require software of dernonstrably iugh quaiity to support tesults pmented to the Cadian Nuclear Safety Commission (CNSC) and the public. ln 1999 the Canadian Standards Miation (CSA) adopted astandard (CSA N286.7) [41 lot the development of nuclear safety related computer progranm. a scxipe that included many DGRTP models. While the software development procm used previously was considered robust, it required reiinement in order to achieve cornplianuice

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    99 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us