Feditec development methodology is a process for managing the development of business applications. It is comprised of a series of phases.
|
| Project Scope Identification |
In this phase Feditec staff conduct study of the existing systems. Find out the scope of work. Meet user of each section/departments; gather marco-level requirements and discuss possible solutions and critical success factors.
The primary goal of the phase is to determine:
What is included in the scope of work?
How much time it will take to complete the project?
What would be the resources required for the project?
|
| Project Planning |
Once the project is awarded to Feditec, a whole exercise of project planning is performed. That includes the formation of teams i. e Development team, and QA team. The Project Manager and QA Manager develops Project Plan and QA Plan. Schedules and milestones are defines in this phase. All schedules commitments are reviewed by the, CTO, and CEO before giving project Plan to customer.
|
| Requirements Collection Phase |
Team of analysts documents the details requirements of user during this phase. The deliverables of this phase is the Software Requirements Specification (SRS). It is the goal of the analyst team to dig out hidden requirements. Business Analyst shares their knowledge about best practices with users in joint sessions. The customer/users are always heavily involved in this process.
|
| Design Phase |
The primary goal of the design phase is to develop detailed architecture of the various modules of the software. When SRS is approved by user, then design phase translate the SRS into set of representation that describe the data structure, architecture, and algorithms.
|
| Coding Phase |
During this phase initial version of the product is built. Feditec uses various standards include coding conventions (Coding Standards, naming convention, Style-guide) to facilitate this phase.
|
| Testing / Rework Phase |
This phase includes application testing. This includes integration, and defect resolution. It is critical to allow enough time not only to find, but also to fix and retest any defects. Errors are characterized as severe or non-severe.
|