At Ortho Pharmaceutical Corporation, the Research Systems and Programming group makes use of comprehensive software engineering standards in the development of new systems. Our standards consist of a structured development life cycle, an accompanying structured documentation set, and associated control procedures. The purpose of this article is to reiterate the importance of validation throughout the software life cycle, with special emphasis on the emergence of rapid prototyping techniques for facilitating requirements definition and validation, and user acceptance testing.
KlinglerDERaskaskyKR: Software engineering standards in the pharmaceutical industry: Making the most of a regulated environment, in Proceedings of the IEEE Computer Society Computer Standards Conference—1986. Washington, DC, IEEE Computer Society Press, 1986, pp 76–80.
2.
KlinglerDE: Documentation and management of structured software development. J Inf Syst Manage1987; in press.
3.
KlinglerDE: Validation techniques for internally developed computer systems, in Proceedings of the PMA Computer Systems Validation Seminar II-1986, Washington, DC, Pharmaceutical Manufacturers Association, 1986, pp 182–195.
4.
FrantaWR: Formal Methods of Program Verification and Specification.Englewood Cliffs, NJ, Prentice-Hall, 1982.
KlinglerDEDavisGJ: Drug safety evaluation automation: A distributed system approach. Drug Inf J1986; 20(2): 199–212.
7.
KlinglerDE: A drug safety evaluation on-line study log. Drug Inf J1987; 21(2) 185–191.
8.
Good laboratory practice for nonclinical laboratory studies. Code of Federal Regulations, title 21, part 58, April 1, 1981, pp 209–223.
9.
YourdonE: What ever happened to structured analysis?Datamation1986; 32(11): 133–138.
10.
DeMarcoT: Structured Analysis and System Specification.New York, Yourdon Press, 1978.
11.
KellerR: The Practice of Structured Analysis: Exploding Myths.New York, Yourdon Press, 1983.
12.
PalmerLS: Computing in a pharmaceutical company: Hassle's unconventional approach. Drug Inf J, 1986; 20(1): 43–50.
13.
SquiresSLBranstadMZelkowitzM: Special issue on rapid prototyping: Working papers from the ACM SIGSOFT rapid prototyping workshop. ACM SIGSOFT Software Eng Notes1982; 7(5).
14.
NaumannJDJenkinsAM: Prototyping: The new paradigm for systems development. MIS Q1982; 6(3): 29–44.
15.
BlumBI: Still more about rapid prototyping. ACM SIGSOFT Software Eng Notes1983; 8(3): 9–11.
GomaaH: The impact of rapid prototyping on specifying user requirements. ACM SIGSOFT Software Eng Notes1983; 8(2): 17–28.
21.
McNurlinBC: Developing systems by prototyping. EDP Ana1981; 19(9): 1–14.
22.
NystromH: Prototyping. Interact1986; 5(2): 60–63.
23.
ConnellJLBriceL: The impact of implementing a rapid prototype on system maintenance, in Proceedings of the AFIPS National Computer Conference-1985. Reston, VA, AFIPS Press, 1985, pp 515–524.
24.
ChristoffKA: Building a fourth generation environment. Datamation1985; 31(18): 118–124.
25.
GrantFJ: The downside of 4GLs. Datamation1985; 31(14): 99–104.
26.
ZelkowitzMV: A case study in rapid prototyping. Software Pract Exp1980; 10: 1037–1042.
27.
SmithPM: A prototyping case study. J Inf Syst Manage1985; 2(3): 20–25.
28.
CareyTTMasonREA: Information system prototyping: Techniques, tools, and methodologies. Information1983; 21: 177–191.
29.
LeavittD: More than end-user tools, 4GLs add to productivity. Software News1986; 6(4): 70–77.
30.
MasonREACareyTT: Prototyping interactive information systems. Commun ACM1983; 26: 347–354.
31.
Steinbrock-HarrisonT: Techniques and issues in rapid prototyping. J Syst Manage1985; 1(3): 8–13.
