250 likes | 949 Views
Group 8 Group Project Presentation. Chair: James Sugrue Secretary: Ataul M. Munim Group Members : Ani Gasparyan Benjamin Swanson Elena Hadjiyiangou Jae Yeon Kim Nikolaos Zangelidis Wan Yankui Yemisi Fabusiwa.
E N D
Group 8Group Project Presentation. Chair: James Sugrue Secretary:Ataul M. Munim Group Members: AniGasparyan Benjamin Swanson Elena Hadjiyiangou Jae Yeon Kim NikolaosZangelidis Wan Yankui YemisiFabusiwa
Work Allocation: • The workload was evenly distributed among all seven deliverables. • People were often put in groups to work on a certain thing. • Worklogs were consistent throughout the course and written in Latex. • Work Allocation was based on skills set. PART A- The way the group worked: (1)
Skills Set: Jobs were divided into six distinctive categories: • Programmers • Latex writers • System designers • Human Resources (i.e. Worklogs) • Secretary • Manager PART A- The way the group worked: (2)
Time Management: • Each member was given strict time to finish their part for the deliverable. • Helped us keep our work organised and on track. • Faced situations where work slightly rushed, but always on time. PART A- The way the group worked: (3)
Group Meetings: • were booked in advanced. • were typically 3-4 times a week. • had a concise and structured plan. PART A- The way the group worked: (4)
Team Work: • Teamwork was not an issue for us, everyone pulled together and did their assigned tasks. • In general, our work was delivered in a clear and creative manner. PART A- The way the group worked: (5)
1. Java as a Programming Language. (skill base) 2. Limited skill base => lead us to allocate tasks of programming carefully. 3. System is designed using Windows. 4. At first we had a basic idea. But we redesigned it in the process of making it. PART B- Technical Part of the design: (1)
5. At the end we decided to use 2 Main Principles: (a) Use the Model View Controller Design Pattern for the data creation and storage. (i.e. Shopper Types or Employee Types). PART B- Technical Part of the design: (2)
(b) Core Part of the System(i.e. Simulations) to be running on real world principle. 6. The most important thing is that we met all the requirements(functional and non). PART B- Technical Part of the design: (2)
One Important Problem we had, during testing was that people pointing out massive flaws in the System. And now some problems we experienced during the process of making the System ...
The Final User Interface of our System: Login screen: password protected, Basic is a subset of Advanced User features.
Main menu: upon choosing a user type (advanced) Default shopper, employee, day, product list and checkout types are provided.
Windows open as you click - we chose this so that you would only have those windows you needed open (picture shows all windows open)
Simulation Input screen: to input parameters for a new simulation
Result: generates a set of graphs representing the output, upon clicking "Generate Results" with at least one checkout