Design and Production in Software Engineering

Design and Production in Software Engineering

1. Naur

   • Profiles of software designers and producers
     • No Distinction
       • Production
       • Design
         • Properly Belong
           • Performance of the software system
             • Include Decisions

2. Dijkstra

   • If you have your production group
     • it must produce something
       • thing produced has to be
         • Correct
         • Good
   • ability to convince
     • users
     • yourself
     • Product is good
       • Is intertwined
         • Design process

3. Kinslow

   • Design Process is iterative
     • Flowchart
       • Understand the problem
     • Write code
       • Realize that you don´t
     • Go Back
       • do the flowchart
     • Write
       • Some more code
         • Feel is the correct solution

4. Ross

   • Most deadly in software
     • Is the concept
       • specify what you are going to do
         • Then do it
   • Specifications
     • based upon designers ignorance
       • Before they started the job

5. ·

   • THE NATURE OF SOFTWARE ENGINEERING
     • Perlis
       • A feedback loop is required.
         • Monitor the system
         • Collect system data
         • Make future improvements
     • Fraser
       • Design and execution in stages
         • A usable product is created
         • Products of successive stages
         • Final design requirements
         • Program of usable objects
     • Galler
       • Language designers
         • Implementors should not
         • Implement the desired extensions
     • Selig
       • External specifications
         • Describe the software product
       • The internal design
         • Describe the software product
         • Terms of program structures
       • The internal specifications
         • Implementation process
     • d’Agapeyeff
       • Application programs
         • Middleware
           • Service Routines
             • Control program
               • Compilers
               • Assemblers
   • SOFTWARE ENGINEERING AND SOCIETY
     • SOFTWARE DEVELOPMENT
       • INVESTMENTS IN GROWTH
         • T.J. Watson
           • TSS / 360
             • 1000 MAN-YEARS
           • OS / 360
             • 5000 YEAR – MEN INVESMENT
             • MORE OF $50,000,000
             • USE COMPLEX SYSTEMS
             • IT IS USED IN MANY SOPHISTICATED APPLICATIONS
       • GROWTH RATE
         • 10000 INSTALLED COMPUTERS
         • 25% – 50 %
         • 1000 – 2000 PROGRAMMERS
       • CENTRAL PROBLEMS
         • PRODUCTION PROCESS
           • The construction of the program
           • Identify the nature of progress
           • Final Product
     • SOFTWARE ENGINEERING MANAGEMENT AND METHODOLOGY
       • Kolence
         • Software design techniques
         • Software management problems
       • D’Agapeyeff
         • Costs reduction
         • Structure and execution flow
         • Modules and environment for analysis
         • Run-time simulation
       • Kinslow
         • Two kinds of systems designer
         • Solve problems one by one
         • Proposes solution to single problem
       • Berghuis
         • Independent software packages do not exist
         • Point of view of systems development
       • Harr
         • Review the program design process
         • Activities require production
           • Documentation
           • Tests
           • Running program
         • No matter the programming task
         • Steps to follow
           • The design process
             • Full hardware and software specification
             • Design and documentation of master plan
             • Fundamental data formulated and defined
             • Each block design, coding, and documentation
             • Compilation and hand check
             • Test and evaluation
             • Final load test
             • Define functions that perform the program
             • Subdivision in manageable blocks
             • Basic defined and documented subroutines
             • Design and documentation of test methods
             • Simulation using test methods
             • Integration of complete program
           • Organization used in the design process
             • Structure of the programming groups
               • Organization of program groups (1961)
                 • System planning and requirements dept.
                 • System program design dept.
                 • Total 70 program designers
               • Organization of program groups (1963)
                 • ESS Requirements
                 • ESS Program design
                 • ESS Maintenance program
                 • Total 130 program designers
             • Types of personnel
               • Two-years trade school graduates
               • B.S.
               • M.S.
               • Ph.D’s in Electrical Engineering and Mathematics
             • Communications within and between programming groups
               • Group meetings on design specifications
               • Formal program design specifications
               • Informal engineering and programming memoranda
               • Program characterization data
               • Formal program documentation
             • Control and measurement of programmer’s output
           • Program Documentation
             • Methods and standards
             • Preparation and updating
           • Development of general purpose computer tools
             • A macro-compiler, assembler and loader
             • Parameter compiler
             • Simulators
               • Studying traffic and real-time capabilities
               • Testing hardware design
             • Translation data assembler
             • Summary of general purpose computer support
           • Program test and evaluation support programs
             • Simulation on a general purpose machine
             • On the system itself
               • First by program blocks
               • Second by program functions
               • A complete hardware software system
     • quotes of software engineering conference
       • On testing software
         • should be automated
         • should list the interfaces and tables
         • each test should list the modules it has exercised
         • is important to document success or failure
       • On the production of software
         • Large systems must evolve
         • cannot be produced all at one time
       • observations
         • observations
           • operating system developments may depend on new hardware
           • microprogramming high-level language compiler
         • Barton
           • in design we should start by designing hardware and software
           • This will require a a computer engineer
       • On the management of software projects
       • On the distinction between design and production
         • is essentially a practical