A new case study was added to the DataPlex website today discussing DataPlex’s interactive English language word root reference guides. Read more.
A new case study was added to the DataPlex website today discussing DataPlex’s interactive English language word root reference guides. Read more.
By “old,” we mean systems that were designed more than a generation of technology ago. “Generations of technology” are usually indicated when the class of the components are superseded by a new one. Here are some examples:
A particular hardware circuit is comprised by different sections, and each section may be different numbers of generations old, so a weighted analysis can be used to explore trade-offs of a design upgrade.
For lack of any other measure, an electronic design can be considered old if it is more than ten years old. The electronics industry as a whole advances quickly, and few electronic components are used in the same way ten years later.
One useful question to ponder: If a qualified engineer were to design a circuit today for the same application, how would it be different? The answer helps to point us in the right direction. A new electronics design will utilize parts that are currently available and have a complete yet cost effective feature set. If the design were to be significantly different, then that is a strong argument for not perpetuating the approach of old design, although.
That said, an engineer might still choose to perpetuate an old design based on economic, compatibility and political factors. He may wish to use up existing supplies of old parts, or continue to provide products which meet with customer expectations. Something more technically modernbut significantly different may be perceived by customers as inferior or undesirable. Other technical reasons relate to support and repair and intellectual property issues.
Once the decision is made to update an old design, the update process is straightforward. Here is the general process we use at DataPlex:
If it was not the first step to break inertia, this should be the easiest step. Old manuals and product datasheets are often useful references.
A bit more challenging, identifying key features requires an understanding of the products and, not only how it is used by customers, but also how is it not used. Features that are under-utilized but require significant ongoing support may need to be dropped.
Probably the most difficult step, choosing which features remain and what new features need to be developed has to take into account what are the expectations of the marketplace and weigh them against the up-front engineering expense, the per-unit production cost, and what alternatives provides and what competitors are doing.
The design team researches components and explores overall design approaches that seem to optimize between cost, reliability, serviceability and an appropriate feature set. For economic and development schedule reasons, not all features will make the cut (hence the need to order them).
Begin to develop in a top-down approach several different designs to see how then begin to flow. Often one design will leap ahead of the rest as a better or less expensive way. Pick it as the primary design.
Explore the designs with management and (very important) also with key customers to see how well their feature sets fit with their actual needs and requirements.
At this point, a design team may iterate back to an earlier step should, with management and customer feedback, it become obvious that none of the design alternative sufficiently meet expectations.
Once a design seems to be acceptable, the actual primary design phase begins. While it may feel as though the actual design work is a long time in coming, actually most of the difficult decisions have already been made, the complete function set is known, and it is just a matter of implementation. Backup designs can also be begun now or held off for a later time. Also, the design team should work with management to prepare contingency plans should something go wrong.
While the main design phase is underway, should any new information indicate that the results may not meet expectations, management should decide which earlier steps should be reviewed to make the necessary adjustments to bring the design back in line. In some occasions, an alternate design replaces the originally preferred design based on the new information. Within reason, it is much better to take some extra time to develop a product that is right for the marketplace rather than push throw with one that is known to be inferior.
When the design is complete, we move on to prototyping and testing.
Updating an old electronics design is still an electronics design process and can derail for any number of reasons. For updating a design, a design team must be sure to meet the important targets of feature set, backwards compatibility, production rates, delivery schedule and price points.
It is especially important to get one or more prototypes ready as soon as possible so that the targets can be evaluated by different groups such as management and key customers. These prototypes can also be used for showing to potential customers and demonstrating trade shows while production ramps up. At all times, be vigilant for discrepancies between the prototype and the marketplace’s expectations and acceptance and review Step 9 if necessary.
Should something go wrong — say, production doesn’t ramp up quickly enough to meet the delivery schedule – there is no need to panic. Management should have already developed contingencies such as using more expensive vendors but ones that can fill in the production schedule as necessary.
One area that is particular debilitating is so vast that is deserves its own section…
While we do not practice law or offer legal advice, this article would not be complete without a discussion about intellectual property, both developing it and being sure not to step on others.
If it comes to your attention that you are stepping on someone’s intellectual property, you might see what it will take to license it. If the patent assignee’s (owner) is not a direct competitor, you should find a warm reception since you will potentially be providing a new revenue stream.
Or, if you think the updated design improves on the current state-of-the-art for the product class in a novel and unobvious way, you might explore applying for a patent. We won’t tell you that patents are easy — they are not, but should you get one, you will have a government sanctioned monopoly on the invention disclosed in the patent for close to 20 years, hindering competitors and providing a cash flow from licensing.
Note Well: There are ongoing changes to both domestic and international patent law, and you need to be informed about the precise process you will have to follow. For example, as of this writing, a United States invention must have its patent filed before it is first offered for sale lest it jeopardizes its international validity.
In any case, should you feel that you are in such an industry or have a product that requires or steps on intellectual property, gather your design team and consult your patent lawyer.
Please consider DataPlex as your one-stop design team. Our products can be found in many different industries and chances our experience staff and proprietary design tools can get you a redesign in quick order. Also, with our being technical and having been successful in written what are now issued patents, we can help you document any new inventiveness so that you can more readily apply for intellectual property.
For more information, please visit:
Posted in Articles, Case Studies, Hardware Design, Project Management
Tagged ADC, CMOS, compatibility, components, DAC, economics, electronics, engineering, features, hardware, intellectual property, iteration, legal issues, LinkedIn, marketplace, microcontroller, microprocessor, old design, patent, price point, production, revenue, schedule, technology, TTL, updating designs
Volume 3, Number 1
Designing, implementing and managing a commercial website suitable for a modern-day company, firm or business enterprise has become both a software technology minefield and somewhat of an art form. While almost anyone with some basic web design experience can create a nice-looking website using off-the-shelf tools and some training, having a website perform precisely along certain desired lines to help grow a business is another matter indeed.
This article presents a case for a disciplined engineering approach to a website design, what we call “Website Engineering,” and includes a checklist of considerations, useful at various stages of the design and implementation phases.
The management of a firm might think that an in-house website development effort could both be cost-effective and yield high-quality results. Sadly, this is rarely the case. Most of these efforts are not successful because they are not provided enough time, planning or staff members with the necessary specialized training.
One reason why in-house efforts yield sub-par results is that the “minimal effort” to pull-off a successful website now involves several dissimilar technologies.
Every year, the bar moves up slightly where site visitors expect better performance and previously advanced features are now considered standard. A demonstration of the latter can be had by simply visiting a site that was designed ten years ago (example from ibm.com), before the advent of HTML 4 and Cascading Style Sheets (CSS) that “upped the bar” by allowing web sites to look like printed brochures. (For comparison, here is a modern-day IBM web page.)
Having a network technician or programmer on staff doesn’t necessarily mean that he (or she) knows which intricacies of website design and implementation would be required to best support the firm’s branding, promotional, sales and marketing activities. Conversely, having in-house graphic artists put together a site does not mean that they have the technical skills to develop the respective critical server-side elements such as databases, templates, scripts, security and access control for different types of site visitors nor able to effectively utilize such elements should they even already exist.
…a firm would benefit from having experienced developers approach their website’s design from more of a systems and software engineering perspective.
We submit that a firm would benefit from having experienced developers approach their website’s design from more of a systems and software engineering perspective. Inherently, engineer are trained to handle implementation pathways littered with technically advanced requirements and to resolve issues and solve problems that occur along the way. Also, such engineers can be conveniently called upon to address other technical issues beyond the scope of the website implementation.
Whether updating an existing site or starting from scratch, a firm should consider the following factors as they will influence the degree to which the resulting website is successful.
A first step for a firm is conducting an adequate amount of research in order to help define the role, expectations and metrics for the website. Here are a few questions to ask before any design work begins:
These are just a few preliminary questions that could be answered. Additional questions will arise depending on the characteristics of the firm, its industry, and its business procedures and the number of products or types of services, the size of its customer base, covenants, government regulations, and so on. A good design team will interview a firm’s management to determine the proper requirements for the site. Once the requirements are set, an implementation plan to create the site can be easily developed and then adopted.
The overall graphical interface of a firm’s website needs to be attention-grabbing enough to invite people in, but not so elaborate that it take the focus off the main reason they came in the first place. If the design elements overshadow content, viewers could tire of it quickly.
On the other hand, if the site is lacking in presentation or looks like it was developed in the 1990′s, some viewers may extrapolate this deficiency to mean that the firm generally is in need of updating and that the rest of its technology (in whatever industry it is in) may also be out of date.
The firm may have the best, most advanced products in the world, but without a properly produced website, visitor will never know. A good design team will help a firm achieve a balanced design that combines both form and function without either becoming overbearing.
Usability determines how well visitors to the firm’s site are able to find their way around. The following elements all need to be considered when addressing usability:
If visitors are impeded from being able to easily comprehend the firm’s site, they may quickly decide to move on, quite possibly to the sites of the firm’s competitors. A good design team will ensure that usability issues are properly addressed.
Sometimes too much detail in a large section of text, although accurate, can make readers grow tired.
The firm needs good content, but what does “good” mean? Whether it is repurposed marketing material or newly created web-specific content, it should be consistent and focused. Ideally, it should make clear points and be of enough quality to keep readers’ interest. Sometimes too much detail in a large section of text, although accurate, can make readers grow tired.
The content should be an easy read, easy to print and be structured and positioned well for easy scanning with time-saving connections to other areas of the site.A good design team will help a firm examine and constructively criticize its content, point out places where additional content could be advantageous, and ensure that only the content that meets the site’s philosophy is posted to the website.
HTML and XML serve as the most common base formats for web pages, and are responsible for representing the “look and feel” of content across the Internet. The raw “code” of HTML and XML looks very different from what you see in a browser, cryptic to the uninitiated, and when coupled with scripting languages, it becomes the domain of systems analysts and computer programmers. Improper coding and “bugs” will lead to internal and external website problems that degrade the visitors experience and the delivery of the firm’s message, no matter how otherwise great the presentation of the content.
Website problems can result in:
If a firm’s site is hamstrung even for just a short while, a firm could lose its audience’s trust in its site, or worse, itself. Depending on the agreed-upon services to be provided, the members of an experienced design team can ensure ongoing, well-formed website operation.
When world-class products are being designed, their producers are smart enough to solicit the right types of engineering so that the best possible product is made right out of the gate. Because of the short lifetimes of today’s products, there may not be a second chance.
Creating a website is an engineering effort, requiring an optimized balance between attractive design components and computer technology that has to strike a positive nerve when it is finally unveiled. As is often true in other engineering disciplines, the right approach requires some thinking, recognizing the requirements, and choosing the right tools, much of which may not be obvious.
As you can see, a website is much more than just the graphics and the content; it involves the hardware platform on which the site exists plus all of the software and hardware components required to provide the desired functionality — in other words, an engineering effort.
That “engineering” is required to produce an effective website should not be considered a disadvantage or a turn off. Instead, wrapping a website’s development around an engineering banner actually begins an expedient and cost effective process. For example, DataPlex engineers took over a website, unfinished for years, and completed it in less than four weeks with additional functionality along with significantly better usability.
In another case where a high level of software engineering was applied, DataPlex developed custom applications too advanced for implementation through traditional Internet markup languages and then seamlessly integrated them with the client’s website.
We include the points made above in a convenient checklist that a firm can use as a starting point or modify for its own website design purposes.
For the reasons presented in this article, a firm thinking of building a new website or redesigning an existing website should rely on “website engineers,” a qualified team of experts such as the designers and engineers at DataPlex to develop its site. In so doing, a firm will have the non-obvious considerations properly addressed. It will realize a high-quality site in a quick and professional manner, with the best possible usability, resulting in a high percentage of impressed website visitors, with corresponding benefits that match up to its goals.
For more information, please visit:
Posted in Articles, Business, Case Studies
Tagged checklist, content, experts, HTML coding, LinkedIn, planning, research, site usability, website, Website Design, website engineering
![]() |
|
The Original DataPlex DataKeeper |
In 1988, DataPlex startled the mobile computing market by introducing its DataKeeper, a then state-of-the-art personal computing device that featured a number of built-in modules: a world clock, tine billing and mileage logging for professionals, and an easy-to-use database manager. DataPlex stopped offering the DataKeeper commercially in 1998 but continues to support certain niche markets utilizing the DataKeeper because of its robustness and flexible architecture.
The Time Billing Tracker module was a huge success. It had single button timer activations and supported single button pausing and handling of interruptions. It had lists of user-definable Client and Project codes and optionally allowed users to make more specific notes for each entry. When the time billing information was downloaded to a PC, a DataPlex application produced billing reports for each client sorted by project and date. These reports could be printed and sent directly to a professional’s client or uploaded to a word processor for additional editing.
Although the database manager was designed to be a general purpose utility application, it quickly found its niche by being used by several customers to conduct surveys. DataPlex released a new module for the DataKeeper called Survey Manager with additional features for conducting surveys including where, at the end of the survey period, the survey information from each device would be downloaded to a central PC, consolidated, and summary reports produced.
In 1992, the Department of Public Works of the City of Burbank (Los Angeles County) because the first city agency to use a ruggedized version of the DataKeeper equipped with a new “Road Maintenance” module. City street information was uploaded to a series of DataKeepers and given to city workers to conduct real-time walking surveys of road and sidewalk conditions. The collected survey information was then used to schedule road and sideswalk repair. One city official said that the use of the DataKeeper improved the turnaround time for repairs by as much as 80%.
In the mid-1990’s, the DataKeeper received wireless communication capability where downloads of collected data could be accomplished without the need for cables and where survey information and votes could be monitored and analyzed in real-time. Around that time, several companies developed wireless ARS system packages specifically to handle surveys and votes in a localized region such as a meeting room or a conference hall.
The DataPlex DataKeeper had a novel design for a stepped power saving sequence that has been licensed to several Japanese firms. The stepped power sequence is now standard in all mobile computing devices: first power down or limit wireless communications when you can get away with it, then the CPU when there is no user activity, then the display for low-sleep mode, then the rest of the electronics for deep-sleep mode, then complete power-off (which occurred only rarely).
in 1994, a highly custom version of the DataPlex DataKeeper with motor control was created for artist George Stone’s “Man & Woman” art installation where two DataKeepers were used to memorize the four-dimensional movement of a shelf (3D space and time) and then play it back. In the artist’s studio, a male model stood on one platform and a female model stood on another platform while video cameras mounted on the shelves moved around the models in prescribed paths. Later, in the art installation, the video cameras were replaced by video monitors so, when the movement of the shelves was played back, viewers would be able to see on the monitors the previously taped portions of the male and female models, as though the monitors were windows onto the two models who were now invisible.