DOCSLIB.ORG

Universidad Americana Facultad De Ingeniería

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Universidad Americana Facultad De Ingeniería UNIVERSIDAD AMERICANA FACULTAD DE INGENIERÍA Diseño y desarrollo de un Sistema de registro y control de socios, usuarios y aranceles de la sociedad de gestión NICAUTOR Br. María Gabriela Conrado García. Monografía para optar al grado de: Ingeniero en Sistemas Profesor tutor: Ing. Pablo Hurtado Managua, Nicaragua, Junio, 2008 Dedicatoria El presente trabajo está dedicado a los seres más importantes de mi vida: En primer lugar a Dios, puesto que el me concedió la vida y sabiduría necesaria para elaborarlo, En segundo lugar a mi madre a quien le debo todo lo que soy, En tercer lugar a mi sobrina Hillary, quien con su nacimiento ha inspirado mis deseos de superarme. Agradecimiento Son muchas las personas que han influido en la culminación de este logro, sin embargo quiero hacer referencia a las siguientes: Dios en primer lugar, quien ha sido el motor de mi vida, la luz que guía mi sendero y el proveedor de todas las bendiciones que han llegado a mi vida. Gracias Jesucristo por permitirme cumplir una mas de mis metas. A mi madre, con quien tengo una deuda in cuantificable, ya que con sacrificio y esmero me proveyó no solo de bienes materiales sino de amor, comprensión y apoyo. Este logro también es de ella. A mi tutor el Ingeniero Pablo hurtado quien me apoyo en todo momento compartiendo conmigo sus conocimientos y brindándome su ayuda incondicional no dudando en ningún momento de mi capacidad. A todos mis amigos quienes han compartido conmigo largas horas de sacrificio y abnegación, apoyándome cuando las inclemencias de la vida me sacudieron con mayor fuerza. Índice I. INTRODUCCIÓN .............................................................................................................................. - 6 - II. OBJETIVOS ....................................................................................................................................... - 9 - II.1 OBJETIVOS GENERALES: ...................................................................................................................... - 9 - II.2 OBJETIVOS ESPECÍFICOS: ..................................................................................................................... - 9 - III. MARCO TEÓRICO .................................................................................................................... - 10 - III.I TECNOLOGÍAS DE INFORMACIÓN ............................................................................................- 10 - III.I.1 Definición ................................................................................................................................. - 10 - III.I.2. El desarrollo de la tecnología de la información. ................................................................... - 11 - III.I.3. Importancia de las tecnologías de Información ...................................................................... - 13 - III.2 SOFTWARE .....................................................................................................................................- 15 - III.2.1 Definición ................................................................................................................................ - 15 - III.2.2 Tipología .................................................................................................................................. - 16 - III.2.3 Diversas Formas que adopta un software ............................................................................... - 17 - III.2.4 El software Libre y No Libre ................................................................................................... - 18 - III.2.4.1. Software libre....................................................................................................................... - 18 - III.2.4.2. Software no libre .................................................................................................................. - 19 - III.2.5. Etapas de desarrollo del software .......................................................................................... - 20 - III.3 PROGRAMACIÓN ORIENTADA A OBJETOS ............................................................................- 24 - III.3.1 Origen ...................................................................................................................................... - 25 - III.3.2 Conceptos Básicos ................................................................................................................... - 27 - III.3.3 Diferencias con la programación estructurada ....................................................................... - 30 - III.3.4 La Programación Orientada a Objetos (POO) como solución ............................................... - 32 - III.3.5 Ventajas de un lenguaje orientado a objetos ........................................................................... - 33 - III.3.6 Características de la POO ....................................................................................................... - 34 - III.4 HERRAMIENTAS DE DESARROLLO DEL SOFTWARE ...........................................................- 35 - III.4.1 El Lenguaje Unificado De Modelado (UML) .......................................................................... - 35 - III.4.1.1 Principales Beneficios De UML ........................................................................................... - 37 - III.4.1.2 UML, ¿Método o Lenguaje de Modelado? ........................................................................... - 37 - III.4.1.3 Fases Del Desarrollo De Un Sistema Basados En UML ...................................................... - 39 - III.4.1.4 Software libre para modelado en UML ................................................................................ - 41 - III.4.1.5 Software gratuito para modelado en UML ........................................................................... - 42 - III.4.2 Enterprise Architect ................................................................................................................. - 42 - III.5 LENGUAJES DE PROGRAMACIÓN ............................................................................................- 44 - III.5.1 Clasificación De Los Lenguajes De Programación................................................................. - 45 - III.5.2 Personal Home Page Tools (PHP) .......................................................................................... - 49 - III.5.2.1 Versiones de PHP. ................................................................................................................ - 51 - III.5.2.2 Aplicabilidad de PHP ........................................................................................................... - 54 - III.5.2.3 Ventajas de PHP ................................................................................................................... - 54 - III.6 BASE DE DATOS ............................................................................................................................- 55 - III.6.1 Historia .................................................................................................................................... - 55 - III.6.1.2 Lenguajes de programación ................................................................................................. - 56 - III.6.1.3 Aplicaciones .......................................................................................................................... - 56 - III.6.1.4 Especificaciones ................................................................................................................... - 57 - III.7 REDES .............................................................................................................................................- 59 - III.7.1 TIPOS ...................................................................................................................................... - 59 - III.7.2 CARACTERÍSTICAS ...................................................................................................................- 60 - III.7.3 APLICACIONES ...................................................................................................................... - 61 - III.8 ESTUDIO DE FACTIBILIDAD ......................................................................................................- 62 - IV. HIPÓTESIS .......................................................................................................................................... - 67 - V. DISEÑO METODOLÓGICO .............................................................................................................. - 68 - VI. FORMULACIÓN DE LOS REQUERIMIENTOS DE LA SOCIEDAD DE GESTIÓN NICAUTOR. ............................................................................................................................................... - 70 - Prólogo ............................................................................................................................................... - 71 - Descripción Situación actual .............................................................................................................. - 72 - Lista de Requerimientos. .................................................................................................................... - 75 - Alcances .............................................................................................................................................. - 82 - Limitaciones ......................................................................................................................................
Load more

Recommended publications
  • Java (Programming Langua a (Programming Language)
    Java (programming language) From Wikipedia, the free encyclopedialopedia "Java language" redirects here. For the natural language from the Indonesian island of Java, see Javanese language. Not to be confused with JavaScript. Java multi-paradigm: object-oriented, structured, imperative, Paradigm(s) functional, generic, reflective, concurrent James Gosling and Designed by Sun Microsystems Developer Oracle Corporation Appeared in 1995[1] Java Standard Edition 8 Update Stable release 5 (1.8.0_5) / April 15, 2014; 2 months ago Static, strong, safe, nominative, Typing discipline manifest Major OpenJDK, many others implementations Dialects Generic Java, Pizza Ada 83, C++, C#,[2] Eiffel,[3] Generic Java, Mesa,[4] Modula- Influenced by 3,[5] Oberon,[6] Objective-C,[7] UCSD Pascal,[8][9] Smalltalk Ada 2005, BeanShell, C#, Clojure, D, ECMAScript, Influenced Groovy, J#, JavaScript, Kotlin, PHP, Python, Scala, Seed7, Vala Implementation C and C++ language OS Cross-platform (multi-platform) GNU General Public License, License Java CommuniCommunity Process Filename .java , .class, .jar extension(s) Website For Java Developers Java Programming at Wikibooks Java is a computer programming language that is concurrent, class-based, object-oriented, and specifically designed to have as few impimplementation dependencies as possible.ble. It is intended to let application developers "write once, run ananywhere" (WORA), meaning that code that runs on one platform does not need to be recompiled to rurun on another. Java applications ns are typically compiled to bytecode (class file) that can run on anany Java virtual machine (JVM)) regardless of computer architecture. Java is, as of 2014, one of tthe most popular programming ng languages in use, particularly for client-server web applications, witwith a reported 9 million developers.[10][11] Java was originallyy developed by James Gosling at Sun Microsystems (which has since merged into Oracle Corporation) and released in 1995 as a core component of Sun Microsystems'Micros Java platform.
    [Show full text]
  • Thesis.Pdf (PDF, 656Kb)
    Extending old languages for new architectures Leo P. White University of Cambridge Computer Laboratory Queens' College October 2012 This dissertation is submitted for the degree of Doctor of Philosophy Declaration This dissertation is the result of my own work and includes nothing which is the outcome of work done in collaboration except where specifically indicated in the text. This dissertation does not exceed the regulation length of 60 000 words, including tables and footnotes. Extending old languages for new architectures Leo P. White Summary Architectures evolve quickly. The number of transistors available to chip designers doubles every 18 months, allowing increasingly complex architectures to be developed on a single chip. Power dissipation issues have forced chip designers to look for new ways to use the transistors at their disposal. This situation inevitably leads to new architectural features on a fairly regular basis. Enabling programmers to benefit from these new architectural features can be problematic. Since architectures change frequently, and compilers last for a long time, it is clear that compilers should be designed to be extensible. This thesis argues that to support evolving architectures a compiler should support the creation of high-level language extensions. In particular, it must support extending the compiler's middle-end. We describe the design of EMCC, a C compiler that allows extension of its front-, middle- and back-ends. OpenMP is an extension to the C programming language to support parallelism. It has recently added support for task-based parallelism, a dynamic form of parallelism made popular by Cilk. However, implementing task-based parallelism efficiently requires much more involved program transformation than the simple static parallelism originally supported by OpenMP.
    [Show full text]
  • Evaluation of On-Ramp Control Algorithms
    CALIFORNIA PATH PROGRAM INSTITUTE OF TRANSPORTATION STUDIES UNIVERSITY OF CALIFORNIA, BERKELEY Evaluation of On-ramp Control Algorithms Michael Zhang, Taewan Kim, Xiaojian Nie, Wenlong Jin University of California, Davis Lianyu Chu, Will Recker University of California, Irvine California PATH Research Report UCB-ITS-PRR-2001-36 This work was performed as part of the California PATH Program of the University of California, in cooperation with the State of California Business, Transportation, and Housing Agency, Department of Transportation; and the United States Department of Transportation, Federal Highway Administration. The contents of this report reflect the views of the authors who are responsible for the facts and the accuracy of the data presented herein. The contents do not necessarily reflect the official views or policies of the State of California. This report does not constitute a standard, specification, or regulation. Final Report for MOU 3013 December 2001 ISSN 1055-1425 CALIFORNIA PARTNERS FOR ADVANCED TRANSIT AND HIGHWAYS Evaluation of On-ramp Control Algorithms September 2001 Michael Zhang, Taewan Kim, Xiaojian Nie, Wenlong Jin University of California at Davis Lianyu Chu, Will Recker PATH Center for ATMS Research University of California, Irvine Institute of Transportation Studies One Shields Avenue University of California, Davis Davis, CA 95616 ACKNOWLEDGEMENTS Technical assistance on Paramics simulation from the Quadstone Technical Support sta is also gratefully acknowledged. ii EXECUTIVE SUMMARY This project has three objectives: 1) review existing ramp metering algorithms and choose a few attractive ones for further evaluation, 2) develop a ramp metering evaluation framework using microscopic simulation, and 3) compare the performances of the selected algorithms and make recommendations about future developments and eld tests of ramp metering systems.
    [Show full text]
  • The Convergence of Modeling and Programming
    The Convergence of Modeling and Programming: Facilitating the Representation of Attributes and Associations in the Umple Model-Oriented Programming Language by Andrew Forward PhD Thesis Presented to the Faculty of Graduate and Postdoctoral Studies in partial fulfillment of the requirements for the degree Doctor of Philosophy (Computer Science1) Ottawa-Carleton Institute for Computer Science School of Information Technology and Engineering University of Ottawa Ottawa, Ontario, K1N 6N5 Canada © Andrew Forward, 2010 1 The Ph.D. program in Computer Science is a joint program with Carleton University, administered by the Ottawa Carleton Institute for Computer Science Acknowledgements A very special, and well-deserved, thank you to the following: a) Dr. Timothy C. Lethbridge. Tim has been a mentor of mine for several years, first as one of my undergraduate professors, later as my Master’s supervisor. Tim has again helped to shape my approach to software engineering, research and academics during my journey as a PhD candidate. b) The Complexity Reduction in Software Engineering (CRUISE) group and in particular Omar Badreddin and Julie Filion. Our weekly meetings, work with IBM, and the collaboration with the development of Umple were of great help. c) My family and friends. Thank you and much love Ayana; your support during this endeavor was much appreciated despite the occasional teasing about me still being in school. To my mom (and editor) Jayne, my dad Bill, my sister Allison and her husband Dennis. And, to my friends Neil, Roy, Van, Rob, Pat, and Ernesto – your help will be forever recorded in my work. Finally a special note to Ryan Lowe, a fellow Software Engineer that helped to keep my work grounded during our lengthy discussion about software development – I will miss you greatly.
    [Show full text]
  • An Open Source Software Selection Process and a Case Study
    AN OPEN SOURCE SOFTWARE SELECTION PROCESS AND A CASE STUDY A Record of Study by GUOBIN HE Submitted to the Office of Graduate Studies of Texas A&M University in partial fulfillment of the requirements for the degree of DOCTOR OF ENGINEERING August 2007 Major Subject: Engineering College of Engineering AN OPEN SOURCE SOFTWARE SELECTION PROCESS AND A CASE STUDY A Record of Study by GUOBIN HE Submitted to the Office of Graduate Studies of Texas A&M University in partial fulfillment of the requirements for the degree of DOCTOR OF ENGINEERING Approved by: Chair of Committee, Dick B. Simmons Committee Members, William M. Lively Jianer Chen Sheng-Jen Hsieh John Fierstien Head of Doctor of Engineering Programs, N.K. Anand August 2007 Major Subject: Engineering College of Engineering iii ABSTRACT An Open Source Software Selection Process and a Case Study. (August 2007) Guobin He, B.S., National University of Defense Technology; M.S., Beijing University of Aeronautics and Astronautics Chair of Advisory Committee: Dr. Dick B. Simmons In this study, I design an empirical open source software selection process, which reuses some ideas from Commercial Off-the-Shelf selection methods and addresses the characteristics of the open source software. Basically, it consists of three basic steps: identification, screening and evaluation. The identification step is to find all possible alternatives to open source software that can meet the high level requirements. The next step is screening, in which the refined requirements are applied to filter the alternatives. The evaluation step is based on the Analytic Hierarchy Process, in which the alternatives are inspected from functional suitability, source code, support strength and popularity.
    [Show full text]
  • Enhancing Legacy Software System Analysis by Combining Behavioural and Semantic Information Sources
    Enhancing Legacy Software System Analysis by Combining Behavioural and Semantic Information Sources David Cutting School of Computing Sciences University of East Anglia A thesis submitted for the degree of Doctor of Philosophy November 2016 c This copy of the thesis has been supplied on condition that anyone who consults it is understood to recognise that its copyright rests with the author and that use of any information derived there from must be in accordance with current UK Copyright Law. In addition, any quotation or extract must include full attribution. To my parents, Peter and Valerie, who brought me into this world, and have tirelessly supported me. Maybe this makes up for it all? At least in some small part? Even a teeny bit? Probably not. Thanks for the inspiration Acknowledgements First I must acknowledge and deeply thank my supervisor, Dr. Joost Noppen, for not only giving me a chance at this project but tolerat- ing with good cheer my countless mistakes, poor drafts, and general laziness. Also my great gratitude goes to my second supervisor, Dr. Anthony Bagnall, for putting up with me. Any errors contained within are entirely mine. For their “support” (usually in the form of abuse) in no particular order I heap praise upon: 1) The fellow dishonourable members of the illustrious bigtime super funclub of the UEA: Dani and Sam. 2) My fellow 2.02 lab members: Alex, Andrei, Awat, Bogdan, Claudia, James, Matt, and Sarah. 3) Those funny funny people who have also survived the Nam (you weren’t there man) and continue to speak to me: Celia, Erwin, Joanna, Marika (squeak with joy!), Marjolijn, Matt, and Siew Wee.
    [Show full text]
  • Volume 8 Issue 3
    INFOLINE EDITORIAL BOARD EXECUTIVE COMMITTEE Chief Patron : Thiru A.K.Ilango Correspondent Patron : Dr. N.Raman, M.Com., M.B.A., M.Phil., Ph.D., Principal Editor in Chief : Mr. S.Muruganantham, M.Sc., M.Phil., Head of the Department STAFF ADVISOR Ms. P.Kalarani M.Sc., M.C.A., M.Phil., Assistant Professor, Department of Computer Technology and Information Technology STAFF EDITOR Ms. C.Indrani M.C.A., M.Phil., Assistant Professor, Department of Computer Technology and Information Technology STUDENT EDITORS B.Mano Pretha III B.Sc. (Computer Technology) K.Nishanthan III B.Sc. (Computer Technology) P.Deepika Rani III B.Sc. (Information Technology) R.Pradeep Rajan III B.Sc. (Information Technology) D.Harini II B.Sc. (Computer Technology) V.A.Jayendiran II B.Sc. (Computer Technology) S.Karunya II B.Sc. (Information Technology) E.Mohanraj II B.Sc. (Information Technology) S.Aiswarya I B.Sc. (Computer Technology) A.Tamilhariharan I B.Sc. (Computer Technology) P.Vijaya shree I B.Sc. (Information Technology) S.Prakash I B.Sc. (Information Technology) CONTENTS Nano Air Vehicle 1 Reinforcement Learning 2 Graphics Processing Unit (GPU) 4 The History of C Programming 5 Fog Computing 7 Big Data Analytics 9 Common Network Problems 14 Bridging the Human-Computer Interaction 15 Adaptive Security Architecture 16 Digital Platform ` 16 Mesh App and Service Architecture 17 Blockchain Technology 18 Digital Twin 20 Puzzles 21 Riddles 22 right, forward and backward, rotate clockwise NANO AIR VEHICLE (NAV) and counter-clockwise; and hover in mid-air. The artificial hummingbird using its flapping The AeroVironment Nano wings for propulsion and attitude control.
    [Show full text]
  • Fundamental Data Structures Contents
    Fundamental Data Structures Contents 1 Introduction 1 1.1 Abstract data type ........................................... 1 1.1.1 Examples ........................................... 1 1.1.2 Introduction .......................................... 2 1.1.3 Defining an abstract data type ................................. 2 1.1.4 Advantages of abstract data typing .............................. 4 1.1.5 Typical operations ...................................... 4 1.1.6 Examples ........................................... 5 1.1.7 Implementation ........................................ 5 1.1.8 See also ............................................ 6 1.1.9 Notes ............................................. 6 1.1.10 References .......................................... 6 1.1.11 Further ............................................ 7 1.1.12 External links ......................................... 7 1.2 Data structure ............................................. 7 1.2.1 Overview ........................................... 7 1.2.2 Examples ........................................... 7 1.2.3 Language support ....................................... 8 1.2.4 See also ............................................ 8 1.2.5 References .......................................... 8 1.2.6 Further reading ........................................ 8 1.2.7 External links ......................................... 9 1.3 Analysis of algorithms ......................................... 9 1.3.1 Cost models ......................................... 9 1.3.2 Run-time analysis
    [Show full text]
  • UML Modelleme Araçlarının Pratik Kullanım Için Analizi
    UML Modelleme Araçlarının Pratik Kullanım için Analizi Mert Ozkaya1 and Ferhat Erata2 1 Yeditepe Üniversitesi , Ataşehir, İstanbul [email protected] 2 UNIT Bilgi Teknolojileri R&D Ltd., Bornova, Izmir [email protected] Özet. Günümüzde, Unified Modeling Language(UML) pratisyenler tarafından en sık tercih edilen yazılım sistemi modelleme ve tasarlama notasyonu olarak kabul edilmektedir. UML, aynı zamanda, birçok yazılım modelleme aracı tarafın- dan desteklenmektedir, ve bu araçlar sayesinde, pratisyenler yazılım sistem- lerini kolayca UML notasyonunu kullanarak modelleyebilir ve analiz, yazılım kodu üretme, ve işbirliği gibi birçok faydalı değişik işlemler gerçekleştirebilirler. Bu çalışmada, tanınan 11 farklı UML modelleme aracını pratisyenlerin UML’i benimsemeleri açısından önemli olduğunu düşündüğümüz bir grup gereksinim bakımından analiz ettik. Bu gereksinimler başlıca, modellerin tasarımı, model analizi, modelden kod üretme, iş-birliği halinde modelleme, ve genişletilebilir- lik olmaktadır. Model tasarımı gereksinimi, modelleme araçlarının UML diya- gramlarına olan destekleri, yazılım modelleme bakış-açılarına olan destekleri, ve büyük ve karmaşık yazılım modellerinin tasarımına olan destekleri açıların- dan ele alınmaktadır. Model analizi gereksinimi, simülasyon ve doğrulama (hem önceden tanımlanmış doğrulama hem de kullanıcı tanımlı doğrulama) gereksin- imlerine olan destek bakımından incelenmektedir. İş-birliği halinde modelleme gereksinimi ise, senkron ve asenkron olarak çoklu kullanıcı desteği, görev yöne-
    [Show full text]
  • Comparative Studies of Six Programming Languages
    Comparative Studies of Six Programming Languages Zakaria Alomari Oualid El Halimi Kaushik Sivaprasad Chitrang Pandit Concordia University Concordia University Concordia University Concordia University Montreal, Canada Montreal, Canada Montreal, Canada Montreal, Canada [email protected] [email protected] [email protected] [email protected] Abstract Comparison of programming languages is a common topic of discussion among software engineers. Multiple programming languages are designed, specified, and implemented every year in order to keep up with the changing programming paradigms, hardware evolution, etc. In this paper we present a comparative study between six programming languages: C++, PHP, C#, Java, Python, VB ; These languages are compared under the characteristics of reusability, reliability, portability, availability of compilers and tools, readability, efficiency, familiarity and expressiveness. 1. Introduction: Programming languages are fascinating and interesting field of study. Computer scientists tend to create new programming language. Thousand different languages have been created in the last few years. Some languages enjoy wide popularity and others introduce new features. Each language has its advantages and drawbacks. The present work provides a comparison of various properties, paradigms, and features used by a couple of popular programming languages: C++, PHP, C#, Java, Python, VB. With these variety of languages and their widespread use, software designer and programmers should to be aware
    [Show full text]
  • Comparative Programming Languages CM20253
    We have briefly covered many aspects of language design And there are many more factors we could talk about in making choices of language The End There are many languages out there, both general purpose and specialist And there are many more factors we could talk about in making choices of language The End There are many languages out there, both general purpose and specialist We have briefly covered many aspects of language design The End There are many languages out there, both general purpose and specialist We have briefly covered many aspects of language design And there are many more factors we could talk about in making choices of language Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important For example, can you easily join together code written in Java and C? The End Or languages And then the interopability of languages becomes important For example, can you easily join together code written in Java and C? The End Or languages Often a single project can use several languages, each suited to its part of the project For example, can you easily join together code written in Java and C? The End Or languages Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important The End Or languages Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important For example, can you easily
    [Show full text]
  • Seminario De Herramientas
    Seminario de Herramientas Instalación y uso básico de una herramienta UML: BOUML Otras herramientas del laboratorio Laura Barros Computadores y Tiempo Real ProConDis 2009 1 1 Características Herramienta UML 2.0 Software libre. Puede ser redistribuida y/o modificada bajo los términos de la Licencia Pública General (General Public License, GNU). Permite especificar y generar código C++, Java, IDL, PHP y Python. Multiplataforma: Linux, Windows, MacOS Es rápida y no consume mucha memoria Instalación : Descargar el programa: http://bouml.free.fr/download.html Windows: Bouml_4.15_setup.exe z Ejecutar el Setup y seguir las instrucciones. Linux: existen paquetes para las distribuciones principales. Manual de usuario: http://bouml.free.fr/doc/index.html Santander, 2009 BOUML L.Barros 2 2 Crear un proyecto nuevo Al iniciar BOUML nos pide un identificador del desarrollador (BOUML_ID): si varios desarrolladores van a trabajar con el mismo modelo, se debe especificar esta variable de entorno Windows: start > settings > control panel > system > advanced > environmentvariables. Crear el proyecto: Project => New Guardar el proyecto: se indica el directorio donde se guardará el proyecto. Nota: la carpeta debe llamarse como el fichero .prj Indicar lenguaje de desarrollo: Pestaña Languages=> Java default definition Santander, 2009 BOUML L.Barros 3 3 Pantalla principal Elementos estructurales Diagramas Documentación Santander, 2009 BOUML L.Barros 4 4 Ejemplo de uso: Creación de un diagrama de clases Generar una vista de clases: Botón derecho en el
    [Show full text]