Module

Submission:

Written coursework should be submitted by following the standard CMP practice. Students are advised to refer to the Guidelines and Hints on Written Work in CMP.

Deadlines:

If coursework is handed in after the deadline day or an agreed extension:
 

Saturdays and Sundays will NOT be taken into account for the purposes of calculation of marks deducted.

All extension requests will be managed through the LTS Hub. A request for an extension to a deadline for the submission of work for assessment should be submitted by the student to the appropriate Learning and Teaching Service Hub, prior to the deadline, on a University Extension Request Form accompanied by appropriate evidence. Extension requests will be considered by the appropriate Learning and Teaching Service Manager in those instances where (a) acceptable extenuating circumstances exist and (b) the request is submitted before the deadline. All other cases will be considered by a Coursework Coordinator in CMP.

For more details, including how to apply for an extension due to extenuating circumstances download Submission for Work Assessment (PDF, 39KB)
 

Plagiarism:

Plagiarism is the copying or close paraphrasing of published or unpublished work, including    the work of another student; without due acknowledgement. Plagiarism is regarded a serious offence by the University, and all cases will be investigated. Possible consequences of plagiarism include deduction of marks and disciplinary action, as detailed by UEA's Policy on Plagiarism and Collusion.

Module specific:

• To introduce models of the systems development process.
• To explore the intrinsic complexity of the software development process.
• To discuss the importance of description and modelling to the development process and examine a range of techniques.
• To develop competence in the use of methods of analysis and design for information systems.

Transferable skills:

• Written communication. Students write a report as part of their coursework. This must be written coherently and grammatically.
• Oral communication. Non-assessed seminar exercises emphasise all aspects of oral communication. Formal presentation forms part of the second piece of course assessed work on this unit.
• Problem solving. Systems Analysis and Design are inherently problem solving activities.
• Working with others. Non-assessed seminar exercises emphasise the importance of working with others during Systems Analysis and Design. The second piece of assessed coursework is a group exercise.

On completion of this module students should be able to:

• Describe all activities involved in the systems development life cycle.
• Describe what is meant by the environment surrounding a system and the stakeholders involved.
• Explain why systems development is far more than just software development.
• Explain what is meant by systems analysis and list the various skills needed by a systems analyst.
• Describe a range of requirements elicitation and validation methods.
• Summarise the importance of prototyping to systems analysis and design.
• Appreciate alternative approaches for systems analysis and design including the structured approach and the Object Oriented approach.
• Carry out an analysis and design exercise for a small system.

Topics will be introduced during lectures, but the intention is that students will become actively involved during the supporting seminars, which will have a group work, problem-solving flavour.

Total Hours: 48

Lectures: 36 hours: 36 Content (with provisional weekly schedule)

1. Introduction to analysis and design. The systems analyst. Systems development overview.
2. The early stages of systems development.
3. Fact finding.
4. Systems analysis using a structured approach.
5. Further structured analysis.
6. Systems analysis using an Object-Oriented approach.
7. Reading Week - No Lectures
8. Systems design using a structured approach.
9. Further systems design.
10. Systems design using an Object-Oriented approach.
11. Implementation and evaluation.
12. Student Presentations.

Seminars: 12 hours: 12 Content (with provisional weekly schedule)

1. The Analyst
2. Feasibility Studies
3. Interviewing
4. Physical DFDs & process specifications
5. Logical DFDs.
6. UML exercise
7. Reading Week
8. Interface design.
9. Software design.
10. OO design.
11. Implementation
12. Student presentations

Laboratory work: 0 hours

There are no formal laboratory sessions for this unit. You will, however, be required to produce nicely presented specifications. All CMP labs provide access to Visio a useful tool for drawing the various modelling diagrams.

This module is assessed by a combination of coursework and an end of module examination. The exam accounts for 60% of the module's marks. It is scheduled during the summer exam period and lasts 3 hrs.

The coursework is divided into two components. The first piece of coursework is an individual piece of work worth 15% of the module's marks. It is set in week 3 and is due in at the beginning of week 7. The second, more demanding, piece of coursework, worth 25% of the module's marks, is set in week 6 and is due in at the beginning of week 12. This uses a real case, (where possible), as the basis for a group analysis and design exercise. Students are allocated into a mixed group. The work consists mainly of analysing, designing, an oral presentation, and a written presentation. Marks are awarded on both a group and an individual basis. For the group exercise, marks will be deducted for non-participation.