One semester, Jr/Sr/Grad course in systems analysis and design, or capstone course in MIS departments where students work on a project or extensive case. McLeod and Jordan's text is ideal for courses where student teams develop and implement software systems in real organizations, or where students develop software to solve problems in written cases. The text is organized into nine chapters and eight supporting technical modules: the chapters provide a unique, thorough coverage of the entire system development life cycle (SDLC), and a strong foundation in systems concepts and systems methodologies, while the technical modules provide the tools students need to implement and apply the concepts. The goal of the text is to provide a strong foundation of the concepts, with emphasis on the later phases of actual implementation and design, providing the methodologies and tools necessary to complete a systems project in a real organization, including installation of operational software. It has been successfully class-tested by over 400 students.

Information systems (IS) are the backbone of any organization today, supporting all major business processes. This book deals with the question: how do these systems come into existence? It gives a comprehensive coverage of managerial, methodological and technological aspects including: Management decisions before and during IS development, acquisition and implementation Project management Requirements engineering and design using UML Implementation, testing and customization Software architecture and platforms Tool support (CASE tools, IDEs, collaboration tools) The book takes into account that for most organizations today, inhouse development is only one of several options to obtain an IS. A good deal of IS development has moved to software vendors – be it domestic, offshore or multinational software firms. Since an increasing share of this work is done in Asia, Eastern Europe, Latin America and Africa, the making of information systems is discussed within a global context.

This book shows the reader how to write a system engineering management plan (SEMP) that reflects the company's identity and is appropriate to most customers' requirements, e.g., MIL-STD-499, ISO 9001, the U.S. Air Force Integrated Management System, and EIA STD 632. The first section of this book provides a brief introduction to the process of developing a SEMP. The remainder contains a source model of a SEMP that is generic in nature. A computer disk is included with the book to provide the SEMP in a form (Microsoft Word) that can be used for the reader's own plan.

Very few software projects are completed on time, on budget, and to their original specification causing the global IT software industry to lose billions each year in project overruns and reworking software. Research supports that projects usually fail because of management mistakes rather than technical mistakes. Risk Management in Software Development Projects focuses on what the practitioner needs to know about risk in the pursuit of delivering software projects. Risk Management in Software Development Projects will help all practicing IT Project Managers and IT Managers understand: * Key components of the risk management process * Current processes and best practices for software risk identification * Techniques of risk analysis * Risk Planning * Management processes and be able to develop the process for various organizations

- support an adaptive culture or mindset, in which change and uncertainty are assumed to be the natural state--not a false expectation of order- introduce frameworks to guide the iterative process of managing change- institute collaboration, the interaction of people on three levels: interpersonal, cultural, and structural- add rigor and discipline to the RAD approach, making it scalable to the uncertainty and complexity of real-life undertakings