|
|
 |
Information and Communications
Technology Qualifications
| Back to list of Prescriptions
| Prescription: SA700 (SA300)Systems Analysis |
| Aim of Module | To provide students with the ability to work from a user proposal to produce, and present, a Feasibility Report and a Requirements Specification from which a systems designer can work
|
| Credits | 7
|
| Student Learning hours | 70
|
| Content Revised | 2002
|
| Prescription Expiry Date | Nov 2005
|
LEARNING OUTCOMES
The Student Will
| | | | | A | 1 | Write and present a feasilibility report | | | | | A | 2 | Write and present a Requirements Specification | | |
CONTENT
| | | | > | Define the current problem. Define high-level project objectives, (e.g. save $x over first six months, create a website to deliver a credible corporate image). Determine the scope of the required system. Identify constraints on the project. | | | > | Build models to facilitate developer understanding, and to enable clear definition of the problem. | | | | Range: Data Model, Process Model, Domain Model, Use Case Models. | | | > | Write and present a Feasibility Report for user management, including project objective, problem definition, scope statement, broad cost-and-benefit statement, first-guess project plan, and recommendation. | | |
|
top
| | | | > | Continue information gathering beyond acceptance of the feasibility study to gain all user requirements in detail. | | | > | Develop models beyond feasibility, and keep the models updated as requirements are specified. | | | > | Define each requirement in business language as a measurable system objective. | | | > | Prioritise system requirements and identify project risks. | | | > | Do a full cost-and-benefit analysis of at least one possible architecture for the proposed system. Identify likely costs, savings and intangible benefits, and present using narrative, tables and meaningful graphs. Take into account the variation of value with time, using a method such as Discounted Cash Flow, or Net Present Value. | | | > | Write and present a Requirements Specification for user management, including background, summary of current problems, overview of methodology used, detailed system objectives, detailed cost-and-benefit analysis, revised project plan, and recommendation. The presentation should be brief, business-oriented and non-technical, and may include some preliminary interface designs to help the user understand how the requirements may be realised. The presenter(s) should be able to field questions from users. | | |
|
top
|
|
