Aspect-oriented requirements engineering (AORE) is a new methodology that can help us improve the analysis, structure, and cost of development of software requirements. AORE does not replace but rather complements any of the existing requirements methodologies. This two-part paper explains to software practitioners the AORE concept, illustrates how it can be applied on software projects, and discusses the benefits of AORE. Part I focuses on the AORE analysis techniques.
Writing requirements purely top-down or only bottom-up is risky to say the least. The devil's in the details, and those details are likely to be missed when working from a single direction. What if you could tackle your requirements from both directions by incorporating use cases and user centered design? Learn how balancing your approach to writing requirements can result in more detailed, pragmatic documentation.
Trying to communicate with businesspeople about requirements can make you feel like you're from another planet. Using concrete examples expressed as storytests to drive the development of a system can help bring you back into the same orbit. Discover ways to introduce this process on your next project.
One school of thought says each should do what he's best at and no more. But one company has graduated to a new way of life. Instead of isolating testers and business analysts, the two teams are melded into one—resulting in a more robust product created in less time at a reduced cost. Could this hybrid approach work for you?
Fashioning a new requirements method is an almost impossible task, given budget and time constraints. But that doesn't mean you have to be stuck with an ill-fitting process. Learn about seven alterations that almost any organization can make.
This application tool allows non-programmers to produce working prototypes of Windows, or Web-based, database-driven applications. Read on to find out how this new tool makes protoyping a viable part of the IT software development process.
Chances are you won't be able to deliver on everything your customer wants. Asking good questions at the beginning of a project can help you determine where your customer wants to go. Although you may not be able to give them everything they want, if you are able to deliver the top ten things on a list of fifty items you've still delivered value. Keeping the lines of communication open is essential to helping you achieve your project goal.
Translating customer requests into software requires exploration, learning, and discovery. As such, this Reference Point lists resources you can use to learn more about requirements exploration and modeling. Ellen Gottesdiener—a recognized authority on software requirements—provides her top recommendations for books, journals, and online resources on the subject.
If you buy a hammer, you are not considered a master carpenter automatically. The same holds true for tool knowledge alone solving requirements problems. Kelley Schmidt shares the biggest lesson she learned on a project: commercial process and tools alone cannot lead to project success.