skip to main content
10.1145/257683.257714acmconferencesArticle/Chapter ViewAbstractPublication PagesadaConference Proceedingsconference-collections
Article
Free Access

Information systems modeling: an object oriented development method

Published:16 July 1992Publication History
First page image

References

  1. Basili, V.R., &. Perricone, B.T. (1984). Software errors and complexity: An empirical investigation. Communications of the ACM, 2_27: 42.52. Google ScholarGoogle ScholarDigital LibraryDigital Library
  2. Batoson, A.G., Alexander, R.A., & Murphy, M.D. (1987). Cognitive proc=ssing differences between novice and expert programmers. Inter.nati0. nal Journal of ~Man:: Machine Studies, 26: 649-660, Google ScholarGoogle ScholarDigital LibraryDigital Library
  3. Belady, L.A., & Evang~listi, C.J. (1981). System partitioning and its measure. Journal Qf System.s and Software, 2: 23-39.Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. Bitman, W.R. (1990). Functional lists: Object-oriented design classes for MiS applications. Proceedings of the Washin~on Ads Symposium, 7: 101.122. Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. Bitman, W.R. (1991). Complexity metrics as feedback mechanism for object oriented software engineering. Abstracts of the International Conference on Industrial and Annlied Mathematics: 22.Google ScholarGoogle Scholar
  6. Card, D.N., Church, V.E., & Agresti, W.W. (1'986). An empirical study of software design practices. IEEE Transactions on Software Emzin.eerin$, 12: 264-271. Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. Card, D.N., & Glass, R.L. (1990). Measurine Software Design Ouality. Englewood Cliffs: Prentice Hall. Google ScholarGoogle ScholarDigital LibraryDigital Library
  8. Corbin, D.S. (1988, May). Strategic IRM plan: User involvement spells success. J of Systems M_m-nt: 12.16. Google ScholarGoogle ScholarDigital LibraryDigital Library
  9. Doll, W.J,, & Torkzadeh, G. (1988). The measurement of end-user computing satisfaction.MIS Ouarterlv, 1.22: 259-274. Google ScholarGoogle ScholarDigital LibraryDigital Library
  10. Er, M.C. (1986). Classic tools of systems analysis- why they have failed. Data Prqqes.sin. g, 28: 512-513. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. Favaro, J. (1991, Spring). What price reusability? A case study. Ads Letters, 1.3.1: 115-124. Google ScholarGoogle ScholarDigital LibraryDigital Library
  12. Grady, R.B. (1990, March). Work-product analysis: The philosopher's stone of software? IEEE Software:26-34. Google ScholarGoogle ScholarDigital LibraryDigital Library
  13. Green, R. (1990, June 25). Ada system helps Army Reserve assign recruits. Govt Computer News: 53.Google ScholarGoogle Scholar
  14. Henry, S., Kafura, D., & Harris, K. (1981, Spring). On the relationship among three metrics. Perfbrmance Evaluation Review: 81-88. Google ScholarGoogle ScholarDigital LibraryDigital Library
  15. Henry, S., & Selig, C. (1990, March). Predicting source code complexity at the design stage. IEEE Software: 36-44. Google ScholarGoogle ScholarDigital LibraryDigital Library
  16. Kafura, D., & Reddy G.R. (1987). The use of software complexity metrics in software maintenance. IEEE Trans. on SWE, 13: 335-343. Google ScholarGoogle ScholarDigital LibraryDigital Library
  17. Lind, R.K. & Vairavan, K. (1989). An experimental investigation of software metrics and their relationship to software development effort. IEEE Trans.on SWE, _t~.: 649-653. Google ScholarGoogle ScholarDigital LibraryDigital Library
  18. McCab~, T.J. (1976). A complexity measure. IEEE Tran~ on SWE, 2: 308-320.Google ScholarGoogle Scholar
  19. McCabe, Tj., & Butler, C.W. (1989). Design complexity measurement and testing. C~, 32: 1415-1425. Google ScholarGoogle ScholarDigital LibraryDigital Library
  20. McKeithen, K.B., Reitman, J'.S., Ruetter, H.I-i, & I-tittle, S.C. (1981). Knowledge organization and skill difference in computer programmers. Co ffnitiye psychology, 13: 307-325.Google ScholarGoogle Scholar
  21. Myers, G.J. (1975). Reliable Software Through Composite ~. NY: Petrocetli/Charter. Google ScholarGoogle ScholarDigital LibraryDigital Library
  22. Parnas, D.L. (1972). A technique for software module specification with examples. A_Q6._QM, 15: 300-306. Google ScholarGoogle ScholarDigital LibraryDigital Library
  23. Parnas, D.L., Clements, P.C., & Weiss, D.M. (1985). The modular structure of complex systems. IEEE Trans. on SWE, 11: 259-266.Google ScholarGoogle ScholarDigital LibraryDigital Library
  24. Prieto-Diaz, R. (1991, May). Implementing faceted classification for software reuse. ~: 89-97. Google ScholarGoogle ScholarDigital LibraryDigital Library
  25. Rombach, H.D. (1990, March). Design Measurement: Some lessons learned. IEEE Software: 17-25. Google ScholarGoogle ScholarDigital LibraryDigital Library
  26. Selby, R.W., & Basili, V.R. (1991).Analyzingerror-prone system structure. IEEE Trans. on SWE, 17: 141-152. Google ScholarGoogle ScholarDigital LibraryDigital Library
  27. Shen, V., Yu, T., Thebaut, S., & Paulsen, L. (1985).Identifying error prone software - An empirical study. IEEE Trans, on SWE, 11: 317-324. Google ScholarGoogle ScholarDigital LibraryDigital Library
  28. Tracz, W. (1990, Sep/Oct). Modularization: Approaches to reuse in Ada. J of Pascal. Ada& Module-2: 11-25. Google ScholarGoogle ScholarDigital LibraryDigital Library
  29. Vitalari, N.P., & Dickson, G.W. (1983). Problem solving for effective systems analysis: An experimental exploration. CACM, 26: 9,*8.955. Google ScholarGoogle ScholarDigital LibraryDigital Library
  30. Walbert, T. (1989, Sept. 8). New software eases Reserve guidance counselor's job. Recruiter Journal: 8.Google ScholarGoogle Scholar
  31. Ward, W.T. (1989, April). Software defect prevention using McCabe's complexity metric. Hewlett-Packard Journal: 64-69.Google ScholarGoogle Scholar
  32. Woodfield, S.N. (1979). An experiment on unit increase in problem complexity, iEEE T.on SWE, 5_: 76-79.Google ScholarGoogle Scholar

Recommendations

Comments

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Sign in
  • Published in

    cover image ACM Conferences
    WADAS '92: Proceedings of the ninth Washington Ada symposium on Ada: Empowering software users and developers
    July 1992
    194 pages
    ISBN:0897914872
    DOI:10.1145/257683

    Copyright © 1992 ACM

    Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

    Publisher

    Association for Computing Machinery

    New York, NY, United States

    Publication History

    • Published: 16 July 1992

    Permissions

    Request permissions about this article.

    Request Permissions

    Check for updates

    Qualifiers

    • Article
  • Article Metrics

    • Downloads (Last 12 months)8
    • Downloads (Last 6 weeks)1

    Other Metrics

PDF Format

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader