 |
Computer Platforms
Computer Platforms
This unit is aimed at practitioners who need sufficient knowledge to make decisions on the selection/specification of systems and to use computer hardware and software effectively. Students will be shown how to use operating systems to create their own operating environment and participate in its development. Many practitioners communicate with specialist technical support staff during the specification and planning of systems implementation. This unit aims to give practitioners the confidence to communicate with technical specialists and to validate their recommendations CONTENTS
1. Computer system Processor: description of components (Von-Neuman architecture), terminology (e.g. bits, bytes, kilobytes etc), identification of factors affecting performance (e.g. MIPS, FLOPS, clock speed, computer performance indexes, bus architecture). Backing Store: identification of types (disc, CD etc), performance factors (e.g. data transfer rate, seek times, capacity) Peripherals: description of available peripherals (display, printers etc), understanding of performance factors (e.g. display-performance, resolution, colour planes, video RAM, refresh rate, interlacing, slot pitch etc. printer-speed, resolution, image quality, software requirements, postscript, PCL and associated printer control) Computer Selection: specification of requirements, evaluating the performance of the selected system. 2. Operating systems Operating system functions: overview of functions (e.g. user interface, machine and peripheral management etc), comparison between functions of different types of operating systems (personal computers, net work, mainframe etc) Computer operations: use of a proprietary operating system, generation of environment and systems for a computer user (file/directory structures, tailoring of screen interface, backup systems etc). Network administration: user management (maintenance of work groups, security etc) 3. Computer system Upgrading opportunities: overview of opportunities (e.g. memory, additions of cards etc. current de facto standards) 4. Network installation Network resources: components of a network (e.g. network operating systems, nodes, communication systems, server, network cards etc) functions of components, understanding of networking principles (e.g. packets, communications protocols topologies etc) External links: external information systems (e.g. email, internet, intranet) knowledge of capacity of external communications systems (e.g. ISDN, radio etc.) Network planning: creating an implementation schedule, producing a plan containing location of nodes, repeaters etc. and server capacities for a specific set of defined applications. User support planning: identifying user training needs, producing a training schedule, functions of a help desk Security: physical and logical security measures, back-up and recovery, hacking, encryption, levels of access rights
|
 |
Systems Analysis
Systems Analysis
This unit will give students the ability to compare the different lifecycle models. It will provide the foundation of systems analysis and design by covering requirement analysis for both commercial and technical applications. It will also introduce the data and functional modelling techniques which students can be expected to use. The unit provides the opportunity for students to implement the data models using a proprietary database. Contents 1.Lifecycles models: Systems lifecycle: the stages of a chosen cycle (eg specification, design, detailed design code and unit test, integrated and test, maintenance), the purpose of each stage, definition of validation and verification Evaluation of models: comparison of a chosen mode l with other techniques (e.g. prototyping, dynamic systems analysis or object-based methods) 2. System investigation Fact finding techniques; interview, observation, investigation, questionnaire Fact recording methods and standard: current computer and paper based fact-recording methods such as grid charts, flow diagrams, and standard documentations technique 3. Functional and data modelling Functional modelling: identification of system processes and functions, data flow diagrams and process modelling techniques Data modelling; top down techniques, entity relation modelling, implementations of simple relational system using a proprietary database
|
 |
Software Constructs & Tools
Software Constructs & Tools
The aim of this unit is to provide students with an awareness of wide range of problems within computing, the way that problem and solution can be modelled and techniques to solve them. They will be introduced to the concept of business model and will be shown how to use spreadsheets to model current and future situations. The unit also profiles students with the opportunity to perform some coding; albeit within the framework of appropriate mechanisms. Although a third-generation programming languages is the most appropriate, centre could consider spreadsheets, data bases, 4GLs or knowledge-based expert systems as alternatives Contents 1. Problem-solving theory, applications and techniques Problem solving applications: an overview of the areas within computing (eg system design, software development and computer management) where problem solving is appropriate and examples of applications within those areas Overview of problem-solving theory and technique: well defined and ill defined problems techniques available (e.g. abstractions and generalisations, brainstorming, decision trees, project management, algorithms) Testing and documenting the solution: recognition that every proposed solution requires testing and documentation before implementation, testing and documentation templates for software development 2. Business Models Model definition: a description with appropriate examples of how numerical information can model both current and future views of an organisational problem Spreadsheet features: description and use of the features of spreadsheets (formulae, graphs, functions etc) Design and implementation of spread-sheet based model: the production of a design from a specification, the implementation to satisfy the design, test the solution, use with various 'what if' scenarios 3. Programme methodology Storage: the concept of data storage within a computer program, using variables, constants and literals Control structures: identify and select appropriate iterative and selections structures when writing simple programs Programming language syntax: the facility and rules of the language (operator, I/O commands, functions) Program design: algorithm method for the development of a solution to a problem (structure diagrams, pseudo code etc), producing tested programs to meet given specifications Programming standards and practice: use of comments, consistent indentations and descriptive identifiers
|
 |
Computing solutions
Computing solutions
Organisations have always depended on information to ensure success. Over the years organisations have changed their information systems from dealing purely with data processing to strategic and decision support. Managers need information to plan successfully in the short, medium and long term. It is also recognised nowadays that information is required at all levels in an organisation and that information itself can have many sources. The importance of valid information system is gaining competitive advantage needs to be stressed. Students will gain an understanding of the ways in which data can be processed and the applications that support organisations. They will also be asked to evaluate the capacity of an information system to satisfy the needs of the user. Contents 1. Information and contemporary applications Information and data: definition of information and data, sources of information, information requirement and the needs of information at different levels within an organisation, storing information and its importance with regard to security, accuracy and relevance. Contemporary applications: operational transaction processing, managerial decision making, executive information systems 2. Information processing Tools: description of current tools (e.g. text processor, client server, databases, artificial intelligence, expert systems, data warehousing), description of the use of telecommunications (e.g. internet, email etc.) Information processing: transaction processing, information presentation and reporting strategic advantage and problem solving, relationship with tools. 3. Information systems within an organisation Measures: evaluation/criteria, e.g. accuracy, suitability, timeliness, cost, confidence, legal, ethical and social issues.
|
 |
Computer Implementation Project
Computer Implementation Project
The aim of this unit is to help students integrate the skills and knowledge they have acquired during the course to produce a soft ware-based solution to a realistic problem. The emphasis may vary widely (e.g. 3GL procedural programming, object-based programming, event-driven programming, declarative programming, internet/intranet, multi-media,. Database development via 4GL, application development via macros, software engineering principles, A and quality manuals etc), but students must produce a software application. This is a major piece of work that should demonstrate the performance expected at an HND Computing/ software Engineering level. The problem may be work-based, college -based, or a student interest but it must be developed in accordance with the unit's framework and constraints. This will develop the ability to produce an acceptable and viable software solution to an agreed specification within a defined timescale and constraints. Contents 1. Plan an appropriate project Project selection: research and review areas of interest, select and appraise the feasibility of the chosen project. Project specification: identify, structure and develop a list of user requirement relevant to the chosen project into a project specification Project plan: produce an appropriate computer-based plan for the project including timescales, deliverables, and milestones etc. for a Software Engineering project this should also include quality assurance system and quality plan etc 2. Develop the project Design / structure: consider alternative design methods/techniques and environment which could include the use of structured design, object design, real time design, graphical displays, story boarding, data analysis etc. Development: review, select and use suitable software to implement the project Documentation: documents all stages to agreed standards 3 Verify the project Plan: formulate and agree a verification plan, which ensures the developed product, fulfils its specification Verification techniques: review, select and use appropriate verifications techniques-these will vary according to the nature of the project but must include software testing techniques such as black box and / or White Box and should be relevant to the type of software used for the project. Implementation: Implement and document the agreed verification plan 4. Evaluate the project Demonstration: this will vary according to the project but should include a demonstration of a software solution, which is well organised, structured and delivered by the student Audience: demonstration should be to a know audience (peer group, tutor etc) Documentation: the content will differ according to the specific project but in each case it should include complete relevant documentation of all stages of the project to agreed standards, critical evaluation of the project
|
 |
Software Engineering Implementation Project
Software Engineering Implementation Project
The aim of this unit is to help student to integrate the skills and knowledge they have acquired during the course to produce a software-based solution to a realistic problem. The emphasis may vary according to the chose outcomes. This is a major piece of work that should demonstrate the performance expected at an HN Computing/ software Engineering level. The problem may be work-based, college -based, or a student interest but it must be developed in accordance with the unit's framework and constraints. This will develop the ability to produce an acceptable and viable software solution to an agreed specification within a defined timescale and constraints. Contents 1. Plan an appropriate project Project selection: research and review areas of interest, select an appropriate project, devise a structure and produce aim for the project, estimate and list required resource for the chosen project. Project plan: produce an appropriate computer-based plan for the project including timescales, deliverables, and milestones, quality assurance systems, quality plans etc. Project specification: identify, structure and develop a list of user requirement relevant to the chosen project and acceptable to client, produce an outline and a detailed design for the project in relation to the requirement using standard methods, document the project specifications. Or 1.Plan an appropriate project to an agreed specification Project selection: research and review areas of interest, select an appropriate project, devise a structure and produce aim for the project, estimate and list required resource for the chosen project. Project plan: produce an appropriate computer-based plan for the project including timescales, deliverables, and milestones, quality assurance systems, quality plans etc. Design/structure: consider alternative design methods/techniques and environment which could include the use of preliminary design, detailed design, data design, object design, real time design, graphical displays, story boarding, data analysis etc. Development: review, select and use suitable software to develop the project Development: 2. Verify the project Plan: formulate and agree a verification plan which ensure the developed product fulfils the project objectives Verification techniques; review, select and use appropriate verifications techniques-these will vary according to the nature of the project but must include user verification, statistical survey, questionnaires, software techniques such as Black Box and/or White Box etc.
|
|
 |
|
|
|
 |
Bussiness IT Implementation Project
Bussiness Information Technology Implementation Project
The aim of this unit is to help student to integrate the skills and knowledge they have acquired during the course to produce a software-based solution to a realistic problem. The emphasis may vary according to the chose outcomes. This is a major piece of work that should demonstrate the performance expected at an HN Computing/ software Engineering level. The problem may be work-based, college -based, or a student interest but it must be developed in accordance with the unit's framework and constraints. This will develop the ability to produce an acceptable and viable software solution to an agreed specification within a defined timescale and constraints. Contents 1. Plan an appropriate project Project selection: research and review areas of interest, select an appropriate project, devise a structure and produce aim for the project, estimate and list required resource for the chosen project. Project plan: produce an appropriate computer-based plan for the project including timescales, deliverables, and milestones, quality assurance systems, quality plans etc. Project specification: identify, structure and develop a list of user requirement relevant to the chosen project and acceptable to client, produce an outline and a detailed design for the project in relation to the requirement using standard methods, document the project specifications. Or 1.Plan an appropriate project to an agreed specification Project selection: research and review areas of interest, select an appropriate project, devise a structure and produce aim for the project, estimate and list required resource for the chosen project. Project plan: produce an appropriate computer-based plan for the project including timescales, deliverables, and milestones, quality assurance systems, quality plans etc. Design/structure: consider alternative design methods/techniques and environment which could include the use of preliminary design, detailed design, data design, object design, real time design, graphical displays, story boarding, data analysis etc. Development: review, select and use suitable software to develop the project Development: 2. Verify the project Plan: formulate and agree a verification plan which ensure the developed product fulfils the project objectives Verification techniques; review, select and use appropriate verifications techniques-these will vary according to the nature of the project but must include user verification, statistical survey, questionnaires, software techniques such as Black Box and/or White Box etc.
|
 |
Quality Management Principles
Quality Management Principles
The unit will enable students to learn about quality assurance through the maintenance of an existing computer system. It will deal with the quality assurance and professional issues related to computer systems implementation and management. It will be left to centre so select an appropriate system development method as a vehicle to cover the units requirements, if the unit is delivered within a course which contains software development method relevant to the software tools used is suggested Contents 1. Systems analysis and design tools Systems analysis and design tools: graphical and text-based tools appropriate for the methodology chosen, tools which define both the environmental and behavioural perspectives of a system, tools designed for process/functional modelling (e.g. state transitions, even traces) object modelling (e.g. object diagram, CRCs) and data modelling Project management: production of simple critical path networks, using computer based project management tools Systems maintenance: change request form, the production of a new version of the analysis and design documentation for a project developed using the selected methodology, use of computer based text and presentation packages for documentation, maintenance of cross referencing and indexes 2.Quality assurance Quality assurance factors: meeting specifications, budget, delivery time, maintainability, and external and internal quality systems Quality: assurance tools: quality manual, quality plan, project plan, configuration management, and walkthrough and inspection records 3. Professional standard Legal requirements: the requirement of current legislation affecting the implementation and management of computer systems (e.g. health and safety, data protection) Professional requirements: professional standards required by professional computing bodies (e.g. British Computer Society) problem arising from lack of compliance with professional standards
|
 |
Communication Technology
Communication Technology
Communications systems including networks, telecommunications and digital broadcasting are pivotal to the development of modern information and transaction systems. Mangers need to be involved in specifying and evaluating such systems. This unit will provide the required knowledge to specify and manage communication networks in the light of the needs of the organisation. It will also provide skills, which will enable the practitioner to make informed decisions on communication strategies in the workplace. Contents 1. Performance of communication systems Performance factors: the bandwidth required for given applications including text, graphics, video, and speech, options for providing bandwidth, evaluation of acceptable network performance, cost of providing and monitoring performance Communication technologies: a survey of hardware components (e.g. modems, fast internet routes etc) a survey of communications standards e.g. ATM, FDDI etc Human factors: the trade off between ideal and acceptable performance, user requirements versus business needs 2. Impact of communication technology Business factors: the commercial opportunities presented by new communication technologies, information content of intranets and the benefits of sharing of this information within an organisation, the internet as a source of information, trading, advertising and marketing opportunities, application of digital broadcasting Communication factors: security of transactions over the internet, the use of LANs and WANs as a means of increasing efficient communication in an organisation, software and file format, version control across an organisation (avoidance of multiple incompatible formats) electronic fund transfer systems, role of communication devices (eg web servers, routers) 2. Cost and security Development costs: the accurate costing for a particular system to include hardware, software, staff training, data conversion from previous systems, acceptance trails, pilot schemes etc planning the future costs of repetitive hardware and software upgrades, the cost of server based compared with workstation-based application software in terms of hardware maintenance contracts cost and the costing of providing use help facilities Security costs: cost and value of data and information on a network, cost associated with re-building and checking consistency following system failure or unauthorised access, the costs and loss of willing staff participation as a result of over zealous security measures Security mechanisms: security mechanisms supplied by the network system including backup and data restoration, passwords, ownership and access rights, physical security devices (e.g. RAID servers, disc mirroring, ring back etc), software security e.g. transactions rollback
|
 |
Advance Computing Project
Advance Computing Project
The aim of this unit is to help students integrate the skills and Knowledge they have acquired during the course to produce a solution to a realistic problem. The emphasis in contrast with level one project units, should be to provide a distinctive area of study appropriate to the Computing pathway in the HNC/HND. The business information technology and software Enineering pathways provide emphasis in those areas, whereas the computing pathway is a general qualification in computing. Therefore, the project undertaken in this unit should show as much integration as possible of the abilities across units already completed or are currently underway. This may vary from one student and (where possible) the needs of employers. The subject area may vary widely (eg the production software, the use or automation of application software, the specification and implementation of a computerised solution to a problem etc), however the emphasis should be on applying existing knowledge and skills rather than new knowledge.This is a major piece of work that should demonstrate the performance expected at an HN level 2 and reflect the double value in both workload and content. The problem may be work-based, college-based or a student interest, but it must be developed in accordance with the unit's framework and constraints. Contents 1. Plan an appropriate project Project selection: review areas of study already undertaken in the Computing pathway (or skills acquired elsewhere but directly appropriate to the Computing pathway) and select an area of interest, appraise the feasibility of the project in terms of workload, level of ability required, estimates of timescale and resources available. Project specification: identify, structure and develop a user specification relevant to the project then develop a detailed technical specification, both these specifications to be in a form appropriate for presentation to management in a real or simulated work environment. The aim is to allow such managers to have sufficient information to make an informed decision about the viability of the project. Project plan: produce a realistic plan for the project including timescales, deliverables, milestones, resource requirements etc 2. Develop the project Design: consider all possible solution to the problem, evaluate these solutions then select the most viable, select a suitable design method and apply it to the selected solution, consider adventurous or radical solutions even if the final solution is conventional Development: review, select and use suitable software, hardware or systems to implement the project, monitor development against the agreed plan and take appropriate action if the project does not always go to plan. Students should show awareness of this and the ability to take effective action to mitigate the effects of unforeseen problems Documentation: document all aspects of the project to agreed standards 3. Verify the project or plan appropriate action Verification plan: formulate and agree a verification plan which ensures the developed product fulfils its specification Verification techniques: review, select and use appropriate verification techniques - these will vary according to the nature of the project but must include testing techniques such as Black Box and/or White Box and should be relevant to the type of software used for the project Verification implementation: implement and document the agreed verification plan 4. Evaluate the project Demonstration: this will vary according to the project but should include a demonstration of the solution which is well organised, structured and delivered by the student Audience: demonstration should be to a known audience (peer group, tutors etc) and the audience should include those who would have approved the project against the plan in Outcome 1 Documentation: content will differ according to the specific project but in each case it should include complete relevant documentation of all stages of the project to agreed standards and the completion of a critical evaluation Future development: Most projects seldom achieve the perfect solution at the first attempt, demonstrate the route that must be taken to develop the project further and the methods to be used
|
 |
Advanced Software Engineering Project
Advanced Software Engineering Project
This unit will form a central part in the development of the student's ability to link and integrate the knowledge and skills acquired during the programme to produce a practical solution to a realistic problem. The unit will encourage team work but assessment will be based on the individual work. Student(s) will undertake a complete and realistic project and successfully complete it within the time constraint imposed, working within a group and individually when necessary. The project will span all the lifecycle stages for the development of software, from planning to implementation and maintenance. The problem may be work-based, college-based or student interest but it must be developed in accordance with the unit's framework and constraints. Content 1. Project plan Planning stage: state the project aims, structure the project, test the project plan through simulation, review the project plan, schedule the project, establish control Estimate and list required resource: feasibility study, human resources, hardware resources, software resources Managing the project: planning, organising, staffing, directing and controlling Use of software support tools: develop, construct, implement and test the project planning 2. System analysis and design Analysis stage: requirement definition, analysis type implemented, information gathering, profiling the organisation, finalise the target requirements, confirm the requirements, agree the specification with the client, document the project specification (user requirement) Design stage: Preliminary design, detail design, data design, architectural design, procedural design, modular design, structured design, object design, real time design, graphical display, store boarding etc Use of case tool: notations, techniques, methods selected and used 3. Program coding Programming languages: select the languages suitable for the project, specify the language and the part of the project it deals with Programming techniques: list the types of techniques which will be implemented and where each technique will be used in the project Program requirement: data type and declarations, assignments and expressions, control structures, subprograms including recession, arrays and records, data structure, algorithms Program testing: functional testing (black box), Structural testing (white box) 4. Solution Hardware installation: develop hardware installation procedures, link all hardware together to form a complete hardware system, format the necessary hardware, test the hardware system operation Software installation: develop software installation procedures, copy software to hardware using correct procedure, reboot system hardware Testing activities: unit testing, link testing, integrating testing, validation testing, system testing 5. Quality and maintainability Quality and standards: quality assurance, quality matrices, standards for quality (BS, ISO) Maintenance: type of maintenance to be used, maintenance phases and their schedules, configuration management 6. Evaluate the project Presentation: this will vary according to the project but should include a presentation of each outcome and full solution which should be well organised, structured and delivered by either the individual student, or a group of students if it is a group project Audience: is should be presented to a known audience (peer group, tutors, internal and external supervisors, clients etc) Documentation: the content will differ according to the specific project but in each case it should include complete relevant documentation of all stages of the project to agreed standards, and a full a critical evaluation
|
 |
Advanced Business IT Project
Advanced Business Information Technology Project
This unit which has a value of 2 will be a significant piece of work designed to integrate H2 units. Knowledge and skills developed throughout the course are drawn on to deliver practical and realistic solutions to business-related problems.Students are expected to analyse a business problem, understand its context, and plan and design a suitable solution. The project should be chosen by the student, under guidance from the centre to establish an appropriate level of study.
Content
1 Identify a realistic business problem
Problem identification: sources of information/ideas, investigations, problem domains, finding and recording facts.
Options and solutions: problem-solving techniques, comparative/contrasting problems, feasibility assessment, methodologies and communication proposals.Project management: planning, estimating, resource allocation, budgeting, monitoring and control techniques, use of computer-based tools
2 Specify and design a solution
Requirements specification: development, maintenance and operating environments, functional requirements and constraints, external interfaces, data flows, screen mock-ups, dialogues, reports, data dictionaries.
Quality assurance: exception handling, verification procedures, event identification, acceptance criteria, standards for documentation and testing, service level agreements
Design: data analysis and design, application design, user interfaces, dialogues, design specifications, non-computer procedures, models prototypes and design walkthroughs, job descriptions, service levels, logging systems, security and audit procedures, use of software tools appropriate to chosen project
3 Implement the project
Content for Outcome 3 will depend on the nature of the selected project but will typically consist of the following:
Implementation: methods and techniques, user involvement, implementation, planning documentation support, selection and support changeover (eg pilot, parallel running), help systems, prototyping, user involvement, softwareTesting: test plans, test cases/scenarios, functionality, user interfaces and documentation testing compliance with standards, verification that project meets specification
4 Evaluate the project
Presentation: writing styles, report writing and presentation techniques, use of graphics/illustrations, screen dumps, demonstrations, packaging and delivery, use of appropriate software
Critical evaluation: detailed analysis of results, conclusions and recommendations, ethical and social considerations, planned versus actual costs, opportunities for further studies and developments
|
|
 |
|
|