4th Week: Design Document

For this week, I was unable to attend the class because I went to my hometown in Terengganu. But I manage to catch up with my group members about the topic that the class discussion this week - Design Document. After all, what is design document is about?

From my search in Wikipedia, design document can be defined as...

• A written description of a software product, that a software designer writes in order to give a software development team an overall guidance of the architecture of the software project.
• usually accompanies an architecture diagram with pointers to detailed feature specifications of smaller pieces of the design.
• required to coordinate a large team under a single vision.
• needs to be a stable reference, outlining all parts of the software and how they will work.
• is commanded to give a fairly complete description, while maintaining a high-level view of the software.

And in my personal point of view, design document provide a platform or guidlines for the courseware developer to implement their project to meet the specific objectives

Regarding our courseware project, we have a discussion to construct our design document for our project. the most important part is to know what theory and strategies to be applied in the coursware to meet to objective and the needs.

The design document format are as below: