LAT_Present_AlphaPrototype_V0.3 [1.54 MiB]

Download Report

Transcript LAT_Present_AlphaPrototype_V0.3 [1.54 MiB]

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)
2016-05-24
1
Alpha Prototype
2016-05-24
2
Content
•
•
•
•
•
•
Project Schedule
Current State
Important Events
Process Info
Experience
Prototype Demo
2016-05-24
3
Current State
Timeliness
General Project
Status
on track
2016-05-24
Fulfillment of Next
Milestone
on track
4
Current Project Cost
Current Planned Cost
Current Actual Cost
Planned Project Cost
Forecasted Project Cost
2016-05-24
$9.180
$9.015
$26.040
$25.875
5
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
2016-05-24
6
• 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
2016-05-24
7
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
2016-05-24
8
Working Hours
Member
Adrien
Dominik
Hassan
Morteza
Petar B
Petar D.
Rashid K.
Total
2016-05-24
W39
9
9
9
9
9
9
9
63
W40 W41 W42 W43
2
18
18 14
37
16
20 24
14
11
20:30
6
9
20
39
6
11 13
23
4
15 18:45 15:30
13
75 89:45 58:30
Total
29
94
78
35:30
83
60
71:15
164
450:45
9
Project Cost
Week 40 Week 41 Week 42 Week 43
Current
Planned
Cost
$2.400
$4.380
$6.720
$9.180
Current
Actual Cost
$2.760
$4.555
$5.365
$9.015
Planned
Project Cost
$26.040
$26.040
$26.040
$26.04
Forecasted
Project Cost
$26.400
$26.215
$24.685
$25.875
2016-05-24
10
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
2016-05-24
11
Changes in requirements
• Abandon the use of PHP.
• Decided to develop only in Java server side
language.
• Using JDBC instead of Hibernate
2016-05-24
12
Development Process’ Definitions
Keyword
Definitions
Visualize
Graphically represent the calls or data
Transactions transfer between different users.
Search
Depth
Activity
Matrix
2016-05-24
No of hops from a certain user or
Subscriber
A table representing certain
transactions over a period of Time
13
Used policies
•
•
•
•
•
General policies
Collaboration policy
Naming policy
Week report policy
Coding policy
2016-05-24
14
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)
2016-05-24
15
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.
2016-05-24
16
2016-05-24
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
2016-05-24
18
Time schedule
Finished week
Id
M001
M002
M003
M004
M005
M006
M007
M008
M009
M010
M011
Milestone Description
Project vision
Project plan
Requirements Definition
Design Description
Prototyping–Iteration1
Milestone - Alpha prototype
Prototyping–Iteration2
Milestone - Beta prototype
Implementation
Milestone – Release candidate
Testing
Final Project Report,final
M012 version existing documents,other
project-related documentation
M013 Final product
2016-05-24
Responsible
ept./Initials Plan Forecast Actual Metr. Rem.
Week +/39 0
40 0
40 0
41 0
44
44
47
47
51
51
01
DR, HAK
DR
HAK
RK, DR
RK, PD
RK, PD
AO
AO
DR, RK, AO
DR, RK, AO
MHS
39
40
40
41
44
44
47
47
51
51
01
HAK
03
03
RK, PD, DR,
AO
03
03
39
40
40
41
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.
2016-05-24
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
2016-05-24
21
Problems
Week 40
Multiple roles
Lack of time
Communication,
Understanding role
Technologies integration problems
Week 42
Lack of time
Can’t access to main site
2016-05-24
Week 41
Architecture
People’s time and
appointments.
Didn’t send week report.
Week 43
Incomplete database.
JSON data format.
Don’t respect deadlines
Organization of work
Lack of time
Lack of knowledge
Lot of coding problems
22
Use Case Diagram
2016-05-24
23
Software architecture
Client Server Architecture
2016-05-24
24
System architecture in general
General System Architecture
2016-05-24
25
Detailed software design
Class Diagram
2016-05-24
26
General Sequence Diagram
2016-05-24
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)
2016-05-24
28
External interfaces
2016-05-24
29
Demo
• Show demo…
2016-05-24
30