help5501

It's UWAweek 42 (2nd semester, week 12)

help5501

This forum is provided to promote discussion amongst students enrolled in CITS5501 Software Testing and Quality Assurance. If posting a question, it's suggested you check first whether your question is answered in the unit Frequently Asked Questions (FAQ) list, and use the search box (on the right) to see if an answer to your question has already been posted.

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.

Note that any posts must comply with the UWA Code of Conduct and the UWA Academic Conduct Policy. That means you should (a) treat everyone with respect and courtesy, and (b) not post your solutions to an assessment that's in progress.

If asking a programming question, it's recommended you read How do I ask a good question? If reporting or troubleshooting a bug in software used in the unit, it's recommend you read How to report bugs effectively.

Displaying the 3 articles in this topic

Showing 3 of 143 articles.
Currently 85 other people reading this forum.

UWA week 39 (2nd semester, week 9) ↓

project Domolect 1.7 (all 3)

12:59pm Fri 27th Sep, ANONYMOUS

In Domolect 1.7, there are no definitions of <number> and <location>. So do I need to define the non-terminals <number> and <location> in task 1?

project Domolect 1.7 (all 3)

2:50pm Fri 27th Sep, Arran S.

ANONYMOUS wrote:

> In Domolect 1.7, there are no definitions of and . So do I need to define the non-terminals and in task 1?

Hi,

No, you don't. As the project spec says, you can just assume that they are available, and for testing purposes are considered to have just one production.

If using the BNF playground - which doesn't permit undefined non-terminals - I suggest just defining them with some placeholder string.

Cheers

Arran

UWA week 41 (2nd semester, week 11) ↓

project Domolect 1.7 (all 3)

10:20am Fri 11th Oct, ANONYMOUS

"Arran Stewart" [email protected] wrote:

ANONYMOUS wrote:

> In Domolect 1.7, there are no definitions of and . So do I need to define the non-terminals and in task 1?

Hi,

No, you don't. As the project spec says, you can just assume that they are available, and for testing purposes are considered to have just one production.

If using the BNF playground - which doesn't permit undefined non-terminals - I suggest just defining them with some placeholder string.

Cheers

Arran

Hi Arran,

Is your statement above still valid? (since this statement is before the project description update). I still confuse about the , as there is no statement in the project description that ask us to assume. The only statement about is:

"Commands can optionally start with a location, which isn’t defined in the grammar".

And if we don't define the grammar for , it will conflict with task 1 description "Your grammar should use the notation accepted by the BNF playground. It must be in plain text which could be pasted into the BNF playground and compiled without error.".

Last question: if your statement above "No, you don't. As the project spec says, you can just assume that they are available, and for testing purposes are considered to have just one production." still valid, do we have to write assumption in the answer or we don't have to? As your statement is already stated in the help forum.

Thank you,

Regards

help5501 articles all ANNOUNCEMENTS recent articles login to post a new article tagged articles (118 / 209) the unit in general (3) lectures (9) labs (16) project (65) final exam (7) tests and quizzes (18) help5501 topics from today and yesterday from the past week from the past two weeks ALL topics, most recent first	login chapter0 unitinfo research projects csforum csse-feedback csbreakdown cssubmit csmarks 2nd semester help fora Algebra Advanced Algorithms Cloud Computing High Performance Computing Intelligent Agents Professional Computing Relational Database Management Systems Systems Programming