COIS 3030H Lecture Notes - Lecture 2: Functional Requirement, De-Ice, Business Analyst
17 Sep 2018
School
Department
Course
Professor
Document Summary
Functional requirements: describe the products actions, the product shall produce a schedule of all roads upon which ice is predicted to form within a given parameter. The functionality of the end product is restricted by the constraints. The functionality is to the benefit of its user, but it is the non-fu(cid:374)(cid:272)tio(cid:374)al (cid:396)e(cid:395)ui(cid:396)e(cid:373)e(cid:374)ts that (cid:862)delive(cid:396)(cid:863) the fu(cid:374)(cid:272)tio(cid:374)ality (cid:271)y (cid:373)aki(cid:374)g the p(cid:396)odu(cid:272)t usable and acceptable to the users. Trawling for requirements: understand the underlying business reason, most stakeholders talk about perceived solution, which may not be the optimal solution, your job is to uncover the essence of the system, not the perceived solution. Quick and dirty modeling: models, sometimes referred to as prototypes, can be used at any time during the specification life cycle. Scenarios: shows functionality of a business process by breaking it down into a series of easily recognizable steps, written in english, of they are accessible to all stakeholders.
