DhIiT FILE COPY -a) - DTIC
DhIiTFILE COPY -a)cV)(0CDNAVAL POSTGRADUATE SCHOOLMonterey, CaliforniaNNDTICSEP 24 190THESISTHE CLASSIFICATION AND EVALUATIONOFCOMPUTER-AIDED SOFTWARE ENGINEERINGTOOLSbyGARY WAYNE MANLEYSeptember, 1990Thesis Advisor:Co-Advisor:LuqiBernd J. KrimerApproved for public rclease, distl'ib iontisunlimited.90 09 20 026
UNCIASSIFIEl)SECURITY CLASSIFICATION OF THIS PAGEREPORT DOCUMENTATION PAGEla REPORT SECURITY CLASSIFICATIONU NCLASSIFIEDl b RESTRICTIVE MARKINGS2a. SECURITY CLASSIFICATION AUTHORITY3 DISTRIBUTIONIAVAILABILITY OF REPORTApproved for public release;disLribution is unlimited.2b DECLASSIFICATION/DOWNGRADING SCHEDULE4 PERFORMING ORGANIZATION REPORT NUMBER(S)5 MONITORING ORGANIZATION REPORT NUMBER(S)6a NAME OF PERFORMING ORGANIZATIONNaval Postgraduate School7a NAME OF MONITORING ORGANIZATIONNaval Postgraduate School6b OFFICE SYMBOL(If applicable)1376c ADDRESS (City. State, andZIP Code)7b ADDRESS (City, State, andZIP Code)Monterey, CA 93943-5000Monterey, CA 93943-50008a NAME OF FUNDING/SPONSORING8b OFFICE SYMBOLORGANIZATION9 PROCUREMENT INSTRUMENT IDENTIFICATION NUMBER(1f applicable)National Science FoundationNSF CCR-87107378c ADDRESS (City, State, and ZIP Code)10 SOURCE OF FUNDING NUMBERSProqrtm tiement NoProjectNOI d'Washington, D).C. 20550NOWork Unlt AccelaonNumber11 TITLE (Include Security Classification)The Classification and Evaluatin of (oomputer-Aided Software Engineering Tools12 PERSONAL AUTHOR(S)Manley, Gary Wayne13a TYPE OF REPORTN;astor's Thesis13b TIML COVEREDFromTo14 DATE OF REPORT (year, month, day)1990, September15 PAGE COUNT19716 SUPPLEMENTARY NOTATIONThe views expressed in this thesis are those of the author and do not reflect the official policy or position of the Department of l)efense or the U.S.Government.17 COSATI CODES18 SUBJECT TERMS (continue on reverse if necessary and identify by block number)FIELDGROUPSUBGROUPComputer-Aided Software Engineering; Systems Development Lifecycle; Dol) STD-2167A;CASE Environment; Framework; Repository; Tool Taxonomy; Tool Evaluation Process19 ABSTRACT (continue on reverse if necessary and identify by block number)-)The use ofComputer Aided Software Engineering (CASE) IAols has been viewed as a remedy for the software development crisis by achievingimproved productivity and system quality via the automation of all or part of the software engineering process. The proliferatinn and tremendousvariety of tUras available have stretched the understanding of experienced practicioners and has had a profound impact on the softwareengineering process itself. To understand what a tool does and compare it to similar tools is a formidable task given the existing diversity offunctionality. This thesis investigates what tools are available, proposes a general classification scheme to assist those investigating tools todecide where a tool falls within the software engineering process and identifies a tool's capabilities and limitations. This thesis also providesguidance for the evaluation ofa LAoland evaluates three commercially available tools./(L-77A20 DISTRIBUTION/AVAILABILITY OF ABSTRACTlNCI AW,%IIItIJNI MI1321 ABSTRACT SECURITY CLASSIFICATIONQ) 1,ii-t1% Hi'iSU NCI.ASSI FlEl)22a NAME OF RESPONSIBLE INDIVIDUALProfessor 1.u(DD FORM 1473,84 MAR22b TELEPHONE (Include Area code)14081) 646 273583 APR edition may be used until exhaustedAll other editions are obsoletei22c OFFICE SYMBOLCode 521qSECURITY CLASSIFICATION OF THIS PAGEU NC LASSIFIE)
Approved for public release; distribution is unlimited.The Classification and Evaluation ofComputer-Aided Software Engineering ToolsbyGary W. ManleyCaptain, United States Marine CorpsB.B.A., Texas A&M University, 1981Submitted in partial fulfillmentof the requirements for the degree ofMASTER OF SCIENCE IN INFORMATION SYSTEMSfrom theNAVAL POSTGRADUATE SCHOOLSeptember 1990Author:Gary Wayne ManleyApproved by:(,A-Luqi, Thes's AdvisorBernd J. Kramer, Co-AdvisorTarek Abdel-Hamid, SaderDavid ofR. AdministratiWhipple, ChamanDepartmente Sciences
ABSTRACTThe use of Computer-Aided Software Engineeringhas been viewed asa remedyfor thesoftware(CASE) toolsdevelopmentcrisis by achieving improved productivity and system qualityvia the automation of all or part of the software engineeringprocess.The proliferation and tremendous variety oZ toolsavailable havestretchedthe understandingofexperiencedpractitioners and has had a profound impact on the softwareengineering process itself.To understand what a tool doesand compare it to similar tools is a formidable task given theexisting diversity of functionality.This thesis investigateswhat tools are available, proposes a general classificationscheme to assist those investigating tools to decide where entifies a tool's capabilities and limitations.This thesisalsoaprovidesguidance' fortheevaluationoftoolandevaluates three commercially available tools.CD7.-,----.-.,iWTiiis!.
Thesis DisclaimerThe following trademarks are used throughout this thesis:3COM is a Registered Trademark of 3COM t (Ada Joint Program tionalBusines Machines CorporationAnalysis/Design Workbenchis a Registered Trademark of KnowledgeWare, IncApollois a Registered Trademark of Apollo ComputerIncorporatedAT&T 6300/AT&T StarLANare Registered Trademarks of AT&T BellLaboratoriesAutoCADis a Registered Trademark of AutodeskIncorporatedBATis a Registered Trademark of McCabe &Associates, IncCCCis a Registered Trademark of SoftoolCorporationCompaq III/Compaq Plus/Compaq Portable 286are Registered Trademarks of Compaq ComputerCorporationCross Systems Productis a Registered Trademark ofBusiness Machines CorporationCustomizeris a Registered Trademark of Index TechnologyCorporationData AnalystisaRegisteredTrademarkInformation Systems, IncDevelopmateis a Registered Trademark ofBusiness Machines CorporationDSEEis a Registered Trademark of Hewlett-PackardCompanyEPOSis a Registered Trademark of Software Product& Services IncorporatedEpson/FXI00/LQI500are Registered Trademarks of Epson AmericaIncorporatedExpert Systems Environment is a Registeredi Trademark ofBusiness Machines ernationalInternationialis a Registered Trademark of Index TechnologyCorporationiv
FrameMakerHP 9000/Laserjet/HP/Vectra/HP7475Ais a Registered Trademark of Frame TechnologyCorpare Registered Trademarks of Hewlett-PackardCompanyHP SoftBench/HP Encapsulatoris a Registered Trademark of Hewlett-PackardCompanyIBMis a Registered Trademark of InternationalBusiness Machines CorporationIBM PC-DOS/Proprintersare Registered Trademarks of InternationalBusiness Machines CorporationIBM PC LANis a Registered Trademark of InternationalBusiness Machines CorporationIBM Token Ringis a Registered Trademark of InternationalBusiness Machines CorporationIBM XT/AT/PS/2are Registered Trademarks of InternationalBusiness Machines CorporationIEF/TI 855are Registered Trademarks of Texas InstrumentsIncInterLeafis a Registered Trademark of InterLeaf, IncKEEis a Registered Trademark of InternationalBusiness Machines CorporationKeyOneis a Registered Trademark of LPS s.r.l.Knowledge Toolis a Registered Trademark of InternationalBusiness Machines CorporationMicroSTEPis a Registered Trademark of SysCorpInternationalMS-DOSis a Registered Trademark of MicrosoftCorporationNovell Advanced Netwareis a Registered Trademark of Novell IncNovell ELS Netware 286is a Registered Trademark of Novell IncPC Prismis a Registered Trademark of Index TechnologyCorporationPlanning Workbenchis a Registered Trademark of KnowledgeWare, IncRCSis a Registered Trademark of Hewlett-PackardCompanyRefineis a Registered Trademark of Reasoning Systems,Inc.Repository Manageris a Registered Trademark of InternationalBusiness Machines CorporationSaber-Cis a Registered Trademark of Saber Software,IncV
SES/workbenchis a Registered Trademark of Scientific &Engineering Software, IncSoftware BackPlaneis a Registered Trademark of AthertonTechnologySTARTis a Registered Trademark of McCabe &Associates, IncStPis a Registered Trademark of InteractiveDevelopment EnvironmentsStP/INGRES Interfaceis a Registered Trademark of SoftoolCorporationStP/TESTBED Interfaceis a Registered Trademark of IGL TechnologySYBASE SQL Serveris a Registered Trademark of SybaseIncorporatedSun/Sparcstationare Registered Trademarks of Sun MicrosystemsIncorporatedTIRSis a Registered Trademark of InternationalBusiness Machines Corporationare Registered Trademarks of Toshiba AmericaToshiba P1350/PI351/P351IncUNIFACEis a Registered Trademark of Uniface B. V.Unixis a Registered Trademark of AT&TBellaboratoriesVADSis a Registered Trademark of Verdix onare Registered Trademarks of Digital EquipmentCorporationXL/Docis a Registered Trademark of Index TechnologyCorporationXL/Interfaceis a Registered Trademark of Index TechnologyCorporationXL/Programmer Interfaceis a Registered Trademark of Index TechnologyCorporationvi
GLOSSARYData Item Descriptions (DID's):DID's describe the set ofdocuments for recording information required by the DoD STD2167A.Encyclopedia: A database that stores information created byan integrated set of CASE tools.Framework:An architecture for the integration of acollection of CASE tools designed to form a singleintegrated environment with a consistent user interface.Product Baseline:The software as designed, tested, andimplemented prior to installation.Project Management: All the tasks associated with the role ofthe project manager including planning, estimating andmonitoring the progress of a software development project.Support for project management includes a set of well-knowntools and procedures such as cost and size modeling, criticalpath methods, schedule charts, (Gantt charts or timelines),resource loading, spreadsheets, work breakdown structure,status reporting, electronic mail, milestone definition,budgeting, expense tracking, capital allocation, problemtracking and change authorization.Rapid Prototyping: Quick and inexpensive construction of highfidelity simulation of an interactive system for whateverpurpose (i.e., requirements definition).Used to convey thelook and feel of a system. Depends heavily on automated toolsupportlike datadictionaries,screenformattersandpainters, report generators and very high level languages likefourth generation languages and functional languages.Repository:The database management facility of the CASEenvironment which provides data integration services among allthe tools in the environment. It saves design information inan abstract form like an Encyclopedia, but also capturesproject and enterprise information.Software Development Plan (SDP): A single document outliningthe steps for conducting the activities required by thestandard.vii
TABLE OF CONTENTSI.INTRODUCTIONA.II.BACKGROUND.Rising Software Costs2.Software Development Crisis .WHY CASE.C.CASE OBJECTIVES .D.TOOL EXPLOSIONE.RESEARCH FOCUSF.THESIS ORGANIZATION .4.5.5WHAT IS CASEB.EVOLUTION OF CASE .6.7.7.8.8.9.9.1.Origin of Case2.CASE Arrives3.The CASE Environment.ELEMENTS1.Toolset .2.Integration Architecture3.Toolkits10.11.(CASE) vs WorkbenchesWorkbenches(ICASE)c. CASE vs ICASE(ICASE).viii10.a. Toolkits (CASE) .b.ENVIRONMENT .ENVIRONMENTAL4.A.C.2. 2.B.12. .1.THE FULL .ASE. . . . . . . . . . . . . . . .13131516
Repository5.Methodology .D.THE FULL CASE ENVIRONMENT .E.CASE TRENDSF.16.19.20.23.23.261.Integration Architectures .2.Specification CompilersSUMARY.IMPACT OF DoD STD-2167A ON CASEIII.A.BACKGROUNDB.APPLICABILITY OF DoD STD-2167AC.SOFTWARE DEVELOPMENT PROCESS.D.IMPACT ON CASE.E.IV.4.2828.29.3031.33.35First Generation Support Tools.36Second Generation Support Tools.36.37.38.38.39.39.40.40.1.Documentation Requirements2.Traceability of Requirements3.4.SUMMARY .TCOL TAXONOMY .A.CLASSIFICATION GOALB.CLASSIFICATION STRATEGY1.Framework2.Categories3.27.a.Lifecycle Coverage .b.Integration Level.41c.Application Areas.43.45Attributes.ix
4.V.45C.SURVEYS.47D.SUMMARY.48TOOL EVALUATION PROCESS.49A.PREFACEB.EVALUATION CRITERIA .50C.ASSESSMENT PROCESS.511.Needs Analysis.522.Environment Analysis.533.Develop Candidate List.534.Apply Criteria and Select.56D.VI.Employment.a.Establish Evaluative Criteriab.Define a Specific Experimentc.Execute the Experiment .d.Analyze the Results.50.SUMMARY .Tool EvaluationsA.-.1.9OFCORPORATION rdware/Operating System Evaluated On632.Tool Description.633.Methodology Supported.644.Hardware/Operating Systems .Interface to Other Products.x.68
8.Multi-user Support.709.Network Support.7010. DoD STD-2167A Support.7111. User-Interface.7212. Traceability of Requirements.7313. Dictionary/Repository.7414. Prototyping.7715. Consistency/Completeness Checking.7816. Training Support.8117. Diagramming/Graphic TENVIRONMENTS.861.Hardware/Operating System Evaluated On2.Tool Description.863.Methodology Supported.874.Hardware/Operating Systems rface to Other Products.948.Multi-user Support.969.Network Support.9886.8910. DoD STD-2167A Support.10011. User-Interface.10212. Traceability of Requirements.10413. Dictionary/Repository.10514. Prototyping.107xi
15. Consistency/Completeness Checking16. Training Support.EPOS4.0(PC-Vers)OFil.SOFTWARESERVICES, INC .PRODUCTS.112&1151.Hardware/Operating System Evaluated On1152.Tool Description.1163.Methodology Supported .1164.Hardware/Operating Systems Requirements1175.Installation.1186.Documentation .1207.Interface to Other Products .8.Multi-user Support9.Network Support .10. DoD STD-2167A Support .11. User-Interface.124.125.13. Dictionary/Repository .14. Prototyping .15. Consistency/Completeness Checking16. Training Support.OVERALL .138.139.140.142APPENDIX A - SAMPLE TOOL TAXONOMY FORM .xii125.17. Diagramming/Graphic FacilitiesD.123.12. Traceability of RequirementsVII.109.17. Diagramming/Graphic FacilitiesC. .145
APPENDIX B-TOOL TAXONOMY.147APPENDIX C-BLANK TOOL TAXONOMY FORM.155APPENDIX D-TOOL EVALUATION CHECKLIST.157LIST OF REFERENCES.174INITIAL DISTRIBUTION LIST.177xiii
I.INTRODUCTIONCost overruns, delivery postponements and the productionof ineffective or inadequatesystems hascharacterized thesoftware development process within the software engineeringindustry and the Department of Defense(DoD).Both industryand DoD have explored many options to address these shortfallsand reduce bothsoftware costs and application backlogs.Theapplication of software engineering and the use of softwaredevelopmentmethodologies helped, butdid not provide thedesired impact.Computer Aided Software CASE)softwaredevelopment crisis by automating analysis, design, and coding,butmetwithlittleinitialsuccessduetechnology and limited tool availability.totheimmatureHowever, the recentrevolutions in CASE technology have caused an explosion intool capabilities and y of their evaluation.The assorted features andgreatlyincreasedtheThis thesis will examine thetools available and their range of capabilities and evaluatea discrete sample of tools.
A.BACKGROUND1.Rising Software CostsBoth the Department of Defense (DoD) and industry areexpending enormous amounts of time and money developing andmaintaining software systems with costs continuing to rise.Figure 1 reflects the trends of software costs noted by Boehm[Ref. 1:pp. 32-33].Software Costs(Billions)WorldU.S.DoDFigure 1-11985199014025070125198519951136Rising Software CostsThe sheer magnitude of these costs and the pendingbudget reductions necessitate serious considerations by DoD tounderstand and control software costs.2.Software Development CrisisDoD and other federal software development effortshave been plagued by costoverruns,postponements and thedelivery of ineffective or inadequate systems.The extent ofthe problem is evidenced by the following statistics:2
A U.S. Army study of several federal projects found that:-47 percent were delivered, but not used-29 percent were paid for, but not delivered-19 percent abandoned or reworked-3 percent were used after changes were made-only 2 percent were used as delivered.For a U.S. Air Force command and control system:-the initial estimate was 1.5 million-the winner's bid was 400,000-the actual project cost was 3.7 million [Ref. 2: p.51].In addition to the problems noted above, DoD facesanother pending reality of the software crisis regarding thebacklog of systems needed and the maintenance requirements ofexisting software systems:such efforts.The lack of personnel to performThis issue is best reflected in the followingstatemepts:The backlog for software development in both the DP/MISand the Aerospace, Defense, Engineering (ADE) sectors islarge and growing at an accelerating pace, and the supplyof professionals to address this backlog is severelylimited. [Ref. 3: p. viii]. the national demand for software is rising at least 12percent per year, while the supply of people who producesoftware is increasing about four percent per year; thisleaves a cumulative four percent gap [Ref. 4]. 25 percent of the draft age population will be requiredto maintain DoD software by the year 2000 [Ref. 5].The quality and productivity issues cited above arecompounded by the increasing complexity of software systems aswell.DoD cannot ignore these issues.Software Engineeringhas mitigated some of the impact of these issues, but in orderto achieve the quality and productivity required DoD must relyon the automation of all aspects of software development.3
B.WHY CASEThe fundamental purpose of CASE is to allow developers toproduce higher quality software more quickly with less effort[Ref. 3:p. viii].CASE focuses on automating the activitiesof software developers. Automating these activities increasesquality and productivity at the same time (Ref. 2:p. 49].C.CASE OBJECTIVESCASE is not just confined to quality and productivity.Mc
dhiit file copy -a) cv) (0 naval postgraduate school cd monterey, california nn dtic sep 24 190 thesis the classification and evaluation of computer-aided software en
A file pointer must be declared and used to access a file. Declaring a file pointer would be in this general form: FILE * ptr_name for example: FILE * inFile; // for an input file FILE * outFile; // for an output file inFile and outFile are just variable names, and as you know, you can name your variables whatever you want.
Emory University OneDrive for Business LITS Messaging Team 5 Delete: Delete the selected file or folder Move to: Move the file or folder to another folder Copy to: Copy the file or folder to another folder Rename: Rename the file or folder File View Buttons When clicking on a file, t
Day 1 pwd - report your current directory cd to where - change your current directory ls directory -list contents of directory cp old file new file - copy file cp –r old dir new dir - copy a directory and its contents mv old file/dir new file/dir - move (or rename) rm file -delete a fil
akuntansi musyarakah (sak no 106) Ayat tentang Musyarakah (Q.S. 39; 29) لًََّز ãَ åِاَ óِ îَخظَْ ó Þَْ ë Þٍجُزَِ ß ا äًَّ àَط لًَّجُرَ íَ åَ îظُِ Ûاَش
Collectively make tawbah to Allāh S so that you may acquire falāḥ [of this world and the Hereafter]. (24:31) The one who repents also becomes the beloved of Allāh S, Âَْ Èِﺑاﻮَّﺘﻟاَّﺐُّ ßُِ çﻪَّٰﻠﻟانَّاِ Verily, Allāh S loves those who are most repenting. (2:22
Four line copy for GK, MSC, Comp. 200pg 3 Two line copy for Hindi 200 pg 1 Box copy for Maths 200 pg 1 Test copies- four line copy 100 pg 5 Two line copy 100 pg 1 Box copy 100 pg 1 Covering paper Orange S.NO SUB NAME OF THE BOOKS PUBLISHERS CLASS STD 3 1 ENG NEW OXFORD MODERN ENG. COURSE BOOK III OXFORD UNIVERSITY PRESS
Crush It - Cart Card. Crush It - Cart Card with Club Name. PRINT. Cart Cards. Place these in your carts during prime sign up seasons. Contact us today! 000.000.0000 name.here@clubcorp.com. Introducing a Golf Program for Life. Copy here copy here copy here copy here copy here copy here co
To better understand the events that led to the American Revolution, we will have to travel back in time to the years between 1754 and 1763, when the British fought against the French in a different war on North American soil. This war, known as the French and Indian War, was part of a larger struggle in other countries for power and wealth. In this conflict, the British fought the French for .
