561.572.0233

1901 South Congress Avenue, Suite 350, Boynton Beach, FL 33426

 

Our Process for Custom Software Development

Palm Beach Software Design utilizes a modern hybrid “.Net Best Practice” strategy customized for each client that prioritizes: Custom Business Application Development, Delivered On-time, Within a contracted budget.

For a more complete understanding of this process please download our whitepaper:

Best Practices in Modern Application Development for Custom Business Software

 
 

01. Discovery

In the beginning of the project, Palm Beach Software Design, utilizing modern hybrid best practices learns about the current workflow and data flow of the client company's business and machine interfaces, which can be referred to as the Discovery Phase.

Our discovery practices include:

  • Discussion of the full scope and requirements of a project to establish expectations of function.
  • Analysis: A full analysis of existing business processes to define and document the scope and requirements for each major sector or module of a project is undertaken. This involves personal interaction with key client employees.
  • Investigation: Determination and recommendation of the optimal technologies and languages. Determination of existing component architecture to speed development and reduce costs is included.
  • Scope and Requirements: The creation and client approval of a robust scope and requirements document to memorialize requirements, expectations, and technology-use plan is carried out.
  • Project Plan, Timeline, and Contract: Includes the creation and client approval of a detailed project plan and timeline with milestones, along with the full development or implementation contract.

Palm Beach Software’s success rate, over thirty years of software development, is based on a process that minimizes mistakes and expensive rewrites because we model the data and logic with a complete understanding of the client’s requirements.



 
 

02. Design

When the scope and requirements process and project specifications are complete, the design phase begins.

Our design practices include:

  • Visual Modeling: The mockup creation of screens, forms, and reports, including look and feel. This process involves multiple meetings to discuss placement of items on the screens, the business intelligence required, etc.
  • UX Design: User experience is designed including the capture of the structure and behavior of user experience and the hiding or exposure of details appropriate to the task.
  • Data Modeling: Data is structured for current requirements, with the ability to expand and encompass future additions and changes to products and services as growth occurs.

Upon completion and approval of visual models and UX design by the client, the implementation phase is entered.



 
 

03. Implementation Phase

Implementation is the writing of code.

Our implementation practices include:

  • Iterative Milestone Approval: All required changes or fixes to meet client objectives are discussed and approved at each defined milestone; this provides for short-term focus. The impact of iterative change requests is assessed and discussed. Approved change requests are prioritized by client management for the current iteration or planned for a second phase of the software after initial release.

Software Personnel

  • Project Manager and Software Architect: Their job is to manage the project, and meet with the client regularly to refine the understanding of how the business runs, so the software always meets and/or exceeds expectations.
  • Technical Team Lead: A seasoned software developer leads the team for each sector or module of the project. The Team Lead makes decisions on technology and coaches other developers while contributing as the lead programmer.
  • Quality Assurance: Includes a continuous repetitive testing and debugging loop for responding to bugs and necessary logic changes within the implementation.

Although testing has been ongoing, upon completion of the implementation phase, full system quality verification begins.



 
 

04. Quality Assurance

Best practices defines quality software as an application or product which meets or exceeds client-approved specifications in the scope and requirements document by objective measures.

Our Quality Assurance features “3-Pass” Testing:

  • Functionality: Follows scope and requirements specifications
  • Errors and Exceptions: No errors or cryptic messages
  • User Experience (UX): Ease of use, look and feel

Note: All work is posted on secured staging servers for easy testing and monitoring.



 
 

05. Delivery and Training

Our delivery practices include:

  • On-time or agreed to delivery based on approved change requests
  • Initial delivery presentation
  • Client-performed software quality verification before the software goes live
  • Agreed to initial client personnel training just prior to “go live” date
  • Installation training support during 1st 30 days after “go live” date