Assessment

1.1 Requirement Specification for Sub system

1.1.1 Requirement Elicitations

1.1.2 List of FR/ NFR (Common Elements) /w priority

Trend of hotel web technologies

- Chatbot
- Link with non-hotel bookings, e.g. car, flight or local tour

Check with
- OAuth
- API
- Framework

2 Conclusions

2.1.1 References (Mazen)

Learning Outcomes

Knowledge & Understanding:

1. Plan appropriate requirements, design and implementation strategies and methods for the development of a significant computing product related to your programme of study (including consideration of commercial, economic, legal, ethical, social and professional factors)

2. Critically apply a well-integrated requirements, design and development methodology to a computing problem

Intellectual / Professional skills & abilities:

3. Develop a significant computing product using industrial standard development tools and techniques (including those related to information security) including the application of the required project management and team working skills

4. Apply appropriate quality assurance techniques and work to appropriate professional standards for documentation, quality control and product integrity

Learning outcomes are assessed throughout this assessment.

Further information
It is expected that most, if not all demonstrations will be held during class time but, if necessary, an alternativetime/s will be arranged.

You will submit a zip file containing:
a. All the files of the system your group constructed
b. Sufficient installation instructions to enable the re-installation of your product
c. A readme document containing relevant system details. For example the newnumyspace URL of the system and any passwords/usernames needed to use the system. The password to the newnumyspace account is NOT required.
d. YourTerms of Reference

Assessment

1 Implementation of individual specified functions
Comprehensiveness of implementation of the prototyped functions specified in the requirements specification derived in previous phase, including any enhancements based on feedback received for your terms of reference.

2. Quality and Robustness of Prototype
Error handling, user validation and robustness of prototype functions; this should be demonstrated across the scope of the individual component. To obtain full marks you must have provided a fluent implementation of the full scope of your element.

3. Demonstration structure, understanding & responses to questions
Structure and clarity of demonstration; understanding of the work done; quality of responses to questions about the prototype. We expect you to demonstrate professionalism by being punctual, using appropriate language and respect for your audience and team members and measured responses to questions.

4. Quality and Consistency of System Integration

Comprehensiveness of system integration and consistency of the whole system. You will not be penalised for incomplete individual sub-components. Additionally if there are group issues please inform the module team at the earliest opportunity.

Report - Tasks

A critical evaluation document should be produced which details the entire system, the group effort and your individual input to the application, the ways in which your work dealt with the issues of professional practice and quality, and how decisions made elsewhere impacted on your own decisions. This will depend on the nature of the responsibilities you undertook. You must produce areport that provides a critical evaluation on the system implemented and the tools/techniques used to facilitate the implementation.

Each group member must also submit relevant copies of the minutes of the formal meetings held as an appendix to the main document. These will enable you to comment on the group work process, the decisions that were made and your particular role in the project - please refer to your Terms of Reference and meeting minutes.

Examples should be used throughout to support each section. Evidence should be provided to support your claims and statements - use appendices appropriately to support your work. Reference should be made to meeting minutes submitted in the document's appendix to show when key decisions were made, when issues were discussed and when/how tasks were assigned.

NOTE this document is not:
a. A description of what happened
b. A blame finding exercise / witch hunt
c. We are great us - didn't we do well!
d. A collection of unjustified views

Attachment:- Group.zip