Register now or log in to join your professional community.
Patterns present solutions for recurrent problems in software engineering. They are applicable at
different stages of the software development process. This paper focuses on patterns at requirements and
analysis level. Although the term “requirements patterns” has appeared in the requirements engineering
community, the name “analysis patterns” is more established in the patterns community. Here we briefly
discuss these terms and the existing approaches. The main goal of this paper is to propose a new template to
fill some gaps concerning the specification of analysis patterns.
The traditional software development lifecycle includes the following phases: requirements elicitation,
analysis, design, implementation and test. Each phase creates a more detailed image of the system than the
previous one. Nevertheless, to be effective, software development must consider reuse since early stages.
Patterns are considered a successful technique to help reusing previous specifications and solutions.
Software patterns are classified in different categories depending on various factors including their application
to the software development phases (see Figure1). The most common patterns are analysis and design patterns.
Anti-patterns are a kind of pattern that embraces all the development phases (including the test phase), as well as
the project management area.For More detail click below link
