On Final Presentation and Midterm Report

Posted: 2015-09-10 18:23:18 +0800

Final Presentation

The dates for final presentation have been shifted forward to 17 November and 18 November, Tuesday and Wednesday, during the reading week. Your examiners include A/P Leow Wee Kheng, Dr. Anand Bhojan, Dr. Bimlesh Wadhwa, and Dr. Damith Rajapakse.

Since these dates are usually reserved for UROP and FYP presentation, if any of you are going to give your final UROP/FYP presentation this semester, please let me know (even if you do not know your actual presentation time yet).

Read more..


Software Architecture and Design

Posted: 2015-09-03 21:09:42 +0800

If your team already has sufficient ideas about what to implement for your project, it is now time to think about how to implement it. This step is where you plan your implementation details, from what are the major components of the system, what languages/libraries/frameworks/databases to use, what algorithms/data structures to use, what the UI would look like, what are the key classes in your system, etc. You may even start a small prototype to explore the options you have.

Read more..


Thinking About Security

Posted: 2015-08-27 19:34:07 +0800

Instead of going through another past project, I decided to change the lecture plan so that I can address something that I observe during the work sessions so far. There is a lack of consideration on security when you capture the software requirements

I mentioned passing penetration tests as a verifiable non-functional requirement. But building a secure system is more than meeting non-functional requirements. Some functionalities have to be included into the system to ensure the security of the system. Security is not a feature. It is a property that emerges after sufficient number security-related mechanisms are implemented.

Read more..


On Software Requirements

Posted: 2015-08-20 23:38:00 +0800

In this week’s lecture, we will talk about gathering and documenting software requirements. Here are the outlines:

Introduction

  • The user requirements specify what your end-product can do / what the customer wants
  • Functional / non-functional requirements
  • Many tools for requirement gathering:
    • brainstorming
    • user survey
    • observation
    • interviews
    • focus groups
    • prototyping
    • analyzing related software
  • Use whatever tools suitable for your project

Read more..


Sample Requirements C

Posted: 2015-08-20 23:37:00 +0800

This sample is taken from a past CS3283/4 project.

System Y is a software system project aiming to provide historians, history hobbyists, teachers, students as well as casual internet users a friendly and easy-to-use platform where users can create and browse well-visualized historical data in a unique way powered by modern web technologies.

Read more..