270 likes | 396 Vues
The ColdWatch project successfully concluded on January 10, 2012, showcasing an extensive overview of system architecture, statistics, and team experiences. Key milestones including Alpha, Beta, and final version deliverables were met on schedule, despite some project requirements being adjusted in agreement with the customer. The project highlighted the challenges faced during web-interface development and communications, with an impressive count of over 900 emails and 16 group meetings. Essential lessons learned emphasize the importance of thorough planning and clear specification of project requirements.
E N D
Distributed software development 2012-01-10
ColdWatch Final project presentation Angie Angarita Matija Renić 2012-01-10
Overview • Overall system • General statistics • Experiences • General project requirements • Demonstration 2012-01-10
Final state of the project Project successfully finished • Some of the project requirements were dropped in agreement with customer 2012-01-10
Overall system ETL
General statistics 2012-01-10
Workload 2012-01-10
Other statistics 360 Commits 2425 Files Analyzed 539 Files 2012-01-10
Sprint burnup chart (tasks) 2012-01-10
Timeliness • Milestones: • Alpha • Beta • Final version • Documents: • All on time: • 15 revisions (mostly requirements)
Stories stats • Started with • Added some requirements • Dropped some • Making up meaningful data • Weather forecast prediction • Backup in XML format
Communication in numbers • Exchanged over 900 e-mails all together • Chatted over 500 times all together • 16 group meetings • 7 meetings with the customer • In average each of us made 4 new friends
Work on project • Web-interface part turned out to be the tricky one • Occupied 4 team members • Developing new things was time consuming • Graphical libraries, whole reporting process • Writing documentation was sometimes exhausting
Lessons we learned • Rather spend more time on defining project than on adjustments and changes later ! • Plan ahead your schedule!
General project requirements Presumptions: • Passive heating system • Tube under ground • Ventilator • Protected facility • Sensors 2012-01-10
General project requirements 2012-01-10
Functional requirements • GSN server • Sensor readings simulation • Email & SMS notifications 2012-01-10
Functional requirements • Database • ETL process – Data archive • Data availability • Data marts • 2012-01-10
Functional requirements • WEB interface • Data presentation • User friendly • Secure login • Roles 2012-01-10
Non-functional requirements • Usability • Reliability • Performance • Scalability 2012-01-10