Project Specifications CIS3007 2013 Due date: 28 October 2013 Value: 40% Objectives The course objectives met by this assignment include: •Course specifications are available online from the USQ website <http://www.usq.edu.au/course/specification/>. Always check the website for the latest version. On successful completion of this course, students should be able to: 1. demonstrate advanced written and oral communication skills by preparing and presenting professional documentation that is tailored to a specific audience 2. demonstrate understanding of advanced programming and design techniques in developing distributed business enterprise systems 3. apply the appropriate planning and problem-solving skills required for the successful completion of a business systems project 4. demonstrate an understanding of technologies used in J2EE Enterprise applications (such as JSF, JSP, XML, DOM, StAX, JAX-RS, JAX-WS, SAX, SOAP, EJB, RPC, JMS, JNDI, JMS, etc) 5. demonstrate creativity, initiative, and enterprise by translating the problem into a solution (enterprise web application) that is efficient, economic, smart, and easily maintainable, and complies with the course material and specified Java 2EE software installations 6. demonstrate the ability to create, manage, and distribute robust, reliable, secure, and user-friendly component-based enterprise applications to provide business solutions in a multi tier web based enterprise system 7. where relevant, demonstrate the capacity to work successfully with others as part of a team to plan and deliver a project.Project Specifications Duke-Bookstore Background Currently our organisation has a sample running application to sell books which has been designed as an early proof of concept. The application can be found in your installation at C:\glassfish3\glassfish\docs\javaee-tutorial\examples\case-studies\dukes-bookstore if you installed the system as per instructions. The demo uses NetBeans project so you should be able to open existing project to load the application and all its files into the IDE. Please take time and explore the application fully to understand how it operates. The sample application provides very basic functionalities that we will need to upgrade and extend to deploy as an enterprise business solution. A number of changes to the current system have been identified that must be implemented before we can proceed to the next step of suitability evaluation. You have been given a lot of freedoms in the look and feel of the design but the functionalities which need to be addresses are very specific and mandatory. Visual Changes The web site needs to have a uniform design and feel across all the pages. The functionality needs to be carefully separated so as not to confuse the user as to the purpose of current pages. For example the current design allows us to control the shopping cart (delete all items) shop for available articles and see the current stock and quantities. This d ...

1. Project Specifications CIS3007 2013
Due date:
28 October 2013
Value:
40%
Objectives
The course objectives met by this assignment include:
•Course specifications are available online from the USQ
website <http://www.usq.edu.au/course/specification/>. Always
check the website for the latest version.
On successful completion of this course, students should be able
to:
1. demonstrate advanced written and oral communication skills
by preparing and presenting professional documentation that is
tailored to a specific audience
2. demonstrate understanding of advanced programming and
design techniques in developing distributed business enterprise
systems
3. apply the appropriate planning and problem-solving skills
required for the successful completion of a business systems
project
4. demonstrate an understanding of technologies used in J2EE
Enterprise applications (such as JSF, JSP, XML, DOM, StAX,
JAX-RS, JAX-WS, SAX, SOAP, EJB, RPC, JMS, JNDI, JMS,
etc)
5. demonstrate creativity, initiative, and enterprise by
translating the problem into a solution (enterprise web
application) that is efficient, economic, smart, and easily
maintainable, and complies with the course material and
specified Java 2EE software installations
6. demonstrate the ability to create, manage, and distribute
robust, reliable, secure, and user-friendly component-based
enterprise applications to provide business solutions in a multi
tier web based enterprise system

2. 7. where relevant, demonstrate the capacity to work
successfully with others as part of a team to plan and deliver a
project.Project Specifications Duke-Bookstore
Background
Currently our organisation has a sample running application to
sell books which has been designed as an early proof of
concept. The application can be found in your installation at
C:glassfish3glassfishdocsjavaee-tutorialexamplescase-
studiesdukes-bookstore if you installed the system as per
instructions. The demo uses NetBeans project so you should be
able to open existing project to load the application and all its
files into the IDE. Please take time and explore the application
fully to understand how it operates. The sample application
provides very basic functionalities that we will need to upgrade
and extend to deploy as an enterprise business solution. A
number of changes to the current system have been identified
that must be implemented before we can proceed to the next
step of suitability evaluation. You have been given a lot of
freedoms in the look and feel of the design but the
functionalities which need to be addresses are very specific and
mandatory.
Visual Changes
The web site needs to have a uniform design and feel across all
the pages. The functionality needs to be carefully separated so
as not to confuse the user as to the purpose of current pages.
For example the current design allows us to control the
shopping cart (delete all items) shop for available articles and
see the current stock and quantities. This design is too cluttered
and confusing. You are encouraged to look at other designs for
inspirations but not copy the ideas. You will have to add extra
pages and navigational capabilities between the different
sections depending on the current logical state of the activities.
Things to be addresses by new design
· Unified screen design and placement of option across all the

3. screens.
· Separate screen for different sections of activities
· Add last historical data for the user when logging onto the
system (last login and purchases with greeting)
· Unified mechanisms for moving between the screens and
options on the web pages.
· Extend the book descriptions to provide more details reading
book structure and content.
· Ability to review previous shopping history for the customer
· Ability to modify information for the customer (shipping
address and so on)
· Information to personalise the pages across different screens
when logged into the system.
· Ability to peruse and add items to the cart without being
logged in or registered to the system
· Ability to add and remove items to a wish list as future
possible purchases.
· Ability to review historical purchases for registered and
authenticated users.
· Users should be given the option to rate/review a book once
they are a member and have logged into the system.
· List of the rate/reconditions of books by the customers
· Extend the options to include other categories of products
beyond computer programming
· Expand the collection of customer information to include
contact details and newletters as well new product notifications
· Current front screen needs to be brought up to date and made
more functional.
Structural Changes
The structural changes are modifications to the system either
logical or physical by addition of new capabilities or design to
add or capture new data or activities.
Currently the information tier is a simple item in the backing
bean to fill in the DB with books and details. For current
iteration of the project you can either keep it in the in memory
database or convert the system to a physical Data Base system.

4. If using the in memory database you will need to modify the
process so that changes to the database can be exported in
appropriate format to be loaded at next start-up of the system.
Current solution uses classes to create the database entries
which will not be flexible for our purposes.
Functional Changes
There are a number of changes that need to be implemented in
terms of processing to make the system more suitable for the
organisation. These changes are designed to provide extra
feedback and incentive for users to return and participate in the
product offerings.Things to be addresses by new design
· A more functioning database mechanism needs to be
implemented to record and search the information stored in the
application
· The system must be able to support multiple connections and
processes by appropriately separating the state information
between different communications.
· At the finalisation of the purchases a 10% discount added to
the current purchases to users who have submitted 5 or more
reviews or ratings in the system.
· Collect information to create a mailing list of customers with
their authorisation. The system will look at the wish list and
notify of them of the current process as well as any new
products in their wish list category
· Authentication and for logging into the system. Preferably
that you use the existing facilities security mechanisms but if
that fails write your own checks
· Full controls of the shopping cart to be able add and remove
items as well as process payments.
· Where possible provide client side checks and validations for
input before being submitted
Final Thoughts
While the changes do not look difficult in order to add them to
the existing system they require quite a good understanding of
how the current system is working and the services supplied by
each of the technologies. While the changes might look trivial

5. actually implementing them can be quite demanding.
The biggest change will be moving to the database option and
linking the resources correctly. All the activities are grouped
around the data store and access operations. Once you are over
that hurdle and can access the data store you can either use
mapping or backing bans for the access. Both options have
their advantages and disadvantages.
The final design and operation of the screen are left up to the
individual. Note that you are encouraged to utilise the new
design features and technologies.
Solution
s which have been discarded / deprecated by the J2EE systems
should not be implemented. For example you are encouraged to
use JSF solutions in place of Servlets or scriptlets. Separation
of responsibilities and a good MVC design is very important for
future development.
The downloaded textbook provides you with a lot example code
demonstrating various technologies or procedures to correctly
set up and deploy the solutions. You are strongly encouraged to
carefully go through the different aspects to familiarise yourself
with the technology and terminology. Try and work only on one
part at a time as a small error can be quite hard to diagnose.
Please use the discussion list for the course to discuss issues
and possible problem solutions.
All the best

6. At this point, we have covered all but color. This assignment is
one of two research assignments in the class. For each of the
thirty-four items in the following list, find a large image and
discuss how that image fits the element or principle. I’ve
included an example on the last page of this assignment. You
will need to give credit for each image.
When you’ve finished, you should have 35 pages: a title page,
with your name, completion date and title, - AND – the
following 34 samples with text. You will turn in the file through
Blackboard by attaching it to the assignment page and
submitting it.
1. Use of 1-point perspective in an image
2. Use of 2-point perspective in an image
3. Scenes with a short depth of field
4. Images with an almost infinite depth of field
5. Shapes and designs that suggest the third dimension /
heightened volume
6. Texture as primary element
7. Gestalt Principle: figure/ground ambiguity
8. Gestalt Principle: Proximity
9. Gestalt Principle: Closure
10. Gestalt Principle: Continuation
11. Gestalt Principle: Anomaly

7. 12. Gestalt Principle: Similarity
13. Abstraction with chaotic rhythm
14. Abstraction with fluid rhythm
15. color used to imply (or support) sophistication
16. color used to guide the eye
17. color used to suggest childlike (or for children)
18. color: triadic (non-primary)
19. color: analogous with complement
20. color: analogous
21. color: split complementary (three colors)
22. color: complementary
23. color: monochromatic
24. color: achromatic
25. Typography as primary element in fine art (not design)
26. Value change: abrupt (posterized)
27. Value change: gradual (rich and varied, gradient)
28. Designs that rely solely on 2D shapes (can have text)
29. Shape as primary element
30. Line as primary element
31. Proportion: Golden Section
32. Repetition and variation (patterns)
33. Asymmetrical balance (AKA: asymmetry)
34. Symmetrical balance
Sample 90: Math Influenced (Tessellation)
Image Source: American Math Society, 2002

8. Tiling an equilateral shape, such as a square or hexagon, over a
plane without leaving a gap, creates a tessellation. The above
image uses a hexagon comprised of a rosette of twelve right
triangles, alternating in black and right. These were then tiled
and all of the vertices that did not fall along the vertical or
horizontal axes were disturbed to create a spherical effect. The
use of figure/ground ambiguity, created by the strict adherence
to Black and White, increases the three-dimensional effect and
gives the appearance of a shifting texture.
Assignment 3 Project Proposal Documentation
Description
Marks out of
Wtg(%)
Due date
Assignment 3
100
35%
06/09/13
In the assignment we will start analysing and designing the
changes needed to implement the new functionalities in the
sample solution. Before we can start the implementation we

9. need to analyse the project and describe the changes we will be
implementing and what changes we need to make to make the
project a success. For this purpose we need to provide a project
proposal to the customer.
This part along with submission 6 combined make up the
documentation for project proposal and implementation. You
are free to extend the proposal section but you must include the
sections listed in this document. Ensure that the sections are
easy identifiable and discoverable.
Assignment 3 Activities.(minimum 20 pages in length)
a.) Update the project Management tool with the time spent on
research and working with new technologies needed for the
application.
b.) Add to the Project Management tool the different activities
needed to implement the changes to the solution.
c.) Document the current application describing the major
classes used by the application.
d.) Document the current application describing the flow
between the different activities .
You are to report on the current state of your assignment 3. You
need to provide the following details regarding assignment 3.
Assignment 3 Deliverables.
a.) Detailed printout of the activities in the Project Management
tool.
b.) Project Plan describing in detail the activities needed to

10. finalise the project.
c.) The Project document should include the following sections
· Project title page
· Letter of transmittal
· Executive summary
· Current application description
· System overview (description of what makes this system
unique)
· System operation (services provided and operations
performed)
· Proposal Objectives
· Project/System Overview
· Project Scope
· Project Exclusions
· Current Application Design
· UML of classes
· UML Sequence Diagrams
· Information flow between pages and activities
· Detailed Proposed Changes
· Proposed Costs and Time for Each Change
· Estimated Cost of the Changes
· Benefits of the proposed changes
· Detailed description of the new