Recognize and Organize Patterns

Question: Discuss about the Recognize and Organize Patterns. Answer: Introduction Requirements engineering (RE) is one of the most significant phases in the Software Development Life cycle (SDLC). It comprises of elicitation, documentation and validation of the requirements and is the base of any project. The requirements that are associated with any software are categorized in to two categories as functional and non-functional requirements. It is necessary to understand, gather and analyze both of these requirement sets for the success of the project and achieve the required goals and objectives (Bochmann, 2016). The report discusses the evaluation of requirement patterns for a problem associated with software associated with the mobile phone and the assessment of problem solving technique most applicable to the scenario. A co-relation between the identified patterns has also been covered in the report. Requirement Patterns and Visual Taxonomy A pattern refers to the solution to a problem that exists in a particular system by making use of popular methods, techniques and strategies that have been previously stated and defined. There are multiple ways to describe the pattern associated with the system such as in the template form or in the degenerate or prose form as well. There are pattern languages developed on the basis of these defined patterns in order to understand the large problem space and requirements engineering is one application of the same. Software is defined as the set of programs and processes that are created and defined to perform a specific task. The following patterns help in the evaluation of the qproblem associated with the software of mobile phone (Ambler, 2016). Event Driven This is the pattern that is initiated only when a specific event occurs during the functioning of the software of the mobile phone. It will help to understand the root cause of the problem by coming up with the results of events that passed and the ones that could not go through (Konrad, 2016). This pattern makes use of when keyword. For instance, booting of phone when it is powered on Event Phone is powered on Pre-Condition Power button and hardware is functioning accurately Actor Mobile software Action Boot Capability Driven This requirement pattern will enable to understand the high level capabilities that are associated with the mobile phone software. This pattern makes use of shall be capable of capability. For instance, the software is capable of working correctly with the user interface (Roher Richardson, 2016). Event Phone is powered on and is booted Actor Mobile software Capability User interface is working correctly State Driven This is the requirements pattern that works on a specific state of the system and the mobile phone software in this case. This pattern makes use of while/during keywords. For instance, the software shall work accurately in the low power state as well and there shall be no variances with the normal battery mode (Srivastava, 2016). System State Low battery mode Actor Mobile software Action Make a phone call Object of Action Phone Management Pre/Post Condition This is the requirement pattern that works upon the set of pre condition and the post condition of the system. Start condition and the end result are specified in this pattern and will treat the mobile phone software as a black box. For instance, disk management functionality and the requirements associated with the mobile phone software in this regard can be determined with the help of this pattern (Palomares, 2016). Pre Condition More than 90% of the internal memory has been consumed Actor Mobile software Action Freeing up of disk space that is the internal memory Object of Action Internal Memory Post Condition After the freeing up of the disk space, a minimum of 20% of the memory space must be available Event Post condition is not met Actor Mobile software Action Sending the message Object of Action Error message Universal Attribute This requirement pattern states the fundamental properties that are associated with the mobile phone software. These properties exist with the software at all times. For instance, the security features are a part of all mobile software in the present era. The software must prevent any unauthenticated or unauthorized access to the system (Spinoza, 2016). Actor Mobile software Action Prevent unauthorized and unauthenticated access to the system Object of Action Mobile data and information Assessment of most Effective Problem Solving Technique Pattern matching and evaluation is an effective problem solving technique in the case of faulty mobile phone software. The event driven and state driven pattern aids in the assessment of the specific problems that are present in the system. These patterns also aid in the assessment of specific problems associated with the functional, user, system and non-functional aspects of the system. Before carrying out the pattern recognition technique for problem solving, decision making strategies such as SWOT (Strengths, Weaknesses, Opportunities and Threats) can also be carried out to understand the system and its features in a better manner. Relationship between the Patterns The patterns that have been defined earlier in relation with the problem associated with the mobile phone software have a great degree of co-relation and similar aspects between each other. All of these patterns that have been identified have a common actor as the mobile software and work on the event or state driven approach. These patterns also have a specific keyword present which helps in understanding the identified pattern and the results in a simpler way. Also, the problem-solving and decision making abilities depend on the results that are retrieved from each set of pattern. The objective associated with each pattern is also the same and every pattern aims to come up with a solution to the problem associated with the software. References Ambler, S. (2016). Requirements Engineering Patterns. Dr. Dobb's. Retrieved 8 September 2016, from https://www.drdobbs.com/requirements-engineering-patterns/184414612 Bochmann, G. (2016). Basics : the Requirements Engineering Process. Retrieved 8 September 2016, from https://www.site.uottawa.ca/~bochmann/SEG3101/Notes/SEG3101-ch1-2%20-%20Basics%20-%20the%20RE%20process.pdf Konrad, S. (2016). A Requirements Patterns-Driven Approach to Specify Systems and Check Properties. Retrieved 8 September 2016, from https://ftp://ftp.cse.msu.edu/pub/serg/requirements/spin03.pdf Palomares, C. (2016). Definition and Use of Software Requirement Patterns in Requirements Engineering Activities. Retrieved 8 September 2016, from https://ceur-ws.org/Vol-1138/ds3.pdf Roher, K. Richardson, D. (2016). Sustainability Requirement Patterns. Retrieved 8 September 2016, from https://www.ics.uci.edu/~kroher/Kristin_Roher/Home_files/rews13repa-id6-p-18156-preprint.pdf Spinoza,. (2016). Requirements pattern | Software Specification | Ontology | Requirements Specification. Chambers.com.au. Retrieved 8 September 2016, from https://www.chambers.com.au/glossary/requirements_patterns.php Srivastava, S. (2016). A Repository of Software Requirement Patterns for Online Examination System. Retrieved 8 September 2016, from https://www.ijcsi.org/papers/IJCSI-10-3-2-247-255.pdf