DOCSLIB.ORG

Introduction Development Lifecycle Model

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Introduction Development Lifecycle Model DeveIopment of a Comprehensive Software Engineering Environment Thomas C. Hartrum Gary B. Lamont Department of Electrical and Computer Engineering Department of Electrical and Computer Engineering School of Engineering School of Engineering Air Force Institute of Technology Air Force Institute of Technology Wright-Patterson AFB, Dayton, Ohio, 45433 Wright-Patterson AFB, Dayton, Ohio, 45433 Abstract The concept of an integrated software development environment The generation of a set of tools for the software lifecycle is a recur- can be realized in two distinct levels. The first level deals with the ring theme in the software engineering literature. The development of access and usage mechanisms for the interactive tools, while the sec- such tools and their integration into a software development environ- ond level concerns the preservation of software development data and ment is a difficult task at best because of the magnitude (number of the relationships between the products of the different software life variables) and the complexity (combinatorics) of the software lifecycle cycle stages. The first level requires that all of the component tools process. An initial development of a global approach was initiated at be resident under one operating system and be accessible through a AFIT in 1982 as the Software Development Workbench (SDW). Also common user interface. The second level dictates the need to store de- other restricted environments have evolved emphasizing Ada and di5 velopment data (requirements specifications, designs, code, test plans tributed processing. Continuing efforts focus on tool development, and procedures, manuals, etc.) in an integrated data base that pre- tool integration, human interfacing (graphics; SADT, DFD, structure serves the relationships between the products of the different life cy- charts, ...), data dictionaries, and testing algorithms. Current efforts cle stages. This integration of tools and techniques at both levels is a are emphasizing natural language interfaces, expert system software major objective of any software engineering environment development development associates and distributed environments with Ada as effort. the target language. The current implementation of the SDW is on The major objectives are to provide a production software devel- a VAX-11/780 under VMS. Also, a simplified version of the SDW opment environment for students and faculty and to generate a soft- has been hosted on personal computers. Other software development ware engineering research testbed. Initially the SDW provided the tools are hosted under UNIX and are being networked through en- overall architecture for a “complete” capability. Itecently, efforts are gineering work stations. This paper discusses the various aspects of focusing on a distributed version of the SDW concept called System AFIT’s development of software engineering environments. 690 in support of the software engineering laboratory course, EENG 690. Introduction Development Lifecycle Model A software development environment is an integrated set of auto- The definition of the software lifecycle as supported and used by the mated and interactive software development tools that aid the soft- various environments consists of the standard six phases; require- ware engineer in the development of quality software products. The ments definition, preliminary design, detailed design, implementation specific software products which are associated with the software life (coding), integration and operation and maintenance. This general cycle include requirements definitions; design specifications; source methodology is reflected in DOD Standard 2167 [l]. Documentation and executable program codes; test plans, procedures, and results; as must be provided within each phase to support reviews (static) and well as other associated documentation such as guides and manuals testing (dynamic) of results associated with each activity. ca- of operation and maintenance of the software. By definition, software This pability can be provided through the use of a data dictionary and only exists in its documentation! Thus, extensive records must be associated data base management system. Software system correc- generated, maintained, and managed to properly fulfill the software tions and enhancements should flow through all previous phases for engineering objectives. A well planned and implemented software “proper” documentation. develapment environment can effectively assist in the generation of Note that validation and testing is not a distinct stage in this reliable and maintainable computer software. lifecycle, but rather an activity that is performed along the entire The typical software development environment includes both hard- lifecycle. This activity involves the testing of the products of each ware and software tools to aid the software engineer in the production stage for internal consistency and completeness with the products of programs. Software development environments may consist of a of the previous stages. Furthermore, the products of each stage are minimal set of tools, such as an editor, a compiler, and a link/loader, validated against the user’s perception of the requirements. that support only the actual coding of software. However, the most The Software Development Workbench(SDW) and the distributed effective environments are those with an extensive set of powerful in- environment, System 690, are developed using this software life cycle teractive and integrated tools that support state-of-the-art method- definition with the primary objective of providing integrated and au- ologies for dealing with software from its very conception through its tomated support. Discussion of each environment follows the stages of eventual termination. A specific software development environment its initial lifecycle. The objectives and accomplishments of each stage consists of a process methodology along with given hardware and sys- of the lifecycle development are presented. The requirements defini- tem software, manual procedures and support personnel. The process tion and preliminary design stages deal with a system as it should ex- methodology usually involves a specific set of operations (steps) along ist in its ultimate form, whereas the detailed design, implementation, with conceptual tools to support these steps within the software life- integration, and operation stages emphasize a prototype environment cycle phases mentioned previously. with a menu driven interface and initial tool set. 31 SDW Requirements and Design concerns are of special significance to the SDW effort. Integration is to be realized in terms of both accessing component tools and storing The first stages of the SDW development effort [2] emphasized the of the development data. Traceability must also be preserved between requirements definition and preliminary design of the ultimate SDW the products of the different stages of the development effort. User- implementation. Due to the extensive scope of this task, the target friendliness is also a very significant concern. The SDW must utilize was set at a fairly high level specification with the individual subsys- the latest concepts of ergonomics in the design of its human inter- tems specified in greater detail with the use of recursive applications face. This interface should be easily understandable with a simple of the software life cycle. logical structure, well laid out display, and a simple command input The results of this task are a set of five primary objectives of mechanism. Prefabricated programming, or the incorporation of ex- the SDW, thirteen specific concerns for its development [3], a func- isting software can improve development productivity. Flexibility is tional model and associated evaluation criteria, a hardware/software required at both the environment and tool level to allow users to op- configuration model, and a structure model that identifies all generic erate in a mode comfortable to their knowledge and experience levels. component tool types. That is, the operation of the SDW must allow the user to tailor the Of the five objectives of the SDW, the reduction of software errors type of prompting, feedback, and structure [5]. is the first (41. This is to be achieved by supporting and enforcing the A functional model of the software development process using use of accepted software engineering principles, as well as by using SADT (Structured Analysis and Design Technique) diagrams [SI was the computer to augment different testing procedures. developed in order to define the SDW process and to select those The SDW must also be responsive to change. Realizing that soft- aspects of the process that could be automated. Furthermore, a set ware is a dynamic entity, the SDW must be able to support changing of evaluation criteria is established with which to judge the effective- requirements for its operation. ness of the environment in satisfying its requirements. However, for The rapid assessment of design alternatives is also quite impor- reasons of brevity, these topics are not discussed further. tant. The use of simulation models and prototyping is selected more The configuration model of the SDW shown in Figure 1 illustrates and more to assess design operations as well as to aid in determining the basic hardware/software configuration for the environment. The the end user’s true needs. SDW Executive is the primary interface and controller of the com- The SDW must also be capable of providing interactive
Load more

Recommended publications
  • Job Description - Software Engineer I
    Job Description - Software Engineer I Department: Engineering - 2013-03 Exemption Status: Non-Exempt Summary: This position is responsible for software development in multi-application, multi-server, and hosted environments. The candidate will primarily provide system/configuration support with a focus in helping the needs of both internal and external customers. He or she will participate in all facets of software and system development life-cycle. The most qualified candidate for this role will have experience working with business intelligence in the public safety and/or public health software fields and have formal software education and/or a ton of practical experience. We develop primarily in C#, .NET, SQL, SSRS and mobile. Anyone that might fit well at FirstWatch must be hard-working, people-oriented, friendly, patient, a fast learner, think quickly on their feet, take initiative and responsibility, and LOVE providing our customers great and honest customer service. This person will need to maintain a high quality productivity level within a fast paced environment. This position shares responsibility (rotates) with other engineering staff for 24×7 on call duties and so must be able to thrive in this environment. Responsibilities: - Maintain and modify the software and system configurations of production, staged, and test applications. - Interface with different stakeholders to determine and propose appropriate and effective technology solutions to meet business and technical objectives. - Develop interfaces, applications and other technical solutions to support the business needs through the planning, analysis, design, development, implementation and maintenance phases of the software and systems development lifecycle. - Create system requirements, technical specifications, and test plans.
    [Show full text]
  • Structured Programming - Retrospect and Prospect Harlan D
    University of Tennessee, Knoxville Trace: Tennessee Research and Creative Exchange The aH rlan D. Mills Collection Science Alliance 11-1986 Structured Programming - Retrospect and Prospect Harlan D. Mills Follow this and additional works at: http://trace.tennessee.edu/utk_harlan Part of the Software Engineering Commons Recommended Citation Mills, Harlan D., "Structured Programming - Retrospect and Prospect" (1986). The Harlan D. Mills Collection. http://trace.tennessee.edu/utk_harlan/20 This Article is brought to you for free and open access by the Science Alliance at Trace: Tennessee Research and Creative Exchange. It has been accepted for inclusion in The aH rlan D. Mills Collection by an authorized administrator of Trace: Tennessee Research and Creative Exchange. For more information, please contact [email protected]. mJNDAMNTL9JNNEPTS IN SOFTWARE ENGINEERING Structured Programming. Retrospect and Prospect Harlan D. Mills, IBM Corp. Stnuctured program- 2 ' dsger W. Dijkstra's 1969 "Struc- mon wisdom that no sizable program Ste red .tured Programming" articlel could be error-free. After, many sizable ming haxs changed ho w precipitated a decade of intense programs have run a year or more with no programs are written focus on programming techniques that has errors detected. since its introduction fundamentally alteredhumanexpectations and achievements in software devel- Impact of structured programming. two decades ago. opment. These expectations and achievements are However, it still has a Before this decade of intense focus, pro- not universal because of the inertia of lot of potentialfor gramming was regarded as a private, industrial practices. But they are well- lot of fo puzzle-solving activity ofwriting computer enough established to herald fundamental more change.
    [Show full text]
  • It Software Engineer 1
    Pierce County Classification Description IT SOFTWARE ENGINEER 1 Department: Finance FLSA: Non-Exempt Job Class #: 632700 Represented: No Pay Range: Professional 15 Classification descriptions are intended to present a descriptive list of the range of duties performed by employees in this class and are not intended to reflect all duties performed within the job. GENERAL FUNCTION: This is professional, technical, analytical, and customer-oriented work in the Software Development Division of the Information Technology Division of Finance. An employee in this classification provides technical expertise to Pierce County departments and agencies in multiple areas. The Software Engineer 1 may include any or all of the essential functions listed below and functions as an IT professional in the capacity of a software designer, coder, and project manager. SERIES CONCEPT: This is the first level in the series. This classification is distinguished from other IT Software Engineers by performing a narrower range of technically complex duties and the level of direction required to perform job functions. ESSENTIAL FUNCTIONS: Perform professional functions in software programming and analysis. Assist in designing, coding, testing, deploying, maintaining, enhancing, and supporting County software systems. Assist in working with business customers in translating requirements into plans and specifications. Assist in developing new software and customize, developing interfaces to, or integrating with third- party business systems. Work in a team-based environment, communicating effectively with all levels of staff and management. Collaborate on the identification of business and system requirements. Address customer’s information needs by developing technology solutions and supporting information and technology systems on multiple computing platforms.
    [Show full text]
  • Tackling Traceability Challenges Through Modeling Principles in Methodologies Underpinned by Metamodels
    Tackling Traceability Challenges through Modeling Principles in Methodologies Underpinned by Metamodels Angelina Espinoza and Juan Garbajosa Universidad Politecnica de Madrid - Technical University of Madrid, System and Software Technology Group (SYST), E.U. Informatica. Ctra. de Valencia Km. 7, E-28031, Spain, http://syst.eui.upm.es; aespinoza -at- syst.eui.upm.es, jgs -at- eui.upm.es Abstract. Traceability is recognized to be essential for supporting soft- ware development. However, a number of traceability issues are still open, such as link semantics formalization or traceability process models. Traceability methodologies underpinned by metamodels are a promis- ing approach. However current metamodels still have serious limitations. Concerning methodologies in general, three hierarchical layered levels have been identified: metamodel, methodology and project. Metamod- els do not often properly support this architecture, and that results in semantic problems at the time of specifying the methodology. Another reason is that they provide extensive predefined sets of types for describ- ing project attributes, while these project attributes are domain specific and, sometimes, even project specific. This paper introduces two com- plementary modeling principles to overcome these limitations, i.e. the metamodeling three layer hierarchy, and power-type patterns modeling principles. Mechanisms to extend and refine traceability models are in- herent to them. The paper shows that, when methodologies are developed from metamodels based on these two principles, the result is a method- ology well fitted to project features. Links semantics is also improved. Keywords: Traceability methodology, traceability metamodel, clabject, power-type pattern, metamodeling hierarchy, mechanisms for extension of traceability metamodels, metamodel extensibility. 1 Introduction Traceability is considered fundamental to perform processes and tasks such as V&V, change management, and impact analysis.
    [Show full text]
  • IT- Software Engineer Career Ladder Matrix
    IT- Software Engineer Career Ladder Matrix Software Engineer Family Job Title Software Engineer, Assoc Software Engineer Sr, Software Engineer Principal Software Engineer Mgr, Software Engineering Job Code MC0080 MC0079 MC0078 MC0074 MC0068 Pay Grade 74 75 76 76 76 Position Summary This role is responsible for all the This role is responsible for all This role is responsible for all This role is responsible for all This role is responsible for functions in all phases of applications phases of the applications phases of the applications phases of the applications providing technical leadership development. This role assists with development. This role is development. development. and mentoring a team of 10+ analysis of user needs, software and responsible for the analysis of engineers. database design, programming and life- user needs, software and cycle development of all business and database design, clinical applications. programming and life cycle development of all business and clinical applications. Essential Functions /Scope *Participate in code reviews, support *Work independently within *Provide mentoring and *Drive technology plan for the IT *Manage and lead assigned business processes, and assist in guidelines, provide technical knowledge transfer to Software organization, and ensure that plans staff. Hire, train, rate problem analysis and consultation consulting on complex projects Engineers including input to code for their assigned applications performance, and take considering equipment capacity, reviews, training and developing
    [Show full text]
  • The Conferences Start Time Table
    ETAPS DAILY 4 April 2016 ETAPS DAILY Monday | The first main conferences day | Reception | Edsger W. Dijkstra Main Conferences The conferences start Time Table 830 - 900 : opening The first day of the main ETAPS conferences will be opened 900 -1000 : invited talk by Joost-Pieter Katoen followed by the first plenary speaker, Andrew D. Gordon. 1000 -1030 : coffee break 1030 -1230: parallel sessions Title: Structure and Interpretation of Probabilistic Programs Abstract: Probabilistic programming is a technique for 1230-1400: lunch solving statistical inference and machine learning problems by writing short pieces of code to model data. We survey the area 1400-1600 : parallel sessions and describe recent advances in semantic interpretation. Probabilistic programs exhibit structures that include 1600-1630: coffee break hierarchies of random variables corresponding to the data 1630-1800: parallel sessions schema, recurring modelling patterns, and also the classical Bayesian distinction between prior and likelihood. We exploit 1900-2230: reception this structure in language designs that yield data insights with only a modicum of user input. 1 ETAPS DAILY 4 April 2016 Reception at Kazerne Kazerne is a cultural organization oriented towards creative innovation in all its activities and at an international level. But Kazerne has ambitions to be more than just an international design hotspot where everything is shiny and new. It has its roots in the belief that creativity has an essential role to play in shaping the future of society. Edsger Wybe Dijkstra Edsger Wybe Dijkstra (11 May 1930 - 6 August 2002) was one of the most influential persons in the history of the Dutch computer science.
    [Show full text]
  • Control Software Engineer
    Control Software Engineer Alternate Titles: Automation Engineer, Manufacturing Automation Engineer, Process Automation Engineer, Integration Engineer, SCADA Engineer, Application Engineer, Software Engineer, Batch Control Engineer, Systems Analyst Description: Control Software Engineers analyze user requirements, procedures, and problems to develop automation systems control configuration. They develop the functional specifications, coding strategy, logic, and control configuration structure. They develop and direct software system testing and validation procedures, and oversee all configuration and documentation. Sources of Material: Certified Automation Professional Body of Knowledge, Automation Competency Model, Control Systems Engineer (CSE) Examination Specification. Performance Domains: Domain I: Software System Design Domain II: Development Domain III: Installation and Testing Domain I: Software System Design - the conceptual design of the software to be used in control and information systems. Task 1: Establish standards, templates, and guidelines as applied to the automation system using the information gathered in the definition stage and considering human- factor effects in order to satisfy customer design criteria and preferences. Knowledge of: Process Industry Practices (PIP) (Construction Industry Institute) Programming Languages C/C++ G-Code (CNC) Visual Basic IEC - 61131 Instruction List Ladder Diagram Function block Structured Text Sequential Function Chart Electronic Device Description Language (EDDL) Vendor
    [Show full text]
  • Chapter 1: Introduction
    Just Enough Structured Analysis Chapter 1: Introduction “The beginnings and endings of all human undertakings are untidy, the building of a house, the writing of a novel, the demolition of a bridge, and, eminently, the finish of a voyage.” — John Galsworthy Over the River, 1933 www.yourdon.com ©2006 Ed Yourdon - rev. 051406 In this chapter, you will learn: 1. Why systems analysis is interesting; 2. Why systems analysis is more difficult than programming; and 3. Why it is important to be familiar with systems analysis. Chances are that you groaned when you first picked up this book, seeing how heavy and thick it was. The prospect of reading such a long, technical book is enough to make anyone gloomy; fortunately, just as long journeys take place one day at a time, and ultimately one step at a time, so long books get read one chapter at a time, and ultimately one sentence at a time. 1.1 Why is systems analysis interesting? Long books are often dull; fortunately, the subject matter of this book — systems analysis — is interesting. In fact, systems analysis is more interesting than anything I know, with the possible exception of sex and some rare vintages of Australian wine. Without a doubt, it is more interesting than computer programming (not that programming is dull) because it involves studying the interactions of people, and disparate groups of people, and computers and organizations. As Tom DeMarco said in his delightful book, Structured Analysis and Systems Specification (DeMarco, 1978), [systems] analysis is frustrating, full of complex interpersonal relationships, indefinite, and difficult.
    [Show full text]
  • A Debate on Teaching Computing Science
    Teaching Computing Science t the ACM Computer Science Conference last Strategic Defense Initiative. William Scherlis is February, Edsger Dijkstra gave an invited talk known for his articulate advocacy of formal methods called “On the Cruelty of Really Teaching in computer science. M. H. van Emden is known for Computing Science.” He challenged some of his contributions in programming languages and the basic assumptions on which our curricula philosophical insights into science. Jacques Cohen Aare based and provoked a lot of discussion. The edi- is known for his work with programming languages tors of Comwunications received several recommenda- and logic programming and is a member of the Edi- tions to publish his talk in these pages. His comments torial Panel of this magazine. Richard Hamming brought into the foreground some of the background received the Turing Award in 1968 and is well known of controversy that surrounds the issue of what be- for his work in communications and coding theory. longs in the core of a computer science curriculum. Richard M. Karp received the Turing Award in 1985 To give full airing to the controversy, we invited and is known for his contributions in the design of Dijkstra to engage in a debate with selected col- algorithms. Terry Winograd is well known for his leagues, each of whom would contribute a short early work in artificial intelligence and recent work critique of his position, with Dijkstra himself making in the principles of design. a closing statement. He graciously accepted this offer. I am grateful to these people for participating in We invited people from a variety of specialties, this debate and to Professor Dijkstra for creating the backgrounds, and interpretations to provide their opening.
    [Show full text]
  • Software Engineer, Google.Com - Mountain View
    Software Engineer, Google.com - Mountain View This position can be based in San Francisco, CA; Santa Monica, CA; Pittsburgh, PA; New York, NY or Kirkland/Seattle, WA. To apply vist: http://www.google.com/intl/en/jobs/uslocations/mountain-view/swe/software- engineer-google-com-mountain-view/index.html The area: Google.com Engineering With analytical and code-level troubleshooting abilities to spare, Google.com's engineers are technology whizzes who love being in the center of the action. We tackle a range of complex software and systems issues, including monitoring, responding to and safeguarding the availability of our most popular services. The role: Software Engineer, Google.com As a Software Engineer working on Google's critical production applications and infrastructure, your mission will be to ensure Google is always fast, available, scalable and engineered to withstand unparalleled demand. You will be in the thick of solving the [often unexpected] problems of systems at scale in a way most engineers never experience. Your scope is from the kernel level to the continent level. This position requires the flexibility and aptitude to zoom in to fine-grained detail, and the agility to zoom right back out and up the stack. Delve into how software performs, packets flow, and hardware and code interact, in support of managing services, steering global traffic and predicting and preventing failures.... all in a day's work. You will design and develop systems to run Google Search, Gmail, YouTube, Wave, Maps, Voice, AppEngine, and more. You'll manage, automate, and make data-based decisions and judgment calls which influence globally distributed applications.
    [Show full text]
  • Formalized Structured Analysis Specifications David L
    Iowa State University Capstones, Theses and Retrospective Theses and Dissertations Dissertations 1991 Formalized structured analysis specifications David L. Coleman Iowa State University Follow this and additional works at: https://lib.dr.iastate.edu/rtd Part of the Computer Sciences Commons, and the Mathematics Commons Recommended Citation Coleman, David L., "Formalized structured analysis specifications " (1991). Retrospective Theses and Dissertations. 9634. https://lib.dr.iastate.edu/rtd/9634 This Dissertation is brought to you for free and open access by the Iowa State University Capstones, Theses and Dissertations at Iowa State University Digital Repository. It has been accepted for inclusion in Retrospective Theses and Dissertations by an authorized administrator of Iowa State University Digital Repository. For more information, please contact [email protected]. INFORMATION TO USERS This manuscript has been reproduced from the microfihn master. UMI fUms the text directly &om the original or copy submitted. Thus, some thesis and dissertation copies are in typewriter face, while others may be from any type of computer printer. The quality of this reproduction is dependent upon the quality of the copy submitted. Broken or indistinct print, colored or poor quality illustrations and photographs, print bleedthrough, substandard margins, and improper alignment can adversely afifect reproduction. In the unlikely event that the author did not send UMI a complete manuscript and there are missing pages, these will be noted. Also, if unauthorized copyright material had to be removed, a note will indicate the deletion. Oversize materials (e.g., maps, drawings, charts) are reproduced by sectioning the original, beginning at the upper left-hand corner and continuing from left to right in equal sections with small overlaps.
    [Show full text]
  • Analysis of Methods TECHNICAL REPORT
    Analysis of Methods Final Report Richard J. Mayer, ed. Knowledge Based Systems Laboratory Texas A&M University March 8, 1991 w -o _0 co ! m f_ U cD C 0 Z 0 Cooperative Agreement NCC 9-16 Research Activity No. IM.06: Methodologies for Integrated 0 Information Management Systems r CDOC NASA Johnson Space Center Information Systems Directorate Information Technology Division -J • 0 _D A _OE e._ ,t C I LL -C,-- ::2" I C" m E Research Institute for Computing and Information Systems v;I _0 University of Houston-C/ear Lake TECHNICAL REPORT The RICIS Concept The University of Houston-Clear Lake established the Research lnsUtute for Computing and Information Systems (RICIS) in 1986 to encourage the NASA Johnson Space Center (JSC) and local industry to actively support research in the computing and information sciences. As part of thls endeavor. UHCL proposed a partnership with JSC to Jointly define and manage an integrated program of research in advanced data processing technology needed for JSC's main missions, including administrative, engineering and science responsi- bilities. JSC agreed and entered into a continuing cooperative agreement with UHCL beginning in May 1986, to Jointly plan and execute such research through RICIS. Additionally, under Cooperative Agreement NCC 9-16, computing and educaUonal facilities are shared by the two instituUons to conduct the research. The UHCL/RICIS mission is to conduct, coordinate, and disseminate research and professional level edueaUon in computing and information systems to serve the needs of the government, industry, community and academia. RICIS combines resources ofUHCLand Itsgateway affiliatestoresearch and develop materials, prototypes and publications on topics of mutual interest to its sponsors and researchers.
    [Show full text]