Co-developing Model for User Participation in Web Application Development

Transcription

1 Co-developing Model for User Participation in Web Application Development Tae Yoneda, Kouhei Mitsui, Jun Sasaki, Yutaka Funyu Iwate Prefectural University, Japan

2 Contents 2 Background and Object of our research Co-developing Model Logic to realize the Co-developing Prototype System of Co-developing Environment Conclusion

3 Background [1] Failure of the software development projects 3 Failed 18% Succeeded 29% Challenged 53% The CHAOS Report (Standish group, 2004) Project Challenged Factors Top3 1. Lack of User Input 2. Incomplete Requirements 3. Changing Requirements How to get and reflect the user requirements precisely and flexibly are important issue.

4 Object of our research 4 To propose a new software development framework to realize that user requirements can be gotten and reflected precisely and flexibly. Scale of System: Small and medium-sized scale system

5 5 Scale of System: Information systems have increasingly been introduced in a variety of fields. From large size system of big company to small size system nearing our life Iwate Prefecture needs to promote agriculture and fishery to promote social services to develop small businesses etc. Example) safety confirming system

6 Object of our research 6 To consider and propose a new software development methodology to realize that user requirements can be gotten and reflected precisely and flexibly. System Size: Small and medium-sized scale system System Type: a web application is developed by using web application User: who will use a developed system who has the basic handling skills to use a computer who has not the skills to develop a web application

7 Developing Style of our target 7 User Oriented End User Computing Engineer Oriented System Engineer Developing (Traditional Style)

8 End User Computing 8 Input Push User Development Environment - Cyber Framework developed by Cyber Laboratory Inc. - HIMEKAMI: an End-user System Development Environment Based on Lyee Theory, K. Mitsui et al., Proc. of SoMeT04 It is still difficult to realize the style and apply it widely in practice.

9 Developing Style of our target 9 User Oriented End User Computing (Studying, Difficult to realize) On-site Customer Style in XP (Practical New Style) Engineer Oriented System Engineer Developing (Traditional Style)

10 On-site Customer Style on XP 10 User Input Push System Engineers Development Environment - The user requirements can be comparatively more satisfied. - A user doesn't develop the system subjectively. Difficult to develop a system that flexibly reflects the user requirements Funyu Lab.

11 Developing Style of our target 11 User Oriented End User Computing (Studying, Difficult to realize) User and System Engineer Co-developing Our target On-site Customer Style in XP (Practical New Style) Engineer Oriented System Engineer Developing (Traditional Style)

12 User and System Engineer Co-developing 12 User Input Push System Engineer System Development Environment - User can participate to system development positively. - System Engineer support to develop the system.

13 Co-development Model

14 Co-development Model 14 For user, requirements can be described easily. The developing system can be confirmed by executing. Modifying the developing system can be easily. User Input Push System Engineer Co-development Environment User requirements can be understood easily and in detail. User requirements can be coded easily.

15 Co-development Flow [1] 15 Requirements can be described by natural language. User User System requirements Engineer can be understood.

16 Co-development Flow [2] 16 The developing system can be confirmed by executing. Push User Input System User requirements Engineer can be coded part by part.

17 Co-development Flow [3] 17 Modifying the developing system by natural languge. Push User Input System Engineer User requirements can be understood.

18 18 Co-development Flow [4] The developing system can be confirmed by executing. Push Input User User requirements for modifying are coded. System Engineer Funyu Lab.

19 Logic to realize the co-developing Web application by LAMP

20 point of view 20 Screen Screen Transition User Screen name Pre-screen name Post-screen name SE Screen composition (natural language) (program code) Condition, Transaction (natural language) (program code)

21 Actions in a web application 21 Step 1) decisions in respect of the screen displayed (screen transition) Step 2) display of the screen (screen display)

22 Operation Model 22 (b) Evaluation and Transaction Web Application <Screen Transition> (a) Selection request User <Screen Display> (c) (e) Data Extraction Screen Output output (d) Data Synthesis

23 23 Co-development procedures Step3) Definitions of screen transitions Step4) Whole Control Evaluation and Transaction Selection User Step1) Step4) Library Data Extraction Screen Output Step2) Definitions of screens Step2) Data Synthesis System Engineer

24 Prototype System of Co-developing Environment

25 25

26 26 Input a system name

27 27

28 28

29 User describe a screen by using natural language. 29

30 30

31 User describe a screen transition by using natural language. 31

32 Engineer code for each part described by user. 32

33 33

34 34

35 Conclusion [1] 35 Described the Co-developing Model and showed the prototype system of Co-developing environment User oriented development model There is a generator to generate program. The developing system can be confirmed by executing. Suit for Agile development User requirements can be gotten and reflected precisely and flexibly.

36 Conclution [2] 36 Considerations; There is not enough support to create dynamic pages in the web application. There is not enough support to set up a database. Future works; To evaluate this model; thus, it will be necessary to apply it to real user system developments. A visual interface for the user will be required. The creation of a mechanism to reuse the defined and programmed components.

37 37 Thank you