ABCs of Requirements Engineering Requirements engineering plays a fundamental role in the establishment of a release. Requirements engineering can be described as having five key areas of focus. This includes the ability to elicit requirements, document requirements, approve and baseline requirements, manage the requirements after approval, and trace from the requirements thru test.
|
||
Integrating an SCM Tool with a Java Development Platform: The IDE has emerged as the de-facto development tool in many Java shops. As the Java IDE evolved, team support became an important aspect of the tool and plays a prominent role in the popular Java development environment, IBM WebSphere Studio Application Developer 5.0 (WSAD). The clean design of the SCM interface to WSAD means configuration managers do not need to craft a custom solution to integrate their organization’s SCM tool with the IDE. |
Michael Sayko
November 30, 2005 |
|
Creating an SCM Plan to Support Iterative Software Development Since the establishment of software configuration management (SCM) as a formal engineering discipline, the written SCM plan has been accepted as an essential document for software development organizations. SCM engineers regard the plan as a description of the CM process and an enumeration of the CM procedures to be used on a project or program. Writing an SCM plan is often viewed as the first step in establishing the CM process for a new software development effort. |
Michael Sayko
November 30, 2005 |
|
Capacity Planning For Software Build Management Servers A software build management server is an integral part of the Application Lifecycle Management (ALM) infrastructure. A typical ALM infrastructure consists of a version control system, a bug or an issue tracking system, and a build server. Software build processes such as Continuous Integration and daily builds are highly IO, memory and computationally intensive. Dedicating adequate resources to the build management server ensures efficient software development. |
||
A High-Quality Plan What does it take to produce a high-quality product? A clear understanding of the customers' needs? Of course! Solid engineering work? Yes! Intensive testing? Naturally! Consistent practices? You bet! A committed, cohesive team? Without a doubt! Anything else?
|
Alan S. Koch
November 30, 2005 |
|
Levels of an SCM Product Evaluation and their Associated Risk Performing an SCM product evaluation is important so that the product selected meets the needs of the application being developed. Typically, there is not as much time spent evaluating SCM products as needed, even though an SCM product will be one of the more highly used tools in the application lifecycle. It is with this in mind that it is important to understand the levels of an SCM product evaluation and the level of risk each assumes. |
||
National Treasures of Agile Development Introduction |
||
Consistent Quality Requires Consistent Processes It was a restaurant my wife and I had passed many times, and we had always told each other, "We must try them some day." When we finally tried them, we were pleasantly surprised. The food, the service, the atmosphere, even the price were great! "This will be a regular stop for us," we agreed. But on our third visit, we had to send our food back twice. Another time, we waited nearly an hour for our order. Then, some time later, we were seated at a table that was not clean. Most of the time, things were great. But as we experienced sporadic problems, we visited that place less and less often. |
Alan S. Koch
November 30, 2005 |
|
The Journey Through Traceability to Process Control Taking a team from an undisciplined product development strategy, through an organized process with visible tracks, to a mostly automated, self-improving process is a long journey. It requires a good understanding of change, an adequate SCM tool or tool suite, good people for sure, and a lot of common sense. The journey is well worth the effort, though. I've been down the road more than once. It leads you to the path where you can manage properly and let the configuration management be handled automatically. |
||
Requirements Driven Development: A Stream-Based WBS Approach Requirements are a must have. Or should have. Maybe a want. OK, maybe not really requirements. When it comes down to it, you need to understand why you're building what you're building in sufficient detail so that you will know if what you built does the job. You also need full traceability to show that you have met the requirements. Developers work to a set of requirements, but these are not the same as the product requirements, which are again different from the customers' requirements. And what about ad hoc requests? Where do they fit in? |
Pages
Upcoming Events
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |
Jun 08 |
AI Con USA An Intelligence-Driven Future |
Sep 21 |
STARWEST Software Testing Conference in Anaheim & Online |