Form-Based Requirement Definitions of Applications for a Sustainable Society
It is expected that information technology (IT) will contribute to resource saving and environmental preservation for a sustainable society. For this purpose, application software is required and then the fund is needed for its development by IT professionals. However, the preparation of the fund must be difficult. The end-user initiative development of application software is indispensable for the solution of this dilemma. This paper describes requirement definitions based on abstract forms in a method that business professionals build applications by themselves. The abstract forms are considered as interfaces of Web services based on the simple concept that “one service = one form.” Therefore, the business logic can be defined as the form transformation from input forms into outputs form by business professionals.
KeywordsEUC Form-to-form transformation Visual tool Web service integration
- 1.The Apache Software Foundation, Struts, http://struts.apache.org/.
- 3.Brown A.W. (Ed.) (1996). Component-based software engineering. Los Alamitos, CA: IEEE Computer Science Press.Google Scholar
- 4.Chusho, T., Ishigure, H., Konda, N., & Iwata, T. (2000). Component-based application development on architecture of a model, UI and components. Proceedings of the APSEC2000, pp. 349–353. IEEE Computer Society.Google Scholar
- 5.Chusho, T., Tsukui, H., & Fujiwara, K. (2004). A Form-base and UI-driven approach for enduser-initiative development of web applications. Proceedings of the Applied Computing 2004, pp. II/11–II/16. IADIS.Google Scholar
- 6.Chusho, T., Yuasa, R., Nishida, S., & Fujiwara, K. (2007). Web service integration based on abstract forms in xml for end-user initiative development. Proceedings of the 2007 IAENG International Conference on Internet Computing and Web Services (ICICWS’07), pp. 950–957. Hong Kong.Google Scholar
- 10.Fayad, M., & Schmidt, D.C. (Ed.) (1997). Object-oriented application frameworks. Communications of the ACM, 39(10), 32–87.Google Scholar
- 11.Hirooka, N. (2005). Nagasaki prefecture (in Japanese). Nikkei Computer, No.2007.7.25.Google Scholar
- 12.Jacobson, J., et al. (1999). The unified software development process. Reading, MA: Addison-Wesley.Google Scholar
- 14.Larman, C. (2002). Introduction to object-oriented analysis and design and the unified process. Prentice-Hall, USA.Google Scholar
- 16.Lieberman, H. (Ed.) (2000). Special issue on Programming by example. Communications of the ACM, 43(3), 72–114.Google Scholar
- 17.Margaria, T. (Ed.) (2007). Guest editors’ introduction:service is in the eyes of the beholder. IEEE Computer, 40(11), 33–37.Google Scholar
- 18.Nano, O., & Zisman, A. (Ed.) (2007). Guest editors’ introduction: realizing service-centric software systems. IEEE Software, 24(6), 28–30.Google Scholar
- 19.OMG, OMG Model Driven Architecture, http://www.omg.org/mda/.
- 20.OMG, Unified Modeling Language, http://www.uml.org/.
- 22.Sutcliffe, A., & Mehandjiev, N. (Guest Ed.) (2004). End-user development. Communications of the ACM, 47(9), 31–32.Google Scholar