You Have Been Asked By Your Manager To Create A User-Friendl

You Have Been Asked By Your Manager To Create a User Friendly Applicat

You have been asked by your manager to create a user-friendly application that will present a survey to your customers. The application will compile and analyze the results entered by the survey respondents. You will deliver your working application with a Design Document and test results. Upon completing all functional and design requirements, submit the following: Design document that has UML Class Diagrams to document your design of your Survey and SurveyConductor classes. UML Sequence Diagram that documents the design of your SurveyConductor application class. Screenshots showing results of testing. Update your Survey class based on feedback and lessons learned in all Phases of this course. Perfect your code and all comments to all necessary areas to describe what is happening at that point of your code. Zipped NetBeans project of the application that correctly meets all stated design and functional requirements. Code should be well commented. Appropriate use of control structures should be used. Logic should be sound and correct. A design document should be submitted that contains: UML Class and Sequence Diagrams using proper UML notation. Pseudocode for the SurveyConductor application. Pseudocode for the Survey class methods. Logic for error checking to validate the response is between 1 and 5 should be included in the pseudocode. Screenshots showing your application runs. Document each screenshot with a caption that explains the test data entered and the resulting application behavior/output. The second part of the Key assignment is a competency test that will assess your knowledge on fundamental data types, control structures, classes, objects, and methods. If you do not pass this competency exam, you will not be able to proceed to IT251. Declaring more than one method with the same name but different sets of parameters is called method overloading. You cannot overload a constructor. Given a method with the signature: public void numberCruncher(int num1, int num2, String name), an example call to this method could be: myNumberCrunch.numberCruncher("Fred", 3, 5). The + operator can be used in string concatenation. A static method can be used even if no objects of the class have been instantiated. A class or static variable should be used when all objects of a class must use the same copy of the variable. If packages are used, the package declaration should come directly after any import declarations in a java source file. The private access modifier can control the access to variables and methods of a class. An accessor is another term for a set method. Arrays have to hold the values of the same type. The first index of an array is index zero. The following code creates an array, b, with 3 columns and 2 rows: int[][] b = new int[2][3]; Given an array called x, you can access the 5th element in array x by the following code: x[5]; //reference the 5th element in an array. Nested for loops are commonly used to display the contents of 2-dimensional arrays. The enhanced "for" statement will iterate through the elements of an array. Given array ‘y’ that holds values of type int, the following code will set the 5th element of the array to 6: y[4] = 6; The list of method parameters are separated by commas. A method can return at most one value. Class Math has several static methods. The Java Application Programming Interface is a Java class library with thousands of predefined classes.

Paper For Above instruction

Creating a user-friendly application for conducting surveys involves careful planning, design, implementation, and testing. The goal is to develop an intuitive interface that engages customers, accurately captures their responses, and effectively analyzes the collected data. This process encompasses designing classes, defining interactions through UML diagrams, and ensuring the application's logic is robust and efficient.

Design Overview

The core classes in this application include Survey and SurveyConductor. The Survey class is responsible for managing individual survey questions, storing responses, and performing data validation, especially ensuring responses are within the range of 1 to 5. The SurveyConductor class orchestrates the overall survey process, including presenting questions, collecting responses, and compiling results.

UML Class Diagrams

The UML class diagram for the Survey and SurveyConductor classes illustrates their attributes and methods, including constructors, accessors, mutators, and utility methods such as validateResponse(). The diagram demonstrates associations, encapsulation of data, and the relationship between survey questions and handling of responses.

The Survey class contains attributes like questionText (String), response (int), and methods including getQuestionText(), setResponse(int response), and validateResponse(int response). The SurveyConductor class manages an array of Survey objects and methods for conducting the survey, displaying questions, and analyzing results.

Sequence Diagram

The UML sequence diagram shows the interaction sequence between the user, the SurveyConductor object, and individual Survey objects. It models how the application prompts for responses, verifies input, records responses, and finally displays results. Key message flows include initiateSurvey(), askQuestion(), validateResponse(), and displayResults().

Pseudocode

Pseudocode for SurveyConductor

BEGIN


Initialize Survey array with questions


FOR each question


DISPLAY question


GET user response


WHILE response invalid (not between 1 and 5)


DISPLAY error message


GET user response again


RECORD response in related Survey object


ENDFOR


ANALYZE responses (e.g., calculate averages)


DISPLAY results


END

Pseudocode for Survey class methods

CLASS Survey


ATTRIBUTE questionText AS String


ATTRIBUTE response AS int


METHOD getQuestionText()


RETURN questionText


END


METHOD setResponse(int response)


IF validateResponse(response) THEN


SET this.response = response


ELSE


DISPLAY error


ENDIF


END


METHOD validateResponse(int response)


RETURN (response >= 1 AND response 

END


END

Error Checking Logic

In the pseudocode, during response collection, include a loop that prompts the user until a valid response between 1 and 5 is entered. The validateResponse() method ensures data integrity by checking that the response falls within acceptable bounds. If an invalid response is detected, the application displays an error message and prompts again, enforcing proper validation.

Testing and Results

Testing involves entering different responses such as 3, 5, or invalid inputs like 0 or 6, verifying that the application prompts for correction when necessary. Screenshots should portray the input process, displaying the entered responses, error messages for invalid inputs, and the final analysis results, such as average scores.

Conclusion

The development of this survey application emphasizes clear design, robust input validation, intuitive user interface, and thorough testing. Through UML diagrams, pseudocode, and test results, the project demonstrates a comprehensive understanding of object-oriented principles, control structures, and data validation essential for successful software development.

References

  • Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1994). Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley.
  • Bloch, J. (2008). Effective Java (2nd ed.). Addison-Wesley.
  • Oracle. (2020). Java SE Documentation. Oracle Corporation. Retrieved from https://docs.oracle.com/javase/8/docs/api/
  • Beck, K., Beedle, M., van Bennekum, A., et al. (2001). Manifesto for Agile Software Development. Agile Alliance.
  • Object Management Group. (2017). UML 2.5 Specification. OMG.
  • Hart, J., & Tenenbaum, A. (2019). Data Validation Techniques for Java Applications. Journal of Software Engineering, 15(3), 45-50.
  • Rademacher, D. (2010). Introduction to Java Collections Framework. JavaWorld. Retrieved from https://www.javaworld.com/article/2077737/
  • McConnell, S. (2004). Code Complete (2nd ed.). Microsoft Press.
  • Gosling, J., Joy, B., Steele, G., & Bracha, G. (2005). The Java Language Specification. Addison-Wesley.
  • Fowler, M. (2003). UML Distilled: A Brief Guide to the Standard Object Modeling Language. Addison-Wesley.

Related Assignments