90 likes | 251 Views
iTeams Fall 2006: Morpheus Project . Timothy B. Jones 8/28/2006. Overview. Overview Assumptions Diligence List Potential Deliverables Go/No Go Items. Overview. Morpheus is an Eclipse-based browser tool for data transformation and conversion. Key features include:
E N D
iTeams Fall 2006:Morpheus Project Timothy B. Jones 8/28/2006
Overview • Overview • Assumptions • Diligence List • Potential Deliverables • Go/No Go Items
Overview • Morpheus is an Eclipse-based browser tool for data transformation and conversion. Key features include: • Integration with the PostGres database • Transforms occur inside the DBMS, thus faster and creating potential for some sort of knowledge base
Assumptions to Validate • Funding by Microsoft • Issue: Who owns the IP? • Assumption: MIT owns IP • Patent potential • Issue: Public Disclosure at SIGMOD • Assumption: Technology is still patentable • MIT – UF collaboration • Issue: Is UF licensing office involved • Assumption: This is MIT only, and group can move forward independent of UF
Architectural Diagram Q: Is this best suited for enterprise SW or Internet deployment?
Diligence List • IP status – What is ability to patent? • Public Disclosure first made when? What about July 2006 presentation at Sigmod • UML Model • Code Base/Examples • Demonstration of prototype • Scalability test • Dependent technology • Eclipse, PostGres,? • Requirements/Specifications Doc
Market Assessment • Assumption 1: ETL (Extract, Transform, Load) Mkt as initial foray • What is the size of this mkt? <$1B • Who are market leaders • Ascential/IBM, SAS, Informatica, Oracle, • Assumption 2: This is something else, plays into another market • Open Source DBMS? (Enterprise DB, MySQL0 • Q: is there a bigger mkt somewhere else? • Enterprise Web 2.0 • Financial Services Technology • ?
Potential Team Deliverables • Beta test/Pilot Program • CIO Questionnaire/Survey • Business Model • Competitive Analysis • Market Demand Analysis • Demonstration • Services Model • Detailed Deployment design • Vertical Market Solution(s) design
Potential No/No Go points • Who is the entrepreneur? • Is this a UF or MIT project? • Is this a product or a technology enabled service? • Does this scale? Or, does this require expensive enterprise sw installation? • Is the development team going to leave to do a startup?