Learners will investigate the principles of systems analysis and learn how to use systems analysis methods to examine an organisation and its current systems. They will also develop the skills needed to design a system solution to meet organisational requirements.
Understand the principles of systems analysis.
- Systems life cycle stages: definition, investigation and analysis, design, implementation, testing, documentation, evaluation, maintenance.
- Development lifecycle models: Waterfall, other e.g. Spiral, Rapid Applications Development (RAD), agile methodologies, e.g. Scrum, dynamic systems development method (DSDM), adaptive software development (ASD), prototyping, benefits, stages e.g. initiation and feasibility, investigation, requirements analysis and specification, design (logical and physical), build systems, testing, implementation, maintenance.
- Systems analysis tools and techniques: any contemporary methodology for systems analysis and design, typical e.g. activity diagrams, dataflow diagrams, computer-aided software engineering tools (CASE).
- Structured systems analysis and design method (SSADM), Unified Modelling Language (UML), structure (static) diagrams, e.g. class diagram, component diagram, behaviour (dynamic) diagrams, e.g. activity diagram, use case diagram, interaction diagrams, suitability of methods for different programming paradigms, e.g. object-oriented, event-driven, procedural, business process reengineering (BPR).
- Key drivers: business need, e.g. need for growth, company acquisition, need to increase productivity, legal requirements.
Illustrate the stages of the systems lifecycle.
Compare different software development models used by industry.
Assess the suitability of different systems analysis tools and techniques for modelling business processes.
Be able to investigate IT requirements to meet business needs.
- Business needs of an identified organisation: the aims and requirements of an organisation, and how IT is used to support: the services an organisation provides, aims and goals of an organisation, customers – needs, expectations, how product/service is delivered, staff – needs, working styles and patterns, location – staff, customers, premises, market/service delivery point.
- Investigation: techniques e.g. interview, questionnaire, meeting, observation, document analysis, data analysis, sensitivity in collecting information and observing individuals at work.
- Analysis: as related to the chosen methodology, cost-benefit analysis.
- Threats - factors affecting the success and failure of a current system: risks, e.g. completing tasks, budget, missed deadline(s), stakeholder support, staff involvement, constraints, e.g. costs, scope, time, provision of appropriate resources, e.g. people, time, budgets, maintenance system, change management, user involvement in the development process.
- Requirements specification: contents e.g. scope, inputs, outputs, processes, costs and benefits, recommendations, alternative solutions.
Produce a system requirements specification for an identified organisation.
Be able to develop a design for an IT system to meet business needs.
- Design: input and output requirements (appropriate and detailed design documentation for the input and output of the proposed system) including: visuals, e.g. screen layouts, storyboards, alternative layout for different platforms and devices, data entry forms, including layout and structure, proposed fields, data entry methods, report forms, hardware and software requirements.
- Data and processes within a system (the data requirements of and use within a proposed system) including: modelling data, e.g. entity relationship diagrams, data flow diagrams, data dictionaries, e.g. data stores, entities, data structures, validation, process modelling using a variety of tools, e.g. flow charts, decision tables, activity diagrams.
- Testing and maintenance methodologies (a plan for testing and maintenance of the proposed system) including: • testing methods, e.g. volume testing, scalability, multiplatform, developing test plans, identifying test data, e.g. normal, extreme, abnormal, choosing test users, proposed test schedule, proposed maintenance and update schedule.
Produce a design for a system, justifying decisions.
Obtain feedback to refine the design.