1

2
 Consumer Survey System
Task One
Introduction
The aim of this project is to develop a consumer survey system, that enables
administrator to create a survey, view questions and answers.
The program consists of the following:
Function: is a name for a part of code in a program that performs a certain task, or
a type routine.
Selection: This program allows us to execute an expression or a value. It regulates
the program's flow.
Loops: They allow us to execute a sentence until it is complete. It aids in the
completion of a greater number of tasks. It creates distinct items as a class. It's a
collection of items with the same type of property.
The Consumer Survey system has been developed using C# language.

Task two
Test Plan
A test plan is basically a list of necessities that ensures that a code solution works.
The major reason of doing a test plan is to ensure that the user’s functionality is
meet and that you deliver a system that is working according to the user’s
requirements.
There two types of testing
➢ Black box testing this focuses of the functionality of a developed system. It
looks at the aspect of does this system do what it claims? is the functionality
aspect meet? Those are the questions that arise from a black box test.
➢ White box testing, this focuses on the internal components to see if at all
they are working.

3
Fig 1

Admin

Fig 2

4
signup

Fig 3

Testing product and results.

Fig 4

5
Fig 5

Fig 6

6
Fig 7

Fig 8

7
Fig 9

Fig 10

8
Fig 11

Fig 12

9
Screen shots of consumer survey system
User enter details

Fig 13

10
The output of intered details

Fig 14

11
Admin screen shots

Fig 15

Opens the Consumer survey system

Fig 16

12
You enter Product Name and create questions respectively

Fig 17

13
Questions and product created

Fig 18

14
Product Survey Created

Fig 19

15
Sign up code

16
Fig 20

Survey Answers code

17
18
19
20
Fig 21

21
Task three
Class Diagram
A class gives a developer a brief understanding of how the system behaves, each
class consists of attributes and somewhat give and understanding of the behavioral
pattern.A class diagram will help a developer have a visual understabding of what
the system will do.A classs diagram will give an idea of the relationships that are
presnt amoung classes.A class diagram is helpful to a programmer in a system as it
gives him or her an idea of how things ought to be done.
This Consumer Survey Class diagram gives a depiction of each classes and shows
the relationships between them.
Signup class: this class contains these attributes:
➢ Username: Filed is a text(string) data type that will be used to store admin or
customer users. It also has the read and write properties.
➢ Password: Filed is a text(string) data type that will be used to store the full
name of the administrator or client. It also has the read and write properties.
➢ UserType: Filed is a text (String) data type that is used to store user or
admin. It has read and write properties.
Login Class: this class contains these attributes:
➢ The user name: Will be stored in this field, which also includes the ability to
set and retrieve values from the user.
➢ Password: Is used to store passwords and also has the ability to set and
retrieve data from the user.
Admin Class
This class consists of the following attributes:
The SurveyDescription: This attribute holds a string value, it contains read and write
properties.
Create Question attribute: This attribute enables an admin or user to create
questions.
The ProductName: This attribute holds a string value.
Create Survey: This attribute enables the user or admin to create the survey after
they are done creating the questions.
Survey Answers class
This consists of the following attributes:
ReadQuestions: This attribute holds a String value, it contains read properties.
The ProductName: this consists of the name of the product which value is a string.

22
Answer: This attribute prints the answers in notepad.
Justification of class design
According to my understanding, the system required the login class to allow an
admin or user to log onto the system; additionally, the signup class was required
because those users who are not registered on the system would need to create
accounts; the admin class, is important because it allows an administrator to
smoothly manage the system, including the ability to create users, edit details, create
questions, view answers, and many other functions; and the SurveyAnswers class,
which allows a user to view answers to a survey. The ConsumerSurveySystem class
is the parent class from which all of the preceding classes derive their
characteristics.

Fig 22

23
CONSUMER SURVRY SYSTEM USER MANUAL
This user manual is to help the user know how to use the consumer survey system
with less difficulties.

➢ First time user click SignUp button.

Fig 23

➢ Create Username and password choose what type of user you opt to be
under user type .

Fig 24

24
 ➢ Log into Consumer system using the created credentials
➢ Clicking on the login button brings you to a “product survey system template”

Fig 25

25
 ➢ Enter product name, create questions and then click on create survey to
complete process.
➢ You enter the product, then you create a question under 1,2 and 3 then click
create survey.

Fig 26

26
 ➢ When you enter the details, you click on create to complete process.

Fig 27

27
 ➢ Once done you click on log out to exit the system

Fig 28

28
Conclusion
Developing a consumer survey system was an eye-opening experience that taught
me a lot about the C# programming language, as well as what a class is, what
characteristics are, and many other concepts that are important in the building of
such a system.
One of the benefits of learning to code in C# is how efficient it is. C# is a simple to
read and understand statically typed language, making it easier to spot problems in
code (yours or another developer's) and comprehend the code you're reading. This
is crucial for a student who is taking this course for the first time.
The knowledge gained makes it simple to create C# programs with fewer
complications.

29
List of References
Bartoll, M. Ahari, N and Moldez, OC (2004). Design Patterns in C#. Västerås,
Sweden: Department of Computer Science Mälardalen University.

Bennett, S. McRobb, S and Farmer, R. (2004). Object-Oriented Systems Analysis and

Hoffer, J., George, J. and Valaciah, J. (2010). Modern Systems Analysis and Design,
6th Edition. Pearson Education Ltd

Hughes, B. and Cotterell, M. (2009). Software Project Management 5 th Edition.

http://docplayer.net/48000858-What-is-software-design.html
http:/link.springer.com/chapter/10.1007%2F978-0-85729-172-1_2
https://www.guru99.com/white-box-testing.html

Larman, C. (2004). Applying UML and Patterns: An Introduction to Object -Oriented

Woulds, J. (1997). Information Privacy and Security - A Regulator's Priorities.

www.guru99.com/functional-requirement-specification-example.html

www.guru99.com/functional-vs-non-functional-requirements.html

30
Yeates, D and Wakefield, T. (2004). Systems Analysis and Design, 2nd ed. Harlow:
Pearson Education Limited.

31