Taught Component: The module content for part 1 may be delivered in a series of lecture/tutorial sessions accounting for up to 36 hours. Non-contact time will be used for independent research and completion of the assessed work.
Learning Contract Component
The academic content time for this will be dependent on the contract agreed.
For individual student contracts, there will be 3 hours of supervision time (20 minutes per week) with at least one formative review (midpoint) with university/college tutors lasting around 30 minutes. Additional time may be allocated where groups of students are involved. Employer Feedback Forms will be completed by the work-based mentor where appropriate and Self-assessment forms will be completed by the student. These will inform the formative review and summative assessment.

A Coursework Weighted at 50% meeting Learning Outcomes 1-4, A second Coursework Weighted at 50% meeting Learning outcome 5
Coursework 1: (circa 3000 words) to include
- A requirements specification
- Analysis documentation
- Design models (Including Interface Design) and associated documentation.
- A report covering the testing process and factors influencing selection.
A Coursework Weighted at 50% meeting Learning outcome 5.
Students will work to a negotiated learning contract which may involve one of the following:
- Attending an external training course (eg. PRINCE 2, ITIL, CISCO - in this case gain academic credit is gained for assessing the impact of the training courses/work-based training undertaken on work practice. The credit is gained for a reflective assessment, not directly for the training course itself.
- Submitting a research report on an academic area related to the student¿s current role or career
- Undertaking a short work-based project.
In some cases, the nature of the learning contract will be decided by the employer, in others by individual students. In all cases, the contracts must be signed off by the module leader or delegate.

The module will cover the following topics:
- Systems Analysis and Design in Context: What constitutes a system? The history of systems development, the reasons for system failure.
o The traditional systems development lifecycle
o Requirements elicitation and specification
o Introduction to method related techniques: eg. mind maps, entity relationship models, dataflow diagrams, use case models
o The formal documentation of a system resulting from the application of tools and techniques of the systems development lifecycle
o Use of a chosen notation, for example, structured systems analysis and design methodology (SSADM), the UML
o Introduction to the corresponding documentation, for example process descriptions, entity descriptions, use case descriptions to complete the model
- Introduction to the concept and use of a Database Management systems (DBMS)
o Systems Architectures
- System testing methods

Part 2 requires students to work to a pre-defined learning contract. Some students may define their own contract while for others who are taking this award as part of a Higher Apprenticeship, this learning contract may have input from the employer to ensure that the students gain specific skills or qualifications relevant to their work. It may cover work leading to CISCO, ITIL, PRINCE 2 certification for example or require students to reflect on how a work-based training course has improved their work practice.

Prior Study of either CESCOM10091-4 Professional and Academic Skills for ICT II or similar

An appropriate CASE tool

Systems Analysis and Design : Techniques, Methodologies, Approaches, and Architectures (Available as e-book in University library), Chiang, Roger Siau, Keng Hardgrave, Bill C. 2009 , M.E. Sharpe, Inc. eISBN: 9780765623768 (Edition: 4)

Designing Effective Database Systems (Available as e-book in University library), Riordan, R.M., 2005, Addison-Wesley Professional, ISBN-10: 0321290933 , ISBN-13: 978-0321290939 (Edition: 1)

(Information Systems Development: Methodologies, Techniques and Tools, Avison, G., Fitzgerald D.,2006. McGraw-Hill, ISBN-10: 0077114175, ISBN-13: 978-0077114176 (Edition: 4)

Object Oriented Systems and Design using UML, Bennett, S, Mcrobb, R., Farmer, S. 2010, McGraw Hill ISBN-10: 0077125363, ISBN-13: 978-0077125363, (Edition: 4)