University of Leicester

Department of Computer Science

CO7201 Individual Project

2004

Student Viva Schedule  New

Thesis and Viva

Module Description

Project Allocation and Second Marking  

Important Dates:  

• Friday, 30 April 2004. Submission of project registration forms (pdf) (ps) to module convenor*.
• Monday, 10 May 2004.  Students presentation and  the preliminary report. 
• Friday, 9 July 2004. Submission of Interim Report 1 (5%). 
• Monday, 9 August 2004. Submission of Interim Report 2 (5%). 
• Friday, 10 September 2004. Submission of the dissertation.

        * The form should be filled electronically using a word processor and signed by the student and supervisor.

Resources:  

• CO7203 Planning module will equip the students with the  necessary skills for planning and working on their projects will doing CO7203 course work at the same time.
• The List of Project Proposals
• An advice on enhancing your writing and presentation skills from Student Learning Centre

M.Sc. Project Proposals:  Updated

The following is the list of project proposed by some members of staff. Students are welcomed to discuss these projects with the staff proposing them. Also, students can propose their own projects and seek a suitable member of staff to supervise it. After picking a project and a supervisor, the student should get the project supervisor to sign the project registration form and hand it to Dr. El-Ramly by the deadline.

1. XML Tools to Support the Software Process –  Dr. Simon Ambler  

2. Web Service Composition - Dr. Stephan Reiff-Marganiec  

3. Efficient XML Technology for Data Storage and Querying – Prof. Rajeev Raman  

4. Coordination Technologies – Prof. José Luiz Fiadeiro  

5. Development of a graphical editor and simulator for component-based Petri nets – Dr. Nasreddine Aoumeur

6. Development of a graphical interface for editing/validating an integrated UML-based conceptual model  – Dr. Nasreddine Aoumeur  

7. From Legacy Systems to Web Services - Dr. Mohammad El-Ramly

8. Multi User Dungeon: A Mobile Game - Dr. Piotr Kosiuczenko  

9. Online Java Automatic Knowledge Test Framewo - Dr. Piotr Kosiuczenko  

10. Imaging Fabrics for E-commerce - Proposed by Mick Sharpe

1. XML Tools to Support the Software Process –  Dr. Simon Ambler

 A mature software development process will produce many interrelated artefacts: plans, schedules, specifications, program code, test data, inspection reports, defect reports, etc. Most of these are highly structured documents.

 XML provides a standard way to specify the structure and content of documents. Special tags, with semantic significance, are introduced to mark-up the content of the document. These are particular to the type of document and are specified by a Document Type Definition (DTD).

 XML for Structured Requirements (ReqSol 1.0) is an example of an XML applied o requirements specifications and solutions documents

 http://www.cs.le.ac.uk/~sambler/xml/reqsol/1.0/welcome.html

 The aim of this project would be to establish a general framework for storing and handling the XML documents arising from a software development process. This could be done by implementing a suitable XML database.

 The framework should include full version control and the possibility of tracing the relationships between documents. One might also enforce integrity constraints by using xlinkit

 http://www.systemwire.com/xlinkit/

The framework might be demonstrated in the specific case of structured equirements specifications using the ReqSol mark-up language.

2. Web Service Composition - Dr. Stephan Reiff-Marganiec

 Web services are software functionality available over the internet. While each service on its own offers certain features, it is the combination of many such services that allows creating powerful applications.

 Current work is considering how web services can be composed, and there are several ideas available. My interest is in dynamic (automatic) composition of services guided by some high level language -- preferably a language in the end-users domain.

 Possible projects in this area are manifold and might address issues such as:

·        Service conflict: from telephony service we know that composing services is not straight forward, for example two services which individually function as expected might lead to new, often undesired, behaviour when composed. What does feature interaction mean in the arena of web services, how can it be addressed?

·        Goal driven composition: How can we express at some higher level how services should be composed?

·        Service composition architectures: Considering that web services are supported by the web service architecture, one can ask whether this is strong enough to support composition? What enhancements to the architecture are required to support dynamic composition?

 These ideas are rather vague, as I would expect the student to explore the area in more detail and identify a suitable project, matching their interest and overlapping with my own ideas.

3. Efficient XML Technology for Data Storage and Querying – Prof. Rajeev Raman

"XML has become a de-facto standard data interchange format.  The ability of XML to represent far more complex relationships between data items than (say) the relational model means that XML is a very promising technology for data storage and querying as well.  However, XML technology for storage and querying is very inefficient compared to relational databases. In particular, the memory usage and CPU time for running queries is much, much worse. An important research direction is to reduce the "penalty" for using XML, and there is an ongoing research project in this direction. The project would involve implementing some of XML DOM's functionality on top of a highly space-efficient and fast representation.  The language could be C++ or Java, and the student would work with a team involving me, Naila Rahman, Richard Geary and one more PhD student."

4. Coordination Technologies – Prof. José Luiz Fiadeiro

Aims: Coordination Technologies are a set of architectural principles and modelling primitives centred around the notion of Coordination Contract.  They are based on the separation between what in systems can account for the computations that are responsible for the functionality of the services that they offer, and the mechanisms that coordinate the interconnections through which global properties of systems, such as absence of collisions and derailing, can emerge.  Such technologies rely on a mathematical model epitomised in the language CommUnity, and can be demonstrated over a Java-based Coordination Development Environment (CDE).  The Department, through the Software Specification and Design Group (SoftSD), is collaborating with ATX Software SA in the development of these technologies.

The aim of the project is to investigate the applicability of Coordination Technologies, namely through the use of CommUnity and Coordination Contracts over the CDE, to the modelling of particular kinds of systems (for instance, Railway Interlocking Systems, Telecommunications, Embedded Systems, Collaborative Systems, inter alia).  The choice of the class of system can be agreed between the student and the supervisor

Learning Outcomes:

• Understanding of typical challenges that Software Engineering is facing in the chosen application domain.
• Understanding of Coordination Technologies and their role in Software Development.

End Product: Application models in CommUnity and their implementation in the CDE; a critical appraisal of the applicability of Coordination Technologies to the application domain concerned.

5. Development of a graphical editor and simulator for component-based Petri nets – Dr. Nasreddine Aoumeur

Description : For adequately specifying and validating distributed information systems, we have recently developed in [AouSaa02] a specification/validation framework based on a sound integration of object-orientation with modularity features into a suitable variety of algebraic Petri nets. The conceptual model referred to as CO-NETS has been experienced with several case studies including : banking specification, staff-management system, train control system, and production system: all published in conferences. The validation of CO-NETS is based on graphical animation with rewriting logic as a formal symbolic computation support.

 Tasks:

The project around this framework consists in developing a software tool (using Java or C++) for editing and simulating these Co-nets components. More precisely the tasks would be:

1.      Conceive an adequate data structure for internally representing different Co-nets elements (places, transitions, arcs, classes, components, rewrite rules, ...). In this context, I have several exisitng structures, and the student has just to compare and adapt one of them.

2.      Implement this data structure with highly friendly graphical interfaces (with icons, menus, ...).

3.      For simulating the Co-nets, adapt the rewrite rules of the MAUDE system or develop proper rewriting system for computing transitions. Here also, I have developed several rewriting environments and the student has just to adapt them to the Co-nets specificities.

The Main References:

[AouSaa02] : N. Aoumeur and G. Saake, "A Component-Based Petri Net Model for Specifying and Validating Cooperative Information Systems". Data and Knowledge Engineering Journal, Volume 44, number 2, pages 143-187, August, 2002.

6. Development of a graphical interface for editing/validating an integrated UML-based conceptual model  – Dr. Nasreddine Aoumeur

Description : In our effort of bringing more coherence, in developing complex information systems, using different UML-based diagrams and constraints (OCL), we proposed in [AouSaaUML02] a new form of integrated UML-based conceptual model. This model endeavours integrating class-diagrams, object-diagrams, state diagrams and OCL constraints, and it has a rewriting logic semantics for rapid-prototyping purposes. The model bridges the gap between a UML analysis phase and its correct implementation.

 Tasks:

·        Propose an adequate internal representation for the UML-based integrated conceptual model (data structure for attributes, classes, generalisation, inheritance, ...)

·        Development of a graphical tool for editing this integrated model in a highly user-friendly manner.

·        Development of a rewriting-based engine for computing on this model and doing some form of simulation and validation by rapid-prototyping.

 The Main References:

[AouSaaUML02] : N. Aoumeur, G. Saake, "Integrating and Rapid-prototyping UML Structural and Behavioural Diagrams Using Rewriting Logic". In Proceedings of the 14th International Conference on Advanced Information Systems Engineering (CAiSE 2002, Toronto, Canada), A.B. Pidduck and J. Mylopoulos and C.C. Woo and M.T. Ozsu (editors), Lecture Notes in Computer Science, Volume 2348, pages 296-310, 2002.

7. From Legacy Systems to Web Services - Dr. Mohammad El-Ramly

Web services is the hottest trend in business application integration. The World Wide Web consortium (W3C) defines a Web service as: "a software application identified by a URI, whose interface and bindings are capable of being defined, described and discovered as XML artefacts. A Web service supports direct interactions with other software agents using XML-based message exchange via Internet-based protocols." 

The online technical dictionary Webopedia.com defines Web services as: "a standardized way of integrating Web-based applications using the XML, SOAP, WSDL and UDDI open standards over an Internet protocol backbone. XML is used to tag the data, SOAP is used to transfer the data, WSDL is used for describing the services available and UDDI is used for listing what services are available. Used primarily as a means for businesses to communicate with each other and with clients, Web services allow organizations to communicate data without intimate knowledge of each other's IT systems behind the firewall. Unlike traditional client/server models, such as a Web server/Web page system, Web services do not provide the user with a GUI. Web services instead share business logic, data and processes through a programmatic interface across a network. The applications interface, not the users. Developers can then add the Web service to a GUI (such as a Web page or an executable program) to offer specific functionality to users. Web services allow different applications from different sources to communicate with each other without time-consuming custom coding, and because all communication is in XML, Web services are not tied to any one operating system or programming language." 

On the other hand, software legacy systems are the backbone for computing services in many organizations, with years of investment and proven reliability. With every new computing revolution, IT industry and research have to invent methods for leveraging  legacy systems with the new technology. With the advent of PC's, emulators were invented to access legacy systems. With the advent of window systems, graphical emulators came followed by screen scraping to dress up legacy screens. With the advent of CORBA and distributed objects, focus shifted to objectifying legacy systems, i.e., wrapping their services as objects. With the advent of the Internet, a lot of work was done to Web-enable legacy systems. With new trends in programming languages or new versions of older languages, source code transformation gets attention. Web services are no exception. A lot of useful business services are residing on legacy applications and wrapping them as Web services, brings the best of both worlds together.

In this project, the student will explore how legacy systems can migrate to Web services. In other words how the services of a legacy systems can be decomposed and offered as Web services. Of particular interest is:

• Surveying the current work on migrating legacy systems to Web Services and the methods used for the migration. 

• Studying and possibly implementing a proof of concept prototype for lightweight wrapping of legacy user interfaces as Web Services. This would benefit from lightweight wrapping technology, e.g., screen mapping, to wrap some legacy system service(s) of interest as Web services. 

However, as Web Services technology is still at infant-to-toddlers stages and I am myself new to Web Services, there is amble room to jointly define the project with the interested student and tailor it to his/her interest. 

References

[ACKM04] Gustavo Alonso, Fabio Casati, Harumi Kuno, Vijay Machiraju, Web Services: Concepts, Architectures and Applications, Springer Verlag, ISBN 3-540-44008-9, 2004.

[Elr03] Mohammad El-Ramly, Reengineering Legacy User Interfaces Using Interaction Traces, Ph.D. Thesis, university of Alberta, Canada, 2003. Publications from the thesis are available here.

[Vog03] Werner Vogles, Gustavo Alonso, Web Services Are Not Distributed Objects, IEEE Internet Computing, Nov.-Dec. 2003.

[KE02] D. Kuebler and W. Eibach, Adapting legacy applications as Web services, Technical Article, developerWorks newsletter, IBM Corporation, Jan.-Feb. 2002 .

8. Multi User Dungeon: A Mobile Game - Dr. Piotr Kosiuczenko

• Sequence Diagrams for Mobility (SDM)
• Activity Diagrams for Mobility (ADM)
• Homepage von Jade (Downloads and Documentation)
• Java MIDP
• MID Description

Two different platforms can be used for implementing this game: an Agent Platform like JADE and the Micro Java Platform. In the first case, the student should know the basic features of the Agent Platform and be able to write programs for this platform.

In the case Micro Java Platform, basic knowledge of and the ability to write programs for this platform are required. In this case also two different projects are possible: a project devoted to mobile platform implementation and a project devoted to the game itself. These two projects require close cooptation.

9. Online Java Automatic Knowledge Test Framework - Dr. Piotr Kosiuczenko  

The goal of this project will be to design an automatic test framework. The MSc candidates will be asked to do some Java-programming exercises and submit their answers online. The submitted programs will be compiled and, if syntactically correct, tested. For the testing, JUnit will be used. JUnit displays the number of failures and errors found. Candidates will repeat their solutions until they manage to submit a correct one, or of their chose to proceed to the next exercise. At the very end of the test, the test system will advise student to read more or less advanced stuff, depending on his/her performance. The diagnosis should be based on performance (time spent, number of questions answered) and multiple-choice questions. The system should be safe, i.e. it should disallow execution of dangerous programs. The project will focus also on ways of ensuring safety.

10. Imaging Fabrics for E-commerce - Proposed by Mick Sharpe

Project Allocation and Second Marking

Students Presentations and  Preliminary Reports

Student Presentation:

• Presentations are rescheduled for May 10th at 1pm in the M.Sc. of SE lab.
• Each presentation will last for 10 minutes + 5 minutes for questios.
• Presentations are NOT marked for the project module. 
• But they ARE MARKED for the planning module. They carry 30% of the module mark. 
• Presentations are assessed based on: (1) Content (2) Quality of slides (3) Quality of delivery (4) Handling of questions.  
• It is REQUIRED that students do a professional presentation using power point or similar software. 
• Presentations are scheduled according to the alphabetic order of the first name:

1. 1:00 - 1:15 A...
2. 1:15 - 1:30 J...
3. 1:30 - 1:45 M...
4. 1:45 - 2:00 N...
5. 2:00 - 2:15 W... 

Preliminary Report:

• This report is NOT marked for the project module.
• IT IS MARKED for the planning module. It is worth 70% of the planning module mark.
• We expect to see in the report:

  1. Clear objective and technical specification of the project.
  2. Any background material, e.g., brief of relevant work, summary of introductory material, draft software requirement specifications if you are going to implement software, etc.
  3. A detailed plan and time table.
  4. Other relevant content to make a good report, e.g., TOC, Intro., Cover Page, References, Glossary of important terms if needed, etc.

Interim Report 1 (5%)

• The report is due at 4:00 pm on  Friday, 9 July 2004.
• It should be handed to Dr. El-Ramly or to the main office to put in his mail slot.
• This should include:

  1. A clear description of the project aims and objectives and how they will be measured, e.g., this can be the test suite for passing a software system, if your project implements one.
  2. The detailed specifications of the project. If you are implementing a software system, you should describe clearly with enough details what functionality your system provides. This can be in any notation you see suitable, including plain English. 
  3. A detailed plan for achieving the project objectives.
  4. Any other relevant information.

• There is no minimum length for the report. We recommend not exceeding 10 pages of core content. Generally, try to express the required content in the least number of words; i.e., the shorter the better as long as it conveys the message.

Interim Report 2 (5%)

• The report is due at 4:00 pm on Monday, 9 August 2004.
• It should be handed to Dr. El-Ramly or to the main office to put in his mail slot.
• This report is a progress report. It should include:

1. A clear description of what progress has been made to achieve the project objectives and what is still to be done.
2. An updated version of your plan that describes what activities were added, deleted, shortened and/or  extended and why.
3. The TOC of your thesis
4. Any other relevant information.

• There is no minimum length for the report. We recommend not exceeding 10 pages of core content. Generally, try to express the required content in the least number of words; i.e., the shorter the better as long as it conveys the message.

Thesis and Viva

• The dissertation is due at 4:00 pm on Friday 10, Sep. 2004.
• It should be handed to Dr. El-Ramly or to the main office to put in his mail slot.
• Three bound copies of the dissertation must be submitted. If the student has more than one supervisor, then an extra copy must be submitted for every additional supervisor (e.g., a student that is co-supervised needs to submit 4 copies) 
• The dissertation should not exceed 15,000 words, excluding program code and documentation and user manual, if any.
• The dissertation must be written in good English. It must be prepared in a document typesetting system and must be laser-printed on A4 paper.
• Each copy should include an attached CD with:

1. A electronic copy of the dissertation 
2. A copy of the source code of the software developed, if any.
3. An installable or executable copy of the software that is ready to run.
4. A copy of any technical documentation and/or user manual of the software, if any.

• Dissertation content and structure should be discussed with the supervisor, but generally, each dissertation should include a description of the following aspects of the project:

1. A declaration of originality as shown below..
2. An abstract and table of content.
3. The technical background of the work, including appropriate references to the technical literature.
4. Specific objectives of the project.
5. Detailed specification of the software produced, if any.
6. The technical contribution of the project, including experimental and/or theoretical results.
7. Conclusions; including overview of what has actually been achieved by the project, changes in the plan from the original one and the reasons, interpretation of the results, and suggestions how the project could be further extended.
8. A list of references.
9. Appendices if required.

• The supervisor will read and comment on a draft of a student's dissertation provided that this is produced sufficiently in advance of the deadline for final submission. The supervisor may comment on technical adequacy and style of presentation.

• Each student will be required to attend a viva for his/her project to better inform the markers of his work and demonstrate his/her software, if any. Students will informed of the date and time of their viva soon.

• DECLARATION: All sentences or passages quoted in this report from other people’s work have been specifically acknowledged by clear cross referencing to author, work and page(s). I understand that failure to do this amounts to plagiarism and will be considered grounds for failure in this module.

Student Viva Schedule

• The purpose of the viva is to help the project markers better understand the project, appreciate the effort the student put in it, and ask any questions they have. 
• The duration of the viva is 45 minutes approximately. 
• The format of viva is: 

  10 min student's introduction to the  project

  10 min software demo if any

  25 min for questions