Preview

Impact of Organizational Structure on Distributed Requirements Engineering Processes: Lessons Learned

Powerful Essays
Open Document
Open Document
2822 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
Impact of Organizational Structure on Distributed Requirements Engineering Processes: Lessons Learned
Impact of Organizational Structure on Distributed Requirements Engineering Processes: Lessons Learned
Brian Berenbach
Siemens Corporate Research, Inc. 755 College Road East Princeton, New Jersey 08820 +1 609-734-6500

brian.berenbach@siemens.com ABSTRACT
The requirements engineering program at Siemens Corporate Research has been involved with process improvement, training and project execution across many of the Siemens operating companies. We have been able to observe and assist with process improvement in mainly global software development efforts. Other researchers have reported extensively on various aspects of distributed requirements engineering, but issues specific to organizational structure have not been well categorized. Our experience has been that organizational and other management issues can overshadow technical problems caused by globalization. This paper describes some of the different organizational structures we have encountered, the problems introduced into requirements engineering processes by these structures, and techniques that were effective in mitigating some of the negative effects of global software development. projects in the large, and specifically distributed requirements engineering efforts. The requirements engineering (RE) competency center at Siemens Corporate Research in Princeton has had the unique opportunity to participate in large, global projects with different organizational structures. Each structure brought different challenges, benefits and issues. In the following sections, I will describe some of the structures we encountered, problems caused by the organizational structures, and, finally, I will suggest techniques for mitigating the problems encountered.

2. ORGANIZATIONAL STRUCTURES
Organization in this paper has a very specific meaning. It refers to the leadership and/or management of a specific area. If for example, there are analysts at a remote site but they all report to and are managed by one



References: [1] Damian, D.E.H.; Eberlein, A.; Woodward, B.; Shaw, M.L.G.; Gaines, B.R., "An empirical study of facilitation of computer-mediated distributed requirements negotiations”, Proceedings of the Fifth IEEE International Symposium on Requirements Engineering, 2001 , vol., no.pp.128-135, 2001 [2] Damian, D.E.; Eberlein, A.; Shaw, M.L.G.; Gaines, B.R., “An exploratory study of facilitation in distributed requirements engineering,” Requirements Engineering (2003), vol.8, no.1, p.23-41.

You May Also Find These Documents Helpful

  • Better Essays

    An organizational structure refers to the way that an organization arranges people and jobs so that its work can be performed and its goals can be met. When a work group is very small and face-to-face communication is frequent, formal structure may be unnecessary, but in a larger organization such as Barnes and Noble, decisions have to be made about the delegation of various tasks. Thus, procedures are established that assign responsibilities for various functions. It is these decisions that determine the organizational structure.…

    • 1089 Words
    • 5 Pages
    Better Essays
  • Powerful Essays

    In corporate America projects are implemented on a regular basis. With implementing these projects there is a grave possibility that they may not be successful. In conducting any successful project it takes some type of organizational skills. Successfulness of a project can be jeopardized by a lack of planning, not enough funds to complete it, or the materials needed to complete it may not be readily available. In order for a project to be a success everything about the business must be evaluated to understand how well the system works. This paper will which information gathering methods can be used in analyzing the requirements, classifying which business process mapping methods should be used in analysis, discussing which business process mapping tools to use in documenting analysis, indicate how the analyst would know if these methods and tools were effecting in understanding requirements, and explaining how prototyping tools could be used to confirm these requirements.…

    • 1279 Words
    • 6 Pages
    Powerful Essays
  • Powerful Essays

    In the research paper “Requirements Engineering: A Roadmap”, the authors Bashar Nuseibeh and Steve Easterbrook state that the “primary measure of success of a software system is the degree to which it meets the purpose for which it was intended”. Requirements Engineering is also considered a branch of systems engineering because “software cannot function in isolation from the system in which it is embedded and Requirements Engineering must encompass a systems level view” (Nuseibeh and Easterbrook). The role of Requirements Engineering (RE) plays a vital role in the completion of this goal during the software development process. The process of Requirements Engineering consists of five core activities:…

    • 2962 Words
    • 12 Pages
    Powerful Essays
  • Good Essays

    Law Sof Eng

    • 10098 Words
    • 41 Pages

    Requirements definition is the process that determines the properties a particular system should have. The requirements process generates the…

    • 10098 Words
    • 41 Pages
    Good Essays
  • Better Essays

    Requirement Traceability

    • 2436 Words
    • 10 Pages

    5. O. Gotel and A. Finkelstein, An analysis of the requirements traceability problem, in International Conference on Requirements Engineering, 1994, pp. 94-101.…

    • 2436 Words
    • 10 Pages
    Better Essays
  • Satisfactory Essays

    An organization it is composed by an operating core and an administrative component made up by managers (strategic apex and middle line) and analysts (“technostructure” and staff), partially responsible for their work.…

    • 362 Words
    • 2 Pages
    Satisfactory Essays
  • Better Essays

    Software development involves perhaps 50 percent computing and 50 percent communication. Unfortunately, most teams are better at the computing part, and requirements are almost entirely about communication. There are many links in the requirements communication chain, like end user, sales representative, marketing, product manager, developer, and tester. A breakdown in any of these links leads to significant problems. The inevitable outcome of requirements errors is time consuming and costly rework. Analysts report that rework can consume 30 to 40 percent of the total effort expended on a software project. Multiple studies have indicated that roughly 50 percent of the defects…

    • 1961 Words
    • 8 Pages
    Better Essays
  • Good Essays

    Requirement gathering is a process of collecting the user needs to solve a problem or issues and achieve an objective. It is basically a software capability needed by the user to solve a problem or achieve an objective. This is really an important phase/ milestone in a project life cycle. If the requirement gathering is not done properly/ completely, all the hierarchy phases given below stay incomplete, no matter how best the design, until and unless requirements are complete. So we should carefully plan and carry out the requirements gathering with a systematic approach.…

    • 685 Words
    • 3 Pages
    Good Essays
  • Good Essays

    1. What is the most striking feature of software development process at Microsoft (as discussed in the case), according to you and WHY so?…

    • 1162 Words
    • 5 Pages
    Good Essays
  • Powerful Essays

    Abstract— Service Oriented Architecture (SOA) is a shift of paradigm in software development. It can be seen as an evolution of Component Based Software Development (CBSD), with web services used instead of Commercial Off-the-shelf (COTS) software. For the last few years the number of services on the web has increased exponentially. Among available services locating the best service that fulfills the user requirement is a challenging task for researchers. There is still no standard Requirement Engineering (RE) process defined for Service Oriented Software Development (SOSD). The traditional processes and those used for COTS selection cannot be used due to the architectural differences of SOSD with other domains. In this paper we have extracted a list of issues and challenges from literature under considerations by research community for RE process in SOSD. The issues of RE in CBSD are compared with those of SOSD, as CBSD is considered close in nature to SOSD. The results shows that there is a need of standard RE process for SOSD with proper guidance on how to perform different steps with details. Keywords - requirement engineering; service oriented software development; component based software development; commercial off-the-shelf softwares (COTS).…

    • 5034 Words
    • 21 Pages
    Powerful Essays
  • Good Essays

    Business Process Methodology

    • 8366 Words
    • 34 Pages

    Capturing requirements is widely considered to be one of the most difficult tasks in software engineering. At the same time, errors made in this phase are among the most difficult to detect and the most expensive to correct [1]. Therefore, much can be gained from requirements capturing techniques that speed up the creation of requirements specifications, and produce robust requirements specifications. In this paper we propose such a technique. The technique we propose is based on the observation that one of the forms of requirements engineering, the use case based requirements engineering [3, 4, 12, 10], bears much resemblance to business process modeling. The resemblance between use case based requirements engineering and business process modeling becomes obvious when inspecting the following definitions of use case and business process. According to Jacobson [10] a UML use case: ’... specifies a sequence of actions, including variants,…

    • 8366 Words
    • 34 Pages
    Good Essays
  • Better Essays

    4p's of Organisation

    • 1510 Words
    • 7 Pages

    * An organization (or organisation – see spelling differences) is a social entity that has a collective goal and is linked to an external environment. It is the collection of organs of scientific methods and artefacts of the al ammeter. The word is derived from the Greek word “organon”, itself derived from the better-known word “ergon”, which means "organ" – a compartment for a particular task. An organization is defined by the elements that are part of it (who belongs to the organization and who does not?), its communication (which elements communicate and how do they communicate?), its autonomy (which changes are executed autonomously by the organization or its elements?), and its rules of action compared to outside events (what causes an organization to act as a collective actor?).…

    • 1510 Words
    • 7 Pages
    Better Essays
  • Good Essays

    The Software Requirements Specification (SRS) is an important document usually produced in the development of a software product. It clearly and unambiguously defines the functionality of the software project for both the stakeholder and for the developer.…

    • 442 Words
    • 2 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

    Software Engineering

    • 769 Words
    • 4 Pages

    Assumptions provide presumed real world facts that systems are guaranteed to operate correctly. Although software processes have existed for many years now, domain knowledge should be applied throughout every phase of the software development process. An appreciation of the assumptions underlying software engineering can lead to a better understanding of the applicability of structure and quality of work produced. Software plays an important role in business decision-making, and because of its growing importance, assumptions should not be excluded. Its seems increasingly clear that unorganized structures can be a problem in software requirements. What determines whether these problems are important in our decision-making? In business sense, we should focus more on improving the quality of decisions by linking problem solving and decision-making. This paper examines major assumptions in the real world and how they affect decision-making in environmental behavior. This paper also identifies limitations that may arise from these assumptions and how the implementation approach is incorporated in the software development of architecture and tools. In addition, I will explain where we are headed in Software Engineering.…

    • 769 Words
    • 4 Pages
    Good Essays