Releases: MusesProject/Muses
Final Prototype # 1 RC6
Release Notes MUSES
Copyright (C) 2013 - 2014 Sweden Connectivity
Date: 20141006
Release: Muses Prototype # 1 RC6 (FINAL)
Binaries
Muses Client
Git: d1b3f20cd3650714026a9a2ad178aaf8a11dcc81
File: MusesClient.apk
MusesAwareApp
Git: 5b52219ad0e5a901af2f3c18211275282eb71108
File: MusesAwareApp.apk
common
Git: cab27ee67ea6b046edd3059a4d44a38f4ca708f6
File: common-0.0.1-SNAPSHOT.jar
server
Git: 7d659bf8122fcb0ad4458e5fcbb2635dc42d805b
File: server-0.0.1-SNAPSHOT.war
Fixes
- Disable screen lock for checking device configuration fixed
- Requires apps installed fixed, now uninstallation receives a policy and shows the feedback
- Folders sensed for opening,saving and receives policy now from non musesaware file explorer.
Issues
- opening blacklist app does not work.
- policies are some times not received on the first attempt.
- path is null in decision maker which causes no feedback shown to the user.
Coverage
- 33.5% coverage for server project (1 failure)
- No test coverage for common project
- 35.1% (No failures)
Code quality
- Server : Rules Compliance 84.1%, Violations 637
- Common : Rules Compliance 91.6%, Violations 75
- Client : Lint: 71 issues.
Feature List
| UC 1 states: “Check of the end user terminal before granting access to company sensitive data on the company intranet” | |||||
|---|---|---|---|---|---|
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F1:1 | Grant/deny access to company sensitive information | 1 | Open | 3% | "Total actions: 62 |
| Left: 4" | |||||
| F1:2 | Check user device's security level | 1 | Open | 50% | "Total actions: 6 |
| Left: 3" | |||||
| F1:3 | Check user past usage patterns | 1 | Open | 20% | "Total actions:5 |
| Left:1" | |||||
| F1:4 | Check connection properties | 1 | Done | 0% | |
| F1:5 | Evaluation of device trust level | 2 | Open | 100% | |
| F1:6 | Provide ad hoc suggestions to the user | 1 | Done | 0% | |
| F1:7 | MUSES checks if end user is connected to the company Intranet | 1 | Done | 0% | |
| F1:8 | MUSES checks Wi-Fi is unsecure | 1 | Done | 0% | |
| F1:9 | MUSES perform risk analysis. Risk analysis is based on continuously updating the measures of trust levels. | 1 | Done | 0% | |
| F1:10 | MUSES provides authentication | 1 | Open | 30% | |
| UC 2 states: “Check of the end user terminal before granting access to company sensitive data from the Internet” | |||||
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F2:1 | Check potentially unsafe communication settings | 1 | Done | 0% | |
| F2:2 | Check existence of additional protection features (VPN,…) | 1 | Done | 0% | |
| F2:3 | Provide ad hoc suggestions to the user: Migrate to a secure network connection | 1 | Done | 0% | |
| F2:4 | Detection of sensible data insertion (PIN, passwords,…) | 1 | Done | 0% | |
| F2:5 | Evaluation of current security and risk level | 1 | Done | 0% | |
| F2:6 | Propose a possible insertion and data transmission method (private place, Setup SSL connection) | 1 | Open | 100% | |
| F2:7 | Performs all the checks necessary to evaluate the context and uses the results against the company policies associated to the requested asset | 2 | Open | 100% | |
| F2:8 | Grant/deny access to company sensitive information | 1 | Done | 0% | |
| F2:9 | MUSES dynamically perform risk analysis. Risk analysis is based on continuously updating the measures of trust levels. | 1 | Done | 0% | |
| UC 3 states: “Dynamic data aggregation within the company intranet” | |||||
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F3:1 | Generate specific hints (advices) | 1 | Open | 60% | "Total actions:10 |
| Left:6" | |||||
| F3:2 | Detect asset's sensitivity level | 2 | Open | 100% | |
| F3:3 | Detection of data aggregation from different sources | 1 | Open | 100% | |
| F3:4 | Check risk of data combination | 1 | Open | 100% | |
| F3:5 | Grant/deny access to requested data | 1 | Done | 0% | |
| F3:6 | Removes sensible information stored into the terminal if the device is not safe. | 1 | Open | 25% | "Total actions:4 |
| Left:1" | |||||
| F3:7 | Assign value to assets | 1 | Open | 100% | |
| F3:8 | Perform risk analysis with regard to User's past behaviour | 1 | Done | 0% | |
| UC 4 states: “Dynamic data aggregation from the Internet” | |||||
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F4:1 | Change Policy. (A trusted user and terminal remotely change a document policy. A policy is an Asset) | 1 | Open | 100% | |
| F4:2 | Configuration enforcement | 1 | Open | 100% | |
| F4:3 | Performs more strict evaluation of the device environment | 1 | Open | 100% | |
| F4:4 | Actively monitors terminal's configuration within the trusted state | 1 | Done | 0% | |
| F4:5 | Detects a change of configuration in the system and reverts the terminal to the non-trusted status | 1 | Open | 100% | |
| UC 5 states: “Check-up of the connected terminals/end points (still previously connected)” | |||||
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F5:1 | Detection of terminal corruption | 1 | Open | 100% | "Total actions:2 |
| Left:2" | |||||
| F5:2 | Analyse risk of having two active editing sessions on the same asset (Removed from scope matrix) | 1 | Open | 100% | "Total actions:2 |
| Left:2" | |||||
| F5:3 | Understanding the risk that a cross contamination could have happened in the past or is still present | 1 | Open | 100% | "Total actions:2 |
| Left:2" | |||||
| F5:4 | Evaluating the security levels and the interaction models among the devices | 1 | Open | 100% | |
| F5:5 | Suspending the task until the terminal has been verified and possibly cleaned | 1 | Open | 100% | |
| F5:6 | Invokes cleaning of the stored assets (If no other solution available) | 2 | Open | 100% | "Total actions:2 |
| Left:2" | |||||
| F5:7 | Keep track of all opened and closed assets, multiple devices, Users | 2 | Open | 100% | |
| UC 6 states: “A non-secure mobile terminal is physically moved to a high-security area” | |||||
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F6:1 | Sensing of physical context (GPS, Cell Ids, indoor Wi-Fi) | 1 | Open | 85% | "Total actions:7 |
| Left:6" | ... |
Muses Prototype # 1 RC5
Release Notes MUSES
Copyright (C) 2013 - 2014 Sweden Connectivity
Date: 20140911
Release: Muses Prototype # 1 RC5
Binaries
Muses Client
Git: ab2e1b869431642b6d956202700b95654cd4b891
File: MusesClient.apk
MusesAwareApp
Git: 943700b7235fb60962a4751b78e7a295a7d02324
File: MusesAwareApp.apk
common
Git: 33157424664af996018480fa507e8cb09e817347
File: common-0.0.1-SNAPSHOT.jar
server
Git: 3e1f08a6a419c2b494f8236c5628fff315722aac
File: server-0.0.1-SNAPSHOT.war
Fixes
- Code quality improved (Client/Server=> Connection Manager package) and test coverage improved Connection Manager Server
- Mail sensor senses the email sent and receives the policy from server
- Attachment sensor support added for Tablet.
- Different risktreatment received from after virus infection
- Polices receive for all implemented actions now.
Issues
- Tomcat stops responding after a while then need to be restarted.
- Memory leak due to hibernate
Coverage
- 32.4% coverage for server project (1 failure)
- No test coverage for common project
- 35.1% (No failures)
Code quality
- Server : Rules Compliance 81.1%, Violations 695
- Common : Rules Compliance 91.5%, Violations 58
- Client : Lint: 71 issues.
| UC 1 states: “Check of the end user terminal before granting access to company sensitive data on the company intranet” | |||||
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F1:1 | Grant/deny access to company sensitive information | 1 | Open | 3% | "Total actions: 62 |
| Left: 4" | |||||
| F1:2 | Check user device's security level | 1 | Open | 50% | "Total actions: 6 |
| Left: 3" | |||||
| F1:3 | Check user past usage patterns | 1 | Open | 20% | "Total actions:5 |
| Left:1" | |||||
| F1:4 | Check connection properties | 1 | Done | 0% | |
| F1:5 | Evaluation of device trust level | 2 | Open | 100% | |
| F1:6 | Provide ad hoc suggestions to the user | 1 | Done | 0% | |
| F1:7 | MUSES checks if end user is connected to the company Intranet | 1 | Done | 0% | |
| F1:8 | MUSES checks Wi-Fi is unsecure | 1 | Done | 0% | |
| F1:9 | MUSES perform risk analysis. Risk analysis is based on continuously updating the measures of trust levels. | 1 | Done | 0% | |
| F1:10 | MUSES provides authentication | 1 | Open | 30% | |
| UC 2 states: “Check of the end user terminal before granting access to company sensitive data from the Internet” | |||||
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F2:1 | Check potentially unsafe communication settings | 1 | Done | 0% | |
| F2:2 | Check existence of additional protection features (VPN,…) | 1 | Done | 0% | |
| F2:3 | Provide ad hoc suggestions to the user: Migrate to a secure network connection | 1 | Done | 0% | |
| F2:4 | Detection of sensible data insertion (PIN, passwords,…) | 1 | Done | 0% | |
| F2:5 | Evaluation of current security and risk level | 1 | Done | 0% | |
| F2:6 | Propose a possible insertion and data transmission method (private place, Setup SSL connection) | 1 | Open | 100% | |
| F2:7 | Performs all the checks necessary to evaluate the context and uses the results against the company policies associated to the requested asset | 2 | Open | 100% | |
| F2:8 | Grant/deny access to company sensitive information | 1 | Done | 0% | |
| F2:9 | MUSES dynamically perform risk analysis. Risk analysis is based on continuously updating the measures of trust levels. | 1 | Done | 0% | |
| UC 3 states: “Dynamic data aggregation within the company intranet” | |||||
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F3:1 | Generate specific hints (advices) | 1 | Open | 60% | "Total actions:10 |
| Left:6" | |||||
| F3:2 | Detect asset's sensitivity level | 2 | Open | 100% | |
| F3:3 | Detection of data aggregation from different sources | 1 | Open | 100% | |
| F3:4 | Check risk of data combination | 1 | Open | 100% | |
| F3:5 | Grant/deny access to requested data | 1 | Done | 0% | |
| F3:6 | Removes sensible information stored into the terminal if the device is not safe. | 1 | Open | 25% | "Total actions:4 |
| Left:1" | |||||
| F3:7 | Assign value to assets | 1 | Open | 100% | |
| F3:8 | Perform risk analysis with regard to User's past behaviour | 1 | Done | 0% | |
| UC 4 states: “Dynamic data aggregation from the Internet” | |||||
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F4:1 | Change Policy. (A trusted user and terminal remotely change a document policy. A policy is an Asset) | 1 | Open | 100% | |
| F4:2 | Configuration enforcement | 1 | Open | 100% | |
| F4:3 | Performs more strict evaluation of the device environment | 1 | Open | 100% | |
| F4:4 | Actively monitors terminal's configuration within the trusted state | 1 | Done | 0% | |
| F4:5 | Detects a change of configuration in the system and reverts the terminal to the non-trusted status | 1 | Open | 100% | |
| UC 5 states: “Check-up of the connected terminals/end points (still previously connected)” | |||||
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F5:1 | Detection of terminal corruption | 1 | Open | 100% | "Total actions:2 |
| Left:2" | |||||
| F5:2 | Analyse risk of having two active editing sessions on the same asset (Removed from scope matrix) | 1 | Open | 100% | "Total actions:2 |
| Left:2" | |||||
| F5:3 | Understanding the risk that a cross contamination could have happened in the past or is still present | 1 | Open | 100% | "Total actions:2 |
| Left:2" | |||||
| F5:4 | Evaluating the security levels and the interaction models among the devices | 1 | Open | 100% | |
| F5:5 | Suspending the task until the terminal has been verified and possibly cleaned | 1 | Open | 100% | |
| F5:6 | Invokes cleaning of the stored assets (If no other solution available) | 2 | Open | 100% | "Total actions:2 |
| Left:2" | |||||
| F5:7 | Keep track of all opened and closed assets, multiple devices, Users | 2 | Open | 100% | |
| UC 6 states: “A non-secure mobile terminal is physically moved to a high-security area” | |||||
| Ref: | Feature description | Prototype | Status | Delta | Comments |
| F6:1 | Sensing of physical context (GPS, Cell Ids, indoor Wi-Fi) | 1 | O... |
Feature Complete RC4
Release Notes MUSES
Copyright (C) 2013 - 2014 Sweden Connectivity
Date: 20140807
Release: Muses Feature Complete
Binaries
Muses Client
Git: 4dcc6d690ad97153eb07a9e4f279bbc97a074c4d
File: MusesClient.apk
MusesAwareApp
Git: 3995e7321d743358298f87e1657f6cbfb791e386
File: MusesAwareApp.apk
common
Git: 9302d93084239a3b49caa1dc69c8af6534d61d14
File: common-0.0.1-SNAPSHOT.jar
server
Git: c9ff1b4000e7097d63b42df0cff8d98f3da405aa
File: server-0.0.1-SNAPSHOT.war
Fixes
- Code quality improved (Client/Server=> Connection Manager package) and test coverage improved Connection Manager Server
Issues
- Tomcat stops responding after a while then need to be restarted.
- Log4j stops logging after a while (most probably above tomcat problem causing it)
- Mail sensor does not work with tabs.
- No policy received from server for virus found event.
- No policy received for email event (fake or gmail compose email)
Coverage
- 30.3% coverage for server project (1 failure)
- No test coverage for common project
- 35.1% (No failures)
Code quality
- Server : Rules Compliance 80.5%, Violations 644
- Common : Rules Compliance 92.4%, Violations 58
- Client : Lint: 70 issues.
Feature List MUSES
| UC 1 states: “Check of the end user terminal before granting access to company sensitive data on the company intranet” | ||||
|---|---|---|---|---|
| Ref: | Feature description | Prototype | Status | Delta |
| F1:1 | Grant/deny access to company sensitive information | 1 | Open | 3% |
| F1:2 | Check user device's security level | 1 | Open | 50% |
| F1:3 | Check user past usage patterns | 1 | Open | 20% |
| F1:4 | Check connection properties | 1 | Done | 0% |
| F1:5 | Evaluation of device trust level | 2 | Open | 0% |
| F1:6 | Provide ad hoc suggestions to the user | 1 | Done | 0% |
| F1:7 | MUSES checks if end user is connected to the company Intranet | 1 | Done | 0% |
| F1:8 | MUSES checks Wi-Fi is unsecure | 1 | Done | 0% |
| F1:9 | MUSES perform risk analysis. Risk analysis is based on continuously updating the measures of trust levels. | 1 | Done | 0% |
| F1:10 | MUSES provides authentication | 1 | Done | 30% |
| UC 2 states: “Check of the end user terminal before granting access to company sensitive data from the Internet” | ||||
| Ref: | Feature description | Prototype | Status | Delta |
| F2:1 | Check potentially unsafe communication settings | 1 | Done | 0% |
| F2:2 | Check existence of additional protection features (VPN,…) | 1 | Done | 0% |
| F2:3 | Provide ad hoc suggestions to the user: Migrate to a secure network connection | 1 | Done | 0% |
| F2:4 | Detection of sensible data insertion (PIN, passwords,…) | 1 | Done | 0% |
| F2:5 | Evaluation of current security and risk level | 1 | Done | 0% |
| F2:6 | Propose a possible insertion and data transmission method (private place, Setup SSL connection) | 1 | Open | 100% |
| F2:7 | Performs all the checks necessary to evaluate the context and uses the results against the company policies associated to the requested asset | 2 | Open | 100% |
| F2:8 | Grant/deny access to company sensitive information | 1 | Done | 0% |
| F2:9 | MUSES dynamically perform risk analysis. Risk analysis is based on continuously updating the measures of trust levels. | 1 | Done | 0% |
| UC 3 states: “Dynamic data aggregation within the company intranet” | ||||
| Ref: | Feature description | Prototype | Status | Delta |
| F3:1 | Generate specific hints (advices) | 1 | Open | 60% |
| F3:2 | Detect asset's sensitivity level | 2 | Open | 100% |
| F3:3 | Detection of data aggregation from different sources | 1 | Open | 100% |
| F3:4 | Check risk of data combination | 1 | Open | 100% |
| F3:5 | Grant/deny access to requested data | 1 | Done | 0% |
| F3:6 | Removes sensible information stored into the terminal if the device is not safe. | 1 | Done | 25% |
| F3:7 | Assign value to assets | 1 | Open | |
| F3:8 | Perform risk analysis with regard to User's past behaviour | 1 | Open | 0% |
| UC 4 states: “Dynamic data aggregation from the Internet” | ||||
| Ref: | Feature description | Prototype | Status | Delta |
| F4:1 | Change Policy. (A trusted user and terminal remotely change a document policy. A policy is an Asset) | 1 | Open | |
| F4:2 | Configuration enforcement | 1 | Open | 100% |
| F4:3 | Performs more strict evaluation of the device environment | 1 | Open | |
| F4:4 | Actively monitors terminal's configuration within the trusted state | 1 | Done | 100% |
| F4:5 | Detects a change of configuration in the system and reverts the terminal to the non-trusted status | 1 | Open | 100% |
| UC 5 states: “Check-up of the connected terminals/end points (still previously connected)” | ||||
| Ref: | Feature description | Prototype | Status | Delta |
| F5:1 | Detection of terminal corruption | 1 | Open | 100% |
| F5:2 | Analyse risk of having two active editing sessions on the same asset (Removed from scope matrix) | 1 | Open | 100% |
| F5:3 | Understanding the risk that a cross contamination could have happened in the past or is still present | 1 | Open | 100% |
| F5:4 | Evaluating the security levels and the interaction models among the devices | 1 | Open | |
| F5:5 | Suspending the task until the terminal has been verified and possibly cleaned | 1 | Open | |
| F5:6 | Invokes cleaning of the stored assets (If no other solution available) | 2 | Open | 100% |
| F5:7 | Keep track of all opened and closed assets, multiple devices, Users | 2 | Open | |
| UC 6 states: “A non-secure mobile terminal is physically moved to a high-security area” | ||||
| Ref: | Feature description | Prototype | Status | Delta |
| F6:1 | Sensing of physical context (GPS, Cell Ids, indoor Wi-Fi) | 1 | Open | 85% |
| F6:2 | Sensing of connected peripherals (USB keys) | 2 | Open | |
| F6:3 | Detection of unsatisfied policy requirements | 1 | Open | 7% |
| F6:5 | Avoids physical violation of an asset | 1 | Open | |
| F6:6 | Enforce the new configuration on the terminal (making sure physical location is secure) | 2 | Open | 13% |
| UC 7 states: “Supply chain partner data exchange” | ||||
| Ref: | Feature description | Prototype | Status | Delta |
| F7:1 | Application installation control | 1 | Open | 16% |
| F7:2 | Application execution control | 1 | Done | 0% |
| F7:3 | Check communication encryption | 1 | Done | 0% |
| F7:4 | Evaluate all communication endpoints (i.e., the company user’s and its supply chain counterparts’ terminals) | 2 | Open | |
| F7:5 | Prevent the sharing of any sensible data to the uncontrolled terminals of the third parties until MUSES is corre... |
Feature Complete RC3
Release Notes MUSES
Copyright (C) 2013 - 2014 Sweden Connectivity
Date: 20140724
Release: Muses Feature Complete
Binaries
Muses Client
Git: e5db140ec0ec62b003f41c6d1496741f2f0dfbc6
File: MusesClient.apk
MusesAwareApp
Git: 3995e7321d743358298f87e1657f6cbfb791e386
File: MusesAwareApp.apk
common
Git: 7f6e17ae1dedec60dda08341e1dec8dee2efa3ba
File: common-0.0.1-SNAPSHOT.jar
server
Git: ab58da87e6aa1f0322587863b6819696f96b11b9
File: server-0.0.1-SNAPSHOT.war
Features included
Context event to server (HITEC):
- Open app event sent to server
- Changes in network configurations are sent to the server
- Modifications of observed folders are sent to the server
- App installation, uninstallation and update are sent
- Installed apps are sent
- User feedback on MUSES UI dialogs are sent
- Device protection indicators like a rooted device are sent
- All context informations are transformed to JSON
- Information about the android system and device like the SDK level and the IMEI is sent
- Muses client receives, transforms and sends information from muses aware apps to the server
Polices received from Server (S2):
- Device policy received from the server
- Policy for accessing public asset with unsecure Wi-Fi and secure Wi-Fi
- Policy for accessing confidential asset with unsecure Wi-Fi and secure Wi-Fi
- Policy for virus detected on user device
- Policy for email with and without attachments
Event Processing from Server (S2):
- Implementation of Policy Compliance
- Composition of Access Requests
- Detection of clues associated to access requests
- Detection of Device Security State changes
- Detection of Security Incidents
- Detection of User Feedback
RT2AE (UNIGE):
- Implementation of the Decision not the last version
- Creation of RiskTreatment
- Detection of Threats (simulation mode)
- Computing the probability of Threats (simulation mode)
- Computing TrustValue of User (simulation mode)
- Computing TrustValue of the Device (simulation mode)
Fixes
- SSL support added for spring now.
- Actions fixed for virus found, email
- communication fixed for server not responding
Issues
- Tomcat stops responding after a while then need to be restarted.
System tests
- Setup 1
- VirusFound 1
- Setup 2
- OpenInternalAsset 2
- OpenStrictlyConfidentialAsset 2
- OpenSensitiveAsset 2
- VirusFound 2
- SendEmail 2
- SendEmailWAttachment 2
- InstallApplication 2
Coverage
- 29.19% percent coverage for server project (No failures)
- No test coverage for common project
- 34% (No failures)
Code quality
- Server : Rules Compliance 80%, Violations 660
- Common : Rules Compliance 92.4%, Violations 58
- Client : Lint: 71 issues.
Feature Complete RC2
Release Notes
Date: 20140717
Release: Muses Feature Complete
Muses Client
Muses Client
Git: 44933f0aa886edf9ee41056b8e06feb03e75c90b
File: MusesClient.apk
MusesAwareApp
Git: 832448e5b796dd02af2ca3cbd1db99d851de7cd4
File: MusesAwareApp.apk
Common Code
common
Git: 2b80d1ca39b508048bc08dae5b8bc35454d7c17e
File: common-0.0.1-SNAPSHOT.jar
Server
server
Git: 34d7ca502c1ed2441f10bd2d2f9fc6c9f4d4d804
File: server-0.0.1-SNAPSHOT.war
Updates:
- Database implementation added in server (Hibernate and JPA)
- Fix for Server by S2 but still problems
Coverage :
- 31.9% percent coverage for server project (No failures)
- No test coverage for common project
- 34% (No failures)
Code quality:
Server : Rules Compliance 72.5%, Violations 576
Common : Rules Compliance 92.4%, Violations 58
Client : Lint: 71 issues.
RC2-Beta-Protptype 1
Release Notes
Date: 20140425
Release: Muses Prototype - 1 Alpha
Muses Client
Muses Client
Git: d2ed4ea
File: MusesClient.apk
MusesAwareApp
Git: 9f4a92a
File: MusesAwareApp.apk
Common Code
common
Git: 0f76c70
File: common-0.0.1-SNAPSHOT.jar
Server
server
Git: 49d45e7
File: server-0.0.1-SNAPSHOT.war
Comments:
- No communication with the server, when user performs any action (login).
- No policy or other data is received from the server.
Fixes:
- Communication fixed between client and server for users action from muses aware app (accessing an asset)
- Fixes in muses GUI (Logged in view was not shown after login).
Coverage :
- 35.8% (31 tests) percent coverage for server project
- No test coverage for common project
- 31% coverage for client project
Code quality:
Server : Rules Compliance 72%, Violations 375
Common : Rules Compliance 93.5%, Violations 46
Client : Lint: 84 issues.
Feature Complete RC1
Release Notes
Date: 20140703
Release: Muses Feature Complete
Muses Client
Muses Client
Git: 21cfa298a4b81b031f2b1e69073e7b65c62245a7
File: MusesClient.apk
MusesAwareApp
Git: 5910102f3977b2676e74e1ad2bb55dd063c12ec9
File: MusesAwareApp.apk
Common Code
common
Git: ec975f8fa0f2fe78910bf32020a8408dc8caf575
File: common-0.0.1-SNAPSHOT.jar
Server
server
Git: 4f5834c9d6e39fb4b5b0aa5da6a53715e0ef283e
File: server-0.0.1-SNAPSHOT.war
Coverage :
- 31.5% percent coverage for server project (No failures)
- No test coverage for common project
- 34% (No failures)
Code quality:
Server : Rules Compliance 69.5%, Violations 614
Common : Rules Compliance 91.7%, Violations 73
Client : Lint: 68 issues.
RC1-Beta-Protptype 1
Release Notes
Date: 20140416
Release: Muses Prototype - 1 Alpha
Muses Client
Muses Client
Git: acbf68e
File: MusesClient.apk
MusesAwareApp
Git: 9f4a92a
File: MusesAwareApp.apk
Common Code
common
Git: 21681ca
File: common-0.0.1-SNAPSHOT.jar
Server
server
Git: d0d36e0
File: server-0.0.1-SNAPSHOT.war
Comments:
- No communication with the server, when user performs any action (login, accessing asset)
- First version of decision maker, static responses sent currently.
Coverage :
- 38.8% (31 tests) percent coverage for server project
- No test coverage for common project
- 26% coverage for client project
Code quality:
Server : Rules Compliance 74.7%, Violations 324
Common : Rules Compliance 94.2%, Violations 41
Client : Lint: 84 issues.
Final-Gamma-Protptype 1
Release Notes
Date: 20140610
Release: Muses Prototype - 1 Alpha
Muses Client
Muses Client
Git: 7c4778b28bb2451a6148b1f83e8ba52a871f5978
File: MusesClient.apk
MusesAwareApp
Git: 80aeb01abc8e150b84d8a14130b088cf8917b73d
File: MusesAwareApp.apk
Common Code
common
Git: 3383a28f021cd083aff11c248ee0f1805ed0fb20
File: common-0.0.1-SNAPSHOT.jar
Server
server
Git: af6f758e0a655fe44c9870d1c95e58be17b1e588
File: server-0.0.1-SNAPSHOT.war
Updates:
- Client-Server communication more stable.
- Policy received from the server.
- Different decision showed according to policies.
Coverage :
- 24.5% percent coverage for server project
- No test coverage for common project
- coverage for client project not available due to test failures
Code quality:
Server : Rules Compliance 68.7%, Violations 533
Common : Rules Compliance 92.4%, Violations 57
Client : Lint: 84 issues.
Gamma-Protptype 1
Release Notes
Date: 20140602
Release: Muses Prototype - 1 Alpha
Muses Client
Muses Client
Git: ce9bcb07c71edc3efa14d06ac261afe3debb9524
File: MusesClient.apk
MusesAwareApp
Git: d7ef8871d6e511e535cc18bfea1ab4eaa5c13a82
File: MusesAwareApp.apk
Common Code
common
Git: e6c9b88e4911918daa5aed9f26c15a79f4d240ca
File: common-0.0.1-SNAPSHOT.jar
Server
server
Git: 70501fcf0915b792af4e54ff79248e5415cc21db
File: server-0.0.1-SNAPSHOT.war
Updates:
- Client-Server communication more stable.
- Policy received from the server.
- UI cleaned according to the latest GUI.
Coverage :
- 31.5% percent coverage for server project
- No test coverage for common project
- coverage for client project not available due to test failures
Code quality:
Server : Rules Compliance 68.7%, Violations 533
Common : Rules Compliance 92.4%, Violations 57
Client : Lint: 84 issues.