A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
Crunch mode: building effective systems on a tight schedule
Crunch mode: building effective systems on a tight schedule
Peopleware: productive projects and teams
Peopleware: productive projects and teams
SSADM, applications and context
SSADM, applications and context
Principles of software engineering management
Principles of software engineering management
Managing the software process
SSADM for the advanced practitioner
SSADM for the advanced practitioner
Rapid application development
Japanese perspectives in software engineering
Japanese perspectives in software engineering
Soft systems methodology in action
Soft systems methodology in action
Object-oriented analysis (2nd ed.)
Object-oriented analysis (2nd ed.)
Customers do not want frozen specifications
Software Engineering Journal
Case study in human factors evaluation
Information and Software Technology
Software quality and the Capability Maturity Model
Communications of the ACM
Prototyping: does your view of its advantages depend on your job?
Journal of Systems and Software
Introducing Systems Design
Software Engineering Economics
Software Engineering Economics
Measures for Excellence: Reliable Software on Time, within Budget
Measures for Excellence: Reliable Software on Time, within Budget
Practical Formal Methods with VDM
Practical Formal Methods with VDM
Controlling Software Projects: Management, Measurement, and Estimates
Controlling Software Projects: Management, Measurement, and Estimates
| Hi-index | 0.00 |
This paper examines the efficiency and effectiveness of a prescriptive systems development methodology in practice. The UK Government's mandatory Structured Systems Analysis and Design Method (SSADM) was examined to determine its value to software projects. The evidence was collected from interviews with 17 project managers, discussions with participants on 3 large SSADM projects and from observing 90 end users in training. The conclusions are that prescriptive information systems methodologies are unlikely to cope well with strategic uncertainty, user communication or staff development. The recommendations are to focus more on soft organizational issues and to use approaches tailored to each project.