Project Ideas: SE2-Software Design & Architecture
(CS446/CS646/ECE452) Spring 2011

Project Guidelines:

The term project reflects 40% of the total marks. This should be strongly considered when determining the scope of the project. Projects with low design complexity will be rejected. Remember the emphasis is on the architecture and the design part. Hence, these two aspects should be the main focus of the project. Implementation is important but it should not be the central focus. Remember to plan the implementation over various iterations. Implementing the first few iterations along with the complete iteration plan (for the whole project) will be sufficient for the implementation portion of the project.

The project does not have to be built from scratch. In fact it is encouraged to find an existing product and design a new feature/component for it.

Multi-team large scoped projects are also encouraged, where each team is focused on a given aspect of the overall application. Additional marks will be awarded to teams that can achieve interoperability.

Other considerations

• Usability
• Functionality
• Scalability
• Security & privacy
• Evolution
• Deployment
• Testing
• Development
• Project planning
• Time & cost estimation

Project Ideas:

Web-based Enterprise Applications:

• Policy based enterprise security framework adaptable to various layers (presentation, web-services, business, persistence etc).
  • Discover the security requirements of each tier
  • Define security policies. Different policies can be applied at runtime to get different levels of security
  • Should handle the security concerns (i)authentication (ii)authorization (iii)management
• Create an online Engineering log book. Researchers use paper based log books for various reasons. The electronic version of the log book should provide the same features. A wiki based log book might be interesting.
  I would also encourage you to explore other possible extensions that might be realizable in the electronic version of the log book when compared with the paper based log book.

GWT Application:

• Take an existing synchronous web application and convert it into a GWT asynchronous application
• JSP Wiki is a Java based wiki with somewhat clean code base. It uses a JSP based front-end on the browser. Create a GWT based front-end for it.

Extending other plugin based projects

• Create a plugin for Mozilla platform (Firefox/ Thunderbird)
• Create a plugin for Eclipse platform
• JSP Wiki is a Java based wiki with somewhat clean code base. It has a strong plugin based framework to extend/add new functionality. Creating new plugin to add additional functionality such as a wiki import/export feature.

Application specific communication protocol:

• Create your own communication protocol on top of TCP, UDP, SCTP.

  You will have to investigate the strength and weaknesses of these protocols and then justify your choice based on your application needs and requirements.

Mobile Application: (Blackberry/iPhone/Google Android application):

• Poker tournament director to organize and run poker tournaments. Utilize the capabilities provided on the device (such as the camera, Wifi, Bluetooth etc) to provide a functional experience for the players as well as the viewers. For example, all devices can communication over Wifi. One device can run the blind scheduler. All player devices can capture player hands and stream them to the viewers etc.

  Mobile applications should have a server side component or a P2P component. Special attention should be paid to concerns such as usability, security, communication, testing and deployment.

Games:

• Server based games
• Device based games

  All games should include the traditional components such as game design/level editor, AI (computer opponent), physics (collision detection/gravity) etc. Multi-player games are encouraged.

Past Projects: