A Multi-level Methodology for Developing UML Sequence Diagrams
ER '08 Proceedings of the 27th International Conference on Conceptual Modeling
Parsed use case descriptions as a basis for object-oriented class model generation
Journal of Systems and Software
| Hi-index | 0.00 |
From the Book:PREFACE: PrefaceThis book presents the details of a complete software development process using the methods and tools of object technology. It is based on my work as a consultant, mentor, and instructor over the last 17 years. The process architecture is based on ideas originally presented in Radice88, and I have refined it over the years to integrate elements of Jacobson92 with my own experiences in software engineering.Readers should have a working knowledge of object-oriented concepts and terminology. For readers unfamiliar with the terminology of object technology, I suggest Firesmith95 and Taylor90 as good references. What this book is aboutI intend this book to be a tool that enhances object-oriented software development by providing a step-by-step flow for application by project teams wishing to blend software engineering principles with object-oriented methods. With that in mind, the book is organized around process work products (deliverables) that act as vehicles for refining detail from original requirements to delivered code. All defined work products are accompanied by a set of criteria, in a check-list format, that the development team can use to objectively evaluate whether the deliverable is correct for the given product requirements. Who should read this bookThe details of object-oriented software development I present are intended to help software analysts, designers, programmers, and testers develop software with rigor rather than speculation. The book is also intended to help project managers and leaders create a formal process for managing the development of the software itself. How the bookisorganizedPart I describes the object-oriented development process (OODP). Chapter 1 defines a generic process architecture and chapter 2 provides the rationale behind OODP. Chapters 3 to 12 provide the details of each step in the OODP, starting with requirements and continuing through implementation and test. Among these are chapters on class design, persistence, test planning, and user interface development. This part concludes with a discussion of the major issues that a project manager would face as he or she attempted to integrate the technologies of object orientation into the organization's software development process.Part II takes a medium-sized example and develops a complete solution with all of the deliverables of OODP. It develops the solution in four increments and reviews the steps of each activity as the deliverables are created.