DOCSLIB.ORG

Management Procedures in Computer Programming for Apollo Interim Report

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Management Procedures in Computer Programming for Apollo Interim Report TH-64-222-1 MANAGEMENT PROCEDURES IN COMPUTER PROGRAMMING INTERIM REPORT November 30, 1364 W, M, Keese - Bellcomm, Incc B, If, W, J, LicbowltzMar*tin - Bellcomm, - Bellcomm, Inc, Inc, I, D, Nehama - Bellcomm, Inc, A. I{. Scheinman - Rellcomm, Inc, C, S, Sherrerd - Bellcomm, Inc, W, C, Dennis - Computer Sciences Corporation s, E, Fliege - Computer Sciences Corporation D. A, Jackson - Computer Sciences Corporation B, J, Thielen - Computer Sciences Corporation Work Performed for Manned Space Plight, National Aeronautics and Space Administration, as part of Task 22 under Contract NASW-417, BELLCOMM, INC. TABLE OF CONTENTS Abstract Table of Contents 1. Introduction- 2. Problems in Developing Computer Programs 2.1 Lack of Definitive Requirements 2.2 Complex Interface of Elements 2 . 3 Inadequate Quaiity 2.4 Inadequate Understanding of Th.e Pro- gramming Process 2.5 Inadequate Understanding of The Cost Elements 3. Management Tools for Computer Programming 3.1 Description of The Computer programming Process 3.1.1 Understanding The. Process , 3,1,2 The Elements of a Programming Svstern ~ . I 3.1.3 Types of Computer Programming Projects 3.1.4 The Phase6 of Problem Solution 1, Definition of System Requirements 2. Definition of Performance Specifications 3. Development of Program Design 4, Program Implementation 5, System Integration 6. Program Maintenance 3.2 Policies, Procedures, and Standards 3 a 2 1 Planning 1, Role of the Information Proces- sing Specialist in Planning 2. The Software System Baseline 3* Planning, Scheduling, and Cost Estimating 3,2,2 Development of* Program Production Procedures and Standards 1, Programming Procedures and Standards A, Program Design Bo Flow Diagramming C, Program Coding Do Program Desk Checking E, Program Assembly and Modifioation BELLCOMM, INC. F Program Testing Go Documenting 2, Configuration Management A, configuration Identification Ua Configuration Control C, Configuration Accounting Documentation Requirements 1, Documentation Related to Program Requirements A, Dcflnition of Software Requirements B, Software Performance Specifications C, Development of Program Deslpp (1) Computer Program System Design Specifications (2) Basic Programming Language Manual (3) Machine-Program Interfaces Specifications (4 1 Man-Machine Interfaces Specification 2, Documcrltation Related to Program Implementation A, Individual Program Coding Descriptions B, Self-Suf'ficicncy of the Program Listina~ ~~" Co Subprogrim Interrelationships Descriptions D,2 Progress Reports Software Testing 3.3 Writing of Contracts 3.301 Contract Clauses 1, Customer Furnished Items 2, Baseline Documentation 3, Implementation Procedures and Standards 4, Planning, Scheduling and Progress Reporting 5* Deliverable Items 6, Contract Reviews 70 Acceptance Tests 80 Milestone Dates 90 costs 1Oa Change Control ., . .. BELLCOMM. INC. 3,3,2 Phases of the Programming Process and the Contract 1, Definition of System Requirements 2, Definition of Performance Speci- fications 3" Development of Program Design 4, Program Implementation 5o Systems Integration 6, Program Maintenance 304 Monitoring and Control by Management 304,1 Introduction 3,4,2 Management-Support Functions and Organizations 1, Quality Assurance Group A, The Need for Quality Assurance in Software Development Bo Responsibilities of the Group (1) Monitoring (2) Testing C, Staffing D, Independence of the Group 2, Center Programming Group 3* NASA Headquarters Programming Group A, Administrative and Monitoring Functions Bo Computer Program Status and Requirements Reviews 3.h03 Example of an Integrated Management Structure 4, Conclusions 5. Future Effort Bibliography Glossary Appendix Table 1, sheets 1 through 6 Figure 1, sheets 1 through 4 Figure 2 Figure 3 Distribution List BELLCOMM, INC. ""-> ""-> ABSTRACT This report concludes that computer programming is a describ- able, orderly process having a determinable, predictable end product, It is susceptible to close management control at the NASA center level for the purpose of delivering usable programs on schedule within estimated costs, A set of management functions and procedures is proposed, which are submitted at this time as tentative recommendations, and which will ensure control over procurement and production of computer programs for Apollo, It is recommended that: 1, A mechanism be established for the identification of computer progratnming end items, and the reporting of milestone information be made to specified levels of management 2, The contract be used as the principal instrument of NASA control of procurement and production of computer programs; standard contractual clauses be developed to assure adherence to delivery costs, documentation and production requirements, '30 The function of quality control of computer programs be implemented at the NASA center level, Groups of information processing specialists be formed at the centers and headquarters to provide a source,of programming expertise to managemento 4, Managers at all levels of Project Apollo be made aware of the computer programming process so as to better understand the requirements and costs involved, 5,, Pertinent statistics related to the production of computer programs be collected and processed to provide criteria fop measuring contractor performance and estimating expected costs,, These proposals will be examined and developed in depth, and final recommendations made in forthcoming reports, BELLCOMM, INC. MANAGEMENT PROCEDURES IN COMPUTER PROGRAMMING FOR APOLLO INTERIM REPORT 1a 0 INTRODUCTION This is the first report on Task 22 undertaken by Bellcomm at . the request of the Director of the Apollo Program for the purpose of studying,, developing and recommending management procedures in computer programming for Apollo, The conditions which gave rise to this task can be summarized as follows : The utilization of computers in the Apollo Program -- consider- ing all the technical uses, iaeo, real-time and off-line, t.0 which they will be put -- represents a twenty- to fifty-fold increase compared to the previous manned space flight programs that will have been undertaken by NASA,, Experience from similar situations indicates, without exception, that the effects on costs, manpower and management resources associated with the pro- duction of the necessary computer programs will be greater by a factor of two to five compared to the corresponding effects associated with computer hardware One of the more serious problems created by the drastic in- creases in computer usage in the Apollo Program is the problem of technic,al management of computer programming, That NASA is not alone In facing this problem is attested by the vast amount / of literature on the subject from sources in government and industry+* The underlying cause seems to be that, while the management capability available in these agencies and industrial organizations is derived from long experience with hardware systems, the experience with computer “software” has been rela- tively small, * A bibliography of articles and books discussing problems associated with computer programming and programmers is given at the end of this report, I-. .”””-.- BELLCOMM, INC. Several factors contribute in compoundlng the problems asso- ciated with computer programming in Apollo, One factor is the size .of the effort involved. It has been estimated that a total of more than five million machine language instructions will hqve to be produced, Another factor is that responsibility for computer programs in Apollo is apread over four NASA Space Flight Centers: GSFC, KSC, MSC and MSFC, Eighteen operationaJ* programming systems associated with these Centers have been identified (see Table l), These programs do not constitute complete systems by themselves, but are intended to perform certain functions in conjunction with other systems for the accomplishment of a mission. The specification of requirements for these programs, perhaps the most. important initial step in tlfe process, is the responsibility o.f the "ultimate user" -- in general, not an information processing specialist -- in the Center. It is the thesis of this report that the problems of technical management of computer programming can be solved, and that work- ing, well-documented programs can be delivered on time within estimated costs; that management tools useful at the project level in the Centers can be developed and imp1emented.to insure control over production of computer programs; and that .'informa- tion reporting schemes can be established so that ma,nagement at a11 levels in NASA can be made aware of, and reac't to problems related to computer programming, The report includes a broad discussion of the major ordered activities and elements of the computer programming process involved in a large-scale programming effort, such as will be required in Apollo,' From this broad treatment, a number of tentative conclusions are drawn concerning the type of manage- ment procedures needed, and means of implementing them in the NASA environment. The concept of quality control in program- ming is also introduced, Some important management functions are described in terms of a hypothetical organization structure for purposes of illustration on,ly, and are not intended to be final recommendations at this time, The tentative conclusions presented in this report will be examined in detail in the continuing effort on this task, and recommendations will be made in a series of forthcoming reports, * For definitions of some of the special terms used in this report, see
Load more

Recommended publications
  • CMPS 161 – Algorithm Design and Implementation I Current Course Description
    CMPS 161 – Algorithm Design and Implementation I Current Course Description: Credit 3 hours. Prerequisite: Mathematics 161 or 165 or permission of the Department Head. Basic concepts of computer programming, problem solving, algorithm development, and program coding using a high-level, block structured language. Credit may be given for both Computer Science 110 and 161. Minimum Topics: • Fundamental programming constructs: Syntax and semantics of a higher-level language; variables, types, expressions, and assignment; simple I/O; conditional and iterative control structures; functions and parameter passing; structured decomposition • Algorithms and problem-solving: Problem-solving strategies; the role of algorithms in the problem- solving process; implementation strategies for algorithms; debugging strategies; the concept and properties of algorithms • Fundamental data structures: Primitive types; single-dimension and multiple-dimension arrays; strings and string processing • Machine level representation of data: Bits, bytes and words; numeric data representation; representation of character data • Human-computer interaction: Introduction to design issues • Software development methodology: Fundamental design concepts and principles; structured design; testing and debugging strategies; test-case design; programming environments; testing and debugging tools Learning Objectives: Students will be able to: • Analyze and explain the behavior of simple programs involving the fundamental programming constructs covered by this unit. • Modify and expand short programs that use standard conditional and iterative control structures and functions. • Design, implement, test, and debug a program that uses each of the following fundamental programming constructs: basic computation, simple I/O, standard conditional and iterative structures, and the definition of functions. • Choose appropriate conditional and iteration constructs for a given programming task. • Apply the techniques of structured (functional) decomposition to break a program into smaller pieces.
    [Show full text]
  • Skepu 2: Flexible and Type-Safe Skeleton Programming for Heterogeneous Parallel Systems
    Int J Parallel Prog DOI 10.1007/s10766-017-0490-5 SkePU 2: Flexible and Type-Safe Skeleton Programming for Heterogeneous Parallel Systems August Ernstsson1 · Lu Li1 · Christoph Kessler1 Received: 30 September 2016 / Accepted: 10 January 2017 © The Author(s) 2017. This article is published with open access at Springerlink.com Abstract In this article we present SkePU 2, the next generation of the SkePU C++ skeleton programming framework for heterogeneous parallel systems. We critically examine the design and limitations of the SkePU 1 programming interface. We present a new, flexible and type-safe, interface for skeleton programming in SkePU 2, and a source-to-source transformation tool which knows about SkePU 2 constructs such as skeletons and user functions. We demonstrate how the source-to-source compiler transforms programs to enable efficient execution on parallel heterogeneous systems. We show how SkePU 2 enables new use-cases and applications by increasing the flexibility from SkePU 1, and how programming errors can be caught earlier and easier thanks to improved type safety. We propose a new skeleton, Call, unique in the sense that it does not impose any predefined skeleton structure and can encapsulate arbitrary user-defined multi-backend computations. We also discuss how the source- to-source compiler can enable a new optimization opportunity by selecting among multiple user function specializations when building a parallel program. Finally, we show that the performance of our prototype SkePU 2 implementation closely matches that of
    [Show full text]
  • Software Requirements Implementation and Management
    Software Requirements Implementation and Management Juho Jäälinoja¹ and Markku Oivo² 1 VTT Technical Research Centre of Finland P.O. Box 1100, 90571 Oulu, Finland [email protected] tel. +358-40-8415550 2 University of Oulu P.O. Box 3000, 90014 University of Oulu, Finland [email protected] tel. +358-8-553 1900 Abstract. Proper elicitation, analysis, and documentation of requirements at the beginning of a software development project are considered important preconditions for successful software development. Furthermore, successful development requires that the requirements be correctly implemented and managed throughout the rest of the development. This latter success criterion is discussed in this paper. The paper presents a taxonomy for requirements implementation and management (RIM) and provides insights into the current state of these practices in the software industry. Based on the taxonomy and the industrial observations, a model for RIM is elaborated. The model describes the essential elements needed for successful implementation and management of requirements. In addition, three critical elements of the model with which the practitioners are currently struggling are discussed. These elements were identified as (1) involvement of software developers in system level requirements allocation, (2) work product verification with reviews, and (3) requirements traceability. Keywords: Requirements engineering, software requirements, requirements implementation, requirements management 1/9 1. INTRODUCTION Among the key concepts of efficient software development are proper elicitation, analysis, and documentation of requirements at the beginning of a project and correct implementation and management of these requirements in the later stages of the project. In this paper, the latter issue related to the life of software requirements beyond their initial development is discussed.
    [Show full text]
  • Efficient High-Level Parallel Programming
    Theoretical Computer Science EISEVIER Theoretical Computer Science 196 (1998) 71-107 Efficient high-level parallel programming George Horaliu Botoroga,*,‘, Herbert Kuchenb aAachen University of Technology, Lehrstuhl fiir Informatik IL Ahornstr. 55, D-52074 Aachen, Germany b University of Miinster, Institut fir Wirtschaftsinformatik, Grevener Str. 91, D-48159 Miinster, Germany Abstract Algorithmic skeletons are polymorphic higher-order functions that represent common parallel- ization patterns and that are implemented in parallel. They can be used as the building blocks of parallel and distributed applications by embedding them into a sequential language. In this paper, we present a new approach to programming with skeletons. We integrate the skeletons into an imperative host language enhanced with higher-order functions and currying, as well as with a polymorphic type system. We thus obtain a high-level programming language, which can be implemented very efficiently. We then present a compile-time technique for the implementation of the functional features which has an important positive impact on the efficiency of the language. Afier describing a series of skeletons which work with distributed arrays, we give two examples of parallel algorithms implemented in our language, namely matrix multiplication and Gaussian elimination. Run-time measurements for these and other applications show that we approach the efficiency of message-passing C up to a factor between 1 and 1.5. @ 1998-Elsevier Science B.V. All rights reserved Keywords: Algorithmic skeletons; High-level parallel programming; Efficient implementation of functional features; Distributed arrays 1. Introduction Although parallel and distributed systems gain more and more importance nowadays, the state of the art in the field of parallel software is far from being satisfactory.
    [Show full text]
  • Map, Reduce and Mapreduce, the Skeleton Way$
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Elsevier - Publisher Connector Procedia Computer Science ProcediaProcedia Computer Computer Science Science 00 1 (2010)(2012) 1–9 2095–2103 www.elsevier.com/locate/procedia International Conference on Computational Science, ICCS 2010 Map, Reduce and MapReduce, the skeleton way$ D. Buonoa, M. Daneluttoa, S. Lamettia aDept. of Computer Science, Univ. of Pisa, Italy Abstract Composition of Map and Reduce algorithmic skeletons have been widely studied at the end of the last century and it has demonstrated effective on a wide class of problems. We recall the theoretical results motivating the intro- duction of these skeletons, then we discuss an experiment implementing three algorithmic skeletons, a map,areduce and an optimized composition of a map followed by a reduce skeleton (map+reduce). The map+reduce skeleton implemented computes the same kind of problems computed by Google MapReduce, but the data flow through the skeleton is streamed rather than relying on already distributed (and possibly quite large) data items. We discuss the implementation of the three skeletons on top of ProActive/GCM in the MareMare prototype and we present some experimental obtained on a COTS cluster. ⃝c 2012 Published by Elsevier Ltd. Open access under CC BY-NC-ND license. Keywords: Algorithmic skeletons, map, reduce, list theory, homomorphisms 1. Introduction Algorithmic skeletons have been around since Murray Cole’s PhD thesis [1]. An algorithmic skeleton is a paramet- ric, reusable, efficient and composable programming construct that exploits a well know, efficient parallelism exploita- tion pattern. A skeleton programmer may build parallel applications simply picking up a (composition of) skeleton from the skeleton library available, providing the required parameters and running some kind of compiler+run time library tool specific of the target architecture at hand [2].
    [Show full text]
  • Cleanroom Software Engineering Implementation of the Capability Maturity Model (Cmmsm) for Software
    Technical Report CMU/SEI-96-TR-023 ESC-TR-96-023 Cleanroom Software Engineering Implementation of the Capability Maturity Model (CMMsm) for Software Richard C. Linger Mark C. Paulk Carmen J. Trammell December 1996 Technical Report CMU/SEI-96-TR-023 ESC-TR-96-023 December 1996 Cleanroom Software Engineering Implementation of the Capability Maturity Model (CMMsm) for Software Richard C. Linger Mark C. Paulk Software Engineering Institute Carmen J. Trammell University of Tennessee Process Program Unlimited distribution subject to the copyright Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 This report was prepared for the SEI Joint Program Office HQ ESC/AXS 5 Eglin Street Hanscom AFB, MA 01731-2116 The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange. FOR THE COMMANDER (signature on file) Thomas R. Miller, Lt Col, USAF SEI Joint Program Office This work is sponsored by the U.S. Department of Defense. Copyright © 1996 by Carnegie Mellon University. Permission to reproduce this document and to prepare derivative works from this document for internal use is granted, provided the copyright and “No Warranty” statements are included with all reproductions and derivative works. Requests for permission to reproduce this document or to prepare derivative works of this document for external and commercial use should be addressed to the SEI Licensing Agent. NO WARRANTY THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL.
    [Show full text]
  • Computer Science (CS) Implementation Guidance
    Computer Science (CS) Implementation Guidance Landscape of Computer Science CS for AZ: Leaders CS Toolbox: Curricula and Tools Document prepared by Janice Mak Note: The following document contains examples of resources for elementary school, middle school, and high school. These resources are not explicitly recommended or endorsed by the Arizona Department of Education. The absence of a resource from this does not indicate its value. 1 of 43 Computer Science (CS) Implementation Guidance Table of Contents Overview and Purpose ..........................................................................................2 Introduction: Landscape of Computer Science ......................................................2 Arizona Challenge .........................................................................................3 Recommendations ........................................................................................3 A Brief Introduction: AZ K-12 Computer Science Standards ..................... 5-6 CS for AZ: Leaders................................................................................................7 Vision ............................................................................................................7 Data Collection and Goal-Setting ............................................................. 7-8 Plan ...............................................................................................................9 CS Toolbox: Curricula and Tools .......................................................................
    [Show full text]
  • Software Design Pattern Using : Algorithmic Skeleton Approach S
    International Journal of Computer Network and Security (IJCNS) Vol. 3 No. 1 ISSN : 0975-8283 Software Design Pattern Using : Algorithmic Skeleton Approach S. Sarika Lecturer,Department of Computer Sciene and Engineering Sathyabama University, Chennai-119. [email protected] Abstract - In software engineering, a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved. Many patterns imply object-orientation or more generally mutable state, and so may not be as applicable in functional programming languages, in which data is immutable Fig 1. Primary design pattern or treated as such..Not all software patterns are design patterns. For instance, algorithms solve 1.1Attributes related to design : computational problems rather than software design Expandability : The degree to which the design of a problems.In this paper we try to focous the system can be extended. algorithimic pattern for good software design. Simplicity : The degree to which the design of a Key words - Software Design, Design Patterns, system can be understood easily. Software esuability,Alogrithmic pattern. Reusability : The degree to which a piece of design can be reused in another design. 1. INTRODUCTION Many studies in the literature (including some by 1.2 Attributes related to implementation: these authors) have for premise that design patterns Learn ability : The degree to which the code source of improve the quality of object-oriented software systems, a system is easy to learn.
    [Show full text]
  • 5 Programming Language Implementation
    5 Programming Language Implementation Program ®le for this chapter: pascal We are now ready to turn from the questions of language design to those of compiler implementation. A Pascal compiler is a much larger programming project than most of the ones we've explored so far. You might well ask, ªwhere do we begin in writing a compiler?º My goal in this chapter is to show some of the parts that go into a compiler design. A compiler translates programs from a language like Pascal into the machine language of some particular computer model. My compiler translates into a simpli®ed, simulated machine language; the compiled programs are actually carried out by another Logo program, the simulator, rather than directly by the computer hardware. The advantage of using this simulated machine language is that this compiler will work no matter what kind of computer you have; also, the simpli®cations in this simulated machine allow me to leave out many confusing details of a practical compiler. Our machine language is, however, realistic enough to give you a good sense of what compiling into a real machine language would be like; it's loosely based on the MIPS microprocessor design. You'll see in a moment that most of the structure of the compiler is independent of the target language, anyway. Here is a short, uninteresting Pascal program: program test; procedure doit(n:integer); begin writeln(n,n*n) end; begin doit(3) end. 209 If you type this program into a disk ®le and then compile it using compile as described in Chapter 4, the compiler will translate
    [Show full text]
  • Skeleton Programming for Heterogeneous GPU-Based Systems
    Linköping Studies in Science and Technology Thesis No. 1504 Skeleton Programming for Heterogeneous GPU-based Systems by Usman Dastgeer Submitted to Linköping Institute of Technology at Linköping University in partial fulfilment of the requirements for degree of Licentiate of Engineering Department of Computer and Information Science Linköping universitet SE-581 83 Linköping, Sweden Linköping 2011 Copyright c 2011 Usman Dastgeer [except Chapter 4] Copyright notice for Chapter 4: c ACM, 2011. This is a minor revision of the work published in Proceedings of the Fourth International Workshop on Multicore Software Engineering (IWMSE’11), Honolulu, Hawaii, USA , 2011, http://doi.acm.org/10.1145/ 1984693.1984697. ACM COPYRIGHT NOTICE. Copyright c 2011 by the Association for Computing Machinery, Inc. Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, to republish, to post on servers, or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from Publications Dept., ACM, Inc., fax +1 (212) 869-0481, or [email protected]. ISBN 978-91-7393-066-6 ISSN 0280–7971 Printed by LiU Tryck 2011 URL: http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-70234 Skeleton Programming for Heterogeneous GPU-based Systems by Usman Dastgeer October 2011 ISBN 978-91-7393-066-6 Linköping Studies in Science and Technology Thesis No.
    [Show full text]
  • Theory of Computational Implementation
    A Theory of Computational Implementation Michael Rescorla Abstract: I articulate and defend a new theory of what it is for a physical system to implement an abstract computational model. According to my descriptivist theory, a physical system implements a computational model just in case the model accurately describes the system. Specifically, the system must reliably transit between computational states in accord with mechanical instructions encoded by the model. I contrast my theory with an influential approach to computational implementation espoused by Chalmers, Putnam, and others. I deploy my theory to illuminate the relation between computation and representation. I also address arguments, propounded by Putnam and Searle, that computational implementation is trivial. §1. The physical realization relation Physical computation occupies a pivotal role within contemporary science. Computer scientists design and build machines that compute, while cognitive psychologists postulate that the mental processes of various biological creatures are computational. To describe a physical system’s computational activity, scientists typically offer a computational model, such as a Turing machine or a finite state machine. Computational models are abstract entities. They are not located in space or time, and they do not participate in causal interactions. Under certain circumstances, a physical system realizes or implements an abstract computational model. Which circumstances? What is it for a physical system to realize a computational model? When does a 2 concrete physical entity --- such as a desktop computer, a robot, or a brain --- implement a given computation? These questions are foundational to any science that studies physical computation. Over the past few decades, philosophers have offered several theories of computational implementation.
    [Show full text]
  • Implementation Phase During Software Development Life Cycle: Interpreting Tools and Methods
    Youssef Zerkani Implementation Phase during Software Development Life Cycle Interpreting Tools and Methods Helsinki Metropolia University of Applied Sciences Bachelor of Engineering Information Technology Thesis 10 May 2017 Abstract Author(s) Youssef Zerkani Title Implementation Phase during Software Development Life Cycle: Interpreting Tools and Methods Number of Pages 40 pages + 1 appendix Date 10 May 2017 Degree Bachelor of Engineering Degree Programme Information Technology Specialisation option Software Engineering Instructor(s) Jenni Alasuutari, Supervisor Patrick Ausderau, Senior Lecturer The purpose of the project was to describe the methods used during the implementation phase of a piece of software. The main idea of the project was to introduce a package of information about the technologies and frameworks such as CakePHP, JavaScript and Boot- strap that help building a software application. During this project, a search engine application was developed from a previous version by the Bookndo company. A pre-analysis of the old version was made in order to understand more about the main technologies. The goal of the project was to ameliorate the application by manual testing and make manipulating code easier. As an outcome, designs were updated and new ideas were discussed to improve the soft- ware. The thesis presents the technologies used and the final results. In conclusion, code reusability and testing are the main fundamental elements to improve the software. The technologies that were utilized to improve the software, such
    [Show full text]