Tutorial MbT for printing

Model-based Transition from Requirements to High-level Software DesignModel-based Transition from Requirements to High-level Software DesignHermann KaindlInstitut fürComputertechnik Vienna University of Technology, ICTICTAustriaInstitute ofComputer TechnologySystem overviewbusiness actorbusiness workersBusinessSystem BorderSW system to be builtComposite systemInstitute of Computer Technology© Hermann Kaindl„„„„„„„„„„Model-based Transition from Requirements to High-level Software DesignOutlineBackgroundFunctional requirements, goals and scenarios / use casesRequirements and UML modelsTransition to software designModel-based transformation?Institute of Computer TechnologyWhat are requirements?User wishes / needsIEEE Standard:“A condition or capacity needed by a user to solve a problem or achieve an objective.”“The shall be able to ...”- system to be built- composite systemExample: “The ATM shall accept a cash card.”Requirements modelingInstitute of Computer Technology© Hermann KaindlModel-based Transition from Requirements to High-level Software DesignWhat are requirements? – In practiceUser requirements documentsSoftware/system requirements documentsMostly descriptions in natural languageRepresentation often unstructuredAd hoc processCommunication problemRequirements and use cases?Institute of Computer TechnologyClass and generalization Class in UML (Unified Modeling Language)http://www.omg ...