Please enable JavaScript.

Coggle requires JavaScript to display documents.

Expert System Lifecycle (ES Life Cycle (A detailed life cycle model:…

- - - - Comment on Phase 1:
        ◦ it's important to discover what problem/problems the client expects the system to solve for them, and what their real needs are. The problem may very well be that more knowledge is needed in the organisation, but there may be other, better ways to provide it.
        ◦ 'Management issues' include availability of finance, legal constraints, and finding a 'champion' in top management.
    - - Comment on Phase 2:
        ◦ the 'conceptual design' will describe the general capabilities of the intended system, and the required resources.
        ◦ The problems of selecting software, and finding a domain expert (and persuading him/her to co-operate) have been discussed in the last two lectures.
    - - Comments on Phase 3:
        ◦ Comments: See below on the question of what exactly this prototype is used for.
        ◦ It's important to establish the feasibility (economic, technical and operational) of the system before too much work has been done, and it's easier to do this if a prototype has been built.
    - - Comments on Phase 4:
        ◦ See below on the question of how the knowledge base, as constructed, relates to the prototype.
        ◦ The evaluation of an expert system (in terms of validation and verification) is a particularly difficult problem.
    - - Comments on Phase 5:
        ◦ If the system is not accepted by the users, the project has largely been a waste of time.
        ◦ Field testing (leading to refinement of the system) is essential, but may be quite lengthy.
    - - Comments on Phase 6:
        ◦ A person or group of people must be put in charge of maintenance (and, perhaps, expansion). They are responsible for correcting bugs, and updating the knowledgebase. They must therefore have some knowledge engineering skills.
        ◦ The system should be evaluated, once or twice a year, in terms of its costs & benefits, its accuracy, its accessibility, and its acceptance.
- - - - Major increment – assistant level :arrow_forward: colleague level :arrow_forward: expert level
        
        Minor increment – expertise within each level
        
        Microincrement – add/refining individual rules
- - - - Three (3) main issues that must be considered
        
        ◦ Is a knowledge-based technique suited?
        
        a) Is human problem-solving knowledge being replicated in the solution of the problem?
        b) Is the problem-solving knowledge heuristic in nature or is it predominantly algorithmatic.
        c) Does the knowledge or expertise periodically change or does it remain constant
        d) If the expertise is involved, is the expertise well understood and accepted?
        e) Are the input data always complete and correct?
        f) Can the problem be solved through other means?
        
        ◦ Is a knowledge-based approach justified?
        
         The cost of developing a knowledge based system is higher than a conventional programming due to specialized software.
         There is a need for experienced personnel.
         Problem tend to be too complex thus it defies practical solution through a knowledge-based system
        
        ◦ Does a problem exists?
        Does the problem bring a significant impact to the company.
    - - Is there management support for the project?
         Availability of time
         Tools and training
         Expert availability
      - Is there support from the expert?
         Is the Expert Competence
         Is the Expert Articulate
         Is the Expert in Physical Proximity/Availability.