1 / 32

Distributed Software evelopment

Distributed Software evelopment. Adrien Olivier(AO) Dominik Rojković (DR) Hassan Aziz Khan(HSK) Petar Butković (PB) Petar Dučić (PD) Rashid Khan(RK) Seyed Morteza Hosseini (SMH). Link Analysis Tool. Alpha Prototype. Content. Project Schedule Current State Important Events

tamra
Download Presentation

Distributed Software evelopment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Distributed Software evelopment AdrienOlivier(AO) DominikRojković(DR) Hassan Aziz Khan(HSK) PetarButković(PB)PetarDučić(PD)Rashid Khan(RK)SeyedMortezaHosseini(SMH)

  2. Link Analysis Tool Alpha Prototype

  3. Content • Project Schedule • Current State • Important Events • Process Info • Experience • Prototype Demo

  4. Current State Timeliness

  5. Current Project Cost

  6. Results Last Week • Analyzing database-adapt to the hibernate mapping • Change to JDBC instead of Hibernate • Implementing methods to access to the database • Establishing SSH tunnel on MAC • Refining the requirements • Re-shaping the design • Creating the UML diagrams • Studying Java Server Faces and AJAX • Creating web pages for authentication and main page, Creating client side of web application

  7. Creating security for JavaBeans classes • Integration of connection graph with web application • Working on server side of web application • Making the initial web pages in HTML and CSS • Studying JSON • Finalizing work on initial version of connection Graph • Configuring and running Tomcat • Troubleshooting of access to the PostgreSQL

  8. Activities Planned for Next Period • Continuing implement database interface needs • Refine the Requirements • Enhance the design • Modify the Requirements specification document • Improving domain layer • Work on the matrix • Studying how to make zoomed-out graph • Update coding policy • Insert more data in DB tables

  9. Working Hours

  10. Project Cost

  11. Important Events • Meeting with customer • Arrange communication’s channels. • Familiarizing with project details. • Geting details about connection diagram, activity matrix, database tables and list of main options. • Geting data for DB, details for preparing tables and tips for optimizing tables for searching. • General meetings • Local meetings • Leaders meetings

  12. Used policies • General policies • Collaboration policy • Naming policy • Week report policy • Coding policy

  13. Changes in design decisions • Abandon the use of PHP. • Decided to develop only in Java server side language. • Using JDBC instead of Hibernate

  14. Development Process’ Definitions

  15. Requirements Description 1.Graphically(transactions between subscribers) 2.Search depth 3.Time period(user defined) 4.Types of transactions(in different colors) 5.Zoomed out graph(whole network) 6.Activity matrix(summarize transactions) 7.Clickable and zoomable main graph. 8.Selectable cells. 9.Selected cell’s transactions(highlighted in main graph)

  16. Specific requirements Interface 1.Main content. 2.Control panel on right side. 3.A small zoomed out graph. 4.Activity matrix at the bottom of the screen.

  17. Assumptions and constraints • Technological • HTML, CSS (web pages) • JSF (client authentication and DB connection) • JavaScript(Graphs) • AJAX(asynchronous communication SQL DB queries) • Environmental • Apache(Tomcat),PostgreSQL(database) • Server running application are Linux based

  18. Time schedule

  19. Experiences • Help on Skype. • Lot of work that isn't visible. • Not enough time for everything. • Hard to organize work when people do not keep the schedule. • Many interesting meetings and people.

  20. Work distribution • AO- Interfaces for DB • HAK-Documentaion • RK-Activitiy mat + HTML • DR-Organization + Visualization • MHS-Presentation + SVN • PB-MVC + JSF + system maintenance • PD-Interface design + servlets

  21. Problems

  22. Use Case Diagram

  23. Software architecture Client Server Architecture

  24. System architecture in general General System Architecture

  25. Detailed software design Class Diagram

  26. General Sequence Diagram

  27. Database Tables • RTX • The RTX table contains call detail records • RTX_TYPES • The table defines different types of transactions found in table RTX (column RTX_TYPE) • RTX_USAGE_TYPES • The table defines different usage types of transactions found in table RTX (column NR). • LEAP_CUSTOMERS • This table contains subscriber details)

More Related