CMP73010: Managing Software Development Assignment 2022

Running head: CMP73010 - MANAGING SOFTWARE DEVELOPMENT
CMP73010 - Managing Software Development
Name of the Student
Name of the University
Authors note

CMP73010 - MANAGING SOFTWARE DEVELOPMENT1
Part 1
Acceptance Testing
Scenario: The student wants to know what the acceptable formats that can be
submitted.
Acceptance criteria: The Acceptable format for different type of the assignments are
displayed such as different documents formats that includes (.odt, .doc, .docx, .pdf, .xlx).
For different other assignments such as .sql, .accdb, .html etc are displayed whenever
students try to upload any other file types that are accepted by the system.
Student submission time and dates: Student wants to know, the remaining time to
submit a specific assignment.
Acceptance criteria: The time is displayed in remaining hours and minutes from the
actual deadline for the assignment to submit.
The Time displayed must not be greater than actual deadline.
Notify Word-count
Scenario: Student wants to know the total word count in the submitted paper.
Acceptance criteria: The system should count all the words in the submitted file and display
the total count on the submission portal. If the required word count for an assignment is not
met then it will prompt an error displaying error message about the remaining word count for
the assignment.
Send a receipt of submission
Scenario: The student submits solution for an assignment to the system.

CMP73010 - MANAGING SOFTWARE DEVELOPMENT2
Acceptance criteria: The system should sent a mail to the registered mail id of the student
informing that the assignment is submitted to the system.
Draft submission of the assignment
Scenario: The student wants to check the draft solution with the professor.
Acceptance criteria: The system will have some specific button or container to which the
draft solution can be uploaded by the student for feedback from professor.
Upload of draft solution should not impact on the deadline displayed for the final and
complete solution.
Black box testing
As the black box testing is for the testing the functionality without having the in depth
knowledge of the internal logic. In this testing process specific knowledge about the code of
the developed application is not available to the tester. Consequently internal structure as
well as programming knowledge in general is not available. The tester of the application is
aware of the functionalities of the software needs to do but is not the way it completes the
functionalities.