Application Development

Zantech performs the full range of Software Development Life Cycle (SDLC) activities for our customers. Based on customer-specific requirements, we customize existing software for special applications, develop specialized applications for mobile platforms, and create new systems using various development approaches from Classic Waterfall, to Agile or a hybrid. 

Regardless of the development methodology or the development environment, our application development projects follow a similar approach:

  •  Examine/Understand Project Scope
    • Develop Product Requirements Backlog – System Requirements Documents (SRD) and Logical Design Documents (LDD) leading to Preliminary Design Reviews (PDR)
    • Develop project artifacts including: Project Planning Reviews (PPR): Quality Assurance and Surveillance Plans (QASP), System Requirements Plans (SRP), Draft Test and Evaluation Master Plans (TEMP), Project Management Plans (PMP), Requirements Management Plans (RMP), Configuration Management Plans (CMP), and Data Management Plans (DMP)
  • Define Requirements
    • Capture requirements as User Stories – Logically decompose functional requirements
    • Establish Release Backlog and prepare for System Design Reviews (SDR) and Critical Design Reviews (CDR); Prepare Functional Requirements Documents (FRD), Requirements Traceability Matrices (RTM), Contingency Plans (CP), Final RTM, Final SRD, System Design Documents (SDD), and Deployment Plans
    • Conduct CDRs with Sprint planning, aligning our design with the enterprise architecture
  • Design, Develop, Integrate, and Test
    • Determine iteration length
    • Elaborate stories at a level of detail to be implemented within a single iteration
    • Move highest-risk/highest-priority stories to front of the queue for implementation
    • Start each iteration with the team planning session
    • Select stories from the queue until a full iteration’s work is identified
    • Refine each story further into specific tasks
    • Development work begins with writing Unit Tests using the Test-Driven Design
    • Coding does not begin until the Unit Tests have been written

Zantech performs the full range of Software Development Life Cycle (SDLC) activities for our customers. Based on customer-specific requirements, we customize existing software for special applications, develop specialized applications for mobile platforms, and create new systems using various development approaches from Classic Waterfall, to Agile or a hybrid.  Regardless of the development methodology or the development environment, our application development projects follow a similar approach:

  •  Examine/Understand Project Scope
    • Develop Product Requirements Backlog – System Requirements Documents (SRD) and Logical Design Documents (LDD) leading to Preliminary Design Reviews (PDR)
    • Develop project artifacts including: Project Planning Reviews (PPR): Quality Assurance and Surveillance Plans (QASP), System Requirements Plans (SRP), Draft Test and Evaluation Master Plans (TEMP), Project Management Plans (PMP), Requirements Management Plans (RMP), Configuration Management Plans (CMP), and Data Management Plans (DMP)
  • Define Requirements
    • Capture requirements as User Stories – Logically decompose functional requirements
    • Establish Release Backlog and prepare for System Design Reviews (SDR) and Critical Design Reviews (CDR)
    • Prepare Functional Requirements Documents (FRD), Requirements Traceability Matrices (RTM), Contingency Plans (CP), Final RTM, Final SRD, System Design Documents (SDD), and Deployment Plans
    • Conduct CDRs with Sprint planning, aligning our design with the enterprise architecture
  • Design, Develop, Integrate, and Test
    • Determine iteration length
    • Elaborate stories at a level of detail to be implemented within a single iteration
    • Move highest-risk/highest-priority stories to front of the queue for implementation
    • Start each iteration with the team planning session
    • Select stories from the queue until a full iteration’s work is identified
    • Refine each story further into specific tasks
    • Development work begins with writing Unit Tests using the Test-Driven Design
    • Coding does not begin until the Unit Tests have been written
  • Implement
    • Prepare documentation for Operational Readiness Reviews (ORR) consisting of: Final TEMP, System Test Acceptance Reports, Final System Documentation, Version Description Documents (VDD), and Transition to Support Documents (TSD)

    Case Study

    Here, you will find Case Studies detailing the challenges we have faced on multiple contracts, and the impressive actions we have taken to overcome them. To learn more about our application development capabilities, click on “Discover more”, and check back regularly to learn about our newest contracts and customer testimonials.

    Print Friendly, PDF & Email