There are plenty of books that show you how to write applications in a specific language. They explain the nuts and bolts of the syntax and the use of the tools to build applications with the latest features and functionality available. There are also a number of fine books that show you how to be "a computer consultant." But there are a whole host of issues specific to the business of writing, delivering and supporting custom software systems. This is the only book that will take you on a step-by-step tour of the entire process. "DevGuide 3", with over 150 pages of new material, shows you how to do "The Other 90%" of the work involved in producing custom software applications.
The Information System Consultant's Handbook familiarizes systems analysts, systems designers, and information systems consultants with underlying principles, specific documentation, and methodologies. Corresponding to the primary stages in the systems development life cycle, the book divides into eight sections: Principles Information Gathering and Problem Definition Project Planning and Project Management Systems Analysis Identifying Alternatives Component Design Testing and Implementation Operation and Maintenance Eighty-two chapters comprise the book, and each chapter covers a single tool, technique, set of principles, or methodology. The clear, concise narrative, supplemented with numerous illustrations and diagrams, makes the material accessible for readers - effectively outlining new and unfamiliar analysis and design topics.
A benchmark text on software development and quantitative softwareengineering "We all trust software. All too frequently, this trust ismisplaced. Larry Bernstein has created and applied quantitativetechniques to develop trustworthy software systems. He and C. M.Yuhas have organized this quantitative experience into a book ofgreat value to make software trustworthy for all of us." -Barry Boehm Trustworthy Systems Through Quantitative Software Engineeringproposes a novel, reliability-driven software engineering approach,and discusses human factors in software engineering and how theseaffect team dynamics. This practical approach gives softwareengineering students and professionals a solid foundation inproblem analysis, allowing them to meet customers' changing needsby tailoring their projects to meet specific challenges, andcomplete projects on schedule and within budget. Specifically, it helps developers identify customer requirements,develop software designs, manage a software development team, andevaluate software products to customer specifications. Studentslearn "magic numbers of software engineering," rules of thumb thatshow how to simplify architecture, design, andimplementation. Case histories and exercises clearly present successful softwareengineers' experiences and illustrate potential problems, results,and trade-offs. Also featuring an accompanying Web site withadditional and related material, Trustworthy Systems ThroughQuantitative Software Engineering is a hands-on, project-orientedresource for upper-level software and computer science students,engineers, professional developers, managers, and professionalsinvolved in software engineering projects. An Instructor's Manual presenting detailed solutions to all theproblems in the book is available from the Wiley editorialdepartment. An Instructor Support FTP site is also available.
Corporate and commercial software-development teams all want solutions for one important problem—how to get their high-pressure development schedules under control. In RAPID DEVELOPMENT, author Steve McConnell addresses that concern head-on with overall strategies, specific best practices, and valuable tips that help shrink and control development schedules and keep projects moving. Inside, you’ll find: A rapid-development strategy that can be applied to any project and the best practices to make that strategy work Candid discussions of great and not-so-great rapid-development practices—estimation, prototyping, forced overtime, motivation, teamwork, rapid-development languages, risk management, and many others A list of classic mistakes to avoid for rapid-development projects, including creeping requirements, shortchanged quality, and silver-bullet syndrome Case studies that vividly illustrate what can go wrong, what can go right, and how to tell which direction your project is going RAPID DEVELOPMENT is the real-world guide to more efficient applications development.
Nursing Informatics and the Foundation of Knowledge, Fourth Edition teaches nursing students the history of healthcare informatics, current issues, basic informatics concepts, and health information management applications. This comprehensive text includes the building blocks of informatics through complicated topics such as data mining, bioinformatics, and system development.
Introduction to Programming with Visual Basic .NET introduces the major concepts and applications of this important language within the context of sound programming principles, in a manner that is accessible to students and beginning programmers. Coverage includes the new visual objects required in creating a Windows-based graphical user interface, event-based programming, and the integration of traditional procedural programming techniques with VB .NET's object-oriented framework. The text places a strong emphasis on real-world business applications, case studies, and rapid application development to help engage students with discussion of practical programming issues. A full range of supplements for students and instructors accompany the text.
Information Systems: An Experiential Approach is a brief,inexpensive, paperback alternative for professors who want anexperiential approach for the undergraduate or first year graduatelevel Intro to IS course. Offering a learner-centeredapproach and using a learn-do-reflect model,Bélanger/Van Slyke provides a focused treatment of topics andengaging activities. The authors have used this model in theirclasses to great success. The authors found that students performedbetter on exams, class discussions became more animated andattendance improved as engagement with the material increased.
This volume shows how all the techniques and products of a computer development project can be brought together within a complete method - SSADM. The individual products and techniques of SSADM are demonstrated. Information is given on managing SSADM projects, how to customise the method, and it provides a structural model and a product breakdown structure both of which can be used as the basis for planning a computer project.