PlantMerchant System Horticulture Club Team A2

1
PlantMerchant SystemHorticulture ClubTeam A2

• SE Morgan Pittkin, Robert Hardy, Rongrong Wang

UE Cody Henthorne, Tao Ni, Sarah Peck, Yoon Suk
Lee
2
Outline

• UE Issues
• SE Issues
• Team Interaction Issues
• Conclusion

3
UE Issues

• Initial Planning
• Low-Fidelity and High-Fidelity Prototyping
• Formative Evaluation

4
Initial Planning

• Web-interface for all systems (POS, Preorder,
  Inventory, etc)
• Simple and consistent design from the beginning
• Pre-order Other e-commerce websites
• POS Easy to learn, similar to retail systems

5
Low-Fidelity Prototyping

• Based our initial screen designs on SEs designs
• Walk-through with client
• Client liked the similar look
• Discovered new features and functionality
• VT PID login
• Scientific names
• Purchase price

6
High-Fidelity Prototyping

• Based very closely on our low-fidelity prototype
• Developed as a series of static web pages
• Aimed towards providing for our benchmark tasks
• Primarily used for our Formative Evaluations

7
Formative Evaluations

• Extremely useful
• Evaluated POS and Inventory with high-fidelity
  prototype
• Evaluated Pre-order with SE implementation
• Key participants
• Experience with current Retail Systems
• Non-club related
• Overall no real big critical problems, but lots
  of good general feedback

8
SE Issues

• Design Issues
• Initial Planning
• Modularity
• Consistency
• Work Arrangement
• Advantages of Design
• Agile-esque

9
Initial Planning High-Level Archietcture
10
Initial Planning

• Early database design
• Paypal helped
• Effective High-Level Design

11
Modularity

• Components are functionally independent
• Incremental development testing
• Easy division of labor

Point-of-Sale
Reports
Inventory Mgmt
Database Wrapper
Database
12
Consistency

• Component interactions all followed the same
  design paradigm.

Container Classes
JSP Pages
Database Wrapper
13
Advantages of Design

• Modularity allowed easy division of work
• Changes could be made quickly and easily
• Example Authentication
• Ease of testing

14
Agile-esque

• Finished pre-order site quickly
• Finished separate components one-at-a-time
• Close interaction between SE/UE
• Face-to-face development environment
• Self-organization

15
SE-UE Interaction

• Early design collaboration
• Communication
• Problems

16
Early Design Collaboration
17
Early Design Collaboration
18
Early Design Collaboration
19
Communication

• Several meetings outside those required
• E-mail communication
• Had representative from other group at meetings

20
Problems

• Early communication delays
• Brought up Paypal idea late
• UE Team worried after finding out about J2EE
  restriction
• VT pid/password authentication brought up late

21
Point-of-Sale System
22
Administrative System
23
Conclusion

• Reasons we think we worked well together
• Early and frequent communication
• Collaboration on initial design
• Respect for each others responsibilities

24
Conclusion

• Positive aspects of the project
• Working on a meaningful project
• Working in a larger group

25
FIN