This book addresses how best to make build vs. buy decisions, and what effect such decisions have on the software development life cycle (SDLC). Offering an integrated approach that includes important management and decision practices, the text explains how to create successful solutions that fit user and customer needs, by mixing different SDLC methodologies. Features: provides concrete examples and effective case studies; focuses on the skills and insights that distinguish successful software implementations; covers management issues as well as technical considerations, including how to deal with political and cultural realities in organizations; identifies many new alternatives for how to manage and model a system using sophisticated analysis tools and advanced management practices; emphasizes how and when professionals can best apply these tools and practices, and what benefits can be derived from their application; discusses searching for vendor solutions, and vendor contract considerations.

This book presents a guide to navigating the complicated issues of quality and process improvement in enterprise software implementation, and the effect these have on the software development life cycle (SDLC). Offering an integrated approach that includes important management and decision practices, the text explains how to create successful automated solutions that fit user and customer needs, by mixing different SDLC methodologies. With an emphasis on the realities of practice, the book offers essential advice on defining business requirements, and managing change. This revised and expanded second edition includes new content on such areas as cybersecurity, big data, and digital transformation. Features: presents examples, case studies, and chapter-ending problems and exercises; concentrates on the skills needed to distinguish successful software implementations; considers the political and cultural realities in organizations; suggests many alternatives for how to manage and model a system.

Focusing on a wide variety of technologies, this book shows readers how to identify, choose, and integrate state-of-the-art software for customized business applications; offers real-world examples and case studies of successfully integrated systems from Fortune 500 companies; and includes special quick-access charts on software currently available.

This book argues that the key problems of software systems development (SSD) are socio-technical rather than purely technical in nature. Software systems are unique. They are the only human artefacts that are both intangible and determinant. This presents unprecedented problems for the development process both in determining what is required and how it is developed. Primarily this is a problem of communications between stakeholders and developers, and of communications within the development team. Current solutions are not only inadequate in expressing the technical problem, they also evade the communications problems almost entirely. Whilst the book addresses the theoretical aspects of the process, its fundamental philosophy is anchored in the practical problems of everyday software development. It therefore offers both a better understanding of the problems of SSD and practical suggestions of how to deal with those problems. It is intended as a guide for practising IT project managers, particularly those who are relatively new to the position or do not have a strong IT development background. The book will also benefit students in computing and computer-related disciplines who need to know how to develop high quality systems. Software systems development (particularly of large projects) has a notoriously poor track record of delivering projects on time, on budget, and of meeting user needs. Proponents of software engineering suggest that this is because too few project managers actually comply with the disciplines demanded of the process. It is time to ask the question, if this is the case, why might this be? Perhaps instead, it is not the project managers who are wrong, but the definition of the process. The new understanding of the SSD presented here offers alternative models that can help project managers address the difficulties they face and better achieve the targets they are set. This book argues that time is up for the software engineering paradigm of SSD and that it should be replaced with a socio-technical paradigm based on open systems thinking.

This book covers the fundamentals of structured development from requirements through to implementation and is aimed at anyone who has to carry out or understand development. This highly practical book explains how to implement structured development, rather than explaining what it is. The book treats the techniques of structured development as practical tools, rather than thoretical ideas.

This book is perhaps the first attempt to give full treatment to the topic of Software Design. It will facilitate the academia as well as the industry. This book covers all the topics of software design including the ancillary ones.

This book provides a step by step guide to all the processes, goals, inputs, outputs and many other aspects of a repeatable software methodology for ANY project. From “soup to nuts” … the whole shebang ~! All in one place at an incredible price…. over 130 pages of knowledge. Any information technology organization must have a highly structured framework into which it can place processes, principles, and guidelines. The framework used for software development is a called a lifecycle. The software development lifecycle (SDLC) defines a repeatable process for building information system that incorporate guidelines, methodologies, and standards. A lifecycle delivers value to an organization by addressing specific business needs within the software application development environment. The implementation of a lifecycle aids project managers in minimizing system development risks, eliminating redundancy, and increasing efficiencies. It also encourages reuse, redesign, and, more importantly, reducing costs.

In the Guide to the Software Engineering Body of Knowledge (SWEBOK(R) Guide), the IEEE Computer Society establishes a baseline for the body of knowledge for the field of software engineering, and the work supports the Society's responsibility to promote the advancement of both theory and practice in this field. It should be noted that the Guide does not purport to define the body of knowledge but rather to serve as a compendium and guide to the knowledge that has been developing and evolving over the past four decades. Now in Version 3.0, the Guide's 15 knowledge areas summarize generally accepted topics and list references for detailed information. The editors for Version 3.0 of the SWEBOK(R) Guide are Pierre Bourque (Ecole de technologie superieure (ETS), Universite du Quebec) and Richard E. (Dick) Fairley (Software and Systems Engineering Associates (S2EA)).

This classroom-tested textbook presents an active-learning approach to the foundational concepts of software design. These concepts are then applied to a case study, and reinforced through practice exercises, with the option to follow either a structured design or object-oriented design paradigm. The text applies an incremental and iterative software development approach, emphasizing the use of design characteristics and modeling techniques as a way to represent higher levels of design abstraction, and promoting the model-view-controller (MVC) architecture. Topics and features: provides a case study to illustrate the various concepts discussed throughout the book, offering an in-depth look at the pros and cons of different software designs; includes discussion questions and hands-on exercises that extend the case study and apply the concepts to other problem domains; presents a review of program design fundamentals to reinforce understanding of the basic concepts; focuses on a bottom-up approach to describing software design concepts; introduces the characteristics of a good software design, emphasizing the model-view-controller as an underlying architectural principle; describes software design from both object-oriented and structured perspectives; examines additional topics on human-computer interaction design, quality assurance, secure design, design patterns, and persistent data storage design; discusses design concepts that may be applied to many types of software development projects; suggests a template for a software design document, and offers ideas for further learning. Students of computer science and software engineering will find this textbook to be indispensable for advanced undergraduate courses on programming and software design. Prior background knowledge and experience of programming is required, but familiarity in software design is not assumed.

The purpose of this book is to provide a detailed understanding of the evolutionary approach to the development of computerized information systems. It does this by describing the principles of evolutionary development and showing how they relate to the more traditional approaches to systems analysis and design.