A component-based groupware development methodology

Cléver Guareis de farias, Luis Ferreira Pires, Marten J. van Sinderen

    Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

    12 Citations (Scopus)
    289 Downloads (Pure)

    Abstract

    Software development in general and groupware applications in particular can greatly benefit from the reusability and interoperability aspects associated with software components. Component-based software development enables the construction of software artefacts by assembling prefabricated, configurable and independently evolving building blocks, called software components. This paper presents a methodology for the development of groupware applications using a set of composable software components. This methodology consists of splitting the software development process according to four abstraction levels, viz., enterprise, system, component and object, and three different views, viz., structural, behavioural and interactional. The use of different abstraction levels and views allows a better control of the development process. We illustrate this methodology using a chat application as a case study.
    Original languageUndefined
    Title of host publicationProceedings of the Fourth IEEE International Enterprise Distributed Object Computing Conference (EDOC 2000)
    Place of PublicationUSA
    PublisherIEEE
    Pages204-213
    Number of pages10
    ISBN (Print)07-6950-8650
    DOIs
    Publication statusPublished - 2000
    Event4th International Enterprise Distributed Object Computing Conference, EDOC 2000 - Makuhari, Japan
    Duration: 25 Sept 200028 Sept 2000
    Conference number: 4

    Publication series

    Name
    PublisherIEEE

    Conference

    Conference4th International Enterprise Distributed Object Computing Conference, EDOC 2000
    Abbreviated titleEDOC
    Country/TerritoryJapan
    CityMakuhari
    Period25/09/0028/09/00

    Keywords

    • EWI-8740
    • IR-19027
    • METIS-119549
    • SCS-Services

    Cite this