IFB103 Lecture Notes - Lecture 8: Functional Requirement, Activity Diagram, Mobile App
22 Jul 2018
School
Department
Course
Professor
Document Summary
Unified modelling language - use cases - week 8. Suppose you want to create a website (e. g. music web store) or any mobile app (e. g. Examples: a use case describes the users" goals, an activity diagram describes how the system implements the users" goals, a class diagram describes the software things that must be implemented by the system to support the users" goals. Internal - how system interacts with the users. Functional - what the users do with the system. Where to start: draw a requirements matrix, use uml to draw use case, and several other types of diagrams including class, activity, Sequence, component and package: a uc illustrates the activities that are performed by certain types of users of a system. Initial work centred on expressing users" functional requirements: main reason why they say that system design is user-centred, entry point link to other diagrams, also an entry point for software validation and verification.
