Requirement Reuse Using Patternstaff.iium.edu.my/azlinnordin/fyp/pattern.pdf · Poster ID : RB-04-1...
1
Requirement Reuse Using Pattern Farah Nur Atiqah binti Suhaizad, Raida Rasyiqa binti Burhanudin Supervisor: Madam Azlin binti Nordin Kulliyah of Information Communication of Technology (KICT) International Islamic University Malaysia (IIUM). Poster ID : RB-04-1 Contact No : 017-7440519 019-2696112 Email: [email protected] [email protected] Requirement engineering (RE) helps to define clearly what the user wants, thus saving time and money. However, RE might take a lot of time if the project involves stakeholders. Requirement reuse using pattern helps in cutting the process of RE much shorter. This research investigates requirements reuse using pattern by applying and implementing the requirements patterns into domain specific application. We apply existing requirement pattern to write access control requirements and create new requirement pattern for domain specific requirements. The new pattern is being reviewed by expert to evaluate the quality. ABSTRACT INTRODUCTION • A study was conducted by Standish group, shown that 16% of small companies and only 9% of large companies were able to deliver their projects within budget and on time due to incomplete requirements and lack of user involvement during Requirement Engineering process [1]. • Apart from that, it has been revealed that the cost of fixing requirements-based problems kept incrementing rapidly the farther into software development they are discovered. • A pattern is a solution to the common issues and enabling the reuse of some techniques and strategies. Patterns can also be described in template form or in degenerate form. Meanwhile, Requirement Pattern can be defined as a reusable, experience based framework that helps requirement engineers to write or model better quality requirements in a possible less time [2]. • The aim of our study is to: 1) investigate requirements reuse technique specifically on requirements patterns. 2) to apply and implement the requirements patterns into domain application. • Research questions: 1) Does the approach of requirement reuse using pattern make the requirements complete without missing requirements? 2) Does the approach of requirement reuse using pattern can increase the quality of the requirements? METHODOLOGY CASE STUDY A. Derivation of Domain Specific Requirement Pattern Catalog C. Steps of Creating New Requirement Patterns B. Steps of Applying Existing Pattern 1) Make sure the pattern for the requirement exists. 2) Read through the whole pattern. The pattern can suggest what should be focused on and extra topics to consider. 3) Pay attention to the Extra Requirements. 4) Study the template given for each pattern. 5) Alter the templates to suit the system or organization. 6) Write the requirements based on the templates given. Figure 1: User Authentication Pattern Template DISCUSSION Challenges Benefits poor attention in the literature to experimentally address the benefits of requirement reuse using pattern late growth of trend difficult to find a good adaptation of pattern to fit desired context simple and easy to learn various pattern categories is recognized easily more views and recommendations to the related pattern shall be provided “faster time-to-market” benefit is proven to be true in real processes EVALUATION • Using patterns is an important applications as the rationales in decision-making and reporting review from a domain expert evaluated that, the use of requirement patterns in an experiment by the users to specify requirements of the application is very helpful • “Consideration for Development” and “Consideration for Testing” in the requirement pattern are being very helpful in order to evaluate the completeness of the requirements. • Prototyping Model is an example of a model that can be used to transform requirements into a prototype. steps in Prototyping Model: 1) Requirements Engineering 2) Preliminary or Quick Design 3) Build prototype CONCLUSION • By applying requirement reuse using pattern, it helps to boost analyst productivity by providing a great place to start and guidance. • In future works, we would like to apply the templates for generating use case maps to discover more patterns for both functional and non–functional requirements. • To develop an effective tool that can use the existing patterns and creating new requirement patterns. REFERENCES [1] C. Palomares, "Definition and Use of Software Requirement Patterns in Requirements Engineering Activities," pp. 1-7. [2] P. M. &. A. Ghazarian, "Patterns in the Requirements Engineering: A Survey and Analysis Study," WSEAS TRANSACTIONS on INFORMATION SCIENCE and APPLICATIONS, vol. 11, pp. 214-230, 2014.
Transcript of Requirement Reuse Using Patternstaff.iium.edu.my/azlinnordin/fyp/pattern.pdf · Poster ID : RB-04-1...
Requirement Reuse Using PatternFarah Nur Atiqah binti Suhaizad, Raida Rasyiqa binti Burhanudin
Supervisor: Madam Azlin binti NordinKulliyah of Information Communication of Technology (KICT)
International Islamic University Malaysia (IIUM).
Poster ID : RB-04-1Contact No : 017-7440519
019-2696112
Email: [email protected]
Requirement engineering (RE) helps to define clearly what the user wants, thus saving time and money. However, RE might take a lot of time if the project involves
stakeholders. Requirement reuse using pattern helps in cutting the process of RE much shorter. This research investigates requirements reuse using pattern by
applying and implementing the requirements patterns into domain specific application. We apply existing requirement pattern to write access control requirements
and create new requirement pattern for domain specific requirements. The new pattern is being reviewed by expert to evaluate the quality.
.
ABSTRACT
INTRODUCTION
• A study was conducted by Standish group, shown that 16% of
small companies and only 9% of large companies were able
to deliver their projects within budget and on time due to
incomplete requirements and lack of user involvement during
Requirement Engineering process [1].
• Apart from that, it has been revealed that the cost of fixing
requirements-based problems kept incrementing rapidly the
farther into software development they are discovered.
• A pattern is a solution to the common issues and enabling
the reuse of some techniques and strategies. Patterns can
also be described in template form or in degenerate form.
Meanwhile, Requirement Pattern can be defined as a
reusable, experience based framework that helps requirement
engineers to write or model better quality requirements in a
possible less time [2].
• The aim of our study is to:
1) investigate requirements reuse technique specifically on
requirements patterns.
2) to apply and implement the requirements patterns into
domain application.
• Research questions:
1) Does the approach of requirement reuse using pattern
make the requirements complete without missing
requirements?
2) Does the approach of requirement reuse using pattern
can increase the quality of the requirements?
METHODOLOGY
CASE STUDYA. Derivation of Domain Specific
Requirement Pattern Catalog
C. Steps of Creating New Requirement
Patterns
B. Steps of Applying Existing
Pattern
1) Make sure the pattern for the requirement
exists.
2) Read through the whole pattern. The
pattern can suggest what should be
focused on and extra topics to consider.
3) Pay attention to the Extra Requirements.
4) Study the template given for each pattern.
5) Alter the templates to suit the system or
organization.
6) Write the requirements based on the
templates given.
Figure 1: User Authentication Pattern Template
DISCUSSIONChallenges Benefits
poor attention in the literature to
experimentally address the benefits of
requirement reuse using pattern
late growth of trend
difficult to find a good adaptation of pattern
to fit desired context
simple and easy to learn
various pattern categories is recognized
easily
more views and recommendations to the
related pattern shall be provided
“faster time-to-market” benefit is proven
to be true in real processes
EVALUATION• Using patterns is an important applications as the rationales in decision-making and reporting
review from a domain expert evaluated that, the use of requirement patterns in an experiment
by the users to specify requirements of the application is very helpful
• “Consideration for Development” and “Consideration for Testing” in the requirement pattern are
being very helpful in order to evaluate the completeness of the requirements.
• Prototyping Model is an example of a model that can be used to transform requirements into a
prototype. steps in Prototyping Model:
1) Requirements Engineering
2) Preliminary or Quick Design
3) Build prototype
CONCLUSION
• By applying requirement reuse using pattern, it helps toboost analyst productivity by providing a great place to startand guidance.
• In future works, we would like to apply the templates forgenerating use case maps to discover more patterns for bothfunctional and non–functional requirements.
• To develop an effective tool that can use the existing patternsand creating new requirement patterns.
REFERENCES
[1] C. Palomares, "Definition and Use of Software Requirement Patterns in Requirements EngineeringActivities," pp. 1-7.
[2] P. M. &. A. Ghazarian, "Patterns in the Requirements Engineering: A Survey and Analysis Study,"WSEAS TRANSACTIONS on INFORMATION SCIENCE and APPLICATIONS, vol. 11, pp. 214-230, 2014.
