Adore believe repeatable, predictable processes or methodologies that improve productivity and quality.

Adore Follows these methodologies

• Software Elements Analysis:
• Specification Software
• Implementation (or coding):
• Testing:
• Documentation:
• Maintenance:

Some of software development methods we use:

• Waterfall model
• Top-down and bottom-up design
• Prototyping
• V model

The following is an overview of the quality practices of Software Quality Assurance team:

# The iterative approach to software development presents a significant challenge for SQA. The iterative, rapid deployment process is characterized by a lack of strict adherence to a traditional waterfall development methodology (marketing first specs the feature set, then engineering refines the marketing requests into more detailed specifications and a schedule, then engineering starts building to specification and SQA starts building tests, then a formal testing cycle, and finally product release). Here is a variant of development

# As progress is made toward a release, the first priority features are done to a significant level of completion before much progress is made on the second priority features. A similar approach is taken for the hopefully and third priority features. The first priority feature list is all that has to be completed before a product is feature complete, even though, there has been time built into the schedule to complete the second priority, as well.

# Other than the initial OK from the executive team that they want a particular product built, there is not a rigorous set of phases that each feature must pass.

# Developers (designers, coders, testers, writers, managers) are expected to interact aggressively and exchange ideas and status.

# By not going heavily into complete specifications, the impact of a better idea along the way need not invalidate a great deal of work.