Preview

Object Oriented

Powerful Essays
Open Document
Open Document
6144 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
Object Oriented
tedSystems Engineering Test and Evaluation (SETE) Conference, Canberra, October 2003

Page1

Object-Oriented Requirements Engineering and Management
Joseph E. Kasser DSc, CEng, CM, MIEE Systems Engineering and Evaluation Centre University of South Australia (UniSA) Mawson Lakes South Australia, 5095 Joseph.kasser@unisa.edu.au Abstract Object-Oriented requirements engineering is an approach to encapsulating information about the process and product, as well as functionality into a requirements object. This paper identifies properties of a requirement object based on information in the process (development, management and test and development streams of work in the system life cycle (SLC) as well as information about the product needed. The paper also describes some of the functionality that could be added to the requirements object. The paper concludes that Object-Oriented requirements engineering and management can effect a significant reduction of the problems currently encountered in the SLC due to poor requirements engineering and management. Background The systems and software development industry is characterized by a paradigm of project failure (Standish 1995). The situation has been described by Cobb’s Paradox (Voyages 1996), which stated “We know why projects fail, we know how to prevent their failure --so why do they still fail?” One of the known contributing causes of these project failures is poor requirements engineering and management, which has been repeatedly and widely discussed and documented for at least 10 years (Hooks 1993; Kasser and Schermerhorn 1994; Jacobs 1999; Carson 2001; etc.). However, this continual documentation and discussion of the problem of poor requirements engineering and management has not resulted in a practical solution to the problem. This paper contains a preliminary introduction to an Object-Oriented approach to requirements engineering that might help to reduce the contribution of poor requirements engineering and



References: Alexander, I. F., Stevens, S., Writing Better Requirements, Addison-Wesley, 2002. Carson, R.S., “Keeping the Focus During Requirements Analysis”, Proceedings of the 11th International Symposium of the International Council on Systems Engineering (INCOSE), Melbourne, Australia, 2001. Cook S. C., Kasser J.E., Asenstorfer J., “A Frame-Based Approach to Requirements Engineering”, 11th International Symposium of the INCOSE, Melbourne, Australia, 2001. Dorfman M., Thayer R.H. System and Software Requirements Engineering, IEEE Computer Society Press, 1990. Hooks, I., "Writing Good Requirements", Proceedings of the 3rd NCOSE International Symposium, 1993, available at http://www.incose.org/rwg /writing.html, last accessed November 1, 2001. Hull, M.E.C, Jackson, K., Dick, A.J.J., Requirements Engineering, Springer, 2002. Jacobs, S., “Introducing Measurable Quality Requirements: A Case Study”, IEEE International Symposium on Requirements Engineering, Limerick, Ireland, 1999. Hopkins, F.W., Rhoads, R.P. “Object Oriented Systems Engineering – An Approach”, Proceedings of the 8th International INCOSE Symposium, 1998 Systems Engineering Test and Evaluation (SETE) Conference, Canberra, October 2003 Page15 Kasser, J.E., Applying Total Quality Management to Systems Engineering, Artech House, 1995. Kasser, J.E., “What Do You Mean, You Can 't Tell Me How Much of My Project Has Been Completed?”, Proceedings of the 7th Annual International Symposium of the INCOSE, Los Angeles, CA. 1997. Kasser, J.E., “A Framework for Requirements Engineering in a Digital Integrated Environment (FREDIE)”, Proceedings of the Systems Engineering, Test and Evaluation Conference (SETE 2000), Brisbane, Australia, 2000. Kasser J.E., (2000a), "Enhancing the Role of Test and Evaluation in the Acquisition Process to Increase the Probability of the Delivery of Equipment that Meets the Needs of the Users", SETE 2000, Brisbane, Australia, 2000. Kasser J.E., "A Prototype Tool for Improving the Wording of Requirements", Proceedings of the 12th International INCOSE Symposium, 2002. Kasser J.E., (2002a), "Does Object-Oriented System Engineering Eliminate the Need for Requirements?", Proceedings of the 12th International INCOSE Symposium, 2002. Kasser J.E., (2000b), “The Cataract Methodology for Systems and Software Acquisition, SETE 2002, Sydney Australia, October 2002. Kasser J.E., Cook S.C., “Using a Rapid Incremental Solution Construction Approach to Maximise the Completeness and Correctness of a Set of Requirements for a System” Proceedings of the 13th International INCOSE Symposium, 2003. Kasser J.E. and Cook S.C. “The Communications Requirements Evaluation & Assessment Prototype (CREAP)”, Proceedings of the 12th INCOSE, Las Vegas, NV, 2002. Kasser J.E., Cook S.C., Scott W, Clothier J., Chen P., “Introducing a Next Generation Computer Enhanced Systems Engineering Tool: The Operations Concept Harbinger”, SETE 2002, Sydney Australia, 2002. Kasser, J.E., Schermerhorn R., “Determining Metrics for Systems Engineering”, Proceedings of the 4th International Symposium of the NCOSE, San Jose, CA., 1994. Kasser J.E., Tran X-L, Matisons S., “Prototype Educational Tools for Systems and Software (PETS) Engineering”, Proceedings of the 14th Annual Conference for Australian Engineering Education, Melbourne, 2003. Kotonya G. and Sommerville I., Requirements Engineering: Processes and Techniques, Wiley, 1998. Lykins, H., Friedenthal, S., Meilich, A., “Adapting UML for an Object Oriented Systems Engineering Method (OOSEM)”, Proceedings of the 10th International INCOSE Symposium, 2000. Meilich, A., Rickels, M., “An Application of Object Oriented Systems Engineering (OOSE) To an Army Command and Control System: A New Approach to Integration of System and Software Requirements and Design”, Proceedings of the 9th International INCOSE Symposium, 1999. Schach S., Object-Oriented and Classical Software Engineering, p 294, McGraw Hill, 2002. Standish (1995), Chaos, The Standish Group, http://www.standishgroup.com/chaos.html, last accessed March 19, 1998. ST DADS (1992). Requirements Analysis Document (FAC STR-22), Rev. C, August 1992, as modified by the following CCR 's:- 139, 146, 147C, 150 and 151B. Von Knethen A., Paech B., Kiedaisch F., Houdek F., “Systematic Requirements Recycling through Abstraction and Traceability”, Proceedings IEEE Joint International Conference on Requirements Engineering, 2002. Voyages (1996), “Unfinished Voyages, A follow up to the CHAOS Report”, The Standish Group, http://www.pm2go.com/sample_research/unfinished_voyages_1.asp, last accessed January 21, 2002.

You May Also Find These Documents Helpful

  • Powerful Essays

    Cis518 Assignment 2

    • 776 Words
    • 4 Pages

    The technique that is being used for gathering requirements in this document is combining “software requirement specification with use case modeling”.…

    • 776 Words
    • 4 Pages
    Powerful Essays
  • Satisfactory Essays

    Requirements Definition: This step defines project goals into specific functions and operations of the intended application. It also analyzes end-user information needs.…

    • 595 Words
    • 3 Pages
    Satisfactory Essays
  • Good Essays

    analysis, and computer-aided systems engineering (CASE) tools. The goal of requirements gathering is to gain a complete and detailed understanding of a company’s problem and how the proposed system will solve it. The third phase is the system design phase. The goal of this phase is to describe in detail how…

    • 435 Words
    • 2 Pages
    Good Essays
  • Satisfactory Essays

    The great awakening was an event the happened in the 18th century religious scene. A new spiritual renewal began with the Wesley brothers and George Whitefield in England and all over the American colonies during the most of the first half of the 18th century. The awakening allowed a lot of people to express their emotions and feelings more overtly. People wants to feel a greater bond and intimacy with god. During the late 17th century England was fighting between religious and different political groups. Many of the religions were stabilized since everyone was practicing the same religion. Instead of everyone being positive everyone decided to force religious beliefs causing a complacency and spiritual dryness among many of the believers.…

    • 213 Words
    • 1 Page
    Satisfactory Essays
  • Better Essays

    Software Development

    • 6242 Words
    • 25 Pages

    -2Introduction Over the past 20 years it has become accepted in the software engineering community that software development should be undertaken using a model of the software life cycle. The benefits of such an approach include: the ability to plan the project; the ability to estimate resource requirements for the development; the ability to size the likely software product; the ability to estimate hardware requirements; the ability to update estimates on the basis of real figures during monitoring; the availability of documents for monitoring and control; the ability to fit the development process into a Quality Management System; a development structure which may be audited for quality. The result of using life cycle approaches is that the development process is made visible to the project management, project controller, quality controller, the project sponsor and…

    • 6242 Words
    • 25 Pages
    Better 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
  • Better Essays

    Engineer

    • 2620 Words
    • 11 Pages

    INFORMATION SYSTEMS PROJECT MANAGEMENT Referenced report IT project management 1-Successful IT project management 1-Successful It is impossible to read a newspaper,magazine,or web page without hearing about impact of information technology on our society.information is traveling faster and being shared by more individuals than ever before. There is no (one size fits all) solution to managing projects .Although project management has been an established field for many years , managing information technology projects requires ideas and information that go beyond standard project management 1.1 What is a project ? "a project is a task that has a beginning and an end" (Maylor2010) . 1.2 What is project management? "Project management is the application of knowledgement,skills,tools and techniques to project activities to meet project requirements" (Schwalble,2010) . 1.3 Project procedures : Maylor(2010) creates 4D model for project management processes : Define it-Design it-Develope it-Do it In definition process which contains a-stakholders strategy ,he assume that sucess of stackholders management is very critical issu because the complexity of requirements of many different groups of stackholders . Mayor express requirements as measures which is an explicit expression of the requirements .he relate the success in this stage to three basic issues : stakeholders,measures,timing. Schwalble(2010) summerizes the ways of project success into 3 ways 1-the project meets scope,time,cost and quality goals . 2-the project satisfied the customer/ sponsor 3-the results of the project met its main objectives. So we notice that the success of a project is not only the project manager responsibility and all stackholders share in this success . The requirements specification for IT system is collected to be: 1.4 System Requirement Specification: · Desired operational capabilities · Physical characteristics · Performance parameters and expected values · Interfaces with its…

    • 2620 Words
    • 11 Pages
    Better Essays
  • Good Essays

    Kkkj

    • 623 Words
    • 3 Pages

    • Conduct relevant “Requirements Analysis” to develop an accurate understanding of system requirements, in order to design the best solution within project, business and technical constraints.…

    • 623 Words
    • 3 Pages
    Good Essays
  • Best Essays

    The common way to express requirements is with large volumes of text [1] which can be referred to as natural language (NL) requirements. NL requirements are typically coming from a pool of natural language statements which are gathered from interview excerpts, documents and notes. Due to the inherent ambiguity of natural language, it is often difficult to prove properties on natural language requirements [2]. For this reason, Informal natural language requirements are better to be expressed as formal representations.…

    • 3944 Words
    • 15 Pages
    Best Essays
  • Satisfactory Essays

    Computer Science

    • 4838 Words
    • 20 Pages

    TCS-406 SOFTWARE ENGINEERING LTP 2 00 Unit-I: Introduction (5L) Introduction to Software Engineering, Software Characteristics, Software Crisis, Software Engineering Processes, Software Development Life Cycle (SDLC) Models: Water Fall Model, Prototype Model, Spiral Model, Evolutionary Development Models, Iterative Enhancement Models. Unit-II: Software Requirement Specifications (SRS) (5L) Requirement Engineering Process: Elicitation, Analysis, Documentation, Review and Management of User Needs, Feasibility Study, Information Modeling, Data Flow Diagrams, Entity Relationship Diagrams, Decision Tables, SRS Document, IEEE Standards for SRS. Software Quality Assurance (SQA),SEI-CMM Model. Unit-III: Software Design (7L) Basic Concept of Software Design, Architectural Design, Low Level Design: Modularization, Design Structure Charts, Pseudo Codes, Flow Charts, Coupling and Cohesion Measures, Design Strategies: Function Oriented Design, Object Oriented Design, Top-Down and Bottom-Up Design.Software Measurement and Metrics: Various Size Oriented Measures: Halestead’s Software Science, Function Point (FP) Based Measures, Cyclomatic Complexity Measures: Control Flow Graphs. Unit-IV: Coding, Testing & Software Maintenance (7L) Top-Down and Bottom –Up programming, structured programming, Compliance with Design and Coding Standards. Testing Objectives, Unit Testing, Integration Testing, Acceptance Testing, Regression Testing, Top-Down and Bottom-Up Testing Strategies: Test Drivers and Test Stubs, Structural Testing (White Box Testing), Functional Testing (Black Box Testing), Corrective and Perfective Maintenance, Cost of Maintenance, Software Re-Engineering, Reverse Engineering. Constructive Cost Models (COCOMO), Text Books: 1. Rajib Mall, Fundamentals of Software Engineering, PHI Publication, 3rd Edition. 2. Pankaj Jalote, Software Engineering, Narosa Publication, 3rd Edition 3. K. K. Aggarwal and Yogesh Singh, Software Engineering, New Age International Publishers, 3rd Edition. Reference Books: 1. R. S. Pressman, Software Engineering: A Practitioners Approach, McGraw Hill, 6th Edition. 2. Ian Sommerville, Software Engineering, Addison Wesley, 8th Edition. 3. Carlo Ghezzi, M. Jarayeri, D. Manodrioli, Fundamentals of Software Engineering, PHI Publication…

    • 4838 Words
    • 20 Pages
    Satisfactory Essays
  • Better Essays

    How to Write Srs

    • 2752 Words
    • 12 Pages

    In this article I explain the major sections of a typical Software Requirement Specification document. I also provide a generic SRS template which can be customized for your project needs.…

    • 2752 Words
    • 12 Pages
    Better Essays
  • Powerful Essays

    Software Quality Assurance (QA) plays a major role in successful implementation and maintenance of a software project. In many organizations, QA has been simply traded-off to project cost [1]. The motivation of this research is to highlight the value of Software Quality Assurance against the economic cost. The IEEE standard ANSI/IEEE 730-2002 defines software quality assurance as “a planned and systematic pattern of all actions necessary to provide adequate confidence that the software conforms to established technical requirements”[2]. QA is not only holding a direct relationship of meeting customer satisfaction, but it has a very high impact on project schedules and cost. Failing to pay attention is often resulted in…

    • 5694 Words
    • 23 Pages
    Powerful Essays
  • Satisfactory Essays

    Newerwwrwerwe

    • 608 Words
    • 3 Pages

    This course is an introduction for a series of software testing track. This course aims to introduce software testing process and definition. Then, it reflects the roles and responsibilities of test team in collaboration with development team. Finally, the course demonstrates the training bundles of software testing.…

    • 608 Words
    • 3 Pages
    Satisfactory Essays
  • Powerful Essays

    Software Engineering

    • 3574 Words
    • 15 Pages

    Objectives Successful completion of the Requirements Analysis Phase should comprise: • Definition of approved requirements • Creation of the System Requirements Document and Requirements Traceability Matrix • Development of planned test activities • Approval to progress to the Design Phase Goals The purpose of the Requirements Analysis Phase is to transform the needs and high-level requirements specified in earlier phases into unambiguous (measurable and testable), traceable, complete, consistent, and stakeholder-approved requirements. 2.0…

    • 3574 Words
    • 15 Pages
    Powerful Essays
  • Powerful Essays

    Software Engineering

    • 23657 Words
    • 95 Pages

    tasks have different importance or are applied in a different sequence, or even cyclically. The…

    • 23657 Words
    • 95 Pages
    Powerful Essays