Showing posts with label software. Show all posts
Showing posts with label software. Show all posts

Friday, October 16, 2009

Secrets of Successful Software Requirements

Source: www.millionslink.com

By: Igor Jese, Wed May 23rd, 2007
Introduction Although most companies do some form of requirements, there is often a lack of understanding as to exactly why the requirements need to be created and the level of detail that should be included in the requirements. Software is always created to solve a need for a client. The client may be an internal client, an external client, or even the general public. Detailed requirements are important to ensure that a program correctly and fully addresses client’s needs. Detailed requirements make initial development easier and faster because the developers know exactly what should be developed and do not need to make their best guess at the functionality to be implemented or delay development by creating requirements during development. Giving the developers accurate requirements will also result in less rework at the end of development because the stakeholder’s requirements will have been implemented correctly initially and will not be arrived at through trial and error. A project manager can use the detailed requirements to create accurate timelines and give correct estimates to the client. This ensures that stakeholders are completely aware how long development will take so they can adjust the scope of a project or proactively add resources if necessary. Finally, testers can use the requirements to create test plans while development is ongoing rather than waiting until development is complete. The requirements give them information about what the program will do so there cannot be disputes between developers and testers as to what the program functionality should be. High quality requirements also describe problem paths that may need additional testing. Even though highly detailed requirements make development easier in future phases, this is not always possible due to time constraints imposed by the client or market conditions. With this in mind, let’s look at some secrets to improve your requirements process even under tight deadlines. Secret #1 – Include Use Cases Use cases look at the requirements from the standpoint of an end user working with the program and how the program responds to the user’s inputs. At its simplest level, a use case can be thought of as a play where the end user is one actor and the program is another actor. These two actors then have dialogs which explain the interactions between the actors. More complicated scenarios can have additional actors including other programs, other types of users, and even hardware. Use cases have proven to be very easy to read and understand even for non-technical clients. Each use case explores what happens when something goes wrong in addition to the “normal” interactions. The exploration of these failure conditions is very important because these cases are the most difficult to code and can cause the most amount of testing. Traditional requirements often ignore these cases. It can be helpful to have developers and testers both think of additional possible failures in a use case so they can be fully documented in the requirements. Use cases do not provide a complete picture of the system though. A technical specification should also be included in the requirements to detail formulas and routines that take place behind the scenes. Secret #2 – Prototype Screens with a Design Tool A user of the program only interacts with a program through the user interface so it makes sense to spend a significant amount of time during requirements to ensure that the user interface makes sense, that all functionality is included, and that the most commonly used functionality is easily accessible. The easiest way of doing this is using a screen prototype. There are a variety of methods of making screen prototypes which range from simply drawing the interface with a pen and paper to building “working” prototypes in a higher level language like Visual Basic which allows rapid screen design. However, each of these extremes has serious drawbacks. A pen and paper prototype does not allow users to interact with the prototype and it is more difficult to change. A “working” prototype done in a programming language like Visual Basic can lead the client to believe that the program is nearly complete and that development should not take very long or it can lead the client to believe that changes to the prototype will be costly making them reluctant to make necessary suggestions to improve the program. Between these two extremes lies screen design applications which allow you to draw the screens and model interactions between screens. High quality prototyping tools allow you to enter sample data and allow users to move between screens by pressing buttons so they can easily understand the interface and its functionality. Most prototyping tools produce the final output in an HTML format so they can be easily shared even if a client is not in the same office where requirements are being developed. When looking for a prototyping tool, make sure to select a tool which is easy enough to use that you can easily prototype screens while your customer is in the room. This will allow you to brainstorm and make changes to the screens without delays. A prototyping tool should already have common controls already defined to maintain design standards and improve the appearance of your screens. Being able to enter sample data in each screen can allow the customer to pinpoint areas that may be incorrect. Secret #3 – Work Directly with End Users When designing a new application or making revisions to an existing application, there is no substitute for the direct experience that end users have. An end user can give immediate feedback on your design to point out awkward or incorrect functionality. They also help to ensure that all controls are logically placed for the most efficient use of the system. Using an interactive prototyping tool allows you to walk a user through the interface or even allow them to work directly with the prototype so they can quickly suggest improvements. As use cases are being developed, it is a good idea to walk users through the use case to ensure that the use case is well thought out and that all functionality is captured both in the use case and the prototype. Secret #4 – Do Iterative Requirements Development When you create requirements, it is important to develop the requirements in multiple stages. For example, you may want to do a general layout of the program and create higher level use cases in the first session to get a feel for the overall requirements. In the next session(s), you can focus on each key feature to ensure that the normal paths are all defined in the use cases and further refine the prototypes. In the next session(s), you can attempt to define all of the error conditions which can occur and update the prototypes as necessary. The final sessions should review all work previously done to ensure that all requirements are clear and complete. At each stage, you should not be afraid to revise work done in a previous step because getting the requirements correct will ultimately save time in the more costly development and testing stages. Secret #5 – Place Requirements Documents under Change Control With all of the time spent on generating clear requirements, it is very important to make sure that all of the requirements documents are included in your change control system. This includes use cases, screen prototypes, technical specifications, and any other documents used to define the requirements. Conclusion In this article, we have explored various secrets to make your requirements process successful and ensure that your clients are satisfied with the resulting program even under tight deadlines. At the start of your next project, make sure you have the proper tools in place for a successful requirements iterations including a prototyping program, a tool to write use cases, and a version control program. These tools do not have to be expensive, and they will help to get your requirements right and schedule under control. About the Author Igor Jese works in software development since early 1990s, with emphasis on software requirements and development methodology. He is a certified Software Requirements Expert and Project Management Professional, and also the author of Mockup Screens (www.MockupScreens.com), a popular tool for quick GUI prototyping.

The Benefits of Using Estimating Software

Source: www.millionslink.com


By: George Hague, Thu May 24th, 2007
Years ago, electrical contractors had no choice but to estimate the old-fashioned way, using their intuition, their guts, and a hand-cranked adding machine. It wasn’t until the 1970s that the personal computer stood ready to push the technology envelope. Yet even today, with a variety of software tools available, many contractors still go by the seat of their pants when it comes to bidding jobs. No task affects as many areas of electrical contracting as the task of estimating. There are six primary reasons why estimating software is critical to today’s electrical contractor: 1. Speed 2. Accuracy 3. Consistency 4. Procurement 5. Project Management 6. Professionalism Speed: The foremost benefit of using computerized estimating is speed. No other software product in your business saves as much time and money as your estimating software. Since a computer is basically just a super-fast number cruncher, it is particularly well suited to the task of estimating. Accuracy: In today’s industry and changing economy, contractors need to track actual labor and material costs as well as equipment and subcontract expenses. They need to keep tabs on back orders as well as installed and stored materials. This process begins with the estimate. The owner and chief estimator will use the estimate to determine the job’s true cost and to develop a selling price. A disturbing comment heard too often is,“I can beat any computerized estimating system doing it the old fashioned way…even if we do sometimes find ourselves in a labor crunch at the end of the project.” Think about the irony in that philosophy: Sure, the estimating department can quickly crank out a number that will win the contract, but then the management team has to scramble to figure out how they’re going to meet that estimate’s labor schedule. Where is the advantage in that? For these contractors, it’s almost as though estimating is nothing more than a necessary evil to get the contract. They might as well pull a number out of a hat. At the other end of the spectrum, you can find contractors who have established convoluted procedures involving everything from maze-like scheduling boards with magic marker hieroglyphics and magnetic pins, to unreadable scraps of paper plastered with sticky notes. In their attempts to be as thorough as possible, they only create chaos, resulting in wasted time and devastating mistakes. If either scenario sounds like business as usual at your company, it might be time to take a closer look at estimating software. Consistency: Using an estimating system allows the estimator to prepare estimates that use the exact same procedures and values, time after time. In addition, it provides a basis for comparison of the estimate to the actual job cost. Retaining a history of job costs gives the estimator the tools necessary to adjust future estimates and avoid costly overruns, or to point out cost-saving procedures. Without specific, consistent procedures, an estimate is little more than a guess. Procurement: The project manager will use the estimate to determine labor resources, equipment and subcontractor requirements to properly schedule and track job progress. The purchasing department will find it just as useful in scheduling timely delivery of materials. Project Management: The foreman will use the estimate to help oversee installations, and to requisition stock. The electrician and apprentice will review the estimate to gain an understanding of how the estimator took off specific installations, while the accounting department will use the estimate to prepare the schedule of values and track job costs. Computers can help contractors perform the diverse tasks of estimating, project management, correspondence, and purchasing more efficiently. Professionalism: In addition to speed, precision, accuracy, and consistency, computerized estimating delivers a higher level of professionalism. Today’s contractors use estimating programs to organize and optimize their business. The estimate is used as a sales tool to document costs, and there is nothing that builds confidence in your sales presentation more than an estimate that has been professionally prepared and printed using an estimating software system. Electrical estimating software systems are evolving into smarter and faster tools that help the estimator make decisions…decisions such as automatically adjusting labor units by calculating the installation difficulty factor for each item, rather than using one factor for an entire installation. An estimating program should have the ability to correct conduit sizes, and fix installations using the National Electrical Code tables. A good estimating system should quickly and accurately help you determine the bottom line cost of a job, and ultimately increase your profit margin. The rise of computer estimating has forever changed the face of electrical contracting. It has lessened the estimator’s workload and liability while increasing accuracy and profitability. It has cut overhead by up to 75% while freeing employees to concentrate on other revenue-generating activities. The ROI is measured in months rather than years. Studies indicate that most contractors today are using computers, and that many are on their second and third generation of estimating products. These contractors have seen the clear advantage computers can give them, and are working that advantage for all it’s worth. Keep in mind that some of these contractors are your competition. Gain a competitive edge by computerizing your estimating department today! Written by George Hague President & CEO of ConEst Software Systems www.conest.com