70 likes | 278 Views
Requirements Analysis for Complex Software Systems. Vereistenanalyse voor complexe softwaresystemen. Context. Study programs Master informatics Software engineering: basic package Master applied informatics Software engineering: mandatory package Master of Computer Science
E N D
Requirements Analysis for Complex Software Systems Vereistenanalyse voor complexe softwaresystemen
Context • Study programs • Master informatics • Software engineering: basic package • Master applied informatics • Software engineering: mandatory package • Master of Computer Science • Software engineering: mandatory package • Secure software: optional package • Timetable • 1st or 2nd year • 1st semester • Load • 3 study points
Objectives • Requirements specification • Study and describe functional requirements • Emphasis is on (advanced) use case modeling • Transition from business use cases to system use cases • Evolution from clients interacting with real-world entities to clients interacting with the ultimate system • Domain modeling • Model the context (the business) of the software system • Emphasis is on advanced modeling concepts in the Unified Modeling Language (UML) • Emphasis is also on formal specifications in the Object Constraint Language (OCL)
Teaching Staff • Academic [K.U.Leuven] • Eric Steegmans • Industrial [ACA IT-Solutions] • Kurt Hardy • Stijn Van Den Enden
Contact Sessions • Example driven [music store] • Short presentations of basic concepts • Application • Homework • Schedule • Sep29: Introduction [Eric] • Oct 13, oct27, nov17 : Use Cases [Kurt] • Nov 24, dec 8: Domain Modeling [Stijn] • Dec 22: Object Constraint Language [Eric]
Course Material • Course notes • Agile Requirements Management [K. Hardy] • Distributed by VTK and WINA • Electronically available on Toledo • The Object Constraint Language [Tutorial] • Slides • Material of previous year is available on Toledo • Updates are posted throughout the semester
Examination • Homework • A bonus of 1 point for each homework delivered on time and of acceptable quality • Project-driven • Requirements analysis of a vaguely described system • Business use cases • System use cases • Domain models • Individual or in teams of 2 students • Schedule • Nov : distribution of assignment • Jan : solutions due • 1st Exam Period: defense (appointment)