By admin on October 9, 2011
pScan home page new design - IE8
pScan home page mockup - IE8
pScan edit criteria dialog new design - IE8
pScan edit criteria dialog mockup - IE8
Jassim, thanks 
Posted in pScan | Tagged Design
By admin on September 27, 2011
Parallel processing can be implemented using the following Java API/library
Factorial is a study of performance characteristics of various methods to do parallel processing in Java. In this study, we calculate factorial of a non-negative integer in parallel. Stay tuned
Posted in Factorial
By admin on September 26, 2011
List of questions/issues related to pScan architecture
- Q : How to have a distributed system and still keep data feed cost to mininum?
A : Use OpenDDS Data Distribution Service to distribute data in FAST protocol
POC : 100 hours(first C++, OMG DDS and FAST project)
- Q : How does front-end receive filtering results without continuous polling?
A : Use CometD to send events/filtering results to browsers
POC : 30 hours
- Q : Can CometD Java server be a client of DDS C++ server?
A : No answer yet. Finding the answer may take 5 hours.
POC : 40 hours
Besides questions/issues related to pScan architecture, we still have the task to evaluate Java application servers(5 hours).
Since pScan design may take two weeks(September 26 to October 9 2011), we can do the following tasks in this period assuming 10 working hours per week:
- Can CometD Java server be a client of DDS C++ server?(5 hours)
- Java application server evaluation(5 hours)
- Learn selected Java application server(10 hours)
Posted in pScan | Tagged Architecture
By admin on September 26, 2011
- pScan architecture. Some questions are answered. However none is proven using proof of concept.
- pScan designer selection. A designer is selected on September 21, 2011.
- Learn JBoss Application Server 7. Decision to use JBoss is doubted due to documentation issue and memory usage. A simple study of JBoss AS using existing research results will be carried out.
What went well during the sprint?
- We realise we need an end-to-end architecture for pScan.
What could be improved in the next sprint?
- Expectation/Estimation. Assigning 5 hours for architecture analysis and design is misleading since we are new to low latency and highly scalable system. This is a timely reminder since we have been successful in previous sprints.
- Adherence to Scrum methodology. Architecture analysis and design should be done in sprint zero as discussed in SG Spring 2008 Open Space. However as described in pScan roadmap, front-end is developed first for quick ROI.
Posted in pScan | Tagged Scrum
By admin on September 4, 2011
1. After a bit of progress on pScan user interface, it is time to define general architecture of pScan from front-end to back-end – 5 hours
Minimum requirements for pScan architecture:
- No proprietary software as there is no budget allocated .
- Able to support filtering of one US market for one criterion for 15-minute stock quotes using a server with Intel chip G6950 (2 x 2.8GHz) and 1G RAM.
- Front-end receives filtering results without continuous polling.
- Back-end must able to utilize multi-core server and cold standby server.
2. pScan designer selection – 2 hours
3. Learn JBoss Application Server 7 – 3 hours
Start date – September 5, 2011
End date – September 11, 2011 (based 10-hour work week)
Note : Why one-week sprint? pScan project has reached a point where the general architecture has to be known first before going further. The architecture is required for future sprint/task planning. From this sprint, you may suspect some conclusions have been made from preliminary research, e.g. no proprietary software(free software is available to handle minimum requirements), using JBoss AS(JBoss AS is likely able to support to-be-determined pScan architecture).
Posted in pScan | Tagged Scrum
