Development process

Briefly, agile development is followed in our development process. In different projects, SCRUM, XP, UP are applied. Short iteration is the common feature of all our approaches.

All project disciplines, including requirements, analysis & design, implementation and test, happen in each iteration, although these disciplines may have different profiles in different iterations. Once the project enters the construction iterations, each iteration will produce an executable release, with more functions integrated and tested. Each iteration is looked at as a mini project which involves planning, execution, and assessment.

Once an iteration finishes, whether to enter the next iteration or not depends on the decision of the customer, based on the assessment of the finishing iteration, current business conditions, and environment. Therefore, iteration assessment is a key activity of Shinetech's development methodology.

Requirement

The purpose of the requirement discipline is:

• To establish and maintain agreement with the customers and other stakeholders on what the system should do.
• To provide system developers with a better understanding of the system requirements.
• To define the boundaries of (delimit) the system.
• To provide a basis for planning the technical contents of iterations.
• To provide a basis for estimating cost and time to develop the system.
• To define a user-interface for the system, focusing on the needs and goals of the users.

The key output documents of the requirements discipline include Use Case Model and Supplementary Specification.

Analysis & Design

The purposes of Analysis & Design are:

• To transform the requirements into a design of the system-to-be.
• To evolve a robust architecture for the system.
• To adapt the design to match the implementation environment, designing it for performance.

The key output documents of the analysis & design discipline include Software Architecture Document and Design Model.

Implementation

The purpose of implementation is:

• to define the organization of the code, in terms of implementation subsystems organized in layers
• to implement the design elements in terms of implementation elements (source files, binaries, executables, and others)
• to test the developed components as units
• to integrate the results produced by individual implementers (or teams), into an executable system

Test

The Test discipline acts as a service provider to the other disciplines in many respects. Testing focuses primarily on evaluating or assessing product quality, which is realized through these core practices:

• Find and document defects in software quality.
• Advise on the perceived software quality.
• Validate and prove the assumptions made in design and requirement specifications through concrete demonstration.
• Validate that the software product works as designed.
• Validate that the requirements are implemented appropriately.

 

To learn more about Shinetech's development process, please download the below studies or contact us:
How we guarantee code quality  
Methodology and technical approach
Shinetech QA process management whitepaper

back