DOCSLIB.ORG

AN INTERACTIVE GRAPHICS EDITOR with INTEGRATED DATA DICTIONARY for Idefo STRUCTURED ANALYSIS DIAGRAMS

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
AN INTERACTIVE GRAPHICS EDITOR with INTEGRATED DATA DICTIONARY for Idefo STRUCTURED ANALYSIS DIAGRAMS AN INTERACTIVE GRAPHICS EDITOR WITH INTEGRATED DATA DICTIONARY FOR IDEFo STRUCTURED ANALYSIS DIAGRAMS Thomas C. Hartrum, Ted D. Connally, and Steven E. Johnson Department of Electrical and Computer Engineering School of Engineering Air Force Institute of Technology Wright-Patterson AFB, Dayton, Ohio, 45433 supports a classical process-oriented lifecycle based on the Abstract ideas in Dod Standard 2167. A standard “waterfall” model Most of the commercially available structured analysis tools are is followed, consisting of a Requirements Analysis phase, a based on data flow diagrams. However, many Government agencies, from the Air Force Materials Laboratory to the Strategic Defense Ini- Design phase, an Implementation & Testing phase, and a tiative Office depend on IDEFo diagrams, a derivative of SofTech’s Maintenance phase. Each phase is supported by database Structured Analysis and Design Technique (SADT’). This paper de- consisting of specific data dictionary entries. scribes SAlool, a graphics IDEFo editor for a SUN workstation. This paper describes a graphics tool developed to sup- An extension of the original IDEFo definition is a data dictio- nary. Entries are defined for both activities and data items, and port the Requirements Analysis phase and the integration mapped into a relational database management system (DBMS). A of that tool with a centralized relational database manage- data manager handles checking data out of the centralized DBMS in ment system. Some results of analysis of user satisfaction a format useable by the graphics editor and updating the appropriate with this tool are also presented. This paper describes relations when the data is checked back in. The data manager was developed in a generic format to support other software development the integration of these two techniques into a computer tools. automated tool SAtool for the purpose of improving the The editor and data manager, as part of the Air Force Institute software requirements analyst’s productivity. This pro- of Technology’s System 690 software development system, were used ductivity increase is possible for two significant reasons. in the development of a distributed mail system. User acceptance of the tool was measured through the use of a user survey. Results of First, several pieces of information are needed for both an this survey, as well as a description of the editor and data manager, SA diagram and the corresponding data dictionary entries. are presented in the paper. The integration of the two methods eliminates significant duplication of effort to enter the information. Second, the analyst is freed from much of the effort needed to create the diagram manually by using a tool tailored for this specific 1 Introduction purpose. SAtoolexecutes on a SUN workstation and trans- fers data dictionary information over a TCP/IP local area System 690 is the name given to the software development network (LAN) and through a data manager to a central environment under development at the Air Force Institute relational database management system on a Unix-based of Technology’s Department of Electrical and Computer Vax computer. Engineering. The goal of System 690 is to provide an integrated system in which a designer could sit down at 2 Requirements Analysis Method- a workstation, download the necessary data from a cen- tral database, work on a portion of the design, and when ology finished, upload the modified data back to the database. This data, stored in a comprehensive,centralized database, The requirements analysis phase of the software life cycle would support a system which could share data between is an important one. System 690 has established an anal- tools and provide the means to document a software project ysis methodology for this phase of the software life cycle throughout its entire life cycle. that consists of using structured analysis (SA) d’iagrams System 690 is based on a set of integrated workstation and a data dictionary. This section describes each of the tools and a central database to support a specific design components. methodology. In its current implementation, System 690 2.1 ’SA Diagrams ‘SADT is a registered trademark of SoUech, Inc The SA diagrams use a graphical language that is de- This work sponsored by SDI0 rived from the Structured Analysis and Design Technique 765 U.S. Government work not protected by U.S. copyright. AUTHOR' lEdM 4 ~O~lE.BI/BBIEB~R€~DERI I I (SADT) (SADT is a trademark of SofTech, Inc.), and are PROJECT: ECS (REV:I.I DATE accompanied by facing page text to assist in the under- optlo" standing of the diagram. Rectangular boxes and arrows are the primary graphical constructs used in an SADT di- agram. The boxes represent the decomposition of the func- tions .of the system being analyzed. The arrows are used to describe how the boxes interface between each other on the diagram. The graphical language consists of English text to label the diagram and 40 graphical constructs to describe relationships [I]. SofTech proposed that the SADT methodology could be applied to many types of problems in addition to soft- ware requirements analysis [2]. The U.S. Air Force Pro- gram for Integrated Computer Aided Manufacturing (ICAM) adopted a version of SADT from SofI'ech and called it ICAM Definition Method Zero or IDEFO. Now the Air Figure 1: Example IDEFo Diagram Force uses this similarly structured methodology to im- prove the communication of people who use computers to increase manufacturing productivity. System 690 uses the IDEFo syntax to support the re- quirements analysis phase of the software development life- cycle. A example of an IDEF, diagram as produced by NAME: mess-parts SAtoolis shown in Figure 1. PROJECT: NETOS-IS0 TYPE: PARAMETER 2.2 Data Dictionary DESCRIPTION: Decomposed message parameters. DATA TYPE: C structure or PASCAL record. The purpose of a data dictionary is to manage and docu- MIN VALUE None ment data. According to Lefkovits (Lefkovits, 1977), using MAX VALUE: None data dictionaries provides many benefits including: reduc- RANGE OF VALUES: None tion of administrative effort, reduction of data redundancy, VALUES: None and reduction of system development costs. Regarding PART OF: None software requirements analysis, Leong-Hong and Plagman COMPOSITION: suggested that data dictionaries are an excellent vehicle SRC for maintaining documentation. Furthermore, they rec- DST ommended that the data dictionary systeiii for producing QTY documentation be automated to reduce the monotony of Buffer the task. [3]. ALIAS: Message Parts In System 690, a data dictionary is established for WHERE USED: Passed to Flush Buffer. the Requirements Analysis, Design, and Implementation COMMENT: Part of existing library. phases of the software life cycle. Each of these phases con- REFERENCE: MSG-PARTS sists of a set of action entities and a set of object entities REFERENCE TYPE: SADT for a total of six types of data dictionary entries. Figure 2 VERSION: 1.2 shows a sample data dictionary entry. VERSION CHANGES: Component USE added The data dictionary entries, as can be seen from Fig- DATE: 11/05/85 ure 2, are designed to be readable by human analysts. The AUTHOR. T. C. Hartrum corresponding relational database consists of a number of CALLING PROCESS: Process Message third-normal form relations. (Figure 3 shows the schema PROCESS CALLED: DecomposeMessage for the design phase object entity). The data dictionary DIRECTION: up database contains the schema for all six data dictionary en- 1/0 PARAMETER NAME: partslist tries, and is implemented using the Ingres relational DBMS under the Unix operating system on a VAX 111785. Figure 2: Sample Design Phase Object Entity Dictionary Entry [4] 744 parameter 2. Break the input process into parts to achieve “psy- project c12 chological closure.” paname c25 3. Provide positive feedback to the user. datatype c25 papassed low c15 project c12 4. Minimize memorization required by the user. hi c15 paname c25 span c6 0 prcalling c25 5. Provide a visually pleasing display on the screen. prcalled c25 status cl 6. Minimize the response time of the tool. direction c4 padesc iopaname c25 Finally, part of the tool’s function was to provide hard- project cl 2 copy outputs of the various products maintained by the paname c25 pavalueset tool. Therefore, it was required that the tool implement a line i2 project c12 means to produce the iIDEFo diagram, the accompany- description c60 paname c25 ing facing page text, and the data dictionaries generated value c15 by the tool. paalias pahierarchy project c12 3.2 Description of the Tool paname c25 project c12 aliasname c25 hipaname c25 SAtool was designed to run of SUN workstations due to comment c60 lopaname c25 their availability. Each SUN has a large display moni- whereused c25 tor to accommodate an uncluttered user interface, and a paref mouse input device for manipulating the graphical con- pahistory project c12 structs of the IDEFo diagram. In addition, all the SUN project c12 paname c25 workstations are tied to the AFIT computer network, im- paname c25 reference c6G portant for transporting the data dictionary information version c10 reftype c25 to the central computer. Based on the availability of the date c8 SunView package and the desire to reuse certain software author c20 modules from the prototype, it was decided to proceed comment c60 with the SunView package. The tool was implemented in C because SunView supports this language. Figure 3: Database Schema for the Design Phase Object The design of an acceptable human/computer interface Entity [5] was a primary task in this effort. The screen layout con- sists of five areas or windows as shown in Figure 4. 3 SAtooZ, an Interactive Graphics Editor 3.1 Requirements Definition Requirements for this tool were based on previous research at AFIT. A prototype tool to integrate SA diagrams and data dictionaries was built at AFIT in 1986.
Load more

Recommended publications
  • INCOSE: the FAR Approach “Functional Analysis/Allocation and Requirements Flowdown Using Use Case Realizations”
    in Proceedings of the 16th Intern. Symposium of the International Council on Systems Engineering (INCOSE'06), Orlando, FL, USA, Jul 2006. The FAR Approach – Functional Analysis/Allocation and Requirements Flowdown Using Use Case Realizations Magnus Eriksson1,2, Kjell Borg1, Jürgen Börstler2 1BAE Systems Hägglunds AB 2Umeå University SE-891 82 Örnsköldsvik SE-901 87 Umeå Sweden Sweden {magnus.eriksson, kjell.borg}@baesystems.se {magnuse, jubo}@cs.umu.se Copyright © 2006 by Magnus Eriksson, Kjell Borg and Jürgen Börstler. Published and used by INCOSE with permission. Abstract. This paper describes a use case driven approach for functional analysis/allocation and requirements flowdown. The approach utilizes use cases and use case realizations for functional architecture modeling, which in turn form the basis for design synthesis and requirements flowdown. We refer to this approach as the FAR (Functional Architecture by use case Realizations) approach. The FAR approach is currently applied in several large-scale defense projects within BAE Systems Hägglunds AB and the experience so far is quite positive. The approach is illustrated throughout the paper using the well known Automatic Teller Machine (ATM) example. INTRODUCTION Organizations developing software intensive defense systems, for example vehicles, are today faced with a number of challenges. These challenges are related to the characteristics of both the market place and the system domain. • Systems are growing ever more complex, consisting of tightly integrated mechanical, electrical/electronic and software components. • Systems have very long life spans, typically 30 years or longer. • Due to reduced acquisition budgets, these systems are often developed in relatively short series; ranging from only a few to several hundred units.
    [Show full text]
  • The Roots of Software Engineering*
    THE ROOTS OF SOFTWARE ENGINEERING* Michael S. Mahoney Princeton University (CWI Quarterly 3,4(1990), 325-334) At the International Conference on the History of Computing held in Los Alamos in 1976, R.W. Hamming placed his proposed agenda in the title of his paper: "We Would Know What They Thought When They Did It."1 He pleaded for a history of computing that pursued the contextual development of ideas, rather than merely listing names, dates, and places of "firsts". Moreover, he exhorted historians to go beyond the documents to "informed speculation" about the results of undocumented practice. What people actually did and what they thought they were doing may well not be accurately reflected in what they wrote and what they said they were thinking. His own experience had taught him that. Historians of science recognize in Hamming's point what they learned from Thomas Kuhn's Structure of Scientific Revolutions some time ago, namely that the practice of science and the literature of science do not necessarily coincide. Paradigms (or, if you prefer with Kuhn, disciplinary matrices) direct not so much what scientists say as what they do. Hence, to determine the paradigms of past science historians must watch scientists at work practicing their science. We have to reconstruct what they thought from the evidence of what they did, and that work of reconstruction in the history of science has often involved a certain amount of speculation informed by historians' own experience of science. That is all the more the case in the history of technology, where up to the present century the inventor and engineer have \*-as Derek Price once put it\*- "thought with their fingertips", leaving the record of their thinking in the artefacts they have designed rather than in texts they have written.
    [Show full text]
  • A Comparative Analysis of Structured and Object-Oriented Programming Methods
    JASEM ISSN 1119-8362 Full-text Available Online at J. Appl. Sci. Environ. Manage. December, 2008 All rights reserved www.bioline.org.br/ja Vol. 12(4) 41 - 46 A Comparative Analysis of Structured and Object-Oriented Programming Methods ASAGBA, PRINCE OGHENEKARO; OGHENEOVO, EDWARD E. CPN, MNCS. Department of Computer Science, University of Port Harcourt, Port Harcourt, Nigeria. [email protected], [email protected]. 08056023566 ABSTRACT: The concepts of structured and object-oriented programming methods are not relatively new but these approaches are still very much useful and relevant in today’s programming paradigm. In this paper, we distinguish the features of structured programs from that of object oriented programs. Structured programming is a method of organizing and coding programs that can provide easy understanding and modification, whereas object- oriented programming (OOP) consists of a set of objects, which can vary dynamically, and which can execute by acting and reacting to each other, in much the same way that a real-world process proceeds (the interaction of real- world objects). An object-oriented approach makes programs more intuitive to design, faster to develop, more amenable to modifications, and easier to understand. With the traditional, procedural-oriented/structured programming, a program describes a series of steps to be performed (an algorithm). In the object-oriented view of programming, instead of programs consisting of sets of data loosely coupled to many different procedures, object- oriented programs
    [Show full text]
  • Leveraging Software Development Approaches in Systems Engineering
    Raytheon Leveraging Software Development Approaches in Systems Engineering Rick Steiner Engineering Fellow Raytheon Integrated Defense Systems [email protected] 6 May 2004 Naval Postgraduate School SI4000 Project Seminar Copyright © 2003 Raytheon Company UNPUBLISHED WORK ALL RIGHTS RESERVED 1 We’re going to talk about: Raytheon • Why Software Tools exist, why Systems Engineers should care • Software vs. SE as a discipline – key differences • The importance of requirements – Different requirement/system development approaches – Pros & cons of each, and how they relate to software approaches • How Use Cases relate to Requirements – Hints on how to manage use case development • How Object Oriented Design relates to Functional Analysis – or not! • What graphical languages can help (UML, SysML) • The promise of Model Driven Architecture (MDA) Copyright © 2003 Raytheon Company UNPUBLISHED WORK ALL RIGHTS RESERVED 2 Software Development Crisis Raytheon • In the 1980’s, software development underwent a crisis: – Software was RAPIDLY proliferating – Software was becoming very complex • Software on top of Software (OS, Application) • Software talking to Software (interfaces) – Software development delays were holding up system delivery – Software was becoming very expensive to develop and maintain – Software development effort was becoming very hard to estimate – Software reliability was becoming problematic – Existing techniques were proving inadequate to manage the problem • Reasons: – Economics • Processing hardware (silicon) got cheap –
    [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]
  • 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]
  • & Evocean Bridging the Enterprise Architecture to IT Architecture
    & Evocean Bridging the Enterprise Architecture to IT Architecture Gap Presented by Jog Raj 31st January 2008 © Telelogic AB Agenda • Introductions • The Business Challenge • What is Enterprise Architecture • Bridging the Business and IT gap • Service Orientated Architectures • Role of Tools in Architecture • Demonstration • Questions & Answers • Summary © Telelogic AB Telelogic At A Glance • Founded 1983 • HQ Malmö, Sweden • US HQ Irvine, California • Public Company Listed in 1999 • Development Sites USA, Sweden, UK, India © Telelogic AB Global Presence Over 40 offices around the world As of September 2004 © Telelogic AB Bridging the Enterprise Architecture to IT Architecture Gap © Telelogic AB Current Business Challenges • Hypercompetitive Market – Innovation – Ability to implement ideas • Mergers and Acquisitions • Governance and Compliance • Reduce Cost – Operational costs – IT Asset Management • Reuse of assets • Application Integration Costs • Risk Reduction and Mitigation © Telelogic AB A Growing Divide? Business Challenges and Opportunities Business Process Adaptability The Internet 1990s 2000s © Telelogic AB What is Enterprise Architecture? • A description of business and IT domains: – Mission, Strategy, Landscape, Organization, People, Locations – Processes, Technology, Information, Data, Applications • A description of the relationships between them • A set of graphical and textual models and artefacts that can be communicated in a common manner • An Enterprise Architecture supports an operating business in achieving its goals
    [Show full text]
  • Course Name : Structured and Object Oriented Analysis and Design
    GUJARAT TECHNOLOGICAL UNIVERSITY MASTER OF COMPUTER APPLICATIONS (MCA) Semester: III Subject: Structured & Object Oriented Analysis and Design Methodology (SOOADM) Subject Code: 630001 (W.E.F June 2012) Learning Objectives : System Analysis and Design is a practical field that relies on a core set of concepts and principles. The objective of this course is to teach the students tried-and-tested techniques widely embraced by experienced analysts plus new and emerging tools and techniques that recent graduates are expected to apply on the job. The course is meant to give balanced exposure to both traditional and object oriented approaches to system analysis & design. Prerequisites : Fundamentals of Structured Programming and Fundamentals of Object Oriented Programming Contents : 1. System Analysis Fundamentals [4 hrs.] Types of Systems, Role of the System Analyst, Systems Development Life Cycle, CASE Tools, Interviewing, Joint Application Development, Using Questionnaires 2. Analysis Modeling [10 hrs.] Data Flow Approach, Developing Data Flow Diagrams, Logical and Physical Data Flow Diagrams, Data Dictionary, Creating Data Dictionary, Using Data Dictionary, Process Specifications, Structured English, Decision Tables, Decision Trees 3. System Design [10 hrs.] Designing Effective Output, Output Design Objectives, Designing a Web Site, Form Design, Web Forms Design, Human-Computer Interaction, Types of Interfaces, Dialog Design, Designing Queries, Effective Coding, Effective Data Capture, Input Validation 4. Object Modeling Concepts [10 hrs.] Introduction, Modeling as a design technique, Class Modeling-Object and Classes, Association, Generalization, aggregation, Abstract class, Multiple inheritance, Metadata, Reification, Constraints, Derived data, Packages, State Modeling- State, Transitions and Conditions, State Diagrams, Nested state diagrams , Nested States, Signal Generalization, Concurrency 5. Basic Structural Modeling [4 hrs.] Classes, Relationships, Common Mechanisms, Diagrams, Class Diagrams 6.
    [Show full text]
  • Chap 1. Introduction to Software Architecture
    Chap 1. Introduction to Software Architecture 1. Introduction 2. IEEE Recommended Practice for Architecture Modeling 3. Architecture Description Language: the UML 4. The Rational Unified Process (RUP) 1 1. Introduction Preamble “Conventional wisdom has been to use terms like ‘software architecture’, ‘software architectural design’, or ‘coarse-grained design’ for the high-level structural subdivision of a system, and ‘design’ or ‘detailed design’ for more detailed planning… we denote the whole activity of constructing a software system as ‘software design’ and the resulting artifacts as ‘software architecture’.” “Many developers nowadays prefer the term ‘software architecture’ to ‘software design’ for denoting all the artifacts that result from design activities.” “In doing so, they want to express the fact that they do not just decompose the functionality of a system into a set of cooperating components, but rather that they construct a software architecture… They no longer agree that high-level design decisions can be made independently of lower-level decisions.” From “Pattern-Oriented Software Architecture, A System of Patterns” By F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, M. Stal 2 Software Architecture as a Design Plan Software architecture provides a design plan, a blueprint of a system, an abstraction to help manage the complexity of a system, and also a communication medium between stakeholders. Critical factor for a product’s success: good software architecture that is understood by the stakeholders and by the developers. Structural plan that describes the elements of the system, how they fit together, and how they work together to fulfill the system’s requirements. •Used to negotiate system requirements, and to set expectations with customers, marketing and management personnel.
    [Show full text]
  • Chapter 4 Structured Analysis and Functional Architecture Design
    Chapter 4 Structured Analysis and Functional Architecture Design Dr. Eng. Shady Aly 1 Modeling IIS • This is the first step in the design of IIS for an industrial enterprise. • The design proceeds from a definition of a business model of the enterprise. This business model (IS model ) is a description of – the functions of the business , – the data requirements , and – the interactions between the functions and data requirements. • Functional or activity architecture describes a conceptual model of the activities that operate the business and the relationships between those activities. 2 Modeling IIS • The word architecture denotes the fact that ون ن the model has a layered structure طت • A related conceptual model of the firm is the informational or data architecture . This is a model of the information requirements needed to perform the functions of the business. 3 Modeling IIS • There are three layers of system design to consider in an information system project: conceptual , implementation and execution • The conceptual layer consists of the logical design of function and data requirements • When a conceptual design is complete, the next step is to implement the blueprint in hardware and software. This is the implementation layer that requires the selection of a database management system, hardware platforms, and a communication medium. 4 Modeling IIS • At the execution layer, the conceptual model and implementation techniques are coded in software in terms of forms and reports • The forms and reports are used to interface with the individuals performing the functions defined in the functional architecture. 5 Layers of the information system design process 6 Functional modeling Integrated computer-aided manufacturing definition 0 (IDEF0) 7 IDEF0 Methodology modeling primitives • IDEF0 (integrated computer-aided manufacturing definition 0) is a modeling methodology for designing and documenting hierarchic , layered , modular systems .
    [Show full text]
  • SHORT HISTORY of SOFTWARE METHODS by David F. Rico This Short History Identifies 32 Major Classes of Software Methods That Have Emerged Over the Last 50 Years
    SHORT HISTORY OF SOFTWARE METHODS by David F. Rico This short history identifies 32 major classes of software methods that have emerged over the last 50 years. There are many variations of each major class of software method, which renders the number of software methods in the hundreds. This short history contains a brief synopsis of each of the 32 major classes of software methods, identifying the decade and year they appeared, their purpose, their major tenets, their strengths, and their weaknesses. The year each software method appeared corresponds to the seminal work that introduced the method based on extensive bibliographic research and the strengths and weaknesses were based on scholarly and empirical works to provide an objective capstone for each method. Mainframe Era Midrange Era Microcomputer Era Internet Era Personalized Era 1960s 1970s 1980s 1990s 2000s Flowcharting Structured Design Formal Specification Software Estimation Software Reliability Iterative/Incremental Software Inspections Structured Analysis Software Testing Configuration Control Quality Assurance Project Management Defect Prevention Process Improvement CASE Tools Object Oriented Software Reuse Rapid Prototyping Concurrent Lifecycle Software Factory Domain Analysis Quality Management Risk Management Software Architecture Software Metrics Six Sigma Buy versus Make Personal Processes Product Lines Synch-n-Stabilize Team Processes Agile Methods Market Conditions Market Conditions Market Conditions Market Conditions Market Conditions y Mainframe computer y Computer
    [Show full text]
  • A Structured Programming Approach to Data Ebook
    A STRUCTURED PROGRAMMING APPROACH TO DATA PDF, EPUB, EBOOK Coleman | 222 pages | 27 Aug 2012 | Springer-Verlag New York Inc. | 9781468479874 | English | New York, NY, United States A Structured Programming Approach to Data PDF Book File globbing in Linux. It seems that you're in Germany. De Marco's approach [13] consists of the following objects see figure : [12]. Get print book. Bibliographic information. There is no reason to discard it. No Downloads. Programming is becoming a technology, a theory known as structured programming is developing. Visibility Others can see my Clipboard. From Wikipedia, the free encyclopedia. ALGOL 60 implementation Call stack Concurrency Concurrent programming Cooperating sequential processes Critical section Deadly embrace deadlock Dining philosophers problem Dutch national flag problem Fault-tolerant system Goto-less programming Guarded Command Language Layered structure in software architecture Levels of abstraction Multithreaded programming Mutual exclusion mutex Producer—consumer problem bounded buffer problem Program families Predicate transformer semantics Process synchronization Self-stabilizing distributed system Semaphore programming Separation of concerns Sleeping barber problem Software crisis Structured analysis Structured programming THE multiprogramming system Unbounded nondeterminism Weakest precondition calculus. Comments and Discussions. The code block runs at most once. Latest Articles. Show all. How any system is developed can be determined through a data flow diagram. The result of structured analysis is a set of related graphical diagrams, process descriptions, and data definitions. Therefore, when changes are made to that type of data, the corresponding change must be made at each location that acts on that type of data within the program. It means that the program uses single-entry and single-exit elements.
    [Show full text]