The Detailed Design phase builds on the existing design to incorporate technology choices and performance requirements and ensures compliance with the FSA Reference Architecture
. A limited amount of construction/testing activities may occur in an effort to refine and validate the design.
During this phase, the development team will:
- Elaborate Design - Build on the High Level Design by incorporating language specific design patterns and mechanisms and identifying dependencies, attributes, state, associations, etc.
- Integrate with Target Environment - Refine the design to consider choices in technology (i.e., SQL Server, WebSphere, etc.), FSA components (i.e., SCIMS, CBS, eAuth, etc.), and infrastructure constraints.
- Plan Deployments - Determine how and when the deployment unit (EAR file, JAR file, etc.) will be made available.
- Specify Test Details - Identify the test cases including descriptions, inputs, execution conditions, and expected results.
- Finalize the project's Architectural Decisions.
Developers should use FSA templates and style sheets for Web page development. The templates support multiple browsers; however, individual browsers may display Web pages differently based on space and size configurations. These templates can be found via the following links: HTML Templates
, Struts Templates
. See the Coding Practices
page for more detailed information.
Interaction with the DBMO will likely occur during every phase of the SDLC. During this phase the DBMO may be contacted to support the development team with the physical design of the application. This may also be when the creation and maintenance of audit tables
takes place within the FSA databases.
Additionally, DBMO has detailed specific requirements for the security model of the FSA Microsoft SQL Server 2005 platform database environment that should be considered during this phase. Users will be granted permissions via assignment to database security roles. No direct permissions are granted to user IDs. The security roles consist of:
- Read Only - authority to read data in all current and future tables within the database(s).
- Read/Write - provides permission to read and write data in all current and future tables within the database(s).
- Execute - provides permission to execute all current and future stored procedures within the database(s).
- Restricted Access - grants access to specified tables and/or stored procedures or other objects within the database, the tables, views, etc.
For more information regarding the SQL Server 2005 security model, refer to the Developer Resource - Security Policy for SQL 2005
C&A documentation to consider during this phase: Business Impact Analysis, Preliminary Risk Assessment, Security Controls Compliance Matrix, System Security Plan.
Contact the Information Security Office
for further details regarding specific efforts relevant to this phase of the SDLC.
The source code
for the Physical Data Model is also available.