Java case studies: game playing

1
Java case studies game playing

• A simple software development process from
  specification, to design, implementation, and test

2
Points of this development Java sample games

• Create a simple game by using Java

Demonstrate the importance of software
engineering principles for simple Java programs
development
Point out the significance of requirements in
software development
Using Java API
3
Course materials

• Lecture slides
• about 20 slides
• takes 1 lecture hour
• Assignments
• modify presented programs by adding new
  requirements
• make new games using presented examples
• Starting from presented examples, make a program
  that can be use in education.

4
Goal Develop the program-game Memory test

• Task
• Develop a program, to test the memory of the
  user!

5
First option

• The Requirements are not specified on the
  beginning.
• A pupil I made a good Pascal program, we can
  use it!
• OK, we can try that program! (The same kind of
  program, as an application, we can easily make in
  Java!)
• Text-based programPascal\MEM1.EXE

6
Facts concerning software development phases

• Most errors of software systems result from
  misunderstanding the problem to be solved.

• Software development consists only of a small
  part of programming
• Requirements analysis 20
• Design 15
• Implementation 20
• Test 45

7
Learning goals

• The presented examples should stress out the
  importance of requirements in the process of
  software development.
• Before implementing, the next step should be
  design of the application
• specify components and
• relations between them.
• Starting with the implementation too early may
  lead to projects failure.

8
Development process of Memory test

• Requirements analysis
• Design
• Implementation and test

9
1. Requirements analysis Memory test

• Task
• Develop a program based on GUI to test memory
  of the user. The user should have possibilities
  to open 2 fields and see data there. If 2 fields
  with same data are opened, the fields stay
  opened, otherwise closed. The goal is to open all
  fields.

10
Open questions

• What kind of program should be developed (applet
  or application in Java)?
• Whether use keyboard or mouse?
• How the field should look like?
• What kind of data should be put into fields?
• How to measure the properties (capacity) of
  memory?

11
Requirements specification (1,2,3)

• 1. It is not so important the applet is
  acceptable.
• 2. The mouse should be use.

3. The table with fields can be designed in the
following way
A field
12
Requirements Specification (4,5)

• 4. For the beginning, the kind of data is not so
  important (we can use numbers, letters, signes,
  ...)

5. The numbers of mouse-clicks can be use as the
measure.
The second option MarijaSegrt\PAMCENJE.HTML
13
2. Requirements analysis Memory test

• The first 3 requirements can stay.
• Additional requirements
• Instead the numbers, some pictures can be used
  as data in fields. For example, something like
  these
• Some other measures could be use for the
  capacity of memory. For example the time spent.

14
Some changes are made in design of table and two
new implementations are created. The third
option Ann\SEMINARSKI_JEZICI\index.html SrdjanJei
sel\memorija.html
15
3. Requirements analysis Memory test

• The previous requirements can be kept.
• The game may be improved by introducing the
  different levels.
• As the measure, the number of tests can be used
  (in fact, this measure is used in the second
  option).
• The fourth option
• Dusan Radojevic\Memory.html

16
Development process of Memory test

• Requirements analysis
• Design
• Implementation and test

17
Notes about design

• SW architecture description languages UML-
  industry standard. So, the UML is used in this
  process.
• The finding of classes and relations between them
  is the most important task. (In our cases
  different classes are used in different
  examples.)
• Our task is not so complicated (it is a simple
  students assignment!) Thus, the structure of our
  program(s) should not be complicated.
• We will skip the details about design-phase.

18
Development process of Memory test

• Requirements analysis
• Design
• Implementation and test

19
Note about implementation
The different implementations are presented
here. The programming language Java is used for
the GUI-implementation. If requirements are well
defined and design phase is completed, the
implementation phase is simple. The details
related to the implementation will be skipped.
(The source code is available.)
20
Testing

• This is the most time consuming phase.
• After the first version of programs, different
  corrections are made.
• On the beginning, the testing is made without
  pictures. Later, the pictures are included.
• The most interesting cases are examined but the
  errors are possible.

21
Critics of the implementations

• The on-line help is usually absent.
• The applets are not scaleable.
• Better structure of classes is necessary.
• Program should be more secure (the private
  variable should be used).
• . . .