비즈니스 프로세스 서술 도구의 성능 비교 연구
Comparing Tools for Business Process Description
0
조회
0
다운로드
0
인용
0
참고문헌
키워드
초록
정보시스템의 발전과 함께 현실업무가 더욱 복잡해지면서, 정보시스템 개발 초기단계에서 사용자의 요구사항이 누락되거나 중복되는 경우가 자주 발생하고, 차후에 이를 수정하기 위한 노력이 증대되면서, 전체개발비용과 기간이 증가하게 된다. 이 문제를 해결하기 위해서 업무 프로세스를 표현하기 위한 다양한 방법론이 제안되어왔지만, 각 방법론의 우열을 어떻게 가릴지에 대한 체계적인 항목별 연구는 이제까지 없었다. 이 연구에서는 사용자가 직관적으로 이해할 수 있고, 분석가가 업무 프로세스를 충분히 표현할 수 있으며 동시에 시스템구축 비용을 최소화할 수 있는 방법론이 가장 이상적이라는 점을 고려해서, 누락도, 중복도, 명확도, 표현력 등의 방법론 평가기준을 제안하며, 이 지표를 은행의 자산건전성 평가업무라는 표준 업무에 적용해서 각 방법론의 우위내지는 문제점들을 살펴본다. 프로세스 중심 기법인 자료흐름도와 유즈케이스 다이어그램과 비교할 때, 데이터 중심 기법인 개체관계도가 상대적으로 낮은 함축성과 높은 복잡성에도 불구하고 낮은 누락도와 명확한 표현력을 가지고 있으며, 업무기술서와 병행될 때 프로세스 함축과 누락에 대한 부담을 크게 감소시킬 수 있을 것으로 나타난다.
Abstract
In developing information systems, frequent omissions and redundancies of user requirements lead to increasing total cost should such fallacies be corrected later. Thus business requirements may better be formalized consistently in order to shorten development cycles as well as to control overall costs. To cope with this problem, various methods for describing business processes have been proposed in the past. Yet there has been no general agreement as to which model works better over which. This research approaches the problem by defining quality dimensions measuring effectiveness of individual methods and provides a general framework for analyzing and appraising competitive methodologies by specifically focusing on Entity-Relationship Diagram, Data Flow Diagram, and Use Case Diagram. Empirically speaking, Entity-Relationship Diagram outclasses the other two in simplicity, correctness, and expression power, possibly reflecting its dominance over other tools. We find that, despite that its lower readability, its high expression power and convenience quite surpasses its drawbacks. Additionally, it also makes sense to adequately use well-formed job descriptions to enjoy considerable synergy with Entity-Relationship Diagram for successful information systems developments.
참고문헌 (24)
- 문송천, "데이터 아키텍춰" (2004), 형설출판사
- 유치수, "소프트웨어 공학" (1998), 홍릉과학출판사
- Benediktsson, Oddur, "COCOMO-Based Effort Estimation for Iterative and Incremental Software Development", Software Quality Control, 11(4), pp.265~281 (2003)
- Berente, Nicholas, "Iteration in Systems Analysis and Design: Cognitive Processes and Representational Artifacts", working paper, Case Western Reserve University, ~ (2005)
- Booch, Grady, "Object-Oriented Development", IEEE Transaction on Software Engineering, 12(2), pp.211~221 (1986)
- Brinkkemper, Sjaak, "Method Engineering: Engineering of Information Systems Development Methods and Tools", Journal of Information and Software Technology, 38, pp.275~280 (1996)
- Chen, Pin-Shan Peter, "The Entity-Relationship Model: Toward a Unified View of Data", ACM Transactions on Database Systems, 1(1), pp.9~36 (1976)
- Cherf, G. S., "An Investigation of The Maintenance and Support Characteristics of Commercial Software", Software Quality Journal, 1(3), pp.147~158 (1992)
- Emam, Khaled El, "A Field Study of Requirements Engineering Practices in Information Systems Development", the 2nd IEEE International Symposium on Requirements Engineering, pp.68~80 (1995), IEEE Computer Society
- Forrester, J. Wright, "Industrial Dynamics" (1961), MIT Press
- Giaglis, George M., "A Taxonomy of Business Process Modeling and Information Systems Modeling Techniques", International Journal of Flexible Manufacturing Systems, 13(2), pp.209~228 (2001)
- Glass, L. Robert, "Software Runaways: Monumental Software Disasters" (1997), Prentice-Hall
- Godwin, Anthony N., "An Assessment of The IDEF Notations as Descriptive Tools", Information Systems, 14(1), pp.13~28 (1989)
- Huckvale, Tim, "Process Modeling: Who, What and How: Role Activity Diagramming, in Business Process Change: Concepts, Methods, and Technologies, Grover, V. and W. J. Kettinger (Eds.)", pp.330~349 (1995), Idea Group Publishing
- Hull, Elizabeth, "Requirements Engineering" (2002), Springer
- Kettinger, William J., "Business Process Change: A Study of Methodologies, Techniques, and Tools", MIS Quarterly, 21(1), pp.55~80 (1997)
- Mayer, Richard J., "A Framework and a Suite of Methods for Business Process Reengineering, in Business Process Change: Concepts, Methods, and Technologies" (1995)
- Pressman, S. Roger, "Software Engineering: A Practitioner's Approach" (2004), McGraw-Hill
- Schriber, Thomas J., "Fundamentals of Flowcharting" (1969), Wiley
- UML, "UML Proposal to the Object Management Group", http:, www.rational.com, pp.uml, 1997[DOI]
- Valacich, Joseph S., "Essentials of System Analysis and Design" (2005), Prentice-Hall
- Weber, Ron, "Conceptual Modeling and Ontology: Possibilities and Pitfalls", Journal of Database Management, 14(3), pp.1~20 (2003)
- Wolstenholme, Eric F., "The Evaluation of Management Information Systems: A Dynamic and Holistic Approach" (1993), John Wiley & Sons
- Yourdon, Edward N., "Modern Structured Analysis. Englewood Cliffs" (1989), Prentice-Hall International