Digital Money

 PROJECT DOCUMENTATION

HIGHLIGHT REPORT

Project:     Digital Money

Release:         06-11-2020

Date:              23-10-2020

PRINCE2

Author:  Karthik Reddy Puram    

Owner:   University of Bedfordshire

Client:   University of Bedfordshire

Document Ref: CATS/G4/CIS120-6

Version No: 1.1

1        Highlight Report History

1.1     Document Location

This document is only valid on the day it was printed.

The source of the document will be found at this location.

1.2     Revision History

Date of this revision:                                    

Date of next revision:     

 

Revision date	Previous revision date	Summary of Changes	Changes marked
Nil	Nil		Nil

1.3     Approvals

This document requires the following approvals.

Signed approval forms should be filed appropriately in the project filing system.

 

Name	Signature	Title	Date of Issue	Version
University of Bedfordshire		Project client	23-10-2020	1.1
Ashish kumar Reddy Ramidi		Project Manager	23-10-2020	1.1

1.4     Distribution

This document has been distributed to:

 

Name	Title	Date of Issue	Version
University of Bedfordshire	client	23-10-2020	1.1
Ashish kumar Reddy Ramidi	Project manager	23-10-2020	1.1
Mehidia AfrinTania	Team member	23-10-2020	1.1
Rani Noothula	Team member	23-10-2020	1.1
Akash Dinkarkumar Patel	Team member	23-10-2020	1.1
Vijayakanth Dhulipalla	Team member	23-10-2020	1.1
Karthik Reddy Puram	Team member	23-10-2020	1.1
Sanjay Reddy perkit	Team member	23-10-2020	1.1
Amandeep Kaur	Team member	23-10-2020	1.1

2      Table of Contents

                                                                                                                      

 

1      Highlight Report History                                                                  

1.1  Document Location                                                                   

1.2  Revision History

1.3  Approvals

1.4     Distribution

2      Table of Contents

3      Date

4      Period

5      Status Summary

6      This Reporting Period

7      Next Reporting Period

8      Project and Stage Tolerance Status

9      Requests for Change

 

10    Key Issues and Risks

 

11    Lessons Report (if appropriate)

3        Date

This project report has been started on 28-09-2020.

4        Period

The period of the highlight report is covered from 19-10-2020 to 23-10-2020.

5        Status Summary

The before 3 weeks of the project mainly working on the project management documentation. The project mainly works on those three weeks the project brief, project initiation document including risk response plan and the highlight report. And other two documents like RACI matrix and Gantt chart those are included in the Project Brief during this period.

The poster, structure report, legal and ethical report, video, social media, lessons learned report are additionally included in the next week For suppose week5.

 

Status of all Project Tasks:

 

·       RACI matrix is Completed Modified as per given Review from Client.

·       Gantt chart is completed.

·       Project Brief is completed modified as per given Review from client.

·       Project Initiation document also completed modified as per given review from client.

·       Highlight is completed and submitted for Review.

·       Structure Report is in progress. Not yet submitted.

·       The video is in the execution. Not yet submitted.

·       Social media is in progress. Not yet submitted.

·       Poster is waiting input from structured Report. Not yet submitted.

·       Legal and ethical report id in progress. Not yet submitted.

·       Lessons Learned report not yet started. Not yet submitted.

6        This Reporting Period:

 

During this Reporting period, It basically focussed on passing on the endeavour the project documentation, for instance, project brief, project Initiation Document (PID) and the Highlight report. All these documentation has been made and submitted, but due to inconvenience of the project making, the gathering has not submitted the document before the deadline time and there has been a couple of changes done on the project brief, Project Initiation document (PID) and RACI Matrix during this period as per the suggestion from the client.

Work Package:

·       In this report period, we have completed project brief and including Gantt chart  Modified as per feedback from the client.

·       In this report period, we have completed project Initiation document and including       the Risk management plan also Modified as per feedback from client.

·       We change the RACI matrix also as per the feedback from the client.

·       Highlight report is completed and submitted for approval.

7        Next Reporting Period

For this Reporting period the project team needs to deliver undertakings which incorporates the Structure report, legal and ethical report, video, Social media, Poster and lessons learned report the last week has an individual intelligent report that must be submitted.

Work package:

·       Structure Report is in progress.

·       The video is in the execution.

·       Social media is in progress.

·       Poster is waiting input from structured Report.

·       Legal and ethical report id in progress.

·       Lessons Learned report not yet started.

8        Project and Stage Tolerance Status

The Project needs to experience many requirements, and tolerances to convey the task documentation effectively. These tolerances are the limits set by the Project individuals, for viable dynamic. The whole project team of 'DIGITAL MONEY' have set after tolerances:

 

Schedule Tolerance: First week, the group couldn't finish the given task inside the schedule time period, as the undertaking was trickier.

 

Risk Tolerance: The project team investigated the Risk of correspondence holes while creating project brief and further more project Initiation, and this issue was settled by evading conflicting information flow.

9                Requests for Change

·       As per the request raised we altered the duration video from1 minute to 5 minutes.

·       In project brief we sorted the issue regarding team structure.

10            Key Issues and Risks

·       Concerns related to digital money centre around their price volatility, ways of criminal behaviour, and environmental impacts.

·       Changes have been done on RACI MATRIX about Roles and Responsibilities.

·       Changes have been done on project Brief and Project Initiation document as per given by feedback from client.

11            Lessons Report (if appropriate)

The project team of DIGITAL MONEY, faced various inconveniences while building up the Project. A portion of the checks while building up the project are according to the given below:

 

·       The team required a slight unwinding in the dispersed deadline time, as the team members didn't think about the bearing in the production of the task.

·       Communication holes emerge at the same time, later on they were managed effectively.

 

 

Read More

CO3102/CO7102 Mobile and Web Applications

CO3102/CO7102 Mobile and Web Applications 

Coursework 1 

XML and JSON 

Important Dates: 

Handed out: 12-Oct-2020

Deadline: 3-Nov-2020 at 16:59 GMT 

Please ensure that you submit your work on time.

• This coursework counts as 10% of your final mark. 
• Please read guidelines on plagiarism in the study guide and course documentation. 
• This coursework requires knowledge about XML Schema, XSLT, JSON and Document Parsing. 
• Learning outcome:

 ◦ Use data-interchange formats (XML and JSON) and techniques appropriately to create documents and handle data. 

 Data Description

           Consider an XML document (WebAppInterface.xml): 

<?xml version="1.0" encoding="UTF-8"?> <interface id="RESTController">  <package>uk.ac.le.cs.wt</package> <extends> <from>Remote</from> </extends> <import>java.rmi.Remote</import> <import>java.rmi.RemoteException</import> <import>java.net.*</import> <abstract_method name="authenticateUser"> <access_level>public</access_level> <arguments> <parameter type="String">user</parameter> <parameter type="String">password</parameter> </arguments> <throws> <exception>RemoteException</exception> <exception>SecurityException</exception> </throws> <return>boolean</return> </abstract_method> <abstract_method name="activateUser"> <access_level>public</access_level> <arguments> <parameter type="URL">link</parameter> </arguments> <return>void</return> </abstract_method> </interface>

This XML document describes a Java interface below:

package uk.ac.le.cs.wt; import java.rmi.Remote; import java.rmi.RemoteException; import java.net.*; interface RESTController extends Remote{ public boolean authenticateUser (String user, String password) throws RemoteException, SecurityException; public void activateUser(URL link); }

Tasks:

Task 1: [40 Marks]

Write an XML Schema (WebAppInterface.xsd) that allows validation of the provided XML document. Note that the schema must be consistent with these rules in Java: 

• An interface may extend one or many interfaces. 

• There can be only one package statement 

• There can be zero to many import statements 

• An interface can have zero to many abstract methods 

• A method only allows one value to be returned (or void) 

• A method can only have zero or one visibility modifier * 

• A method can accept zero to many arguments

 • Exception(s) may be thrown from a method 

* If a method has no visibility modifier then it is accessible only within its own package (default visibility); assuming all methods are non-static. (Hint: Related lab exercise – Week 1)

(Hint: Related lab exercise – Week 1)

Task 2: [30 Marks] 

Write an XSLT stylesheet (WebAppInterface.xslt) that takes the provided XML document as input and generates an HTML document as follows: 

RESTControler

Operation	Argument(s)	Return
authenticateUser	User:String,password:string	Boolean
ActivateUser	Link: URL	Void

Note: You may show the result in a different page layout or colour scheme. The page must display the controller id, return type and the parameter list of each method. (Hint: Related lab exercise – Week 2/3)

{  "abstract_method": [  {  "name": "authenticateUser",  "access_level": "public",  "arguments": [  {  "type": "String",  "variable": "user"  },  {  "type": "String",  "variable": "password"  }  ],  "throws": [  "RemoteException",  "SecurityException"  ],  "return": "boolean"  },  {  "name": "activateUser",  "access_level": "public",  "arguments": {  "parameter": {  "type": "URL",  "variable": "link"  }  },  "return": "void"  }  ] }

Note: A Java template (WebAppInterfaceParser.java, and you will need xercesImpl.jar and xmlapis.jar which are provided on Blackboard) is provided for Task 3. However, you are allowed to use any programming languages or parsers for this task as you wish. If so, please include a text file README.txt explaining how to run your code. 

Note that this JSON output was deliberately formatted in this way to prevent people from using offthe-shelf XMLtoJSON function provided by certain APIs. If there is only one parameter in the method then it should be structured as an object (e.g. parameter: {}) while if there are multiple parameters, you should print it as an JSON array using [].

(Note: You are free to use any parsers, but the implementation of the parsing technique must be your work. The program must generate the JSON output specified above (e.g. must not contain “package”, “import”), which means you are not allowed not use any off-the-shelf XML-to-JSON libraries for the conversion e.g. toJSONObject)

Submission 

• Zip all files in a single zip file for submission. 

o WebAppInterface.xsd 

o WebAppInterface.xslt 

o WebAppInterfaceParser.java (or in your language of choice) 

• The archive should be named CO3102_CW1_email_id.zip or CO7102_CW1_email_id.zip (e.g. CO3102_CW1_yh37.zip). 

Your submission should also include a completed coursework plagiarism coversheet (print and signed PDF or image). You need to submit the zip file via Blackboard and you are allowed to resubmit as many times as you like before the deadline. Marks for any coursework which does not have the accompanying cover sheet will be withheld till you provide one.  

Marking Scheme

Note: In addition to the sample XML provided in Table 1, additional XML documents will be included in the test suite.

 Part 1: XML Schema validity checking will be automated. In total, a test suite consisting of 12 XML documents will be used for the assessment. The marks will be distributed according to test results. 

Part 2: XSLT will be compiled and applied to 7 test cases (XML documents) for the assessment. All HTML pages will be checked by TA(s) manually. The marks will be distributed according to test results. 

Part 3: In total, 7 test cases (XML documents) will be used the assessment. Any JSON generated by your XML Parser will be checked by an JSON validator. The marks will be distributed according to test results. 

Anonymous marking 

We operate an anonymous marking scheme. All submitted files will be renamed using anonymous fingerprinting generated by SHA256. 

Read More