 |


Prescription:SD300 Systems Design |
Aim of Module | To enable students to complete the design of one or two systems, given the requirements definition.
|
Credits | 7
|
Suggested Time | 70 student learning hours
|
Prescription Expiry Date | Nov 2002
|
Level and Assessment Schedule
|
Topics | Highest Skill Level | Suggested Assessment Percentage | |
1 Systems Design |
P |
100 |
|
|
| | | | 100
| |
The Student Will
| | | > | Given a complete requirements definition for a realistic business system design a new system. This will include: |
|
| | - analysis of existing system against requirements |
| | - logical design refinement |
| | - physical design |
| | - documentation |
| | - planning for data conversion |
| | - planning for implementation |
| | - planning for post-implementation review
| top
| | | Note | > | Students should undertake the design process either for two modestly-sized systems or one larger system. It may be appropriate for them to work in teams rather than individually. |
|
> | This is CASE STUDY work; it is in the Project (PJ300) that a student may undertake the design of a real system. |
|
|
|
|