Unit Systems Analysis and Design Assignment Brief
| Qualification | OTHM Level 4 Diploma In Information Technology |
| Qualification Number | 610/1191/5 |
| Unit Reference Number | F/617/2266 |
| Unit Title | Systems Analysis and Design |
| Unit Level | 4 |
| Number of Credits | 20 |
| Total Qualification Time | 200 Hours |
| Guided Learning Hours (GLH) | 80 Hours |
| Mandatory / Optional | Mandatory |
| SSAs | 6.1 ICT practitioners |
| Unit Grading Structure | Pass / Fail |
Unit Aims
The aim of this unit is to develop learners’ awareness of system analysis and design in an organisational context. The unit introduces various techniques used within systems analysis and design and the methodologies used in the system development process.
Learning Outcomes, Assessment Criteria and Indicative Content
| Learning Outcomes (The learner will:) | Assessment Criteria (The learner can:) | Indicative Content |
|---|---|---|
| 1. Understand the principles of systems analysis and design. | 1.1 Explain how systems analysis and design contributes to the software development life cycle. 1.2 Describe the components of systems analysis. 1.3 Analyse different approaches to system analysis and design. 1.4 Evaluate system design requirements. 1.5 Explain the importance of each stage in traditional software lifecycle approaches. 1.6 Evaluate software development lifecycle models. 1.7 Explain hard and soft system methodologies. |
● Basic definitions and motivations of HCI, including history, theories, interaction paradigms, design principles and models. ● User centred design methods comprising user studies ● Input ● Processing ● Output ● Design approaches for interfaces and interaction ● Quality factors ● Evaluation methods ● Techniques for data analysis. ● Research frontiers of HCI, including accessibility, universal design, and pervasive computing (ubiquitous, mobile and wearable applications). ● Lifecycle stage and connectivity: feasibility study, analysis, design, implementation, testing, review or analysis, design, implementation, maintenance, planning; requirements traceability. ● Lifecycle models: understanding and use of predictive (Waterfall, Prototyping, RAD) and adaptive (Spiral, Agile, DSDM) software development models. ● Test and integration: building test environments; developing test harnesses; black box/white box testing; incremental testing; acceptance test and integration approaches; changeover strategies, trials and Go-Live prerequisites. ● Prototyping methodology ● End user categorisations, classifications and behaviour modelling techniques. ● Agile, Cleanroom, Incremental, Prototyping, Spiral V model, Waterfall. |
| 2. Understand system design methodologies and modelling. | 2.1 Explain types of information systems. 2.2 Evaluate how the functionality of information systems varies between different information systems. 2.3 Explain system design concepts. 2.4 Evaluate different system design methodologies. |
● Information system types: Business information systems, decision support systems, management information systems, strategic/executive information systems, office information systems, transaction processing systems, expert systems, global information systems, data warehouse systems, enterprise systems, enterprise resource planning systems, integrated information systems. ● Categories of information systems: operational, tactical and strategic information systems ● Agile development methodology. ● DevOps deployment methodology ● Waterfall development method ● Rapid application development |
| 3. Understand human computer interface (HCI). | 3.1 Explain the principles of HCI. 3.2 Explain how HCI improves the user experience of a system 3.3 Explain the considerations to make in relation to HCI when designing a system 3.4 Evaluate HCI methodologies. |
● Definition of information and data, sources of information, information requirements and the needs for information at different levels within an organisation; storing information and its importance regarding security, accuracy and relevance; outputs e.g., payroll, invoicing, ordering, bookings, stock control, personnel records, goods tracking, decision-making, marketing, customer service. ● Management information: Reports e.g., sales report, college enrolment statistics, marketing analysis (brick v click), trends in the market, competition and market share, – management of computer systems, staffing, maintenance, project management and scheduling. ● Selecting information: Analysis of information in terms of validity, accuracy, currency and relevancy; identifying and rationalising meaningful information from data sets. ● Uses: Proficiency in terms of accessing quality information that can be used for decision- making, problem- solving, predictions, trending and forecasting. ● Accessibility ● Functionality ● Useability ● Icons ● Colours ● Layout ● Speed ● Security ● Flowcharts; Pseudocode; Formal specification Methods; Event/State/Data Driven; Finite State. Machines (extended- FSM)/FSP; problem of e- FSM state explosion; reachability analysis. ● Docker, CoreOS, Cloud Foundry, Kubernetes and OpenStack. ● DevOps and continuous integration practices, as well as the deployment tools available to architects to meet and exceed their business goals. |
| 4. Be able to produce a system design using modelling techniques. | 4.1 Create a system design document. 4.2 Produce a model of a software system. 4.3 Produce a security and control design. |
● System design document: purpose, design ideas, aim, audience ● Software Determinations: The usefulness of the product and imperatives on its activity should be characterized. ● Software Turn Of Events: The product to meet the prerequisite should be created. ● Software Approval: The product should be approved to guarantee that it does what the client needs. ● Software Development: The product should advance to meet changing customer needs. ● The model should illustrate how a real-life system would work |
Assessment
To achieve a ‘pass’ for this unit, learners must provide evidence to demonstrate that they have fulfilled all the learning outcomes and meet the standards specified by all assessment criteria.
| Learning Outcomes to be met | Assessment criteria to be covered | Type of assessment | Word count (approx. length) |
| LO1, LO2 | All ACs under LO1, LO2, LO3 | Coursework | 2500 words |
| LO3 | All ACs under LO3 | Presentation | Presentation and 500 words |
| LO4 | All ACs under LO4 | Project | N/A |
Need help with OTHM Level 4 IT assignment? Get support now
Order Non Plagiarized Assignment
The post OTHM Level 4 Unit Systems Analysis and Design (F/617/2266) Assignment Brief 2026 appeared first on Students Assignment Help UK.