"Technical writing is any written form of writing or drafting technical communication used in a variety of technical and occupational fields, such as computer hardware and software. It encompasses the largest sub-field within technical communication."

After gathering detailed information about business and user requirements and business processes, the CIS team will then proceed to the analysis of the information. This is the analysis of the created documents in the envisioning phase where the initial or candidate requirements are created. There are two purposes of the analysis. The first is to review user and business processes and activities. The second purpose is to document and model the context, workflow, task sequence, and environmental relationships of the business. The transformation is performed in the following steps: 1. Synthesizing information 2. Refining use case diagrams 3. Selecting an appropriate application architecture for the solution 4. Creating a conceptual model of the application.

Business requirements describe the organization's needs and expectations for the solution. They define what the solution must deliver in order to capitalize on a business opportunity or to meet business challenges. Requirements are identified by considering the organization as a valid entity with its own set of needs from the solution. These requirements are generally high-level requirements and provide the context in which the solution will operate. An example requirement might be that the solution must be able to interact and communicate with other business processes, applications, and data sources.

Technical Components

The technical specifications are a set of reference documents that in the development phase is used to determine the scope of work and define development tasks. These documents may consist of artifacts that detail the class specifications, component models, metrics, and network topologies. Also included are interface definitions, configuration files, dynamic link library (DLL) and assembly names, strong names keys, and deployment elements. This is a living document that is completed after the conceptual, logical, and physical design phases are complete. It is updated during the development process as components are completed.  contact us for more info.