Premium Essay

Software Reusability

In:

Submitted By prasadasarp
Words 3225
Pages 13
Software reusability

TERM PAPER

Software reusability is generally considered a way to solve the software development crisis. When we solve a problem we try to apply the solution to similar problems because that makes our work easy and simple. Now in this paper I would like to cover important aspects of software reusability. But one thing is for sure software reusability can improve software productivity. Software reuse has become a topic of much interest in the software community due to its potential benefits, which include increased product quality and decreased product cost and schedule. The most substantial benefits derive from a product line approach, where a common set of reusable software assets act as a base for subsequent similar products in a given functional domain. The upfront investments required for software reuse are considerable, and need to be duly considered prior to attempting a software reuse initiative.
1. Introduction

Software reuse is the process of implementing or updating software systems using existing software components. A good software reuse process facilitates the increase of productivity, quality, and reliability, and the decrease of costs and implementation time. An initial investment is required to start a software reuse process, but that investment pays for itself in a few reuses. In short, the development of a reuse process and repository produces a base of knowledge that improves in quality after every reuse, minimizing the amount of development work required for future projects, and ultimately reducing the risk of new projects that are based on repository knowledge..
Types of Reuse
Horizontal reuse

Horizontal reuse refers to software components used across a wide variety of applications. In terms of code assets, this includes the typically envisioned library of components, such as a linked list class, string

Similar Documents

Premium Essay

Analysis of Software Quality Models for Organizations

...Computing (E-ISSN: 2045-5364) Volume 1, Issue 2, December 2010 19 Analysis of Software Quality Models for Organizations Dr. Deepshikha Jamwal University of Jammu Department Of Computer Science & IT jamwal.shivani@gmail.com Abstract Software Quality model is a vital to obtained data so that actions can be taken to improve the performance. Such improvement can be measured quality, increased customer satisfaction and decreased cost of quality. Software metrics and quality models play a pivotal role in measurement of software quality. A number of well known qualities models are used to build quality software. Different researchers have proposed different software quality models to help measure the quality of software products. In our research, we are discussing the different software quality models and compare the software quality models with each other. Also a framework containing steps is proposed by authors. Some recommendations are also framed hereby in the following research paper. Keywords Software Quality Models, McCall model, Dromey‟s model, FURPS model, ISO 9126 model. Objectives To begin with there are some common objectives: To analysis various software quality models w.r.t various attributes.  The presence, or absence, of these attributes can be measured objectively.  The degree to which each of these attributes is present reflects the overall quality of the software product.  These attributes facilitate continuous improvement, allowing cause and...

Words: 3104 - Pages: 13

Premium Essay

Software Quality Factors

...to Validate the software requirements. Product transition •Portability, the ability to transfer the software from one environment to another. •Reusability, the ease of using existing software components in a different context. •Interoperability, the extent, or ease, to which software components work together. Product operations •Correctness, the functionality matches the specification. •Reliability, the extent to which the system fails. •Efficiency, system resource (including cpu, disk, memory, network) usage. •Integrity, protection from unauthorized access. •Usability, ease of use. PREDICTION OF RATE OF IMPROVEMENT OF SOFTWARE QUALITY AND DEVELOPMENT EFFORT ON THE BASIS OF DEGREE OF EXCELLENCE WITH RESPECT TO NUMBER OF LINES OF CODE http://arxiv.org/ftp/arxiv/papers/1404/1404.4970.pdf Problems in Systematic Application of Software Metrics and Possible Solution http://arxiv.org/ftp/arxiv/papers/1311/1311.3852.pdf SQA comparison : QUALITY MODEL BASED ON Commercial Of the shelf QUALITY ATTRIBUTES http://airccse.org/journal/ijsea/papers/4113ijsea01.pdf Quality Models in Software Engineering Literature: An Analytical and Comparative http://www.jofamericanscience.org/journals/am-sci/am0603/22_2208_Qutaish_am0603_166_175.pdf A SYSTEMATIC STUDY OF SOFTWARE QUALITY MODELS http://www.airccse.org/journal/ijsea/papers/1011ijsea06.pdf Testability Phogat, M., Kumar, D., & Murthal, D. C. R. U. S. T. (2011). Testability of Software System. IJCEM...

Words: 401 - Pages: 2

Free Essay

Software

...Robert P. Ward Software Engineering in the Small Smaller-sized software companies are developing significant products that need effective, tailored software engineering practices. n 1968, the NATO Software Engineering Conference in Garmisch, Germany [6] initiated the concept of software engineering, identifying the problems with producing large, high-quality software applications. In 1975, De Remer [2] introduced the terms, “programming in the small” and “programming in the large” to differentiate the development characteristics of large-scale software development from detailed programming (for example, data structures and algorithms). The principal source of large-scale software at the time was development contracts issued by the U.S. Department of Defense. Since then, virtually all software engineering literature has concentrated explicitly and implicitly on the model of DoD contract software development. Since the late 1970s, the microcomputer revolution has dramatically increased the quantity of software produced, the average I size of programs, and the number of companies involved in software development. Much more software is produced for internal use, commercial applications, and the mass-market than for deep-pocketed government and large industry. Using the number of units sold, mass-market software dwarfs the other forms of software sales. The growth of the software industry has produced many small companies that do not do contract software, but rather compete...

Words: 2136 - Pages: 9

Premium Essay

Software Engineering

...Software Engineering 1.) What does the term requirement mean? Explain the process of determining the requirement for a software system.  ‘Requirements’ suggests that there is someone out there doing the ‘requiring’ – a specific customer who knows what she wants. In some projects, requirements are understood to be the list of features (or functions, properties, constraints, etc.) Demanded by the customer. In practice, there is rarely a single customer, but rather a diverse set of people who will be affected in one way or another by the system. These people may have varied and conflicting goals. Their goals may not be explicit, or may be hard to articulate. They may not know what they want or what is possible. Under these circumstances, asking them what they ‘require’ is not likely to be fruitful. 2.) Describe the various steps of requirement engineering? Is it essential to follow these steps?  Requirements engineering is an important aspect of any software project, and is a general term used to encompass all the activities related to requirements. The four specific steps in software requirements engineering are: • Requirements elicitation is the practice of obtaining the requirements of a system from users, customers and other stakeholders. • Requirements analysis encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various...

Words: 1772 - Pages: 8

Premium Essay

Software Engineering (Chapter 1 Summ.)

...Inadequate software engineering has led to failure of modern softwares. Causes of software failures ---------- 1. increasing demand: software developers are tasked to develop softwares that solve more complex solutions and are often given short time. the existing software engineering techniques are therefore not able to cater for this complexity. 2. low expectation: most software developers develop softwares without using software engineering techniques which often cause software failures and unreliable softwares Attributes of a good software:(M.A.D.E) Maintainability: it should be able to evolve in order to fit new needs or suit new customers Acceptability: it must meet the need for which it was developed for and must be usable for its users Dependability and Security: it must not cause physical damage or be open to malicious attackers for exploits Efficiency: it must not waste system resources like memory, disk space, e.t.c Others are D.R.I.P Distributability,Reusability,Interoperatability,Portability software engineering is an aspect of engineering discipline that focuses on all the aspect of software development production Fundamental software engineering activities DEVS: software development, software evolution, software validation, software specification Difference between software engineering and computer science: computer science focuses on the theories and fundamentals of software development...

Words: 334 - Pages: 2

Premium Essay

Refactoring

...A. /m'cCall, Gene F./Waiters Software Quality for an Vk~~ '4 Paul K./RichA'rds -General Electric Company .,..... . 4- Approved for public release; distribution unlimited. ROME AIR DEVELOPMENT CENTER Air Force Systems Command Griffiss Air Force Base, New York 13441 This report has been reviewed by the PADC Information Office (01) and is releasable to the National Technical Information Service (NTIS). At NTIS it will be releasable to the general public, including foreign nations. RADC-TR-77-369, Vo] III (of three) has been reviewed and approved for publication. APPROVED: JOSEPH P. CAVANO Project Engineer APPROVED: (2 &4~L ( ALAN R. BARNUM, Assistant Chief information Sciences Division FOR THE COMMANDER: JOH" F . HUSS Acting Clief, Plans Office If your address has changed or if you wish to be removed from the RADC mailing list, or if the addressee is no longer employed by your organization, please notify RADC (ISIS) Griffiss AFB NY 13441. This will assist us in maintaining a current mailing list. Do not return this copy. Retain or destroy. SECURITY CLASSIFICATION OF THIS PAGE (IW.i, Vt e En eed)RE REPORT DOCUMENJATIO4 PAGE I. REPORT NU bER . D I S UC ON BFRE COMPTING ORM ... ' j2. GOVT ACCESSION NO. 3. ft9CIPIkNTIS CATALOG NUMBER RADC-TR-77-369, 4. TITLE (and Subtlfe) Vol III (of three) COVERED S. TYPE OF REPORT A P91111O0 Final Technical Report FACTORS IN SOFTWARE QUALITY Aug 76 - Jul 77 ...

Words: 6344 - Pages: 26

Premium Essay

Software Requirements

...September 16, 2014 INSS 615- Mini Paper Chpt. 1 – Understanding Software Requirements Software requirements first start off deciding what to build and then how to document the process for designing the specified system needed or acquired. We will discuss what are software requirement, methodologies, requirements and architecture, and emerging trends. A software requirement is typically classified in two distinct functions. A stated by Thayer and Dorfman (2013) functional typically refers to requirements defining the acceptable mappings between system input values and corresponding output values. Non-functional refers to all constraints including, but not limited to, performance, dependability, maintainability, reusability, and safety. These two functions work intangible with common attributes and similar qualities that behavioral requirements deal with output values and deadlines, and developing quality attributes deals with deadlines and maintaining the goals achieved. One major issue inherent with requirements is discovering significant errors later during maintenance can be very costly. It is recommended to detect errors during the design and development so as is less expensive. The goal of requirements phase is to establish and specify precisely what the software must do without describing how to do it (Thayer and Dorfman, 2013). The ultimate outcome is to specify the problem to be solved and not its solutions. The average person doesn’t understand very technical...

Words: 571 - Pages: 3

Free Essay

Introducion Al Eviews

...Análisis y predicción de costos. Análisis Financiero. Predicción macroeconómica. Simulación. Análisis científico de los datos y evaluación. E-views es una nueva versión del conjunto de herramientas para manipular series de tiempo originalmente desarrolladas en el software Time Series Processor para grandes computadoras. El predecesor inmediato de E-views fue el MicroTSP, lanzado por primera vez en 1981. Aunque Eviews fue desarrollado por economistas y la mayoría de sus usos están en la economía, no hay nada que haga limitar su utilidad a las series de tiempo económicas. Inclusive considerables proyectos de corte transversal pueden llevarse a cabo en E-views. El objeto básico dentro de E-views es la serie de tiempo. Cada serie posee un nombre, y usted puede realizar cualquier tipo de operación sobre todas las observaciones simplemente mencionando el nombre de la serie. E-views provee convenientes formas de visualización para ingresar las series desde el teclado o desde un archivo, para crear una serie a partir de otra ya existente, para mostrar o imprimir la serie, y para llevar a cabo análisis estadísticos sobre las relaciones entre las series. E-views utiliza la forma de visualización moderna del software Windows. Usted puede usar su mouse para guiar las operaciones a través de...

Words: 8183 - Pages: 33

Free Essay

Vlsm

...Portafolio de Servicios FORMACIÓN FORMACIÓN TITULADA: TECNOLOGÍAS * ADMINISTRACIÓN BANCARIA Y DE INSTITUCIONES FINANCIERAS   * ADMINISTRACIÓN DE REDES DE COMPUTADORES       * ADMINISTRACIÓN DEL ENSAMBLE Y MANTENIMIENTO DE COMPUTADORES Y REDES   * ADMINISTRACIÓN EMPRESARIAL   * ADMINISTRACIÓN HOTELERA           * ANÁLISIS Y DESARROLLO DE SISTEMAS DE INFORMACIÓN   * ANIMACIÓN 3D   * ANIMACIÓN DIGITAL   * CÁMARA Y FOTOGRAFÍA PARA CINE   * COCINA       * COORDINACIÓN DEL PROCESO PARA DISEÑO DE MEDIOS IMPRESOS   * DESARROLLO DE VIDEOJUEGOS   * DISEÑO PARA LA COMUNICACIÓN GRÁFICA   * ESCRITURA PARA PRODUCTOS AUDIOVISUALES   * FORMULACIÓN DE PROYECTOS   * GASTRONOMÍA       * GESTIÓN ADMINISTRATIVA   * GESTIÓN BANCARIA Y DE ENTIDADES FINANCIERAS * SONIDO DIRECTO PARA PRODUCCIÓN DE MEDIOS AUDIOVISUALES * GESTIÓN DE SERVICIOS RECREATIVOS * GESTIÓN DEL TALENTO HUMANO * GESTIÓN EMPRESARIAL * GESTIÓN HOTELERA * GESTIÓN INTEGRAL DEL  RIESGO EN SEGUROS * GESTIÓN INTEGRAL EN FONDOS DE PENSIONES  Y CESANTIAS * GESTIÓN LOGÍSTICA * GRABACIÓN, EDICIÓN Y MEZCLA DE VOCES Y DOBLAJES PARA MEDIOS AUDIOVISUALES * GUIANZA TURÍSTICA * ILUMINACIÓN Y RENDER PARA ARTE 3D * ILUSTRACIÓN PARA PRODUCCIONES AUDIOVISUALES * LOGÍSTICA DEL  TRANSPORTE * MODELADO Y TEXTURIZADO PARA ARTE 3D * ORGANIZACIÓN DE EVENTOS * PROCESOS RECREATIVOS Y TURÍSTICOS * PRODUCCIÓN DE CAMPO...

Words: 366 - Pages: 2

Free Essay

Chorus

...UNIVERSIDAD DE GUADALAJA CENTRO UNIVERSITARIO DE CIENCIAS EXACTAS E INGENIERÍAS DIVISIÓN DE ELECTRONICA Y COMPUTACIÓN SISTEMAS OPERATIVOS AVANZADOS PROYECTO FINAL 2012-A JIMÉNEZ BENÍTEZ OMAR ALEJANDRO CÓDIGO.- 208435758 ING. LUIS HEBERTO GUTIÉRREZ AVILÉS Introducción Chorus es un sistema operativo para aplicaciones embebidas o de tiempo real. Sun MicroSystems adquirió Chorus Systèmes, la compañía que había creado Chorus OS, en 1997. Sun (ahora Oracle) ya proporciona soporte a Chorus. Desde el 2002 los creadores de Chorus se unieron formando una nueva compañía llamada Juluana que posteriormente se hizo llamar VirtualLogix, misma que aun da mantenimiento constante a Chorus. Actualmente liberado bajo código abierto, sistema operativo altamente escalable y estable, sirve para sistemas distribuidos, en red, embebidos, o en tiempo real y se ha establecido como un sistema operativo muy utilizado en hardware para comunicaciones, como celulares, cajeros bancarios, switches, impresoras, autómatas, etc. Su arquitectura se basa en módulos, característica que lo dota de alta configurabilidad y escalabilidad. Historia Chorus surgió del Instituto Francés de investigación INRIA en 1980, como proyecto de investigación en sistemas distribuidos, desde entonces han aparecido 5 versiones, enumeradas del 0 al 4. La idea de la versión 0, era modelar aplicaciones distribuidas como colecciones de actores, en esencia procesos estructurados, cada uno de los cuales alternaban entre...

Words: 7191 - Pages: 29

Free Essay

Law 571

...Reconociendo contrato riesgosos y oportunidades Amaryllis Ayala Hernáiz, Natalie Rivera Víctor Rivera y Santos Rodríguez University of Phoenix Leyes Laborales / Law 531 18 de julio de 2012 Prof. Nelson Cardona Muñiz Reconociendo contrato de riesgo y oportunidades Entre corporaciones hay cientos de ofertas hechas todos los días. En este informe se explicarán los riesgos legales, oportunidades que se presentan y las alternativas para la solución de los conflictos. Cada vez más los hombres de negocios exitosos y mujeres de la sociedad actual están conscientes de los peligros que se encuentran en los contratos ya sean verbales o escritos. Si el contrato está lleno de ambigüedad y de vagas declaraciones esto puede ser costoso para ambas partes involucradas. Los tribunales, cuando se encuentran con un contrato con tal ambigüedad, no tiene más remedio que confiar en lo que la gente común habría asumido es cierto por el propósito de las partes; y se deja sin efecto aquellas partes del contrato donde el lenguaje carece de información exacta. Esta simulación demuestra los errores y equivocaciones que se pueden realizar y las medidas adoptadas para hacer cumplir un contrato. Citizen-Schwarz AG Bank acusa a Span System de incumplimiento de contrato en el rendimiento de los sistemas que Span System entrega. Citizen-Schwarz AG Bank también afirma que los sistemas de entregas de Span System están en retraso y que la calidad de estos es inaceptable. Citizen-Schwarz AG Bank...

Words: 1323 - Pages: 6

Free Essay

Documento Visión Sistema de Almacén

...Sistema de almacén SISTAL Visión Versión 1.0 Historial de revisiones Fecha | Versión | Descripción | Autor | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tabla de Contenidos 1. Introducción 4 1.1 Propósito 4 1.2 Alcance 4 1.3 Definiciones, Acrónimos, y Abreviaciones 4 1.4 Referencias 4 2. Posicionamiento 5 2.1 Oportunidad de Negocio 5 2.2 Sentencia que define el problema 5 2.3 Sentencia que define la posición del Producto 6 3. Descripción de Stakeholders (Participantes en el Proyecto) y Usuarios 7 3.1 Resumen de Stakeholders 7 3.2 Resumen de Usuarios 7 3.3 Entorno de usuario 8 3.4 Perfil de los Stakeholders 8 3.4.1 Representante del área técnica y sistemas de información 8 3.5 Perfiles de Usuario 9 3.5.1 Jefe de Almacén 9 3.5.2 Almacenista 9 4. Descripción Global del Producto 10 4.1 Perspectiva del producto 10 4.2 Resumen de características 10 4.3 Suposiciones y dependencias 10 4.4 Costo y precio 10 5. Descripción Global del Producto 10 5.1 Control de almacen 10 5.1.1 Control de movimientos de productos 10 5.1.2 Consulta de productos terminados 11 5.1.3 Consulta de documentos 11 5.1.4 Consulta de orden de pedido 11 5.1.5 Mantenimiento de productos 11 5.1.6 Reportes 11 [ Visión ] Introducción Propósito El objetivo de declarar esta visión es describir la idea inicial del...

Words: 1572 - Pages: 7

Free Essay

Analisis Y Diseno de Sistemas

...Análisis y Diseño de Sistemas Diseño de Sistemas de Informacion Análisis y Diseño de Sistemas SISTEMA DE INFORMACION Conjunto u ordenación de elementos organizados para llevar a cabo algún métodos, procedimiento o control mediante el proceso de información. ANALISIS Y SISTEMAS El análisis y diseño de sistemas se refiere al proceso de examinar la situación de una empresa con el propósito de mejorar con métodos y procedimientos más adecuados. El desarrollo de sistemas tiene dos componentes. Análisis Es el proceso de clasificación e interpretación de hechos, diagnostico de problemas y empleo de la información para recomendar mejoras al sistemas. Diseño: Especifica las características del producto terminado. Análisis: Especifica que es lo que el sistema debe hacer. Diseño: Establece como alcanzar el objetivo. LO QUE NO ES EL ANÁLISIS DE SISTEMAS NO es: El estudio de una empresa para buscar procesos ya existentes con el propósito de determinar cuáles deberían, ser llevados a cabo por una computadora y cuáles por métodos manuales. La finalidad del análisis está en comprender los detalles de una situación y decir si es deseable o factible una mejora. La selección del método, ya sea utilizando o no una computadora, es un aspecto secundario. No es: Determinar los cambios que deberían efectuarse. No es: Determinar la mejor forma de resolver un `problema de sistemas de información. Sin importar cuál sea la organización, el analista trabaja en los problemas de ésta. Es...

Words: 1340 - Pages: 6

Free Essay

Codigo Abierto

...¿ES EL MOMENTO PARA EL CÓDIGO ABIERTO? A fines de la década de 1990, cuando el volumen de transacciones de E*Trade Financial se multiplicó, la empresa de servicios financieros en línea manejó este crecimiento al incrementar su capacidad en forma de servidores grandes de Sun Microsystems que ejecutaban Sun Solaris, la versión de Unix patentada por Sun. Para el otoño de 2001 el mercado accionarios tenía poca actividad, y los volúmenes de transacciones – lo mismo que el flujo efectivo de E*Trade – se derrumbaron estrepitosamente. La empresa decidió cambiar Linux ejecutándose en servidores IBM x355 basados en procesadores Intel de bajo costo para controlar los costos. Las pruebas preliminares que ejecutaron en Linux aplicaciones de autenticación, servicios de cotización, servicios de productos financieros y servicios de transacciones financieras de E*Trade mostraron que cada servidor con sistema operativo Linux podía manejar alrededor de 180 usuarios al mismo tiempo, en comparación con los 300 a 400 usuarios simultáneos en uno de los servidores de Sun 4500 de E*Trade. Con más de 180 usuarios se degradaba el rendimiento, pero con 180 más rápido que el servidor de Sun. El costo de un servidor Sun 4500 era de aproximadamente 250,000 dólares. Aun cuando cada computadora con Linux podía manejar sólo 180 usuarios a la vez, únicamente costaba 4,000 dólares. E*Trade tan sólo necesitaba comprar dos computadoras con Linux por un costo total de 8,000 dólares para suministrar las...

Words: 1058 - Pages: 5

Premium Essay

Theng

...Software is designed and built by software engineers. Software is used by virtually everyone in society. Software is pervasive in commerce, our culture, and our everyday lives. Software engineers have a moral obligation to build reliable software that does not harm other people. Software engineers view computer software, as being made up of the programs, documents, and data required to design and build the system. Software users are only concerned with whether or not software products meet their expectations and make their tasks easier to complete. Important questions for Software Engineers. Why does it take so long to get software finished? Why are development costs so high? Why can’t we find all errors before we give the software to our costumers? Why do we spend so much time and effort maintaining existing programs? Why do we continue to have difficulty in measuring progress as software is being developed? Software Software s both a product and a vehicle for delivering a product(information). Software is engineered not manufactured. Software does not wear out, but it does deteriorate. Industry is moving toward component-based software construction, but most software is still custom built. Software Application Domains System Application Domains Application Software Engineering or Scientific Software Embedded software Product-line software Web Applications Artificial Intelligence software New Software Challenges Open world Computing Creating...

Words: 469 - Pages: 2