• DocumentCode
    2620428
  • Title

    Modeling Requirements

  • Author

    Prindahl, Anette

  • Author_Institution
    ATP
  • fYear
    2006
  • fDate
    11-15 Sept. 2006
  • Firstpage
    267
  • Lastpage
    267
  • Abstract
    Summary form only given. Hear about how ATP do the business modeling, how we decide what is going to be handled by an IT-system, how we specify the system use case representing that. On the information side, how we do information concept modeling with the business, how we specify the services and service operations to fit a SOA architecture. How we integrate functionality and information in the description of the use cases, where we describe what the actors do, what the system does, and which service operations make it happen. Hear about the benefits and challenges of using a modeling tool to integrate and keep track of all the models
  • Keywords
    formal specification; software tools; systems analysis; IT-system; SOA architecture; business modeling; information concept modeling; modeling requirements; service operations; system use case; Business; Information systems; Service oriented architecture;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Requirements Engineering, 14th IEEE International Conference
  • Conference_Location
    Minneapolis/St. Paul, MN
  • ISSN
    1090-705X
  • Print_ISBN
    978-0-7695-2555-6
  • Type

    conf

  • DOI
    10.1109/RE.2006.44
  • Filename
    1704074