S62_Use of Mobile Devices With Agile Assets in Louisiana_LTC2013
Pseudo Agile Software Development Process for Mobile Application
-
Upload
christoph-hechenblaikner -
Category
Technology
-
view
580 -
download
2
description
Transcript of Pseudo Agile Software Development Process for Mobile Application
CMPE 131 Group 1 SiQuoia Final Presentation
Joey Richardson, Christoph Hechenblaikner, Joseph Chong, Wenjia Zhang Dec. 3rd, 2013
¡ Objective
¡ Observation
¡ Execution
¡ Process
¡ Tools
¡ Key Takeaways
¡ Almost everyone has a mobile device.
¡ Will continue to progress and grow to
become more available to everyone
¡ Quizzes and learning on the go in the palm of
your hand. (high usability)
¡ Ease of use for kids to employees in big
companies. Ref.: http://mashable.com/2010/04/13/mobile-‐web-‐stats/
¡ Productivity Apps are very UI Oriented ¡ Most Requirements can be bound to UI-‐Screens
¡ Unit Tests are often problematic (UI dependency)
¡ Tools for agile in place ¡ We use waterfall for this project in this course
¡ Interactive Mockup ¡ Use-‐Case based ¡ SRS (Software Requirement Statement):
§ Organized by Use-‐Case
§ Use-‐Case to Screen Mapping
¡ SDD (Software Design Document):
§ Focused on MVC
Joey Christoph
Developers
Joseph Weinja
Testers +
Documentation
Requirements
Design
Implementation
Testing
Requirements
Design
Implementation Testing
Refactor
Implement Test + Req.
Unit-‐Tests
Peer-‐Inspection
Adaptation
UI-‐Tests
Adaptation
Textbook Agile Pseudo-‐Agile
Source: Software Engineering: Modern Approaches, Eric J. Braude, Michael E. Bernstein, 2nd Edition, Wiley 2010
¡ Git source control on GitHub
¡ Xcode built in unit tests
¡ Microsoft Project
¡ AppCooker, AppTaster (Mockup)
¡ Google Hangout (SCRUM like Iteration
Meetings)
¡ Successful implementation of Pseudo-‐Agile into mobile app development.
¡ Successful software engineering management for mobile apps.
¡ Successful usage of tools to facilitate project and product development.
¡ Successful in meeting deadlines so far. ¡ Discovered points to improve
Q&A