| ||||||
Implementation:General DesignNow that your house's architecture is decided on, it's time to make sure that all the rooms open to one another and that the water pipes run pretty close to the sinks. In the world of systems development, that step is called General Design. General Design consists of defining the "big chunks" of the system in terms of what they do and how they interact with each other. You can think of the "big chunks" as the the various rooms of the house and the General Design as describing what purposes each room will serve. Additionally, it means the organization of the rooms into a coherent whole. (For example, it would probably be a bad idea to place all of the bedrooms on the second floor and all of the bathrooms on the first.) Depending on the complexity of the system, there can be a lot of pitfalls in a general design, many of which may go unnoticed...at least until the system is turned on. Let Elbow Technologies share their wealth of experience in helping make your General Design a sound one. If you want, we'll even show you our scars for the mistakes we have made in the past, so that you don't have to make them in the future. Detailed DesignOK, we have decided on the building materials (Architecture) and how the rooms will be related (General Design), so now it must be time to finally build, right? Sorry! not quite yet. We still need to be sure that a good solid approach is used for construction, regardless of who is on the crew. That's where Detailed Design comes in. By putting in writing the details of how to construct each "big chunk" identified and defined in the General Design, you can 1) improve the chances that the actual coding is performed in a uniform and high quality fashion and 2) have the documentation needed when it comes time to enhance the system and the original builders are no longer with your firm. CodingWhen it finally gets time to build, make sure that you use personnel that think about future maintainability as least as much as about the immediate goal at hand. Lack of such foresight represents one of the major causes of Y2K concerns. And if extra manpower is what you need to accomplish this step, Elbow Technologies is ready to lend a hand, providing the additional resources to produce well-commented, maintainable code. Testing and RolloutMany people think of the finishing of the coding as the last step in a project lifecycle. Oh! would that is were so. In fact, proper final testing and a well considered rollout plan are just as important as the steps above. Without proper pre-release testing, your client base unwittingly becomes your testers. And, unless you are incredibly lucky, two thing are true: 1) despite best efforts, there will be implementation mistakes and 2) your customers will find them...whether they wanted to or not. Don't risk your company's reputation by skimping on testing.Lastly, a controlled, well-plan delivery of your product is essential to conveying your company's technological competence to your customer-base. Help them believe that your company knows what is doing, by having your company actually know what it is doing (we know, a radical concept). And let Elbow Technologies, with its extensive experience and know-how in these areas help you get it right. |
Send mail to webmaster@elbowtech.com with
questions or comments about this web site.
|