Programming and Software Engineering CPT106

Select one out of the 4 projects on pages 5-8.

System design and coding

(1) The project descriptions are deliberately given in the form of simple customer specifications , which (as in the real world) are incomplete and often ambiguous, rather than a set of exact functional specifications. The group members should work methodically together (as the developers in a real-world software project) to:

iuww520iuww520iuww520iuww520iuww520iuww520iuww520iuww520

 Analyse and formalize the customer specifications on pages 4-7 (at this stage, the various design choices and the software features can be subject to the group’s creativity). This should be different from customer supplication, which should clearly state the features of the delivered system.

 Apply objected-orientated design methodology (encapsulation, inheritance and

polymorphism, if needed) , design and decompose the programmatic aspects of the problem using classes, and allocate constituent development tasks to each group member.

 Implement the product with frequent meetings to report progress and decisions to each other and re-evaluate the agreed courses of action.

 Implement test procedures, debug and correct the product.

 Finalize the deliverables.

(2) The given customer specifications on pages 5-8 are only basic, and most of the design choices should be decided in the group meetings. The systems described within the different projects have a variety of different features, and the disambiguation of thecustomer specifications can be based on the student’s logic and real-life experience.

(3) Prioritization for the implementation of the different parts of the system is the group’s decision; however, for the purposes of demonstration and testing, those parts that manage and populate the file stores with data such as customers’ details, for instance, are necessary

(4) You should install the Github plugin component (third part component) in Visual Studio to share, manage and maintain your source code and documents with members in the group.

report

(1) The SDP report should clearly state all the features implemented and the hierarchical chart of your programme. It is better to have a few features fully working without run-time crashes than all features with many bugs without working properly or causing disrupting ripple effects to other subsystems.

(2) In any case, any related decisions and compromises should be included in the report. The required testing procedures should simply take into account the input of each subsystem and what the output or operation of the software is supposed to do.

(3) The Github link should be listed at the end of your report. All the source code and related documents in the Github repository should be shared publically so that the we could check if

Github is used in your project.

Assessment

Assessment will be based on whether the product offers reasonable functionality and features, its design quality, flexibility, software bugs, and other stated deliverables.