Assessment Weighting:
Project Proposal & Plan 0%
Phase I (Project Planning, Initial knowledge acquisition) 5%
Phase II (Problem Modeling & System Design) 15%
Phase III (Implementation & Results) 25%
Final System (Functionalities & results demo) 35%
Peer Assessment 20%
TOTAL 100%
Phase 0, 1, 2 done
Phase 3 deliverable is as follows:
3.1 Final Project Report (2 hardcopies) 10%
YB
Henry
Ryan
These are the sections under the report. Refer to the color codes for individual tasks. I have also copy
and paste the guides for each session from the original pdf for ease of reference.
DISTRIBUTION LIST
ACKNOWLEDGEMENTS
TABLE OF CONTENTS
EXECUTIVE SUMMARY
Problem Definition
Project Scope & Objectives
Benefits & Costs
Findings & Recommendations
1.0 PROBLEM DEFINITION
1.1 PROBLEM DESCRIPTION
1.2 PROJECT SCOPE & OBJECTIVES
1.3 BENEFITS AND COSTS
1.4 SOLUTION OUTLINE
2.0 KNOWLEDGE ACQUISITION & MODELLING, PROBLEM ANALYSIS
2.1 KNOWLEDGE ACQUISITION
2.2 KNOWLEDGE MODELLING
Describe and include the results of your problem analysis (ie. the modelling diagrams) where appropriate.
From your knowledge modelling results, how do these translate to System Design?
3.0 SYSTEM DESIGN
3.1 OPERATIONAL CONTEXT
3.2 FUNCTIONAL DESCRIPTION
3.3 USER INTERFACE DESIGN
Describe the user interface design. What user characteristics did you consider in the design? (Appendix:
full user guide). How does the design facilitate the consultation process?
What is the purpose of the interface? Who are the users? How does the interface facilitate the use of your
system/experimental results?
3.4 KNOWLEDGE STRUCTURE & REPRESENTATION
Describe the natural or basic structure of the knowledge to be incorporated into the system. (Appendices:
KA documentation such as concept dictionary, CommonKADS expertise models etc). Eg. if mathematical
models were used, why were they appropriate?
Describe the techniques (eg. learning or vision techniques), synthetic or intermediate structures, models
or transformations, if any, that you created, imposed or performed on the knowledge elicited (Appendices:
detailed knowledge modelling diagrams, if appropriate). Why was this approach chosen?
Describe the final knowledge representation schemes chosen, and explain your choices.
3.5 PROBLEM SOLVING PARADIGM
Describe the problem-solving paradigms and processes adopted or performed by the system, including
specifications of all algorithmic components, inferencing and metacontrol
mechanisms (Appendices: Task and Inference Knowledge.).
3.6 TECHNICAL ARCHITECTURE AND DESIGN
3.7 HARDWARE & SOFTWARE
4.0 IMPLEMENTATION AND RESULTS
4.1 IMPLEMENTATION
Give top-level overview of rules (if appropriate) or other knowledge representation formalisms, search
algorithms, decision-making algorithms, matching and retrieval algorithms (if CBR system), etc.
4.2 RESULTS/ VALIDATION & VERIFICATION
Describe your plan and procedures for validating and verifying the system, identifying specific steps or
stages (Appendices: detailed test plans, sample test cases and expected results). Be sure to explain how
the experts and users of the system fit into your plan.
Give the results of your validation and verification plan for the prototype or experimental results (if the
project involved experimental application or verification of KE techniques). Was it adequate? What
additional validation (if any) have you performed? (Appendices: detailed test results).
Describe the use of any special tools or techniques in the testing.
How were the objectives of completeness and consistency addressed in your testing?
What policy does the system adopt in dealing with inadvertent attempts to exceed its scope (ie. how
gracefully does it degrade)?
How were experimental results validated? Has the prototype/experimental result been used/reviewed by
the final users, if yes then how many users and for how long. What were their reactions? Describe these
user sessions, ie. how many cases, situations, etc. did they consider? Give figures and results wherever
possible. External validation of the prototype or experimental results must be provided. Describe the plan,
process and results of that validation.
Has the prototype been used by the experts, if yes then how many and for how long. Describe these
expert sessions, ie. how many cases, situations, etc. did they consider? Give figures and results
wherever possible. Compare the system’s performance against that of the experts (or other oracle).
What remedial actions were required as a result of the testing? Were there any major design changes
required? On hindsight, how could these have been avoided?
5.0 FINDINGS AND RECOMMENDATIONS
5.1 PROJECT MANAGEMENT
5.2 RESULTS
To what extent has the prototype/experiment succeeded in demonstrating the technical, operational and
financial feasibility of the eventual system/results? What changes in scope or functionality will be
necessary?
Discuss the anticipated organisational impact of the eventual system and any, organisational changes or
adjustment which need to be made to accommodate it.
Describe what the experimental results suggest; and describe follow-up experiments on feasibility of
developing a system based on those results.
Provide a high-level, tentative schedule for the implementation of the delivery system.
Estimate each of the following for the eventual system:
(1) Development manpower and duration, include developers, experts and users’ time.
(2) Hardware and software requirements and costs.
(3) The size of the eventual system (in terms of number of rules, premises, conclusions, frames, memory
requirements, etc.).
(4) Other costs.
(5) Risks, both technical and organisational.
What other recommendations or follow-up activity could you suggest at this stage?
5.3 CONCLUSION
6.0 REFERENCES
APPENDICES
3.2 Technical Paper (3 hardcopies) 5%
The Technical Paper (stapled together) is a summary of the whole final report, and the content/format is
like any typical journal paper, approximately 8-10 pages, single spacing, Times Roman font and, font size
12.
3.3 KBS System (softcopy) 35%
- installation and user guide
This is a approximate guide to the marks distribution of the 35% for Research project:
• Complexity of problem 20%
• Innovativeness 50%
• Application of Methodology & Results 10%
• Programmiing 20%
3.4 Softcopies of all the above on a CD
3.5 Give Final Presentation to ISS and conduct a Live System Demo 10%