It's UWAweek 19

help4401

This forum is provided to promote discussion amongst students enrolled in CITS4401 Software Requirements and Design.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying selected article
Showing 1 of 65 articles.
Currently no other people reading this forum.


SVG not supported

Login to reply

👍?
helpful
6:20pm Wed 19th Apr, ANONYMOUS

Hi, I watched the recording from today where you went through the take home test and wanted to ask about two question. The use case diagram (q3) and the two non-functional requirements (q5). Q3. In the lecture you mentioned that HatsOff is an actor. Creating UML diagrams can be subjective and in this case I don't fully agree with HatsOff being an actor depending on how the system is defined. From what I understood of the case study, the chatbot requires HatsOff to function, so in this sense the system can be considered to be made up of the chatbot+hatsoff. Also from what I've searched, API's can be considered part of the system and in this case a HatsOff API was being used. Not sure about others, but I specified the system was made up of the chatbot and hatsoff but was deducted marks. Q5. I, probably like many others said Security and Privacy for this question. I understand your reasoning for saying Backup as a non-functional requirement and I agree it would be relevant for the system, however, for this question I don't believe it is more important than privacy or security, or at least not important enough to deduct any marks if it wasn't stated. The question states that the data will be sold off to identify people. A backup can prevent loss of data, but it can't prevent 'selling the data and identifying people' which is the main point of the question. Not being able to sell or access unauthorised data = security. Not identifying people = privacy. Thanks

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy