Topic
Design process
About: Design process is a research topic. Over the lifetime, 11302 publications have been published within this topic receiving 140717 citations.
Papers published on a yearly basis
Papers
More filters
Book•
01 Jan 1999
TL;DR: This book provides a comprehensive guide to The Objectory Software Development Process derived from the three market leading OOA&D methods: Booch, OOSE (Use-Case), and OMT.
Abstract: The three amigos of software development come together again to bring you an introduction to a new standard for creating today's software that will definitely be useful for any developer or manager familiar with UML. This book provides a comprehensive guide to The Objectory Software Development Process derived from the three market leading OOA&D methods: Booch, OOSE (Use-Case), and OMT. Overviews of the four basic principles of the Unified Process are complemented by excellent use case examples that are drawn from such areas as banking and inventory control.
3,486 citations
Book•
01 Jan 1998
TL;DR: This chapter discusses the Rational Unified Process, a method for Modeling the Software Development Business using Software Engineering Techniques for Business Modeling, and its applications, from the Business Models to the Systems.
Abstract: (NOTE: Each chapter concludes with a summary.) Preface. I. THE PROCESS. 1. Software Development Best Practices. The Value of Software. Symptoms and Root Causes of Software Development Problems. Software Best Practices. Develop Software Iteratively. Manage Requirements. Use Component-Based Architectures. Visually Model Software. Continuously Verify Software Quality. Control Changes to Software. The Rational Unified Process. 2. The Rational Unified Process. What Is the Rational Unified Process? The Rational Unified Process as a Product. Software Best Practices in the Rational Unified Process. Other Key Features of the Rational Unified Process. A Brief History of the Rational Unified Process. 3. Static Structure: Process Description. A Model of the Rational Unified Process. Roles. Activities. Artifacts. Disciplines. Workflows. Additional Process Elements. A Process Framework. 4. Dynamic Structure: Iterative Development. The Sequential Process. Overcoming Difficulties: Iterate! Gaining Control: Phases and Milestones. A Shifting Focus across the Cycle. Phases Revisited. Benefits of an Iterative Approach. 5. An Architecture-Centric Process. The Importance of Models. Architecture. The Importance of Architecture. A Definition of Architecture. Architecture Representation. An Architecture-Centric Process. The Purpose of Architecture. Component-Based Development. Other Architectural Concepts. 6. A Use-Case-Driven Process. Definitions. Identifying Use Cases. Evolving Use Cases. Organizing Use Cases. Use Cases in the Process. II. PROCESS DISCIPLINES. 7. The Project Management Discipline. Purpose. Planning an Iterative Project. The Concept of Risk. The Concept of Measurement. Roles and Artifacts. Workflow. Building an Iteration Plan. 8. The Business Modeling Discipline. Purpose. Why Business Modeling? Using Software Engineering Techniques for Business Modeling. Business Modeling Scenarios. Roles and Artifacts. Workflow. From the Business Models to the Systems. Modeling the Software Development Business. Tool Support. 9. The Requirements Discipline. Purpose. What Is a Requirement? Types of Requirements. Capturing and Managing Requirements. Requirements Workflow. Roles in Requirements. Artifacts Used in Requirements. Tool Support. 10. The Analysis and Design Discipline. Purpose. Analysis versus Design. How Far Must Design Go? Roles and Artifacts. Designing a User-Centered Interface. The Design Model. The Analysis Model. The Role of Interfaces. Artifacts for Real-Time Systems. Component-Based Design. Workflow. Tool Support. 11. The Implementation Discipline. Purpose. Builds. Integration. Prototypes. Roles and Artifacts. Workflow. Tool Support. 12. The Test Discipline. Purpose. Testing in the Iterative Lifecycle. Dimensions of Testing. Roles and Artifacts. Workflow. Tool Support. 13. The Configuration and Change Management Discipline. Purpose. The CCM Cube. Roles and Artifacts. Workflow. Tool Support. 14. The Environment Discipline. Purpose. Process Engineering Process. Roles and Artifacts. Workflow. Tool Support. 15. The Deployment Discipline. Purpose. Roles and Artifacts. Workflow. 16. Typical Iteration Plans. Defining the Product Vision and the Business Case. Building an Architectural Prototype. Implementing the System. 17. Implementing the Rational Unified Process. Introduction. The Effect of Implementing a Process. Implementing the Rational Unified Process Step by Step. Implementing a Process Is a Project. Appendix A: Summary of Roles. Appendix B: Summary of Artifacts. Appendix C: Acronyms. Glossary. Bibliography. Index. 0321197704T11172003
2,231 citations
TL;DR: From the protocol data, aspects of creativity in design related to the formulation of the design problem and to the concept of originality are identified and a model of creative design as the co-evolution of problem/solution spaces is applied, confirming the general validity of the model.
1,956 citations
Book•
01 Feb 1988
TL;DR: In this paper, the authors present a strategy for process synthesis and analysis and propose a conceptual design and finding the best flow-sheet for a solvent recovery system. But, they do not discuss how to find the best flowsheet.
Abstract: Part I A Strategy For Process Synthesis and Analysis1 The Nature of Process Synthesis and Analysis2 Engineering Economics3 Economic Decision Making-Design of a Solvent Recovery SystemPart II Developing A Conceptual Design and Finding the Best Flowsheet4 Input Information and Batch vs Continuous5 Input-Output Structure of the Flowsheet6 Recycle Structure of the Flowsheet7 Separation System8 Heat-Exchanger Networks9 Cost Diagrams and the Quick Screening of Process AlternativesPart III Other Design Tools And Applications10 Preliminary Process Optimization11 Process Retrofits12 Computer-Aided Design Programs13 Summary of the Conceptual Design Procedure and Extensions of the MethodAppendixes
1,489 citations
TL;DR: In this article, a knowledge representation schema for design called design prototypes is presented, which supports the initiation and continuation of the act of designing and provides a suitable framework to distinguish routine, innovative, and creative design.
Abstract: This article begins with an elaboration of models of design as a process. It then introduces and describes a knowledge representation schema for design called design prototypes. This schema supports the initiation and continuation of the act of designing. Design prototypes are shown to provide a suitable framework to distinguish routine, innovative, and creative design.
1,410 citations