1 / 11

Android Development

Andrew Mangle – Asst. Professor – CSIT Seminar 1 – Nov. 1. Android Development. Overview. Welcome Goals / Expectations Seminar Overview Seminar Organization Seminar Project Overview Next Steps. Welcome. Thanks for attending and contributing Student and Faculty Introductions Name

walker
Download Presentation

Android Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Andrew Mangle – Asst. Professor – CSIT Seminar 1 – Nov. 1 Android Development

  2. Overview • Welcome • Goals / Expectations • Seminar Overview • Seminar Organization • Seminar Project Overview • Next Steps

  3. Welcome • Thanks for attending and contributing • Student and Faculty Introductions • Name • Seminars start @ 5:00 • The earlier you arrive the better! • Cooperation AND Collaboration • NOT COMPETITION!

  4. Goals and Expectations • Create and support an environment conducive to learning • Be flexible and open to different perspectives • Encourage and support others within and outside your team • We are here to develop and learn, not to be in competition (business/personal) • Don’t expect to be millionaires / experts by December • Expect to work hard and be challenged • Expect to work with others

  5. Seminar Overview • Introduce Agile Development processes in order to deliver results quickly • Agile Manifesto • Value - • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan • Break tasks into small increments with minimal planning (with short iterations) • Emphasize communication (Pair Programming / Face-to-face communication) • Create a routine – schedule • Daily Updates – even if you didn’t do anything are recommended • Seminar meetings will serve as our group-Scrum meetings

  6. Seminar Organization – Group Selection • Everyone has to be an active participant • 45 minutes gives us time to regroup and reflect • Small groups are the best options • Individuals will be supported by other team members • Select teams • Quickly need to determine a “match” or if you need to regroup • Similar interests, goals, communication style, personality • Need to feel comfortable sharing ideas, exchanging best practices and lessons learned [communication!] • Think – who would YOU want to be on your team?

  7. Seminar Organization • We can’t jump right into programming  • Nov 1 – • Project identification, Team selection, Wireframing, Diagramming • Nov 8 – • Eclipse setup/ADK/Emulator, team check-in, group reorganization based on progress (HelloWorld) • Nov 15 – • Screen setup (GridView), Layout and Linking Screens (Screen Designs) • Nov 29 – • Mapping / Locations (Mapping App) • Each week I’ll provide a PPT for the next week

  8. Seminar Project Overview • Background – CCBC is looking to update the signage, building names and maps for all campuses (Start with Essex) • The faculty, students and staff have requested an app for the proposed changes • Project – Create an app that allows students to identify their current location and where they want to go.

  9. Seminar Projects - Wireframes

  10. Team Selection • At this point in time, I would like everyone to select their initial team • You can change teams, I will rearrange teams next week and some teams may have attrition • There should be three people in a team • Each person should have a name tag • To encourage meeting people • No more than 2 of the same number in a team

  11. Next Steps • Exchange Information with your group • Eclipse IDE / ADK / Emulator • Please review the supplied presentations available at andrewmangle.com/android • Start planning and exchanging ideas • If you are having second thoughts, please let me know (there is a waiting list of 8 people) • Any Questions?

More Related