Phase E: User Interface Prototype

moodusroundoSoftware and s/w Development

Aug 15, 2012 (5 years and 2 months ago)

259 views

SE 273
0

Intro
duction

to Software Engineering

Phase
E
:
User Interface Prototype
Grading Rubric



©Hasker

Page
1



Phase
E
:
User Interface Prototype


Construct a user interface prototype for your project. Your prototype must be implemented in Java, but it
should have absolutely minimal functionality. That is, include buttons, text boxes, drop
-
down lists, and
sample
graphical images, but selecting the components or filling in text boxes should not have any
effect. You can have multiple Java programs if it would be more convenient to prototype different
aspects of your project separately.

Details


1.

Save your project to
proto
\
ui. That is, the source code and other portions should be in a “ui”
folder within a “proto” folder in your project.

2.

If you use Netbeans, be sure to check in any relevant build files.

3.

Do not check in .class or other files that are created by the syste
m.

4.

Save the file
http://www.uwplatt.edu/csse/courses/se273/proj/phE
-
writeup.docx

as
proto
\
ui
\
GroupXUIPrototype.docx and fill in the missing items. In particular, the documen
t
n
ame
should be at the top followed by the grading rubric, meeting log, and member time
report. Fill in the GROUP: line just before the grading rubric.

5.

Fill in the meeting dates and members present in the table. Note only two meetings are
required, but thos
e meetings will be far more effective if everyone spends some time outside
the meetings looking for issues.

6.

Fill in the meeting dates and members present in the table. Note only two meetings are
required, but those meetings will be far more effective if ev
eryone spends some time outside
the meetings looking for issues.

7.

At the bottom is a section entitled “prototype report”. Write a short paragraph describing what
part of the user interface you prototyped and what your conclusions were from this prototype.
I
n addition, insert screen shots showing your user interface in action. In Windows, you can
capture an image for the currently active window by clicking on Control
-
PrtScn. This will copy it
to the copy/paste buffer, then you can paste it into your document.

8.

As always, be sure to
apply

grammar and spell checks.

9.

Have one member of your group arrange a demonstration. It’s not mandatory that all be at the
demonstration, but there should be at least two group members. Plan for about 20 minutes for
the demonstrati
on.


It is very important that you focus this prototype on
just

the user interface. You will lose points if you
implement
much
functionality behind that interface. If your system is window
-
based,
generally
the
maximal functionality you might implement
would be opening a new form when clicking a button that
should result in opening a new form. If your system is console based, you might implement code to
respond to specific commands, but that code would print canned responses to very specific
commands. If

you have any doubts about whether you implemented enough or too much, ask your
instructor!