. . . . . . . "Interpret a requirements document to conceptualize a system's purpose and boundary"@en . . . . . . . . . "Create descriptions of application programming interfaces representing an information system's functions in terms of function signatures, effects, and exceptions "@en . . . . . . . . . . . "Create structural and dynamic models of an information system encompassing actors, processes, data and the interactions between them"@en . . . . . . . . . "Understand the key notions of operational land/urban information systems in terms of their purpose, capability, and function "@en . . . . . . . . . "Execute system analysis and design activities within the context of a development method (SDLC/AGILE/eXtreme)"@en . . . . . . . . . . . . . . . "Specifying interfaces in MVC "@en . "Designing Urban & Land Information Systems: LU9"@en . . . . . . . . . . "Modeling user interactions"@en . "Designing Urban & Land Information Systems: LU6"@en . . . . . . . . . . . "Functional system overview modeling"@en . "Designing Urban & Land Information Systems: LU3"@en . . . . . . . . "Conceptual modeling "@en . "Designing Urban & Land Information Systems: LU4"@en . . . . . . . . . . . "MVC and separation of concerns"@en . "Designing Urban & Land Information Systems: LU8"@en . . . . . . . . . "System states"@en . "Designing Urban & Land Information Systems: LU7"@en . . . . . . . . . . . . . "Developing Information Systems"@en . "Designing Urban & Land Information Systems: LU2"@en . . . . . "Conceptual modeling "@en . "Designing Urban & Land Information Systems: LU5"@en . . . . . . . . . . . . . . . . . "Intro to Information Systems"@en . "Designing Urban & Land Information Systems: LU1"@en . . . . . . . . "Wrap up"@en . "Designing Urban & Land Information Systems: LU10"@en . . . . . . . "information system"@en . . . . . . . . "function signatures"@en . . . . . . "development method"@en . . . . . . "function signatures specification"@en . . . . . . . . "MVC"@en . . . . . . "activity diagrams"@en . . . . . . "system implementation organisation"@en . . . . . . "Requirements analysis"@en . . . . . . "function of operational land and urban information systems"@en . . . . . . "verification"@en . . . . . . "land and urban administration"@en . . . . . . "interactions"@en . . . . . "domain modeling"@en . . . . . . "hardware components"@en . . . . . . "domain of discourse"@en . . . . . . "purpose of operational land and urban information systems"@en . . . . . . "UML use cases"@en . . . . . . "functional system modeling"@en . . . . . . "information systems architectures"@en . . . . . . . "SDLC method"@en . . . . . . . "activities of interest"@en . . . . . . "actors"@en . . . . . . "user actions"@en . . . . . . "separation of concerns"@en . . . . . . "specific land administration"@en . . . . . . "software process"@en . . . . . . "information systems types"@en . . . . . . "dynamic models"@en . . . . . . "system's purpose conceptualization"@en . . . . . . "urban and land administration"@en . . . . . . "land and urban planning"@en . . . . . . "Test Driven Development"@en . . . . . . "elements of interest"@en . . . . . . "function exceptions"@en . . . . . "land information systems"@en . . . . . . "key notions of operational land and urban information systems"@en . . . . . . "non-spatial operations"@en . . . . . . . . . . "assignment"@en . . . . . . "application programming interfaces"@en . . . . . . "user interactions detailing"@en . . . . . . . "UML"@en . . . . . . "information systems development"@en . . . . "Data"@en . . . . . . . . . . . . . "https://ltb.itc.utwente.nl/page/792/concept/152926" . . . . . . . . . . . . . . . . . . . "system's boundary conceptualization"@en . . . . . . "hardware deployment"@en . . . . . . "structural models"@en . . . . . . "spatial operations"@en . . . . . . "user actions effects"@en . . . . . . "non-spatial functionality"@en . . . . . . "function effects"@en . . . . . . "communication"@en . . . . . . "illustrative software architecture"@en . . . . . . "course summary"@en . . . . . . "modeling target domains"@en . . . . . . "interface specification"@en . . . . . . . "software architecture"@en . . . . . . "structured approach"@en . . . . . "system design"@en . . . . . . "eXtreme method"@en . . . . . . . "user interactions modeling"@en . . . . . . "user interactions"@en . . . . . "activity models"@en . . . . . . "information system's function"@en . . . . . . "processes"@en . . . . . . "system analysis"@en . . . . . . "specific urban administration"@en . . . . . . . . . "exam"@en . . . . . . "requirements interpretation"@en . . . . . . "capability of operational land and urban information systems"@en . . . . . . . . . . "validation"@en . . . . . . "information systems application"@en . . . . . . "operational land and urban information systems"@en . . . . . . . "AGILE method"@en . . . . . . . "spatial functionality"@en . . . . . . . . . . . . . . . . . . . . "Planning for Liveable & Resilient Cities"@en . . . . . . . . . . . . . . . . . . . "Making Cities and Land SMART"@en . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . "M-GEO 5.0"@en . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . "Spatial Data Science"@en . . . . . . . . . . . . . . . . . . . . . . . . . "Urban & Land Futures"@en . . . "Course"@en . "1" . "2.5" . "70.0" . "5.0" . "blended" . "Basic land and urban futures concepts (course ULF 1), Spatial data handling (courses FC 1 and FC2), basic programming concepts (course FC3)"@en . "No"@en . "No"@en . "4.0" . "3.0" . "With expanding urban settlements, increasing demand for resources, and exacerbating environmental challenges, the complexity of future urban and regional systems is expected to increase. Information systems for planning and managing land use policy implementation will therefore become indispensable tools in the urban planning and land administration toolboxes. In this course students learn to think in systems terms and use systems analysis and design methods to not only describe the functionality of an information system but, perhaps more importantly, to describe the data, information structures, processes, states, and state evolutions of interest within the urban and/or regional system under consideration. The course introduces the software process as a project implementation methodology. Analysis and design approaches are introduced in the context of this overarching structure. First students will learn to analyse requirements documents to conceptualize a system's purpose and boundary. Additional information from the domain and requirements documents will be used to develop a conceptual model of the domain and identify user actions and processes within the domain. UML class diagrams will be used to structure concepts. UML use case diagrams and activity diagrams will be used to analyse user intentions, actions, and the information system's responses. Finally UML state machines will allow student to describe the set of states that can be occupied by all or part of the system being modelled. The modeling constructs introduced are applicable to both the information system and the real world domain. Examples will help clarify how to apply the tool in both contexts. "@en . "Designing Urban & Land Information Systems"@en . "Designing Urban & Land Information Systems"@en . "Designing Urban & Land Information Systems"@en .