Breakdowns and processes during the early activities of software design by professionals
Empirical studies of programmers: second workshop
Knowledge exploited by experts during software system design
International Journal of Man-Machine Studies - What programmers know
Case: Using Software Development Tools
Case: Using Software Development Tools
The high-tech toolbelt: a study of designers in the workplace
CHI '95 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
The Role of Opportunism in the Software Design Reuse Process
IEEE Transactions on Software Engineering
Extending Design Environments to Software Architecture Design
Automated Software Engineering
User interfaces for authoring systems with object stores
COMPCON '96 Proceedings of the 41st IEEE International Computer Conference
Managing views in a program understanding tool
CASCON '93 Proceedings of the 1993 conference of the Centre for Advanced Studies on Collaborative research: software engineering - Volume 1
Supporting the cognitive process of user interface design with reusable design cases
International Journal of Human-Computer Studies
A cognitive modeling of the user's exploratory behavior with prior knowledge
TAMODIA '05 Proceedings of the 4th international workshop on Task models and diagrams
| Hi-index | 0.00 |
Key findings from empirical studies—early design is opportunistic; critical role of pictures in design conception; impact of various cognitive limitations—have very effectively determined requirements and design for a set of tools to support early design. Key design features of the tools include respectively: (1) The (simultaneous) display of any software modules at arbitrary levels of abstraction and from any subsystems. The unrestricted, smooth navigation between these software modules. (2) Multiple design notations—pictorial and symbolic— cross-referenced, editable, and maintained consistent across all views. Integrated views of control flow, data flow, and functional decomposition. (3) Automatic layout at arbitrary levels of nesting. Visual display of execution paths in the solution. Automatic completeness and consistency check. Automatic visual indication and listing of modules with constraint violations.