North Carolina, South Carolina

Software Architectural Design

When all functional requirements for a custom software project are known, and the final functional specification is complete, the architectural design can proceed. Here, a consultant's expertise is particularly valuable. Appropriate design decisions are important because after coding begins, costs to make necessary design changes rapidly increase.

Important Early Design Considerations

A skilled consultant can guide you through some important design issues including:

• Setting design standards such as variable and procedure naming conventions
• Creating a comprehensive error or exception-handling strategy
• Practicing object-oriented software design
• Identifying key objects, and opportunities for code reuse
• Using time-saving and quality-enhancing design patterns such as pre-tested application blocks and frameworks
• Evaluation of any third-party software components that can reduce development costs
• Establishing source-code control policies, and creating software project management plans
• Determining features to deliver in each development phase
• Evaluating software development resources and coding options
• Identifying integration strategies with other software systems and databases.

Rapid Prototype Design

Prototypes are often useful during a project's design. Frequently, stakeholders require a proof-of-concept to validate a planned software system. Screenshots allow non-technical users the opportunity to participate in the design process. Time used for a prototype often pays dividends in better design and greater stakeholder ownership in the project.

Detailed Design

Where the requirements specification states "what" the system will do, the detailed design spells out "how" the system will meet the requirements. A talented software designer requires a combination of software design knowledge, creativity, adherence to purpose, and an eye for the cost implications of each design decision. Productive Technology has this rare mix of talent, to bring an appropriate design to your new system.

Data Model

Many software systems interact with a database. When a new system requires new database objects, or utilizes existing database objects, a data model can be helpful. Listing all tables, columns, and relationships, a well-designed data model mirrors the system design. When a new system must work with an existing database that cannot feasibly be altered, the data model emphasizes the reason for design decisions that might be made differently under more flexible database conditions.

Data Flow

Your new software system may utilize data created from other systems; or, the other system may consume data produced by your new system. Your staff benefits from understanding the "big picture" of where critical data moves throughout your IT organization. Adequate and current data flow documentation serves as an important troubleshooting and reference tool.

Documentation

Those who develop software systems do not always have the technical writing skills necessary to adequately document a system. Budget constraints may cause documentation to take a low priority, perhaps being deferred indefinitely. Rapidly changing, living systems, require documentation to capture a moving target. User documentation must convey a different message and reach a different audience than documentation oriented toward IT staff.

Productive Technology will provide excellent technical writing capabilities for the appropriate level of documentation you require. Using a clear style, using descriptive graphics, and organized to accommodate system changes as they occur, your consultant will produce the technical documents you need.