1. Shared Multimedia Network for Picture Frames

2. Members Bob Carroll Network Domain Expert IP Development Nick Gorevski Webmaster Bluetooth Development Ngai Lok Team Leader Bluetooth Development Johnny Thompson Team Scribe & Document Development IP Development

3. Massively Important People Kodak Research and Development David Cok Elena Fedorovskaya Dana Wolcott Faculty Coach Professor Lei Wu Lei Wu

4. Agenda Background Requirements Deliverables Milestones Process Risks Metrics Technical Information Architecture Status

5. Background Number of Multimedia Devices on the Market Picture Cell Phones Digital Cameras Picture Frames Laptops / PCs PDAs Storage and Capabilities have increased dramatically There is a need to transfer media between devices Easy (Novice users with little technological experience) Seamless (As little user involvement as possible)

6. Requirements Support different devices Native device – Device that contains our communication platform Foreign device – Device that does not contain our communication platform Translation to allow communication between different protocols Protocols IP/Ethernet Bluetooth: Microsoft and Widcomm Stack Discover devices in the sharing neighborhood Transfer Media Files Between Devices Network Should support authentication of devices User name and password CANNOT be used (violates seamless requirement) Network must be informed of any device that comes within range of another device

7. Deliverables Customer Required Set of Use Cases Communication Platform (Design) API (Set of libraries) Demonstrations of 2+ Use Cases

8. Winter Milestone Schedule 1 st Milestone (January 8, 2008) Project Plan 2 nd Milestone (January 22, 2008) Software Requirements Specification Detailed Use Cases Technology Prototypes 3 rd Milestone (February 5, 2008) System Architecture Document Rough Class Diagram 4 th Milestone (February 19, 2008) Communication Platform Prototype Midterm Presentation to RIT

9. Spring Milestone Schedule 5 th Milestone (March 25, 2008) Core functionality of communication platform 6 th Milestone (March 31, 2008) Testing of communication platform 7 th Milestone (April 14, 2008) Two functional demos for communication platform 8 th Milestone (April 28, 2008) System usage / User tutorial and documentation 9 th Milestone (May 13, 2008) Presentation poster Final Presentation to RIT Hand over system and documentation to Kodak

10. Personal Software Process More planned than agile Most of information needed for process is required by SE Department anyway Team Effort Reports Key to this process is postmortems Analysis after each implementation Find what we did wrong Discuss ways to improve

11. Risks Lack of Domain Knowledge Poor Estimation of Schedule Lack or Failure of open source libraries Changing Implementation Strategies As more is learned about the domain Use Cases are Overlooked Requirements are Overlooked

12. Metrics Estimated Time vs Actual Time Schedule Slippage Priority of Tasks based on Risks Project Progress Function Points per Milestone Development Defects

13. Technical Information Microsoft Visual Studio 2005.NET Framework C# and/or C++ Tortoise SVN Trac

14. Architecture: Communication

15. Architecture: Authentication

16. Current Status Complete (Possibility for Future Revisions) Project Plan Project Schedule Software Requirements Specification System Architecture Document Project Website Completing by End of Quarter Beginning of Communication Protocol Functionality

17. Future Steps Completion of Communication Protocol Translation Authentication Distributed file system Development of 2 or more Use Cases User Tutorial Documentation

18. Positives during this project Interesting project Media sharing Research & development New technologies Gadgets!

19. Negatives during this project Unexpected limitation to protocols and libraries Schedule Slippage due to lack of domain knowledge Over optimistic schedule Time

20. Questions?