Execution Friendly Mobile Application Development Phases We Follow
TipEnter follow the agile mobile app development methodologies to develop apps and games.
Application Development Methodology is divided into the follow phases:
1. Requirements Phase
2. Project Planning Phase
3. Detailed Design Phase
4. QA Testing Phase
5. Project Completion Phase
The requirement phase starts with the Implementation Planning for the mobile app and back end system. The next step of the process is to create a requirement specification based on the information gathered through the Implementation process.
At end of requirement phase – Each of below listed documents are deliverables which are
reviewed with and approved by the customer
• Requirement Specifications
• Functional System Requirements (FSR)
• AKA Functional Requirements Specification (FRS)
• High Level System Design (HLSD)
Project Planning Stage
• Ensuring all project prerequisites are met
• Making sure that all dependencies are identified and recorded in the project plan
• Preparing the chart sheet for the project schedules with deliverables as per the agile methodology
Detailed Design Phase
The detailed design stage will vary based on the customer requirement and business goal.
Based on the functional system requirments and high design document(s), we create Detailed Design specifications which capture all the end to end integration details like:
• Business Object Definitions
• Business Rule Definitions
• Screen Definitions
• Validation Rules
• Transaction to screen/action mapping
• Design Update Processes
• Define target systems
• Define update steps
• Design Error Handling
• Test Cases
• Define test cases and map to FRS
QA Testing Phase
During the QA phase, the following tasks are executed:
• Define and Document Functional Acceptance Test Plan
• Integration Testing
• User Acceptance Testing
• Sign off
It is a standard best practice at TipEnter that developers do not test their own code. In larger projects, we have found an effective practice is to have unit test checklists that developers sign off on as they perform their unit tests as well as when they peer test. This not only provides a paper trail, it encourages accountability.
As with the development environment, it is critical that your test environment match your production environment. This means that:
• We test with production logic.
• We test with the same devices that customer will deploy over the same communication channels.
• The test environment has the same data, configuration, and security as the production
• We have a firm issue resolution and point release plan agreed beforehand.
• It is also important that the project peer testing integrate the customer provided test cases to ensure that all scenarios will be tested
Project Completion Phase
Project completion includes both Post Go Live support and Project Closeout.
Post Go Live Support is an important part of the process as it helps the users become comfortable with the system, identifies opportunities to fine tune, and provides for a mechanism to implement approved changes.
Post Go Live Support includes:
• Support client team
• Review feature requests/issues raised by users
• Implement new features
Project Closeout helps record any lessons learned during the project and helps position the project for long term success.