The calculus of IT support for the banking, securities, and insurance industries has changed dramatically and rapidly over the past few years. Consolidation and deregulation are creating opportunities and challenges never before seen. Unheard of just a few years ago, e-commerce has given birth to new infrastructures and departments needed to support them. And the Internet/Intranet/Extranet triple-whammy is the most critical component of most financial IT shops. At the same time, new intelligent agents stand ready to take on such diverse functions as customer profiling and data mining. Get a handle on all these new and newer ripples with Financial Services Information Systems. Here, in this exhaustive new guide and reference book, industry guru Jessica Keyes gives you the no-nonsense scoop on not just the tried and true IT tools of today, but also the up-and-coming "hot" technologies of tomorrow, and how to plan for them. Financial Services Information Systems addresses challenges and solutions associated with: supporting the self-service revolution by servicing kiosks and ATMs efficiently and economically, straight-through processing for the securities industry, outsourcing business communications in the insurance industry, distributed integration as a cost-effective alternative to data warehousing, and putting inbound fax automation to work in financial organizations.

To achieve consistent software project success under the pressures of today's software development environment, software organizations require achievable plans including viable estimates of schedule, resources, and risks. To estimate realistically, you must understand how to apply sound estimation processes, tools, and data. Software Sizing, Estimation, and Risk Management: When Performance is Measured Performance Improves is a practical, hands-on discussion of the software estimation, planning, and control process. This includes critical factors that impact estimates, methods for selecting and applying appropriate measures to projects, proper software sizing, and processes to identify and manage risk. The authors use their expertise in sizing, estimation, process engineering, and risk management to clearly demonstrate problems that make many estimates crumble and solutions that provide successful project plans. The book offers insight not available anywhere else, enabling you to recognize and avoid downstream impacts resulting from poor estimates.

Based upon the authors' experience in designing and deploying an embedded Linux system with a variety of applications, Embedded Linux System Design and Development contains a full embedded Linux system development roadmap for systems architects and software programmers. Explaining the issues that arise out of the use of Linux in embedded systems, the book facilitates movement to embedded Linux from traditional real-time operating systems, and describes the system design model containing embedded Linux. This book delivers practical solutions for writing, debugging, and profiling applications and drivers in embedded Linux, and for understanding Linux BSP architecture. It enables you to understand: various drivers such as serial, I2C and USB gadgets; uClinux architecture and its programming model; and the embedded Linux graphics subsystem. The text also promotes learning of methods to reduce system boot time, optimize memory and storage, and find memory leaks and corruption in applications. This volume benefits IT managers in planning to choose an embedded Linux distribution and in creating a roadmap for OS transition. It also describes the application of the Linux licensing model in commercial products.

Learn the critical tips and techniques to make using Xcode for the iPhone, iPad, or Mac easier, and even fun. Explore the features and functionality of Xcode you may not have heard of. Go under the hood to discover how projects really work, so when they stop working, you'll know how to fix them. Explore the common problems developers face when using Xcode, and find out how to get the most out of your IDE. Dig into Xcode, and you'll discover it's richer and more powerful than you might have thought. Get a huge productivity boost by working with Xcode instead of against it. Instead of hacky code fixes and manual processes, once you know the the why and how of Xcode's process, you'll discover that doing things Xcode's way makes your app development more elegant and less aggravating. Explore the major features of Xcode: project management, building UIs with storyboards, code editing, compiling apps, fixing bugs and performance problems, unit- and UI testing, and source code management. Go beyond the basics and explore tasks that professionals deal with when they're working on big projects. Create storyboards that many developers can work on at once, even as projects grow to hundreds or thousands of files. Find the tools that make the code editor pleasant to work with, even in long coding sessions. Discover the right way to find and fix bugs when you have lots of code that's not always playing nicely together. Dig into specific and little-discussed features that help developers on Apple's other platforms: macOS, watchOS, and tvOS. When you're ready to distribute your app, learn how Apple's code-signing system really works. Find out when to let Xcode handle it automatically, and how to do it manually when needed. Discover how much easier and more fun iOS development is when you know the secrets of the tools. What You Need: This book requires Xcode 9 and a Mac running macOS High Sierra (10.13.2) or later. Additionally, an iOS device is recommended for on-device testing but not required.

Characterized by lightning quick innovation, abrupt shifts in technology, and shorter lifecycles, the marketing of IT products and services presents a unique set of challenges and often requires IT managers and developers to get involved in the marketing process. Marketing IT Products and Services is written to help busy IT managers and marketing managers get up to speed quickly and easily on what's needed to develop effective marketing strategies and campaigns. Focusing on the unique issues involved, this one-stop resource provides everything needed to understand the roles, responsibilities, and management techniques essential for the development of successful strategies. It covers strategic market planning, targeting markets, researching markets, understanding the competition, integrating market and sales strategies, nuances of global markets, developing marketing budgets, pricing, and implementing marketing campaigns. A plethora of appendices included on the book's downloadable resources allow you to get up and running right away. Aside from a complete marketing glossary, two complete marketing plans-one for a hardware product; the other for a software product-enable you to bypass the "scut" work of developing a marketing plan so you can focus on the creative aspects of marketing. Because a marketing plan is closely aligned with an organization's business and strategic plans, this book provides you with templates for both of these, as well as a template for that all-important business plan executive summary. The downloadable resources also feature loads of fill-in templates including customer and competitor analysis surveys, sample press releases, letters of agreement, demographic and target market worksheets, and cost benefit forms. If you have a marketing need, this book has an effective template to meet that need.

Delivering successful projects means the ability to produce high quality software within budget and on time-consistently, but when one mentions quality to software engineers or project managers, they talk about how impossible it is to eliminate defects from software. This assumption is passed on and on until it becomes accepted wisdom, with the power of a self-fulfilling prophecy. And when a project fails to arrive on time or up to standards, team members will turn on each other. The project got delayed because the engineers did a poor job in development or too much was promised upfront for this short of a timeline. In Delivering Successful Projects with TSPSM and Six Sigma: A Practical Guide to Implementing Team Software ProcessSM, you will learn how to effectively manage the development of a software project and deliver it in line with customer expectations. This refreshing volume - Offers real-world case studies about the author's experience at Microsoft successfully implementing TSP to achieve higher quality software Empowers software developers to take responsibility for project management Explains how Six Sigma and TSP combined can dramatically reduce software defects By applying these principles put forth by one of the most respected names in software development, your software team will learn how to function as a team and turn out products where zero defects and on-time delivery are the norm.

Modeling complex systems is a difficult challenge and all too often one in which modelers are left to their own devices. Using a multidisciplinary approach, The Art of Software Modeling covers theory, practice, and presentation in detail. It focuses on the importance of model creation and demonstrates how to create meaningful models. Presenting three self-contained sections, the text examines the background of modeling and frameworks for organizing information. It identifies techniques for researching and capturing client and system information and addresses the challenges of presenting models to specific audiences. Using concepts from art theory and aesthetics, this broad-based approach encompasses software practices, cognitive science, and information presentation. The book also looks at perception and cognition of diagrams, view composition, color theory, and presentation techniques. Providing practical methods for investigating and organizing complex information, The Art of Software Modeling demonstrates the effective use of modeling techniques to improve the development process and establish a functional, useful, and maintainable software system.

Modeling Software with Finite State Machines: A Practical Approach explains how to apply finite state machines to software development. It provides a critical analysis of using finite state machines as a foundation for executable specifications to reduce software development effort and improve quality. This book discusses the design of a state machine and of a system of state machines. It also presents a detailed analysis of development issues relating to behavior modeling with design examples and design rules for using finite state machines. This volume describes a coherent and well-tested framework for generating reliable software for even the most complex tasks. The authors demonstrate that the established practice of using a specification as a basis for coding is wrong. Divided into three parts, this book opens by delivering the authors' expert opinions on software, covering the evolution of development as well as costs, methods, programmers, and the development cycle. The remaining two parts encourage the use of state machines: promoting the virtual finite state machine (Vfsm) method and the StateWORKS development tools.

A developer's knowledge of a computing system's requirements is necessarily imperfect because organizations change. Many requirements lie in the future and are unknowable at the time the system is designed and built. To avoid burdensome maintenance costs developers must therefore rely on a system's ability to change gracefully-its flexibility. Flexible Software Design: Systems Development for Changing Requirements demonstrates the design principles and techniques that enable the design of software that empowers business staff to make functional changes to their systems with little or no professional IT intervention. The book concentrates on the design aspects of system development, the area with the most flexibility leverage. Divided into four parts, the text begins by introducing the fundamental concepts of flexibility, explaining the reality of imperfect knowledge and how development participants must change their thinking to implement flexible software. The second part covers design guidelines, stable identifiers, stable information structures, the Generic Entity Cloud concept, and regulatory mechanisms that give business staff control over system modifications. Part three relates strategic information systems planning to flexible systems. It examines the elicitation of requirements and the relevance of agile methods in a flexible systems environment. It also discusses practical aspects of stable identifier design and compares the testing of traditional and flexible software. In part four, the book concludes with details of the flexible UniverSIS system and an explanation of the applications and extensions of the Generic Entity Cloud tools. The combination of smart design and smart work offered in Flexible Software Design can materially benefit your organization by radically reducing the systems maintenance burden.

With the recent Electronic Signatures in Global and National Commerce Act, public key cryptography, digital signatures, and digital certificates are finally emerging as a ubiquitous part of the Information Technology landscape. Although these technologies have been around for over twenty years, this legislative move will surely boost e-commerce activity. Secure electronic business transactions, such as contracts, legal documents, insurance, and bank loans are now legally recognized. In order to adjust to the realities of the marketplace, other services may be needed, such as a non-repudiation service, digital notary, or digital time-stamping service. The collection of these components, known as Public Key Infrastructure (PKI), is paving the way for secure communications within organizations and on the public Internet.

The product of many years of practical experience and research in the software measurement business, this technical reference helps you select what metrics to collect, how to convert measurement data to management information, and provides the statistics necessary to perform these conversions. The author explains how to manage software development measurement systems, how to build software measurement tools and standards, and how to construct controlled experiments using standardized measurement tools. There are three fundamental questions that this book seeks to answer. First, exactly how do you get the measurement data? Second, how do you convert the data from the measurement process to information that you can use to manage the software development process? Third, how do you manage all of the data? Millions of dollars are being spent trying to secure software systems. When suitable instrumentation is placed into the systems that we develop, their activity can be monitored in real time. Measurement based automatic detection mechanisms can be designed into systems. This will permit the detection of system misuse and detect incipient reliability problems. By demonstrating how to develop simple experiments for the empirical validation of theoretical research and showing how to convert measurement data into meaningful and valuable information, this text fosters more precise use of software measurement in the computer science and software engineering literature. Software Engineering Measurement shows you how to convert your measurement data to valuable information that can be used immediately for software process improvement.

Novel in its approach to software design, development, and management, Building Software: A Practitioner's Guide shows you how to successfully build and manage a system. The approach the authors recommend is a simple, effective framework known as Solution Engineering Execution (SEE). Through SEE, you create a successful solution by following a highly organized, well-planned process. This process makes you view the solution from a holistic, systematic perspective. Developing a successful system requires that you are able to address technology matters related to architecture, design, selection, integration, and security. Building Software: A Practitioner's Guide offers insight into how to make software reliable and how to ensure it meets customer and organizational needs. Using the above approach you are able to: Find a good solution to the problem at hand Focus on engineering the solution well Address all aspects of delivery associated with the solution The book provides insightful examples of cross-domain and legacy solutions that allow you to overcome common software concerns such as requirement issues, change control, quality and schedule management, and internal and external communication problems.

UML for Developing Knowledge Management Systems provides knowledge engineers the framework in which to identify types of knowledge and where this knowledge exists in an organization. It also shows ways in which to use a standard recognized notation to capture, or model, knowledge to be used in a knowledge management system (KMS). This volume enables knowledge engineers, systems analysts, designers, developers, and researchers to understand the concept of knowledge modeling with Unified Modeling Language (UML). It offers a guide to quantifying, qualifying, understanding, and modeling knowledge by providing a reusable framework that can be adopted for KMS implementation. Following a brief history of knowledge management, the book discusses knowledge acquisition and the types of knowledge that can be discovered within a domain. It offers an overview of types of models and the concepts behind them. It then reviews UML and how to apply UML to model knowledge. The book concludes by defining and applying the Knowledge Acquisition framework via a real-world case study.

Project Managers leading massive IT projects--defined as projects rolling out deliverables across geographic boundaries with budgets ranging well into the millions--need a unique level of expertise and an arsenal of personal and professional skills to successfully accomplish their tasks. Large IT initiatives inherently contain business conditions, technology quirks, and participant and managerial agendas that make them exceedingly difficult to execute. Complex IT Project Management: Sixteen Steps to Success reveals a project management process that the author has proven to be successful in many complex real-world projects. Each step is presented in its logical sequence, with the connections between management methods and project goals clearly defined. The author often refers to the successful tactics he employed, providing you with a strategy to overcome the challenges found in even the most intricate IT projects. This book stands as the perfect tool for project managers at all levels of experience who plan to tackle a high-profile initiative. It also serves as a guide for project sponsors searching for the right manager, and for consultants recommending best practices for the workplace.

Not connecting software project management (SPM) to actual, real-world development processes can lead to a complete divorcing of SPM to software engineering that can undermine any successful software project. By explaining how a layered process architectural model improves operational efficiency, Process-Based Software Project Management outlines a new method that is more effective than the traditional method when dealing with SPM. With a clear and easy-to-read approach, the book discusses the benefits of an integrated project management-process management connection. The described tight coupling of the process world to the SPM world provides a high degree of completeness and accuracy necessary for effective project management. The author shows you that this process-based approach to SPM increases product quality, shortens time-to-market, reduces life cycle costs, facilitates short system test times, and increases developmental supply chain management (SCM) controls and total repeatability. This underlying process approach also actively involves SCM, software quality assurance (SQA), engineering, and accounting as part of your integrated SPM team for total success. Through examples and detailed explanations, Process-Based Software Project Management illustrates how this novel SPM approach is more profitable and time-efficient when compared to traditional SPM methods. The software manager, along with the support team, will finally all be on "the same page" to achieve SPM/engineering success.

Based on an extensive research project done by the author in the United States, Britain, Germany, France, Switzerland, Sweden, and Austria from December 1999 to June 2001, Enterprise Architecture and New Generation Information Systems focuses on four main themes: Next Generation Information Technology The Likely Technologies of this Decade Enterprise Computing The Internet as the 21st Century's Answer to Merchandising While the majority of books presently available on information systems are written from the viewpoint of system analysis, programming, or common applications, this text: Brings to the reader's attention the importance of organization and infrastructure Presents a wealth of case studies to explain the need for reengineering and restructuring Details the latest advances which influence the implementation of advanced technology Written in a simple, comprehensive manner without specific prerequisites and data processing jargon, with concepts and case studies properly explained, this book addresses itself to practitioners in computer technology, telecommunications and software development, who are interested in acquiring skills through knowledge of the most advanced applications, tools, and methods, both present and coming. Enterprise Architecture and New Generation Information Systems will prove appealing to every person charged with planning, developing, applying, and delivering advanced information systems, architectural solutions, and programming products.

If you look around you will find that all computer systems, from your portable devices to the strongest supercomputers, are heterogeneous in nature. The most obvious heterogeneity is the existence of computing nodes of different capabilities (e.g. multicore, GPUs, FPGAs, ...). But there are also other heterogeneity factors that exist in computing systems, like the memory system components, interconnection, etc. The main reason for these different types of heterogeneity is to have good performance with power efficiency. Heterogeneous computing results in both challenges and opportunities. This book discusses both. It shows that we need to deal with these challenges at all levels of the computing stack: from algorithms all the way to process technology. We discuss the topic of heterogeneous computing from different angles: hardware challenges, current hardware state-of-the-art, software issues, how to make the best use of the current heterogeneous systems, and what lies ahead. The aim of this book is to introduce the big picture of heterogeneous computing. Whether you are a hardware designer or a software developer, you need to know how the pieces of the puzzle fit together. The main goal is to bring researchers and engineers to the forefront of the research frontier in the new era that started a few years ago and is expected to continue for decades. We believe that academics, researchers, practitioners, and students will benefit from this book and will be prepared to tackle the big wave of heterogeneous computing that is here to stay.

The first course in software engineering is the most critical. Education must start from an understanding of the heart of software development, from familiar ground that is common to all software development endeavors. This book is an in-depth introduction to software engineering that uses a systematic, universal kernel to teach the essential elements of all software engineering methods. This kernel, Essence, is a vocabulary for defining methods and practices. Essence was envisioned and originally created by Ivar Jacobson and his colleagues, developed by Software Engineering Method and Theory (SEMAT) and approved by The Object Management Group (OMG) as a standard in 2014. Essence is a practice-independent framework for thinking and reasoning about the practices we have and the practices we need. Essence establishes a shared and standard understanding of what is at the heart of software development. Essence is agnostic to any particular method, lifecycle independent, programming language independent, concise, scalable, extensible, and formally specified. Essence frees the practices from their method prisons. The first part of the book describes Essence, the essential elements to work with, the essential things to do and the essential competencies you need when developing software. The other three parts describe more and more advanced use cases of Essence. Using real but manageable examples, it covers the fundamentals of Essence and the innovative use of serious games to support software engineering. It also explains how current practices such as user stories, use cases, Scrum, and micro-services can be described using Essence, and illustrates how their activities can be represented using the Essence notions of cards and checklists. The fourth part of the book offers a vision how Essence can be scaled to support large, complex systems engineering. Essence is supported by an ecosystem developed and maintained by a community of experienced people worldwide. From this ecosystem, professors and students can select what they need and create their own way of working, thus learning how to create ONE way of working that matches the particular situation and needs.

As the digital economy changes the rules of the game for enterprises, the role of software and IT architects is also transforming. Rather than focus on technical decisions alone, architects and senior technologists need to combine organizational and technical knowledge to effect change in their company's structure and processes. To accomplish that, they need to connect the IT engine room to the penthouse, where the business strategy is defined. In this guide, author Gregor Hohpe shares real-world advice and hard-learned lessons from actual IT transformations. His anecdotes help architects, senior developers, and other IT professionals prepare for a more complex but rewarding role in the enterprise. This book is ideal for: Software architects and senior developers looking to shape the company's technology direction or assist in an organizational transformation Enterprise architects and senior technologists searching for practical advice on how to navigate technical and organizational topics CTOs and senior technical architects who are devising an IT strategy that impacts the way the organization works IT managers who want to learn what's worked and what hasn't in large-scale transformation

The increasing penetration of IT in organizations calls for an integrative perspective on enterprises and their supporting information systems. MERODE offers an intuitive and practical approach to enterprise modelling and using these models as core for building enterprise information systems. From a business analyst perspective, benefits of the approach are its simplicity and the possibility to evaluate the consequences of modeling choices through fast prototyping, without requiring any technical experience. The focus on domain modelling ensures the development of a common language for talking about essential business concepts and of a shared understanding of business rules. On the construction side, experienced benefits of the approach are a clear separation between specification and implementation, more generic and future-proof systems, and an improved insight in the cost of changes. A first distinguishing feature is the method's grounding in process algebra provides clear criteria and practical support for model quality. Second, the use of the concept of business events provides a deep integration between structural and behavioral aspects. The clear and intuitive semantics easily extend to application integration (COTS software and Web Services). Students and practitioners are the book's main target audience, as both groups will benefit from its practical advice on how to create complete models which combine structural and behavioral views of a system-to-be and which can readily be transformed into code, and on how to evaluate the quality of those models. In addition, researchers in the area of conceptual or enterprise modelling will find a concise overview of the main findings related to the MERODE project. The work is complemented by a wealth of extra material on the author's web page at KU Leuven, including a free CASE tool with code generator, a collection of cases with solutions, and a set of domain modelling patterns that have been developed on the basis of the method's use in industry and government.

An effective systems development and design process is far easier to explain than it is to implement. A framework is needed that organizes the life cycle activities that form the process. This framework is Configuration Management (CM). Software Configuration Management discusses the framework from a standards viewpoint, using the original DoD MIL-STD-973 and EIA-649 standards to describe the elements of configuration management within a software engineering perspective. Divided into two parts, the first section is composed of 14 chapters that explain every facet of configuration management related to software engineering. The second section consists of 25 appendices that contain many valuable real world CM templates. The content is extensive and inclusive, covering everything from CM planning to configuration identification, verification, and auditing. Although it is vendor-neutral, it offers a serious discussion of what to look for in a CM tool and lists toolsets for review. This volume is a sourcebook of techniques, templates, and best practices in the field, providing software engineers and systems developers with what they need to run a successful CM program.

To really benefit from the reliability and scalability you get with cloud platforms, your applications need to be designed for that environment. Cloud Native Spring in Action is a practical guide for planning, designing, and building your first cloud native apps using the powerful, industry-standard Spring framework Cloud Native Spring in Action teaches you effective Spring and Kubernetes cloud development techniques that you can immediately apply to enterprise-grade applications. As you develop an online bookshop, you'll learn how to build and test a cloud native app with Spring, containerize it with Docker, and deploy it to the public cloud with Kubernetes. Including coverage of security, continuous delivery, and configuration, this hands-on guide is the perfect primer for navigating the increasingly complex cloud landscape. About the Technology Modern applications need scalability, resilience, reliability, and zero-downtime. For most large systems, that means you'll take advantage of cloud-based tools and services. For Java developers, Spring helps effortlessly build cloud native, production-ready applications. Combined with Kubernetes, the Spring ecosystem offers numerous built-in features to help out developers migrating or building new cloud native projects efficiently.

Martin Fowler's guide to reworking bad code into well-structured code Refactoring improves the design of existing code and enhances software maintainability, as well as making existing code easier to understand. Original Agile Manifesto signer and software development thought leader, Martin Fowler, provides a catalog of refactorings that explains why you should refactor; how to recognize code that needs refactoring; and how to actually do it successfully, no matter what language you use. Refactoring principles: understand the process and general principles of refactoring Code smells: recognize "bad smells" in code that signal opportunities to refactor Application improvement: quickly apply useful refactorings to make a program easier to comprehend and change Building tests: writing good tests increases a programmer's effectiveness Moving features: an important part of refactoring is moving elements between contexts Data structures: a collection of refactorings to organize data, an important role in programs Conditional Logic: use refactorings to make conditional sections easier to understand APIs: modules and their functions are the building blocks of our software, and APIs are the joints that we use to plug them together Inheritance: it is both very useful and easy to misuse, and it's often hard to see the misuse until it's in the rear-view mirror---refactorings can fix the misuse Examples are written in JavaScript, but you shouldn't find it difficult to adapt the refactorings to whatever language you are currently using as they look mostly the same in different languages. "Whenever you read [Refactoring], it's time to read it again. And if you haven't read it yet, please do before writing another line of code." -David Heinemeier Hansson, Creator of Ruby on Rails, Founder & CTO at Basecamp "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." -M. Fowler (1999)

In today's unforgiving business environment where customers demand zero defect software at lower costs-it is testing that provides the opportunity for software companies to separate themselves from the competition. Providing a fresh perspective on this increasingly important function, Software Testing as a Service explains, in simple language, how to use software testing to improve productivity, reduce time to market, and reduce costly errors. The book explains how the normal functions of manufacturing can be applied to commoditize the software testing service to achieve consistent quality across all software projects. This up-to-date reference reviews different software testing tools, techniques, and practices and provides succinct guidance on how to estimate costs, allocate resources, and make competitive bids. Replete with examples and case histories, this book shows software development managers, software testers, testing managers, and entrepreneurs how proper planning can lead to the creation of software that proves itself to be head and shoulders above the competition.

Whether you are inheriting a test team or starting one up, Manage Software Testing is a must-have resource that covers all aspects of test management. It guides you through the business and organizational issues that you are confronted with on a daily basis, explaining what you need to focus on strategically, tactically, and operationally. Using a risk-based approach, the author addresses a range of questions about software product development. The book covers unit, system, and non-functional tests and includes examples on how to estimate the number of bugs expected to be found, the time required for testing, and the date when a release is ready. It weighs the cost of finding bugs against the risks of missing release dates or letting bugs appear in the final released product. It is imperative to determine if bugs do exist and then be able to metric how quickly they can be identified, the cost they incur, and how many remain in the product when it is released. With this book, test managers can effectively and accurately establish these parameters.