Subject Code and Name CMP1041 – Foundation Programming
Assessment Number 2
Assessment Title Pseudo Coding and Flowcharting
Assessment Type Report
Length or Duration Four (4) Tasks / 1 File
Subject Learning Outcomes SLO 2, SLO 3, SLO 4
Submission Date / Time Week 8
Weighting 30%
Assessment Purpose
Software development companies have engineering employees with different levels of expertise, i.e. from junior engineers to senior engineers. Junior engineers may be given projects that are outside their ability to achieve, and thus receive help from more experienced engineers.
In this assessment you work as a senior engineer for a security software company that has a new client. A junior engineer was assigned to this client however has been struggling with the more complex parts of the software. Part of your role as a senior engineer at the security software company is to help the junior engineer in providing non-buggy software for the client.
Assessment Task / Item
For this assessment, you must submit a pdf file that contains your final solutions to the following four tasks.
Assessment Instructions
Read each of the following four (4) tasks and write your responses in the form of a report. The report will be submitted as one (1) pdf file.
Hi senior engineer! As a junior engineer I am struggling to finish the following four tasks. I’ve attempted each of them at least a little bit before getting stuck! I would greatly appreciate your help with these tasks!
Task 1
The client wants to add security tag readers to doors that allow employees to scan their security tag and if they have the security level appropriate to access the door, they can progress through the door. If they do not have the appropriate security level, security will be alerted with the employee’s name and the door will be locked down – not allowing anyone to enter until the door has been reset by security.
Doors are given a security level from 1 to 3, where 3 is the highest security level, and 1 is the lowest. Employees are also given a security level from 1 to 3. An employee with a security level of 1 can access all doors that also have a security level of 1. An employee with a security level of 2 can access all doors that have a security level of 1 or 2. An employee with a security level of 3 can access all doors that have a security level of 1 or 2 or 3.
I’ve finished a flowchart, but as a junior I am unsure if it has bugs! Can you please identify any syntax, logic, and runtime errors in the flowchart and do the following:
i) Identify the flowchart node that has the error. ii) Provide a flowchart node that fixes the error. iii) Provide information about what the error was.
Task 2
The client wants to be able to upgrade an employee’s security level, so as the employee receives a promotion they can access new areas.
An employee may upgrade another employee’s security level only if the upgrader (the employee upgrading another employee) has a security level at least one security level above the upgradee (the employee being upgraded). That way an employee with a security level of 2 can upgrade an employee with a security level of 1 to a security level of 2, but is not able to upgrade an employee of security level 2 to a security level of 3. In the case where the employee does not have the correct security level to upgrade another employee, security should be alerted with the names of both of the employees.
As a junior engineer I was unsure how to achieve this, but I have started a flowchart. Could you please finish the flowchart, using appropriate tools that will create presentable flowcharts, so that I can implement this within a programming language.
Task 3
The client wants to be able to downgrade all employee’s security levels, if the employee has a specific role. Only an employee with a role of Security should be able to downgrade all employee’s security levels based on their role.
For example the client decides that all employees with a role of Scientist should no longer have access to security level 2 rooms and wants to be able to downgrade their security level from 2 to 1. An employee with the role of Security will then execute this program to downgrade all employees security level’s with the role of Scientist. An employee’s security level should never be below 1. If an employee tries to execute this program with a role that is not Security then security should be alerted with the employee’s name.
Again, I was unsure how to achieve this, but I have started a flowchart. Could you please finish the flowchart so that I can implement this within a programming language.
Task 4
As a junior engineer, I intend on implementing the above programs in an Object Oriented Language, such as C++. Can you please help me get started by providing the properties and methods for the Employee class, to be used in my class diagram, that has all the properties and methods required for the programs above, specifically methods that allow upgrading or downgrading an employee’s security level easily would be great!
Submission
Export a document with the 4 tasks in a pdf format with the following naming convention:
[Student_ID]_[Surname]_[First Name]_[SubjectCode]_[Assessment_#].pdf E.g.: 1234_Singh_Visha_PRG1002_Assessment_02.pdf
You should take a screenshot or otherwise convert your flowchart to an image that should be contained within the pdf document.
Google Docs, Microsoft Word, and various other word processing applications can export/publish to the pdf format.
All work must be submitted via the LMS, in the assignments section appropriate to this brief. Please ensure the above mentioned submission date and/or time are adhered to, or penalties may apply.
For more information on late submission, please see the Assessment Policy.
Academic Integrity
The integrity of the assessment process is fundamental for ensuring appropriate evaluation at AIT. All work submitted should be your own, and where additional resources are used, they must be referenced according to the Harvard style. Additionally, TurnItIn is available in the LMS to test plagiarism in your writing.
For more information on academic integrity, please see the Academic Integrity and Academic Integrity Penalties Policies.
Appeals
Fair application of the assessment rubric, rules and guidelines should be administered for each assessment. If you feel an evaluation requires further consideration, you may be entitled to an appeal.
For more information on your right to an appeal, please see the Assessment Appeals Procedure and Policy.
Policies
For access to the policies mentioned above and related to education at AIT, please see the footer of the AIT website, and follow the link named Education Policies and Procedures.
Website: https://www.ait.edu.au
Assessment Rubric
Task Descriptor (F)
Fail (P) Pass (C) Credit (D)
Distinction (HD)
High
Distinction
Apply debugging processes to
meet project expectations
20% Fewer than two (2) of the following criteria are met. Other criteria are not included or poorly applied.
1. In the provided flowchart, half the errors are identified.
2. All identified errors are described with respect to the error type.
3. All errors have provided fixes. Two (2) of the following criteria are met. Other criteria are not included or poorly applied.
1. In the provided flowchart, half the errors are identified.
2. All identified errors are described with respect to the error type.
3. All errors have attempted fixes. All three (3) of the following criteria are met. Other criteria are not included or poorly applied.
1. In the provided flowchart, most errors are identified.
2. All identified errors are described with respect to the error type.
3. Most errors are fixed in an appropriate way. All three (3) of the following criteria are met.
1. In the provided flowchart, all errors are identified.
2. All identified errors are described with respect to the error type and how it impacts the program.
3. All errors are fixed in an appropriate way. All three (3) of the following criteria are met.
1. In the provided flowchart, all errors are identified.
2. All identified errors are accurately described with respect to the error type and how it impacts the program.
3. All errors are fixed in an optimal way.
Apply the process for the
implementation of algorithms
40% Fewer than three
(3) of the following criteria are met. Other criteria are not included or poorly applied.
All flowcharts:
1. Have correct inputs, and outputs, except in two (2) cases.
2. Uses variables with types.
3. Has less than three (3) significant logic errors.
4. Has less than eight (8) syntax errors. Three (3) of the following criteria are met. Other criteria are not included or poorly applied.
All flowcharts:
1. Have correct inputs, and outputs, except in two (2) cases.
2. Uses variables with types.
3. Has less than three (3) significant logic errors.
4. Has less than eight (8) syntax errors. All four (4) of the following criteria are met.
All flowcharts:
1. Have correct inputs, and outputs, except in one (1) case.
2. Have less than three (3) cases of redundant or inefficiently typed variables.
3. Have less than two (2) significant logic errors that cause runtime bugs.
4. Have less than five (5) significant syntax errors by using incorrect or inconsistent variable naming. All four (4) of the following criteria
are met
All flowcharts:
1. Have the correct inputs, and outputs.
2. Have less than three (3) cases of redundant or inefficiently typed variables.
3. Have no (0) significant logic errors that cause runtime bugs.
4. Have no (0) significant syntax errors by using incorrect or inconsistent variable naming.
All four (4) of the following criteria
are met
All flowcharts:
1. Have the correct inputs, and outputs.
2. Have no (0) redundant or inefficiently typed variables.
3. Have no (0) logic errors that cause runtime bugs.
4. Have no (0) syntax errors by using incorrect or inconsistent variable naming.
Complete a project according to design specifications
30% Fewer than three
(3) of the following criteria are met. Other criteria are not included or poorly applied.
All flowcharts:
1. Alert security is present in more than two (2) cases.
2. Some variables are present used in alerting security in more than two (2) cases.
3. Security level requirements are enforced in more than two (2) cases.
4. Range of security level is maintained in more than one (1) case.
Three (3) of the following criteria are met. Other criteria are not included or poorly applied.
All flowcharts:
1. Alert security is present in more than two (2) cases.
2. Some variables are present used in alerting security in more than two (2) cases.
3. Security level requirements are enforced in more than two (2) cases.
4. Range of security level is maintained in more than one (1) case.
Three (3) of the following criteria are met. Other criteria are not included or poorly applied.
All flowcharts:
1. Alert security at the appropriate places based on all possible security violations in all but two (2) cases.
2. Appropriate variables are present that are used in alerting security, such as employee names.
3. Security level requirements are enforced correctly in all but two (2) cases.
4. Range of security level is maintained, i.e. never below 1 and above 3 in all but one (1) case. All four (4) of the following criteria are met.
All flowcharts:
1. Alert security at the appropriate places based on all possible security violations in all but one case.
2. Appropriate variables are present that are used in alerting security, such as employee names.
3. Security level requirements are enforced correctly in all but two (2) cases.
4. Range of security level is maintained, i.e. never below 1 and above 3 in all but one (1) case.
All four (4) of the following criteria are met.
All flowcharts:
1. Alert security at the appropriate places based on all possible security violations.
2. Appropriate variables are present that are used in alerting security, such as employee names.
3. Security level requirements are enforced correctly.
4. Range of security level is maintained, i.e. never below 1 and above 3.
Apply appropriate tools and processes for generating
flowcharts and class diagrams
10% Fewer than two (2) of the following criteria are met. Other criteria are not included or poorly applied.
All flowcharts:
1. Use the correct flowchart nodes for the appropriate usage, except in six (6) cases.
2. Have less than five (5) missing arrows.
All Diagrams:
1. Use correctly spelled and Two (2) of the following criteria are met. Other criteria are not included or poorly applied.
All flowcharts:
1. Use the correct flowchart nodes for the appropriate usage, except in six (6) cases.
2. Have less than five (5) missing arrows.
All Diagrams:
1. Use correctly spelled and Three (3) of the following criteria are met.
All flowcharts:
1. Use the correct flowchart nodes for the appropriate usage, except in four (4) cases.
2. Have less than four (4) missing arrows.
All Diagrams:
1. Use correctly spelled and consistent variable, property, and method All four (4) of the following criteria are met.
All flowcharts:
1. Use the correct flowchart nodes for the appropriate usage, except in two (2) cases.
2. Have less than three (3) missing arrows.
All Diagrams:
1. Use correctly spelled and consistent variable, property, and method All four (4) of the following criteria are met.
All flowcharts:
1. Use the correct flowchart nodes for the appropriate usage.
2. Have no (0) missing arrows.
All Diagrams:
1. Use correctly spelled and consistent variable, property, and method names.
consistent variable, property, and method names, except in five (5) cases.
2. Flows from top to bottom, and all text is readable. consistent variable, property, and method names, except in five (5) cases.
2. Flows from top to bottom, and all text is readable. names, except in three (3) cases.
2. Are mostly well formatted and easily readable. names, except in three (3) cases.
2. Are mostly well formatted and easily readable. 2. Are well formatted and easily readable.
