Skip repetitive navigation links.
United States Department of AgricultureFarm Services AgencySystem Development Life Cycle (SDLC)
Go to SDLC Home Go to SDLC Home Go to About SDLC Go to News Go to Help Go to Contact Us
Search FSA
Go To Advanced Search
Go To Search Tips
FSA Enterprise Architecture
Go to EA Overview
Go to Enterprise Architecture Program
Go to Enterprise Architecture
Go to FSA Infrastructure
FSA SDLC
Go to SDLC Overview
Go to Background
Go to Development Process
Go to Quick Start Guide
Go to FSA Quality Assurance & Control Process
Go to Project Management Process
Go to Configuration and Change Management
Mainframe & System 36 SDLC
Browse by Subject
Go to Developer Tools Overview
Go to Architectural Decisions/Waivers
Go to FSA Assets and Shared Services
Go to Approved Software
Go to Templates and Documents
Go to Information Bulletins & Memos
Browse by Subject
Go to Learning Overview
Go to Training Schedule
Development Process

Build the System

 

 
Getting Started

 
Before the focus can shift to the task of coding, the development environment should be chosen, configured and documented in the Developers Guide, or other supporting document. Some of these decisions will likely have been made earlier in the process, but now is the time to ensure everyone is on the same page and the choices are documented. The goal is to ensure new team members, future development teams, etc. have the information needed to set up a development environment, build the deployable unit, and verify the accuracy of the build. Some of the questions to answer are:

 
  • Where will the project be located within Subversion (the approved source code repository)?
  • What data source information, including configuration is needed?
  • How will the project be built (via Maven scripts or some other mechanism), and what are the detailed steps required to complete the build? See the FSA Builds Overview for more information.
  • How to set up a test environment (server configurations)?

 
Other items to document include:

 
  • Internal team standards or processes that will be followed (for example, using a code quality tool such as PMD). See the FSA Code Review Guidelines for more information.
  • Any externally provided libraries, resources or licensed products that will be used. Refer to the Approved Software page (internal users only) for a list of approved Open Source resources. Refer to the FSA Assets page (internal users only) for a list of FSA developed resources.

 
Coding

 
The SDLC is not meant to strictly control the low-level coding practices of each development team. What it does provide are some coding practices and techniques that are commonly used in the FSA to produce successful results. In addition to the recommended practices and techniques, development teams should also follow the FSA Reference Architecture to help ensure consistency across projects. Each team may set up internal practices and guidelines as needed where no FSA guideline exists.


Last Modified: 12/07/10 8:57:57 AM


SDLC Home | FSA Home | USDA.gov | Common Questions | Site Map | Policies and Links
FOIA | Accessibility Statement | Privacy Policy | Nondiscrimination Statement | Information Quality | USA.gov | White House