Architecture Workshops & POC’s

Designing a solution that solves a business problem is necessarily an iterative process. Early on in the process, the customer needs to define the goals and the scope of the project, and the vendor needs to understand these goals.  Each side brings a distinct set of experiences and competencies to the process, and combining them creates a strong solution.
Whatever the business drivers of the design process, Crescent recommends that customers follow a structured design methodology, with each step carefully documented.  Many formal methodologies exist, but all of them should separate these two activities:

Capture technical business requirements. Requirements define the problem that the system solves. Crescent, as a technology company, looks only at the technology layers, not at process re-engineering. Technical business requirements are independent of the underlying technology. With direct customer input, Crescent captures requirements in a WorkOut session.

Design a system that meets the requirements. A complete design fulfills all technical business requirements, and does nothing beyond those requirements. With direct customer interaction, Crescent defines the design in a WorkShop.
Crescent conducts a business requirements gathering WorkOut to ensure we fully understand your enterprise business requirements, followed by a WorkShop to ensure your IT architecture practices and standards are fully considered when designing a solution for mission-critical ERP applications.  Proofs-of-concept are often warranted to validate the architecture and ensure solution fit.