atom02:Computer science a stoiculescu
| (2 intermediate revisions by one user not shown) | |||
| Line 9: | Line 9: | ||
The main topics for the online interface were discussed: | The main topics for the online interface were discussed: | ||
| − | 1. Database integration with an existing web framework (e.g. [http://www.php.net/ PHP], [http://en.wikipedia.org/wiki/Java_Platform,_Enterprise_Edition J2EE]). | + | 1. '''Database integration''' with an existing web framework (e.g. [http://www.php.net/ PHP], [http://en.wikipedia.org/wiki/Java_Platform,_Enterprise_Edition J2EE]). |
| − | 2. User profile creation & security mechanism. | + | 2. '''User profile creation & security mechanism.''' |
| − | 3. Web pages development: | + | 3. '''Web pages development:''' |
Standard web activity or [http://en.wikipedia.org/wiki/Create,_read,_update_and_delete CRUD] create, read, update, delete and send activities to controllers on the site. | Standard web activity or [http://en.wikipedia.org/wiki/Create,_read,_update_and_delete CRUD] create, read, update, delete and send activities to controllers on the site. | ||
| − | Non-standard web activity : navigate on the map to find an empty place. One of the many problems that can appear is when two or more users click on the same place on the map. | + | Non-standard web activity : navigate on the map to find an empty place. One of the many problems that can appear is when two or more users click at the same time on the same place on the map. The interface has to quickly solve the problem and inform the users. |
| + | 4. '''Payment application:''' on a separate server & bank connection. | ||
| − | + | 5. '''Testing.''' | |
| − | + | ||
| − | 5. Testing. | + | |
'''Total work time to implement for an experienced developer is roughly 3 months of 8 hours per day.''' | '''Total work time to implement for an experienced developer is roughly 3 months of 8 hours per day.''' | ||
| Line 29: | Line 28: | ||
'''Conclusions:''' | '''Conclusions:''' | ||
| − | It is the expert's recommendation that the interface can be simulated with a simple [http://en.wikipedia.org/wiki/Queue_%28data_structure%29 queue]. This queue will hold the user-requests for now and will drive the structure controllers on the site. His opinion is that the complexity of the interface itself might prove to be problematic for an inexperienced software developer and ultimately take a lot of time to implement. The option of leaving open the | + | It is the expert's recommendation that the interface can be simulated with a simple [http://en.wikipedia.org/wiki/Queue_%28data_structure%29 queue]. This queue will hold the user-requests for now and will drive the structure controllers on the site. His opinion is that the complexity of the interface itself might prove to be problematic for an inexperienced software developer and ultimately take a lot of time to implement. The option of leaving open the online interface and developing it post-architecture has been discussed. |
Latest revision as of 09:27, 17 October 2011
About:
Andrei Stoiculescu has graduated Computer Science at the Universitatea Politehnica Bucharest. He has since worked for Intrasoft International developing Web Applications for the European Union agency responsible for registering trade marks and designs. Andrei has also worked for Testing Technologies and has done an internship at the Fraunhofer FOKUS Institute. He is a currently enrolled in the Master in Artificial Intelligence at the Rijksuniversiteit Groningen.
First meeting:
The main topics for the online interface were discussed:
1. Database integration with an existing web framework (e.g. PHP, J2EE).
2. User profile creation & security mechanism.
3. Web pages development:
Standard web activity or CRUD create, read, update, delete and send activities to controllers on the site.
Non-standard web activity : navigate on the map to find an empty place. One of the many problems that can appear is when two or more users click at the same time on the same place on the map. The interface has to quickly solve the problem and inform the users.
4. Payment application: on a separate server & bank connection.
5. Testing.
Total work time to implement for an experienced developer is roughly 3 months of 8 hours per day.
Conclusions:
It is the expert's recommendation that the interface can be simulated with a simple queue. This queue will hold the user-requests for now and will drive the structure controllers on the site. His opinion is that the complexity of the interface itself might prove to be problematic for an inexperienced software developer and ultimately take a lot of time to implement. The option of leaving open the online interface and developing it post-architecture has been discussed.
