The Role of Domain Expenence in Software Design
IEEE Transactions on Software Engineering - Special issue on artificial intelligence and software engineering
Comparison of analysis techniques for information requirement determination
Communications of the ACM
Breakdowns and processes during the early activities of software design by professionals
Empirical studies of programmers: second workshop
Modern structured analysis
Object-oriented analysis (2nd ed.)
Object-oriented analysis (2nd ed.)
Toward a taxonomy of software application domains: history
Journal of Systems and Software
Requirements specification: learning object, process, and data methodologies
Communications of the ACM
The sciences of the artificial (3rd ed.)
The sciences of the artificial (3rd ed.)
Information Engineering: Introduction
Information Engineering: Introduction
Application Development without Programmers
Application Development without Programmers
Software Engineering Economics
Software Engineering Economics
Systems Analysis and Design Methods
Systems Analysis and Design Methods
Information Systems Methodologies; A Framework for Understanding, 2nd Ed.
Information Systems Methodologies; A Framework for Understanding, 2nd Ed.
Structured Systems Analysis: Tools and Techniques
Structured Systems Analysis: Tools and Techniques
Human Problem Solving
Structured Analysis and System Specification
Structured Analysis and System Specification
Empirical Software Engineering
Understanding Conceptual Schemas: Exploring the Role of Application and IS Domain Knowledge
Information Systems Research
Crafting Rules: Context-Reflective Data Quality Problem Solving
Journal of Management Information Systems
Stopping Behavior of Systems Analysts During Information Requirements Elicitation
Journal of Management Information Systems
Expertise Integration and Creativity in Information Systems Development
Journal of Management Information Systems
Information and Management
Understanding user behavior with new mobile applications
The Journal of Strategic Information Systems
An analytical model for requirements activities and software product quality
Journal of Computational Methods in Sciences and Engineering - Selected papers from the International Conference on Computer Science, Software Engineering, Information Technology, e-Business, and Applications, 2004
Quantitative assessment of enterprise resource planning software customisation
International Journal of Information Systems and Change Management
Proceedings of the 49th SIGMIS annual conference on Computer personnel research
Technology Acceptance and Performance: An Investigation into Requisite Knowledge
Information Resources Management Journal
A User-Oriented Model of Factors that Affect Information Requirements Determination Process Quality
Information Resources Management Journal
Simplifying process model abstraction: Techniques for generating model names
Information Systems
Hi-index | 0.00 |
The systems development process involves establishing the information requirements of an application and successively transforming those requirements into a computer-based model of the application. Attention iS usually focused almost exclusively on the method of transformation, however, with little recognition of the role of the application. As a first step in examining the relevance of knowledge of the application to the systems development process, this study addresses whether there are synergistic effects of application and methodology knowledge in specifying information requirements. This was achieved via a repeated-measures protocol analysis study that manipulated both experience with the application and knowledge of the methodology. The results show that in learning to specify information requirements, novice analysts: • performed more effectively over time when trained to use a methodology applied the methodology more effectively when familiar with the application; • performed more effectively when they used procedural methodology knowledge rather than declarative methodology knowledge alone; • improved the effectiveness of their problem solving over time only when they used procedural methodology knowledge; • produced idiosyncratic results based on the application. Based on the findings of this research, it appears that research into the nature of applications, as well as methodologies, is warranted. From the viewpoint of the practitioner, since application knowledge is idiosyncratic, it may be necessary to include more than one application-knowledgable person on a systems development team.