ITEC 3010 Lecture Notes - Functional Requirement, Physical Model, Usability Testing

• School: York University
• Department: Information Technology
• Course: ITEC 3010
• Professor: all

Document Summary

Lecture 4 investigating system requirements oct 5. Gather information: involves gathering lots of information, can get information from people who will be using the system. Can get other information by reviewing documents and policy statements (e. g. at a bank) what is done. Can involve the analyst actually doing some or part of the task to get a feel for: in order to automate order-entry you may need to become an expert on the task (knowing how orders are processed) Need to understand current and future users, locations, system interfaces, possible solutions, etc. Logical model: any model that shows what the system is required to do without committing to any one technology requirements model is logical. Physical model: any model that shows how the system will actually be implemented. Models are often graphical in nature: data flow diagrams (dfds, entity-relationship diagrams (erds)