Scalability in Manufacturing Systems Design and Operation: State-Of-The-Art and Future Developments Roadmap

Total Page:16

File Type:pdf, Size:1020Kb

Scalability in Manufacturing Systems Design and Operation: State-Of-The-Art and Future Developments Roadmap CIRP Annals - Manufacturing Technology 62 (2013) 751–774 Contents lists available at SciVerse ScienceDirect CIRP Annals - Manufacturing Technology journal homepage: http://ees.elsevier.com/cirp/default.asp Scalability in manufacturing systems design and operation: State-of-the-art and future developments roadmap G. Putnik (2)a, A. Sluga (2)b, H. ElMaraghy (1)c, R. Teti (1)d, Y. Koren (1)e, T. Tolio (1)f, B. Hon (1)g a Department of Production and Systems Engineering, School of Engineering, University of Minho, Portugal b Department of Control and Manufacturing Systems, University of Ljubljana, Ljubljana, Slovenia c Intelligent Manufacturing Systems Center, Industrial and Manufacturing Systems Engineering, University of Windsor, Ontario, Canada d Fraunhofer J_LEAPT, Department of Chemical, Materials and Production Engineering, University of Naples Federico II, Italy e Department of Mechanical Engineering, University of Michigan, Ann Arbor, MI, USA f Department of Mechanical Engineering, Politecnico di Milano, Milano, Italy g School of Engineering, University of Liverpool, Liverpool, UK ARTICLE INFO ABSTRACT Keywords: The paper covers the main design, management and operational aspects of scalability in manufacturing Manufacturing system systems (MS). It promotes scalability as an area of research of MS theory and practice in order to enhance Flexibility techniques and methodologies in existing MS paradigms using advanced and emerging design and Scalability management approaches and ICT, and meet challenges of emerging MS paradigms and support their promotion and effective and efficient deployment in practice. The paper presents an introduction to scalability, state-of-the art in manufacturing and computer science, and related applications including manufacturing and education and a roadmap for future research and developments. ß 2013 CIRP. 1. Introduction 3. provide transfer of knowledge and ideas from other engineering and management areas, in which ‘‘scalability’’ is also explored, 1.1. Objectives to manufacturing, This is especially relevant for the area of Computer Science1 (or Computing Science, abbr. CS or CompSci). Scalability of systems, and in our particular case of manufactur- ing systems (MS), could be seen as a system’s feature that might 1.2. Relevance I provide a significant increase of potentials for resolving a number of problems in manufacturing systems design and operation and The relevance of scalability might initially be evaluated for enabling new visions, whether quantitatively or qualitatively. indirectly through the references to scalability by the R&D In other words, manufacturing systems scalability might provide community, under assumption that the R&D community reflects further optimization of the manufacturing systems design and well the societal (including industry) requirements. operation or to enable development of new manufacturing The analysis of the most important publication sources as well as systems paradigms, for the sustainability and wellbeing society. of the most significant international and national openly published Besides the functional aspects of scalability, which could be seen as R&D Programs and Roadmaps show that the issue of ‘‘scalability’’, by primarily technical issues, considering a wider social concerns the the criteria of number of the papers that cite the term ‘‘scalability’’, or scalability feature might also be seen as an instrument for number of occurrences of the term ‘‘scalability’’ and as the topic in increasing value (following requests for value creation and R&D Programs and Roadmaps, in the context of manufacturing, has sustainable society, see [190]). in the last years seen steady growth. Thus, the specific objectives of the paper could be defined along On the other hand, the same analysis shows that ‘‘scalability’’ the three main lines of scalability research, development and within the manufacturing community has started to gain major implementation. These are to: attention only since approximately the year 2000. This fact justifies that the relevance at this moment could be evaluated primarily 1. incentivize exploration of ‘‘scalability’’ seeing it as the new through the references by the R&D community rather than by potential, the new capacity, the new resource within ‘‘classical’’, industrial applications, considering the ‘‘incubation’’ period or ‘‘actual’’ MS paradigm; needed for transfer of knowledge and technology to industry. 2. incentivize exploration of ‘‘scalability’’ seeing it as the new potential, the new capacity, the new resource for, and in, 1 ‘‘emergent’’ MS paradigms; and ‘Computer Science’ denotation is adopted to refer to the entire area of computer based applications. Other terms are in use as synonyms, or may be used interchangeably, e.g. Informatics, Information and Communication Technologies (ICT). For the taxonomy of the Computer Science, see e.g. ACM Taxonomy at http:// www.computer.org/portal/web/publications/acmtaxonomy and at http://dl.acm. E-mail addresses: [email protected], [email protected]. org/ccs_flat.cfm. 0007-8506/$ – see front matter ß 2013 CIRP. http://dx.doi.org/10.1016/j.cirp.2013.05.002 752[(Fig._1)TD$IG] G. Putnik et al. / CIRP Annals - Manufacturing Technology 62 (2013) 751–774 the capability for effective and efficient development, implemen- tation and validation of scalability. In the literature, no explicit reference can be found to any meta-theoretical framework, or taxonomy of problematics that refer to the issue of scalability investigation. Therefore, the meta-theoretical framework ‘per se’ that could be identified in the literature are only implicit and on an ‘ad-hoc’ basis. Making this question explicit, as a first approach two criteria for structuring the scalability investigation meta-theoretical frame- work3 are analyzed: 1. scalability functional and application domains; 2. scalability abstractions hierarchy. 1.3.1. Scalability functional and application domains framework Fig. 1. Number of papers by the search terms ‘scalability AND manufacturing’in Manufacturing system (MS) scalability functional and appli- world leading publishers’ collections. cation domains could be identified through analysis of MS models. One of the models, at a very high level of abstraction, that may however represent a global reference model for Thus, the number of papers in collections of world leading scalability investigation, could be illustrated as in Fig. 3.Itis publishers (Elsevier, Springer, T&F, Wiley, Emerald, JSTOR, ACM, presented in IDEF0 graphical language depicting three main IEEE) per year, in which the term ‘‘scalability AND manufacturing’’ global processes of a manufacturing system and global ‘‘input’’, occur is given in Fig. 1. ‘‘output’’, ‘‘control’’ (i.e. control and/or management) and Concerning the CIRP community, the number of papers per year ‘‘mechanism’’ (i.e. instrument) entities. Each of these entities in CIRP Journals, i.e. ‘‘CIRP Annals: Manufacturing Technology’’ and represents a possible functional area for scalability application. ‘‘CIRP Journal of Manufacturing Science and Technology’’ where the These are: [(Fig._2)TD$IG]terms ‘‘scalability’’ or ‘‘scalable’’ occur, is given in Fig. 2. [(Fig._3)TD$IG] Fig. 2. Number of papers by the search term ‘scalability’ in CIRP’s journals. Fig. 3. Manufacturing System functional framework as a meta-theoretical In international and national Research & Development (R&D) framework for scalability investigation. Programs and Roadmaps, the occurrences of the topic and term ‘scalability’ could be assessed as regular, see e.g. [152,138,139, 63,64,151,65,66,67,68,107,57,69,106,71,72,73,74]. Processes 01 MS design 1.3. Meta-theoretical frameworks for the scalability issue 02 MS management/control presentation 03 MS operation Instruments 1. MS architecture models Scalability might be investigated following different meta- 2. MS hardware/equipment theoretical frameworks. Meta-theory is a ‘theory about theory’, the 3. MS management/planning/control models theory treated by the meta-theory being designated ‘object- 4. MS organizational models theory’. Following [134]: 5. MS ICT supporting technologies ‘‘A meta-theoretical perspective, ...is) a critical framework for 6. Product design models analysis, and create a structure that enables elements of different theories and concepts to be located relative to each ‘‘Transitive’’ and ‘‘reflexive’’ ways of scalability applications: The other.’’2 ‘MS design’ process could define that the ‘MS management/control’ Concerning the scalability, the purpose of a Meta-theoretical process will be executed and managed as scalable, but the same framework for scalability research and implementation is to ‘MS design’ process could also define that this very process will be provide a better understanding of scalability as well as to improve executed and managed as scalable. This is valid also for the ‘MS 2 Minor adaptations of the original text were made by the authors of this paper. 3 Other frameworks are possible too. G. Putnik et al. / CIRP Annals - Manufacturing Technology 62 (2013) 751–774 753 operation’ sub-processes. In other words, it is to say that for all ‘‘to climb’’ (see scan (v.)). Modern use of the terms ‘scalability’, ‘processes’ in the above process taxonomy, scalability could be ‘scalable’, ‘scale’ provided other meanings, through the language applied/implemented, in a transitive or reflexive way, i.e. change. referencing (to the object system), and/or self-referencing (to itself). For our purpose more relevant meanings
Recommended publications
  • ASSESSING the MAINTAINABILITY of C++ SOURCE CODE by MARIUS SUNDBAKKEN a Thesis Submitted in Partial Fulfillment of the Requireme
    ASSESSING THE MAINTAINABILITY OF C++ SOURCE CODE By MARIUS SUNDBAKKEN A thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in Computer Science WASHINGTON STATE UNIVERSITY School of Electrical Engineering and Computer Science DECEMBER 2001 To the Faculty of Washington State University: The members of the Committee appointed to examine the thesis of MARIUS SUNDBAKKEN find it satisfactory and recommend that it be accepted. Chair ii ASSESSING THE MAINTAINABILITY OF C++ SOURCE CODE Abstract by Marius Sundbakken, M.S. Washington State University December 2001 Chair: David Bakken Maintenance refers to the modifications made to software systems after their first release. It is not possible to develop a significant software system that does not need maintenance because change, and hence maintenance, is an inherent characteristic of software systems. It has been estimated that it costs 80% more to maintain software than to develop it. Clearly, maintenance is the major expense in the lifetime of a software product. Predicting the maintenance effort is therefore vital for cost-effective design and development. Automated techniques that can quantify the maintainability of object- oriented designs would be very useful. Models based on metrics for object-oriented source code are necessary to assess software quality and predict engineering effort. This thesis will look at C++, one of the most widely used object-oriented programming languages in academia and industry today. Metrics based models that assess the maintainability of the source code using object-oriented software metrics are developed. iii Table of Contents 1. Introduction .................................................................................................................1 1.1. Maintenance and Maintainability.......................................................................
    [Show full text]
  • Distributed Algorithms with Theoretic Scalability Analysis of Radial and Looped Load flows for Power Distribution Systems
    Electric Power Systems Research 65 (2003) 169Á/177 www.elsevier.com/locate/epsr Distributed algorithms with theoretic scalability analysis of radial and looped load flows for power distribution systems Fangxing Li *, Robert P. Broadwater ECE Department Virginia Tech, Blacksburg, VA 24060, USA Received 15 April 2002; received in revised form 14 December 2002; accepted 16 December 2002 Abstract This paper presents distributed algorithms for both radial and looped load flows for unbalanced, multi-phase power distribution systems. The distributed algorithms are developed from tree-based sequential algorithms. Formulas of scalability for the distributed algorithms are presented. It is shown that computation time dominates communication time in the distributed computing model. This provides benefits to real-time load flow calculations, network reconfigurations, and optimization studies that rely on load flow calculations. Also, test results match the predictions of derived formulas. This shows the formulas can be used to predict the computation time when additional processors are involved. # 2003 Elsevier Science B.V. All rights reserved. Keywords: Distributed computing; Scalability analysis; Radial load flow; Looped load flow; Power distribution systems 1. Introduction Also, the method presented in Ref. [10] was tested in radial distribution systems with no more than 528 buses. Parallel and distributed computing has been applied More recent works [11Á/14] presented distributed to many scientific and engineering computations such as implementations for power flows or power flow based weather forecasting and nuclear simulations [1,2]. It also algorithms like optimizations and contingency analysis. has been applied to power system analysis calculations These works also targeted power transmission systems. [3Á/14].
    [Show full text]
  • Scalability and Performance Management of Internet Applications in the Cloud
    Hasso-Plattner-Institut University of Potsdam Internet Technology and Systems Group Scalability and Performance Management of Internet Applications in the Cloud A thesis submitted for the degree of "Doktors der Ingenieurwissenschaften" (Dr.-Ing.) in IT Systems Engineering Faculty of Mathematics and Natural Sciences University of Potsdam By: Wesam Dawoud Supervisor: Prof. Dr. Christoph Meinel Potsdam, Germany, March 2013 This work is licensed under a Creative Commons License: Attribution – Noncommercial – No Derivative Works 3.0 Germany To view a copy of this license visit http://creativecommons.org/licenses/by-nc-nd/3.0/de/ Published online at the Institutional Repository of the University of Potsdam: URL http://opus.kobv.de/ubp/volltexte/2013/6818/ URN urn:nbn:de:kobv:517-opus-68187 http://nbn-resolving.de/urn:nbn:de:kobv:517-opus-68187 To my lovely parents To my lovely wife Safaa To my lovely kids Shatha and Yazan Acknowledgements At Hasso Plattner Institute (HPI), I had the opportunity to meet many wonderful people. It is my pleasure to thank those who sup- ported me to make this thesis possible. First and foremost, I would like to thank my Ph.D. supervisor, Prof. Dr. Christoph Meinel, for his continues support. In spite of his tight schedule, he always found the time to discuss, guide, and motivate my research ideas. The thanks are extended to Dr. Karin-Irene Eiermann for assisting me even before moving to Germany. I am also grateful for Michaela Schmitz. She managed everything well to make everyones life easier. I owe a thanks to Dr. Nemeth Sharon for helping me to improve my English writing skills.
    [Show full text]
  • A Quantitative Reliability, Maintainability and Supportability Approach for NASA's Second Generation Reusable Launch Vehicle
    A Quantitative Reliability, Maintainability and Supportability Approach for NASA's Second Generation Reusable Launch Vehicle Fayssai M. Safie, Ph. D. Marshall Space Flight Center Huntsville, Alabama Tel: 256-544-5278 E-mail: Fayssal.Safie @ msfc.nasa.gov Charles Daniel, Ph.D. Marshall Space Flight Center Huntsville, Alabama Tel: 256-544-5278 E-mail: Charles.Daniel @msfc.nasa.gov Prince Kalia Raytheon ITSS Marshall Space Flight Center Huntsville, Alabama Tel: 256-544-6871 E-mail: Prince.Kalia @ msfc.nasa.gov ABSTRACT The United States National Aeronautics and Space Administration (NASA) is in the midst of a 10-year Second Generation Reusable Launch Vehicle (RLV) program to improve its space transportation capabilities for both cargo and crewed missions. The objectives of the program are to: significantly increase safety and reliability, reduce the cost of accessing low-earth orbit, attempt to leverage commercial launch capabilities, and provide a growth path for manned space exploration. The safety, reliability and life cycle cost of the next generation vehicles are major concerns, and NASA aims to achieve orders of magnitude improvement in these areas. To get these significant improvements, requires a rigorous process that addresses Reliability, Maintainability and Supportability (RMS) and safety through all the phases of the life cycle of the program. This paper discusses the RMS process being implemented for the Second Generation RLV program. 1.0 INTRODUCTION The 2nd Generation RLV program has in place quantitative Level-I RMS, and cost requirements [Ref 1] as shown in Table 1, a paradigm shift from the Space Shuttle program. This paradigm shift is generating a change in how space flight system design is approached.
    [Show full text]
  • Software Quality Management
    Software Quality Management 2004-2005 Marco Scotto ([email protected]) Software Quality Management Contents ¾Definitions ¾Quality of the software product ¾Special features of software ¾ Early software quality models •Boehm model • McCall model ¾ Standard ISO 9126 Software Quality Management 2 Definitions ¾ Software: intellectual product consisting of information stored on a storage device (ISO/DIS 9000: 2000) • Software may occur as concepts, transactions, procedures. One example of software is a computer program • Software is "intellectual creation comprising the programs, procedures, rules and any associated documentation pertaining to the operation of a data processing system" •A software product is the "complete set of computer programs, procedures and associated documentation and data designated for delivery to a user" [ISO 9000-3] • Software is independent of the medium on which it is recorded Software Quality Management 3 Quality of the software product ¾The product should, on the highest level… • Ensure the satisfaction of the user needs • Ensure its proper use ¾ Earlier: 1 developer, 1 user • The program should run and produce results similar to those expected ¾ Later: more developers, more users • Need to economical use of the storage devices • Understandability, portability • User-friendliness, learnability ¾ Nowadays: • Efficiency, reliability, no errors, able to restart without using data Software Quality Management 4 Special features of software (1/6) ¾ Why is software ”different”? • Does not really have “physical” existence
    [Show full text]
  • Scalability and Optimization Strategies for GPU Enhanced Neural Networks (Genn)
    Scalability and Optimization Strategies for GPU Enhanced Neural Networks (GeNN) Naresh Balaji1, Esin Yavuz2, Thomas Nowotny2 {T.Nowotny, E.Yavuz}@sussex.ac.uk, [email protected] 1National Institute of Technology, Tiruchirappalli, India 2School of Engineering and Informatics, University of Sussex, Brighton, UK Abstract: Simulation of spiking neural networks has been traditionally done on high-performance supercomputers or large-scale clusters. Utilizing the parallel nature of neural network computation algorithms, GeNN (GPU Enhanced Neural Network) provides a simulation environment that performs on General Purpose NVIDIA GPUs with a code generation based approach. GeNN allows the users to design and simulate neural networks by specifying the populations of neurons at different stages, their synapse connection densities and the model of individual neurons. In this report we describe work on how to scale synaptic weights based on the configuration of the user-defined network to ensure sufficient spiking and subsequent effective learning. We also discuss optimization strategies particular to GPU computing: sparse representation of synapse connections and occupancy based block-size determination. Keywords: Spiking Neural Network, GPGPU, CUDA, code-generation, occupancy, optimization 1. Introduction The computational performance of traditional single-core CPUs has steadily increased since its arrival, primarily due to the combination of increased clock frequency, process technology advancements and compiler optimizations. The clock frequency was pushed higher and higher, from 5 MHz to 3 GHz in the years from 1983 to 2002, until it reached a stall a few years ago [1] when the power consumption and dissipation of the transistors reached peaks that could not compensated by its cost [2].
    [Show full text]
  • Software Maintainability and Usability in Agile Environment
    Software Maintainability and Usability in Agile Environment {tag} {/tag} International Journal of Computer Applications © 2013 by IJCA Journal Volume 68 - Number 4 Year of Publication: 2013 Authors: Monika Agarwal Rana Majumdar 10.5120/11569-6873 {bibtex}pxc3886873.bib{/bibtex} Abstract This research is based on software maintainability and usability in the agile environment. Maintainability of the system is the ability to undergo changes relatively easily. These changes can affect components, services, interfaces and functionality when adding or changing functions, errors, and respond to business needs. Usability is defined as the application that meets the requirements of users and consumers by providing an intuitive, easy to locate and globalize and provides good access for disabled users and leads to a good overall user experience. In the conventional method of the software development, there are many metrics to calculate the maintenance and use of software. This research is to determine whether the same measures apply to Agile, or there is a need to change some metrics used for the agile environment. The goal of software engineering is to develop good quality maintainable software in schedule and budget. Inflated software costing, delayed time frame, or not meeting quality standards express a failure. A survey suggests about 45% of software fails due to the lack of quality. It is therefore one of the most important aspects for the success of software. Refer ences 1 / 3 Software Maintainability and Usability in Agile Environment - P. Antonellis, D. Antoniou, Y. Kanellopoulos, C. Makris, E. Theodoridis, C. Tjortjis, and N. Tsirakis, "A data mining methodology for evaluating maintainability according to ISO/IEC-9126 software engineering – product quality standard," in Special Session on System Quality and Maintainability - SQM2007, 2007.
    [Show full text]
  • Parallel System Performance: Evaluation & Scalability
    ParallelParallel SystemSystem Performance:Performance: EvaluationEvaluation && ScalabilityScalability • Factors affecting parallel system performance: – Algorithm-related, parallel program related, architecture/hardware-related. • Workload-Driven Quantitative Architectural Evaluation: – Select applications or suite of benchmarks to evaluate architecture either on real or simulated machine. – From measured performance results compute performance metrics: • Speedup, System Efficiency, Redundancy, Utilization, Quality of Parallelism. – Resource-oriented Workload scaling models: How the speedup of a parallel computation is affected subject to specific constraints: 1 • Problem constrained (PC): Fixed-load Model. 2 • Time constrained (TC): Fixed-time Model. 3 • Memory constrained (MC): Fixed-Memory Model. • Parallel Performance Scalability: For a given parallel system and a given parallel computation/problem/algorithm – Definition. Informally: – Conditions of scalability. The ability of parallel system performance to increase – Factors affecting scalability. with increased problem size and system size. Parallel Computer Architecture, Chapter 4 EECC756 - Shaaban Parallel Programming, Chapter 1, handout #1 lec # 9 Spring2013 4-23-2013 Parallel Program Performance • Parallel processing goal is to maximize speedup: Time(1) Sequential Work Speedup = < Time(p) Max (Work + Synch Wait Time + Comm Cost + Extra Work) Fixed Problem Size Speedup Max for any processor Parallelizing Overheads • By: 1 – Balancing computations/overheads (workload) on processors
    [Show full text]
  • Adaptability Evaluation at Software Architecture Level Pentti Tarvainen*
    The Open Software Engineering Journal, 2008, 2, 1-30 1 Open Access Adaptability Evaluation at Software Architecture Level Pentti Tarvainen* VTT Technical Research Centre of Finland, Kaitoväylä 1, P.O. Box 1100, FIN-90571 Oulu, Finland Abstract: Quality of software is one of the major issues in software intensive systems and it is important to analyze it as early as possible. An increasingly important quality attribute of complex software systems is adaptability. Software archi- tecture for adaptive software systems should be flexible enough to allow components to change their behaviors depending upon the environmental and stakeholders' changes and goals of the system. Evaluating adaptability at software architec- ture level to identify the weaknesses of the architecture and further to improve adaptability of the architecture are very important tasks for software architects today. Our contribution is an Adaptability Evaluation Method (AEM) that defines, before system implementation, how adaptability requirements can be negotiated and mapped to the architecture, how they can be represented in architectural models, and how the architecture can be evaluated and analyzed in order to validate whether or not the requirements are met. AEM fills the gap from requirements engineering to evaluation and provides an approach for adaptability evaluation at the software architecture level. In this paper AEM is described and validated with a real-world wireless environment control system. Furthermore, adaptability aspects, role of quality attributes, and diversity of adaptability definitions at software architecture level are discussed. Keywords: Adaptability, adaptation, adaptive software architecture, software quality, software quality attribute. INTRODUCTION understand the system [6]. Examples of design decisions are the decisions such as “we shall separate user interface from Today, quality of a software system plays an increasingly the rest of the application to make both user interface and important role in the domain of software engineering.
    [Show full text]
  • Multiprocessing and Scalability
    Multiprocessing and Scalability A.R. Hurson Computer Science and Engineering The Pennsylvania State University 1 Multiprocessing and Scalability Large-scale multiprocessor systems have long held the promise of substantially higher performance than traditional uni- processor systems. However, due to a number of difficult problems, the potential of these machines has been difficult to realize. This is because of the: Fall 2004 2 Multiprocessing and Scalability Advances in technology ─ Rate of increase in performance of uni-processor, Complexity of multiprocessor system design ─ This drastically effected the cost and implementation cycle. Programmability of multiprocessor system ─ Design complexity of parallel algorithms and parallel programs. Fall 2004 3 Multiprocessing and Scalability Programming a parallel machine is more difficult than a sequential one. In addition, it takes much effort to port an existing sequential program to a parallel machine than to a newly developed sequential machine. Lack of good parallel programming environments and standard parallel languages also has further aggravated this issue. Fall 2004 4 Multiprocessing and Scalability As a result, absolute performance of many early concurrent machines was not significantly better than available or soon- to-be available uni-processors. Fall 2004 5 Multiprocessing and Scalability Recently, there has been an increased interest in large-scale or massively parallel processing systems. This interest stems from many factors, including: Advances in integrated technology. Very
    [Show full text]
  • Software Maintainability and Reusability Using Cohesion Metrics
    International Journal of Computer Trends and Technology (IJCTT) – Volume 54 Issue 2-December2017 Software Maintainability and Reusability using Cohesion Metrics Adekola, O.D#1, Idowu, S.A*2, Okolie, S.O#3, Joshua, J.V#4, Akinsanya, A.O*5, Eze, M.O#6, EbiesuwaSeun#7 #1Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria *2Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria #3Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria #4Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria *5Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria #6Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria #7Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria Abstract - Among others, remarkable external software’s lifetime. Ahn et al., (2003) estimated that quality attributes of interest to software practitioners/ maintenance takes up to 80% of the total costof engineers include testability, maintainability and producing software applications. Expectation of reusability.Software engineers still combat achieving more reliable, quicker time-to-market and softwarecrisis and even chronic software affliction maintainable systems. A lot of research has gone into not because there is no standardized software the areas of software reuse and maintenance due to development process but because enough attention is the fact that these among other issues concern not given to seemingly insignificant but crucial intimately system developers/architects/engineers details of internal design attributes such as cohesion rather than end-users. Therehas been enormous and coupling especially in object-oriented systems. growth in software reuse research from the days of Consequently, the aftermath is increased structured programming concepts to object-oriented maintenance cost, effort and time which negatively methods and beyond (e.g.
    [Show full text]
  • Pascal Viewer: a Tool for the Visualization of Parallel Scalability Trends
    PaScal Viewer: a Tool for the Visualization of Parallel Scalability Trends 1st Anderson B. N. da Silva 2nd Daniel A. M. Cunha Pro-Reitoria´ de Pesquisa, Inovac¸ao˜ e Pos-Graduac¸´ ao˜ Dept. de Eng. de Comp. e Automac¸ao˜ Instituto Federal da Paraiba Univ. Federal do Rio Grande do Norte Joao Pessoa, Brazil Natal, Brazil [email protected] [email protected] 3st Vitor R. G. Silva 4th Alex F. de A. Furtunato 5th Samuel Xavier de Souza Dept. de Eng. de Comp. e Automac¸ao˜ Diretoria de Tecnologia da Informac¸ao˜ Dept. de Eng. de Comp. e Automac¸ao˜ Univ. Federal do Rio Grande do Norte Instituto Federal do Rio Grande do Norte Univ. Federal do Rio Grande do Norte Natal, Brazil Natal, Brazil Natal, Brazil [email protected] [email protected] [email protected] Abstract—Taking advantage of the growing number of cores particular environment. The configuration of this environment in supercomputers to increase the scalabilty of parallel programs includes the number of cores, their operating frequency, and is an increasing challenge. Many advanced profiling tools have the size of the input data or the problem size. Among the var- been developed to assist programmers in the process of analyzing data related to the execution of their program. Programmers ious collected information, the elapsed time in each function can act upon the information generated by these data and make of the code, the number of function calls, and the memory their programs reach higher performance levels. However, the consumption of the program can be cited to name just a few information provided by profiling tools is generally designed [2].
    [Show full text]