Why SednaSpace?<br />By<br />D.Arockiaraj <br />CTO, SednaSpace<br />
Traditional Development<br />Gather requirements.<br />Define  architecture and design.<br />Develop the application based...
       Traditional Development  Issues<br />Any mistake made in a step is discovered in the next step only.<br />It is ver...
Enterprise Application<br />Any enterprise application has three parts.<br />User Interface(UI)(HTML, Flex, Windows Forms,...
Architecture<br />Architecture depends on how the UI, Business Logic and data are linked together.<br />
Monolithic Architecture<br />User Interface, Business logic and data are within the same executable.<br />All the three ex...
       Client/Server Architecture<br />User Interface and (business logic + data) are in separate executables.<br />	OR (U...
Web Architecture<br />User Interface, Business logic and data are in different executables.<br />User Interface is execute...
Business Perspective<br />No matter what the architecture is, the business problem is the same.<br />
What we need?<br />Software development should be based on business problem rather than on architecture and design. i.e. S...
SednaSpace<br />A tool to collect technical details about the application, independent of technology.<br />A server to exe...
       SednaSpace Solution<br />Need not gather complete requirements before starting to develop the application. Developm...
Contact SednaSpace<br />www.sednaspace.com<br />sales@sednaspace.com<br />bsoosai@sednaspace.com<br />Cell: +91 94440 6972...
Upcoming SlideShare
Loading in...5
×

Sedna space philosophy

634

Published on

why sednaspace

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
634
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Sedna space philosophy"

  1. 1. Why SednaSpace?<br />By<br />D.Arockiaraj <br />CTO, SednaSpace<br />
  2. 2. Traditional Development<br />Gather requirements.<br />Define architecture and design.<br />Develop the application based on the architecture and design<br />Test the application<br />Deploy application<br />
  3. 3. Traditional Development Issues<br />Any mistake made in a step is discovered in the next step only.<br />It is very difficult to gather requirements completely before starting the project.<br />It is difficult to check whether developers have written code adhering to the architecture and design specified.<br />The end user can visualize the application only after completing development(it could be partial).<br />Implementing changes after seeing the application is hard and painful. Sometimes we may need to work on the same screen many times.<br />Changing architecture or design half way in the project is very difficult and time consuming.<br />The documentation for the application has to be kept in synch with the application changes.<br />Migrating to another technology will be very difficult.<br />
  4. 4. Enterprise Application<br />Any enterprise application has three parts.<br />User Interface(UI)(HTML, Flex, Windows Forms, Java Swing etc)<br />Business Logic(BL)(C#, Java, PHP etc)<br />Data(Files, RDBMS etc)<br />
  5. 5. Architecture<br />Architecture depends on how the UI, Business Logic and data are linked together.<br />
  6. 6. Monolithic Architecture<br />User Interface, Business logic and data are within the same executable.<br />All the three exist in the same process.<br />E.g. Word, PowerPoint<br />
  7. 7. Client/Server Architecture<br />User Interface and (business logic + data) are in separate executables.<br /> OR (User Interface + business logic) and data are in separate executables.<br />The two executables are linked using network protocols.<br />E.g. Outlook and Exchange Server<br />
  8. 8. Web Architecture<br />User Interface, Business logic and data are in different executables.<br />User Interface is executed browser.<br />Business logic is executed by application server<br />Data is stored in RDBMS<br />
  9. 9. Business Perspective<br />No matter what the architecture is, the business problem is the same.<br />
  10. 10. What we need?<br />Software development should be based on business problem rather than on architecture and design. i.e. Software development should be independent of technology and architecture.<br />
  11. 11. SednaSpace<br />A tool to collect technical details about the application, independent of technology.<br />A server to execute the collected details.<br />The application can be executed in .net or Java environment<br />A code generator to generate code from the collected details.<br />A BPM designer to define business process.<br />A BPM engine to execute business process.<br />
  12. 12. SednaSpace Solution<br />Need not gather complete requirements before starting to develop the application. Development and requirements gathering can be done simultaneously.<br />The end user can be engaged on a daily basis. Thus the end user gives feed back right away for the developer to implement changes.<br />Technical Documentation is automatically generated , thus the documentation is in synch with the application developed.<br />Code is generated by SednaSpace as per the architecture and design specified. Thus there will be no violation of architecture or design.<br />Applying changes is easy in SednaSpace.<br />Migrating to another architecture or technology can be done with zero to less effort.<br />
  13. 13. Contact SednaSpace<br />www.sednaspace.com<br />sales@sednaspace.com<br />bsoosai@sednaspace.com<br />Cell: +91 94440 69727(Borgia Soosai)<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×