Make testing easier in tasks Task 1 and Task 3 → create a directory d:\temp and put the XML-file of the Task 1 and the datastore of the Task 3 to the directory.
Create a console application CountCustomers, that reads our customer's data from a XML file and shows data in following format: Company, title, Lastname, FirstName and sales any (for example: Peanuts ltd, Mister Brown Charlie 10000€). Use this XML-file. Sort the company names to alphabetical order and show them in a console each name in own line. The application counts also sum of sales and shows it if needed. Put the XML-file to the directory d:\temp and point it in a starting arguments.
There are two starting
arguments for application:
- the first argument defines the file name, the argument is obligatory
- the second argument "-c" defines sum of sales counted, the argument is not
obligatory, if missing sum is not presented
- if no arguments are given, th application shows simple help text how to use
the
application.
For example the end-user could start the application with this command:
CountCustomers d:\temp\WorldCustomers2008.xml -c
Check also that the given file exists and it is
accessible, check also that schema of a xml-file is proper.
Use normal try-catch-finally -exception handling.
Create a batch file test.bat to test all argument combinations.
Default time: 45 min
Points: max 12 points
- reading data 2 p
- presenting right data in right format 2 p
- sum of sales
- arguments 2 p
- error handling 2 p
- batch file 2 p
Create a Windows application "one handed fruit machine".
In the beginning a player has 10 zlotys, one spin costs one zloty. There is a button "Spin" where
the player
can start playing. Create eight different
jpg-pictures, if possible same size, motifs of pictures you can select freely,
for example they can be country flags. When the user plays the application draws
three pictures.
More requirements:
Default time: 1:00
Points: max 16 points
- user interface 2 p
- drawing 2 p
- animation of drawing 1 p
- winning logic 2 p
- real time mount of money 2 p
- extra feature locking 3 p
- attractive outlook 2 p
- extra "golden" features 2 p
We have a group of programmers who need to share Tasks in a software projects.
Create a Web Application for handling Task data. The name and directory
of the datastore is in Web.Config configuration file.
The datastore can be text file, xml-file or Access database. There are two kind
of data in datastore: users and tasks. Create datastore with proper schema
and use it. Put datastore to the directory d:\temp
and point it in Web.Config. It is not allowed to put the datastore any other
directory.
About users there must be at least following data:
- first name
- lastname
- e-mail address (use it as username)
- password (no need for encryption now)
About tasks there must be at least following data:
- name of the task
- date when added to datastore
- due date (so date when task should be done)
- completed date (date when task was done, empty if not task is not finished)
- additional information (text)
- person in charge (from the users)
When a programmer navigates to the web site, he/she must identify and
authenticate him/herself with username and password. If authentication is
succesfully, the programmer is directed to main page. If authentication is not
succesfully (three tries), the programmer is directed to an error page.
In the main page the programmer can:
- add tasks
- remove tasks
- change details of tasks
- mark tasks completed (application automatically adds completed date when task
is marked completed, the programmer just clicks button...)
- filter tasks with following filter:
1) show only programmers own tasks
2) show only programmers own uncompleted tasks
3) show all programmers uncompleted tasks
4) show all programmers completed tasks
5) create your own filter
Use MVC-model, so put all data handling to own class, name it as BLData.
Default time: 1:15 min
Points: max 18 points
- datastore 2 p
- configuration file 2 p
- authentication 4 p
- reading data 2 p
- select 2 p
- editing 2 p
- deleting 2 p
- completing task 2 p
- filter 1p/each max 4 p
- MVC 2 p
Grading:
percent of maximum points | grade |
>= 90 % | 5 |
>= 80 % | 4 |
>= 70 % | 3 |
>= 60 % | 2 |
>= 50 % | 1 |
< 50% | failed |