台湾成功大学软件工程课件ch07.ppt

Chapter 7 System Models System models Abstract descriptions of systems whose requirements are being analysed Objectives To explain why the context of a system should be modelled as part of the RE process To describe behavioural modelling, data modelling and object modelling To introduce some of the notations used in the Unified Modeling Language (UML) To show how CASE workbenches support system modelling Topics covered Context models Behavioural models Data models Object models CASE workbenches System modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers Different models present the system from different perspectives External perspective showing the system’s context or environment Behavioural perspective showing the behaviour of the system Structural perspective showing the system or data architecture Structured methods Structured methods incorporate system modelling as an inherent part of the method Methods define a set of models, a process for deriving these models and rules and guidelines that should apply to the models CASE tools support system modelling as part of a structured method Method weaknesses They do not model non-functional system requirements They do not usually include information about whether a method is appropriate for a given problem The may produce too much documentation The system models are sometimes too detailed and difficult for users to understand Model types Data processing model showing how the data is processed at different stages Composition model showing how entities are composed of other entities Architectural model showing principal sub-systems Classification model showing how entities have common characteristics Stimulus/response model showing the system’s reaction to events Context models Context models are used to illustrate the boundaries of a system Social and organisational concerns may affect the decision on where to position system boundar