BISM1201 Lecture Notes - Lecture 6: User Story, Software Design, Database Design
30 Sep 2018
School
Department
Course
Professor
Document Summary
If the requirements are wrong the system will be wrong (and then the problem becomes: when [if ever] do the problems get detected?: determine and document features and functions. Interview users and all stakeholders: document requirements = we have looked at various techniques, examine existing system, review reports, forms, queries, application features, security and controls. Involve functional requirements and non-functional requirements (e. g security: may involves the creation of a data model for a new database. Need to know!!!: build, components/modules constructed independently then combined (some components may be outsourced, document and review, test. Implementation: system conversion - 4 possible strategies: pilot, organisation implements entire system on single, limited unit. If system fails, it only affects limited boundary: reduces exposure, "more geography, phased. Implement part of the system across the whole network: new system installed in phase, tested after each phase, continues until installed at entire organisation, can"t be used in tightly integrated systems.
