Various methods have been used to capture user requirements. They include use of models, prototypes, cases among other techniques. The traditional way of doing requirements analysis has not been sufficient since they have left the task of analysis to the developer yet the users will be the main users. The research evaluates previous studies that have evaluated past requirement capture methodologies and techniques
A comprehensive synthesis of requirement analysis and knowledge acquisition is provided by (Byrd et al. 1992). There has been a move towards joint participation in requirements elicitation process in information systems. User participation is being encouraged and automation of the process is being slowly adopted. Obstacles to eliciting requirements include within obstacles, between obstacles, among obstacles (Byrd, Cossick, and Zmud, 1992). The within obstacles occur due to individual limitations of both the user and the developer to process information and solve problems. The between obstacle occurs due to different level of understanding between developers and users. Inadequate knowledge of the problem domain, user’s lack of technical expertise and lack of a common language (davis 1982; valusek and Fryback 1985) are some of the major obstacles. The among obstacles occur due to different needs among different users hence requirements analysis is necessary in-order to weigh multiple needs and also a mechanism for negotiations in-order to agree on the needs is of great importance.
(Fazlollahi and Tanniru (1991) describe the contingency model. The contingency model is one of the traditional models used. The model offered a three step process that involved determining the level of uncertainty that exists in a system then ...
... middle of paper ...
... (Ed)
Information Systems Research: Issues, Methods and Practical Guidelines, Alfred Walker, pp. 144-162 .
Hansen, H. R. (1995) Conceptual framework and guidelines for the implementation of mass information systems, Information & Management, 28:2, pp. 125-142.
Isakowitz, T., Bieber, M. and Vitali, F. (July 1998) Web information systems, Communications of the ACM,41:7, pp. 78-80.
Lyytinen, K., Rose. G and Welke, R. (July 1998) The brave new world of development in the internetwork computing architecture (InterNCA): or how distributed computing platforms will change systems development, Information Systems Journal, 8:3, pp. 241-253.
Scharl, A. and Brandtweiner, R. (1998) A conceptual research framework for analysing the evolution ofelectronic markets, Electronic Markets, 8:2, pp. 39-42.
Systems Engineering Fundamentals. Defense Acquisition University Press, 2001
Controlled Requirement Expression (CORE) was developed for the British Aerospace programs while the UK Ministry of Defence was carrying out a requirement analysis (Hull et al., 2010). The fundamental component of the CORE methodology is viewpoints as different users see systems in different ways. There are many different stakeholders involved in a system; using CORE methodology involves finding all the different viewpoints of those stakeholders that have an interest in the system whether it’s a person, role or organisation ext.… (Sommerville and Sawyer, 2000). By organising viewpoints hierarchy it assists experts to read the scope and supports the analysis process. CORE Methodology is extensively used for real time system requirements specification.
This phase is the main focus of the project managers and stake holders. Meetings with managers, stake holders and users are held in order to determine the requirements like; Who is going to use the system? How will they use the system? What data should be input into the system? What data should be output by the system? These are general questions that get answered during a requirements gathering phase. After requirement gathering these requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be development is also studied.
...6. Fisher Center for Information Technology & Management, University of California in Berkeley. June 1995
Customized approach to provision the “Your Choice Furniture” of net technical requirements, most of the problems they face by the information system to help them solve.
This article is the results of research on StakeRare, Stakeholder- and Recommender- assisted method for requirements elicitation, a method that is used to identify and prioritize requirements for requirements elicitation using social networks and cooperative filtering. The article states that by using social networks and cooperative filtering three common problems large-scale requirements engineering can be alleviated. These problems are information overload, poor stakeholder input, and predisposed prioritization of requirements. Information overload is unavoidable in large projects as there can be many stakeholders and requirements. Poor stakeholder input due to not recognizing, or allowing enough time to stakeholder. Biased prioritization of requirements happens due to lack of system-wide perspective due to the size of the project. StakeRare uses social media to combat these issues by using collaborative filtering to gather knowledge from relevant requirements according to stakeholders, having stakeholders identify other stakeholders, and then uses stakeholders’ input to rate the requirements. The article evaluates the performance on StakeRare by testing the process on a large scale project the comparing the results in comparison to other elicitation methods.
After the systems planning is complete, the next course of action is the systems analysis phase. This phase includes defining the requirements of the system. This means that the team must conclude what the system needs to do in order to satisfy the users. This is done by forming a requirements...
The Requirements Analyst captures and validates environmental requirements in Context Analysis and in Rest-of-Scenario Analysis, conducted iteratively with Functional Analysis.
A documentation framework is essential for any large project; hence, RUP describes how to document functionality, constraints, design decisions and business requirements. Use Cases and Scenarios, are examples of artifacts prescribed by the process and have been found to be very effective at both capturing functional requirements and providing coherent threads throughout the development and deployment of the system.
Requirements are what the customers, users and suppliers wants from a system. This needs to be identified and determined based on the available information and agreed by customer and project stakeholders. Based on this what functional requirements must be implemented to support client business needs , what can these requirements do to effectively perform client’s business functions must be determined. Further what those non functional requirements can do to add any value to clients must be determined, since non functional requirements improve the overall user experience ,Moreover what are the limitations in implementing the requirements must be identified by the technical team based on technical limitations, less Return of Investment(ROI) due to changing trends etc.
Stair, R., & Reynolds, G. ( 200). Fundamentals of information systems second edition. 2nd ed. : Course Technology.
User participation has two distinct components: (1) user involvement which refers to subjective psychological state reflecting the importance and personal relevance that a user attached to a given system; (2) user participation which refers to the assignments, activities and behaviors that users or their representatives perform during the system development process (Tesch, D., Sobol, M., Klein, G., & Jiang, J., 2009). Hence, it is believed that the user participation has a big ...
Joint Application Development, sometimes referred to as Joint Application Design was developed for internal use at IBM by researchers Chuck Morris and Tony Crawford (Soltys & Crawford, 1995). It applies facilitated techniques that can be an effective tactic for eliciting and developing the require...
Since the development of the Internet in late 1980s, communication has changed enormously. The Internet has altered the lives of people in the world in a way that was never imagined before. As little as a decade ago, if someone tried to explain the Internet and World Wide Web, it would have been difficult, if not impossible, to understand. Computers were just beginning to become popular and few individuals realized the capacity of one PC, let alone the power of a network of electronic technology. By linking together computers, users could remotely access others on the network, share information, and send electronic mail as easily as pushing a button. Millions of people with shared interests, exchange information and build communities through Web sites, email and instant-messaging software.
As more companies that are leading technology are transforming from the traditional waterfall development model to an Agile software methodology, requirements engineering provides a process for software engineers to understand the problems they need to solve (Martin, Newkirk, & Koss, 2014). It is of key importance to understand the customer 's wants and needs before beginning designing or building the computer-based solution, as developing a solution that ignores the customer’s needs provides value to none of the parties involved. Thus, the intent of requirements engineering is to produce a written understanding of the customer 's problem (Pressman, 2010). Work products that are available to communicate this understanding include user scenarios, function and feature lists, analysis models, and specifications. This paper provides an evaluation of requirement patterns, an assessment of problem solving techniques most effective, a descriptive explanation of the patterns that includes a visual taxonomy, and an explanation of how the patterns identified are related.
This law explains the properties which a software development system should have while development of the software. The requirements phase gather the Information which assist in next phase of software engineering (software development). Requirement phase determines all the questions start from W such as after final development where the final product will be use, what type of users use it and what features or services it should provide. It is imperative to continue check and update the requirements up to when the appropriate requirements not finalize. Inadequate, incomplete or irrelative data or information of requirement may generates errors in next development phases of project. The main cause behind erroneous requirement definitions are distinct needs of several users groups and difference among their interest. (santhoshgoud, 2010)