Chapter 5. Developing Specifications

Terms you'll need to understand:

• Functional specifications

• Technical specifications

• Logging

• Auditing

• Integration

• Globalization

• Localization

• Error handling

• State management

• Constraints

• Coexistence

• Data migration

• Deployment

• Encryptions

• Signing

• Sealing

• Archiving

• Purging

• Support plan

• Test plan

• Education plan

• Privacy

• Deployment

• ViewState

• Network Address Translation (NAT)

• Internet Protocol Security (IPSec)

• Secure Sockets Layer (SSL)

• Transport Layer Security (TLS)

Techniques you'll need to master:

• Selecting a deployment mechanism

• Planning Internet, intranet, and extranet systems

• Selecting the security mechanism best suited to the situation

• Preparing to achieve system acceptance among users

The developing-specifications phase of the system development process for .NET solution architectures has very specific goals. During this phase, system requirements are transformed into functional specifications, and there are many factors you should consider to produce a useful design. A strong solution must be able to provide the business environment with a useful end product and plan for the system's ongoing maintenance needs. The system must provide services that perform the required tasks as well as securely transmit and maintain data.

You should create a plan for the solution's deployment that makes it accessible to those who need the system's programs, services, and data. The system must be able to grow and adapt to business changes and provide all this functionality with an acceptable level of performance.

The technical specifications needed for the system to operate as designed must also provide similar features. Performance, maintainability, extensibility, scalability, availability, deployability, security, and accessibility are the buzzwords of this phase of the process. This chapter addresses these PASS MADE requirements and discusses the strategies for achieving them.