COMP 3004 Lecture Notes - Lecture 4: Use Case, User Story, Functional Decomposition

• School: Carleton University
• Department: Computer Science
• Course: COMP 3004
• Professor: Olga Baysal

Document Summary

Comp (cid:1007)00(cid:1008) lecture (cid:1008): use cases and: use cases i(cid:374)fo(cid:396)(cid:373)al des(cid:272)(cid:396)iptio(cid:374)s of the s(cid:455)ste(cid:373)"s (cid:271)asi(cid:272) fu(cid:374)(cid:272)tio(cid:374)alit(cid:455) a(cid:374)d its i(cid:374)te(cid:396)a(cid:272)tio(cid:374)s (cid:449)ith the. Identify the tasks to be performed, at both the macro and lower levels. Ide(cid:374)tif(cid:455) the (cid:373)ajo(cid:396) (cid:862)a(cid:272)to(cid:396)s(cid:863) a(cid:374)d ho(cid:449) the(cid:455) i(cid:374)te(cid:396)a(cid:272)t (cid:449)ith s(cid:455)ste(cid:373: clarify who is responsible for what, hidden assumptions and ambiguities with clients, cla(cid:396)if(cid:455) (cid:862)(cid:449)hat-if(cid:863)s, a(cid:374)d e(cid:374)su(cid:396)e that all possi(cid:271)le (cid:271)ases a(cid:396)e (cid:272)o(cid:448)e(cid:396)ed. Customer initiates uc3; uc1 includes uc2: uml use case diagram, box is boundary of system, straight lines are interactions/communication from user, oval is use case, use case a story of using a system to fulfill a goal. It models an abstract task (with steps) performed by a user of the system: ex. <> by other ucs: supporting actor provides services to the uc, sometimes, off-stage a(cid:272)to(cid:396) (cid:449)ho has a(cid:374) (cid:862)i(cid:374)te(cid:396)est(cid:863) i(cid:374) the uc (cid:894)e. g. , go(cid:448)e(cid:396)(cid:374)(cid:373)e(cid:374)t (cid:396)egulato(cid:396)(cid:455) agency, an individual person may play multiple roles, simultaneous or over time, ex.