Preview

Markus K

Powerful Essays
Open Document
Open Document
32739 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
Markus K
Capturing Requirements Meeting Customer Intent:
A Structured Methodological Approach

Markus K. Gröner

Dissertation submitted to the Faculty of the
Virginia Polytechnic Institute and State University in partial fulfillment of the requirements for the degree of

Doctor of Philosophy in Computer Science and Applications

Approved:

_________________________
James D. Arthur, Chair

__________________
J.A.N. Lee

__________________
Richard E. Nance

__________________
Linda H. Rosenberg

__________________
MaryBeth Rosson

May, 2002
Blacksburg, Virginia

Keywords: Requirements Engineering, Software Engineering, Methodology

Copyright 2002, Markus K. Gröner

Capturing Requirements Meeting Customer Intent:
A Structured Methodological Approach

Markus K. Gröner

(ABSTRACT)

Product quality is directly related to how well that product meets the customer’s needs and intents. It is paramount, therefore, to capture customer requirements correctly and succinctly. Unfortunately, most development models tend to avoid, or only vaguely define the process by which requirements are generated. Other models rely on formalistic characterizations that require specialized training to understand. To address such drawbacks we introduce the Requirements Generation Model (RGM) that (a) decomposes the conventional “requirements analysis” phase into sub-phases which focus and refine requirements generation activities, (b) constrains and structures those activities, and (c) incorporates a monitoring methodology to assist in detecting and resolving deviations from process activities defined by the RGM. We present an empirical study of the RGM in an industrial setting, and results derived from this study that substantiate the effectiveness of the RGM in producing a better set of requirements.

ACKNOWLEDGEMENTS
I am forever thankful for the wisdom and guidance my advisor Dr. James D. Arthur has provided me over the past seven years. He and I have spent an incredible number of hours together in



References: P. Mambrey, R. Oppermann, and A. Tepper, Computer und Partizipation: Ergebnisse zu Gestaltungs- und Handlungspotentialen. Opladen: Westdeutscher Verlag GmbH, 1986. John Wiley & Sons, 1976. IEEE Software, vol. 4, pp. 19-24, 1987. York, NY: Macmillan Publishing Company, 1987. York, NY: McGraw-Hill, 2001. England: Addison-Wesley, 1999. 25-35, 1984. and Techniques," presented at WESCON, 1970. Addison-Wesley, 1996. Publishing Co., 1996. Natural Language Requirements Specifications," presented at 14th Annual Pacific Northwest Software Quality Conference, Portland, 1996. Inc., 1985.

You May Also Find These Documents Helpful

  • Powerful Essays

    Cis518 Assignment 2

    • 776 Words
    • 4 Pages

    The reason that I am using this technique, many software teams discovered that mixing use-case modeling techniques for requirements expression along with traditional methods of documenting specific requirements within a “software requirements specification” (SRS) document provides an efficient means to record the complete set of detailed requirements for a system or application to be built.…

    • 776 Words
    • 4 Pages
    Powerful Essays
  • Satisfactory Essays

    EXAM 5 AIS

    • 1909 Words
    • 18 Pages

    Which development phase has the purpose of developing specifications for the new or revised system?…

    • 1909 Words
    • 18 Pages
    Satisfactory Essays
  • Powerful Essays

    Design Unit 11 Task 3

    • 1386 Words
    • 11 Pages

    provides a brief overview of the product defined as a result of the requirements elicitation process.…

    • 1386 Words
    • 11 Pages
    Powerful Essays
  • Powerful Essays

    Scope Plan

    • 2253 Words
    • 10 Pages

    1. Collect Requirements – Collecting requirements defines and documents requirements needed to meet all project objectives. To begin collecting requirements the project team should leverage the project charter and stakeholder list. Starting with the inputs, the team should identify requirements, research details to accomplish the requirements, detail the requirements, and determine measurable criteria to monitor the requirements. Refer to the Requirements Traceability Framework. Document the tools and techniques used to…

    • 2253 Words
    • 10 Pages
    Powerful Essays
  • Satisfactory Essays

    New System Proposal

    • 400 Words
    • 2 Pages

    Let us look at an example of a business requirement that could become a project. Suppose a global business has recently expanded its manufacturing locations into a new country, Czech Republic, which will add about 100 local employees. These 100 employees need to access the company’s global systems, which the employees can only read and understand the Czech language. The requirements should be developed by first looking at how big a problem it would be if no changes were to happen and could the employees be able to perform their job responsibilities. These tasks are defining and understanding the problem. Next would be to find possible solutions to the problem, so maybe employees need access to three different systems. The question will be whether the one system should get updated with the appropriate language, or if not available, a person with English and Czech language knowledge can assist users. Many variations of solutions can be available, so it also requires knowing the cost and maintenance of the solution in order to know if the project should get created.…

    • 400 Words
    • 2 Pages
    Satisfactory Essays
  • Satisfactory Essays

    paper

    • 10796 Words
    • 44 Pages

    Software Requirements Specification Amazing Lunch Indicator Sarah Geagea 881024-4940 Sheng Zhang 850820-4735 Niclas Sahlin 880314-5658 Faegheh Hasibi 870625-5166 Farhan Hameed 851007-9695 Elmira Rafiyan 840724-5383 Magnus Ekberg 851022-1933 Table of Contents 1. Introduction ............................................................................................................................................... 1 1.1 Purpose................................................................................................................................................ 1 1.2 Scope ................................................................................................................................................... 1 1.3 Definitions, acronyms, and abbreviations ........................................................................................... 1 1.4 References ........................................................................................................................................... 2 2. Overall description .................................................................................................................................... 4 2.1 Product perspective ............................................................................................................................. 4 2.2 Product functions ................................................................................................................................ 4 2.3 User characteristics .............................................................................................................................…

    • 10796 Words
    • 44 Pages
    Satisfactory Essays
  • Satisfactory Essays

    Use Cases

    • 9692 Words
    • 39 Pages

    Customers and end users have goals (also known as needs in the UP) and want computer systems to help meet them, ranging from recording sales to estimating the flow of oil from future wells. There are several ways to capture these goals and system requirements; the better ones are simple and familiar because this makes it easier—especially for customers and end users—to contribute to their definition or evaluation. That lowers the risk of missing the mark. Use cases are a mechanism to help keep it simple and understandable for all stakeholders. Informally, they are stories of using a system to meet goals. Here is an example brief format use case: Process Sale: A customer arrives at a checkout with items to purchase. The cashier uses the POS system to record each purchased item. The system presents…

    • 9692 Words
    • 39 Pages
    Satisfactory Essays
  • Satisfactory Essays

    1. Determination of requirements (Requisitions) – By user - The user department responsible can pass a…

    • 834 Words
    • 4 Pages
    Satisfactory Essays
  • Powerful Essays

    Requirements traceability is the ability to follow the life of a requirement, in both forward and backward direction, i.e. from its origin, to its refinement and inclusion in the requirement specification document, and from there to its subsequent deployment in coding, testing and validation [1]. Requirement traceability is often divided into Pre-Requirement Traceability and Post-Requirement Traceability. Pre-Requirement Traceability is concerned with requirement’s life before its inclusion in the requirement specification, while Post-Requirement Traceability is concerned with the requirement’s life after its inclusion in the requirement specification.…

    • 3789 Words
    • 16 Pages
    Powerful Essays
  • Better Essays

    system analyst

    • 1451 Words
    • 5 Pages

    Defining Requirement: The basic step for any system analyst is to understand the requirements of the users. This is achieved by various fact finding techniques like interviewing, observation, questionnaire etc. It involves interviewing users and finding out what information they use in current system and how they use it, what information they lack, which if provided will allow them to do their job better. The analyst then determines how such information can be generated.…

    • 1451 Words
    • 5 Pages
    Better Essays
  • Good Essays

    This method is based on an iterative and incremental development model. As requirements are not clear when project is commenced so requirement evolution process is done through iterative and incremental activities and this model is useful in all phases.…

    • 620 Words
    • 3 Pages
    Good Essays
  • Good Essays

    Customer Needs in e-Services 32 interpretation. Journal of Advertising Research, 28(1), 11-29. Schreiber, A. T., Akkermans, J. M., Anjewierden, A. A., de Hoog, R., Shadbolt, N., Van der Velde, W., et al. (2000). Knowledge engineering and management. Cambridge, MA: MIT Press. Sharp, H., & Galal, A. F. G. (1999). Stakeholder identification in the requirements engineering process. Proceedings of the 10th International Conference and Workshop on Database and Expert Systems Applications (DEXA 99), Florence, Italy. Stefik, M. (1995). Introduction to knowledge systems. San Francisco, CA: Morgan Kaufmann. Stephens, S. A., & Tripp, L. L. (1978). Requirements expression and verification aid. Proceedings of the 3rd international conference on Software engineering (ICSE 1978), Atlanta, Georgia. Teare, R. E. (1998). Interpreting and responding to customer needs. Journal of Workplace Learning, 10(2), 76-94. Van Lamsweerde, A. (2000). Requirements engineering in the year 00: A research perspective. Proceedings of the 22nd International Conference on Software Engineering, Limerick, Ireland. Van Lamsweerde, A. (2001). Goal-oriented requirements engineering: A guided tour, invited minitutorial. Proceedings of the International Joint Conference on Requirements Engineering (RE’01), Toronto, Canada. Van Lamsweerde, A., Darimont, R., & Letier, E. (1998). Managing conflicts in goaldriven requirements engineering. IEEE Transactions on Software Engineering, 24(11), 908–926. Vasarhelyi, M., & Greenstein, M. (2003). Underlying principles of the electronization of business: A research agenda. International Journal of Accounting Information Systems, 4(1), 1-25. Xue, M., Harker, P. T., & Heim, G. R. (2003). Incorporating the dual customer roles in e-service design (working paper no. 03-04, retrieved august 2004 from http://fic.Wharton.Upenn.Edu/fic/papers/03/0304.Pdf). Zeithaml, V. A. (1988). Consumer perceptions of price, quality, and value: A means-end model and synthesis of evidence. Journal of Marketing, 52(3), 2-22. Zeithaml, V. A., & Bitner, M. J. (1996). Services marketing. New York, NY: McGrawHill. Zeithaml, V. A., Parasuraman, A., & Berry, L. (1990). Delivering quality service: Balancing customer perceptions and expectations. New York, NY: The Free Press.…

    • 15481 Words
    • 62 Pages
    Good Essays
  • Good Essays

    * Businesses operate in a fast –changing requirement and it is practically impossible to produce a set of stable software requirements…

    • 690 Words
    • 3 Pages
    Good Essays
  • Good Essays

    miss

    • 855 Words
    • 4 Pages

    identify further requirements. T his process is then repeated, producing a new version of the software at the end…

    • 855 Words
    • 4 Pages
    Good Essays
  • Powerful Essays

    Functional requiements had described the details of each modules. Requirements analysis is an important part of the system design process. Once the client 's requirements have been identified and facts collected, we are then in a position to design a solution.…

    • 783 Words
    • 4 Pages
    Powerful Essays