From Customer Value Constellation to Service Experience Blueprinting
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
PMR 5020 Modelagem Do Projeto De Sistemas Aula 2: Sistemas E Seu Processo De Projeto Prof
PMR 5020 Modelagem do Projeto de Sistemas Aula 2: Sistemas e seu processo de projeto Prof. José Reinaldo Silva [email protected] PMR5020 Escola Politécnica da USP 1 O Design Mecatrônico (Mechatronic Design) Sistema de informação Sistema Mecânico Artefato Mecatrônico Sistema de controle Sistema Eletrônico Prof. José Reinaldo Silva PMR5020 Escola Politécnica da USP 2 O noso artefato alvo… Sistemas Não tem fronteiras óbvias Não tem um “corpo” material Geralmente acoplado Prof. José Reinaldo Silva PMR5020 Escola Politécnica da USP 3 Um sistema é um conjunto de objetos distinguíveis – não necessariamente homogêneo – que trabalham em conjunto para atingir um objetivo coletivo. Eventualmente cada um dos elementos constituintes pode ser também um sistema menor do que o sistema que o contém. Assim a definição é recursiva e convergente. Existem uma (ou mais) categorias de elemento constituinte tal que não vale a pena imergir nos detalhes internos deste, isto é, a precisão dos detalhes não contribui em nada seja para o funcionamento do sistema, seja para entender a sua funcionalidade. Prof. José Reinaldo Silva PMR5020 Escola Politécnica da USP 4 Teoria de sistemas Proposta em 1940 por Ludwig von Bartalanffy Em busca da unificação da ciência X reducionismo Prof. José Reinaldo Silva PMR5020 Escola Politécnica da USP 5 Sistema: uma definição holônica Um sistema é definido pelo par ordenado S=(A, R) onde A é um conjunto de elementos constituintes (objetos) relevantes A e R o conjunto R de relações definidas entre estes objetos. Eventual- mente um elemento de A tem as mesmas características do sistema e é chamado de sub-sistema de S. -
Chapter 1: Introduction
Just Enough Structured Analysis Chapter 1: Introduction “The beginnings and endings of all human undertakings are untidy, the building of a house, the writing of a novel, the demolition of a bridge, and, eminently, the finish of a voyage.” — John Galsworthy Over the River, 1933 www.yourdon.com ©2006 Ed Yourdon - rev. 051406 In this chapter, you will learn: 1. Why systems analysis is interesting; 2. Why systems analysis is more difficult than programming; and 3. Why it is important to be familiar with systems analysis. Chances are that you groaned when you first picked up this book, seeing how heavy and thick it was. The prospect of reading such a long, technical book is enough to make anyone gloomy; fortunately, just as long journeys take place one day at a time, and ultimately one step at a time, so long books get read one chapter at a time, and ultimately one sentence at a time. 1.1 Why is systems analysis interesting? Long books are often dull; fortunately, the subject matter of this book — systems analysis — is interesting. In fact, systems analysis is more interesting than anything I know, with the possible exception of sex and some rare vintages of Australian wine. Without a doubt, it is more interesting than computer programming (not that programming is dull) because it involves studying the interactions of people, and disparate groups of people, and computers and organizations. As Tom DeMarco said in his delightful book, Structured Analysis and Systems Specification (DeMarco, 1978), [systems] analysis is frustrating, full of complex interpersonal relationships, indefinite, and difficult. -
Users, Roles, and Personas (PDF)
Constantine & Lockwood, Ltd. PREPRINT Users, Roles, and Personas Larry Constantine, IDSA Chief Scientist, Constantine & Lockwood, Ltd. You cannot think outside the box when you are trying to represent a box. Brian Hayes To do effective design you need to understand your users and their needs. While no credible school of thought in design would take serious exception, opinions vary considerably on how best to gain that understanding and how to record and communicate it once you do. Models of one form or another are the medium for the message in most design methods. Models function as intermediaries between the often ambiguous, overwhelmingly complex reality of actual users and the more narrowly focused and specific needs of designers. In usage-centered design (see sidebar, “Users or Usage”), user roles capture and carry the essential understanding about users. User roles, one of the three core models of usage-centered design, are close cousins of personas but differ in a number of ways of potential significance to designers. In an attempt to sound a counterpoint to complement the main themes of the book, this chapter introduces user roles in the context of usage-centered design and explores the relationships between user roles and personas. Compared to typical personas as presented in this book and elsewhere, user roles are a more compact and concise representation that is more finely focused on issues with direct relevance for visual and interaction design. For these reasons, user role models can also be simpler and faster to develop. Although roles and personas can complement each other, user role models may also, under some circumstances and for some purposes, offer distinct advantages for designers. -
Contents U U U
Contents u u u ACM Awards Reception and Banquet, June 2018 .................................................. 2 Introduction ......................................................................................................................... 3 A.M. Turing Award .............................................................................................................. 4 ACM Prize in Computing ................................................................................................. 5 ACM Charles P. “Chuck” Thacker Breakthrough in Computing Award ............. 6 ACM – AAAI Allen Newell Award .................................................................................. 7 Software System Award ................................................................................................... 8 Grace Murray Hopper Award ......................................................................................... 9 Paris Kanellakis Theory and Practice Award ...........................................................10 Karl V. Karlstrom Outstanding Educator Award .....................................................11 Eugene L. Lawler Award for Humanitarian Contributions within Computer Science and Informatics ..........................................................12 Distinguished Service Award .......................................................................................13 ACM Athena Lecturer Award ........................................................................................14 Outstanding Contribution -
Survey of Pen-And-Paper Computing
Human-Computer Interaction Series Editors-in-chief John Karat Jean Vanderdonckt, Université Catholique de Louvain, Belgium Editorial Board Gaëlle Calvary, LIG-University of Grenoble 1, France John Carroll, Penn State University, USA. Gilbert Cockton, Northumbria University, Newcastle, UK Larry Constantine, University of Madeira, Portugal Steven Feiner, Columbia University, USA Peter Forbrig, Universität Rostock, Germany Elizabeth Furtado, University of Fortaleza, Brazil Hans Gellersen, Lancaster University, UK Robert Jacob, Tufts University, USA Hilary Johnson, University of Bath, UK Dianne Murray, Putting People Before Computers, UK Kumiyo Nakakoji, University of Tokyo, Japan Philippe Palanque, Université Paul Sabatier, France Oscar Pastor, University of Valencia, Spain Fabio Pianesi, Istituto Trentino di Cultura, Italy Costin Pribeanu, National Institute for Research & Development in Informatics, Romania Gerd Szwillus, Universität Paderborn, Germany Manfred Tscheligi, Center for Usability Research and Engineering, Austria Gerrit van der Veer, Vrije Universiteit Amsterdam, The Netherlands Shumin Zhai, IBM Almaden Research Center, USA Thomas Ziegert, SAP Research CEC Darmstadt,Germany Human-computer interaction is a multidisciplinary field focused on human aspects of the de- velopment of computer technology. As computer-based technology becomes increasingly per- vasive – not just in developed countries, but worldwide – the need to take a human-centered approach in the design and development of this technology becomes ever more important. For roughly 30 years now, researchers and practitioners in computational and behavioral sciences have worked to identify theory and practice that influences the direction of these technologies, and this diverse work makes up the field of human-computer interaction. Broadly speaking it includes the study of what technology might be able to do for people and how people might interact with the technology. -
Algorithms (One of the Following) L Buy the Book - Introduction to Algorithms, Thomas H
Level 9 Reading List [ladder home page] [ladder overview] [reading list] [pyramid] Required reading Recommended Reading Appropriate Optional Reading The top list is a recommendation by category. Detailed book descriptions follow the summary table. R Algorithms (one of the following) L Buy the book - Introduction to Algorithms, Thomas H. Cormen, et al Buy the book - Data Structures and Algorithms, Aho, Hopcraft, and Ullman Buy the book - Algorithms in C++, Robert Sedgewick Buy vol.1 Buy vol.2 - The Art of Computer Programming (vols. 1-3), Donald Knuth Buy vol.3 Construction Practices Buy the book A Code Complete, Steve McConnell Buy the book A Programming Pearls, Jon Bentley Buy the book - Practice of Programming, Brian Kernighan and Rob Pike Buy the book - Writing Solid Code, Steve Maguire Buy the Book - Programming on Purpose: Essays on Software Design, P. J. Plauger Buy the book - Programmers at Work, Susan Lammers Software Development Overview Buy the book. A 201 Principles of Software Development, Alan M. Davis Get the article A "The Humble Programmer," Edsger Dijkstra "Software Engineering Programmes are not Computer Science Programmes," David Get the article A Parnas Get the article A "They Write the Right Stuff ," Charles Fishman Buy the book - Software Engineering, Ian Sommerville Buy the book - Software Engineering: A Practitioner's Approach, Roger Pressman Professional Ethics Get the code A Software Engineering Code of Ethics and Professional Practice, ACM/IEEE-CS Periodicals Subscribe - Software Development Subscribe - IEEE Software Algorithms Introduction to Algorithms, Thomas H. Cormen, et al. This comprehensive book contains an exhaustive discussion of specific algorithms, algorithm analysis, and algorithm design (though not as exhaustive as Knuth's seven volume series). -
CALIFORNIA STATE UNIVERSITY, NORTHRIDGE the EVOLUTION of SOFTWARE DESIGN IDEAS a Thesis Submitted in Partial Satisfaction Of
CALIFORNIA STATE UNIVERSITY, NORTHRIDGE THE EVOLUTION OF SOFTWARE DESIGN IDEAS A thesis submitted in partial satisfaction of the requirements for the degree of Master of Science in Computer Science by David J. Koepke May 1985 The thesis of David J. Koepke is approved: Professor Diane Schwartz Professor Russell '1:1;;'{t;Chair California State University, Northridge 11 ACKNOWLEDGEMENTS I would like to express my sincere gratitude to Professor Russ Abbott for all the enlightening conversations, suggestions, and generous extended use of his software design books and articles. I would also like to thank Pat Morales for her vital assistance in typing and revising this thesis, typing and distributing the inquiry letters, and her moral support throughout this project. A special thanks to Larry Constantine, Edsger Dijkstra, C.A.R. Hoare, James Emery and Donald Knuth for their responses to my questions on the history of software design. iii TABLE OF CONTENTS Page List of Figures ..................................... vii Abstract . Vlll Chapter 1 INTRODUCTION . 1 1.1 Overview of Thesis . 3 1.2 Previous Historical Texts 4 1.3 Historical Errors . 4 1.4 Design Influences of the Past 6 Chapter 2 ABSTRACTION 9 2.1 Early Abstraction 10 2.2 Top-Down Design/Stepwise Refinement 14 2.3 Levels of Abstraction . 20 2.4 Program Families 22 2.5 Abstract Data Types 24 2.6 Summary 32 Chapter 3 MODULARITY 34 3.1 Early Modularity 35 3.2 Information Hiding ..•.....• 42 3.3 Object-Oriented Programming 46 3.4 Summary ................................ 53 iv Chapter 4 STRUCTURED PROGRAMMING 54 4.1 Genesis of Structured Programming .