The student will be required to choose one out of four system specifications or any system of interest and must be discussed with tutor. To meet the marking criteria for the course-work all systems must have extensive well written documentation of the following elements: 1. Use of object-oriented analysis, design and implementation of classes obtained 2. Use of use case analysis to determine system requirements 3. Use of activity diagrams to model system behaviour and specific system outcomes. 4.
Use of sequence diagram to demonstrate implementation system component interaction 5. Use of a class relationship diagram that reflects outputs of the use case, activity and sequence diagram 6. Use of wireframe models and/or package diagrams 7. A text user interface should be implemented for the system using the ncurses library 8. The use of low-level algorithms, programs, functions, pseudocode and flowcharts. 9. Unit tests should be written for a minimum of 5 functions within the program. 10.Working functional and appropriately commented program that demonstrates a direct implementation of the system design
Question is : Tic Tac Toe game The program should allow a user to play a game of tic tac toe against the computer. The user should be able to select 3 modes of game play easy, intermediate and hard. For the easy mode, the computer will place moves randomly on the board. For the intermediate mode the computer will also place moves randomly on the board but prioritize blocking the users win moves. For hard the computer will play with the aim to place winning moves on the board based on a random selection of winning sequences.
Marking Criteria • UML Diagrams: This includes any diagrams or documents that you have produces to plan and understand your system. You may have employed flow chart diagrams for each activity/function of your system, produced a use case, activity and sequence diagrams. These must be well documented to show the reasoning behind each element in the diagram.
In order to produce a solution to this problem you are strongly encouraged to apply techniques of analysis in order to break the problem down into manageable and solvable elements. These will involve both high-level systems and subsystems and low-level methods and sub procedures involving pseudocode algorithms and flowcharts. [50%]
• Functionality:
This criterion focuses on the extent to which your project achieves what it is required to do, and the way by which it goes about doing it. The implementation must be object-oriented involving multiple related classes to implement the software designs and all the functionality which are described in the specification brief.
• Documentation: This criterion considers the degree to which your assignment gives the impression of a coherent, thoughtful, thorough and sustainable project. Consistency throughout the project in terms of your visual approach, your use of terms and the linkage between the statement of goals in your planning and their final realisation. This also includes in-code commenting and use of a consistent and readable coding style. [10%]
0 comments